...
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
node_types: org.onap.CL_Component: properties: component_name: type: string description: Human readable name for the component. required: true provider: type: string description: Provider of the component and of the descriptor. required: true component_version: type: string description: Software version of the component. required: true resource_id: type: string description: >The ID of the resource, should be provided if the resource was uploaded to the entity's inventory already. required: false resource_content: type: string description: the contents of the component resource, to be uploaded during deploycommssioning phase of loop. required: false monitoring_policy: type: string description: A reference to the monitoring policy if applicable. required: false version: 0.0.1 derived_from: tosca.nodes.Root |
...
Warning |
---|
The below example doesn't explicitly include any order, ordering of deployment control loop execution is to be considered in the future which likely would lead to changes to this |
...
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
topology_template: inputs: pm_docker_image: type: string description: docker image used for deployinginstantiating the PMSH service. required: true operational_policy_name: type: string description: name of the operational policy to be triggered on MR when subscription is created. required: true outbound_topic_name: type: string description: Name of topic used for messages to policy. required: true feedback_topic_name: type: string description: Name of topic used for feedback from policy. required: true inventory_notification_topic_name: type: string description: Name of topic used for inventory inventory notifications. required: true pmsh_resource_id: type: string description: ID of the PMSH blueprint in the inventory. required: true node_templates: org.onap.PM_Subscription_Handler: type: org.onap.CL_Component properties: application_name: PMSH provider: DCAE application_Version: '1.0.1' resource_id: { get_input: pmsh_resource_id } monitoring_policy: 'monitoring_policy_id' application_config: tag_version: { get_input: pm_docker_image } operational_policy_name: { get_input: operational_policy_name } pmsh_publish_topic_name: { get_input: outbound_topic_name } policy_feedback_topic_name: { get_input: feedback_topic_name } aai_notification_topic_name: { get_input: inventory_notification_topic_name } |
...
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
tosca_definitions_version: tosca_simple_yaml_1_3 node_types: org.onap.CL_Component: properties: application_name: type: string description: Human readable name for the application. required: true provider: type: string description: Provider of the application and of the descriptor. required: true application_version: type: string description: Software version of the application. required: true resource_id: type: string description: >The ID of the resource, should be provided if the resource was uploaded to the entity's inventory already. required: false resource_content: type: string description: the contents of the application resource, to be uploaded during deployinstantiation phase of loop. required: false monitoring_policy: type: string description: A reference to the monitoring policy if applicable. required: false version: 0.0.1 derived_from: tosca.nodes.Root topology_template: inputs: pm_docker_image: type: string description: docker image used for deployinginstantiating the PMSH service. required: true operational_policy_name: type: string description: name of the operational policy to be triggered on MR when subscription is created. required: true outbound_topic_name: type: string description: Name of topic used for messages to policy. required: true feedback_topic_name: type: string description: Name of topic used for feedback from policy. required: true inventory_notification_topic_name: type: string description: Name of topic used for inventory inventory notifications. required: true pmsh_resource_id: type: string description: ID of the PMSH blueprint in the inventory. required: true node_templates: org.onap.PM_Subscription_Handler: type: org.onap.Cl_Component properties: application_name: PMSH provider: DCAE application_Version: '1.0.1' resource_id: { get_input: pmsh_resource_id } monitoring_policy: 'monitoring_policy_id' application_config: tag_version: { get_input: pm_docker_image } operational_policy_name: { get_input: operational_policy_name } pmsh_publish_topic_name: { get_input: outbound_topic_name } policy_feedback_topic_name: { get_input: feedback_topic_name } aai_notification_topic_name: { get_input: inventory_notification_topic_name } |
2.2: Modelling from TOSCA to
...
Commissioned Data in Run Time Catalogue
2.3: Modelling from TOSCA to Instance Data Run Time Catalogue
3: APIs and Sequence Diagrams
3.1:
...
Commissioning
Ajay Deep Singh to pad out this section
This section defines DeploymentCommissioning/CRUD Operations that can be performed on ControlLoops.
...