Extend Standard Images Standard To Move Away From Fixed Names

by ADMIN 62 views

Introduction

In the current stable version of the standard images, a specific naming scheme is enforced for each mandatory and recommended image, along with a certain source URL. However, this fixed name is undesirable, except for the special case of the CAPI image, as it duplicates images and confuses customers. Moreover, Glance, the OpenStack service responsible for image managing, has viable filtering capabilities that can be utilized. In this article, we will explore the possibility of extending the standard images to move away from fixed names and provide a more flexible and efficient way of image management.

The Current Standard

The current standard, scs-0104-v1, enforces a specific naming scheme for each mandatory and recommended image. This includes a certain source URL, which can be restrictive and limiting. The current standard is as follows:

  • Mandatory images: os_distro=X, os_version=Y, and os_original=true
  • Recommended images: name matches a specific regex
  • Mandatory images: image_source starting with one of XYZ

The Proposed Change

The proposed change aims to extend the standard images to move away from fixed names and provide a more flexible and efficient way of image management. The proposed changes are as follows:

  • An image with either os_distro=X, os_version=Y, and os_original=true (used for stock OS images such as Ubuntu 24.04 or Debian 12) or name matches a specific regex (used for special case of CAPI)
  • MAY, SHOULD, or MUST be present (corresponding to status=optional, recommended, or mandatory, respectively)
  • If present, it MUST have image_source starting with one of XYZ

Justification for the Change

The added capability will not be activated by existing YAML files, so their meaning will not change. Changing the YAML file in a way that breaks compliance is not possible for a stable version of a certificate scope. In other words, whatever test subject complies with the current v1 will also comply with the updated v1.

Benefits of the Proposed Change

The proposed change will provide several benefits, including:

  • Flexibility: The proposed change will allow for more flexibility in image management, as it will no longer be restricted by a specific naming scheme.
  • Efficiency: The proposed change will improve efficiency, as it will reduce the need for duplicating images and will make it easier to manage images.
  • Simplification: The proposed change will simplify the image management process, as it will reduce the complexity of the current standard.

Definition of Done

The definition of done for this proposal is as follows:

  • Confirm that selecting images using the os_X properties is readily possible with Glance.
  • Write a blog post explaining how this image selection works for end users.
  • Extend the standard.
  • Adapt the check script.
  • Change relevant YAML file so names are no longer enforced for stock OS images.

Conclusion

In conclusion, the proposed change to extend the standard images to move away from fixed names will provide several benefits, including flexibility, efficiency, and simplification. The added capability will not be activated by existing YAML files, so their meaning will not change. Changing the YAML file in a way that breaks compliance is not possible for a stable version of a certificate scope. Therefore, we can justify updating v1 for the proposed change.

Implementation Plan

To implement the proposed change, we will follow the definition of done outlined above. This will involve the following steps:

Step 1: Confirm that selecting images using the os_X properties is readily possible with Glance

We will confirm that selecting images using the os_X properties is readily possible with Glance. This will involve testing the functionality of Glance to ensure that it can select images based on the os_X properties.

Step 2: Write a blog post explaining how this image selection works for end users

We will write a blog post explaining how this image selection works for end users. This will involve creating a clear and concise explanation of the proposed change and how it will benefit end users.

Step 3: Extend the standard

We will extend the standard to include the proposed changes. This will involve updating the standard to reflect the new image management process.

Step 4: Adapt the check script

We will adapt the check script to reflect the proposed changes. This will involve updating the check script to ensure that it can validate the new image management process.

Step 5: Change relevant YAML file so names are no longer enforced for stock OS images

We will change the relevant YAML file so that names are no longer enforced for stock OS images. This will involve updating the YAML file to reflect the new image management process.

Timeline

The timeline for implementing the proposed change is as follows:

  • Week 1-2: Confirm that selecting images using the os_X properties is readily possible with Glance.
  • Week 3-4: Write a blog post explaining how this image selection works for end users.
  • Week 5-6: Extend the standard.
  • Week 7-8: Adapt the check script.
  • Week 9-10: Change relevant YAML file so names are no longer enforced for stock OS images.

Resources

