Add floating IP support

[Jacek Nykis]

Currently if we want to redeploy an environment we have to manually reassign floating IPs to new units.

Please add support for assigning floating IPs using juju commands.

[Matt Rae (mattrae)]

Using juju 1.18.1 with "use-floating-ip: true" juju bootstrap and juju add-machine allocate a floating ip but it does not get associated successfully.

If I load the instances page in openstack the floating ip shows it is assigned for a short time then it disappears and must be associated manually before "juju status" will work.

Openstack is havana from the cloud archive:
2013.2.2-0ubuntu1~cloud0

[Matt Rae (mattrae)]

Noting that openstack havana is deployed with neutron networking (quantum-gateway charm)

[Matt Rae (mattrae)]

Example from juju status.. machine 0 has a floating ip, machine 1 was a given a private ip although a floating ip was allocated in openstack.

$ juju status
environment: openstack
machines:
  "0":
    agent-state: started
    agent-version: 1.18.1
    dns-name: 172.35.20.136
    instance-id: f1e9e700-d038-446a-92db-d4637b468d94
    instance-state: ACTIVE
    series: precise
    hardware: arch=amd64 cpu-cores=1 mem=2048M root-disk=20480M
  "1":
    agent-state: started
    agent-version: 1.18.1
    dns-name: 192.168.0.4
    instance-id: 47fe46fb-183f-4311-b144-69e5236d0185
    instance-state: ACTIVE
    series: precise
    hardware: arch=amd64 cpu-cores=1 mem=2048M root-disk=20480M

[Matt Rae (mattrae)]

More example of intermittent floating ip association

juju bootstrap shows only a private ip:

$ juju -v bootstrap --metadata-source /home/joeuser/.juju
Launching instance
 - c551977d-bb16-423a-ace2-ae45347373b4
Waiting for address
Attempting to connect to 192.168.0.2:22
^CInterrupt signalled: waiting for bootstrap to exit
ERROR bootstrap failed: interrupted
Stopping instance...
Bootstrap failed, destroying environment
ERROR interrupted

A second attempt directly after shows floating ip as well:

$ juju -v bootstrap --metadata-source /home/joeuser/.juju
Launching instance
 - 498a9dac-1c73-4fdd-b476-0cab66b734dd
Waiting for address
Attempting to connect to 192.168.0.2:22
Attempting to connect to 172.35.20.143:22

Even though it shows the floating ip in 'juju status', the association failed and had to be made manually

[Heather Lanigan (hmlanigan)]

We don't believe this is an issue in Juju 2.x. Please add details if you disagree.

[James Troup (elmo)]

| james@malefic:~$ juju help commands | egrep -i "(floating|ip)"
| james@malefic:~$ juju --version
| 2.1.1-xenial-amd64
| james@malefic:~$

As the original bug report said; we would like Juju to have commands
to manipulate floating IPs (a construct available in almost all cloud
providers). Nothing has changed since then.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.

[John A Meinel (jameinel)]

@hloeung we currently have support for 'constraint=allocate-public-ip=True'. Is the idea that you would like to be able to allocate an explicit ip and be able to move it between instances?

[Haw Loeung (hloeung)]

@jameinel, sorry for the late reply. I must have missed this comment.

What we're after is actually to be able to use things such as AWS Elastic IPs and Azure Public IPs so that they're attached to VMs provisioned by Juju and persist across stop & start operations.

Right now, whenever we have to stop & start operations, VMs are assigned different public IPs and we're forced to update it in various places such as nagios checks and DNS (e.g. HAProxy units).

It's not so much as to be able to move between instances but rather so we don't have to keep having to update IPs on when we need to perform operations within the public cloud where the VMs can have their assigned IPs change.