[02:52] <freeflying> bigjools, ping
[02:52] <bigjools> freeflying: hi
[02:54] <freeflying> bigjools, hey, do you have some mins for a chat?
[02:55] <bigjools> freeflying: I can try.  Coming down with a cold or something so bear with me.
[02:56] <freeflying> bigjools, I'm sorry to hear that, then I'll try catch someone else :) take care
[02:56] <bigjools> freeflying: jtv is around too
[02:56] <bigjools> ask anyway and someone will answer
[02:56] <freeflying> bigjools, cool, thanks
[02:57] <freeflying> so I'm still on the issue that to deploy with 2 dhcp servers, 1 for pxe to offer node boot/enlist/provisioning, the other is managed for maas, and is for for post deployed management network
[02:59] <freeflying> I can enlist nodes now, but have problem with deploy service, CNAME of the node won't be added to DSN record correct, so will ddns on the dhcp server managed by maas solve the issue or need to do some other configuration with celeryd
[02:59] <freeflying> jtv, if you happen to be here, would you mind take a look? thanks
[02:59] <bigjools> you said you had 2 nodes with a cname and one without
[03:00] <bigjools> we established it was not booting correctly
[03:02] <freeflying> yes
[03:03] <freeflying> the 3rd doesn't come up crrectly
[03:04] <bigjools> then you need to work out why
[03:04] <bigjools> it's nothing to do with dhcp or dns
[03:06] <freeflying> during enlist/cmmissioning, both should get a ip from dhcp server, and celeryd-regional-controller is able to have the CNAME added after commissioning, it it corret?
[03:07] <bigjools> CNAME is added after a node is accepted for commisioning and after a lease is added to the leases file
[03:14] <bigjools> so it needs to boot and have the dhcp client request an address
=== CyberJacob|Away is now known as CyberJacob
=== freeflying is now known as freeflying_away
=== freeflying_away is now known as freeflying
=== lifeless_ is now known as lifeless
=== kentb-out is now known as kentb
[17:45] <jbalonso> Is this a reasonable place to ask about (heretofore undocumented) custom commissioning scripts?
[17:59] <kurt_> jbalonso: I would put your question in to askubuntu
[18:08] <free50> hello everyone, I have a reasonably large cluster using infiniband as the interconnect. Does MAAS support FlexBoot?
[18:09] <jbalonso> kurt_: Thanks. I'll look into that. From what I can google, however, the custom commissioning script system has only been discussed in a dev context, so I'm not very optimistic.
[18:10] <kurt_> jbalonso: you'll get better round-the-clock exposure from askubuntu.
[18:10] <free50> I guess a more general question is, does MAAS work with infiniband?
[18:15] <kurt_> free50: I'm kinda clueless on inifiniband - does infiniband support PXE boot and WOL?
[18:19] <jbalonso> kurt_: To close out this conversation, I've submitted my question to http://askubuntu.com/questions/346770/how-do-i-use-maas-custom-commissioning-scripts
[18:19] <kurt_> jbalonso: cool.  Then bigjools will see it.
[18:28] <AskUbuntu> How do I use MAAS custom commissioning scripts? | http://askubuntu.com/q/346770
[18:46] <free50> kurt_: the docs on the mellanox site say they support ipxe
[18:46] <free50> WOL is another question
[18:46] <kurt_> PXE is the big thing
[18:47] <free50> seems like the initrd has to have the infiniband (that is, OFED) drivers included with it
[18:47] <kurt_> free50: you systems have to be able to PXE boot for MAAS to work
[18:48] <kurt_> sorry, I'm not going to be much help in this area.
[18:48] <free50> hmm.
[18:49] <free50> kurt_: do you know if anyone here is knowledgeable WRT infiniband?
[18:50] <kurt_> sorry, no.  as I suggested to jbalonso, you may want to post your question to askubuntu to get widest exposure.
[18:53] <free50> k, I'll try that. thanks for your help
[18:54] <kurt_> good luck
[19:12] <AskUbuntu> Infiniband + Maas? | http://askubuntu.com/q/346780
[19:12] <free50> hey kurt_, on a separate note: does MAAS support diskless boot? I see in the setup docs on ubuntu's site that the node "contacts the region controller, then shuts down"
[19:12] <free50> obviously that isn't conducive to diskless boot..
[19:17] <kurt_> free50: I'm not sure.  It may, but it's definitely not the focus.  The focus is on physical hardware and kvm.
[19:18] <free50> kurt_: so maas is more of a solution for VPS?
[19:19] <free50> rather, vps providers?
[19:19] <kurt_> right.  its more of a physical thing
[19:20] <kurt_> Metal-as-a-service
[19:20] <kurt_> you could try looking at juju as your next layer
[19:21] <kurt_> that being said, I have worked through using MAAS with VMware
[19:21] <kurt_> and it works on KVM
=== CyberJacob is now known as CyberJacob|Away