Validate inputs when creating a baymodel
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Magnum should not create a baymodel if the given image, flavor, keypair, and/or external network id is invalid. For example, the command below should not pass.
$ magnum baymodel-create --name testbaymodel --image-id invalidimage \
> --keypair-
> --external-
> --dns-nameserver 8.8.8.8 --flavor-id invalidflavor
+------
| Property | Value |
+------
| apiserver_port | None |
| uuid | 37230ef5-
| external_network_id | 5b5da68c-
| created_at | 2015-01-
| updated_at | None |
| image_id | invalidimage |
| keypair_id | invalidkey |
| flavor_id | invalidflavor |
| dns_nameserver | 8.8.8.8 |
| name | testbaymodel |
+------
summary: |
- Valid input when creating a baymodel + Validate input when creating a baymodel |
summary: |
- Validate input when creating a baymodel + Validate inputs when creating a baymodel |
Changed in magnum: | |
assignee: | nobody → Madhuri Kumari (madhuri-rai07) |
Changed in magnum: | |
status: | Confirmed → Invalid |
status: | Invalid → Confirmed |
Changed in magnum: | |
milestone: | none → mitaka-1 |
Changed in magnum: | |
assignee: | Madhuri Kumari (madhuri-rai07) → nobody |
Changed in magnum: | |
assignee: | nobody → rajiv (rajiv-kumar) |
Changed in magnum: | |
assignee: | rajiv (rajiv-kumar) → nobody |
The downside of validating on baymodel-create, is that later a user could come along and delete the networks, keypairs, flavors, or image, resulting in a baymodel that is still invalid.
Perhaps what is needed is a baymodel-validate ReST api call, which gets called automatically as part of the baymodel-create functionality, but is also callable later if the user runs into trouble running their baymodel.
I agree the current state of things makes debugging difficult and requires looking at the heat orchestration results, which most users may not be comfortable with.