Network/broadcast addresses can be associated by AssociateAddress
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Ivan Kolodyazhny | ||
Diablo |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Hi,
As I mentioned in the discussion of:
https:/
currently AllocateAddress can return network or broadcast addresses, and
furthermore they can be associated to instances.
Please see the bottom 'euca-associate
calls. In the case below, 10.6.0.0 was associated to an instance.
I think it's better avoiding allocation of network and broadcast addresses
as early as we can, maybe in AllocateAddress call.
The problem is, that Floating IP netmask information is not stored anywhere currently.
An easy workaround could be just excluding Floating IPs with the maximum and minimum 'id's from the query used
in floating_
But, this is stupid.
Another idea is that excluding network and broadcast addresses
from inserting into 'floating_ips' table in 'nova-manage floating create'.
What do you think about?
root@shayol:
iny
RESERVATION r-19tfo8qv admin default
INSTANCE i-00000001 ami-250c5dc3 scheduling i
toumsn_01 (admin, None) 0 m1.tiny 2011-04-
zone
root@shayol:
RESERVATION r-19tfo8qv admin default
INSTANCE i-00000001 ami-250c5dc3 10.0.0.3 10.0.0.3 r
unning itoumsn_01 (admin, shayol) 0 m1.tiny 2011-04-01T17:04
:51Z nova
root@shayol:
udhcpc (v1.17.2) started
Sending discover...
Sending select for 10.0.0.3...
Lease of 10.0.0.3 obtained, lease time 120
starting DHCP forEthernet interface eth0 [ OK ]
cloud-setup: checking http://
cloud-setup: successful after 1/30 tries: up 38.21. iid=i-00000001
cloud-setup: cloudinit: getting ssh keys: [0=itoumsn_01]
stty: /dev/console
generating DSS host key [WATING].. [ OK ]
generating RSA host key [WATING].. [ OK ]
startup dropbear [ OK ]
stty: /dev/console
startup inetd [ OK ]
stty: /dev/console
startup crond [ OK ]
^C
root@shayol:
Chop wood, carry water.
# df
Filesystem 512-blocks Used Available Use% Mounted on
/dev/vda 47594 34552 10586 77% /
tmpfs 48 0 48 0% /dev/shm
# exit
logout
Connection to 10.0.0.3 closed.
root@shayol:
ADDRESS 10.6.0.0 None (admin)
ADDRESS 10.6.0.1 None (admin)
ADDRESS 10.6.0.3 None (admin)
*** AllocateAddress returns sequentially by first hit strategy,
and thus we got '10.6.0.0' ***
root@shayol:
ADDRESS 10.6.0.3 i-00000001
root@shayol:
ADDRESS 10.6.0.0 None (admin)
ADDRESS 10.6.0.1 None (admin)
ADDRESS 10.6.0.3 i-00000001 (admin)
root@shayol:
ADDRESS 10.6.0.0 i-00000001
root@shayol:
RESERVATION r-19tfo8qv admin default
INSTANCE i-00000001 ami-250c5dc3 10.6.0.0 10.0.0.3 r
unning itoumsn_01 (admin, shayol) 0 m1.tiny 2011-04-01T17:04
:51Z nova
*** 10.6.0.0 is the network address in this Floating IP space! ***
Related branches
- Josh Kearney (community): Approve
- Matt Dietz (community): Approve
- Mandell (community): Approve (community)
- Vish Ishaya (community): Needs Fixing
- Devin Carlen (community): Approve
- Masanori Itoh: Pending requested
-
Diff: 41 lines (+7/-2)3 files modified.mailmap (+1/-0)
Authors (+1/-0)
bin/nova-manage (+5/-2)
Changed in nova: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in nova: | |
assignee: | nobody → Ivan kolodyazhny (e0ne) |
status: | Confirmed → In Progress |
Changed in nova: | |
status: | In Progress → Fix Committed |
status: | Fix Committed → In Progress |
Changed in nova: | |
status: | In Progress → Fix Committed |
Changed in nova: | |
status: | Fix Committed → In Progress |
Changed in nova: | |
milestone: | none → essex-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-3 → 2012.1 |
@Ivan: could you refresh your merge proposal and set it to "Needs review" ? Or did you stop working on that ?