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: RE: [tosca] [OASIS Issue Tracker] (TOSCA-255) Refactor NIC concept in Compute


Hi Luca, 

Using the normative types in Tosca, you wouldn't use Properties to model the volumes attached to a Compute node or the NICs connected to a Compute node. Instead, volumes and NICs are modeled as Node Templates in their own right and they establish relationships to the Compute node. The resulting configuration is described using a topology template containing multiple node templates, rather than by a single Compute node.

Using Port node templates specifically, you can model a Compute node that connects to multiple networks and assign one or more IP addresses to each Port. As stated before, the private_ip and public_ip attributes are just shortcuts to help with the simple case where a Compute node connects to only one network.

Chris


-----Original Message-----
From: tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org] On Behalf Of OASIS Issues Tracker
Sent: Thursday, June 11, 2015 7:34 AM
To: tosca@lists.oasis-open.org
Subject: [tosca] [OASIS Issue Tracker] (TOSCA-255) Refactor NIC concept in Compute

Luca Gioppo created TOSCA-255:
---------------------------------

             Summary: Refactor NIC concept in Compute
                 Key: TOSCA-255
                 URL: https://issues.oasis-open.org/browse/TOSCA-255
             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
          Issue Type: Improvement
          Components: Profile-YAML
            Reporter: Luca Gioppo
            Priority: Critical


The Compute needs a set of properties to enable libraries like JClouds or similar to create a complex VM: i.e. A VM with a specific service offerings (CPU+RAM) different volumes, 3 NIC linked to 3 different network offerings.
We need to have these expressed as properties.
The private_ip and public_ip are wrong concept not enough general to allow the generic deployment.




--
This message was sent by Atlassian JIRA
(v6.2.2#6258)

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 



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