[ccsdk/cds.git] /

/*\r
 * Copyright © 2017-2018 AT&T Intellectual Property.\r
 *\r
 * Licensed under the Apache License, Version 2.0 (the "License");\r
 * you may not use this file except in compliance with the License.\r
 * You may obtain a copy of the License at\r
 *\r
 *     http://www.apache.org/licenses/LICENSE-2.0\r
 *\r
 * Unless required by applicable law or agreed to in writing, software\r
 * distributed under the License is distributed on an "AS IS" BASIS,\r
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\r
 * See the License for the specific language governing permissions and\r
 * limitations under the License.\r
 */\r
\r
package org.onap.ccsdk.apps.controllerblueprints.core.data\r
\r
import com.fasterxml.jackson.annotation.JsonIgnore\r
import com.fasterxml.jackson.annotation.JsonProperty\r
import com.fasterxml.jackson.databind.JsonNode\r
\r
/**\r
 *\r
 *\r
 * @author Brinda Santh\r
 */\r
open class EntityType {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    var description: String? = null\r
    var version: String = "1.0.0"\r
    var metadata: MutableMap<String, String>? = null\r
    @get:JsonProperty("derived_from")\r
    lateinit var derivedFrom: String\r
    var attributes: MutableMap<String, AttributeDefinition>? = null\r
    var properties: MutableMap<String, PropertyDefinition>? = null\r
}\r
\r
/*\r
 5.3.2 tosca.datatypes.org.onap.ccsdk.apps.controllerblueprints.core.data.Credential\r
 The org.onap.ccsdk.apps.controllerblueprints.core.data.Credential type is a complex TOSCA data Type used when describing\r
 authorization credentials used to access network accessible resources.\r
 */\r
class Credential {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    var protocol: String? = null\r
    @get:JsonProperty("token_type")\r
    lateinit var tokenType: String\r
    lateinit var token: String\r
    var keys: MutableMap<String, String>? = null\r
    lateinit var user: String\r
}\r
\r
/*\r
3.5.2 Constraint clause\r
A constraint clause defines an operation along with one or more compatible values that can be used to define a constraint on a property or parameter’s allowed values when it is defined in a TOSCA Service Template or one of its entities.\r
 */\r
class ConstraintClause {\r
    @get:JsonProperty("equal")\r
    var equal: Any? = null\r
    @get:JsonProperty("greater_than")\r
    var greaterThan: Any? = null\r
    @get:JsonProperty("greater_or_equal")\r
    var greaterOrEqual: Any? = null\r
    @get:JsonProperty("less_than")\r
    var lessThan: Any? = null\r
    @get:JsonProperty("less_or_equal")\r
    var lessOrEqual: Any? = null\r
    @get:JsonProperty("in_range")\r
    var inRange: Any? = null\r
    @get:JsonProperty("valid_values")\r
    var validValues: MutableList<Any>? = null\r
    @get:JsonProperty("length")\r
    var length: Any? = null\r
    @get:JsonProperty("min_length")\r
    var minLength: Any? = null\r
    @get:JsonProperty("max_length")\r
    var maxLength: Any? = null\r
    @get:JsonProperty("pattern")\r
    var pattern: String? = null\r
}\r
\r
/*\r
3.5.4 Node Filter definition\r
A node filter definition defines criteria for selection of a TOSCA Node Template based upon the template’s property values, capabilities and capability properties.\r
 */\r
\r
class NodeFilterDefinition {\r
    var properties: MutableMap<String, PropertyDefinition>? = null\r
    var capabilities : MutableList<String>? = null\r
}\r
\r
/*\r
3.5.5 Repository definition\r
 A repository definition defines a named external repository which contains deployment\r
 and implementation artifacts that are referenced within the TOSCA Service Template.\r
*/\r
class RepositoryDefinition {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    var description: String? = null\r
    lateinit var url: String\r
    var credential: Credential? = null\r
}\r
\r
\r
/*\r
3.5.6 Artifact definition\r
An artifact definition defines a named, typed file that can be associated with Node Type\r
or Node Template and used by orchestration engine to facilitate deployment and implementation of interface operations.\r
 */\r
class ArtifactDefinition {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    var type: String? = null\r
    var file: String? = null\r
    var repository: String? = null\r
    var description: String? = null\r
    @get:JsonProperty("deploy_Path")\r
    var deployPath: String? = null\r
    var properties: MutableMap<String, JsonNode>? = null\r
    var content: String? = null\r
    @Deprecated("Mapping content is define by the Type")\r
    var mappingContent: String? = null\r
}\r
\r
\r
/*\r
3.5.7 Import definition\r
An import definition is used within a TOSCA Service Template to locate and uniquely name\r
another TOSCA Service Template file which has type and template definitions to be imported (included)\r
and referenced within another Service Template.\r
 */\r
class ImportDefinition {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    lateinit var file: String\r
    var repository: String? = null\r
    @get:JsonProperty("namespace_uri")\r
    var namespaceUri: String? = null\r
    @get:JsonProperty("namespace_prefix")\r
    var namespacePrefix: String? = null\r
}\r
\r
/*\r
3.5.8 Property definition A property definition defines a named, typed value and related data that can be associated with an\r
entity defined in this specification (e.g., Node Types, Relationship Types, Capability Types, etc.).\r
Properties are used by template authors to provide input values to TOSCA entities which indicate their “desired state” when they are\r
instantiated. The value of a property can be retrieved using the get_property function within TOSCA Service Templates.\r
 */\r
class PropertyDefinition {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    var description: String? = null\r
    var required: Boolean? = null\r
    var type: String? = null\r
    @get:JsonProperty("default")\r
    var defaultValue: Any? = null\r
    var status: String? = null\r
    var constraints: MutableList<ConstraintClause>? = null\r
    @get:JsonProperty("entry_schema")\r
    var entrySchema: EntrySchema? = null\r
    var value: Any? = null\r
}\r
\r
\r
/*\r
3.5.10 Attribute definition\r
\r
An attribute definition defines a named, typed value that can be associated with an entity defined in this\r
specification (e.g., a Node, Relationship or Capability Type).  Specifically, it is used to expose the\r
“actual state” of some property of a TOSCA entity after it has been deployed and instantiated\r
(as set by the TOSCA orchestrator). Attribute values can be retrieved via the get_attribute function\r
from the instance model and used as values to other entities within TOSCA Service Templates.\r
 */\r
\r
class AttributeDefinition {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    var description: String? = null\r
    lateinit var type: String\r
    @JsonProperty("default")\r
    var _default: Any? = null\r
    var status: String? = null\r
    @JsonProperty("entry_schema")\r
    var entry_schema: String? = null\r
}\r
\r
/*\r
3.5.13 Operation definition\r
An operation definition defines a named function or procedure that can be bound to an implementation artifact (e.g., a script).\r
 */\r
class OperationDefinition {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    var description: String? = null\r
    var implementation: Implementation? = null\r
    var inputs: MutableMap<String, PropertyDefinition>? = null\r
    var outputs: MutableMap<String, PropertyDefinition>? = null\r
}\r
\r
class Implementation {\r
    var primary: String? = null\r
    var dependencies: MutableList<String>? = null\r
}\r
\r
/*\r
3.5.14 Interface definition\r
An interface definition defines a named interface that can be associated with a Node or Relationship Type\r
 */\r
class InterfaceDefinition {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    var type: String? = null\r
    var operations: MutableMap<String, OperationDefinition>? = null\r
    var inputs: MutableMap<String, PropertyDefinition>? = null\r
}\r
\r
/*\r
3.5.15 Event Filter definition\r
An event filter definition defines criteria for selection of an attribute, for the purpose of monitoring it, within a TOSCA entity, or one its capabilities.\r
 */\r
