Re: [Openstack] [OpenStack][Nova] deference between live-migration and migrate
> From: Vishvananda Ishaya [mailto:vishvana...@gmail.com] > Keep in mind that we actually have three options Good point, I forgot about resize. I guess we have: - Live Migrate (with/without block migrate) - (Non-live) Migrate - Resize I guess the more general way of looking at this is having an "optional scheduler hint": - user might want to live-migrate to a different availability zone - user might want to resize to same availability zone - admin might what to migrate (live or otherwise) to a specific server > Yun actually suggested that resize/migrate be simplified to do the following > instead of scping the file over: > * snapshot to glance > * boot new image from snapshot > This would definitely simplify the code, unfortunately it could have > billing/metering repercussions. Forgot about that, I like that too. To get the same semantics, I guess it would be: stop VM, snapshot VM, start new VM, destroy old VM, allow user to delete snapshot. Rollback just resumes VM and deletes snapshot. I guess you could have something like "this will use data" warning you get on mobiles, but something like: "This operation involves you being billed for a snapshot. You may delete the snapshot once the operation has completed" What do people think about the billing issues from this change? Cheers, John ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [OpenStack][Nova] deference between live-migration and migrate
I would favour a field for the type of migration which allows future expansion. we've already got migrate, live migrate and block migrate but hypervisors may have further different flavours too in the future and the API should support the full set of options while encouraging convergence when there are common functionalities. How about we move the API flag to a text field for the migration type ? For private clouds without billing concerns, a snapshot/restart option may be more attractive. Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of David Kranz Sent: 31 May 2012 20:29 To: openstack@lists.launchpad.net Subject: Re: [Openstack] [OpenStack][Nova] deference between live-migration and migrate On 5/31/2012 2:10 PM, Vishvananda Ishaya wrote: On May 25, 2012, at 2:36 AM, John Garbutt wrote: I have been meaning to draft a blueprint around this. What we have today: . Migrate: move a VM from one server to another, reboots across the move (I think) and destination is picked by scheduler . LiveMigration: move a VM form one server to another, VM doesn't appear to reboot, need to specify the destination I propose we extent the Migrate API (thinking about nova CLI here really) to include: . Optional Flag to force non-live migration, default to live migration . Optional destination host, by default let the scheduler choose . Deprecate the existing live migration API and CLI calls What do people think? +1 Keep in mind that we actually have three options: live migration on shared storage live migration without shared storage (block migration) resize/migrate Yun actually suggested that resize/migrate be simplified to do the following instead of scping the file over: * snapshot to glance * boot new image from snapshot This would definitely simplify the code, unfortunately it could have billing/metering repercussions. Vish I don't think it is documented that you need to set up ssh with credentials between compute nodes to make resize and block migration work. I also heard something about there being a more secure way to do this than setting up ssh in this way. What is the "officially recommended" way to configure compute nodes for these operations? -David smime.p7s Description: S/MIME cryptographic signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [OpenStack][Nova] deference between live-migration and migrate
On 5/31/2012 2:10 PM, Vishvananda Ishaya wrote: On May 25, 2012, at 2:36 AM, John Garbutt wrote: I have been meaning to draft a blueprint around this. What we have today: ·Migrate: move a VM from one server to another, reboots across the move (I think) and destination is picked by scheduler ·LiveMigration: move a VM form one server to another, VM doesn't appear to reboot, need to specify the destination I propose we extent the Migrate API (thinking about nova CLI here really) to include: ·Optional Flag to force non-live migration, default to live migration ·Optional destination host, by default let the scheduler choose ·Deprecate the existing live migration API and CLI calls What do people think? +1 Keep in mind that we actually have three options: live migration on shared storage live migration without shared storage (block migration) resize/migrate Yun actually suggested that resize/migrate be simplified to do the following instead of scping the file over: * snapshot to glance * boot new image from snapshot This would definitely simplify the code, unfortunately it could have billing/metering repercussions. Vish I don't think it is documented that you need to set up ssh with credentials between compute nodes to make resize and block migration work. I also heard something about there being a more secure way to do this than setting up ssh in this way. What is the "officially recommended" way to configure compute nodes for these operations? -David ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [OpenStack][Nova] deference between live-migration and migrate
On May 25, 2012, at 2:36 AM, John Garbutt wrote: > I have been meaning to draft a blueprint around this. > > What we have today: > · Migrate: move a VM from one server to another, reboots across the > move (I think) and destination is picked by scheduler > · LiveMigration: move a VM form one server to another, VM doesn’t > appear to reboot, need to specify the destination > > I propose we extent the Migrate API (thinking about nova CLI here really) to > include: > · Optional Flag to force non-live migration, default to live migration > · Optional destination host, by default let the scheduler choose > · Deprecate the existing live migration API and CLI calls > What do people think? +1 Keep in mind that we actually have three options: live migration on shared storage live migration without shared storage (block migration) resize/migrate Yun actually suggested that resize/migrate be simplified to do the following instead of scping the file over: * snapshot to glance * boot new image from snapshot This would definitely simplify the code, unfortunately it could have billing/metering repercussions. Vish > > I am in the process of adding Live migration support to XenServer: > https://blueprints.launchpad.net/nova/+spec/xenapi-live-migration > > If people like the idea, I should get chance to draft and implement this for > Folsom, but I am happy for others to do this if they are also interested. > > Cheers, > John ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [OpenStack][Nova] deference between live-migration and migrate
Hey Eric. On 05/25/2012 10:54 AM, Eric Luo wrote: > I know that live-migration means "live migration" of an instance. Yes. Premise is that you use shared storage. > But what is this "migrate “ for ? And what does "Migrate a > server." mean here :)Does it mean "Migrates a *non-running *instance > to a new machine" here? For migration you don't need shared storage, local storage is sufficient. The instance will be stopped and afterwards will be moved to the target system of the migration. HTH, Christian. -- Christian Berendt Solution Architect Mail: bere...@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [OpenStack][Nova] deference between live-migration and migrate
I have been meaning to draft a blueprint around this. What we have today: * Migrate: move a VM from one server to another, reboots across the move (I think) and destination is picked by scheduler * LiveMigration: move a VM form one server to another, VM doesn't appear to reboot, need to specify the destination I propose we extent the Migrate API (thinking about nova CLI here really) to include: * Optional Flag to force non-live migration, default to live migration * Optional destination host, by default let the scheduler choose * Deprecate the existing live migration API and CLI calls What do people think? I am in the process of adding Live migration support to XenServer: https://blueprints.launchpad.net/nova/+spec/xenapi-live-migration If people like the idea, I should get chance to draft and implement this for Folsom, but I am happy for others to do this if they are also interested. Cheers, John From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On Behalf Of Eric Luo Sent: 25 May 2012 09:55 To: openstack@lists.launchpad.net Subject: [Openstack] [OpenStack][Nova] deference between live-migration and migrate Hello ,all I saw there are tow commands in nova live-migration Migrates a running instance to a new machine. migrate Migrate a server. I know that live-migration means "live migration" of an instance. But what is this "migrate " for ? And what does "Migrate a server." mean here :)Does it mean "Migrates a non-running instance to a new machine" here? Thank you! Best regards! Eric Luo 2012-05-25 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] [OpenStack][Nova] deference between live-migration and migrate
Hello ,all I saw there are tow commands in nova live-migration Migrates a running instance to a new machine. migrate Migrate a server. I know that live-migration means "live migration" of an instance. But what is this "migrate “ for ? And what does "Migrate a server." mean here :)Does it mean "Migrates a *non-running *instance to a new machine" here? Thank you! Best regards! Eric Luo 2012-05-25 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
