Development Summary - June 8th

Blake Rouse blake.rouse at canonical.com
Mon Jun 12 07:45:43 UTC 2017


We are currently working on machine network configuration and overall
network configuration in the viscera part of the library that gets exposed
through the client Facade.

Example:

client = await login('http://localhost:5240/MAAS', 'admin', 'password')
fabric = await client.fabrics.get_default()
vlan = fabric.vlans.get_default()
vlan.mtu = 9000
await vlan.save()

machines = await client.machines.list()
for machine in machines:
    boot_interface = machine.boot_interface
    boot_interface.vlan = vlan
    await boot_interface.save()

Creating bonds, vlan interfaces, and bridges will come as well.

- Blake Rouse


On Mon, Jun 12, 2017 at 3:32 AM, Ante Karamatić <
ante.karamatic at canonical.com> wrote:

> On Thu, Jun 8, 2017 at 9:20 PM Christian Robottom Reis <kiko at canonical.com>
> wrote:
>
>> > With the continuous improvement of the new MAAS Python Library
>> > (python-libmaas), we have focused our efforts on the following
>> improvements
>> > the past week:
>>
>> Ante, what are they key features missing from libmaas for the node
>> config step for the Foundation work (and is there more we'd like to
>> have)? I'd like to see if they might make 2.3.
>>
>
> libmaas has bones and viscera modules. Bones is low level lib, and it
> might support all that is needed (but it's also much easier to just use
> maas CLI then). Viscera module, which is a high level lib, should at least
> support enlisting machines and network/disk configuration. And this is
> because these are the most repetitive operations that, also take too long
> to execute using CLI. Fabrics, vlans, tags, spaces, etc are things one
> usually sets once, maybe iterate over, but in essence those are not time
> consuming operations.
>
> Andres, Blake and I have already touched on this few weeks back. I think
> we know how to approach the problem within MAAS itself that would solve all
> of the machine configuration in one go; using cloud-config syntax as input
> and output syntax for node configuration. API at that point wouldn't be a
> blocker and in fact wouldn't require a lot of work to support that feature.
> In future it could provide high level abstraction for configuration, but
> that just bonus.
>
> --
> Ante Karamatić
> ante.karamatic at canonical.com
> Canonical
>
> --
> Maas-devel mailing list
> Maas-devel at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/maas-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/maas-devel/attachments/20170612/0b4b1152/attachment.html>


More information about the Maas-devel mailing list