<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div>Ideally a build would continue into deployment, but there are some challenges. We definitely need to brainstorm and implement better guide rails around this in the near term.</div><div><br>On May 18, 2016, at 10:33 AM, Burr Sutter <<a href="mailto:bsutter@redhat.com">bsutter@redhat.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 18, 2016 at 10:14 AM, Clayton Coleman <span dir="ltr"><<a href="mailto:ccoleman@redhat.com" target="_blank">ccoleman@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">start build has no idea what your destination runtime environment is,<br>
unfortunately.<br></blockquote><div><br></div><div>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".</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
On Wed, May 18, 2016 at 10:03 AM, Burr Sutter <<a href="mailto:bsutter@redhat.com">bsutter@redhat.com</a>> wrote:<br>
> Actually I was thinking we need the warning on "oc start-build" since that<br>
> is how we are primarily re-deploying to OpenShift for Helloworld MSA.<br>
><br>
> On Wed, May 18, 2016 at 9:46 AM, Clayton Coleman <<a href="mailto:ccoleman@redhat.com">ccoleman@redhat.com</a>><br>
> wrote:<br>
>><br>
>> Yes, this is an openshift problem (really, it's container platform,<br>
>> but we'll use OpenShift as a proxy here).<br>
>><br>
>> We have added things that make it easier, and warnings, but people<br>
>> don't read stuff. For instance, new-app warns you, and "oc status"<br>
>> tells you exactly what to do, but we need it in more places.<br>
>><br>
>> On Wed, May 18, 2016 at 9:17 AM, Burr Sutter <<a href="mailto:bsutter@redhat.com">bsutter@redhat.com</a>> wrote:<br>
>> ><br>
>> ><br>
>> > On Wed, May 18, 2016 at 8:34 AM, Aaron Weitekamp <<a href="mailto:aweiteka@redhat.com">aweiteka@redhat.com</a>><br>
>> > wrote:<br>
>> >><br>
>> >> On Wed, May 18, 2016 at 8:30 AM, Dusty Mabe <<a href="mailto:dusty@dustymabe.com">dusty@dustymabe.com</a>><br>
>> >> wrote:<br>
>> >>><br>
>> >>><br>
>> >>><br>
>> >>> On 05/18/2016 07:18 AM, Aslak Knutsen wrote:<br>
>> >>> > I think most teams at the Brno F2F were struggling with this. It<br>
>> >>> > works<br>
>> >>> > locally, but semi-obscure failures when pushed 'live'. And out of<br>
>> >>> > the 30 RH<br>
>> >>> > engineers there, none knew 100% or was able to dig up a doc that<br>
>> >>> > explained<br>
>> >>> > why and how to fix it...<br>
>> >>> ><br>
>> >>> > This is/will be a massive pain point moving from Dev to Production.<br>
>> >>> > The<br>
>> >>> > very least we need some very clear, simple guides on how to make it<br>
>> >>> > work.<br>
>> >>><br>
>> >>> Yeah, I think a lot of people are going to be very frustrated by this.<br>
>> >>> It took me over an hour to track down and that's only because I know a<br>
>> >>> lot about how the CDK is set up. Others would probably never be able<br>
>> >>> to figure it out.<br>
>> >>><br>
>> >><br>
>> >> For the "eval" use case we made the right choice. Dusty's question is<br>
>> >> about the CDK use case. To my mind the CDK should add value to a<br>
>> >> n openshift eval environment. This is a great opportunity for the CDK<br>
>> >> to<br>
>> >> provide tooling to address this ubiquitous problem. Mitch Harpur's<br>
>> >> ideas<br>
>> >> around this months ago were spot-on: walk devs through a journey,<br>
>> >> educate<br>
>> >> them, etc.<br>
>> ><br>
>> ><br>
>> > Either the CDK can add this additional "tool", to help walk an end-user<br>
>> > through a "proper" Dockerfile or pre-built container image.<br>
>> ><br>
>> > OR<br>
>> ><br>
>> > Openshift could offer this tool and I believe that is where it belongs.<br>
>> > Because Openshift Online Users are going to hit this 100 times an hour<br>
>> > once<br>
>> > we open up the floodgates. :-)<br>
>> ><br>
>> ><br>
>> >><br>
>> >><br>
>> >>> _______________________________________________<br>
>> >>> Devtools mailing list<br>
>> >>> <a href="mailto:Devtools@redhat.com">Devtools@redhat.com</a><br>
>> >>> <a href="https://www.redhat.com/mailman/listinfo/devtools" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/devtools</a><br>
>> >><br>
>> >><br>
>> >><br>
>> >> _______________________________________________<br>
>> >> Container-tools mailing list<br>
>> >> <a href="mailto:Container-tools@redhat.com">Container-tools@redhat.com</a><br>
>> >> <a href="https://www.redhat.com/mailman/listinfo/container-tools" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/container-tools</a><br>
>> >><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > Devtools mailing list<br>
>> > <a href="mailto:Devtools@redhat.com">Devtools@redhat.com</a><br>
>> > <a href="https://www.redhat.com/mailman/listinfo/devtools" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/devtools</a><br>
>> ><br>
><br>
><br>
</div></div></blockquote></div><br></div></div>
</div></blockquote></body></html>