[ICN-124] Validation mechanism before assigning VM to a cluster Created: 18/Sep/19 Updated: 15/Oct/19 |
|
| Status: | To Do |
| Project: | Integrated Cloud Native NFV |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Medium |
| Reporter: | ramamani yeleswarapu | Assignee: | ramamani yeleswarapu |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | Metal3 Baremetal Operator in ICN Stack |
| Sprint: | ICN Sprint 5 |
| Story Points: | 4 |
| Description |
|
Once VM IP addresses are available, before creating hosts.ini, there needs to be a validation mechanism that the VM is not already deployed. |
| Comments |
| Comment by ramamani yeleswarapu [ 02/Oct/19 ] |
|
This will be pushed to the backlog as this has to be done after the latest bpa code merges and the Virtlet VM support code merges. |