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

feat: commission machines in New state by their PXC MAC #192

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

skatsaounis
Copy link
Collaborator

Fixes: #151

@skatsaounis skatsaounis force-pushed the commission-new-machines branch from 264f838 to c490e7f Compare June 17, 2024 08:08
@sempervictus
Copy link

sempervictus commented Jul 2, 2024

If we kick commissioning from tf, i think that we should be able to assign commissioning and test scripts such that machines are qualified for function and consistency - otherwise workflows gated by component qualification don't work requiring humans to recommission again after this seemingly enforced commissioning pass that doesn't actually "check the boxes" for QA.

Secondly, how does this work with manual power or temporarily inaccessible ready-state hosts? This seems to "take action on behalf of the user" vs being a state of resource induced by the user or a separate resource type entirely (ready, commissioned, deployed, broken, etc being either states of a resource or entire resources themselves)

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

Successfully merging this pull request may close these issues.

feat: maas_machine support commissioning for discovered machines
2 participants