class EventFilterDefinition {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    lateinit var node: String\r
    var requirement: String? = null\r
    var capability: String? = null\r
}\r
\r
/*\r
3.5.16 Trigger definition TODO\r
A trigger definition defines the event, condition and action that is used to “trigger” a policy it is associated with.\r
 */\r
class TriggerDefinition {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    var description: String? = null\r
    @get:JsonProperty("event_type")\r
    lateinit var eventType: String\r
    lateinit var action: String\r
}\r
\r
/*\r
    3.5.17 org.onap.ccsdk.apps.controllerblueprints.core.data.Workflow activity definition\r
    A workflow activity defines an operation to be performed in a TOSCA workflow. Activities allows to:\r
    · Delegate the workflow for a node expected to be provided         by the orchestrator\r
    · Set the state of a node\r
    · Call an operation        defined on a TOSCA interface of a node, relationship or group\r
    · Inline another workflow defined in the topology (to allow reusability)\r
 */\r
class Activity {\r
    var delegate: String? = null\r
    @get:JsonProperty("set_state")\r
    var setState: String? = null\r
    @get:JsonProperty("call_operation")\r
    var callOperation: String? = null\r
    var inlines: ArrayList<String>? = null\r
}\r
\r
/*\r
3.5.20 org.onap.ccsdk.apps.controllerblueprints.core.data.Workflow precondition definition\r
A workflow condition can be used as a filter or precondition to check if a workflow can be processed or not based on the state of the instances of a TOSCA topology deployment. When not met, the workflow will not be triggered.\r
 */\r
class PreConditionDefinition {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    lateinit var target: String\r
    @get:JsonProperty("target_relationship")\r
    lateinit var targetRelationship: String\r
    lateinit var condition: ArrayList<ConditionClause>\r
}\r
\r
/*\r
3.5.21 org.onap.ccsdk.apps.controllerblueprints.core.data.Workflow step definition\r
A workflow step allows to define one or multiple sequenced activities in a workflow and how they are connected to other steps in the workflow. They are the building blocks of a declarative workflow.\r
 */\r
class Step {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    var description: String? = null\r
    var target: String? = null\r
    @JsonProperty("target_relationship")\r
    var targetRelationship: String? = null\r
    @JsonProperty("operation_host")\r
    var operationHost: String? = null\r
    var activities: ArrayList<Activity>? = null\r
    @get:JsonProperty("on_success")\r
    var onSuccess: ArrayList<String>? = null\r
    @get:JsonProperty("on_failure")\r
    var onFailure: ArrayList<String>? = null\r
}\r
\r
/*\r
3.6.2 Capability definition\r
A capability definition defines a named, typed set of data that can be associated with Node Type or Node Template to describe a transparent capability or feature of the software component the node describes.\r
 */\r
\r
class CapabilityDefinition {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    var type: String? = null\r
    var description: String? = null\r
    var properties: MutableMap<String, PropertyDefinition>? = null\r
    @get:JsonProperty("valid_source_types")\r
    var validSourceTypes: MutableList<String>? = null\r
    var occurrences: MutableList<Any>? = null\r
}\r
\r
/*\r
3.6.3 Requirement definition\r
The Requirement definition describes a named requirement (dependencies) of a TOSCA Node Type or Node template which needs to be fulfilled by a matching Capability definition declared by another TOSCA modelable entity.  The requirement definition may itself include the specific name of the fulfilling entity (explicitly) or provide an abstract type, along with additional filtering characteristics, that a TOSCA orchestrator can use to fulfill the capability at runtime (implicitly).\r
 */\r
class RequirementDefinition {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    var description: String? = null\r
    var capability: String? = null\r
    var node: String? = null\r
    var relationship: String? = null\r
    var occurrences: MutableList<Any>? = null\r
}\r
\r
/*\r
3.6.4 Artifact Type\r
An Artifact Type is a reusable entity that defines the type of one or more files that are used to define implementation or deployment artifacts that are referenced by nodes or relationships on their operations.\r
 */\r
class ArtifactType : EntityType() {\r
    @get:JsonProperty("mime_type")\r
    var mimeType: String? = null\r
    @get:JsonProperty("file_ext")\r
    var fileExt: MutableList<String>? = null\r
\r
}\r
\r
/*\r
3.6.6 Data Type\r
A Data Type definition defines the schema for new named datatypes in TOSCA.\r
 */\r
\r
class DataType : EntityType(){\r
    var constraints: MutableList<MutableMap<String, Any>>? = null\r
}\r
\r
/*\r
3.6.9 Node Type\r
A Node Type is a reusable entity that defines the type of one or more Node Templates. As such, a Node Type defines the structure of observable properties via a Properties Definition, the Requirements and Capabilities of the node as well as its supported interfaces.\r
\r
 */\r
\r
class NodeType : EntityType() {\r
    var capabilities: MutableMap<String, CapabilityDefinition>? = null\r
    var requirements: MutableMap<String, RequirementDefinition>? = null\r
    var interfaces: MutableMap<String, InterfaceDefinition>? = null\r
    var artifacts: MutableMap<String, ArtifactDefinition>? = null\r
}\r
\r
/*\r
3.6.8 Requirement Type\r
A Requirement Type is a reusable entity that describes a kind of requirement that a Node Type can declare to expose.  The TOSCA Simple Profile seeks to simplify the need for declaring specific Requirement Types from nodes and instead rely upon nodes declaring their features sets using TOSCA Capability Types along with a named Feature notation.\r
 */\r
\r
class RequirementType : EntityType() {\r
    var requirements: MutableMap<String, RequirementDefinition>? = null\r
    var capabilities: MutableMap<String, CapabilityDefinition>? = null\r
    var interfaces: MutableMap<String, InterfaceDefinition>? = null\r
    var artifacts: MutableMap<String, ArtifactDefinition>? = null\r
}\r
\r
/*\r
3.6.10 Relationship Type\r
A Relationship Type is a reusable entity that defines the type of one or more relationships between Node Types or Node Templates.\r
*/\r
\r
class RelationshipType : EntityType() {\r
    var interfaces: MutableMap<String, InterfaceDefinition>? = null\r
    @get:JsonProperty("valid_target_types")\r
    var validTargetTypes: ArrayList<String>? = null\r
}\r
\r
/*\r
3.6.11 Group Type\r
A Group Type defines logical grouping types for nodes, typically for different management purposes.\r
Groups can effectively be viewed as logical nodes that are not part of the physical deployment topology\r
 of an application, yet can have capabilities and the ability to attach policies and interfaces\r
 that can be applied (depending on the group type) to its member nodes.\r
 */\r
\r
class GroupType : EntityType() {\r
    var members: MutableList<String>? = null\r
    var requirements: ArrayList<RequirementDefinition>? = null\r
    var capabilities: MutableMap<String, CapabilityDefinition>? = null\r
    var interfaces: MutableMap<String, InterfaceDefinition>? = null\r
\r
}\r
\r
/*\r
    3.6.12 Policy Type\r
    A Policy Type defines a type of requirement that affects or governs an application or service’s\r
    topology at some stage of its lifecycle, but is not explicitly part of the topology itself\r
    (i.e., it does not prevent the application or service from being deployed or run if it did not exist).\r
 */\r
class PolicyType : EntityType(){\r
    lateinit var targets: MutableList<String>\r
}\r
\r
/*\r
3.7.1 Capability assignment\r
A capability assignment allows node template authors to assign values to properties and attributes for a named capability definition that is part of a Node Template’s type definition.\r
 */\r
class CapabilityAssignment {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    var attributes: MutableMap<String, JsonNode>? = null\r
    var properties: MutableMap<String, JsonNode>? = null\r
}\r
\r
/*\r
3.7.4 Relationship Template\r
A Relationship Template specifies the occurrence of a manageable relationship between node templates as part of an application’s topology model that is defined in a TOSCA Service Template.  A Relationship template is an instance of a specified Relationship Type and can provide customized properties, constraints or operations which override the defaults provided by its Relationship Type and its implementations.\r
 */\r
class GroupDefinition {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    lateinit var type: String\r
    var description: String? = null\r
    var metadata : MutableMap<String, String>? = null\r
    var properties : MutableMap<String, JsonNode>? = null\r
    var members = ArrayList<String>()\r
    var interfaces : MutableMap<String, InterfaceDefinition>?= null\r
}\r
\r
/*\r
3.7.6 Policy definition\r
A policy definition defines a policy that can be associated with a TOSCA topology or top-level entity definition (e.g., group definition, node template, etc.).\r
 */\r
class PolicyDefinition {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    lateinit var type: String\r
    var description: String? = null\r
    var metadata: MutableMap<String, String>? = null\r
    var properties: MutableMap<String, JsonNode>? = null\r
    var targets: MutableList<String>? = null\r
}\r
\r
\r
/*\r
3.8 Topology Template definition\r
This section defines the topology template of a cloud application. The main ingredients of the topology template are node templates representing components of the application and relationship templates representing links between the components. These elements are defined in the nested node_templates section and the nested relationship_templates sections, respectively.  Furthermore, a topology template allows for defining input parameters, output parameters as well as grouping of node templates.\r
 */\r
class TopologyTemplate {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    var description: String? = null\r
    var inputs: MutableMap<String, PropertyDefinition>? = null\r
    @get:JsonProperty("node_templates")\r
    var nodeTemplates: MutableMap<String, NodeTemplate>? = null\r
    @get:JsonProperty("relationship_templates")\r
    var relationshipTemplates: MutableMap<String, RelationshipTemplate>? = null\r
    var policies: MutableMap<String, PolicyDefinition>? = null\r
    var outputs: MutableMap<String, PropertyDefinition>? = null\r
    @get:JsonProperty("substitution_mappings")\r
    var substitutionMappings: Any? = null\r
    var workflows: MutableMap<String, Workflow>? = null\r
}\r
\r
class SubstitutionMapping {\r
    @get:JsonProperty("node_type")\r
    lateinit var nodeType: String\r
    lateinit var capabilities: ArrayList<String>\r
    lateinit var requirements: ArrayList<String>\r
}\r
\r
class EntrySchema {\r
    lateinit var type: String\r
    var constraints: MutableList<MutableMap<String, Any>>? = null\r
}\r
\r
class InterfaceAssignment {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    var operations: MutableMap<String, OperationAssignment>? = null\r
    var inputs: MutableMap<String, JsonNode>? = null\r
}\r
\r
/*\r
3.7.3 Node Template\r
A Node Template specifies the occurrence of a manageable software component as part of an application’s topology model which is defined in a TOSCA Service Template.  A Node template is an instance of a specified Node Type and can provide customized properties, constraints or operations which override the defaults provided by its Node Type and its implementations.\r
 */\r
\r
class NodeTemplate {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    var description: String? = null\r
    lateinit var type: String\r
    var metadata: MutableMap<String, String>? = null\r
    var directives: MutableList<String>? = null\r
    //@get:JsonSerialize(using = PropertyDefinitionValueSerializer::class)\r
    var properties: MutableMap<String, JsonNode>? = null\r
    var attributes: MutableMap<String, JsonNode>? = null\r
    var capabilities: MutableMap<String, CapabilityAssignment>? = null\r
    var requirements: MutableMap<String, RequirementAssignment>? = null\r
    var interfaces: MutableMap<String, InterfaceAssignment>? = null\r
    var artifacts: MutableMap<String, ArtifactDefinition>? = null\r
    @get:JsonProperty("node_filter")\r
    var nodeFilter: NodeFilterDefinition? = null\r
    var copy: String? = null\r
}\r
\r
class OperationAssignment {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    var description: String? = null\r
    var implementation: Implementation? = null\r
    var inputs: MutableMap<String, JsonNode>? = null\r
    var outputs: MutableMap<String, JsonNode>? = null\r
}\r
\r
/*\r
3.7.4 Relationship Template\r
A Relationship Template specifies the occurrence of a manageable relationship between node templates as part of an application’s topology model that is defined in a TOSCA Service Template.  A Relationship template is an instance of a specified Relationship Type and can provide customized properties, constraints or operations which override the defaults provided by its Relationship Type and its implementations.\r
 */\r
\r
class RelationshipTemplate {\r
    var type: String? = null\r
    var description: String? = null\r
    var metadata: MutableMap<String, String>? = null\r
    var properties: MutableMap<String, PropertyDefinition>? = null\r
    var attributes: MutableMap<String, JsonNode>? = null\r
    var interfaces: MutableMap<String, InterfaceDefinition>? = null\r
    var copy: String? = null\r
}\r
\r
/*\r
3.7.2 Requirement assignment\r
A Requirement assignment allows template authors to provide either concrete names of TOSCA templates or provide abstract selection criteria for providers to use to find matching TOSCA templates that are used to fulfill a named requirement’s declared TOSCA Node Type.\r
 */\r
\r
class RequirementAssignment {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    var capability: String? = null\r
    var node: String? = null\r
    //Relationship Type or Relationship Template\r
    var relationship: String? = null\r
}\r
\r
\r
class Workflow {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    var description: String? = null\r
    var steps: MutableMap<String, Step>? = null\r
    var preconditions: ArrayList<PreConditionDefinition>? = null\r
    var inputs: MutableMap<String, PropertyDefinition>? = null\r
}\r
\r
\r
class ConditionClause {\r
    var and: ArrayList<MutableMap<String, Any>>? = null\r
    var or: ArrayList<MutableMap<String, Any>>? = null\r
    @get:JsonProperty("assert")\r
    var assertConditions: ArrayList<MutableMap<String, Any>>? = null\r
}\r
\r
/*\r
3.9 Service Template definition\r
A TOSCA Service Template (YAML) document contains element definitions of building blocks for cloud application, or complete models of cloud applications. This section describes the top-level structural elements (TOSCA keynames) along with their grammars, which are allowed to appear in a TOSCA Service Template document.\r
 */\r
\r
class ServiceTemplate {\r
    @get:JsonIgnore\r
    var id: String? = null\r
    @get:JsonProperty("tosca_definitions_version")\r
    var toscaDefinitionsVersion: String = "controller_blueprint_1_0_0"\r
    var metadata: MutableMap<String, String>? = null\r
    var description: String? = null\r
    @get:JsonProperty("dsl_definitions")\r
    var dslDefinitions: MutableMap<String, Any>? = null\r
    var repositories: MutableMap<String, RepositoryDefinition>? = null\r
    var imports: MutableList<ImportDefinition>? = null\r
    @get:JsonProperty("artifact_types")\r
    var artifactTypes: MutableMap<String, ArtifactType>? = null\r
    @get:JsonProperty("data_types")\r
    var dataTypes: MutableMap<String, DataType>? = null\r
    @get:JsonProperty("node_types")\r
    var nodeTypes: MutableMap<String, NodeType>? = null\r
    @get:JsonProperty("policy_types")\r
    var policyTypes: PolicyType? = null\r
    @get:JsonProperty("topology_template")\r
    var topologyTemplate: TopologyTemplate? = null\r
}\r
\r
class ToscaMetaData {\r
    lateinit var toscaMetaFileVersion: String\r
    lateinit var csarVersion: String\r
    lateinit var createdBy: String\r
    lateinit var entityDefinitions: String\r
    var templateTags: String? = null\r
}\r
\r