#1396 F22 System Wide Change: Atomic Host - https://fedoraproject.org/wiki/Changes/AtomicHost
Closed None Opened 4 years ago by jreznik.

For the 2015-01-28 meeting as the Change Proposal was announced on devel-announce list on 2015-01-20.

New Fedora product: Fedora Atomic Host, an implementation of the Project Atomic pattern.
This is a continuation and expansion of Changes/Atomic_Cloud_Image.


Will revisit this next week.

This ticket will be discussed in the FESCo meeting on Wednesday at 18:00UTC in #fedora-meeting on irc.freenode.net.

(Has anything changed in the last 2/3 weeks?)

We had a great hackfest/meeting relevant to this at DevConf.cz on Saturday. I think it will be very relevant here, making this change a lot more clear and concrete (and totally rewritten).

More soon -- not by this week's meeting. Obviously we're way past F22 deadline for system-wide changes; this will be designed to be in the F22 timeframe but not tied to the release. (Timing primarily assuming we can hire [http://jobs.redhat.com/jobs/descriptions/lead-engineer-fedora-project-atomic-infrastructure-raleigh-north-carolina-job-1-5092722 this role] RSN.)

From today’s FESCo meeting: Defer tickets 1390, 1396, 1397 until we get more specifics, remove meeting keyword until then (+6)

Matt, can you elaborate on "but not tied to the release."? What does that mean?

A major decision for this is whether AtomicHost remains part of the Cloud group, joins the Server, or becomes its own product. I don't have a strong opinion really - it could remain in Cloud, but it would feel weird as Atomic also can be bare metal/stateful (like Server).

The cloud distinction isn't necessarily bare-metal vs. hosted. But I am kind of thinking it should grow out of the cloud group into its own thing, if not yet its own product.

FESCo, please review the change again and ask concrete questions.

From today's FESCo meeting: FESCo tentatively approves the AtomicHost Change. nirik will work with walters and jzb to clarify things on the Change page (+1: 8, -1: 0, 0:0)

Login to comment on this ticket.

Metadata