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



File Date Author Commit
code 2018-02-01 Daniel Machancoses Daniel Machancoses [d50d90] Improved start-up time by splitting scripts, no...
deployment 2018-02-01 Daniel Machancoses Daniel Machancoses [d50d90] Improved start-up time by splitting scripts, no...
service 2018-02-01 Daniel Machancoses Daniel Machancoses [d50d90] Improved start-up time by splitting scripts, no...
Manifest.json 2018-02-01 Daniel Machancoses Daniel Machancoses [d50d90] Improved start-up time by splitting scripts, no...
component-builder-script.sh 2018-02-01 Daniel Machancoses Daniel Machancoses [d50d90] Improved start-up time by splitting scripts, no...
readme.md 2018-02-02 Daniel Machancoses Daniel Machancoses [139e11] Updated documentation

Read Me

C2NET Logger

Version 0_0_10

Description

Due to restricted access the Kibana Server, which is inside the Stamp cluster, the C2Net users are not able to access the logs of the components.

The C2NET Service Logger grants access to the logs generated by a specific deployment, which in this case, will include all logs generated by the instances that comprehend the C2NET Service.

Usage

In order to deploy the service, you have to provide three parameters to the logger component:

  • context: Indicating the context string to be filtered.
  • interval: This parameter sets the time period for which the Kibana will refresh the results.
  • KibanaHost: This host resolves to the host where Kibana (and more precisely, elastic search) is located.

The C2NET Logger Component requires several resources, as it contains an own Elastic Search and a Kibana Server.
As an example, this Manifest.json can be used to deploy the service:

 {
   "spec": "http://eslap.cloud/manifest/deployment/1_0_0",
   "servicename": "eslap://c2netproject.eu/services/c2net_logger/0_0_10",
   "name": "c2net-logger",
   "interconnection": true,
   "configuration": {
     "resources": {},
     "parameters": {
       "logger": {
         "context": "slap://c2netproject/deployments/20171218_141634/0662894c",
         "interval": 60000,
         "KibanaHost": "kibana.argo.kumori.cloud",
         "RSAKey": "not implemented yet",
         "RSAPub": "not implemented yet"
       }
     }
   },
   "roles": {
     "logger": {
       "resources": {
         "__instances": 1,
         "__cpu": 4,
         "__memory": 8,
         "__ioperf": 1,
         "__iopsintensive": false,
         "__bandwidth": 1,
         "__resilience": 1
       }
     }
   }
 }

Todo List

  • ID-RSA Management: Nowadays the id-rsa key to authenticate into Kibana Host is placed inside the component. This should be a parameter passed along in the deployment, together with the id_rsa-pub key.
  • Logger Runtime: Create a docker image containing ELK, to avoid be included in the component.
  • Access Rights: Implement authentication, check module X-Pack (https://www.elastic.co/guide/en/x-pack/current/setting-up-authentication.html)