From Fedora Project Wiki

Line 26: Line 26:
** If you're planning on coming, please get signed up
** If you're planning on coming, please get signed up
** Please start adding sessions to the FUDCon wiki page, and we can go through them as we get closer and discuss on-list.
** Please start adding sessions to the FUDCon wiki page, and we can go through them as we get closer and discuss on-list.
* F15 Schedule for Feature Submission: [[Schedule]]
* F15 Schedule for Feature Submission: [[Schedule]] - who is submitting?
* Meeting time change? http://lists.fedoraproject.org/pipermail/cloud/2010-October/000320.html
* Looking for folks to help with Deltacloud packaging / reviewing / sponsorship: [[http://deltacloud.org/page/Packaging_list#Things_that_still_need_packaging_for_fedora List]]
* Looking for folks to help with Deltacloud packaging / reviewing / sponsorship: [[http://deltacloud.org/page/Packaging_list#Things_that_still_need_packaging_for_fedora List]]
* ''Add your agenda item here.''
* ''Add your agenda item here.''

Revision as of 18:28, 4 November 2010

Purpose

The Fedora Cloud SIG works to make Fedora successful on all major cloud platforms, public and private.

Looking for Fedora EC2 information?

A list of currently supported AMIs is maintained here

Mailing List

IRC

Fedora Cloud folks hang out on irc.freenode.net at #fedora-cloud.

Meetings

Meetings are held weekly on Thursdays, 2100 UTC on #fedora-meeting (currently 1700 Eastern US daylight time (UTC-4)).

Upcoming meeting agenda

Next meeting: 2010/11/04 - 2100 UTC (5pm Eastern), in #fedora-meeting.

Past Meetings

To-Do List

  • Testing:
    • Can start working on this now with local xen testing - we can test and tune the ks file on rhel 5.3 or newer hosts.
    • Testing without ec2 requires a xen host - once you have a xen host, you can create an image with appliance-tools using the kickstart file from huff.
    • Need to get location of file from huff. Please link it here!
    • Boot image, make sure it works, look for critical packages, report back if things are needed or something doesn't work (or does work).
    • Need to identify list of critical packages
    • Need to identify place for people to list their test results - GOOD OR BAD
  • Documentation
    • Start by documenting how to boot an image from EC2 - ami-988b60f1 is an example, document the use of it, and we change the names to the official release when it is ready.
    • amazon documentation should be linked off the ec2 login page - can be a good reference point. (rbergeron, 21:17:43)
    • need separate docs for publishing to ec2, and booting an image from ec2. But booting and using is the more important, and one that can be worked on now (in fact testers can use it for testing instructions)

Current Projects