Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

On-demand serial port connection #858

Closed
hickeng opened this issue May 31, 2016 · 4 comments
Closed

On-demand serial port connection #858

hickeng opened this issue May 31, 2016 · 4 comments
Assignees
Labels

Comments

@hickeng
Copy link
Member

hickeng commented May 31, 2016

To support vMotion while:

  • not requiring the applianceVM be running
  • not requiring a native agent on the ESX host

the only real option we have available is to toggle the connected state of the network serial port.

This will require code in the following components:

  • portlayer/interaction - toggle the port on when an attach request comes in
  • tether - toggle disconnection of the port if no connection established within timeout (allows for vMotion of VM in the case of appliance failure during attach flow).

To keep attach responsive under normal circumstances we should try having every VM connected as they start, dropping that connection after a couple of minutes. The primary drawback of this will be if starting large numbers of VMs that should immediately be vMotioned - should make this configuration, but with programmatic coupling with rate controls for VM start in VMfork scenarios (where single host start point is more likely),

@hickeng hickeng added area/vsphere Intergration and interoperation with vSphere component/portlayer/interaction component/tether labels May 31, 2016
@mdubya66 mdubya66 added this to the GA milestone May 31, 2016
@mdubya66
Copy link
Contributor

GA feature from SSOD

@caglar10ur
Copy link
Contributor

vmotion disconnects file backed serial devices after the migration hence we are potentially losing data.

@hickeng
Copy link
Member Author

hickeng commented Oct 9, 2016

Some additional follow-up issues still outstanding:
#2625
#2626

@mdubya66
Copy link
Contributor

mdubya66 commented Oct 9, 2016

Closing. Other issues are being tracked.

@mdubya66 mdubya66 closed this as completed Oct 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants