Email this issue
Send issue summary in email
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Physical Server information should be tracked with specific status for them. A minimalistic status list is:
1) NOT READY
2) READY
Specifically, when the physical server transits from READY to NOT_READY, AbiCloud should trigger a chain of events that modifies the status of the Virtual Appliances contained in that physical servers.
|
|
Description
|
Physical Server information should be tracked with specific status for them. A minimalistic status list is:
1) NOT READY
2) READY
Specifically, when the physical server transits from READY to NOT_READY, AbiCloud should trigger a chain of events that modifies the status of the Virtual Appliances contained in that physical servers. |
Show » |
Sort Order:
|
Improvement
Closed
Critical
Changes in the status of physical servers should propagate status changes in the Virtual Servers