openstack team mailing list archive

[Kevin Jackson <kevin@xxxxxxxxxxxxxxxxxxx>]

Hmm, just to add to this - I thought I'd just blindly try an IP address...
just in case... and I could connect...

$ ssh 172.29.1.4
... snip
ubuntu@dev1:~$ logout
Connection to 172.29.1.4 closed.

But looking at nova list - it doesn't show this IP... something is being
quite lazy in getting some updated information...

$ nova list
+--------------------------------------+---------+--------+----------------------------------+
|                  ID                  |   Name  | Status |
Networks             |
+--------------------------------------+---------+--------+----------------------------------+
| b3606cf9-77af-4178-a16f-e92bc458d2db | dev1    | ACTIVE |
development=10.2.0.5             |
+--------------------------------------+---------+--------+----------------------------------+

Cheers,

Kev


On 28 March 2012 12:49, Kevin Jackson <kevin@xxxxxxxxxxxxxxxxxxx> wrote:

> Hi all,
> I've got the following set in my nova.conf:
>
> --auto_assign_floating_ip
>
> and I fire up an instance.
> Everything works, a private IP is assigned... the instance is running...
> but it can take an inordinate amount of time (anywhere upwards of 2 mins,
> sometimes a lot longer) to associate a floating IP automatically.
>
> Anybody else experienced this?  Any clues on what I can do to troubleshoot
> this?  What is the condition when a Floating IP is assigned?  I've seen it
> assign Floating IPs very quickly when it is still Booting, not Active, say.
> Is it dependent on anything within the Instance itself?
>
> Cheers,
>
> Kev
> --
> Kevin Jackson
> @itarchitectkev
>



-- 
Kevin Jackson
@itarchitectkev