maas-devel team mailing list archive

[Boyang <boyang.niu@xxxxxxxxx>]

Hey Gavin,

Currently our machines use layer 3 routing whereas MAAS works mostly on
layer 2.  I realize that we're in a pretty unique scenario ourselves and
aren't the typical MAAS user, so you're right that it's a good idea to make
this functionality separate from the actual application.

We're not going to use Juju and I don't know if MAAS was meant to be
bundled exclusively with Juju but I would like to be able to run it
separately.  The end functionality that I'd like to build into MAAS is
something of a database that holds and organizes data center information
(about nodes and connections) in addition to booting them up.  I understand
if this isn't the direction you want to take :)

Thanks again!


On Mon, Jun 10, 2013 at 2:47 PM, Gavin Panella
<gavin.panella@xxxxxxxxxxxxx>wrote:

> Hi Boyang!
>
> On 10 June 2013 22:17, Boyang <boyang.niu@xxxxxxxxx> wrote:
> > I would like to have a unique loopback IP address assigned to each of my
> > nodes as a kernel param during the install stage.  These addresses are
> > already established; I would be putting them into a database and then
> > linking them during the install.
>
> What's the use case for these? I'm not sure I can think of any reason
> why this kind of feature should be in MAAS itself, but I'm happy to be
> convinced otherwise. Perhaps tell us why you need unique loopback
> interfaces?
>
> On the face of, I think this should be the responsibility of the tool
> that's asking MAAS for nodes. Custom set-up instructions can be passed
> from the asker through to the instance. Juju does just this; it
> bundles up its instructions into a form that cloud-init can consume
> and asks MAAS to pass it on. On Ubuntu Server, cloud-init always runs
> at boot time.
>
> Gavin.
>