dataplaneapi in read only mode

[pontostroy]

Hello, i want to use dataplaneapi only for fetching backed servers.
Is it possible to configure it to do not modify haproxy config file?
Now I see this in my file

# _md5hash=5633fd65bc4d17590eb9365cb8caecfd
# _version=2
# Dataplaneapi managed File
# changing file directly can cause a conflict if dataplaneapi is running

My config

program dataplaneapi 
  command dataplaneapi --host 0.0.0.0 --port 5555 --haproxy-bin /usr/sbin/haproxy --config-file /etc/haproxy/haproxy.cfg -r 'systemctl status haproxy' -s 'systemctl status haproxy' --reload-delay 3600 --userlist api_users
  no option start-on-reload

[mjuraga]

Hi, currently this is not possible, but we can see this being an interesting feature to add in some of the future releases.

[aderumier]

Hi,
I'm also using api mainly read only, or to put some servers in maintenance in a backend.

previously, I was using dataplane api 2.1, and config file was not changed
It seem to be changed since 2.2 and this commit
04964ca

I'm pushing config with puppet, and this is really a problem, as dataplane add theses lines on haproxy reload, so puppet is changing the file again, reload haproxy, . then dataplane write again the file, ....in a infinite change/reload loop.

[discostur]

Also using ansible to deploy / manage haproxy config file. Read-only would be a really great feature +1

[lakshmoji-kallidus]

Hi Team

# _md5hash=5633fd65bc4d17590eb9365cb8caecfd
# _version=2
# Dataplaneapi managed File
# changing file directly can cause a conflict if dataplaneapi is running

Though we push haproxy.cfg with the chef. The last step on config will reload haproxy then dataplane write again the file, ....in an infinite change/reload loop

To resovle this can we run hapaxy-2.6 and datapalneapi API v2.0.1 ?

[mjuraga]

Hi, the reason for rewriting is that we use inotify to reload the parser and the client when the file changes externally. And this writes a new md5hash. To disable this you can use following options in your dataplaneapi.yaml:

dataplaneapi:
  disable_inotify: true

Or run the dataplaneapi with --disable-inotify CLI option.

[titansmc]

Still there is a case where we:

1- Drain a node through the web interface
2- Use dataplaneapi to configure some maps and reload

and now the initial drain is gone

[broxio]

I'm really keen for this feature, just read-only would does the job, I'm using saltstack to render the config and this will cause config drifted without intention.

[brenc]

Attempting to deploy dataplaneapi today for a project and ran into this too. I'm not planning on using it readonly but I definitely do not want my configs to be updated since I deploy with Ansible. dataplaneapi also creates a bunch of files and dirs in my haproxy config dir which isn't good either. This is very odd and unexpected behavior especially on *nix systems.

Readonly mode would be good but even better would be treating the haproxy config dir as readonly and generating runtime configs under /var/run/dataplaneapi or something like that. Every time I try to deploy the api (third or fourth time since release) I run into this and end up backing it all out and writing my own custom thing.

[sawall]

I'd love this feature. We deploy with ansible then use consul-template to update haproxy.cfg and other configs across our infra, and have built in a lot of orchestration to optimize for user experience by minimizing reloads. This is in part because we use websockets extensively. In the case of HAProxy this means that we need to let new configs across multiple regions stabilize over the course of a couple minutes when new servers come up and then perform staggered reloads. We often delete and add multiple servers at once and using the Data Plane API for this would mean lots of reloads.

We currently use the HAProxy Runtime API to monitor health and status but want to use the HAProxy Data Plane API to get the more detailed information that it provides. But we have found that the Data Plane API actively fights with changes that we make to configurations via consul-template, so it's unfortunately a non-starter for us to use without a read-only mode.