Integration is set up while creating a service processing module in BILLmanager, Integration → Service processing modules → Create. The processing module adding wizard consists of four steps:
- Step 1. Product type. Select the Virtual Data Center product type.
- Step 2. Processing module. Select the OpenStack processing module.
- Step 3. Configuring the integration. Enter the information required for integration with OpenStack.
- Step 4. Parameters of the service processing module. Configure internal (within BILLmanager) parameters of the service processing module.
Note
Before you start, you need to purchase the license in your Client area eu.ispsystem.com.
Configuring the integration
Specify the following parameters:
- OpenStack version — the OpenStack version for which the processing module will be configured. The module is guaranteed to work only with Pike and Wallaby versions;
- URL — the address to connect to the API. Specify the URL of the server on which the OpenStack control panel is installed;
- Username — the name of the account for authorization in OpenStack. Use an account with administrator permissions;
- Password — the password for the account;
- OpenStack domain — the domain on the OpenStack side to host a virtual data center (VDC). Specify the domain if you are using a multi-domain architecture. You can leave the field blank. In this case the default domain will be used: "Default";
- Private networks — networks for allocating subnets that clients will be able to use when creating VDC networks;
- Enable oversold cores — an option to sell CPU cores with overselling;
- Hypervisor group for oversold cores is one of the hypervisor groups created on the OpenStack side. Cores will be allocated from the specified group to VMs ordered through this processing module.
Note
If a non-existent group is specified, the "Not enough resources to create a new virtual server" error is displayed when adding a virtual machine to the VDC.
When you connect to OpenStack for the first time, the processing module will load the available values of Disk Type, Operating System and Virtual Server Template into BILLmanager. Subsequently, the available values are synchronized by a scheduler job:
/usr/local/mgr5/sbin/mgrctl -m billmgr processing.getconfig >/dev/null 2>&1