Re: [openstack-dev] OPENSTACK with CEPH storage backend cant down size an instance
Agreed on resizing. Perhaps create a snapshot of the old VM (assuming !ephemeral storage), and boot a new VM with a smaller disk size from the snapshot. Future reference you can leverage SAN-specific tools to save unused disk such as thin provisioning and/or the vendor's dedup capabilities. *Adam Lawson* AQORN, Inc. 427 North Tatnall Street Ste. 58461 Wilmington, Delaware 19801-2230 Toll-free: (844) 4-AQORN-NOW ext. 101 International: +1 302-387-4660 Direct: +1 916-246-2072 On Fri, Jul 24, 2015 at 12:11 PM, Monty Taylor mord...@inaugust.com wrote: On 07/24/2015 12:47 PM, Clint Byrum wrote: Excerpts from James Galvin's message of 2015-07-24 09:08:36 -0700: Hi All I am having some trouble with down sizing an instance, I can resize the instance from say small flavour to medium flavour but when trying to resize the instance back from medium to small I get the following : Error: Failed to perform requested operation on instance jg-10, the instance has an error status: Please try again later [Error: Flavor's disk is too small for requested image.]. I am using ceph as the storage backend clustered over 3 nodes with 3 pools volumes vms images In addition to the note already made about reducing filesystem sizes, I just want to reaffirm that resize is really not the way you want to be using clouds, and IMO should be removed from Nova (but there's enough people who disagree with me that it will probably stay). Anyway, I suggest never using resize, and just deploying new servers, running tests, and then deleting the old ones. Having cloud with flexibility and space for this is why you have a cloud. As a person who runs a system with both long-lived pets and cattle that we grind in to food, I can attest that we do not use resize. It is a much longer downtime/risk operation than you want. __ 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] OPENSTACK with CEPH storage backend cant down size an instance
Monty Taylor wrote: On 07/24/2015 12:47 PM, Clint Byrum wrote: Excerpts from James Galvin's message of 2015-07-24 09:08:36 -0700: Hi All I am having some trouble with down sizing an instance, I can resize the instance from say small flavour to medium flavour but when trying to resize the instance back from medium to small I get the following : Error: Failed to perform requested operation on instance jg-10, the instance has an error status: Please try again later [Error: Flavor's disk is too small for requested image.]. I am using ceph as the storage backend clustered over 3 nodes with 3 pools volumes vms images In addition to the note already made about reducing filesystem sizes, I just want to reaffirm that resize is really not the way you want to be using clouds, and IMO should be removed from Nova (but there's enough people who disagree with me that it will probably stay). Anyway, I suggest never using resize, and just deploying new servers, running tests, and then deleting the old ones. Having cloud with flexibility and space for this is why you have a cloud. As a person who runs a system with both long-lived pets and cattle that we grind in to food, I can attest that we do not use resize. It is a much longer downtime/risk operation than you want. +1 I don't believe yahoo enables it either (but I'll double check tomorrow) because it's honestly confusing and rife with potential issues (especially when resize turns into a live migrate that involves the scheduler and scheduler retries). Resizing down is also questionable imho, because afaik it involves shrinking off disks, which means disk shrinkage that is really hard to get right without user input. Probably better to just snapshot and redeploy, or deploy fresh servers and use chef/puppet... to reinstall your application/server from known build instructions/other. __ 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
[openstack-dev] OPENSTACK with CEPH storage backend cant down size an instance
Hi All I am having some trouble with down sizing an instance, I can resize the instance from say small flavour to medium flavour but when trying to resize the instance back from medium to small I get the following : Error: Failed to perform requested operation on instance jg-10, the instance has an error status: Please try again later [Error: Flavor's disk is too small for requested image.]. I am using ceph as the storage backend clustered over 3 nodes with 3 pools volumes vms images -- Regards, James This e-mail contains confidential information or information belonging to Servecentric Ltd and is intended solely for the addressee(s). The unauthorized disclosure, use, dissemination or copy (either in whole or in part) of this e-mail, or any information it contains, is prohibited. Any views or opinions presented are solely those of the author and do not necessarily represent those of Servecentric Ltd. E-mails are susceptible to alteration and their integrity cannot be guaranteed. Servecentric shall not be liable for the contents of this e-mail if modified or falsified. If you are not the intended recipient of this e-mail, please delete it immediately from your system and notify the sender of the wrong delivery and of the email's deletion. __ 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] OPENSTACK with CEPH storage backend cant down size an instance
Excerpts from James Galvin's message of 2015-07-24 09:08:36 -0700: Hi All I am having some trouble with down sizing an instance, I can resize the instance from say small flavour to medium flavour but when trying to resize the instance back from medium to small I get the following : Error: Failed to perform requested operation on instance jg-10, the instance has an error status: Please try again later [Error: Flavor's disk is too small for requested image.]. I am using ceph as the storage backend clustered over 3 nodes with 3 pools volumes vms images In addition to the note already made about reducing filesystem sizes, I just want to reaffirm that resize is really not the way you want to be using clouds, and IMO should be removed from Nova (but there's enough people who disagree with me that it will probably stay). Anyway, I suggest never using resize, and just deploying new servers, running tests, and then deleting the old ones. Having cloud with flexibility and space for this is why you have a cloud. __ 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] OPENSTACK with CEPH storage backend cant down size an instance
* James Galvin jgal...@servecentric.com wrote: Hi All I am having some trouble with down sizing an instance, I can resize the instance from say small flavour to medium flavour but when trying to resize the instance back from medium to small I get the following : Error: Failed to perform requested operation on instance jg-10, the instance has an error status: Please try again later [Error: Flavor's disk is too small for requested image.]. I am using ceph as the storage backend clustered over 3 nodes with 3 pools volumes vms images Someone will correct me if I'm wrong, but I believe we do not support reducing the size of a volume, as this would require an FS resize. Shrinking a filesystem will often leave you with a suboptimal on-disk layout. I believe this is a general openstack rule, and not just specific to RBD volumes. -- Jon __ 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] OPENSTACK with CEPH storage backend cant down size an instance
On 07/24/2015 12:47 PM, Clint Byrum wrote: Excerpts from James Galvin's message of 2015-07-24 09:08:36 -0700: Hi All I am having some trouble with down sizing an instance, I can resize the instance from say small flavour to medium flavour but when trying to resize the instance back from medium to small I get the following : Error: Failed to perform requested operation on instance jg-10, the instance has an error status: Please try again later [Error: Flavor's disk is too small for requested image.]. I am using ceph as the storage backend clustered over 3 nodes with 3 pools volumes vms images In addition to the note already made about reducing filesystem sizes, I just want to reaffirm that resize is really not the way you want to be using clouds, and IMO should be removed from Nova (but there's enough people who disagree with me that it will probably stay). Anyway, I suggest never using resize, and just deploying new servers, running tests, and then deleting the old ones. Having cloud with flexibility and space for this is why you have a cloud. As a person who runs a system with both long-lived pets and cattle that we grind in to food, I can attest that we do not use resize. It is a much longer downtime/risk operation than you want. __ 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
