[Container-tools] [Devtools] openshift is way too permissive in the CDK/ADB

[Burr Sutter]

On Wed, May 18, 2016 at 10:14 AM, Clayton Coleman <ccoleman at redhat.com>
wrote:

> start build has no idea what your destination runtime environment is,
> unfortunately.
>

Interesting...from an end-user perspective, it causes a "redeployment" but
I guess that is Openshift picking up the image stream change (pull)
therefore the potential "warning" message would only be in the OpenShift
console/logs, not as feedback/output of "start-build".


>
> On Wed, May 18, 2016 at 10:03 AM, Burr Sutter <bsutter at redhat.com> wrote:
> > Actually I was thinking we need the warning on "oc start-build" since
> that
> > is how we are primarily re-deploying to OpenShift for Helloworld MSA.
> >
> > On Wed, May 18, 2016 at 9:46 AM, Clayton Coleman <ccoleman at redhat.com>
> > wrote:
> >>
> >> Yes, this is an openshift problem (really, it's container platform,
> >> but we'll use OpenShift as a proxy here).
> >>
> >> We have added things that make it easier, and warnings, but people
> >> don't read stuff.  For instance, new-app warns you, and "oc status"
> >> tells you exactly what to do, but we need it in more places.
> >>
> >> On Wed, May 18, 2016 at 9:17 AM, Burr Sutter <bsutter at redhat.com>
> wrote:
> >> >
> >> >
> >> > On Wed, May 18, 2016 at 8:34 AM, Aaron Weitekamp <aweiteka at redhat.com
> >
> >> > wrote:
> >> >>
> >> >> On Wed, May 18, 2016 at 8:30 AM, Dusty Mabe <dusty at dustymabe.com>
> >> >> wrote:
> >> >>>
> >> >>>
> >> >>>
> >> >>> On 05/18/2016 07:18 AM, Aslak Knutsen wrote:
> >> >>> > I think most teams at the Brno F2F were struggling with this. It
> >> >>> > works
> >> >>> > locally, but semi-obscure failures when pushed 'live'. And out of
> >> >>> > the 30 RH
> >> >>> > engineers there, none knew 100% or was able to dig up a doc that
> >> >>> > explained
> >> >>> > why and how to fix it...
> >> >>> >
> >> >>> > This is/will be a massive pain point moving from Dev to
> Production.
> >> >>> > The
> >> >>> > very least we need some very clear, simple guides on how to make
> it
> >> >>> > work.
> >> >>>
> >> >>> Yeah, I think a lot of people are going to be very frustrated by
> this.
> >> >>> It took me over an hour to track down and that's only because I
> know a
> >> >>> lot about how the CDK is set up. Others would probably never be able
> >> >>> to figure it out.
> >> >>>
> >> >>
> >> >> For the "eval" use case we made the right choice. Dusty's question is
> >> >> about the CDK use case. To my mind the CDK should add value to a
> >> >> n openshift eval environment. This is a great opportunity for the CDK
> >> >> to
> >> >> provide tooling to address this ubiquitous problem. Mitch Harpur's
> >> >> ideas
> >> >> around this months ago were spot-on: walk devs through a journey,
> >> >> educate
> >> >> them, etc.
> >> >
> >> >
> >> > Either the CDK can add this additional "tool", to help walk an
> end-user
> >> > through a "proper" Dockerfile or pre-built container image.
> >> >
> >> > OR
> >> >
> >> > Openshift could offer this tool and I believe that is where it
> belongs.
> >> > Because Openshift Online Users are going to hit this 100 times an hour
> >> > once
> >> > we open up the floodgates.  :-)
> >> >
> >> >
> >> >>
> >> >>
> >> >>> _______________________________________________
> >> >>> Devtools mailing list
> >> >>> Devtools at redhat.com
> >> >>> https://www.redhat.com/mailman/listinfo/devtools
> >> >>
> >> >>
> >> >>
> >> >> _______________________________________________
> >> >> Container-tools mailing list
> >> >> Container-tools at redhat.com
> >> >> https://www.redhat.com/mailman/listinfo/container-tools
> >> >>
> >> >
> >> >
> >> > _______________________________________________
> >> > Devtools mailing list
> >> > Devtools at redhat.com
> >> > https://www.redhat.com/mailman/listinfo/devtools
> >> >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/container-tools/attachments/20160518/6e853743/attachment.htm>