-
Notifications
You must be signed in to change notification settings - Fork 117
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
Proposal for hot-update of resources (Instance / NIC / Disk) #761
Proposal for hot-update of resources (Instance / NIC / Disk) #761
Conversation
I miss a little bit a discussion around compatibility, transition, generally the stuff in #750. Is that because it's this one here is about an implementation proposal and the other ticket is expected "to be present in reader's mind"? |
2b3f712
to
4fe8c49
Compare
Co-authored-by: Madhav Bhargava <madhav.bhargava@sap.com>
/reviewed ok-to-test |
The diagram is still incomplete.
I think we don't need a diagram in this, as the proposal is quite descriptive and diagramatic details could be discussed once its picked up for implementation. |
I have removed the diagram as of now from this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
What this PR does / why we need it:
Proposal has been added to
docs/proposal
where we have talked about current drawbacks of machineClass (in context of tags specifically), and a way we could hot-update parameters for the resources MCM handles (VM,nics,disks). Hot-update means this fields would be updated for (VM, nics, disks) without any need to do any rolling update and create a new VM.Some examples are:
Which issue(s) this PR fixes:
Fixes #
Proposal for #635
Special notes for your reviewer:
Release note: