All, Mark, Dustin and I have discussed some ideas around the notion that having a more 'automated' method of choosing and allocating public IP addresses in the UEC, while keeping Eucalyptus in MANAGED mode in order to support all of the networking features that Eucalyptus provides (Elastic IPs, Security Groups and VLAN isolated VM networks). At the UDS, we decided that these ideas need not be fleshed out for Lucid (Eucalyptus 1.6.2), but they're certainly 'live' in that, at the core, the notion of building into the Ubuntu installation process a model for easily setting up node/VM network address allocation and management would be a powerful sub-system that Eucalyptus could depend upon when it comes to configuring the VM networks. Right now, the Eucalyptus networking modes are highly configurable, but must largely be configured manually as no such sub-system (well defined model for dealing with large collections of dynamic networked machines) is readily available. I believe that building such a system would allow the UEC, as the original report suggests, to present more sophisticated networking modes that are potentially simpler to manage.
-- Public IP addresses should be assignable by DHCP https://bugs.launchpad.net/bugs/454519 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
