Hey Suraj, sorry for the delay responding On Fri, Feb 10, 2017 at 12:59 AM, Suraj Deshmukh <[email protected]> wrote:
> Hi Clayton, > > > This is new thread in support of `oc import docker-compose` with > kompose as backend. > > (I tried repying to your earlier mail thread but had few issues with > the ML, excuse me for that) > > Instead of deprecating this feature is there a way that we try to > integrate kompose as library/backend for `oc import docker-compose`, > this way kompose can do more. Right now kompose generates > configurations that are cluster agnostic. With this integration > kompose can now generate configurations tailored to that cluster by > querying specific information from cluster. > Kompose could do that on its own - having it in 'import docker-compose' doesn't really change that (since you already have connection via the kubeconfig file) > > For example right now we generate PVCs by default if volume is > specified in docker-compose, but if we know that cluster has no PV and > if we create PVC it's gonna fail, to workaround that we can give > better warnings or pointer to user to create PV first. So this is just > one thing and many other configurations can be generated. > Maybe I'm missing why that's not possible via Kompose. Part of the reason to cut this out is that kompose can be updated independently and deliver those features to users faster. Integrated, you'd be dependent on the release cycle (and thus have to wait longer). I know the Kompose RPM is already available in the centos PaaS sig repo, so it seems like this would actually be easier for users to consume. > > Thanks. > > > -- > - Suraj Deshmukh (surajd) > > https://deshmukhsuraj.wordpress.com > https://twitter.com/surajd_ > > _______________________________________________ > dev mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
