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

Add custom playbooks to manage Dell firmware #1087

Open
wants to merge 1 commit into
base: stackhpc/2023.1
Choose a base branch
from

Conversation

priteau
Copy link
Member

@priteau priteau commented Jun 4, 2024

No description provided.

@priteau priteau requested a review from MaxBed4d June 4, 2024 12:50
@priteau priteau self-assigned this Jun 4, 2024
@priteau priteau requested a review from a team as a code owner June 4, 2024 12:50
@markgoddard
Copy link
Contributor

IMHO it's time to stop pushing features into yoga. Also wondering if we need a stackhpc.dell collection for this kind of thing?

@priteau priteau changed the base branch from stackhpc/yoga to stackhpc/2023.1 June 5, 2024 12:58
@priteau
Copy link
Member Author

priteau commented Jun 5, 2024

I rebased to target Antelope.

Then update the ``dell_drm_repo`` variable in ``drac-firmware-update.yml`` if
required.

Manually adding and update file
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this section an alternative to the Updating the Repo section, or is this part required after it?
If it is an alternative to the previous section, it may be worth mentioning it in the title as an "(alternative method)", if it is not an alternative it may be worth specifying in the title what files they are specifically updating to help differentiate between them.

Copy link
Contributor

@MaxBed4d MaxBed4d left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, and the way it has been documented makes it relatively easy to grasp. I would like to test this out to make sure it does work as intended, unless it already has.

My only real suggestion would be to add a short set of numbered steps somewhere in the docs to outline which steps should be done in which order to prevent some of the ''note:'' warnings e.g. ''The playbook will likely fail with an error if the iDRAC firmware is being updated''.

vars:
# Run with ``-e dell_drm_apply_update=true`` to apply the firmware updates.
dell_drm_apply_update: False
dell_drm_address: "https://{{ oob_oc_net_name | net_ip(inventory_hostname=groups['seed'][0]) }}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The seed is assumed here when previously the criteria was "Choose a host where it won't conflict with another service". I think you should either add a dell_drm group or make it clear that the seed is the default host.

.. code-block:: bash

docker volume create dell_firmware
docker run --detach -v dell_firmware:/dell_firmware --name dell-drm --network host --restart always rockylinux:9.3 sleep infinity
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a lot of manual steps here just to set up the containers properly. Would it be possible to just move everything to a script?

Copy link
Contributor

@Alex-Welsh Alex-Welsh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, needs a release note

@Alex-Welsh Alex-Welsh added enhancement New feature or request antelope Targets the Antelope OpenStack release labels Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
antelope Targets the Antelope OpenStack release enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants