On Mon, Aug 1, 2016 at 7:35 AM, Pete Muir <[email protected]> wrote: > On 29 July 2016 at 19:50, Lalatendu Mohanty <[email protected]> wrote: > > On 07/27/2016 10:06 PM, Rick Wagner wrote: > > > > Hello DevTools SMEs, > > > > We are seeing a few more CDK support cases, most seem to indicate > curiosity > > and tire-kicking. We also have a case with a customer going a step > further. > > > > The customer in question wants to use the CDK to develop on the desktop > and > > deploy to an Enterprise OpenShift. > > > > It's my understanding that there are two primary schemes: > > > > - Push source code (perhaps using a tag like 'prod') to a source > repository > > accessed by the enterprise OpenShift environment. (Be it QE, Prod, > > whatever). > > - Push docker images to an external repository accessed by the enterprise > > OpenShift. > > > > > > These ideas perfectly makes sense to me. Any organization going through > the > > DevOps route would need this work flows. > > > > > > There are nuances like use of WebHooks vs. manual pulls, Jenkins doing > the > > monitoring, etc. > > > > This seems a really foundational use case for the CDK, so it seems like > > something we'd want to document. I've been discussing this with Robert > > Kratky but wanted to open the discussion to get more viewpoints (and > > especially more users that have experience.) > > > > > > These needs to ironed out , needs testing and then documentation. > > > > > > Of special interest: > > > > - The customer is indicating a desire for some widget on the CDK-supplied > > OpenShift UI so he can 'push' artifacts to the enterprise OpenShift's > docker > > repository. > > > > +1 . Developer tool should help move things in to the DevOps workflow. > The > > pipeline work going on in OpenShift might align here. Need to cross > check. > > I think the CD pipeline (i.e. pushing source) should be our > recommended approach here. > > +1 if the developer loses the source on (local hard drive fail) then there would be no way to recreate the image on another machine. It is super critical that "builds be reproducible" and that means all source artifacts (including Dockerfile and/or Openshift template files) need to be "checked in" to a source repo. And from that source repo a CI job runs to produce the "one true image" that moves to the production/enterprise openshift.
Overall, the concept of using the CDK for on-desktop development for a remote OpenShift IS a very normal use case for us to be supporting. > > > > - The customer is asking if Docker version is relevant. (i.e. the CDK's > > version of Docker may need to align with the external image repository's > > version. True or False?) > > > > > > The only requirement I think is the docker version should support the > image > > format present in external image repository. I do not think this would be > > problem if they stick to OpenShift Enterprise. > > > > > > Please consider, add thoughts to the discussion. > > > > Thank you, > > > > Rick > > > > > > _______________________________________________ > > Devtools mailing list > > [email protected] > > https://www.redhat.com/mailman/listinfo/devtools > > > > > > > > _______________________________________________ > > Devtools mailing list > > [email protected] > > https://www.redhat.com/mailman/listinfo/devtools > > > > _______________________________________________ > Devtools mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/devtools >
_______________________________________________ Devtools mailing list [email protected] https://www.redhat.com/mailman/listinfo/devtools
