[Container-tools] Nulecule/AtomicApp BoF at OSCon

[Brian (bex) Exelbierd]

I'd like to resurrect this thread.  We need to be more clear in our use 
cases and let that start to drive some of our complex examples.  To this 
end, I have started an etherpad[0] listing use cases I think we want to 
acknowledge and support.

Are there others?

regards,

bex

0: http://etherpad.osuosl.org/Nulecule-use-cases

On 07/30/2015 04:37 AM, Aaron Weitekamp wrote:
> On Tue, Jul 28, 2015 at 10:37 AM, John Mark Walker <johnmark at redhat.com
> <mailto:johnmark at redhat.com>> wrote:
>
>
>     On Jul 28, 2015 9:25 AM, Daniel J Walsh <dwalsh at redhat.com
>     <mailto:dwalsh at redhat.com>> wrote:
>     >
>     >
>     >
>     > On 07/28/2015 08:43 AM, James Shubin wrote:
>     >>
>     >> On Mon, 2015-07-27 at 20:07 -0400, Langdon White wrote:
>     >>>
>     >>> However, I wanted to bring up one thing which came up. One of the people
>     >>>
>     >>> asked me "how is this different from config mgmt a la chef". While I
>     >>>
>     >>> know in my head it is different,
>     >>>
>     >> I agree...
>     >>
>     >>
>     >>
>     >>>  and potentially even a wrapper around
>     >>>
>     >>> config mgmt, I was struggling with articulating a clear/concise answer.
>     >>>
>     >>> As a result, I thought I would raise it to the list.
>     >>>
>
>     This is perhaps the big question we need to answer.
>
>     >>>
>     >>>
>     >>> Included James Shubin (who may already be subscribed) as the most
>     >>>
>     >>> expert-y config mgmt person I know for his perspective.
>     >>>
>     >> I've thought about this, and the short answer is that it's a long
>     >>
>     >> answer. Here's the shortest version:
>     >>
>     >>
>     >>
>     >> They're different, but only because IMO, the config management tools
>     >>
>     >> which would solve this problem elegantly, don't currently exist ATM.
>     >>
>     >>
>     >>
>     >> Assuming it doesn't offend anyone, I see Nulecule as a stop-gap until
>     >>
>     >> config management learns how to better build multi-container
>     >>
>     >> applications. This won't happen for at least a year. Assuming I'm wrong,
>     >>
>     >> please excuse this due to my lack of knowledge into some of the Nulecule
>     >>
>     >> specifics.
>
>     To be fair, nulecule should be viewed independently of atomic. As
>     in, nulecule could be used by config management tools to define
>     cloud native apps.
>
>     >>
>     >>
>     >>
>     >>Container-tools at redhat.com <mailto:Container-tools at redhat.com>
>     >>
>     >>https://www.redhat.com/mailman/listinfo/container-tools
>     >>
>     > atomic +labels (install, run, uninstall) allows an developer to define how his application runs inside of the Open Container Format.
>     > Nulecule allows the define how Multi-Container applications can be run/installed, and then allows the developer a standard format
>     > to ask administrators for additional configuration data like how my replicas of each service would they like.
>     >
>     > Orchestration tools can than take advantage of this tooling to spread the application throughout the environment.
>     >
>     > Daniel Riek could probably expand on this.
>
>     Aaron W also had some thoughts on this, I believe - Aaron?
>
>
> ​I agree with Dan's summary. I think we should stick with a pretty
> simple story. It's a generalized installation pattern for container
> apps. Like any good installer you can pass in parameters. Like any
> installer it can be incorporated into other tools and workflows or used
> stand-alone.
>
> -Aaron
>
>     -JM
>
>
>     _______________________________________________
>     Container-tools mailing list
>     Container-tools at redhat.com <mailto:Container-tools at redhat.com>
>     https://www.redhat.com/mailman/listinfo/container-tools
>
>
>
>
> _______________________________________________
> Container-tools mailing list
> Container-tools at redhat.com
> https://www.redhat.com/mailman/listinfo/container-tools
>