hi,
As we build and produce an increasing number of images that people can directly consume, eg. AMI's or Vagrant or docker or openstack or opennebula images etc, I'm keen to add a mirrorlist tag to the url that allows us to better serve content into those areas.
Specially since not all the images are built with exclusive centos linux distro content and in some cases, we might need to consider things like cloud-init and cloud-utils to be essentially base-os content for those roles.
This would mean the mirrorlist url will change from : mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&rep...
to mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&rep... or mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&rep...
to indicate the generic cloud image, or the ami's
thoughts ?
On 08/13/2014 07:35 AM, Karanbir Singh wrote:
hi,
As we build and produce an increasing number of images that people can directly consume, eg. AMI's or Vagrant or docker or openstack or opennebula images etc, I'm keen to add a mirrorlist tag to the url that allows us to better serve content into those areas.
Specially since not all the images are built with exclusive centos linux distro content and in some cases, we might need to consider things like cloud-init and cloud-utils to be essentially base-os content for those roles.
This would mean the mirrorlist url will change from : mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&rep...
to mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&rep... or mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&rep...
to indicate the generic cloud image, or the ami's
thoughts ?
I don't have a problem with this, it allows us to much more easily serve different BASE content for different images, etc.
This (or something based on the same concept) might also be useful for SIGs in the future as well.