[Container-tools] Minutes from Tools Cabal Call Sep 8

[Daniel Veillard]

                   Minutes from Tools Cabal Call Sep 8


DV forgot to keep attendance list !

1/ example for nulecule/atomic-app
 - only a few examples should shoiw in the spec
 - most of the new examples should go into a separate repo in atomicapp
 - We sould have a library of useful applications, how do we organize that ?
   Distribution justifications, do we want to set that as a main criteria to
   classify them ?
 - Lala suggest to start on CentOS and see how this grows. Sometimes there
   might be good reason to package on one base OS vs another, but thei
   containers should be an unification mechanism.
 - bex suggested that project atomic host apps on their "best" os, and we create repos in fedora/centos projects that mirror and rebuild on just their os
    Just host the images in Dockerhub ? To avoid bing singled out.
 - Decision: move examples out of nulecule that don't show the spec -
   go for minimal examples but full coverage.  Move appropriate examples into
   atomic app but mostly point to the repo of applications; Put up a repo in
   project atomic and get images into docker hub;
   step 2 work with fedora/centos and hopefully use the centos registry one day

2/ Status of beta2:
  meeting with Sreenath on beta2: what do we deliver exactly
     - vagrant box based on RHEL-7.2 beta (This is ADB-based CDK)
        - box is prepopulated with containers for OS, etc.
         - This was not targetted for Beta2 as we have not agreed on any
           solution.(Lala)
     - vagrant box based on RHEL-Atomic (non-ADB/CDK - just a box for testing)
       (needed tyo verify that app still runs on Atomic)
     - Tar file with all the additional setup tools:
         - plugins, and vagrant  file
             - includes registration plug-in on RHEL only
     - container build and registered in the Red Hat registry
       (Which containers are we delivering to the registry for beta2??)
     - add example containers ? Would make sense but not for beta2

   Building container in brew is based on kickstart files, Ian thinks that
   for layered images one can build them using OSBS, Ian and Vasek to help,
   may try to get Lanbgdon feedback through he's on vacations

3/ Another provider:
   Ratnadeep suggestst to add Docker-compose, which should be simple, and
   also document the process so that others can work on adding providers

   Need to clearly articulate how do do so, that's probably more important
   than adding Docker-compose itself.
   Is the issue about the provider APIs closed ? Should probably go first.
    - Aaron issues about how install and run is to be modified should not
      affect the API
  Langdon had a first Compose provider but it was never merged

  A bunch of challenges with kubernetes were mentioned - can we get more
  detail there?
  - It was hit as part of doing the Sentry packaging it's not broken, it's
    more a difference between how kubernete works and how Docker works

4/ Dynamic parameters:
   When  lanching mutiple comtainer, we need to be able to introspect them,
   and those values and their availability can be used as dependancy graph.
   => this is classic in cloud orchestration
      one part is the introspection, the other is the orchestration

  People like Dan Walsh,  Walters, Calayton, etc ... ought to be involved
  in the discussion if we plan to go into that direction. The openstack
  in container work hit that. it may simply come into provider themselves,
  we probably shouldn't over engineer it and let them solve it.
  Ian points at nulecule/issues/97
  Discussion need to go into container tools list but send a mail to wider
  internal list that say the issue is discussed there.

Daniel

-- 
Daniel Veillard      | Open Source and Standards, Red Hat
veillard at redhat.com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | virtualization library  http://libvirt.org/