ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Configure DA proxy in an open stack project environment.

book

Article ID: 199253

calendar_today

Updated On:

Products

CA Infrastructure Management CA Performance Management - Usage and Administration DX NetOps

Issue/Introduction

We have an openstack environment and a VM environment.

In openstack there is a concept of "floating IP’s" for a server instance.

The server is assigned a private IP that is only good within a "project" or logical group of servers.

Anything outside of that project would be reached via the floating ip. (I think of it like a NAT). 


In most cases the DA’s and the proxy would be in the same project, so most of this would be seamless to CAPM.


But, since our proxy is outside of the openstack environment it would have to use this floating IP to communicate back to the DA's.

Cause

The floating and private IP’s within the openstack project are invisible to the applications running on the VM, so the consul service will use the only address in the ifconfig to BIND

Environment

Release : 20.x

Release : 3.x

Component : PERFORMANCE MANAGEMENT INSTALLATIONS/UPGRADES

Resolution

On the DA’s only:

Edit the service startup parameters to include an “-advertise” argument with the project external IP’s.

/etc/systemd/system/consul.service

Change

[Service]

ExecStart=/opt/CA/daproxy/bin/consul agent -bind=<local-IP> -disable-host-node-id -config-dir=/opt/CA/daproxy/conf

To

[Service]

ExecStart=/opt/IMDataAggregator/consul/bin/consul agent -bind=<local-IP> -advertise=<EXTERNALIP> -disable-host-node-id -config-dir=/opt/IMDataAggregator/consul/conf

 

Additional Information

Please note: This procedure will have to be done after each upgrade of CAPM.

 

https://www.openstack.org