<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 13, 2017 at 5:27 PM, Scott Dodson <span dir="ltr"><<a href="mailto:sdodson@redhat.com" target="_blank">sdodson@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="gmail-">On Wed, Sep 13, 2017 at 5:18 PM, Jason Brooks <span dir="ltr"><<a href="mailto:jbrooks@redhat.com" target="_blank">jbrooks@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span>On Wed, Sep 13, 2017 at 10:31 AM, Scott Dodson <<a href="mailto:sdodson@redhat.com" target="_blank">sdodson@redhat.com</a>> wrote:<br>
> In openshift-ansible we've been working on tooling to create golden images<br>
> and shift the model from running ansible on each provisioned host to<br>
> creating hosts that bootstrap themselves when provided an API endpoint and a<br>
> token. We'd like to explore publishing a Centos based Origin AMI so that<br>
> people could use an existing image without even having to bake their own.<br>
<br>
</span>What are you adding to the base centos image? I'm wondering if this<br>
could be done w/ centos atomic.<br>
<span class="gmail-m_-7931063668009217401HOEnZb"><font color="#888888"><br>
Jason<br></font></span></blockquote><div><br></div></span><div>Right now the bootstrapping process is RPM centric, we'd like to add bootstrapping support for container based installs once we revisit our containerized architecture.</div><div><br></div><div>--</div><div>Scott</div></div></div></div></blockquote><div><br></div><div>Sorry, I just realized I didn't actually answer your question. We're installing all of the origin node rpm and it's entire dependency chain.</div><div><br></div><div><a href="https://github.com/openshift/openshift-ansible/blob/master/roles/openshift_node/defaults/main.yml#L9-L52">https://github.com/openshift/openshift-ansible/blob/master/roles/openshift_node/defaults/main.yml#L9-L52</a><br></div><div><br></div><div>--</div><div>Scott</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="gmail-"><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-m_-7931063668009217401HOEnZb"><font color="#888888">
</font></span><span class="gmail-m_-7931063668009217401im gmail-m_-7931063668009217401HOEnZb"><br>
><br>
> Should we coordinate this through either SIG Cloud or SIG PaaS or should we<br>
> just go ahead and do it on our own for now and work to integrate with those<br>
> SIGs in the future?<br>
><br>
> --<br>
> Scott<br>
><br>
</span><div class="gmail-m_-7931063668009217401HOEnZb"><div class="gmail-m_-7931063668009217401h5">> ______________________________<wbr>_________________<br>
> CentOS-devel mailing list<br>
> <a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a><br>
> <a href="https://lists.centos.org/mailman/listinfo/centos-devel" rel="noreferrer" target="_blank">https://lists.centos.org/mailm<wbr>an/listinfo/centos-devel</a><br>
><br>
______________________________<wbr>_________________<br>
CentOS-devel mailing list<br>
<a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a><br>
<a href="https://lists.centos.org/mailman/listinfo/centos-devel" rel="noreferrer" target="_blank">https://lists.centos.org/mailm<wbr>an/listinfo/centos-devel</a><br>
</div></div></blockquote></span></div><br></div></div>
</blockquote></div><br></div></div>