<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix"><br>
<br>
one last comment is that this solves the use case that of we don't
want to have to introduce two tools to a new Openshift user of oc
to pull from registry. however it still allows them to run
AtomicApp if they to get to the full set of AtomicApp verbs and
namespace/param options<br>
<br>
Carl.<br>
<br>
<br>
On 10/09/2015 08:03 AM, Carl Trieloff wrote:<br>
</div>
<blockquote cite="mid:5617AD28.70500@redhat.com" type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<div class="moz-cite-prefix"><br>
yip looks good<br>
<br>
On 10/08/2015 09:37 PM, Aaron Weitekamp wrote:<br>
</div>
<blockquote
cite="mid:CAOUu1ukrNKU4T1Yesk2b14L1yB+=2Yhfc4J4z_E+=nUzNd+2DA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_default" style="font-size:small">On Thu, Oct
8, 2015 at 5:08 PM, Aaron Weitekamp <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:aweiteka@redhat.com"
target="_blank">aweiteka@redhat.com</a>></span>
wrote:<br>
</div>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">
<div style="font-size:small">Speaking with Clayton we
believe we have a path to running an atomicapp using
native OpenShift 'oc' CLI.</div>
<div style="font-size:small"><br>
</div>
<div style="font-size:small"><b>Proposal:</b></div>
<div style="font-size:small"><br>
</div>
<div style="font-size:small">oc new-app
<atomicapp-image> [-p foo=bar,bee=baz]</div>
<div style="font-size:small"><br>
</div>
<div 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 style="font-size:small"><br>
</div>
<div 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 style="font-size:small"><br>
</div>
<div 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 style="font-size:small"><br>
</div>
<div style="font-size:small"><b>Required changes (for
discussion):</b></div>
<div style="font-size:small">- identify an
io.openshift label for atomicapp image that
identifies as an atomicapp</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
we could also call it something like io.nulecule.executable so
that it is not openshift specific but a generic so any tool can
read the label.. which openshift looks for.<br>
<br>
<blockquote
cite="mid:CAOUu1ukrNKU4T1Yesk2b14L1yB+=2Yhfc4J4z_E+=nUzNd+2DA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">
<div style="font-size:small">- openshift user token
should be passed into the atomicapp pod</div>
<div style="font-size:small">- atomicapp openshift
provider should not call docker but use the oc
client</div>
<div style="font-size:small">- params need to be
passed into atomicapp pod and need to be parsed by
atomicapp</div>
<div 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>
</blockquote>
<div><br>
</div>
<div>
<div class="gmail_default" style="font-size:small">One
more item: since the oc command won't be aware of the
params until the remote pod is run I think we need to
bake these into the image metadata and extend
openshift to display these. Otherwise the end-user
will not know what the params are. Something like
this in the Dockerfile:</div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<div class="gmail_default" style="font-size:small">LABEL
io.openshift.my-app.parameter.FOO.default="bar" \</div>
<div class="gmail_default">
io.openshift.my-app.parameter.FOO.description="Some
foo for your bar"</div>
<br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">
<div style="font-size:small"><br>
</div>
<div 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 style="font-size:small"><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Container-tools mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Container-tools@redhat.com">Container-tools@redhat.com</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/container-tools">https://www.redhat.com/mailman/listinfo/container-tools</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Container-tools mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Container-tools@redhat.com">Container-tools@redhat.com</a>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/container-tools">https://www.redhat.com/mailman/listinfo/container-tools</a>
</pre>
</blockquote>
<br>
</body>
</html>