search

xlab-si / xopera-opera

xOpera orchestrator compliant with TOSCA YAML v1.3 in the making
https://xlab-si.github.io/xopera-docs/
Apache License 2.0
35 stars 14 forks source link

Cannot use an unset value: public_address #245

Closed abitrolly closed 2 years ago

abitrolly commented 2 years ago

opera fails if service.yaml for Compute doesn't specify public_address as attribute.

Cannot use an unset value: public_address

I expected to set only properties, but such property is invalid. I am setting the Ansible host and port from playbook, so it counter intuitive that opera fails to read this attribute even if it is unused. In fact, I would expect it to set it automatically from Ansible host if nothing else is supplied.

anzoman commented 2 years ago

Hi, @abitrolly can you post here your full TOSCA CSARs - i.e., all TOSCA templates and Ansible playbooks you're using to deploy?

abitrolly commented 2 years ago

It is a contract work, so I can not share it yet.

anzoman commented 2 years ago

@abitrolly aha okay can you than recreate this beaviour with some other TOSCA template and Ansible playbook?

anzoman commented 2 years ago

@abitrolly did you manage to overcome the issue?

abitrolly commented 2 years ago

No. It turned to be a lot of hacks on top of each other. Something finally worked, but I don't have the motivation to redo the thing from scratch. The experiment is simple - try to use tosca.nodes.Compute in either types definition or in instance, but I am drained. I could probably try to run copyrighted examples, but again no motivation. If you can't repeat this, might be some mistake on my side.