This is where the execution plugin decides whether to run locally or remotely (ssh): https://github.com/apache/incubator-ariatosca/blob/0.1.1/aria/orchestrator/execution_plugin/instantiation.py#L42
This is indeed related to the "host" role definition. Here you can see the assignment of the "host" role to the Compute type: https://github.com/apache/incubator-ariatosca/blob/1e883c57abb733b10e13f0b7005cf564886d3fb1/extensions/aria_extension_tosca/profiles/tosca-simple-1.0/nodes.yaml#L63 Ran On Wed, Sep 6, 2017 at 10:07 AM, D Jayachandran <[email protected] > wrote: > Hi, > > I just noticed the "role" attribute is added for different "capability" > and "node" types in ARIA profiles. There is no such role with the TOSCA > spec. > Why is this been added in the profiles ? What is the use of them ? > > I faced an issue when I run a local script as part of the Interface > operation. The script was provided to the execution plugin as > "run_script_with_ssh" rather than "run_script_locally". > The "role" seemed to have a saying on deciding this. Based on this role a > host is being added to any node instance. With the host being set a script > is configured either as " run_script_with_ssh" rather than > "run_script_locally". > > So I want to understand under which cicumstances is a host being added to > a node and which decided if the script execution is local or ssh ? > > > Regards, > DJ >
