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

Refresh the BMH v1beta1 design based on recent developments #509

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dtantsur
Copy link
Member

  • BMO has changed the default ChecksumType to auto without waiting for
    v1beta1, so now remove the explicit MD5 type instead.

  • Remove support for VDI and VMDK disk formats. They were disabled in
    the Ironic image validation fixes, and nobody has complained so far.
    These formats have never been tested by the Ironic or Metal3
    communities.

  • Introduce an explicit InspectionMode similar to AutomatedCleaningMode.
    It will replace setting inspect.metal3.io to "disabled" with a proper
    API and pave the way to eventually add a Redfish-based option.

  • Replace UserData, MetaData and NetworkData with UserDataName,
    MetaDataName and NetworkDataName. It has been discovered that allowing
    secrets from a different namespace poses a security issue, so the
    Namespace field is not functional any more.

Signed-off-by: Dmitry Tantsur [email protected]

- BMO has changed the default ChecksumType to auto without waiting for
  v1beta1, so now remove the explicit MD5 type instead.

- Remove support for VDI and VMDK disk formats. They were disabled in
  the Ironic image validation fixes, and nobody has complained so far.
  These formats have never been tested by the Ironic or Metal3
  communities.

- Introduce an explicit InspectionMode similar to AutomatedCleaningMode.
  It will replace setting inspect.metal3.io to "disabled" with a proper
  API and pave the way to eventually add a Redfish-based option.

- Replace UserData, MetaData and NetworkData with UserDataName,
  MetaDataName and NetworkDataName. It has been discovered that allowing
  secrets from a different namespace poses a security issue, so the
  Namespace field is not functional any more.

Signed-off-by: Dmitry Tantsur <[email protected]>
@metal3-io-bot metal3-io-bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Mar 13, 2025
@elfosardo
Copy link
Member

/approve

@metal3-io-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: elfosardo
Once this PR has been reviewed and has the lgtm label, please ask for approval from dtantsur. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@elfosardo
Copy link
Member

/lgtm
always forget I'm not an approver here '^__^

@metal3-io-bot metal3-io-bot added the lgtm Indicates that a PR is ready to be merged. label Mar 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants