-
Notifications
You must be signed in to change notification settings - Fork 1
DISCO Backend Configuration
The configuration of DISCO happens in one single file, sm.cfg. Most configurations can remain as they are,
The provided sm.cfg file from the /etc subdirectory in the repository is shown in this paragraph (without comments). The individual parameters to be changed will be explained after it.
[general]
log_file=sm.log
manager=openstack
[service_manager]
manifest=/home/ubuntu/disco/etc/service_manifest.json
design_uri=https://keystone.cloud.switch.ch:5000/v2.0
[service_manager_admin]
register_service=False
service_token=<keystone token>
service_tenant_name=<keystone tenant>
[disco]
framework_directory=/home/ubuntu/disco/sm/managers/data
sm.cfg is partitioned into 4 sections: [general],[service_manager],[service_manager_admin] and [disco]. The most important ones are the second and the fourth. Still, all of them should be explained.
In the general section, basic settings for the Service Manager are declared such as the log file or the type of Service Manager to start.
The setting log_file defines the path to the log file where logging should take place. If the path is given as a relative path, the origin is taken as the DISCO main directory.
manager is an information for Hurtle which type of Service Manager should be used for this service. In this case, only the openstack service manager is provided within this repository so no need to change anything at this point.
The section service_manager configures the actual service. Both settings, manifest and design_uri, have to be adjusted to the actual environment.
The service_manifest.json file, whose path is to be provided with the setting manifest, is the service description of DISCO. Keep in mind that Hurtle is designed to orchestrate any generic service. The file service_manifest.json doesn't have to be changed anymore: it basically defines the endpoint of the service (in this case "/disco") and the service parameters which can be provided. This file is located in the /etc folder of DISCO's repository.
Over design_uri, the service will be provided with OpenStack's identity endpoint. This is the key setting for DISCO in order to connect to the location where the virtual clusters are to be deployed. Over OpenStack's Horizon dashboard, this setting can be retrieved under Project -> Compute -> Access & Security -> API Access in the row Identity.
This again is a Hurtle-specific section. Here, the service - i.e. DISCO - could be registered within OpenStack. However, this possibility is currently not provided. This is indicated with the setting register_service set to false.
The actual DISCO service needs but one setting, called framework_directory. Here, the location of the /sm/managers/data directory has to be indicated. The reason is that every component (i.e. framework such as Hadoop, Spark, ...) has its templates within that directory.
After configuring DISCO backend with the sm.cfg file, it can be started with the command service_manager -c /path/to/sm.cfg