maas installs python modules with out any namespacing

[Scott Moser]

maas has essentially claimed the names 'provisioningsever', 'metadataserver' 'maasserver' and now 'apiclient' in python modules namespace.

Of those, only 'maasserver' makes even a bit of sense.

These should get namespaced into 'maas.apiclient', 'maas.provisioningserver' ...

[Gavin Panella (allenap)]

We've wanted to address this for a long time, but there are some hurdles to overcome, and it's more work than it appears at first (we know this first hand). South completely lost its mind when we moved modules around, and Django wouldn't initialise for reasons we were never able to understand. However, renaming apiclient and provisioningserver will work okay.

[Scott Moser (smoser)]

Gavin,
 If you think provisioningserver and apiclient can be renamed, could you do that?
 'apiclient' is *really* bad as a name. I'd rather get over the pain of that now than have to deal with people outside of maas source using that later.

[Gavin Panella (allenap)]

Okay, let's limit this to those two for now. I suggest:

  apiclient --> maasclient
  provisioningserver --> maascluster

[Julian Edwards (julian-edwards)]

+1

Although my tab-completion fingers will thank you if s/maasclient/maasapi/

[Gavin Panella (allenap)]

> Although my tab-completion fingers will thank you if s/maasclient/maasapi/

I think that could be confusing with the server-side of the API, so perhaps we'll have to think up something else that's tab-finger-friendly.

[Julian Edwards (julian-edwards)]

This is not something that's SRU-able, so removing the milestone.

[Adam Collard (adam-collard)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team