[Container-tools] Expressing relationships between containers/pods in Nulecule spec

[Mark Lamourine]

I added an issue to the Nulecule spec [1] to start a discussion of how to express relationships and communications links between containers within a nulecule.

It appears to me that we have deferred these relationships to Kubernetes until now by specifying artificats which are Kubernetes Service objects.

To create an OpenShift provider plugin, Atomicapp must communicate with the OpenShift API and express the configuration in terms that OpenShift can understand (and then convert back to its internal Kuberentes configuration).

I think we need to have a way to abstract and express these links in a way which would allow the atomicapp plugins to generate the appropriate output for the back end provider.  For kubernetes this would be the same Service spec JSON file, but for OpenShift or other PaaS providers it might be something very different.

I'd really like to find out I'm wrong.

Comments?

- Mark

[1] https://github.com/projectatomic/nulecule/issues/173

-- 
Mark Lamourine <mlamouri at redhat.com>
Sr. Software Developer, Cloud Strategy
Red Hat, 314 Littleton Road, Westford MA 01886
Voice: +1 978 392 1093
http://people.redhat.com/~mlamouri
markllama @ irc://irc.freenod.org*lopsa