Eucalyptus installer should skip range-of-public-ip's question in favour of DHCP

Bug #454521 reported by Mark Shuttleworth
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)
Triaged
Wishlist
Unassigned

Bug Description

Once Eucalyptus supports the use of DHCP for dynamic public IP assignment to instances running in the cloud, the cloud installer in Ubuntu should skip the question asking about a range of public IP addresses. Such a range can be configured manually if needed, the default "just works" configuration should assume the existence of a DHCP server and act accordingly.

Revision history for this message
Mark Shuttleworth (sabdfl) wrote :

There are three related bug reports in this set:

  #454519 - Eucalyptus node controllers should be able to get a DHCP address for public instances
  #454521 - The Ubuntu private cloud installation should skip public IP range question in favour of DHCP
  #454540 - Cloud DHCP requests should include some custom options to help configure IP ranges neatly

Thierry Carrez (ttx)
Changed in eucalyptus (Ubuntu):
importance: Undecided → Wishlist
status: New → Triaged
Revision history for this message
Dustin Kirkland  (kirkland) wrote :

I need to file a Lucid+1 blueprint on an idea that we've been refining (and prototyping) over the last few months...

Mathias, Scott, Thierry, and I have each implemented out own pxe/tftp/mirror automated network installation infrastructure for rapidly deploying UEC in our own test environments at home, as well as in the Lab.

The components are well known, and well supported in Ubuntu. We think we could/should provide this as a set of packages that could be installed as another uec server/service (even on the same machine as the CLC).

A UEC nearly always involves installing >1 system, and in some cases, many times >1.

We could help UEC users by setting up for them a system that:
 * runs tftpd-hpa
 * has a good /var/lib/tftpboot/ directory serving an Ubuntu netboot installation
 * has an Ubuntu mirror (or apt proxy), is kept in sync, or at least has the released ISO mounted, and served over http to the local network
 * optionally runs a pxe and dhcpd server
 * has a small web front end that initiates the deployment of one or more UEC components on one or more systems on the local network

Using this setup, the user could:
 * rapidly deploy UEC components
 * pxe/netboot UEC servers
 * pxe/netboot even UEC instances

This really deserves a full blueprint for Lucid+1... I'm just braindumping here at the moment...

Revision history for this message
Mark Shuttleworth (sabdfl) wrote : Re: [Bug 454521] Re: Eucalyptus installer should skip range-of-public-ip's question in favour of DHCP

Dustin, +1 for exploring that concept further, it fits very well with
the meme of rapid and efficient deployment.

Mark

Revision history for this message
Thierry Carrez (ttx) wrote :

For reference, branches with everyone's personal implementations:
lp:~mathiaz/+junk/install-srv
lp:~kirkland/+junk/uec-auto
lp:~ttx/+junk/boot-uec

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.