[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: AW: Comment on #TOSCA Simple Profile in YAML v1.3
To keep it short:
[1]
https://docs.openstack.org/api-ref/network/v2/?expanded=create-port-detail#ports [2]
https://docs.openstack.org/api-ref/compute/?expanded=create-server-detail#create-server Von: Vo Hoang, Tri Hi Chris, Actually the use case is as simple as: “A user wants to spawn one Compute node in a given Network with one fixed private IP address”. From my point of view, TOSCA should describe a desired topology of a user as it is. It would be unexpected for the users to see their booted compute node having two NICs (eth0 and eth1)
but in the topology they describe only one Port. > In the current Compute node type, we don’t explicitly model that interface using a Port, but rather just track the allocated IP address. But in Section 8.4.3.2 (Use case: Data Traffic network), the figure shows a scenario whereby users can define eth0 on the VM for their data network explicitly. Also, it is important to model and control the lifecycle of all interfaces explicitly. This makes sure that a compute node reaches a desired state (i.e., has fixed IP addresses). Otherwise,
a restart of a compute node results in a different IP address, and opened to security threats (e.g., causes disruption of availability or the automatic configuration of IP addresses enables an attacker to divert traffic or impair communication). > Perhaps you can share your use case (or we can discuss when you join the TC). This process will take a while… I hope soon. Best, Tri Von: Chris Lauwers <lauwers@ubicity.com>
Hi Vo, Thanks for explaining your use case. From your explanation, I assume you want the Port B for your Compute A to correspond to eth0 (i.e. the first network interface on the VM). Presumably, this network interface will be
used to connect to a “management network” that can also be used by the orchestrator to communicate with the Compute node. In the current Compute node type, we don’t explicitly model that interface using a Port, but rather just track the allocated IP address.
It seems you have a use case in mind for why you want to explicitly model the management address of a Compute host using a Port. Perhaps you can share your use case (or we can discuss when you join the TC). Thanks again for your input. Chris From:
Tri.Vo-Hoang@t-systems.com <Tri.Vo-Hoang@t-systems.com>
Dear Chris Lauwers, thank you for answering my comment.
To create Compute A, the orchestration engine requires either a network-uuid, or a port-uuid [1].
If the relationship is reverse (i.e., Compute A “depends on” Port B), then it is what OpenStack users normally do: create a Port, then create a Compute with the Port [2].
[1]
https://docs.openstack.org/api-ref/compute/#create-server [2]
https://computingforgeeks.com/create-openstack-instance-with-a-fixed-ip-address/ Best regards, Vo Von: Chris Lauwers <lauwers@ubicity.com>
Hi Vo, We’re excited to hear about your efforts to build a TOSCA-based orchestration engine. With respect to your questions:
These are good comments, and we encourage T-Systems to consider joining the TOSCA TC. It would allow you to participate in the technical discussion where these types of design alternatives are discussed. Best regards, Chris Lauwers From:
tosca-comment@lists.oasis-open.org <tosca-comment@lists.oasis-open.org>
On Behalf Of Tri.Vo-Hoang@t-systems.com Dear members of the TOSCA TC, We are trying to follow the profile v1.3 precisely to implement a TOSCA orchestration engine for our public cloud provider. Currently, we have the following comments:
Kind Regards, Vo T-SYSTEMS INTERNATIONAL GMBH Open Telekom Cloud Delivery – Senior Public Cloud Architect Hoang Tri Vo, PhD Publications:
https://dblp.org/pers/hd/v/Vo:Tri_Hoang Linkedin:
https://www.linkedin.com/in/tri-hoang-vo-395819aa/ Legal notice: please see
www.t-systems.com/compulsory-statement Big changes start small – conserve resources by not printing every e-mail. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]