#2883 Change: Ostree Native Container (Phase 2, stable)
Opened a month ago by bcotton. Modified 18 hours ago

Continue the work done in https://fedoraproject.org/wiki/Changes/OstreeNativeContainer but in an officially stable format, and expanded to cover more OSTree-based editions. This goes "all in" on being container-native and significantly changes the technology and user emphasis.

Owners, do not implement this work until the FESCo vote has explicitly ended.
The Fedora Program Manager will create a tracking bug in Bugzilla for this Change, which is your indication to proceed.
See the FESCo ticket policy and the Changes policy for more information.


Hmm, nobody has picked this up. FESCo members: please vote.

-0 to avoid automatic approval.

-0 to avoid automatic approval.

Shouldn't that be a -1 if you want to block auto approval? (And thus tag it for the meeting). -0 seems like we're trying to be too clever with the voting process.

I have concerns about the nature of this proposal, especially creating a co-dependency model for RPM-OSTree based variants with this "layering" thing.

-1

Metadata Update from @ngompa:
- Issue tagged with: meeting

a month ago

especially creating a co-dependency model for RPM-OSTree based variants with this "layering" thing.

Can you elaborate on this? What's the co-dependency here?

This will be discussed during today's meeting at 17:00 UTC.

0 (temporarily)

I think I like where this is headed, but there's so much in the proposal that it's difficult for me to track it all. A visual representation (maybe a diagram or flow chart?) would help me out a lot.

This was discussed during today's FESCo meeting:
* AGREED: Everybody is to re-read the prosal and vote in the ticket.
* If that fails, we'll vote next week in the meeting.

I think I like where this is headed, but there's so much in the proposal that it's difficult for me to track it all. A visual representation (maybe a diagram or flow chart?) would help me out a lot.

Conceptually, the center of the of things becomes bootable container images - implemented using ostree for now.

Are there any more specific details I can help with? Happy to join a realtime meeting and explain/demo things if that helps!

+1

I am a staff engineer on OpenShift core engineering. We are working on shipping this on OpenShift and taking a hard dependency on the ability to boot and configure the operating system from a container image. We are very interested in landing this in Fedora and derived distributions in a sustainable manner.

  • AGREED: Everybody is to re-read the prosal and vote in the ticket.

I'm obviously open to more detailed and nuanced feedback outside of the set of "+1, 0, -1" by the way! It's a big proposal and nothing is "set in stone".

This OpenShift commons lightning talk might help explain some of the motivation behind this - though I'd emphasize from my (OCP developer hat) perspective I also want this functionality to apply to Linux systems in general, not just Kubernetes nodes.

FWIW, I'm +1 to the proposal in general. If we end up having concerns with individual bits of it, we can address those as they come up.

Metadata Update from @sgallagh:
- Issue untagged with: meeting

18 hours ago

+1

This is a good direction overall and will hopefully improve both CoreOS and Silverblue.

Login to comment on this ticket.

Metadata