@Kanagaraj, for #1 there is no 'outputs' section in the TOSCA template itself so translator can't create one. Bharath kindly run translator in Tacker env by adding outputs section in the TOSCA template and that will produce outputs in the main template
e.g. Adding outputs in the template as: policies:
- SP1:
type: tosca.policies.tacker.Scaling
targets: [VDU1, VDU2]
properties: increment: 1
cooldown: 120 min_instances: 1 max_instances: 3 default_instances: 2
outputs:
ip_address:
value: { get_attribute: [ VDU1, public_address ] }
will create outputs in the translated template as:
outputs:
ip_address:
value:
get_attr:
- VDU1
- networks
- private
- 0
@Kanagaraj, for #1 there is no 'outputs' section in the TOSCA template itself so translator can't create one. Bharath kindly run translator in Tacker env by adding outputs section in the TOSCA template and that will produce outputs in the main template tacker. Scaling
increment: 1
min_ instances: 1
max_ instances: 3
default_ instances: 2
e.g. Adding outputs in the template as: policies:
- SP1:
type: tosca.policies.
targets: [VDU1, VDU2]
properties:
cooldown: 120
outputs:
ip_address:
value: { get_attribute: [ VDU1, public_address ] }
will create outputs in the translated template as:
outputs:
ip_address:
value:
get_attr:
- VDU1
- networks
- private
- 0
Hope makes sense.