Re: [openstack-dev] [nova] Boot from volume 's instance of rescue operation
2017-12-27 20:41 GMT+08:00 Jay Pipes : > On 12/27/2017 05:34 AM, 李杰 wrote: >> >> Hi,all >> >> As we all known,Now the boot from volume 's instance of rescue >> operation is invalid. >> To solve it,I have two plans. >> 1.I plan to use the rescue_image as the root disk,and then make >> the original root volume as the second disk to create new domain,in other >> words,the rescued instance is boot from image.Finally,the user can repair >> the rescued instance. >> 2.I plan to transform the rescue_image to a volume,then make this >> volume as the first disk,and make the original root volume as the second >> disk to create new domain,in other words,the rescued instance is boot from >> volume.Finally,the user can repair the rescued instance. >> Can you give me some advice?Help in troubleshooting this issue >> will be appreciated. > > > Hi Rambo, > > I would not advise either of the above plans. This is yet another problem > with boot-from-volume. > > A better use of your time would be to split the original giant volume into > the operating system part and the application data part. Make the > application data part into a normal non-bootable volume and use a regular > operating system image as your root/boot partition. > > You can't build a palace on quicksand. Actually, this is not a like what your said. I think we should judge the type of instance. If it is boot from image, then go original. If it is boot from volume, then the image must be a bootable volume. This is more make sense. > > Best, > -jay > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- 谦谦君子 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] Boot from volume 's instance of rescue operation
On 12/27/2017 05:34 AM, 李杰 wrote: Hi,all As we all known,Now the boot from volume 's instance of rescue operation is invalid. To solve it,I have two plans. 1.I plan to use the rescue_image as the root disk,and then make the original root volume as the second disk to create new domain,in other words,the rescued instance is boot from image.Finally,the user can repair the rescued instance. 2.I plan to transform the rescue_image to a volume,then make this volume as the first disk,and make the original root volume as the second disk to create new domain,in other words,the rescued instance is boot from volume.Finally,the user can repair the rescued instance. Can you give me some advice?Help in troubleshooting this issue will be appreciated. Hi Rambo, I would not advise either of the above plans. This is yet another problem with boot-from-volume. A better use of your time would be to split the original giant volume into the operating system part and the application data part. Make the application data part into a normal non-bootable volume and use a regular operating system image as your root/boot partition. You can't build a palace on quicksand. Best, -jay __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [nova] Boot from volume 's instance of rescue operation
Hi,all As we all known,Now the boot from volume 's instance of rescue operation is invalid. To solve it,I have two plans. 1.I plan to use the rescue_image as the root disk,and then make the original root volume as the second disk to create new domain,in other words,the rescued instance is boot from image.Finally,the user can repair the rescued instance. 2.I plan to transform the rescue_image to a volume,then make this volume as the first disk,and make the original root volume as the second disk to create new domain,in other words,the rescued instance is boot from volume.Finally,the user can repair the rescued instance. Can you give me some advice?Help in troubleshooting this issue will be appreciated. Best Regards Rambo__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev