After configuring relevant paths as described in Global variables, you must provision the global settings for configuring the Billing Data Server (BDS) for deployment. Global settings are located in three sections:
Each section is provisioned in three steps:
- Generate a template for the section.
- Edit the template.
- Import the template into configuration.
The default globals templates for on-premises deployments are added to the ./cloudbilling-prem.local/templates/globals.tpl file during deployment if it does not exist.
Metric, region, and location templates are part of the delivery bundle and are available immediately after deployment in the ./cloudbilling-prem.local/templates/ directory. You can either edit the templates in that directory and import them or generate them again by using the admin tool.
To generate the template, run the admin utility with the template command. For example:
brsctl.py template -t globals -f /vagrant/templates/template_globals.tpl
The entire globals section is contained in one template. You must generate and import a separate template for each dataset and metric in the datasets and metrics sections.
You must configure the name and access credentials for the s3 bucket, sftp destination, and tenant Configuration Management Environment and Genesys Info Mart (GIM) credentials. BDS expects to use the same service account credentials for each tenant's Configuration Management Environment and each tenant's GIM instance.
A metric template must be imported for each metric supported by BDS.
A dataset template must be imported for each dataset that BDS extracts.
The etc directory of the BDS installation contains pre-defined region and location templates. They can be edited and imported, or admin utility's template command can be used to regenerate the templates.
The next step is to Provision the location and tenant.