Devices in maas and automatic DNS entries?

Fri Feb 17 18:10:32 UTC 2017

I’ll answer myself:

Seems you can do all of this through the command line. Removing the subnet, clearing the discovered list and issue a new full scan. 

I do notice that after I initiated a new scan there are a lot of the following in the log:

2017-02-17 10:08:15 provisioningserver.utils.services: [info] observe-mdns: Upon execvpe b'maas-rack' [b'maas-rack', b'observe-mdns'] in environment id 139882625865928
2017-02-17 10:08:15 provisioningserver.utils.services: [info] observe-mdns: :Traceback (most recent call last):
2017-02-17 10:08:15 provisioningserver.utils.services: [info] observe-mdns:   File "/usr/lib/python3/dist-packages/twisted/internet/process.py", line 430, in _fork
2017-02-17 10:08:15 provisioningserver.utils.services: [info] observe-mdns:     environment)
2017-02-17 10:08:15 provisioningserver.utils.services: [info] observe-mdns:   File "/usr/lib/python3/dist-packages/twisted/internet/process.py", line 508, in _execChild
2017-02-17 10:08:15 provisioningserver.utils.services: [info] observe-mdns:     os.execvpe(executable, args, environment)
2017-02-17 10:08:15 provisioningserver.utils.services: [info] observe-mdns:   File "/usr/lib/python3.5/os.py", line 624, in execvpe
2017-02-17 10:08:15 provisioningserver.utils.services: [info] observe-mdns:     _execvpe(file, args, env)
2017-02-17 10:08:15 provisioningserver.utils.services: [info] observe-mdns:   File "/usr/lib/python3.5/os.py", line 660, in _execvpe
2017-02-17 10:08:15 provisioningserver.utils.services: [info] observe-mdns:     raise last_exc.with_traceback(tb)
2017-02-17 10:08:15 provisioningserver.utils.services: [info] observe-mdns:   File "/usr/lib/python3.5/os.py", line 650, in _execvpe
2017-02-17 10:08:15 provisioningserver.utils.services: [info] observe-mdns:     exec_func(fullname, *argrest)
2017-02-17 10:08:15 provisioningserver.utils.services: [info] observe-mdns: FileNotFoundError: [Errno 2] No such file or directory: b'/bin/maas-rack'
2017-02-17 10:08:15 provisioningserver.utils.services: [critical] mDNS observation process failed.
	Traceback (most recent call last):
	Failure: twisted.internet.error.ProcessTerminated: A process has ended with a probable error condition: process ended with exit code 1.

> On Feb 17, 2017, at 9:45 AM, Jim Tilander <jim at tilander.org> wrote:
> 
> Hi Andres,
> 
> Ah, I must have fiddled with this incorrectly before. I now managed to add a device and have it show up in the DNS per your instructions.
> 
> Follow up question:
> 
> The discovered devices becomes quickly cluttered. Is there a way to clear the list and start “fresh” without adding all the devices?
> 
> Also, it seems like when you install libvirt for managing kvm nodes, it causes a new subnet to be discovered for libvirt (192.168.112.0/24). Even though that’s not actively mapped, devices from that network seems to be showing up always. Is there any way to get rid of that subnet in MAAS?
> 
> Cheers,
> Jim
> 
> 
>> On Feb 14, 2017, at 8:11 PM, Andres Rodriguez <andres.rodriguez at canonical.com <mailto:andres.rodriguez at canonical.com>> wrote:
>> 
>> Hi Jim,
>> 
>> Responses inline.
>> 
>> On Tue, Feb 14, 2017 at 9:40 PM, Jim Tilander <jim at tilander.org <mailto:jim at tilander.org>> wrote:
>> Hi,
>> 
>> I’ve been trying to get non maas controlled devices on my network (actually devkits) to be automatically added to the DNS. So far no luck, but I might be doing something wrong.
>> 
>> In my scenario I have some DHCP enabled devices that also offer up the dhcp client name. I’d like for this clientname to actually get entered into the DNS so I can later resolve these devices.
>> 
>> It sounds like you only need to add a device. You can add this device manually. Go to 'Nodes' > 'Devices' > 'Add device'. You will need to specify the MAC and IP assignment for your device. For example, you want your device to have an specific IP address, you can select 'Static' IP Assignment. If you don't care which IP it gets, select 'Dynamic'. This will automatically create a DNS entry.
>>  
>>  
>> I figured that I’d scan for devices on the network, find the device and then assign a name and a domain to it.
>> 
>> This doesn’t actually seem to work. :(
>> 
>> By default, the 'device discovery' feature has 'Passive' scanning active. This will only listen for ARP request. It may be the case that MAAS is missing the specific ARP request. That said, however you can go to the subnet where your device is and you can select the action to 'Map subnet'. This will have MAAS scan the network via 'ping'. If you have 'nmap' installed, it will prefer nmap over ping.
>> 
>> Please see https://docs.ubuntu.com/maas/2.1/en/2.1-release-notes <https://docs.ubuntu.com/maas/2.1/en/2.1-release-notes> for further explanation.
>> 
>> Thanks.
>> 
>> Is this something that is supposed to work and I’ve got some bug in my setup, or am I chasing something that can’t be done currently in MaaS?
>> 
>> Cheers,
>> Jim
>> 
>> 
>> --
>> Maas-devel mailing list
>> Maas-devel at lists.ubuntu.com <mailto:Maas-devel at lists.ubuntu.com>
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/maas-devel <https://lists.ubuntu.com/mailman/listinfo/maas-devel>
>> 
>> 
>> 
>> -- 
>> Andres Rodriguez
>> Engineering Manager, MAAS
>> Canonical USA, Inc.
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/maas-devel/attachments/20170217/2d4e3409/attachment.html>