no way to enable dhcp other than interactive webui

"<roaksoax> smoser: i thnk that they were gonna change the default sto have the dhcp server enabled by default"

This is not going to happen, it's rather invasive.

Why do you need to enable the DHCP stuff other than in the UI? What's the use case?

Use case: Test
I want to do stuff automatically, and set up maas for use in test without requiring a human to click buttons.

The only things enabling that checkbox does is:
 * Generates a job to write out DHCP config when the master worker is configured
 * Enables jobs that poke static host maps into the DHCP server over OMAPI.

If you want to do the former, there's a utility script that you can run manually:
$ bin/maas-provision generate-dhcp-config

I doubt you will need the latter for any testing.

Is this enough?

This is a symptom of the commingling of UI and API. If the UI were a consumer of the API this would be half solved already.

I think all MAAS operations, beyond initial bootstrap, should be available via the API. In fact, the web API should be *the* channel for achieving almost everything. The CLI and web UI should be a consumer of the API. This will concentrate our efforts into making the API better, and complete.

On Friday 31 August 2012 08:01:18 you wrote:
> This is a symptom of the commingling of UI and API. If the UI were a
> consumer of the API this would be half solved already.
>
> I think all MAAS operations, beyond initial bootstrap, should be
> available via the API. In fact, the web API should be *the* channel for
> achieving almost everything. The CLI and web UI should be a consumer of
> the API. This will concentrate our efforts into making the API better,
> and complete.

Totally. This was our originaly intention in Budapest as well but ... time
...

> The only things enabling that checkbox does is:
> * Generates a job to write out DHCP config when the master worker is configured
> * Enables jobs that poke static host maps into the DHCP server over OMAPI.
>
> If you want to do the former, there's a utility script that you can run manually:
> $ bin/maas-provision generate-dhcp-config
>
> I doubt you will need the latter for any testing.

> Is this enough?

Well, I probably want that. I want to test maas and verify stuff works. I want to launch an instance (or provision hardware), and then *use* that maas as fully as possible. If I can't enable dhcp (or some portion of it) then I can't test dhcp.

I'm really surprised to hear any pushback on this.

> Well, I probably want that. I want to test maas and verify stuff works.
> I want to launch an instance (or provision hardware), and then *use*
> that maas as fully as possible. If I can't enable dhcp (or some portion
> of it) then I can't test dhcp.

Ok I think we need to do something anyway because as it stands when installing
the maas package it also installs maas-dhcp, which should be separate.

Please see bug 1044229 because I think it's effectively a dupe of this one.

> I'm really surprised to hear any pushback on this.

I'm trying to fit a quart into a pint pot - we've got more work than we can
handle at the moment so I need to prioritise and the only way I can do that is
to probe deeply when someone files a bug.

Cheers.

Enabling the dhcp stuff is equivalent to setting the config parameter "manage_dhcp" to 'True'. This can be done in the UI but, as with all the configuration options, it's also exposed on the API: $api_url/maas/ op={set_config,get_config}.