Bare metal node N+1 redundancy
Bare metal node N+1 redundancy
This proposes high availability/
Metal Node N+1 Redundancy based on the blueprints
volume-
When a bare metal node is failed due to hardware problem or is likely to be failed due to a sign of hardware failure, this function allows to switch over the node safely to another bare metal node in
short time if the failed node is booted from a share file system such as
FC, FCoE, iSCSI, NFS and etc.
This function exposes an API for switching over and would have an
Ironic CLI such as "ironic host-evacuate-cold" which was borrowed from
"nova host-evacuate-
[1] https:/
[2] https:/
- Nov 9th, 2015, Naohirot:
Overall idea can be found in the following presentation slides P.60 - P.63.
"Ironic Towards Truly Open and Reliable, Eventually for Mission Critical"
http://
https:/
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Low
- Drafter:
- Naohiro Tamura
- Direction:
- Needs approval
- Assignee:
- Naohiro Tamura
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
Would this also be connected to "nova migrate"? (I think it should be).
This depends on quite a bit of work, but seems totally doable. Would like to see the spec.
// jroll 2015-10-15
Hi Naohiro, thanks for the proposal. We're moving from using blueprints to track features to rfe bugs. I've filed one for your change - https:/
Please track further work there using Closes-Bug, Partial-Bug or Related-Bug in commit messages and use the RFE bug link in the proposed spec.
//vdrok 2015-12-15
Hi Vladyslav,
Thanks for taking care of the migration. I continue to work on the RFE bug report.
//naohiro 2015-12-16
Gerrit topic: https:/
Addressed by: https:/
Bare metal node N+1 redundancy
