In openshift-ansible we've been working on tooling to create golden images and shift the model from running ansible on each provisioned host to creating hosts that bootstrap themselves when provided an API endpoint and a token. We'd like to explore publishing a Centos based Origin AMI so that people could use an existing image without even having to bake their own.
Should we coordinate this through either SIG Cloud or SIG PaaS or should we just go ahead and do it on our own for now and work to integrate with those SIGs in the future?
-- Scott
On 13/09/17 18:31, Scott Dodson wrote:
In openshift-ansible we've been working on tooling to create golden images and shift the model from running ansible on each provisioned host to creating hosts that bootstrap themselves when provided an API endpoint and a token. We'd like to explore publishing a Centos based Origin AMI so that people could use an existing image without even having to bake their own.
Should we coordinate this through either SIG Cloud or SIG PaaS or should we just go ahead and do it on our own for now and work to integrate with those SIGs in the future?
Happy to support this via the PaaS or the Cloud Insance SIG ( the Cloud SIG is infra focused, so more openstack ), we work the Cloud images via the Cloud Instance SIG.
we dont meet regularly however, so best to bring this up through the PaaS SIG meetings.
On Wed, Sep 13, 2017 at 10:31 AM, Scott Dodson sdodson@redhat.com wrote:
In openshift-ansible we've been working on tooling to create golden images and shift the model from running ansible on each provisioned host to creating hosts that bootstrap themselves when provided an API endpoint and a token. We'd like to explore publishing a Centos based Origin AMI so that people could use an existing image without even having to bake their own.
What are you adding to the base centos image? I'm wondering if this could be done w/ centos atomic.
Jason
Should we coordinate this through either SIG Cloud or SIG PaaS or should we just go ahead and do it on our own for now and work to integrate with those SIGs in the future?
-- Scott
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Wed, Sep 13, 2017 at 5:18 PM, Jason Brooks jbrooks@redhat.com wrote:
On Wed, Sep 13, 2017 at 10:31 AM, Scott Dodson sdodson@redhat.com wrote:
In openshift-ansible we've been working on tooling to create golden
images
and shift the model from running ansible on each provisioned host to creating hosts that bootstrap themselves when provided an API endpoint
and a
token. We'd like to explore publishing a Centos based Origin AMI so that people could use an existing image without even having to bake their own.
What are you adding to the base centos image? I'm wondering if this could be done w/ centos atomic.
Jason
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.
-- Scott
Should we coordinate this through either SIG Cloud or SIG PaaS or should
we
just go ahead and do it on our own for now and work to integrate with
those
SIGs in the future?
-- Scott
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Wed, Sep 13, 2017 at 5:27 PM, Scott Dodson sdodson@redhat.com wrote:
On Wed, Sep 13, 2017 at 5:18 PM, Jason Brooks jbrooks@redhat.com wrote:
On Wed, Sep 13, 2017 at 10:31 AM, Scott Dodson sdodson@redhat.com wrote:
In openshift-ansible we've been working on tooling to create golden
images
and shift the model from running ansible on each provisioned host to creating hosts that bootstrap themselves when provided an API endpoint
and a
token. We'd like to explore publishing a Centos based Origin AMI so that people could use an existing image without even having to bake their
own.
What are you adding to the base centos image? I'm wondering if this could be done w/ centos atomic.
Jason
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.
-- Scott
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.
https://github.com/openshift/openshift-ansible/blob/master/roles/openshift_n...
-- Scott
Should we coordinate this through either SIG Cloud or SIG PaaS or
should we
just go ahead and do it on our own for now and work to integrate with
those
SIGs in the future?
-- Scott
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 13/09/17 22:29, Scott Dodson wrote:
https://github.com/openshift/openshift-ansible/blob/master/roles/openshift_n...
what is the delivery mech ? are you looking at running ansible post-install to snapshot then clear out ? or is the aim here to refactor this into a kickstart ?
On Wed, Sep 13, 2017 at 5:50 PM, Karanbir Singh mail-lists@karan.org wrote:
On 13/09/17 22:29, Scott Dodson wrote:
roles/openshift_node/defaults/main.yml#L9-L52
what is the delivery mech ? are you looking at running ansible post-install to snapshot then clear out ? or is the aim here to refactor this into a kickstart ?
Our preference is to stick with ansible roles and reseal the image. Feedback we've got is that if someone wishes to customize the image they prefer to start with their own base image and customize on top of that so we'd like for them to be able to use the same ansible tooling we use to prepare an image for bootstrapping.
-- Scott
-- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel