Re: [Openstack] Migration
Hi there, On Wed 29 Aug 2012 (17:15), Tim Bell wrote: I think a new release should contains details of how to do the upgrade (rather than discovering as we try it) I should aim that the deliverables for each of the projects in a new version includes in the release notes: A. dependencies (i.e. does glance folsom need to talk to horizon folsom or can it also talk to horizon essex) I totally agree on this. It is important to know which components need to be upgraded in a row and which are interoperable. Sometimes it is not possible (or desirable) to upgrade the whole system at a time, but perform several small upgrade steps. -- Álvaro López García al...@ifca.unican.es ___ 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] Migration
I think a new release should contains details of how to do the upgrade (rather than discovering as we try it) I should aim that the deliverables for each of the projects in a new version includes in the release notes: A. dependencies (i.e. does glance folsom need to talk to horizon folsom or can it also talk to horizon essex) B. migration steps to move an instance to the latest version (i.e. how do I get glance essex to glance horizon) Planning an production upgrade will be very time consuming if it requires the person(s) to understand all the components in depth and derive the steps from the bug fixes. One of the items to review within the user/project feedback loop would be how we validate for a release (I used to call this system test as opposed to integration test, years ago). This would be the steps where we validate that a release complies with a set of deployability criteria (such as migration steps and documentation). Would the upcoming Folsom release meet these criteria (A./B.) for each core project ? Tim It would be fascinating (for me at least :)) to know the upgrade process you use - how many stages you use, do you have multiple regions and use one/some as canaries? Does the downtime required to do an upgrade affect you? Do you run skewed versions (e.g. folsom nova, essex glance) or do you do lock-step upgrades of all the components? For Launchpad we've been moving more and more to a model of permitting temporary skew so that we can do rolling upgrades of the component services. That seems in-principle doable here - and could make it easier to smoothly transition between versions, at the cost of a (small) amount of attention to detail while writing changes to the various apis. -Rob ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp 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] Migration
Perhaps we should also have a CHANGELOG file to explain the major features/changes... Perhaps a 'MIGRATION' file as well that explains how to migrate from version - 1? On 8/29/12 10:15 AM, Tim Bell tim.b...@cern.ch wrote: I think a new release should contains details of how to do the upgrade (rather than discovering as we try it) I should aim that the deliverables for each of the projects in a new version includes in the release notes: A. dependencies (i.e. does glance folsom need to talk to horizon folsom or can it also talk to horizon essex) B. migration steps to move an instance to the latest version (i.e. how do I get glance essex to glance horizon) Planning an production upgrade will be very time consuming if it requires the person(s) to understand all the components in depth and derive the steps from the bug fixes. One of the items to review within the user/project feedback loop would be how we validate for a release (I used to call this system test as opposed to integration test, years ago). This would be the steps where we validate that a release complies with a set of deployability criteria (such as migration steps and documentation). Would the upcoming Folsom release meet these criteria (A./B.) for each core project ? Tim It would be fascinating (for me at least :)) to know the upgrade process you use - how many stages you use, do you have multiple regions and use one/some as canaries? Does the downtime required to do an upgrade affect you? Do you run skewed versions (e.g. folsom nova, essex glance) or do you do lock-step upgrades of all the components? For Launchpad we've been moving more and more to a model of permitting temporary skew so that we can do rolling upgrades of the component services. That seems in-principle doable here - and could make it easier to smoothly transition between versions, at the cost of a (small) amount of attention to detail while writing changes to the various apis. -Rob ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] Migration
On Wed, Aug 29, 2012 at 12:19 PM, Joshua Harlow harlo...@yahoo-inc.com wrote: Perhaps we should also have a CHANGELOG file to explain the major features/changes... Perhaps a 'MIGRATION' file as well that explains how to migrate from version - 1? I think that this would be a great start. In the long term, I would like to be able to do rolling upgrades across a system. It is important in the short term to understand dependencies between components as it pertains to versioning; ie, is it possible to run a folsom keystone with essex nova? Or could an essex nova-compute interact with a folsom nova-api? What are the hard and soft requirements for version mixing? I've had decent success performing rolling upgrades between versions of nova-compute in terms of the ubuntu maintenance releases of essex, but I suspect in general this is way too high of a bar to expect for all components. Even building a decent mental map of interdependencies would help a lot when planning maintenance activities. -nld ___ 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] Migration of Single, Dual and Multi node
Dear OpenStack Community, is it possible to install a single-node environment and then later on upgrade it to a dual-node environment and even continue to a multi node environment ? I know that it is possible to install all the openstack components (Nova, Glance, Swift) on all nodesyou are using in your network but I'm a bit unsure. Does anyone know there I can find the answer to my question ? Thanks for your help and have a nice day, Nicolas ___ 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] Migration of Single, Dual and Multi node
Yes , possible. You need to have the respective components installed as when you progress to dual/multi node have the references(location of Glance/Swift store) corrected in nova.conf respectively. Thanks Meena Raja From: openstack-bounces+raja.meena=wipro@lists.launchpad.net [mailto:openstack-bounces+raja.meena=wipro@lists.launchpad.net] On Behalf Of Nicolas Odermatt Sent: Thursday, April 26, 2012 8:01 PM To: openstack@lists.launchpad.net Subject: [Openstack] Migration of Single, Dual and Multi node Dear OpenStack Community, is it possible to install a single-node environment and then later on upgrade it to a dual-node environment and even continue to a multi node environment ? I know that it is possible to install all the openstack components (Nova, Glance, Swift) on all nodesyou are using in your network but I'm a bit unsure. Does anyone know there I can find the answer to my question ? Thanks for your help and have a nice day, Nicolas Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com ___ 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] migration an shutdown instance and resize
hi： i have some question： nova-manage vm live-migration and block-migration all need the instances is running,if the instance is down how can i migration the instance to another host? when all instances is store an share store(such as nfs or mfs),if the one compute node is down,the instance is down too,how can i boot the instance in another host? is there anybody resize success? how resize an instance? thanks very much : ___ 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] migration an shutdown instance and resize
Hi, instance's resize is something you can do on xenserver only. I did test it succesfully on XenServer 5.6. Live migration and block migration are KVM features: http://wiki.openstack.org/ReleaseNotes/Diablo#Feature_Disparity_KVM_vs_XenServer To properly setup XenServer you should follow this page: http://wiki.openstack.org/XenServerDevelopment Hope it helps Giuseppe 2011/10/21 l jv ljv...@gmail.com: hi： i have some question： nova-manage vm live-migration and block-migration all need the instances is running,if the instance is down how can i migration the instance to another host? when all instances is store an share store(such as nfs or mfs),if the one compute node is down,the instance is down too,how can i boot the instance in another host? is there anybody resize success? how resize an instance? thanks very much : ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] migration an shutdown instance and resize
i use 'nova-mangage vm live-migration' live-migration an kvm instance success,but block migratin does not sucess. i want to use 'nova-mangage vm block-migration' block-migration. resize just support xen? ljvsss From: Giuseppe Civitella Date: 2011-10-21 16:49 To: l jv CC: openstack Subject: Re: [Openstack] migration an shutdown instance and resize Hi, instance's resize is something you can do on xenserver only. I did test it succesfully on XenServer 5.6. Live migration and block migration are KVM features: http://wiki.openstack.org/ReleaseNotes/Diablo#Feature_Disparity_KVM_vs_XenServer To properly setup XenServer you should follow this page: http://wiki.openstack.org/XenServerDevelopment Hope it helps Giuseppe 2011/10/21 l jv ljv...@gmail.com: hi： i have some question： nova-manage vm live-migration and block-migration all need the instances is running,if the instance is down how can i migration the instance to another host? when all instances is store an share store(such as nfs or mfs),if the one compute node is down,the instance is down too,how can i boot the instance in another host? is there anybody resize success? how resize an instance? thanks very much : ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] migration an shutdown instance and resize
oh ,thank you very much :D ljvsss From: Giuseppe Civitella Date: 2011-10-21 18:33 To: ljvsss CC: openstack Subject: Re: Re: [Openstack] migration an shutdown instance and resize Hi, I'm afraid I cannot give you fresh infos about live or block migration on kvm. Yes, AFAIK, resize is only possible on XenSever. Cheers, Giuseppe 2011/10/21 ljvsss ljv...@gmail.com: i use 'nova-mangage vm live-migration' live-migration an kvm instance success,but block migratin does not sucess. i want to use 'nova-mangage vm block-migration' block-migration. resize just support xen? ljvsss From: Giuseppe Civitella Date: 2011-10-21 16:49 To: l jv CC: openstack Subject: Re: [Openstack] migration an shutdown instance and resize Hi, instance's resize is something you can do on xenserver only. I did test it succesfully on XenServer 5.6. Live migration and block migration are KVM features: http://wiki.openstack.org/ReleaseNotes/Diablo#Feature_Disparity_KVM_vs_XenServer To properly setup XenServer you should follow this page: http://wiki.openstack.org/XenServerDevelopment Hope it helps Giuseppe 2011/10/21 l jv ljv...@gmail.com: hi： i have some question： nova-manage vm live-migration and block-migration all need the instances is running,if the instance is down how can i migration the instance to another host? when all instances is store an share store(such as nfs or mfs),if the one compute node is down,the instance is down too,how can i boot the instance in another host? is there anybody resize success? how resize an instance? thanks very much : ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] migration an shutdown instance and resize
Hi, I'm afraid I cannot give you fresh infos about live or block migration on kvm. Yes, AFAIK, resize is only possible on XenSever. Cheers, Giuseppe 2011/10/21 ljvsss ljv...@gmail.com: i use 'nova-mangage vm live-migration' live-migration an kvm instance success,but block migratin does not sucess. i want to use 'nova-mangage vm block-migration' block-migration. resize just support xen? ljvsss From: Giuseppe Civitella Date: 2011-10-21 16:49 To: l jv CC: openstack Subject: Re: [Openstack] migration an shutdown instance and resize Hi, instance's resize is something you can do on xenserver only. I did test it succesfully on XenServer 5.6. Live migration and block migration are KVM features: http://wiki.openstack.org/ReleaseNotes/Diablo#Feature_Disparity_KVM_vs_XenServer To properly setup XenServer you should follow this page: http://wiki.openstack.org/XenServerDevelopment Hope it helps Giuseppe 2011/10/21 l jv ljv...@gmail.com: hi： i have some question： nova-manage vm live-migration and block-migration all need the instances is running,if the instance is down how can i migration the instance to another host? when all instances is store an share store(such as nfs or mfs),if the one compute node is down,the instance is down too,how can i boot the instance in another host? is there anybody resize success? how resize an instance? thanks very much : ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
