Check key definition in TOSCA template and report incorrectly defined keys

Registered by Victor HU

Currently if the key is not properly defined, the translator will ignore it rather than report an error or warning. For example, a server instance should have a property named 'num_cpus', if it is spelled as 'num_cpu', an exception of missing required field will raise. If it is an optional property like 'description', the template can get parsed but the property is missing. So it's needed to validate the key definition as heat template parser does to see if it meets the TOSCA specification.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Victor HU
Direction:
Needs approval
Assignee:
Victor HU
Definition:
New
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Victor HU
Completed by
Victor HU

Related branches

Sprints

Whiteboard

(spzala) Hi Victor, we have this bp opened sometime back for a better validation need, https://blueprints.launchpad.net/heat-translator/+spec/tosca-validation I assume you are working on it already? Please feel free to merge you bp with it or you can keep it separate. Thanks!

Gerrit topic: https://review.openstack.org/#q,topic:bp/tosca-validation,n,z

Addressed by: https://review.openstack.org/104479
    Enhanced tosca validation

Addressed by: https://review.openstack.org/107575
    Enhanced tosca validation

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.