It may be time for an update to the Atomic manifesto that lays down what all these new things are and how they all interrelate. I've seen bits and pieces, but have had to individually track down projects and intent to understand what atomicapp-run is and how it relaates to atomic and to Atomic, and so on.
It'd also be a good time to line up some clearer operating intent statements. I (for one) am unclear on the relationship between atomic install and say a kubernetes cluster for Atomic hosts. Is atomic run aimed at the standalone use case? Does the LABEL metadata make it into the published Docker image and can be used by kubernetes? Is there a new scheduling use case entirely that atomic run will replace kubernetes, or is that the atomicapp-run? These things may be clearer to folks closer to the projects, but from this list and IRC, I'm not seeing the forest for the trees. Is it just me? - Matt M On Fri, May 8, 2015 at 9:53 AM, Joe Brockmeier <[email protected]> wrote: > Hey all, > > Just a heads up for folks who are paying attention to the > (ever-increasing) git repositories under GitHub/projectatomic. > > Most folks know we've been working on Nulecule ( > https://github.com/projectatomic/nulecule) lately, and we plan to move > the reference implementation (AtomicApp - > https://github.com/vpavlin/atomicapp-run) over to the Project Atomic > github space shortly. > > Best, > > jzb > -- > Joe Brockmeier | Principal Cloud & Storage Analyst > [email protected] | http://community.redhat.com/ > Twitter: @jzb | http://dissociatedpress.net/ > >
