From Fedora Project Wiki
Line 61: Line 61:
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->


We will be adding to koji the the ability to run livemedia-creator in a chroot. we will replace the long legacy tools used to make LiveCD's and ARM disk images, as well as as the ability to deliver pxe2live for atomic.  livecd-creator and applaince-creator only support python2 and yum, they have not seen any significant development in years and are increasingly crufy. using livemedia-creator allows us to use dnf to create the media via anaconda and to ensure that the media is made the same way we make an installed system, reducing the code paths and differences in how a system look sbased on which tool made it.
We will be adding to koji the the ability to run livemedia-creator in a chroot. we will replace the long legacy tools used to make LiveCD's and ARM disk images, as well as as the ability to deliver pxe2live for atomic.  livecd-creator and applaince-creator only support python2 and yum, they have not seen any significant development in years and are increasingly crufy. using livemedia-creator allows us to use dnf to create the media via anaconda and to ensure that the media is made the same way we make an installed system, reducing the code paths and differences in how a system looks based on which tool made it.


== Benefit to Fedora ==
== Benefit to Fedora ==
In addition to enabling the creation of pxe2live we will be able to make LiveCD's and ARM disk images in a much better way.  
In addition to enabling the creation of pxe2live we will be able to make LiveCD's and ARM disk images in a much better way. Anaconda will be the tool used to do all Fedora installs. we will be removing appliance-tools and livecd-tools that have very crufty code bases and can not be ported to python3 due to thier reliance on yum.
   
   
    
    
Line 80: Line 80:
<!-- 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.  
<!-- 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.  
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.-->
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.-->
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: Relase blocking deliverables will be made with tooling changes <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
** [[Fedora_Program_Management/ReleaseBlocking/Fedora24|List of deliverables]]: All LiveCD's, ARM disk images and pxe2live will be made with tooling changes <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings -->
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings -->


* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Policies and guidelines: There is no changes here <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- 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. -->
<!-- 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. -->


Line 93: Line 93:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
We need to communicate this change to people doing remixes and rebuilds of Fedora media that will be created by livemedia-creator as they will need to make changes to thier kickstarts and processes to use the new tooling.


== How To Test ==
== How To Test ==
Line 111: Line 111:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
TODO:
Document how to run livemedia-creator to make the different types of media


== User Experience ==
== 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. -->
<!-- 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 -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
There should be no differences in user experience from the old tools


== Dependencies ==
== Dependencies ==
Line 122: Line 123:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
livemedia-creator exists today, we need to have the koji and pungi integration done.


== Contingency Plan ==
== Contingency Plan ==


<!-- 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.  -->
<!-- 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 mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Contingency mechanism: Continue to use livecd-tools and appliance-tools for making the media <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
<!-- 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 -->
* Contingency deadline: Alpha Change freeze <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
<!-- 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 release? Yes <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
* Blocks product? All <!-- Applicable for Changes that blocks specific product release/Fedora.next -->


== Documentation ==
== Documentation ==
Line 138: Line 139:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
http://lorax.readthedocs.org/en/latest/livemedia-creator.html
TODO: write fedora specifc docs, specifically on writing kickstarts


== Release Notes ==
== Release Notes ==

Revision as of 14:16, 5 November 2015


Livemedia Creator

Summary

livemedia-creator is a tool that is part of lorax, it has the ability to make livecd's, raw disk images, and to do pxe2live. We plan to use it to make pxe2live for Atomic, the LiveCD's and ARM disk images in fedora.

Owner

Current status

  • Targeted release: Fedora 24
  • Last updated: 2015-11-05
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

We will be adding to koji the the ability to run livemedia-creator in a chroot. we will replace the long legacy tools used to make LiveCD's and ARM disk images, as well as as the ability to deliver pxe2live for atomic. livecd-creator and applaince-creator only support python2 and yum, they have not seen any significant development in years and are increasingly crufy. using livemedia-creator allows us to use dnf to create the media via anaconda and to ensure that the media is made the same way we make an installed system, reducing the code paths and differences in how a system looks based on which tool made it.

Benefit to Fedora

In addition to enabling the creation of pxe2live we will be able to make LiveCD's and ARM disk images in a much better way. Anaconda will be the tool used to do all Fedora installs. we will be removing appliance-tools and livecd-tools that have very crufty code bases and can not be ported to python3 due to thier reliance on yum.


Scope

  • Proposal owners:
    • add livemedia-creator support to koji
    • add support to pungi to create media using livemedia-creator
  • Other developers: port spin-kickstarts to work with livemedia-creator
  • Release engineering: communicate the changes and work with spins owners to assist in porting
  • Policies and guidelines: There is no changes here
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

We need to communicate this change to people doing remixes and rebuilds of Fedora media that will be created by livemedia-creator as they will need to make changes to thier kickstarts and processes to use the new tooling.

How To Test

TODO: Document how to run livemedia-creator to make the different types of media

User Experience

There should be no differences in user experience from the old tools

Dependencies

livemedia-creator exists today, we need to have the koji and pungi integration done.

Contingency Plan

  • Contingency mechanism: Continue to use livecd-tools and appliance-tools for making the media
  • Contingency deadline: Alpha Change freeze
  • Blocks release? Yes
  • Blocks product? All

Documentation

http://lorax.readthedocs.org/en/latest/livemedia-creator.html TODO: write fedora specifc docs, specifically on writing kickstarts

Release Notes