Hi Peter, Please find hereunder the explanation that Erwan sent you about this issue. My conclusion is that the the initial image used for the instance deployment was not cloudified, and thus, partitions can’t be modified. I think the best solution would be to use the TID certified Images that are available on the catalogue. You should find Ubuntu and CentOS. Hi Peter, I looked at your " iais-jenkins-2" instance associated with floating IP 193.52.45.135. When looking at this instance properties, It appears that the image used to launch this instance is called "iais-jenkins2". So I looked at this image properties, I see that this image is also in fact a snapshot. Looking one more step deeper, I see that the base image used to build this " iais-jenkins2" is " testiais-ubuntu_snap". I thought that this was also a snapshot (as indicated in its name), but image properties show that it not so. To sum up this, I can't find the original image used to build the not-resizing instance. Without this information, it is hard for me to go further in debug. But here are some information about snapshot and disk/partition size. Maybe you are not aware of the following details, and it will explain this HDD size behavior : - Some image are optimized for being used on cloud environment. Looking at Ubuntu images they often include the string "cloud" in their name. In Lannion glance list, you can for example find "ubuntucloud-1410". I don't know if Ubuntu OSes match your requirements for this kind of use, but they best handle disk/partition resizing than images not optimized for cloud . I did some tests and using this kind of images allows you to snapshot it and relaunch the image snapshot with the flavor of your choice without problem. - The Following images : Ubuntu Server 14.04.1 (x64) / Ubuntu12.04-server-x86_64 located in our glance are not optimized for cloud, they do not handle disk resizing with snapshots. You have to configure them for cloud with specific packages so they can handle disk resizing after that. Then snapshot them and you can used them as image handling that problem. - In fact, your instance HAS a 80 Gb HDD ! Partitioning is just not handled. So you have a default 10Go drive, and unformatted 70+ Gb. You can format it and use it if you want. But notice this is just ephemeral storage, and it won't certainly be handled in case of snapshot. - Best Practice if you want a "template snapshot" is to create an low-sized HDD instance (tiny/small), and launch your new instance with bigger HDD flavor from this snapshot. This works and handles HDD size without problem. But the reverse is not true : For example, if you create a 80Gb template snapshot, you won't be able to run instance with less than 80Gb HDD from this snapshot, the instance won't launch and will fail to start. - If you need to permanently store some data, I recommend you to use a volume, and map it to the chosen instances. Hope this helps. Sources : - https://wiki.openstack.org/wiki/VariableSizeRootDisk - http://docs.openstack.org/image-guide/content/ch_openstack_images.html Best Regards, Erwan Please do not hesitate to contact erwan or engineering at imaginlab.fr <mailto:engineering at imaginlab.fr> in order to find out the best solution Best regards Sergio De : Federico Michele Facca [mailto:federico.facca at create-net.org] Envoyé : mercredi 18 mars 2015 16:34 À : Muryshkin, Peter Cc : fiware-lab-help at lists.fi-ware.org; thierry.nagellen at orange.com; Stefano De Panfilis; Winkler, Thomas; Laura Kohler; Sergio MORANT; Kißels, Timm; Pieter VAN DER LINDEN Objet : Re: JIRA issue does not exist? Please find to help missing FIWARE JIRA ticket LAN-8 (disk space problem on image bakery) hi peter, few weeks ago (i don't recall the date) the database of jira get corrupted, so telefonica restored the database to the night snapshot, this may have affected a number of tickets created in that time span On Wed, Mar 18, 2015 at 4:26 PM, Muryshkin, Peter <Peter.Muryshkin at iais.fraunhofer.de <mailto:Peter.Muryshkin at iais.fraunhofer.de> > wrote: Hi all, on 24.02.2015 I sent a request regarding virtual hardware problem which was tagged as https://jira.fiware.org/browse/LAN-8 Same day I got response from Lannion that they would work on the issue. Since then I never heard of it, and problem now has grown really disturbing because it seems the team has not addredded the issue. Unfortunately I cannot access the ticket on FIWARE JIRA, the software says „issue does not exist“. How comes? When can the hardware problem be fixed (we need more disk space for ? Kind regards / viele Grüße & Servus Peter Muryshkin, M. Sc. Skype ID: peter_iais LinkedIn: http://de.linkedin.com/in/muryshkin ---------------------------------------------------------------------------------- NetMedia / B3-342 Fraunhofer IAIS Schloss Birlinghoven 1 53754 St. Augustin, Germany T: +49 2241 14 3413 <tel:%2B49%202241%2014%203413> Email: <mailto:Peter.Muryshkin at iais.fraunhofer.de> Peter.Muryshkin at iais.fraunhofer.de -- -- Future Internet is closer than you think! http://www.fiware.org Official Mirantis partner for OpenStack Training https://www.create-net.org/community/openstack-training -- Dr. Federico M. Facca CREATE-NET Via alla Cascata 56/D 38123 Povo Trento (Italy) P +39 0461 312471 M +39 334 6049758 E federico.facca at create-net.org <mailto:federico.facca at create-net.org> T @chicco785 W www.create-net.org <http://www.create-net.org> -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-lab-help/attachments/20150318/f4c09041/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 15376 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-lab-help/attachments/20150318/f4c09041/attachment.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5552 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-lab-help/attachments/20150318/f4c09041/attachment.bin>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy