[Container-tools] Spec, Examples and tools

[Christoph Görn]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hmm, 2. as a repo (containing all that is needed to build the
Atomicapp base image), 3. could be one repo (if we do it
Fedora-Dockerfiles style) or many repos (one for each Atomicapp) 1. is
a at least a PDF, therefore asciidoc, therefore a repo.

just me 2cents, as I said, I dont care about filesystem layout and
directory structure.

	//G

On 04/09/2015 05:32 PM, Langdon White wrote:
> 
> 
> On 04/09/2015 11:10 AM, Carl Trieloff wrote:
>> 
>> ack + inline.
>> 
>> 
>> 
>> On 04/09/2015 11:02 AM, Christoph Görn wrote:
>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>> 
>>> Hey all, getting away from the directory structure, I envision
>>> something like
>>> 
>>> 1. we have a Containerized Application Specification 
>>> (containerapp-spec) This will make statements about Atomicfile,
>>> content, meaning of the fields, providers, what providers must
>>> implemente, now fields are mapped by providers to ....
>>> 
>>> 2. We have Atomicapp Base Image This will container what vasec
>>> did, it will container an implementation of the docker
>>> provider, have a README how to use it to derive our/ISV app
>>> from it.
>> 
>> 2a). Don't think we can get away from also providing atomic tool
>> /lib, which can be run outside container to
>> 
>> 1.) validate (dry-run) a config 2.) auto get a container-app
>> basic structure 3.) convert to/from OpenShift format 4.) create
>> the container in (3) injecting the meta info + run tool.
>> 
>> 
>> 
>>> 3. We have some examples derived from 2. like wordpress (vasec
>>> did that) and mongoDB (I will do that)
>>> 
>>> We need to clean up the spec itself... and redo the POC we have
>>> done in the paste two weeks to be refactored to provide 2.
>>> 
>>> Anyway, we can continue with 3. and learn for the spec from
>>> that task and refactor later to meet 2. and 3.
>>> 
>>> //G
>> 
>> I have an open question of do we inject the params file into the
>> root container? if so we will have to touch it for each deploy
>> which is self defeating -- or is it passed in?
>> 
>> 
>> Carl.
>> 
>> _______________________________________________ Container-tools
>> mailing list Container-tools at redhat.com 
>> https://www.redhat.com/mailman/listinfo/container-tools
> 
> Christoph, so are you saying we need a least 3 separate repos? or
> are you just saying we need to be sure those topic areas are
> accounted for?
> 
> I just want to make sure this is approachable for someone from the 
> outside and some of this layout stuff is important to that.
> 
> Langdon
> 
> _______________________________________________ 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 v1

iQIcBAEBAgAGBQJVJpz/AAoJEKn71953Oyo00BYQAMONgAH2K9j6f89+q5NuncSU
NO4Voc66JlK7WId1mdB3DiE91cOapHLc5wQh3E6ckPorYg6MR453WKbbKE2yHSz6
3LFzM8zWlVqmXoN9IjQ+lFTOvBRO9FiOaBUIIW8bmJke1KmdVPkfUwem6O4Ro1ei
oSlTbbbUNyrYGjqjvWQKhda71eo6Exl7fR7IUgXCodM84T/iFCVfngfNr6r6NCYg
EDt+krUJTS+yca8wu+5jHttg1K6nS+y9drKQTy/7/FnDwWUPAPzS5ih0/qTcq+Ts
DCZUl3Hyez7FMMi8PekNkt+x0vJc/aLHIYPMAUGp3yBR/p3fkNfwOCz/mZmj0WWu
fn9tGQfoMvtkNGBmLz8ws+tXqK0jU24Qh66xeQfT94BQAaubqNkMp91RNwu+wE4J
4TLzRwVad9lPWQzmdVkmLBCPrw9NbDa6kZ1pNhQmrP/XVOJsnwafO/3xP1PZtzm5
L/UkAcVabsO9fP8aMQvFtKKUO6qUzKfJLFqpPvwwrhd39RnUAJ+aSpL5GFALs8hz
X/3bEdCQ145I12yGu6Vl6/ffrsLJDM4t/YboXNq3F4NPrzIrl2Saankmd/3BkCS5
6Lu0jq0pE9bLsrPXrxb3mNK5SCJVi5hZuZSKoFO+X/qrdprGwHViMNVLJUryGvbN
9jhA60rzbnmxC9pG8zbe
=jptC
-----END PGP SIGNATURE-----