Revision as of 19:28, 7 April 2014

Comments and Explanations
MOSTLY EMPTY DRAFT WAITING FOR ATTENTION

Move to ImageFactory For Cloud Image Creation

Summary

Create images using Anaconda in Koji rather than appliance-creator. Allows non-scratch builds with fedmsg integration for upload service, and also could produce official Docker images.

Owner

Name: Ian McLeod
Email: imcleod@redhat.com
Release notes owner:

Current status

Targeted release: Fedora 21
Last updated: 2014-04-07
Tracker bug: <will be assigned by the Wrangler>

Detailed Description

Jay Greguske recently added a feature to koji that allows it to create full system disk images using Image Factory. These images can be output both as raw and qcow2 disk images, as well as OVA/OVF bundles compatible with OVirt, VMWare and RHEV-M. They are created by running Anaconda kickstart installs in virt containers and then packaging/encapsulating the results.

Benefit to Fedora

By using Anaconda itself to generate the image we eliminate the gap between the tooling used to generate cloud images (currently appliance-creator) and the tooling used to generate bare metal and "normal" virt images (Anaconda). Using Anaconda running inside of virt containers also eliminates any dependency on kernel-level features of the build system hosts. (e.g. - If we want to build a cloud image using a newly introduce or newly updated filesystem, we can do that.) Finally, using Anaconda means that we are coupled to a tool that is already essential to any given release and can be expected to work.

Scope

Proposal owners: The Image Factory support in Fedora koji has already landed and images are already being built using this technique. The work for F21 should mainly involve making sure that the existing cloud kickstart files work when run directly by Anaconda and making any chances needed to ensure that they do.

Other developers: N/A (not a System Wide Change)

Release engineering: N/A (not a System Wide Change)

Policies and guidelines: N/A (not a System Wide Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

Build images inside of koji using the newly added Image Factory support. Deploy these images on the target cloud/virt environments and test for basic functionality and parity with existing appliance-creator based images.

User Experience

N/A (not a System Wide Change)

Dependencies

None that we are aware of. If Anaconda can be used to generate a working virtual machine image, the Image Factory support in koji can be used to create one.

Contingency Plan

Contingency mechanism: N/A (not a System Wide Change)
Contingency deadline: N/A (not a System Wide Change)
Blocks release? N/A (not a System Wide Change)

Documentation

TODO: Link to Jay Greguske HOWTO documentation

Release Notes

@@ Line 13: / Line 13: @@
 This should link to your home wiki page so we know who you are.
 -->
-* Name: [[User:FASAcountName| Your Name]]
+* Name: [[User:imcleod| Ian McLeod]]
 <!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
-* Email: <your email address so we can contact you, invite you to meetings, etc.>
+* Email: imcleod@redhat.com
 * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
 <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
@@ Line 26: / Line 26: @@
 == Current status ==
-* Targeted release: [[Releases/<number> | Fedora <number> ]]
+* Targeted release: [[Releases/21 | Fedora 21 ]]
-* Last updated: (DATE)
+* Last updated: 2014-04-07
 <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page
 Bugzilla states meaning as usual:
@@ Line 39: / Line 39: @@
 == Detailed Description ==
-<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
+Jay Greguske recently added a feature to koji that allows it to create full system disk images using Image Factory.  These images can be output both as raw and qcow2 disk images, as well as OVA/OVF bundles compatible with OVirt, VMWare and RHEV-M.  They are created by running Anaconda kickstart installs in virt containers and then packaging/encapsulating the results.
 == Benefit to Fedora ==
-<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
+By using Anaconda itself to generate the image we eliminate the gap between the tooling used to generate cloud images (currently appliance-creator) and the tooling used to generate bare metal and "normal" virt images (Anaconda).  Using Anaconda running inside of virt containers also eliminates any dependency on kernel-level features of the build system hosts.  (e.g. - If we want to build a cloud image using a newly introduce or newly updated filesystem, we can do that.)  Finally, using Anaconda means that we are coupled to a tool that is already essential to any given release and can be expected to work.
 == Scope ==
-<!-- What work do the developers have to accomplish to complete the change in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
-* Proposal owners:
+* Proposal owners: The Image Factory support in Fedora koji has already landed and images are already being built using this technique.  The work for F21 should mainly involve making sure that the existing cloud kickstart files work when run directly by Anaconda and making any chances needed to ensure that they do.
-<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
-* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Other developers: N/A (not a System Wide Change)
-<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
-* Release engineering: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Release engineering: N/A (not a System Wide Change)
-<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  If a rel-eng ticket exists, add a link here.  -->
-* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Policies and guidelines: N/A (not a System Wide Change)
-<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->
 == Upgrade/compatibility impact ==
-<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 N/A (not a System Wide Change)
 == How To Test ==
-<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
-Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
+Build images inside of koji using the newly added Image Factory support.  Deploy these images on the target cloud/virt environments and test for basic functionality and parity with existing appliance-creator based images.
-A good "how to test" should answer these four questions:
-. What special hardware / data / etc. is needed (if any)?
-. How do I prepare my system to test this change? What packages
-need to be installed, config files edited, etc.?
-. What specific actions do I perform to check that the change is
-working like it's supposed to?
-. What are the expected results of those actions?
--->
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
 == User Experience ==
-<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 N/A (not a System Wide Change)
 == Dependencies ==
-<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
+None that we are aware of.  If Anaconda can be used to generate a working virtual machine image, the Image Factory support in koji can be used to create one.
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+== Contingency Plan ==
-N/A (not a System Wide Change)
-== Contingency Plan ==
+* Contingency mechanism: N/A (not a System Wide Change)
-<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
+* Contingency deadline: N/A (not a System Wide Change)
-* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Blocks release? N/A (not a System Wide Change)
-<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
-* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
-* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
 == Documentation ==
-<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
+TODO: Link to Jay Greguske HOWTO documentation
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
 == Release Notes ==

Search

Changes/Move to ImageFactory For Cloud Image Creation: Difference between revisions