| 2016-09-21 12:33:17 |
Sahdev Zala |
bug |
|
|
added bug |
| 2016-09-21 12:33:25 |
Sahdev Zala |
heat-translator: assignee |
|
Sahdev Zala (spzala) |
|
| 2016-09-21 12:40:32 |
Sahdev Zala |
description |
By default the private network is named 'private' and that's how heat-translator translates to produce output with get_attr function in the translated template: e.g.
get_attr: [my_instance, networks, private, 0]
This mapping happens for TOSCA Compute's private_address attribute.
However if user has a private network with a name that's not 'private' then translated template won't produce any output because there is no 'private' named network.
The solution could be to ask user to provide the name of network as input to the translator. |
By default the private network is named 'private' and that's how heat-translator translates to produce output with get_attr function in the translated template: e.g.
get_attr: [my_instance, networks, private, 0]
This mapping happens for TOSCA Compute's private_address attribute.
However if user has a private network with a name that's not 'private' then translated template won't produce any output because there is no 'private' named network.
The solution could be to ask user to provide the name of network as input to the translator.
If network is provide in the template then should set accordingly instead of private. |
|
| 2016-09-29 13:09:06 |
Sahdev Zala |
heat-translator: assignee |
Sahdev Zala (spzala) |
|
|
| 2016-09-29 13:09:57 |
Sahdev Zala |
description |
By default the private network is named 'private' and that's how heat-translator translates to produce output with get_attr function in the translated template: e.g.
get_attr: [my_instance, networks, private, 0]
This mapping happens for TOSCA Compute's private_address attribute.
However if user has a private network with a name that's not 'private' then translated template won't produce any output because there is no 'private' named network.
The solution could be to ask user to provide the name of network as input to the translator.
If network is provide in the template then should set accordingly instead of private. |
By default the private network is named 'private' and that's how heat-translator translates to produce output with get_attr function in the translated template: e.g.
get_attr: [my_instance, networks, private, 0]
This mapping happens for TOSCA Compute's private_address attribute.
However if user has a private network with a name that's not 'private' then translated template won't produce any output because there is no 'private' named network.
The solution could be to ask user to provide the name of network as input to the translator. |
|
| 2016-09-29 13:17:41 |
Sahdev Zala |
description |
By default the private network is named 'private' and that's how heat-translator translates to produce output with get_attr function in the translated template: e.g.
get_attr: [my_instance, networks, private, 0]
This mapping happens for TOSCA Compute's private_address attribute.
However if user has a private network with a name that's not 'private' then translated template won't produce any output because there is no 'private' named network.
The solution could be to ask user to provide the name of network as input to the translator. |
By default the private network is named 'private' and that's how heat-translator translates to produce output with get_attr function in the translated template: e.g.
get_attr: [my_instance, networks, private, 0]
This mapping happens for TOSCA Compute's private_address attribute.
However if user has a private network with a name that's not 'private' then translated template won't produce any output because there is no 'private' named network.
The solution could be to programmatically find private network name an instance is associated with or ask user to provide the name of network as input to the translator. |
|