The resources required to implement the proposed change are as follows:

  • Personnel: 1-2 people with expertise in image management and standardization.
  • Equipment: None.
  • Software: Glance, YAML editor.

Risks and Assumptions

The risks and assumptions associated with the proposed change are as follows:

  • Risk 1: The proposed change may not be compatible with existing systems.
  • Assumption 1: The proposed change will not break compliance with existing standards.
  • Risk 2: The proposed change may require significant changes to the check script.
  • Assumption 2: The proposed change will improve efficiency and simplify the image management process.

Conclusion

Introduction

In our previous article, we discussed the proposal to extend the standard images to move away from fixed names. This change aims to provide a more flexible and efficient way of image management, while also simplifying the process. In this article, we will answer some of the frequently asked questions related to this proposal.

Q: What is the current standard for image management?

A: The current standard for image management is scs-0104-v1, which enforces a specific naming scheme for each mandatory and recommended image. This includes a certain source URL, which can be restrictive and limiting.

Q: Why do we need to change the current standard?

A: The current standard is restrictive and limiting, and it does not provide enough flexibility for image management. By extending the standard to move away from fixed names, we can provide a more flexible and efficient way of image management, while also simplifying the process.

Q: How will the proposed change affect existing systems?

A: The proposed change will not break compliance with existing standards. The added capability will not be activated by existing YAML files, so their meaning will not change. Changing the YAML file in a way that breaks compliance is not possible for a stable version of a certificate scope.

Q: What are the benefits of the proposed change?

A: The proposed change will provide several benefits, including:

  • Flexibility: The proposed change will allow for more flexibility in image management, as it will no longer be restricted by a specific naming scheme.
  • Efficiency: The proposed change will improve efficiency, as it will reduce the need for duplicating images and will make it easier to manage images.
  • Simplification: The proposed change will simplify the image management process, as it will reduce the complexity of the current standard.

Q: How will the proposed change be implemented?

A: The proposed change will be implemented in the following steps:

  1. Confirm that selecting images using the os_X properties is readily possible with Glance: We will confirm that selecting images using the os_X properties is readily possible with Glance.
  2. Write a blog post explaining how this image selection works for end users: We will write a blog post explaining how this image selection works for end users.
  3. Extend the standard: We will extend the standard to include the proposed changes.
  4. Adapt the check script: We will adapt the check script to reflect the proposed changes.
  5. Change relevant YAML file so names are no longer enforced for stock OS images: We will change the relevant YAML file so that names are no longer enforced for stock OS images.

Q: What are the resources required to implement the proposed change?

A: The resources required to implement the proposed change are as follows:

  • Personnel: 1-2 people with expertise in image management and standardization.
  • Equipment: None.
  • Software: Glance, YAML editor.

Q: What are the risks and assumptions associated with the proposed change?

A: The risks and assumptions associated with the proposed change are as follows:

  • Risk 1: The proposed change may not be compatible with existing systems.
  • Assumption 1: The proposed change will not break compliance with existing standards.
  • Risk 2: The proposed change may require significant changes to the check script.
  • Assumption 2: The proposed change will improve efficiency and simplify the image management process.

Conclusion

In conclusion, the proposed change to extend the standard images to move away from fixed names will provide several benefits, including flexibility, efficiency, and simplification. The added capability will not be activated by existing YAML files, so their meaning will not change. Changing the YAML file in a way that breaks compliance is not possible for a stable version of a certificate scope. Therefore, we can justify updating v1 for the proposed change.

Frequently Asked Questions

  • Q: What is the current standard for image management?
    • A: The current standard for image management is scs-0104-v1.
  • Q: Why do we need to change the current standard?
    • A: The current standard is restrictive and limiting, and it does not provide enough flexibility for image management.
  • Q: How will the proposed change affect existing systems?
    • A: The proposed change will not break compliance with existing standards.
  • Q: What are the benefits of the proposed change?
    • A: The proposed change will provide several benefits, including flexibility, efficiency, and simplification.

Glossary

  • Glance: The OpenStack service responsible for image managing.
  • YAML: A human-readable serialization format commonly used for configuration files.
  • Certificate scope: A set of rules and constraints that define the scope of a certificate.
  • Image management: The process of managing and maintaining images, including creating, updating, and deleting them.

References