[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [atomic-devel] Adding a new repository on GitHub for

To get a sense of what's going on, I'd read this: http://rhelblog.redhat.com/2015/05/05/rkt-appc-and-docker-a-take-on-the-linux-container-upstream/

Yes, saw that the other day.  It also highlights a general issue that this is a fast moving confusing space to begin with.

 It's cold comfort to tell you that TOP MEN are working on it 


Top.  Men.  (obligatory Indiana Jones reference completion)

In all seriousness, getting these sorts of things into the list faster is always better.  I'd like to get the quick start / getting started docs into a better state that follows an actual workflow.  Knowing where and how things relate even at an early state is good.  For example, I'm working on a quick start version focuses on getting a single host and single container up using the new atomic command, instead of it stopping where it does now.  I'm fairly sure that's not a dead end that will require major rework or set out a bad use case.  

But addressing the other issue about including the kubernetes guestbook example in the getting started guide is a bigger issue if we have other plans for what a clustered Atomic presence entails.  Or I could be conflating something here, and just pick another kubernetes example to fork and make stable for Atomic...

I'm also a bit of a squirrel so each new project gives me something new to chase instead of finishing the quickstart for review.  That's not a community issue :)

- Matt M

On Fri, May 8, 2015 at 12:50 PM, John Mark Walker <jowalker redhat com> wrote:

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?

Yeah, this needs to be laid out.

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?

Nope, not just you. And you're right that there's some stuff missing at the moment. It's cold comfort to tell you that TOP MEN are working on it as I write this, but expect a more community-driven process Real Soon Now.


- Matt M

On Fri, May 8, 2015 at 9:53 AM, Joe Brockmeier <jzb redhat com> 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.


Joe Brockmeier | Principal Cloud & Storage Analyst
jzb redhat com | http://community.redhat.com/
Twitter: @jzb  | http://dissociatedpress.net/

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]