readme.md 221 lines (140 with data), 7.3 kB
ERROR! The markdown supplied could not be parsed correctly. Did you forget to surround a code snippet with "~~~~"?
# C2NET Service Implementation
The C2NET cloud service is implemented and integrated in an incremental and iterative way. This implies to create an initial version of the C2NET service with a subset of its components, and then add new components in new iterations. The aim of this project is to create a common repository to integrate all components within C2NET.
## PHASES
The already integrated components are marked with a check symbol (✔). The actual status of the C2NET service is as follows:
1. **Initial Step**. C2NET service with basic set of PaaS 4 Manufacturing components:
1. UCP
1. CNM ✔
1. ACS ✔
1. DS.sql ✔
1. MariaDBWrapper ✔
2. **OPT Components** :
1. OPC ✔
1. SM ✔
1. PM ✔
1. Job ✔
1. TaskExecutor (with the embedded OptimizationAlgorithms) ✔
3. **DCF Components**:
1. Pub/Sub ✔
1. RM
1. DKMS
1. TPM
1. Mobile Application.
4. **COT Components**:
1. OPP
1. MPE-MD
1. MPE-AA
## INSTRUCTIONS
All repositories, including this c2net-test project, should be cloned into the same folder. We will refer it as
C2NET_HOME. The folder structure is as follows:
C2NET_HOME
.
├── c2net-cpl-paas4man-acs-code
├── c2net-cpl-paas4man-cnm-code
├── c2net-cpl-paas4man-dst-dkms-code
├── c2net-cpl-paas4man-dst-dssql-code
├── c2net-cpl-paas4man-dst-mariadbwrapper-code
├── c2net-cpl-paas4man-jex-jobs-code
├── c2net-cpl-paas4man-jex-taskexecutor-code
├── c2net-cpl-paas4man-ucp-code
├── c2net-cpl-paas4sla-sdk-code
├── c2net-dcf-dcf-rm-code
├── c2net-dcf-msg-queue-code
├── c2net-opt-algorithms-code
├── c2net-opt-poma-opc-code
├── c2net-opt-poma-pomam-code
├── c2net-opt-poma-solvermanager-code
├── c2net-tests
...
The c2net-test folder also contains a components folder where front-end Components are used in this service to test it using HTTP.
More details about how to clone the repositories can be found in the next section.
###Build the service
You may need to be admin:
./C2NET_HOME/c2net-tests/scripts/build.sh
##Verify manifests in the service
./C2NET_HOME/c2net-tests/scripts/validate.sh
###Deploy to local-stamp
Start your local stamp docker, then execute:
./C2NET_HOME/c2net-tests/scripts/deploy_local_stamp.sh
###Test the service
You can use curl or just an explorer:
curl "http://localhost:9000/opc/ping"
and you should get
{
"success":true,
"message":"PONG"
}
### INSTRUCTIONS TO CLONE REPOSITORIES
Execute the following commands form the C2NET_HOME folder:
* UCP
git clone https://{USER}@opensourceprojects.eu/git/p/c2net/cpl/paas4man/ucp/code c2net-cpl-paas4man-ucp-code
* CNM
git clone https://{USER}@opensourceprojects.eu/git/p/c2net/cpl/paas4man/cnm/code c2net-cpl-paas4man-cnm-code
* ACS
git clone https://{USER}@opensourceprojects.eu/git/p/c2net/cpl/paas4man/acs/code c2net-cpl-paas4man-acs-code
* DSSQL
git clone https://{USER}@opensourceprojects.eu/git/p/c2net/cpl/paas4man/dst/dssql/code c2net-cpl-paas4man-dst-dssql-code
* MARIADB WRAPPER
git clone https://{USER}@opensourceprojects.eu/git/p/c2net/cpl/paas4man/dst/mariadbwrapper/code c2net-cpl-paas4man-dst-mariadbwrapper-code
* OPC
git clone https://{USER}@opensourceprojects.eu/git/p/c2net/opt/poma/opc/code c2net-opt-poma-opc-code
* SOLVER MANAGER
git clone https://{USER}@opensourceprojects.eu/git/p/c2net/opt/poma/solvermanager/code c2net-opt-poma-solvermanager-code
* POMA MANAGER
git clone https://{USER}@opensourceprojects.eu/git/p/c2net/opt/poma/pomam/code c2net-opt-poma-pomam-code
* JOB
git clone https://{USER}@opensourceprojects.eu/git/p/c2net/cpl/paas4man/jex/jobs/code c2net-cpl-paas4man-jex-jobs-code
* TASK EXECUTOR
git clone https://{USER}@opensourceprojects.eu/git/p/c2net/cpl/paas4man/jex/taskexecutor/code c2net-cpl-paas4man-jex-taskexecutor-code
* PUB/SUB Broker
git clone https://{USER}@opensourceprojects.eu/git/p/c2net/dcf/msg-queue/code c2net-dcf-msg-queue-code
* Resource Manager _(not integrated)_
git clone https://{USER}@opensourceprojects.eu/git/p/c2net/dcf/dcf-rm/code c2net-dcf-dcf-rm-code
`TO BE COMPLETED...`
### DESCRIPTION OF C2NET-TEST FOLDER
The folder structure of this service is as follows:
.
├── components (1)
│ ├── feacsdssql (2)
│ └── jobexfe (3)
├── deployment
│ └── Manifest.json (4)
├── scripts
│ ├── build.sh (5)
│ ├── deploy_local_stamp.sh (6)
│ └── validate.sh (7)
├── service
│ └── Manifest.json (8)
└── readme.md (9)
Where:
1. Folder which contains the front end components.
1. ACS-DSSQL Front End Component
1. JOBEX Front End Component
1. Deployment manifest
1. Build script
1. Deploy script to local-stamp
1. Syntax validator script
1. Service manifest
1. This file
### COMPONENT DEVELOPMENT STATE
|Component Name | Developer | Urn | Version|Integrated | GIT
|--- |--- |--- |--- |---|---
| ucp | linagora | linagora.c2netproject.eu/components/ucp/|0_0_1| | c2net-cpl-paas4man-ucp-code
| cnm | ikerlan | ikerlan/components/cnm/ | 0_0_115| ✔ | c2net-cpl-paas4man-cnm-code
| acs | iti | iti/components/acs/ | 0_0_118| ✔ | c2net-cpl-paas4man-acs-code
| dssql | iti | iti/components/dssql/ | 0_0_129| ✔ | c2net-cpl-paas4man-dst-dssql-code
| mariadbw | iti | iti/components/mariadbwrapper | 0_0_119| ✔ | c2net-cpl-paas4man-dst-mariadbwrapper-code
| opc | cms | cms.c2net/components/opc/ | 0_0_2 | ✔ | c2net-opt-poma-opc-code
| solvermanager| cigip | cigip/components/solvermanager/| 0_0_1 | ✔ | c2net-opt-poma-solvermanager-code
| poma | cms | cms.c2net/components/pomam/ | 0_0_2 | ✔ | c2net-opt-poma-pomam-code
| jobs | iti | iti/components/jobs/ | 0_0_3 | ✔ | c2net-cpl-paas4man-jex-jobs-code
| taskexecutor | iti | iti/components/taskexecutor/ | 0_0_3 | ✔ | c2net-cpl-paas4man-jex-taskexecutor-code
| optimization | upv | _'not a component'_ | - | ✔ | c2net-opt-algorithms-code
| pubsub | atos |atos.c2net/components/pubsub/ | 1_0_0 | ✔ | c2net-dcf-msg-queue-code
| rm | | | | |c2net-cpl-paas4man-dst-dkms-code
| dkms | uninova |uninova.c2netproject.eu/components/dkms/ |0_0_1 | |c2net-cpl-paas4man-dst-dkms-code
| tpm | | | | |
| mobile | | | | |
| opp | | | | |
| mpe-md | | | | |
| mpe-aa | | | | |