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.
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.