Eucalyptus Public IPs should be submitted in CIDR or range notation

Eucalyptus apparently already has some crude support for this in net/vnetwork.c
So you *can* specify CIDR-style notation, like 192.168.0.128/25.

However if you specify a CIDR-style network that's not aligned to the first address, then it leads to a somewhat incorrect result:

so this leads to a correct result:
192.168.0.128/25 = 192.168.0.128 - 192.168.0.255 -> eucalyptus assigns 192.168.0.129 - 192.168.0.254
192.168.0.228/30 = 192.168.0.228 - 192.168.0.231 -> eucalyptus assigns 192.168.0.229 - 192.168.0.230

but this doesn't:
192.168.0.230/30 = 192.168.0.228 - 192.168.0.231 -> eucalyptus assigns 192.168.0.231 - 192.168.0.232
192.168.0.130/25 = 192.168.0.128 - 192.168.0.255 -> eucalyptus assigns 192.168.0.130 - 192.168.1.0
though you could argue that those are incorrect.

We will be adding the ability for the CC to accept ranges of IPs, using only the last octet of the IPs, in a near commit of Eucalyptus. All octets must obviously be between 0 and 255 inclusive. The following will be accepted:

A.B.C.D-A.B.C.E

where D <= E. Multiple ranges can be specified:

A.B.C.D-A.B.C.E V.W.X.Y-V.W.X.Z

where D <= E and Y <= Z.

examples of ranges that will not work:

A.B.C.D-A.B.C.E

where D > E.

A.B.X.D-A.B.Y.E

(only last octet can be used).

If this plan changes during implementation, i'll post a comment here.

committed in eucalyptus revno 926

This bug was fixed in the package eucalyptus - 1.6~bzr930-0ubuntu1

---------------
eucalyptus (1.6~bzr930-0ubuntu1) karmic; urgency=low

  [ Dustin Kirkland ]
  * debian/eucalyptus-url, debian/eucalyptus-cc.install,
    debian/eucalyptus-cc.links, debian/eucalyptus-cc.postinst::
    - fix whitespace, to match other update-motd urls LP: #450449
    - link to ubuntu.com/cloud, which links to our documentation,
      necessary for new UEC admins
    - ensure that it gets installed with executable permissions,
      LP: #444970
  * debian/eucalyptus-udeb.finish-install: fix typo; fix breakage of
    /etc/network/interfaces when nodes are configured with static IP
    addresses, LP: #446023
  * eucalyptus-cc.upstart,
    eucalyptus-cloud.eucalyptus-cc-registration.upstart,
    eucalyptus-cloud.eucalyptus-sc-registration.upstart,
    eucalyptus-cloud.eucalyptus-walrus-registration.upstart,
    eucalyptus-sc.upstart, eucalyptus-walrus.upstart, rules, control:
    - registration of cc/sc/walrus should *only* ever occur on the CLC,
      so these scripts should be moved to the eucalyptus-cloud package,
      LP: #450815
    - starting cc/sc/walrus should *not* depend on eucalyptus-cloud
      running, since these components can be installed on separate
      machines, LP: #450777
    - but if cc/sc/walrus are on a system doing registration, ensure that
      these jobs kick off when "starting" registration
    - allow for whitespace separated list of $CC_IP_ADDR and $SC_IP_ADDR,
      as there can be more than one of these, and admins in multi-cluster
      or multi-component mode would need to register a list
    - use Replaces to ensure upgrades work properly
  * debian/eucalyptus-ipaddr.conf: update inline documentation accordingly
  * debian/eucalyptus-cc.templates: update public_ips instructions in the
    installer to match the new upstream implementation, LP: #438565
  * eucalyptus-common.eucalyptus.upstart: fix unclean package purging,
    which hangs on stopping eucalyptus service

  [ Upstream ]
  * Merge upstream revision 930
  * This snapshot is expected to fix the following bugs:
    - LP: #449944 - fixes remote component bootstrap issue
    - LP: #430852, #401996 - fix handling of security groups for the admin
    - LP: #449948 - fix issues with network index and address recovery after
      a system restart
    - LP: #398867 - fix storing VLAN tag info from web ui
    - LP: #430266 - fix setting of HTTP error codes
    - LP: #449948 - part of fix to LP:#449948 the CC now correctly sets the
      networkIndex field in the reponse message of describeInstances
    - LP: #438565 - allowing a range of IPs to be specified in the
      VNET_PUBLICIPS field of eucalyptus.conf
    - LP: #449143 - Add the 169.254.169.254 address to eth0 as 'scope link'
      in order to avoid conflict with the UEC avahi-publish mechanism
    - LP: #449135 - Prevents a segfault in CC during client connection to NC
      on describeInstances, when number of instances is high (> 20 or so).
      The number of bytes sent to 'malloc' was being calculated incorrectly.
    - LP: #444838 - fix to fully allow VMs to access meta-data service in
      MANAGED-NOVLAN, when ...