The Productization Pipeline
and the so-called "Factory 2.0"
Presented at DevConf 2017 by @ralphbean.
Slides available at http://threebean.org/presentations/factory2-devconf17/
The Eternal September
A fun tidbit of Hacker Lore:
Also called the September that never ended, the Eternal September is Usenet slang for a period beginning in September 1993, the month that Internet service provider America Online began offering Usenet access to its many users, overwhelming the existing culture for online forums.
The Second Eternal September
and the rise of github
This is fine.
Consequent Changes
To application development and deployment:
pip freeze > requirements.txt # ship it!
In my opinion, Modularity is our attempt to address this.
Our entire toolchain grew up in a time when this modularity stuff was neither possible nor desirable.
What even is this
"Factory 2.0"?
You can read our design documents for the long-winded vision.
It's an umbrella initiative for fixing chronic problems that span the build-to-release pipeline.
For today, I want to focus on:
- Measurements
- Continuous Integration
- Modularity
The existing pipeline
idealized
really
it's more like
but,
let's just pretend
to start with:
measurements
it's getting complicated,
real quick
For example, one of our overall goals is to be able to get content into containers as quickly and painlessly as possible.
Consider measuring the delay for that. It makes my head spin!
continuous integration
today
What problems do we have here?
a first step
resultsdb
some more detail
on the data feed
putting resultsdb
to use
but what if
the machines are wrong?
not entirely
sufficient
the "interface"
for CI
building modules
(new topic)
buildroots,
today
buildroots,
with modules
containers
from modules
let's talk about...
branching,
today
branching,
tomorrow
branching,
with rhel
branching,
with modules
Lots to think about
with a new branching structure
- Will there ever be a f27 branch?
- What about EOLs for these new world branches?
- What's the economic force that will generate new branch requests?
- Is the module's EOL the minimum of the union of its component EOLs?
- If all active branches of a component go EOL, do we automatically retire it?
lots to think about
lots to do
Thank you!
Presented at DevConf 2017 by @ralphbean.
Slides available at http://threebean.org/presentations/factory2-devconf17/
Hop in #fedora-modularity to join the party (we share it with the modularity team).