maas-import-pxe-files could use the http_proxy setting

[Diogo Matsubara]

There's a global setting in the MAAS ui to set a http proxy. the maas-import-pxe-files script could take advantage of that config if set and use the proxy.

[Raphaël Badin (rvb)]

This is already done in raring (i.e. in trunk), where the standard way of running maas-import-pxe-files is by using the API (import_boot_images) or the UI (nodegroup page).
Note that this feature is not present in 1.2.

[Julian Edwards (julian-edwards)]

This was recently tested as not working by Diogo in the lab and I asked him to file this bug.

[Julian Edwards (julian-edwards)]

Oh and it refers to the command line invocation. We need to make that seamless.

I had a lot of problems getting it working from the UI BTW, it often failed silently and there's no feedback. Running it from the command line is the only way of seeing any log output.

[Raphaël Badin (rvb)]

I'm pretty sure we tested this successfully in the lab. But it was using the UI/API. Running the script manually (i.e. from the command line) is sort of deprecated now because the invocation of that script needs to be driven from the region (i.e. be a celery task) so that the value of the config item 'http_config' can be sent when the script is called (see src/provisioningserver/tasks.py:import_boot_images).

[Julian Edwards (julian-edwards)]

There's no reason we can't make manual invocation take the proxy setting from the database.

[Raphaël Badin (rvb)]

We will have to make an API call that's all. The script runs on the cluster and the info is on the region. It's just not the way we've designed this thing :).

[Raphaël Badin (rvb)]

> I had a lot of problems getting it working from the UI BTW, it often failed silently and there's no feedback.

No feedback indeed, but the celery log on the cluster should contain the errors.

[Julian Edwards (julian-edwards)]

On Tuesday 05 Mar 2013 08:01:41 you wrote:
> We will have to make an API call that's all. The script runs on the
> cluster and the info is on the region. It's just not the way we've
> designed this thing :).

That's fine. Let's make this low priority!