This PR adds a new setting to ansible/etc/globals.yaml: enable_killbill. When set to true, the default, Kill Bill will be installed.
I initially attempted to have Kill Bill installed in the same docker compose file as the rest of the concertim components. However, I ran into issues with getting the Kill Bill and KAUI containers to run on anything other than port 8080. The solution I settled on was to have them run in a separate docker compose file, using a bridged network.
As kolla-ansible disables docker's default bridge network, the Kill Bill containers will not be able to initiate requests to the outside world. Though they can initiate requests to services specified in the same docker compose file and also to containers running on the same host machine. This seems to be sufficient for Kill Bill and is the setup that is currently in use on M2.
The ansible/etc/globals.yaml file also contains settings to control which host interface and port the Kill Bill and KAUI services bind to. These are killbill_port, killbill_interface, kaui_port and kaui_interface.
A secure password for the killbill database is created in the same manner as for Concertim.
The default /opt/concertim/etc/openstack_service/config.yml file is now updated working values where possible. These include working settings for the concertim section and the killbill section. The installer will still need to edit this file to provide values for the openstack and rmq sections.
The way that the concertim containers are configured with the IP addresses of the other containers has changed. We now use extra_hosts configuration and have them communicate via service name. This was largely done to help write the documentation for such settings, but going forward will also allow separate installation or a move back to a bridge network mode.
This PR adds a new setting to
ansible/etc/globals.yaml
:enable_killbill
. When set totrue
, the default, Kill Bill will be installed.I initially attempted to have Kill Bill installed in the same docker compose file as the rest of the concertim components. However, I ran into issues with getting the Kill Bill and KAUI containers to run on anything other than port
8080
. The solution I settled on was to have them run in a separate docker compose file, using a bridged network.As kolla-ansible disables docker's default bridge network, the Kill Bill containers will not be able to initiate requests to the outside world. Though they can initiate requests to services specified in the same docker compose file and also to containers running on the same host machine. This seems to be sufficient for Kill Bill and is the setup that is currently in use on M2.
The
ansible/etc/globals.yaml
file also contains settings to control which host interface and port the Kill Bill and KAUI services bind to. These arekillbill_port
,killbill_interface
,kaui_port
andkaui_interface
.A secure password for the killbill database is created in the same manner as for Concertim.
The default
/opt/concertim/etc/openstack_service/config.yml
file is now updated working values where possible. These include working settings for theconcertim
section and thekillbill
section. The installer will still need to edit this file to provide values for theopenstack
andrmq
sections.The way that the concertim containers are configured with the IP addresses of the other containers has changed. We now use
extra_hosts
configuration and have them communicate via service name. This was largely done to help write the documentation for such settings, but going forward will also allow separate installation or a move back to a bridge network mode.