Difference between revisions of "Virtual Machine Image Endorsement"
Line 74: | Line 74: | ||
[https://wiki.appdb.egi.eu/main:guides:guide_for_managing_virtual_appliance_versions_using_the_portal Managing appliance] | [https://wiki.appdb.egi.eu/main:guides:guide_for_managing_virtual_appliance_versions_using_the_portal Managing appliance] | ||
= Continuous improvement = | = Continuous improvement = | ||
It is important to understand how much each image is used. The "popularity" of a given image can be most downloaded (AppDB) | It is important to understand how much each image is used. The "popularity" of a given image can be: | ||
*most downloaded (AppDB) | |||
*most used (accounting) | |||
= Procedures for EGI images = | = Procedures for EGI images = |
Revision as of 07:07, 10 June 2015
Description
Goal
Set up a process assuring that a Virtual Machine Image (VMI)/ Virtual Appliance (VA) published in AppDB is well-configured, secure and up-to-date.
Members
- Enol Fernandez [EF]
- Vincenzo Spinoso [VS]
Contacts
SSO group available: vm-image-endorsement@mailman.egi.eu
Image types
Type | Description | Managed by |
---|---|---|
EGI | General purpose images. Based on largely used Oses | EGI |
VO-specific | VO specific images, available to a specific VO and customized for specific purposes | VO-expert |
Activities and workflow
Activity | Description |
---|---|
A1. Creation | Set up an image ready to be used by a Resource Provider |
A2. Configuration | Configuration assures that packages are up to date and no wrong default configurations are left for any applications/services |
A3. Hardening | Security is provided by applying CSIRT guidelines for the VMI Endorsement |
A4. Publishing | Make image available on AppDB with proper tags, metadata, links |
Documents and Policies
Policies are defined by the SPG group and are published in the https://wiki.egi.eu/wiki/SPG:Documents
It is particularly relevant the Security Policy for the Endorsement and Operation of Virtual Machine Images and a draft of a Virtualisation Policy.
Hardening guidelines
ACTION NEEDED : link to external wiki containing hardening guidelines from CSIRT
Publishing
When publishing, each image will bring its onw tags and metadata in AppDB (TBD).
Registering appliance Managing appliance
Continuous improvement
It is important to understand how much each image is used. The "popularity" of a given image can be:
- most downloaded (AppDB)
- most used (accounting)
Procedures for EGI images
Activity | Initial activity | Ongoing activity |
---|---|---|
A1. Creation | Set up the procedure for a given image | Use the procedure to create/update the image according to a given policy (on security issue, on request, every X days… ) |
A2. Configuration | Create VMI configuration procedure for a given image | Apply VMI configuration procedure to a given image |
A3. Hardening | Create VMI hardening procedure for a given image based on guidelines | Apply VMI hardening procedure to a given image |
A4. Publishing | Publish the image on AppDB | Publish the image on AppDB |
Ubuntu
Creation
Configuration
Hardening
Publishing
CentOS7
Creation
Configuration
Hardening
Publishing
Procedures for VO images
The procedure is similar as to EGI images, but a VO expert (endorser) is fully responsible for the process of the endorsement of a specific VM. For the fedcloud.egi.eu VO the VO expert will get special help from EGI experts.