Jump to: navigation, search

Installing Billing Data Server

Before you install the Billing Data Server (BDS), the System Requirements must be met.

During BDS deployment, the following directories on the deployment host are created:

  • ./cloudbilling-prem.local/etc : BDS passwords encryption keys, configuration dump, and the gvars.py file in the Docker container mapped into /vagrant/etc.
  • ./cloudbilling-prem.local/templates : All BDS configuration templates in the Docker container mapped into /vagrant/templates.
  • ./cloudbilling-prem.local/log : Location for all log files in the Docker container mapped into /vagrant/log.
  • ./cloudbilling-prem.local/data : Storage for persistent non-configuration data, that is, data extracts in the Docker container mapped into /vagrant/data.

Ensure that for BDS configuration you use Docker container paths, that is, set /vagrant/log/bds.log as log file instead of ./cloudbilling-prem.local/log/bds.log and so on.

Genesys recommends that the gvars.py file has the locations for log storage and for data storage specified as below:

  • log_file=/vagrant/log/
  • local_cache=/vagrant/data/

To install the BDS application, follow these steps:

  1. Download the delivery package.
    Genesys sends you the delivery package, which you can download through FTP server. The name of the delivery package includes a version number in the format IP_BDS_PRR_v0.0.1304.18_dockerlinux.tar.gz (for simplicity, it is called “deploy_prem.tgz” as shown in the following sample screen shot).
    Installation 1.png
  2. Transfer the delivery package (archive) contents to the target host through any meaningful process.
    After you've transferred the delivery package, all further actions must be executed in the home directory of the application user (the non-root local user that has access to Docker and is used to run the BDS container).
  3. Create a directory, cloudbilling-prem.
  4. Unpack the contents of the archive to the cloudbilling-prem directory. The unpacking takes very little time.
    Installation 3.png
    The contents are now in the target host.
    Installation 4.png
  5. Navigate to the devbox directory by typing: cd devbox.
  6. Type ls to confirm if the deploy_prem.script script is displayed.
    Installation 5.png
  7. Run the deploy_prem.script script. The script does a few things:
    • Creates the ~/cloudbilling-prem.local directory structure if it does not exist.
    • Adds a new image to the local docker.
    • Unpacks bundled generic templates to the ~/cloudbilling-prem.local/templates/ folder (overwriting existing files does not affect the tenant templates).
    • Adds default config files for premises to the ~/cloudbilling-prem.local/etc/ folder if they do not exist.
    Installation 6.png
  8. Check the uploaded images that are displayed in the registry.
    Images are assigned an ID, for example, C8f2807d883b, as shown in the following screen shot. Any image from a previous attempt is also displayed.
    Installation 8.png
    The deploy script also assigns a prem tag to the latest uploaded image. This tag defines the particular image that is used to run the application.
    The script also creates a startup link ~/cloudbilling-prem.sh that is used for further interaction with BDS.
  9. Run the ./cloudbilling-prem.sh config file.
    After you successfully execute the cloudbilling-prem.sh script, you are logged into the Docker container as a ‘vagrant’ user. Errors that might occur at this point will not affect the installation.
    Installation vagrant.png

After you install the BDS application, you must perform the tasks in the configuration prerequisites section, and then configure the BDS application.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on June 27, 2018, at 11:58.