Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "VT-CloudCaps:Questionnaire"

From EGIWiki
Jump to navigation Jump to search
(Some rephrasing (incomplete))
Line 1: Line 1:
This should evolve to questionnaire which should map state of user-groups using FedCloud and working with our mini-project.
This should evolve to questionnaire which should map state of user-groups using FedCloud and working with our mini-project. We have to create questionnaire, fill it with already known information and only then approach users.  
We have to create questionnaire, fill it with already known information and only then approach users.


Feel free to edit, just first ideas!
Feel free to edit, just first ideas!  


== Image preparation ==
== Image preparation and management ==


How image was created, is managed, should we help with preparation?
How has the image been created, how is it managed, should we help with preparation?  


* how many images is used by this group (one, several with different functions)?
*How many images are used by your group (one, several with different functions)?  
* how image was created? From scratch, from basic OS image, using full OS installation, copy of desktop, copy of image prepared in vmware/virtualbox on desktop, group already provides one ...
*How did you create the image? From scratch, from basic OS image, using full OS installation, copy of desktop, copy of image prepared in vmware/virtualbox on desktop, group already provides one ...  
* is it one partition with system, more partitions/whole disk (with dedicated place for data, empty space for other data, packages, user data)
*Is it one partition with system, multiple partitions/whole disk (with dedicated place for data, empty space for other data, packages, user data)  
* is everything required for computation installed in image? Would it be interesting to install parts during VM start (contextualization, always latest version of packages)? Is it installing packages/software during/after boot? CVMFS?
*Is everything required for computation already installed in the image? Would it be interesting to install parts during VM start (contextualization, always latest version of packages)? Is it installing packages/software during/after boot? CVMFS?  
* image prepared to run with KVM/Xen, in which format (OVF)?
*Image prepared to run with KVM/Xen, in which format (OVF)?  
* kernel version (doesn't matter ... must be exactly the same)?
*Do you rely on a specific Linux Kernel version?  
* how new versions of image should be installed? No need, rarely, often via vmcatcher, other way. What about security updates?
*How should new versions of the image be distributed and installed? No need, rarely, often via vmcatcher, other way. How do you intend to deal with security updates?  
* Is image signed? endorsed by some group? verified by some RP?
*Is image signed? Endorsed by some group? Verified by some RP?  
* HW requirements (special HW, small/big template)
*What kind of hardware requirements (resource demands do  your image and application have? RAM, Disk, Processor, Cores.
* network requirements (public IP, open ports, firewall, running in VPN, expected bandwidth)
*What are the network requirements of your application? Do you require access to the running instance from external? Which ports do you require to be open? Do you expect arbitrary access from within the instance to the outside world? What are your bandwidth expectations?


== Workload management ==
== Workload management ==


How actual work is submitted to running VM? Should we care, help?
How do you submit the actual work to the running instances? Should we care, help?  


* some pilot framework? BOINC? Other implementation of call-home?  
*Do you use a form of pilot framework? BOINC? Other implementation of call-home?  
* Is VM started by some wokload system/application, which immediately submits "jobs"?  
*Is VM started by some workload system/application, which immediately submits "jobs"?  
* Who is doing scheduling? VMs running across several providers?  
*Who is doing scheduling? VMs running across several providers?  
* Is autoscaling usable/needed (different requirements on resources during VM lifetime)? Or is it easier to spawn new VMs?  
*Do you do automatic scaling of your framework? Do you require vertical scaling, e.g. sizing up instances, or horizontal scaling, i.e. adding more instances as needed? <br>
* How long should VM run (long computation, smaller jobs submited inside VM,...)
*How long should a VM run (long computation, smaller jobs submited inside VM,...)?
* Can be VM preempted, migrated?
*Can the VM be preempted or migrated?


== AAI and contextualization ==
== AAI and contextualization ==


How access to running VM is implemented (should we help, explain what's possible, push contextualization?)
How do you intend access to running VMs (should we help, explain what's possible, push contextualization?)  


* some support for user contextualization? Already/would be nice/not needed.
*Is there support for user contextualization? Already available/would be nice/not needed.  
* system with pre-installed ssh access, know root password, ssh public key, group accessible public key, other way to login, remote desktop, no need for root access, need for user contextualization (storing ssh key in authorized_keys)
*Does your system come with pre-installed ssh access, a fixed root password, ssh public key, group accessible public key, other way to login, remote desktop, no need for root access, need for user contextualization (storing ssh key in authorized_keys)  
* management of running VMs - all started by one representative of VO, image/VM shared between group of users, VM just for one user  
*Management of running VMs - all started by one representative of VO, image/VM shared between group of users, VM just for one user  
* does VM contains some credentials to be able to access remote services/data?
*Does VM contain some credentials to be able to access remote services/data? Could this be injected via contextualization?


== Data, big data ==
== Data, big data ==


In some cases, big data are analyzed/produced by cloud applications. There is usually place for improvements, help, new services...
In some cases, big data are analyzed/produced by cloud applications. There is usually place for improvements, help, new services...  


* is application working with some big data? If yes, which type of access is needed (big shared network storage, virtual disk accessed by some VMs, object storage)?  
*Does your application work with large amounts of data? If yes, which type of access is needed (big shared network storage, virtual disk accessed by some VMs, object storage)? Do you only read or also write this category of data?  
* all data used by all VMs? Every VM/job is using small subset? Other patterns?
*Is all of the data used by all VMs? Every VM/job is using small subset? Other patterns?  
* requirements for Hadoop like environment?
*Do you require a Hadoop like environment?  
* already using some object storage like S3, CDMI? Data service from EGI (gridftp, SE, SRM)?  
*Are you already using some object storage like S3, CDMI? Data service from EGI (gridftp, SE, SRM)?  
* large data downloaded/produced during VM lifetime?  
*Large data downloaded/produced during VM lifetime?  
* need for higher-level control of data access?
*Need for higher-level control of data access?


== What else should we know? ==
== What else should we know? ==
* need for other services? Like messaging system, integration with standard EGI services (data?), SQL database?
 
*Is there a need for other services? Like messaging system, integration with standard EGI services (data?), SQL database?

Revision as of 15:17, 23 April 2013

This should evolve to questionnaire which should map state of user-groups using FedCloud and working with our mini-project. We have to create questionnaire, fill it with already known information and only then approach users.

Feel free to edit, just first ideas!

Image preparation and management

How has the image been created, how is it managed, should we help with preparation?

  • How many images are used by your group (one, several with different functions)?
  • How did you create the image? From scratch, from basic OS image, using full OS installation, copy of desktop, copy of image prepared in vmware/virtualbox on desktop, group already provides one ...
  • Is it one partition with system, multiple partitions/whole disk (with dedicated place for data, empty space for other data, packages, user data)
  • Is everything required for computation already installed in the image? Would it be interesting to install parts during VM start (contextualization, always latest version of packages)? Is it installing packages/software during/after boot? CVMFS?
  • Image prepared to run with KVM/Xen, in which format (OVF)?
  • Do you rely on a specific Linux Kernel version?
  • How should new versions of the image be distributed and installed? No need, rarely, often via vmcatcher, other way. How do you intend to deal with security updates?
  • Is image signed? Endorsed by some group? Verified by some RP?
  • What kind of hardware requirements (resource demands do  your image and application have? RAM, Disk, Processor, Cores.
  • What are the network requirements of your application? Do you require access to the running instance from external? Which ports do you require to be open? Do you expect arbitrary access from within the instance to the outside world? What are your bandwidth expectations?

Workload management

How do you submit the actual work to the running instances? Should we care, help?

  • Do you use a form of pilot framework? BOINC? Other implementation of call-home?
  • Is VM started by some workload system/application, which immediately submits "jobs"?
  • Who is doing scheduling? VMs running across several providers?
  • Do you do automatic scaling of your framework? Do you require vertical scaling, e.g. sizing up instances, or horizontal scaling, i.e. adding more instances as needed?
  • How long should a VM run (long computation, smaller jobs submited inside VM,...)?
  • Can the VM be preempted or migrated?

AAI and contextualization

How do you intend access to running VMs (should we help, explain what's possible, push contextualization?)

  • Is there support for user contextualization? Already available/would be nice/not needed.
  • Does your system come with pre-installed ssh access, a fixed root password, ssh public key, group accessible public key, other way to login, remote desktop, no need for root access, need for user contextualization (storing ssh key in authorized_keys)
  • Management of running VMs - all started by one representative of VO, image/VM shared between group of users, VM just for one user
  • Does VM contain some credentials to be able to access remote services/data? Could this be injected via contextualization?

Data, big data

In some cases, big data are analyzed/produced by cloud applications. There is usually place for improvements, help, new services...

  • Does your application work with large amounts of data? If yes, which type of access is needed (big shared network storage, virtual disk accessed by some VMs, object storage)? Do you only read or also write this category of data?
  • Is all of the data used by all VMs? Every VM/job is using small subset? Other patterns?
  • Do you require a Hadoop like environment?
  • Are you already using some object storage like S3, CDMI? Data service from EGI (gridftp, SE, SRM)?
  • Large data downloaded/produced during VM lifetime?
  • Need for higher-level control of data access?

What else should we know?

  • Is there a need for other services? Like messaging system, integration with standard EGI services (data?), SQL database?