From Fedora Project Wiki
< Cloud
Intro
This is a collaborative list of current and future work for the Fedora Cloud SIG. It's meant to describe what's needed or wanted, and what is being done. (It isn't an assignment sheet or list of demands, although it would be lovely if people are interested in taking responsibility for certain areas.)
Work Areas
Base Image
ongoing maintenance of kickstart
- What: The definition of the cloud image needs ongoing work
- Where: kickstart file is at https://fedorahosted.org/spin-kickstarts/
- Why: Because this is our base product
- When: As package sets change and new Fedora releases come out
- Who: Someone in cloud working group in collaboration with rel-eng and spins sig
port to anaconda/oz/imagefactory
- What: The current kickstart file is full of kludges for appliance-creator. Port to anaconda/imagefactory kludges
- Where: same as ongoing maintenance of kickstart
- Why: appliance-creator is being retired; anaconda-based installs are the way forward
- When: As soon as this is available in Koji. Need a new ImageFactory release, then patches into Koji for support, then a new Koji release, then Koji needs to be updated in Fedora production
- Who: Ian McLeod is working on ImageFactory; Jay Greguske on the Koji patches, Mike McLean is Koji maintainer, Dennis Gilmore in release engineering will do the Koji update. Need to work with them to get this in place, and then someone from cloud wg needs to do the updating.
automation in rel-eng
produce scratch builds on change
- What:
- Where:
- Why:
- When:
- Who:
upload to ec2 and ftp
- What:
- Where:
- Why:
- When:
- Who:
quality assurance
develop qa plan
- What:
- Where:
- Why:
- When:
- Who:
ongoing actual qa work
- What:
- Where:
- Why:
- When:
- Who:
Updates
Policies
- What: We talked about putting out updated images periodically (or aperiodically as needed). What are the rules?
- Where:
- Why:
- When:
- Who:
procedures
- What: We talked about putting out updated images periodically (or aperiodically as needed). How does it happen?
- Where:
- Why:
- When:
- Who:
automated testing
- What: How might updated images be automatically tested?
- Where:
- Why:
- When:
- Who:
other qa?
- What: What other QA do we want to do? How do we want to do it?
- Where:
- Why:
- When: initial planning, ongoing as updates happen
- Who:
mirroring updated images
- What: Do we want the updates to go out to the Fedora mirror network?
- Where:
- Why:
- When:
- Who: releng, mirror admins
legal
- What: Needs for keeping track of source for GPL compliance
- Where:
- Why:
- When:
- Who: releng, legal, and us
Docker
Docker Host Image
create kickstart
- What:
- Where:
- Why:
- When:
- Who:
selinux work
- What:
- Where:
- Why:
- When:
- Who:
libvirt size
- What:
- Where:
- Why:
- When:
- Who:
etcd?
- What:
- Where:
- Why:
- When:
- Who:
mesos orchestration?
- What:
- Where:
- Why:
- When:
- Who:
Official Fedora Base Container
initial kickstart
- What:
- Where:
- Why:
- When:
- Who:
ongoing maintenance of kickstart
- What:
- Where:
- Why:
- When:
- Who:
Library of Dockerfiles
- What:
- Where:
- Why:
- When:
- Who:
Orchestration
- What:
- Where:
- Why:
- When:
- Who:
Big Data Image
define
- What:
- Where:
- Why:
- When:
- Who:
create
- What:
- Where:
- Why:
- When:
- Who:
test
- What:
- Where:
- Why:
- When:
- Who:
maintain
- What:
- Where:
- Why:
- When:
- Who:
Openshift Image
define
- What:
- Where:
- Why:
- When:
- Who:
create
- What:
- Where:
- Why:
- When:
- Who:
test
- What:
- Where:
- Why:
- When:
- Who:
maintain
- What:
- Where:
- Why:
- When:
- Who:
Random Bits We Could Use
Cloud-init improvements
- What:
- Where:
- Why:
- When:
- Who:
Notification of pending security updates on login
- What: A system to display a count (or list?) of updates waiting to be applied
- Where: New code needs to be written. https://bugzilla.redhat.com/show_bug.cgi?id=995537 could help.
- Why: Helpful to users. Side-effect: we can count checkins.
- When: nice by F21 release.
- Who:
Planning
this document
- What:
- Where:
- Why:
- When:
- Who:
More / better statistics
- What:
- Where:
- Why:
- When:
- Who:
Ongoing user surveys
- What:
- Where:
- Why:
- When:
- Who:
Fedora.next changes list
- What: see "second deliverable" at https://fedoraproject.org/wiki/Fedora.next/boardproposal#Product_Working_Groups
- Where: Cloud_Changelist
- Why:
- When: REAL SOON NOW
- Who:
Marketing
figure out branding
- What:
- Where:
- Why:
- When:
- Who:
produce content
- What:
- Where:
- Why:
- When:
- Who:
promote!
- What:
- Where:
- Why:
- When:
- Who:
work with web team
- What:
- Where:
- Why:
- When:
- Who:
Documentation
write up what we're doing
- What:
- Where:
- Why:
- When:
- Who:
write up any or all of the above
- What:
- Where:
- Why:
- When:
- Who:
Fedora Cloud Guide
- What: Fedora Cloud Guide
- Where:
- Why: Book form documentation to explain what the Cloud is, how Fedora fits in, and how to use Fedora and provided tools in the Cloud.
- When: Anytime
- Who: Anyone!
How to Contribute to the Cloud Guide
Any form of participation is welcome. You can ask for a particular tool or process to be covered, suggest improvements, critique, point out flaws or outdated content, or write content directly.
Fedora Guides are written in docbook and published using Publican. There is a slight learning curve, but don't let that dissuade you! Even if you don't want to hack on the guide directly, your feedback and guidance is valuable. Your expertise can help writers with less cloud knowledge to put together a good guide.
Public Cloud Providers
Amazon EC2
Amazon Marketplace
- What:
- Where:
- Why:
- When:
- Who:
Ongoing EC2
- What:
- Where:
- Why:
- When:
- Who:
Google Compute Image
- What:
- Where:
- Why:
- When:
- Who:
HP Cloud
- What:
- Where:
- Why:
- When:
- Who:
Rackspace
- What:
- Where:
- Why:
- When:
- Who:
Digital Ocean
- What:
- Where:
- Why:
- When:
- Who: