TOSCA node types are added, listed below:
1) MosquittoBroker
Under radon.nodes.mqtt Namespace
2) ConsMQTT
Under radon.nodes.datapipeline.source Namespace
3) PubsMQTT
Under radon.nodes.datapipeline.destination Namespace
4) Encrypt
Under radon.nodes.datapipeline.process Namespace
5) Decrypt
Under radon.nodes.datapipeline.process Namespace
Short Description of the created node types:
MosquittoBroker :
Using this MosquittoBroker node type user can install Mosquitto Broker in centos instance and can configure it by mentioning the following properties: Username, Password, port.
ConsMQTT:
Using this ConsMQTT node type users can create and configure a data pipeline with configured Mosquitto Broker by mentioning the following properties: Broker_URI, Username, Password, Client_ID, schedulingStrategy, schedulingPeriodCRON, Max_Queue_Size, Quality_of_Service, TopicName.
PubsMQTT:
Using this PubsMQTT node type users can create and configure a data pipeline with configured Mosquitto Broker by mentioning the following properties: Broker_URI, Username, Password, Client_ID, schedulingStrategy, schedulingPeriodCRON, Quality_of_Service, TopicName.
Encrypt:
Using this Encrypt node type user can create and configure a data pipeline by mentioning the following property: Password
Decrypt:
Using this Decrypt node type user can create and configure a data pipeline by mentioning the following property: Password
Created and added one service template with these above mentioned 5 node types to check, node types are working well or not.
That service template is under radon.blueprints.examples named as MQTT_Data_Pipeline_Encryption_Decryption_Example.
Tested with this command :
curl -d "" http://{{My IP}}:{{Port}}/winery/admin/repository/touch
with No error.
TOSCA node types are added, listed below: 1) MosquittoBroker
Under radon.nodes.mqtt Namespace 2) ConsMQTT Under radon.nodes.datapipeline.source Namespace 3) PubsMQTT Under radon.nodes.datapipeline.destination Namespace 4) Encrypt Under radon.nodes.datapipeline.process Namespace 5) Decrypt Under radon.nodes.datapipeline.process Namespace
Short Description of the created node types: MosquittoBroker :
Using this MosquittoBroker node type user can install Mosquitto Broker in centos instance and can configure it by mentioning the following properties: Username, Password, port.
ConsMQTT: Using this ConsMQTT node type users can create and configure a data pipeline with configured Mosquitto Broker by mentioning the following properties: Broker_URI, Username, Password, Client_ID, schedulingStrategy, schedulingPeriodCRON, Max_Queue_Size, Quality_of_Service, TopicName.
PubsMQTT: Using this PubsMQTT node type users can create and configure a data pipeline with configured Mosquitto Broker by mentioning the following properties: Broker_URI, Username, Password, Client_ID, schedulingStrategy, schedulingPeriodCRON, Quality_of_Service, TopicName.
Encrypt: Using this Encrypt node type user can create and configure a data pipeline by mentioning the following property: Password
Decrypt: Using this Decrypt node type user can create and configure a data pipeline by mentioning the following property: Password
Created and added one service template with these above mentioned 5 node types to check, node types are working well or not. That service template is under radon.blueprints.examples named as MQTT_Data_Pipeline_Encryption_Decryption_Example.
Tested with this command :
curl -d "" http://{{My IP}}:{{Port}}/winery/admin/repository/touch with No error.
This is the part of UTR contribution.