Cloud/Cloud ToDo

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.)

Tickets!

This page was previously a gigantic list of items, but that got unwieldy fast. Instead, we have a Trac instance with tickets. Take a look at

• All active tickets
• Easy items for you to jump right in with (don't be shy!)
• Items tagged for the weekly Cloud SIG meeting

Ongoing Work

These are things which are basically continuous effort and might not have open tickets.

Cloud Base Image

General Continuous Updates and Fixes

• 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: mattdm from cloud working group in collaboration with rel-eng and spins sig

QA and Testing

Ongoing QA Documentation Work

• What: Keep above documents up to date, extend and add new documents where necessary.
• Where: Fedora Wiki
• Why: As requirements, processes or tools might change, documents need to change too. Also, some documents need to be copied (and maybe slightly changed) before every round of testing.
• When: Between releasing a new release and the next release's first alpha release candidate's due date.
• Who: Someone in cloud working group or QA.

Ongoing QA Testing Work

• What: Perform the actual testing according to the test plans and test cases from above. For every single release and re-release.
• Where: Fedora Wiki, IRC (#fedora-qa and #fedora-cloud), Bugzilla, Mailing Lists (Cloud SIG and QA), etc.
• Why: Because bugs happen, because no-one and nothing is perfect. Because we want our users to have a as flawless experience as possible. And because the automated testing is not yet implemented (and some things might not be fully automatable).
• When: From the first alpha release candidate until the final release of each and every release, at least until tests are fully automated.
• Who: As many people with as many different environments as possible. Primarily cloud working group and possibly QA people, probably.

Documentation

Improve Cloud SIG wiki

• What: general improvements to wiki page for both SIG and WG
• Where: https://fedoraproject.org/wiki/Cloud_SIG
• Why: keep pace with recent developments, link all the stuff together, make it easy to dive in
• When:
• Who:

Vague Future

And here are ideas for things we want to do, but haven't really planned for yet.

OLD LIST -- MOVE ITEMS BELOW TO TICKETS AND DELETE

Docker

Docker Host Image

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:

More things we can do to make the base better

• What: good ideas here: https://github.com/phusion/baseimage-docker and elsewhere
• 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:

Planning

this document

• What:
• Where:
• Why:
• When:
• Who:

technical specifications

• What: like https://fedoraproject.org/wiki/Workstation/Technical_Specification but for our stuff
• Where:
• Why:
• When:
• Who:

More / better statistics

• What:
• Where:
• Why:
• When:
• Who:

Ongoing user surveys

• What:
• Where:
• Why:
• When:
• Who:

Needs for Base WG

• What: like the Changelist, but specifically, what we'd like / need from the base
• Where:
• Why:
• When:
• Who:

Needs for Env & Stacks

• What: like the Changelist, but specifically, what we'd like / need from Ring 2
• Where:
• Why:
• When:
• 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:
  • Git: https://git.fedorahosted.org/cgit/docs/cloud-guide.git
  • Bugzilla: https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20Documentation&component=cloud-guide
  • Docs Mailing List: https://admin.fedoraproject.org/mailman/listinfo/docs
• 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.

Collaboration

Working with CentOS

Gathering downstream needs

• What: Future version of CentOS will be shaped by what we are doing; let's get feedback!
• Where:
• Why:
• When:
• Who:

Cooperating on infrastructure

• What: Avoid duplication of effort in tools, infrastructure, etc.
• Where:
• Why:
• When:
• Who:

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: