I was told by support that only a standalone Chef server is compatible/supported with the push jobs server. That's unfortunate as regardless of the architecture of Chef server you choose, you still can have a need for push jobs to trigger Chef client runs (or whatever).
I'm able to work around this by changing some configs...
/var/opt/opscode/nginx/etc/addon.d/10-push_jobs_upstreams.conf: change the upstream server to a specific Chef frontend server.
/etc/opscode-push-jobs-server/opscode-push-jobs-server-running.json: change the vip and server_name_advertised to the same specific Chef frontend server.
If the push jobs server can't be truly HA, can the VIP setting at least be overridden via opscode-push-jobs-server.rb to prefer a single Chef frontend server?
I was told by support that only a standalone Chef server is compatible/supported with the push jobs server. That's unfortunate as regardless of the architecture of Chef server you choose, you still can have a need for push jobs to trigger Chef client runs (or whatever).
I'm able to work around this by changing some configs...
/var/opt/opscode/nginx/etc/addon.d/10-push_jobs_upstreams.conf: change the upstream server to a specific Chef frontend server. /etc/opscode-push-jobs-server/opscode-push-jobs-server-running.json: change the
vipandserver_name_advertisedto the same specific Chef frontend server.And that's really enough. Unfortunately, you can't simply override the vip setting in opscode-push-jobs-server.rb as it takes it from the Chef server's
api_fqdnsetting (ala https://github.com/chef/opscode-pushy-server/blob/master/omnibus/files/pushy-server-cookbooks/opscode-pushy-server/libraries/pushy_server.rb#L73), which changing that would potentially upset other Chef server operations.If the push jobs server can't be truly HA, can the VIP setting at least be overridden via opscode-push-jobs-server.rb to prefer a single Chef frontend server?