From Fedora Project Wiki
(→‎Base Image: new format with more detail)
Line 3: Line 3:
== Base Image ==
== Base Image ==


== ongoing maintenance of kickstart ===
== ongoing maintenance of kickstart ==
* What: The definition of the cloud image needs ongoing work
* What: The definition of the cloud image needs ongoing work
* Where: kickstart file is at https://fedorahosted.org/spin-kickstarts/
* Where: kickstart file is at https://fedorahosted.org/spin-kickstarts/
* Why: Because this is our base product
* Why: Because this is our base product
* When: As package sets change and new Fedora releases come out
* 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  
* Who: Someone in cloud working group in collaboration with rel-eng and spins sig
 
 


== port to anaconda/oz/imagefactory ==
== port to anaconda/oz/imagefactory ==

Revision as of 20:03, 28 January 2014

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:

Updates

  • policies
  • procedures
  • automated testing?
  • other qa?
  • mirroring?

Docker

Docker Host Image

  • create kickstart
  • selinux work
  • libvirt size
  • etcd?

Official Fedora Base Container

Library of Dockerfiles

Orchestration

  • mesos?

Big Data Image

  • define
  • create
  • test

Openshift Image

  • define
  • create
  • test


Planning

  • this document
  • Fedora.next changes list

Marketing =

  • figure out branding
  • produce content
  • work with web team


Documentation

  • write up what we're doing
  • write up any or all of the above