[Container-tools] Atomic CLI + Atomicapp workflow

Dusty Mabe dusty at dustymabe.com
Wed Nov 4 14:41:21 UTC 2015



On 11/04/2015 09:17 AM, Christoph Görn wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Hey Dusty, all,
>   I'm all GO on this.
>
>   3. needs to be a 'container first' solution. I know there are RPMs out
>   there, but they will disappear in the future.
Maybe people using rpms directly will be minimized but I think some of 
our base containers will be built from the atomicapp rpm, though.

>
>   1. seems to be a convenience product for atomicapp. I would really love
>   to see the super old and first requirement fulfilled: 'atomic run
>   ipa-server', but I am sure that this 'atomic run' needs to do a few
>   of the lifecycle management steps described in 2.

yes, it will automatically do those steps.

>
> 	//G
>
> On 11/04/2015 02:45 AM, Dusty Mabe wrote:
>> Hi all,
>>
>> I've had conversations over the past few weeks with many of you
>> about atomicapp and running it through Atomic CLI. Basically the
>> problem is that the INSTALL/RUN/STOP labels are a bit fragile and
>> we have seen breakage a few times as a result. In the discussions
>> we have talked about better alternatives and I think this is what
>> we'd like to go with in the future:
>>
>> 1 - the only case where atomic cli needs to work is for running
>> `atomic run <appname>` any other piece of the puzzle WILL be
>> handled by the atomicapp cli (excludes openshift use case) 2 -
>> people can use the atomicapp cli to do
>> unpack/install/run/uninstall/etc... whatever the tool supports they
>> can do it 3 - people can use atomicapp cli from an installed rpm OR
>> from an alias that runs a docker container to run the cli
>>
>> An example of the alias would be: alias atomicapp='docker run -it
>> --rm  --privileged -v $(pwd):/atomicapp -v /run:/run -v /:/host
>> --net=host --name atomicapp projectatomic/atomicapp:latest' OR in
>> the future may be: alias atomicapp='atomic run
>> projectatomic/atomicapp'
>>
>> The idea is that you would use the alias just like if atomicapp
>> were installed on the system: atomicapp install dusty/helloapache
>> cd /var/lib/atomicapp/dusty-helloapache-9cb2a3704f1d atomicapp run
>> --provider docker ./ curl localhost atomicapp stop ./
>>
>> So with all of this, my question is: can we get rid of the INSTALL
>> and STOP labels in the Dockerfiles for Atomic App?
>>
>> Dusty
>>
>> _______________________________________________ Container-tools
>> mailing list Container-tools at redhat.com
>> https://www.redhat.com/mailman/listinfo/container-tools
> - -- 
> Principal Software Engineer - Systems Design & Engineering
> Mobile: +49 171 2801345
>
> Follow Us: https://twitter.com/RedHatRefArch
> Plus Us: https://plus.google.com/u/0/b/114152126783830728030/
> Like Us: https://www.facebook.com/rhrefarch
>
> Red Hat GmbH, http://www.de.redhat.com/ Sitz: Grasbrunn,
> Handelsregister: Amtsgericht München, HRB 153243
> Geschäftsführer: Charles Cachera, Michael Cunningham, Michael O'Neill,
> Charles Peters
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iQIcBAEBCAAGBQJWOhNuAAoJEKn71953Oyo0/uMP/jobGtVv+fFaja3OzBaNlkdi
> +blbPZ56DQCpqpPXpxwPll/v3bowhCJaoy31muoVk7lArJVMUna1MSeiZ1OJORmn
> WZ3SkR60PDkZ2vg6X875gVH1BtLJsKB7IRZV6PaY1lN1j/SE7foUDB3d+sets/4e
> mnfuxBI2ZZ1retQHrz/UUGuQBVHzFpOHqU4CiXJnCJOYJFeAAn1zP/othKgP6x/p
> GhDiIMy6nSoGQDM4y8obPPpaSGhGnfRRGpI441dii7+KvxSqZ+hatvD8OHQTBQ0f
> 9iBqKLnEuq3sYYx/jNPUyfxHMXAa+jzouw7/eFCPTXAgCxobBND4QTX34wJ6GS2D
> Z5RpLb6DTeqo8kGo/vPTiy0TCdgHEinawSXpKx6V1g65u9KaMg2lu63sgxwvQh06
> vJ1Y5Xn3Fz/evzdbaNGW++tyRiXMHZ+hN4rVrqfeModZZVD/kwe2NBZeHBGAdtbP
> TOM/9PHyaO+4HUKNbNisSslngNnrazc7ha+QOSyprkDGOEXC81KDnf/MaauarKve
> BIPas2BTTsyVqg3hr6XWQT3FKVgMaKr/hLCLI9OjZ19NYpsSEl2rgYdXwrDLgait
> pN3AAGq/VuE2hNGz0V2Kz4Zkb8qq7ifHFsG8+BvWtISHmCzk6R3zmXujUr2VAutQ
> SG/0YaWwFh3vv1ofqqk6
> =maS0
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Container-tools mailing list
> Container-tools at redhat.com
> https://www.redhat.com/mailman/listinfo/container-tools




More information about the Container-tools mailing list