Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use GCE OS image families to get latest image version #136

Open
mbrukman opened this issue Sep 15, 2017 · 1 comment
Open

Use GCE OS image families to get latest image version #136

mbrukman opened this issue Sep 15, 2017 · 1 comment

Comments

@mbrukman
Copy link
Member

provider/src/main/resources/com/cloudera/director/google/google.conf includes the following snippet:

google {
  compute {
    imageAliases {
      centos6 = "https://www.googleapis.com/compute/v1/projects/centos-cloud/global/images/centos-6-v20160526",
      rhel6 = "https://www.googleapis.com/compute/v1/projects/rhel-cloud/global/images/rhel-6-v20160511"
    }
[...]

which is hard-coding a specific image versions of CentOS 6 and RHEL 6, respectively, but both are from 2016. They're both quite old, so they should be updated to newer versions. However, it does not need to be manual work every time: using image families, one can get the benefit of these image aliases always pointing to the latest version, without having to have an explicit alias in such a configuration:

Image families simplify the process of managing images in your project by grouping related images together and making it easy to roll forward and roll back between specific image versions. An image family always points to the latest version of an image that is not deprecated. Most public images are grouped into an image families. For example, the debian-8 image family in the debian-cloud project always points to the most recent Debian 8 image.

@jadair-cloudera
Copy link
Contributor

Looks like a great improvement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants