This change: https://fedoraproject.org/wiki/Changes/AtomicHost is presently blocked on: https://fedorahosted.org/rel-eng/ticket/6119
Currently Fedora 22 will have Atomic cloud images and vagrant boxes (and an updated tree).
It will be *possible* to install to bare metal using kickstart, but the Anaconda GUI doesn't support either ostree or docker currently - the change above addresses the ostree part.
There is currently no movement on the PXE-to-Live portion.
Any help appreciated.
On Thu, Mar 26, 2015 at 10:01:15AM -0400, Colin Walters wrote:
This change: https://fedoraproject.org/wiki/Changes/AtomicHost is presently blocked on: https://fedorahosted.org/rel-eng/ticket/6119
Is the blocker a disagreement on where the implementation should be done, or is it a lack of someone to make and test the needed changes?
On Thu, Mar 26, 2015 at 2:29 PM, Matthew Miller mattdm@fedoraproject.org wrote:
On Thu, Mar 26, 2015 at 10:01:15AM -0400, Colin Walters wrote:
This change: https://fedoraproject.org/wiki/Changes/AtomicHost is presently blocked on: https://fedorahosted.org/rel-eng/ticket/6119
Is the blocker a disagreement on where the implementation should be done, or is it a lack of someone to make and test the needed changes?
Ultimately the request came in 3 weeks ago, that's post freeze. Rel-eng has a lot to deliver in each release and limited resources, Changes that need rel-eng engagement should have our buy in long before they're sent to FESCo to ensure we have the time to schedule the changes as we try and freeze all changes to the process by the devel change freeze as well so that we can concentrate on the actual release rather than chasing breakages from last minute requests.
Things like changes to koji should be requested with enough time to devel/test/integrate them and the process of using koji/mock etc is fairly well known here.
Peter
The only use case I have at the moment for Atomic is as a *potential* replacement for "Boot2Docker" on a Windows 8.1 - 10 Client Hyper-V host. And there I'm perfectly happy with a CentOS Atomic - all it has to do is run Docker containers and not have a larger attack surface than Boot2Docker. ;-) .
Moreover, Microsoft seems to be going down the Boot2Docker path and ignoring Atomic. So I'm reluctant to do much more than try to run a container right now, since I don't know I'd be able to find anything in Microsoft support forums.
On Thu, Mar 26, 2015 at 7:57 AM, Peter Robinson pbrobinson@gmail.com wrote:
On Thu, Mar 26, 2015 at 2:29 PM, Matthew Miller mattdm@fedoraproject.org wrote:
On Thu, Mar 26, 2015 at 10:01:15AM -0400, Colin Walters wrote:
This change: https://fedoraproject.org/wiki/Changes/AtomicHost is presently blocked on: https://fedorahosted.org/rel-eng/ticket/6119
Is the blocker a disagreement on where the implementation should be done, or is it a lack of someone to make and test the needed changes?
Ultimately the request came in 3 weeks ago, that's post freeze. Rel-eng has a lot to deliver in each release and limited resources, Changes that need rel-eng engagement should have our buy in long before they're sent to FESCo to ensure we have the time to schedule the changes as we try and freeze all changes to the process by the devel change freeze as well so that we can concentrate on the actual release rather than chasing breakages from last minute requests.
Things like changes to koji should be requested with enough time to devel/test/integrate them and the process of using koji/mock etc is fairly well known here.
Peter _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Thu, Mar 26, 2015 at 10:11:53AM -0700, M. Edward (Ed) Borasky wrote:
Moreover, Microsoft seems to be going down the Boot2Docker path and ignoring Atomic. So I'm reluctant to do much more than try to run a container right now, since I don't know I'd be able to find anything in Microsoft support forums.
I don't know about Microsoft, but Atomic aims to be a lot more than just a "boot to docker" platform, including application orchestration.
On Thu, Mar 26, 2015 at 10:19 AM, Matthew Miller mattdm@fedoraproject.org wrote:
I don't know about Microsoft, but Atomic aims to be a lot more than just a "boot to docker" platform, including application orchestration.
Can't I do that with a CentOS Atomic build?
On Thu, Mar 26, 2015 at 10:24:20AM -0700, M. Edward (Ed) Borasky wrote:
I don't know about Microsoft, but Atomic aims to be a lot more than just a "boot to docker" platform, including application orchestration.
Can't I do that with a CentOS Atomic build?
Oh, of course. The plan being discussed is that development will land first in Fedora, on a two-week cycle, and then flow to CentOS. So, if you want to engage early, Fedora Atomic is the place — especially if you want to be involved in shaping the direction, but also if you want to follow the leading edge of fast-moving Atomic development.
If you're looking to deploy primarily as an end-user, CentOS Atomic might be what you want. With my Fedora hat on, I think there's space for early adopters in Fedora too (and by design, Atomic actually should make it fairly easy to move back and forth as appropriate without much hassle). And of course, with my employer's hat on, if you want certification and support, RHEL Atomic is always there for you (on a still fast but even more conservative cycle).
On Thu, Mar 26, 2015 at 10:36 AM, Matthew Miller mattdm@fedoraproject.org wrote:
Oh, of course. The plan being discussed is that development will land first in Fedora, on a two-week cycle, and then flow to CentOS. So, if you want to engage early, Fedora Atomic is the place — especially if you want to be involved in shaping the direction, but also if you want to follow the leading edge of fast-moving Atomic development.
If you're looking to deploy primarily as an end-user, CentOS Atomic might be what you want. With my Fedora hat on, I think there's space for early adopters in Fedora too (and by design, Atomic actually should make it fairly easy to move back and forth as appropriate without much hassle). And of course, with my employer's hat on, if you want certification and support, RHEL Atomic is always there for you (on a still fast but even more conservative cycle).
-- Matthew Miller mattdm@fedoraproject.org Fedora Project Leader _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
In the end, being the hard-core Linux geek I am, I'll probably test both. But I'm abandoning my Fedora Workstation remix in favor of Fedora-based Docker images that will run on a Fedora Workstation, a CentOS desktop, a Ubuntu LTS or latest OpenSUSE desktop or on Windows or Mac via some hosting mechanism.
Right now the hosting mechanisms for Windows appear to be Boot2Docker inside VirtualBox or Boot2Docker inside Client Hyper-V. My preference is Client Hyper-V because VirtualBox is inefficient and has a dodgy license. But if Atomic has advantages over Boot2Docker I'm going to go that way and hope I can convince Microsoft to go along with me. ;-) And I also want to be able to deploy on OpenShift, so I need to at least have some kind of familiarity with Atomic.
On 03/26/2015 10:01 AM, Colin Walters wrote:
It will be *possible* to install to bare metal using kickstart, but the Anaconda GUI doesn't support either ostree or docker currently - the change above addresses the ostree part.
OK. Not optimal, but then again -- Atomic Host shouldn't be installed as a singleton anyway.
We need to document this well - maybe have an Ansible script and sample KS script that will do the magic for users so they don't need to figure it out on their own.
Anybody want to take that on?