git clone https://@opensourceprojects.eu/git/p/c2net/service c2net-service



File Date Author Commit
deployment 2017-06-28 Daniel Machancoses Daniel Machancoses [f5f1c6] Updated to service 0_0_41
domain 2017-06-14 Daniel Machancoses Daniel Machancoses [deaa9c] Actualizado los certificados de c2net
service 2017-06-28 Daniel Machancoses Daniel Machancoses [f5f1c6] Updated to service 0_0_41
Jenkinsfile 2017-07-04 Josep Maria Bernabé Gisbert Josep Maria Bernabé Gisbert [aee6a5] Corrected some bugs in jenkinsfile
readme.md 2017-06-28 Daniel Machancoses Daniel Machancoses [f5f1c6] Updated to service 0_0_41

Read Me

C2NET Service

C2NET Service VERSION 0_0_41

Service Creation Date : 28/06/2017

This document describes the C2NET service which is deployed in ECLOUD.

Table of contents

  • Manifest Folders Description
  • Service Manifest
  • Deployment Manifest
  • Scrips to Build the service
  • Instructions to Register/Deploy Service
  • Domain Creation and Linking

Manifest Folder Description

The folder structure is:

.
├── service               (1)
│   └── Manifest.json     
├── deployment            (2)
│   └── Manifest.json     
├── scripts               (5)
├── domain
│   ├── c2net_service     (3)
│   └── c2net_dataservice (4)
│   └── c2net_service_nocert (5)
└── readme.md

Where:

  1. Service Manifest Folder
  2. Deployment Manifest Folder
  3. Scripts Folder
  4. Service Domain Manifests Folder
  5. ServiceData Domain Manifests Folder
  6. Service Domain Manifests Folder without certificates (HTTP)

Service Manifest

Component Versions

The following components are deployed in the the service:

Component Zip File Name Version
ACS ACS-0_1_3-ITI.zip eslap://iti/components/acs 0_1_3
CNM CNM-1_0_7-IKERLAN.zip eslap://c2netproject/components/cnm 1_0_7
DKMS DKMS-1_0_4-UNINOVA.zip eslap://c2netproject/components/dkms 1_0_4
DSSQL DSSQL-0_1_15-ITI.zip eslap://iti/components/dssql 0_1_15
JOBS JOBS-0_0_8-ITI.zip eslap://c2netproject/components/jobs 0_0_8
MDBW MDBW-0_0_158-ITI.zip eslap://iti/components/mariadbwrapper 0_0_158
MPE_AA_1_0_1_ITI MPE_AA_1_0_1_ITI.zip eslap://linagora.c2netproject.eu/components/mpe_aa 1_0_1
MPE_MD_1_1_7_ARMINES MPE_MD_1_1_7_ARMINES.zip eslap://linagora.c2netproject.eu/components/mpe_md 1_1_7
OPC OPC-0_0_8-CMS.zip eslap://c2netproject/components/opc 0_0_8
OPP OPP-1_1_2-LINA.zip eslap://linagora.c2netproject.eu/components/opp 1_1_2
POMA POMA-0_0_16-CMS.zip eslap://c2netproject/components/pomam 0_0_16
PSMB PSMB-0_0_3.zip eslap://c2netproject/components/pubsub 0_0_3
RM RM-1_3_4-UNINOVA.zip eslap://uninova.c2net/components/rm 1_3_4
SM_0_0_15 SM_0_0_15-UPV.zip eslap://c2netproject/components/solvermanager 0_0_15
TASKEXEC TASKEXEC-0_0_12-ITI.zip eslap://c2netproject/components/taskexecutor 0_0_12
TPM TPM-1_0_5-VTT.zip eslap://c2netproject/components/tpm 1_0_5
UCP UCP-1_3_4-ITI.zip eslap://c2netproject/components/ucp 1_3_4

Deployment Manifest

Configuration Parameters

The service is configured to be deployed with the following parameters:

  "configuration": {
    "resources": {},
    "parameters": {
      "dssql": {
        "proxyTcpDssql": "{\"req_dssql2mdbw\":{\"port\":3306}}",
        "dbWatcherDelay": 15000
      },
      "acs": {
        "dbWatcherDelay": 15000
      },
      "taskexecutor": {
        "proxyTcpMariaWrapper": "{\"maria_wrapper\":{\"port\":3306}}"
      },
      "mariadbwrapper": {
        "proxyTcpMariadbwrapper": "{\"rep_mdbw2dssql\":{\"port\":3306}}",
        "filesToLoad": [
          "sqlFiles_base/c2net_prepare.sql",
          "sqlFiles_dkms/c2net_dkms_schema.sql",
          "sqlFiles_dkms/c2net_dkms_data.sql",
          "sqlFiles_opt/c2net_prepare_upv.tx_si.sql",
          "sqlFiles_opt/insert_algorithms.sql",
          "sqlFiles_base/insert_pilot1.sql",
          "sqlFiles_base/insert_pilot2.sql",
          "sqlFiles_base/insert_pilot3.sql",
          "sqlFiles_base/insert_pilot4.sql",
          "sqlFiles_base/c2net_check.sql"
        ]
      },
      "solvermanager": {
        "dbWatcherDelay": 15000
      },
        "ucp":{
          "usersToLoad":[
           "true"
          ]
        }
      }

Domain Creation and Linking

This options is only valid when deploying the service in the ECloud. It is not needed in the Local-Stamp.

The manifests required to create the domain links are:

.
└──── domain
    ├── c2net_service
    │   ├── deployment             (1)
    │   │   └── Manifest.json      
    │   ├── link                   (2)
    │   │   └── Manifest.json      
    │   └── resources              (3)
    │       ├── serverCert
    │       │   └── Manifest.json         
    │       └── vhost
    │           └── Manifest.json          
    ├── c2net_service_nocert
    │   ├── deployment             (4)
    │   │   └── Manifest.json      
    │   ├── link                   (5)
    │   │   └── Manifest.json      
    │   └── resources              (6)
    │       ├── serverCert
    │       │   └── Manifest.json         
    │       └── vhost
    │           └── Manifest.json  
    └──c2net_dataservice
        ├── deployment             (7)
        │   └── Manifest.json      
        ├── link                   (8)
        │   └── Manifest.json      
        └── resources              (9)
            ├── serverCert
            │    └── Manifest.json                
            └── vhost
                └── Manifest.json

Where :

  1. Deployment of the c2net_service inbound resource
  2. Manifest to link the domain with the c2net service with channel "portal"
  3. "c2net_service" manifest, in order to register the inbound and certificate in ESLAP
  4. Deployment of the c2net_service_nocert inbound resource
  5. Manifest to link the domain with the c2net service with channel "portal"
  6. "c2net_service_nocert" manifest, in order to register the inbound and WITHOUT certificate in ESLAP
  7. Deployment of the c2net_dataservice inbound resource
  8. Manifest to link the domain with the c2net data service with channel "pubsub"
  9. "c2net_dataservice" domain manifest, in order to register the inbound and certificate in ESLAP