... | @@ -5,26 +5,36 @@ |
... | @@ -5,26 +5,36 @@ |
|
|
|
|
|
Most CII services (not: telemetry and alarms) come as part of the DevEnv installation, however some post-installation set-up is needed before they can be used.
|
|
Most CII services (not: telemetry and alarms) come as part of the DevEnv installation, however some post-installation set-up is needed before they can be used.
|
|
|
|
|
|
As of DevEnv 3.4, the post-install tool is available as puppet scripts.
|
|
|
|
To get hold of the latest post-installation tool, use the following update command.
|
|
|
|
As of DevEnv 3.5, the post-install tool will check for updates automatically (if you are inside the ESO network), and you do not need to execute the yum update command.
|
|
|
|
|
|
|
|
The update command has to be executed as root:
|
|
**Preparation**
|
|
|
|
|
|
|
|
On DevEnv 3.4, first execute this command (as root)
|
|
```
|
|
```
|
|
yum -y install elt-ciisrv-postinstall
|
|
yum -y install elt-ciisrv-postinstall
|
|
```
|
|
```
|
|
|
|
|
|
The post-install command has to be executed as root:
|
|
On DevEnv 3.5, if you are outside ESO, execute this command (as root)
|
|
|
|
```
|
|
|
|
yum -y update elt-ciisrv-postinstall
|
|
|
|
```
|
|
|
|
|
|
|
|
On DevEnv 3.5 inside ESO, and DevEnv 3.6+, there is nothing to do.
|
|
|
|
|
|
|
|
Afterwards, execute this command (as root):
|
|
```
|
|
```
|
|
# /elt/ciisrv/postinstall/cii-postinstall <choose a role>
|
|
# /elt/ciisrv/postinstall/cii-postinstall <choose a role>
|
|
```
|
|
```
|
|
To learn about the options, run the command without arguments.
|
|
To learn about the options, run the command without arguments.
|
|
After that, you will want to start the CII services (unless you have assigned the "groupclient" role to the host).
|
|
After that, you will want to start the CII services (unless you have assigned the "groupclient" role to the host).
|
|
|
|
|
|
### How-to start and stop CII services
|
|
|
|
|
|
|
|
|
|
### How-to start/stop CII services
|
|
|
|
|
|
The cii-services utility lets you start/stop/monitor the CII services. For some operations, it requires root-privileges -> it will show a password prompt when needed.
|
|
The cii-services utility lets you start/stop/monitor the CII services. For some operations, it requires root-privileges -> it will show a password prompt when needed.
|
|
|
|
|
|
|
|
Note: Before using CII services, you or an administrator have to run the CII-post-installation, see [How-to post-install CII services](#how-to-post-install-cii-services)
|
|
|
|
|
|
*status*
|
|
*status*
|
|
This is a feature-centric view, that basically tells you which features you have available. For example, "Blob Values" means that the Distributed File System MinIO (in previous versions: Hadoop) is available for storage of large values and binaries.
|
|
This is a feature-centric view, that basically tells you which features you have available. For example, "Blob Values" means that the Distributed File System MinIO (in previous versions: Hadoop) is available for storage of large values and binaries.
|
|
```
|
|
```
|
... | @@ -45,6 +55,8 @@ To learn about the options, run the command without arguments. |
... | @@ -45,6 +55,8 @@ To learn about the options, run the command without arguments. |
|
|
|
|
|
For more details and examples, see the [cii-services user manual](https://eltjenkins.hq.eso.org/job/CII/job/Docs-Build-Master-Next/lastBuild/artifact/userManual/build/ciiman/html/docs/services.html)
|
|
For more details and examples, see the [cii-services user manual](https://eltjenkins.hq.eso.org/job/CII/job/Docs-Build-Master-Next/lastBuild/artifact/userManual/build/ciiman/html/docs/services.html)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
### How-to get CII Demo apps
|
|
### How-to get CII Demo apps
|
|
|
|
|
|
CII has demo apps that you can download as source, modify, and build yourself. They demonstrate the use of the CII services.
|
|
CII has demo apps that you can download as source, modify, and build yourself. They demonstrate the use of the CII services.
|
... | @@ -66,6 +78,8 @@ Find the build output in ./cii-demo.sh.build.log |
... | @@ -66,6 +78,8 @@ Find the build output in ./cii-demo.sh.build.log |
|
|
|
|
|
After this, you find the list of available demo apps in the (generated) README file. You can at any time modify the sources and rebuild them with "waf build install". Look inside "cii-demo.sh" if unsure.
|
|
After this, you find the list of available demo apps in the (generated) README file. You can at any time modify the sources and rebuild them with "waf build install". Look inside "cii-demo.sh" if unsure.
|
|
|
|
|
|
|
|
Most demo apps require CII Services be running on your host or on another host => Check that the related CII Services (e.g. config service for a a config demo app) are accessible: see [How-to start/stop CII Services](#how-to-start-stop-cii-services)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
### Failure to build ZPB from ICD \[ICD waf build\]
|
|
### Failure to build ZPB from ICD \[ICD waf build\]
|
... | | ... | |