From Fedora Project Wiki
m (Add links)
m (Minor update)
Line 4: Line 4:
This page will outline criteria for success for a Fedora AMI release
This page will outline criteria for success for a Fedora AMI release


A <span style="color:green; font-weight:bold;">good</span> AMI '''must'''...
= Release Criteria =
 
In addition to the existing [[Fedora Release Criteria]], the following criteria apply to EC2 Fedora images.  A <span style="color:green; font-weight:bold;">good</span> AMI '''must'''...
# allow non-root user login
# allow non-root user login
# have SELinux enabled and ''enforcing'' by default
# have SELinux enabled and ''enforcing'' by default
# not contain any package dependency problems
# not contain any package dependency problems
# not include any packages built outside of Fedora infrastructure
# not include any packages built outside of Fedora infrastructure
= How to Test =


To ''create'' an EC2 image, one needs...
To ''create'' an EC2 image, one needs...
# an amazon account
# an amazon account
# the {{package|python-boto}} libraries installed
# the {{package|python-boto}} libraries installed

Revision as of 21:46, 3 March 2011

This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.

This page will outline criteria for success for a Fedora AMI release

Release Criteria

In addition to the existing Fedora Release Criteria, the following criteria apply to EC2 Fedora images. A good AMI must...

  1. allow non-root user login
  2. have SELinux enabled and enforcing by default
  3. not contain any package dependency problems
  4. not include any packages built outside of Fedora infrastructure

How to Test

To create an EC2 image, one needs...

  1. an amazon account
  2. the python-boto libraries installed
  3. a python script to tell Amazon to build an instance
  4. the ability to SSH into a machine to run tests, etc.

Additional Reading