TOSCA translator is re-implementing HOT objects
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Heat Translator |
Confirmed
|
High
|
Ton Ngo | ||
Bug Description
In the current code of the TOSCA translator, there are HOT objects (e.g. parameters, outputs etc) being implemented which are already implemented in the Heat code base. We should really use those implementations in Heat for programmatically constructing templates instead of implementing those classes ourselves. Otherwise, there is a high risk of getting out of synch ... not talking about the duplicate work.
Especially there has been recent work by zaneb to introduct ResourceDefinition classes, and method to add/remove resource definitions to templates which seems like very useful code for TOSCA translator.
We should figure out how we can properly define the dependency on the Heat code base so that development works and test cases work. Once this work, we should refactor our code to use the Heat code.
| Ton Ngo (ton-i) wrote | #1 |
| Changed in heat-translator: | |
| status: | New → Confirmed |
| assignee: | nobody → Ton Ngo (ton-i) |
| Changed in heat-translator: | |
| importance: | Undecided → High |
| Bob Haddleton (bob-haddleton) wrote | #2 |
Good idea, especially with the new ResourceDefinition class. Zane has been factoring the Heat code to use this so it makes sense for us to do the same. We have to figure out how to pick up that class from the Heat code base instead of just copying it here.