Jump to: navigation, search

Configuring BDS for on-premise deployment

After the Configuration prerequisites are met, you can configure the Billing Data Server (BDS) for on-premise deployment. The following steps outline the configuration process for deploying BDS on-premise:

  1. Create or put the tenant template in the ./cloudbilling-prem.local/templates/ folder. Use this format to name the template:
    tenant_<short_tenant_name>.tpl, that is, tenant_acme.tpl.
  2. Use the bundled ./cloudbilling-prem.local/etc/gvars.py file for the initial configuration. See Global variables for parameter descriptions. Launch BDS in configuration mode by running the ./cloudbilling-prem.sh config file and wait for the interactive prompt to appear.
  3. Create encryption keys.
    [vagrant@22175551cb8b brs]$ python /usr/lib/python2.7/site-packages/keyczar/keyczart.py create --location=/vagrant/etc/crypto --purpose=crypt --name="BRS keyset"
    [vagrant@22175551cb8b brs]$ python /usr/lib/python2.7/site-packages/keyczar/keyczart.py addkey --location=/vagrant/etc/crypto --status=primary
    [vagrant@22175551cb8b brs]$ ls /vagrant/etc/crypto 1 meta
  4. Encode the required passwords with the generated key.
    [vagrant@796cd88209be brs]$ pwd
    [vagrant@796cd88209be brs]$
    brsctl.py encrypt
    utils.py:__zk_lock_get: Connected to Zookeeper at
  5. For the first deployment, import the configuration templates. You must exit the configuration mode and launch reset.
    This will reset the configuration to match the configuration that is in the templates, including the current ETL timestamps.
    [genesys@vcd-cat-u004 prem-demo]$ ./cloudbilling-prem.sh reset
  6. Check the output for any errors below the line “Main run, should not produce any errors below this message”.
    If you haven’t yet imported the tenant template, you’ll see the following error: “Cannot read file /vagrant/templates/tenant_*.tpl”.
  7. Import the configuration templates.
    $ /vagrant/bin/reset.sh
  8. Launch the configuration mode again by using the ./cloudbilling-prem.sh config file, and then verify that the templates are loaded.
    $ ./brsctl.py dataset -l
    $ ./brsctl.py metric -l
    $ ./brsctl.py location -l
    $ ./brsctl.py tenant -l

The detailed steps for configuring BDS are described in the subsequent sections:


Comment on this article:

blog comments powered by Disqus
This page was last modified on December 19, 2018, at 09:43.