Re: AWS deployment manifest with HAproxy

CF Runtime

Also Stephen, the templates by default attempt to use an ELB named
cfrouter. So if you want to try to use an ELB again, just create one with
that name and when you deploy BOSH should connect it to your routers.

In either case, you shouldn't need to worry about the DEAs, those are
behind the routers. The only thing the load balancer talks to are the

CF Release Integration Team

On Mon, Aug 3, 2015 at 12:50 AM, Amit Gupta <agupta(a)> wrote:

Hi Stephen,

You generally never want to alter the manifest templates unless you're
making a PR with general improvements to the templates. Customizing your
own deployment should be done either within your stub(s), or modifying your
spiff-generated manifest with your desired changes before deploying.

Try making the following additions to your stub:

- name: ha_proxy_z1
instances: 1
- name: ha_proxy_z1_elastic
static_ips: [YOUR_STATIC_IP_HERE]
- name: cf1
default: [gateway, dns]

- name: ha_proxy_z1_elastic # Add this network to the existing cf1 and
cf2 networks, don't remove those
type: vip

- name: router_z1
elbs: []
- name: router_z2
elbs: []

See if that works for you. You will need to make sure that you've
configured DNS records so that your system domain and app domains point to
YOUR_STATIC_IP for ha_proxy. If you're already using as your system and apps domains, then this will
work without having to create any DNS records.


On Sun, Aug 2, 2015 at 11:11 PM, Stephen Knight <sknight(a)>

Hi All,

The default manifests for CF seem to use ELB's on AWS for load balancing,
I am still getting to grips with manifests so in the meantime, can anyone
tell me how you would insert an HAproxy with an elastic IP into a standard

And should it go in the stub or in the cf-infrastructure-xxx.yml file? As
well as ensuring that the DEA pool goes behind the LB pair?

I'm using spiff as per the deployment instructions on Github, filling out
the spec/fixtures/stub but I still can't get HAproxy to deploy despite
trying to munge something together from other manifests.


cf-dev mailing list

cf-dev mailing list

Join to automatically receive all group messages.