[Fiware-lab-help] FIWARE UAT / sanity test for cloud friendly images

[Muryshkin, Peter]

Hi all,



from discussions with Lannion we have found that neither regions nor end customers can always be sure that an OS image is "cloudified". I assume this stands for specific software configuration.



The following description might be not completely technically correct because I do not know all the details, so please help to assess.



This situation lead to the following scenario known to me, however I beleive this will be not the only one:



-          I picked an Ubuntu OS from the image list, assuming that all images can be used, because it's cloud, you know like all vegetables can be expected tob e edible in a food store

-          We did a snapshot and relaunched it for a bigger instance

-          But the HDD did not scale because that the image might be "not cloudified"





Now towards the question how we can avoid such situations?



-          (1) Who is responsible to validate the cloudification and how?

-          (2) How to communicate that some images cannot support all cloud features?





To (1) I suppose, we might want to extend the Python-based UAT sanity tests<https://github.com/telefonicaid/fiware-health/tree/develop/fiware-region-sanity-tests> with specific testing of a minimal images set we want to be definitely cloudified.



Erwan has kindly provided the following ideas what should be tested:



I see 2 big points to check that can help about cloud feature in an image :

- Your instance boot log should appear in the console tab of the instance in the cloud portal

- Your instance root partition should resize automatically is snapshotted and re-launched with different flavor

but there are some other requirements that make an image cloud-friendly

here you can find some other clues : http://docs.openstack.org/image-guide/content/ch_openstack_images.html

but as I told before, the main feature is that the image should include the cloud-* packages (mainly cloud-init but there are other useful cloud packages)



My 2cts are that possible a sanity check test might include also a white box test: ssh the image under test, install and run some specific operations inside the image to validate its consistency, this goes e.g. to the question "is some package X installed or not".



To (2), a notice should be placed above the images list, like "please use images which have SDC abbreviations in their names, otherwise you might get in trouble"



What do you think?



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

Email: Peter.Muryshkin at iais.fraunhofer.de<mailto:Peter.Muryshkin at iais.fraunhofer.de>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-lab-help/attachments/20150319/33e4a9cf/attachment.html>