Hi Maopeng
TOSCA orchestrators will usually skip an operation that don’t have an
implementation.
You can also associate the cloudinit user-data script with any TOSCA operation
including the create operation.
Below is the operation definition in a node template:
<operation_name>:
description: <operation_description>
implementation:
primary: <implementation_artifact_name>
dependencies:
- <list_of_dependent_artifact_names>
inputs:
<property_assignments>
-Steve
From: [email protected] [mailto:[email protected]]
Sent: Tuesday, March 20, 2018 11:19 PM
To: Steve Baillargeon <[email protected]>
Cc: [email protected]; [email protected]
Subject: 答复: RE: [onap-discuss] 答复: RE: [model][vCPE] Things missing in Onap
Tosca DM?
Hi Steve
As I know the vCPE case requirement of cloudinit user scripts is implimented
via openstack api(vm create()).
In the Tosca configure standard process, the configure() will be after the
create(). I think as properties of Vdu.compute maybe is a good selection.
[cid:[email protected]]
BR
Maopeng
原始邮件
发件人：SteveBaillargeon
<[email protected]<mailto:[email protected]>>
收件人：张茂鹏10030173;[email protected]
<[email protected]<mailto:[email protected]>>
抄送人：[email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>>
日 期 ：2018年03月20日 22:56
主 题 ：RE: [onap-discuss] 答复: RE: [model][vCPE] Things missing in Onap Tosca DM?
Hi
All node types derived from TOSCA Root supports the standard
tosca.interfaces.node.lifecycle.Standard interface.
I am assuming R2 ONAP will use such standard interface in conjunction with the
TOSCA normative install workflow supported by all TOSCA orchestrators including
ARIA.
Is this correct?
With such standard interface and workflow, it is possible to use cloud init and
inject data using the TOSCA configure operation that is part of the
tosca.interfaces.node.lifecycle.Standard interface.
Regards
Steve
From:
[email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of
[email protected]<mailto:[email protected]>
Sent: Tuesday, March 20, 2018 12:47 AM
To: [email protected]<mailto:[email protected]>
Cc: [email protected]<mailto:[email protected]>
Subject: [onap-discuss] 答复: RE: [model][vCPE] Things missing in Onap Tosca DM?
Hi all
1. As I understand, the heat template features vCPE used includes
metadata,usedata,,, which are not included in the IM and DM now.
2. pre-created network issue can be gotten as a input from TOSCA, but needs a
properties of VL to represent it, such as description or a new properties.
BR
Maopeng
原始邮件
发件人：Lu,Lianhao <[email protected]<mailto:[email protected]>>
收件人：Gaoweitao (Victor, MANO)
<[email protected]<mailto:[email protected]>>[email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>>
抄送人：张茂鹏10030173;Vul, Alex <[email protected]<mailto:[email protected]>>Huang,
Haibin <[email protected]<mailto:[email protected]>>
日 期 ：2018年03月20日 11:45
主 题 ：RE: [model][vCPE] Things missing in Onap Tosca DM?
Hi Victor,
I’ve got some following-up questions
1. SSH key pairs for VM
When saying to use inject file to handle this, do you mean to inject ssh
public key to ~/.ssh/authorized_keys file within in the VM?
2. cloudinit user scripts
I’ve looked at the inject file definition in IM. Here I’ve several questions
about inject file:
1. According to IM, the inject file property “Describes the information
(e.g. URL) about the scripts, config drive metadata, etc. which can be used
during Vdu booting process.” Do we need to specify the destination pathname
within the VM image for the injected scripts? Openstack needs this kind of
information.
2. vCPE usecase’s cloudinit scripts needs to get some run-time dynamic
properties & attributes of other VDUs, do we have a mechanism to pass those
property/attribute values to the inject files?
3. Why can’t we leverage the existing
tosca.interfaces.node.lifecycle.Standard interface, just like
https://github.com/openstack/tosca-parser/blob/master/toscaparser/tests/data/CSAR/tosca_elk/Definitions/tosca_elk.yaml#L79
. This could solve the above run-time properties issue.
BR
-Lianhao
From: Gaoweitao (Victor, MANO) [mailto:[email protected]]
Sent: Tuesday, March 20, 2018 9:48 AM
To: Lu, Lianhao <[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>
Cc: [email protected]<mailto:[email protected]>; Vul, Alex
<[email protected]<mailto:[email protected]>>; Huang, Haibin
<[email protected]<mailto:[email protected]>>
Subject: 答复: [model][vCPE] Things missing in Onap Tosca DM?
Hi Lianhao,
Please see my comments inline.
BR
Victor
发件人: Lu, Lianhao [mailto:[email protected]]
发送时间: 2018年3月19日 19:25
收件人: [email protected]<mailto:[email protected]>
抄送: [email protected]<mailto:[email protected]>; Vul, Alex
<[email protected]<mailto:[email protected]>>; Gaoweitao (Victor, MANO)
<[email protected]<mailto:[email protected]>>; Huang, Haibin
<[email protected]<mailto:[email protected]>>
主题: [model][vCPE] Things missing in Onap Tosca DM?
Hi Guys,
I’m now looking at the vCPE usecase
(https://wiki.onap.org/pages/viewpage.action?pageId=3246168#UseCase:ResidentialBroadbandvCPE(Approved)-Description),
and try to convert its heat
template(https://git.onap.org/demo/tree/heat/vCPE) into latest onap Tosca DM
(https://wiki.onap.org/display/DW/Data+Model+align+with+TOSCA+NFV+Profile ).
I found the following things in heat and can NOT find the corresponding mapping
in the Tosca DM.
1. SSH key pairs for VM
Heat supports creating ssh keypair for VM to enable login with ssh
public/private keys. However I could not find corresponding in latest onap
tosca DM. Should we support this in tosca DM?
Victor: I think inject file could handle this.
2. cloudinit user scripts
In heat, vCPE uses cloudinit user script to executed within the VM after VM has
been launched to configure the VNF softwares within the VM. However, in tosca
DM, there is no direct mapping to such things in VDU. Should I use
tosca.interfaces.node.lifecycle.Standard interface instead or should we add
new properties in VDU (see openstack tacker’s VDU as an example
https://github.com/openstack/tacker/blob/master/tacker/tosca/lib/tacker_nfv_defs.yaml#L239
)? The new userdata should also support inputs like
tosca.interfaces.node.lifecycle.Standard interface.
Victor: In general, we will use inject file handle this. You can refer here:
https://wiki.onap.org/display/DW/Node+Type tosca.nodes.nfv.Vdu.Compute and IM
inject file definition for more info :
https://wiki.onap.org/display/DW/Design+Time+Model+Clean+Version#DesignTimeModelCleanVersion-Class:VDU/VDUDesc<https://wiki.onap.org/display/DW/Design+Time+Model+Clean+Version%23DesignTimeModelCleanVersion-Class:VDU/VDUDesc>.
3. pre-created networks:
vCPE will use 2 pre-created networks which are created when ONAP itself is
being deployed: onap_public_net is used to make VM be able to connect to
internet, onap_private_net is the oam network which is used to make some of
the vCPE vnf talk to some onap component(e.g. dcae_collector). So this
requires the VNF VM to be connected to a pre-created network. However in tosca
DM, it seems that there is no way to specify a VDU created by tosca DM
connecting to a pre-created network which is already created during ONAP
deployment using heat. Should we add an property in
tosca.nodes.nfv.VnfVirtualLink to indicate whether the network is pre-created
or not?
Victor：Pre-created network is no difference with new-create network, just use
vnfvirtualLink describe the pre-created network, orchestrator could handle
this（if network already created, vm could re-use it.）
4. VM metadata
vCPE also uses VM metadata which is missing in Tosca DM’s VDU. Should we add
this?( see openstack tacker’s VDU as an example
https://github.com/openstack/tacker/blob/master/tacker/tosca/lib/tacker_nfv_defs.yaml#L198
)?
Victor: Lianhao, could u give more usage/info about the VDU/VM metadata, maybe
we could use other properties or attributes instead.
Best Regards,
-Lianhao
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
