New Charm: Elastic Load Balancer (ELB)

[Clint Byrum]

This charm is EC2 specific. It makes use of the EC2 ELB tools to add the instance that it is being run on into an ELB.

[Juan L. Negron (negronjl)]

Hi Clint:

This charm is really cool but I don't think I can promulgate it until a better user experience can be devised to remove instances from ELB when relation has departed/broken.

The way I am looking at this is from a user-experience point where there needs to be manual intervention to remove load balanced instances once they have been removed ...

Until this issue has been addressed I wouldn't recommend promulgating this charm. Of course, I am only one of many charmers that can easily override me. I am merely stating _my_ opinion on this matter here.

-Juan

[Juan L. Negron (negronjl)]

Hi all:

As it turns it out, it was my environment that was misbehaving and not the ELB charm. I am re-testing this set up again and will shortly re-review this charm.

-Juan

[Juan L. Negron (negronjl)]

Hi Clint:

My first test may not have been valid as my testing environment was acting erratic.
I have fixed my testing environment and re-tested the charm. Here are my findings:
- I followed the steps in your README and I get a start-error in the elb charm.
--- Further examination of the charm.log and I find that config-changed is failing with the following error:
--- /var/lib/juju/units/elb-0/units/elb-0/charm/hooks/config-changed: 40: /var/lib/juju/units/elb-0/units/elb-0/charm/hooks/config-changed: availability_zones: parameter not set

I checked config-changed and see that availability-zones is being set in config.yaml and being defined as azl in config-changed and not as availability_zones.

Would you look into this when you get a chance and resubmit?

Thanks,

Juan

[Clint Byrum (clint-fewbar)]

I have to agree Juan. Basically this bug is blocked on:

https://bugs.launchpad.net/juju/+bug/872264