OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (TOSCA-176) Add connectivity ability to Compute

Moshe Elisha created TOSCA-176:

             Summary: Add connectivity ability to Compute
                 Key: TOSCA-176
                 URL: https://issues.oasis-open.org/browse/TOSCA-176
             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
          Issue Type: Improvement
          Components: Profile-YAML
            Reporter: Moshe Elisha

This issue is suggesting to add the ability for the TOSCA container to connect to a Compute in order to manage it and invoke life-cycle operations.

In order to invoke life-cycle operations (such as start, stop, uninstall) we are missing the connectivity information from the tosca.nodes.Compute.

We would like to think of a way to add connectivity params to a compute such as :username, keypair and script working directory.

We have two options that we thought about to express the additional information. One is based on node type inheritance and the other is based on connectivity information as a capability.

In NFV use-cases, we do see a need for a Compute that has no connectivity information - for example, the Compute might be an appliance VM (for example, firewall) that has everything built-in inside the image and there is no need or way to connect to that VM.

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]