From Fedora Project Wiki
m (Content moved into Features/Gnome3) |
m (Add questions section) |
||
(4 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
{{header|qa}} | |||
{{draft}} | |||
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 <span style="color:green; font-weight:bold;">good</span> AMI '''must'''... | |||
# allow non-root user login | |||
# have SELinux enabled and ''enforcing'' by default | |||
# not contain any package dependency problems | |||
# not include any packages built outside of Fedora infrastructure | |||
= How to Test = | |||
To ''create'' an EC2 image, one needs... | |||
# an amazon account | |||
# the {{package|python-boto}} libraries installed | |||
# a python script to tell Amazon to build an instance | |||
# the ability to SSH into a machine to run tests, etc. | |||
= Open Questions = | |||
# Who is responsible for creating and building EC2 images? | |||
#: | |||
= Additional Reading = | |||
* [[Publishing_image_to_EC2]] | |||
* [[Cloud_SIG]] | |||
* [[Cloud_SIG/EC2_Images]] |
Latest revision as of 17:19, 9 March 2011
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...
- allow non-root user login
- have SELinux enabled and enforcing by default
- not contain any package dependency problems
- not include any packages built outside of Fedora infrastructure
How to Test
To create an EC2 image, one needs...
- an amazon account
- the
python-boto
libraries installed - a python script to tell Amazon to build an instance
- the ability to SSH into a machine to run tests, etc.
Open Questions
- Who is responsible for creating and building EC2 images?