Thanks! Nothing significant yet, just various Ansible hello-world-like scenarios. There are various challenges ahead: Generating "hosts" for Ansible. I think this might require a special Ansible profile with a "Host" capability. Otherwise it's hard to see how Ansible would know. Or maybe metadata that can be applied to any capability type or node type? Attributes. I think these will have to be set by an explicit Ansible role. Graph-iteration (this is a more general problem in Ansible, which has overly simple loops). On Thu, Mar 11, 2021 at 1:57 AM Tamburri, Damian <
d.a.tamburri@tue.nl > wrote: Ciao Tal! This looks awesome! Are there specific scenarios in which you tested this? D. Damian A. Tamburri, Ph.D. Associate Professor TU/e - JADS -Â
https://www.jads.nl/ Sint Janssingel 92, sâHertogenbosch Room 2.18, 2nd Floor Email:
d.a.tamburri@tue.nl Cell: +39 3491279924 Web:Â
https://www.researchgate.net/profile/Damian_Tamburri Executive Director, Jheronimus AcademyÂData & Engineering (JADE) Lab Secretary, OASIS âTopology andÂOrchestration for Cloud ApplicationsâÂ(TOSCA) Standard Technical Committee Secretary, IFIP - WG 2.14 / 6.12 / 8.10 onÂService-Oriented Systems Associate Editor & Online PresenceÂDirector, ACM Transactions on SoftwareÂEngineering & Methodology (TOSEM) On 10 Mar 2021, at 22:34, Tal Liron <
tliron@redhat.com > wrote: Wouldn't it be nice if your Ansible playbooks could consume TOSCA? Well, now they can. This is still a work-in-progress, but Puccini now includes an Ansible module for TOSCA (which in turn relies on the Python wrapper). Here's an example of a simple playbook:
https://github.com/tliron/puccini/blob/main/examples/ansible/hello-world.yaml There's still much more on the TODO list for supporting various Ansible use cases, but even at this early stage there's a lot that's possible by simply iterating on resolved node templates and doing the usual Ansible stuff. Feedback most welcome!