<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div>We're looking in the near future to put app creation behind an API - when we do that the console would be able to leverage it.</div><div><br>On Oct 12, 2015, at 1:22 AM, Lalatendu Mohanty <<a href="mailto:lmohanty@redhat.com">lmohanty@redhat.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type">
<div class="moz-cite-prefix">On 10/09/2015 02:38 AM, Aaron Weitekamp
wrote:<br>
</div>
<blockquote cite="mid:CAOUu1um0ZoOx9tYUb1hTbKAohP40AayZfbZPUVNZgTbqkqd7Zw@mail.gmail.com" type="cite">
<div dir="ltr">
<div class="gmail_default" style="font-size:small">Speaking with
Clayton we believe we have a path to running an atomicapp
using native OpenShift 'oc' CLI.</div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<div class="gmail_default" style="font-size:small"><b>Proposal:</b></div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<div class="gmail_default" style="font-size:small">oc new-app
<atomicapp-image> [-p foo=bar,bee=baz]</div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<div class="gmail_default" style="font-size:small">This command
will kick off running the image in a pod. Inside this pod oc
commands will be executed as the user. Remote or composite
atomicapps will be chained in the same way via oc new-app
<remote-image>.<br>
</div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<div class="gmail_default" style="font-size:small">For MVP we
will not support answerfile or interactive install since oc
does not have a mechanism for that today.</div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<div class="gmail_default" style="font-size:small">All other
application lifecycle commands will be handled by native oc
commands as they are today, outside of atomicapp.</div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<div class="gmail_default" style="font-size:small"><b>Required
changes (for discussion):</b></div>
<div class="gmail_default" style="font-size:small">- identify an
io.openshift label for atomicapp image that identifies as an
atomicapp</div>
<div class="gmail_default" style="font-size:small">- openshift
user token should be passed into the atomicapp pod</div>
<div class="gmail_default" style="font-size:small">- atomicapp
openshift provider should not call docker but use the oc
client</div>
<div class="gmail_default" style="font-size:small">- params need
to be passed into atomicapp pod and need to be parsed by
atomicapp</div>
<div class="gmail_default" style="font-size:small">- oc client
either needs to be built into atomicapp or a sidecar container
needs to be spun up in the same pod. TBD</div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<div class="gmail_default" style="font-size:small">There are
probably many other details I'm missing. It basically means
some patches to openshift, refactor openshift provider and
support all the edge cases to handle params, etc.</div>
<div class="gmail_default" style="font-size:small"><br>
</div>
</div>
<br>
</blockquote>
<br>
Is there a plan to use the web console of OpenShift to run Atomic
App? May be in distant future.<br>
<br>
-Lala <br>
</div></blockquote></body></html>