maas-devel team mailing list archive

[Blake Rouse <blake.rouse@xxxxxxxxxxxxx>]

It agree that using sub-folders would be a better approach. Anything
under the driver folder, would then be used by maas using the
Registry's.

I would not use "drivers/os" as if you imported that folder like so
"from provisioningserver.drivers import os" it would override the most
commonly used "import os". Since the field in the Node model for
operating systems is osystem, I would use "drivers/osystem".

This would get even more expanded as we move to pure python for power control:

drivers/power


On Tue, Jun 3, 2014 at 2:28 PM, Andres Rodriguez
<andres.rodriguez@xxxxxxxxxxxxx> wrote:
> Isn't the driver/ directory only for the different OS' instead of the
> different custom hardware we support. I think we need to keep the separation
> between OS' and custom hardware.
>
> Would a better approach be to do the following:
>
> drivers/hardware.
> drivers/os/
>
> Blake, thoughts?
>
>
> On Mon, Jun 2, 2014 at 9:59 PM, Julian Edwards
> <julian.edwards@xxxxxxxxxxxxx> wrote:
>>
>> These two directories are essentially the same thing.  Can whoever
>> touches something in there next please merge these directories into just
>> driver/
>>
>> Cheers
>> J
>>
>> --
>> Mailing list: https://launchpad.net/~maas-devel
>> Post to     : maas-devel@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~maas-devel
>> More help   : https://help.launchpad.net/ListHelp
>
>
>
>
> --
> Andres Rodriguez
> Engineering Manager, HWE Team
> Canonical USA, Inc.