=== CyberJacob is now known as CyberJacob|Away [00:30] so wierd. maas web ui can start the vm node to comission it, but not to "start" it [00:34] oh ho ho ssh key not registered. thank you mouse hover baloon over start button [00:35] success at lasst! === freeflying_away is now known as freeflying [02:31] it is working sweet now :) === jtv1 is now known as jtv [03:49] bigjools: would you believe that for the models migration I considered setting a standard of not giving manager classes a model-specific name? [03:50] jtv: I'm not horrified [05:42] bigjools: I do wonder if we need to model physical networks before modeling virtual ones. [06:00] jtv: we do, don't we?! [06:00] (sorry had internet brownout, massive storm here) [06:20] jtv: still there? [06:28] bigjools: yes, still here... or again, it turns out [06:34] jtv: can I do a pre-imp with you [06:34] Yes, let me grab the right hardware for that. [06:39] jtv: call me when you're ready === CyberJacob|Away is now known as CyberJacob === mthaddon` is now known as mthaddon [08:53] rvba: I'm grabbing the card for "user should be given a choice of where to place a node." Probably not much to do there — the hard work is in your card I think. [08:54] jtv: indeed. Also, Julian and I briefly talked about this and we don't think this card (the one you picked) should be done. [08:55] well hang on [08:55] not in that format, no, but the choice needs to be available to override the default [08:55] jtv: our idea was that having a default plus letting the user override it should be enough [08:55] What bigjools said :) [08:55] Yes, that's what I figured. [08:56] Let's talk about this after the call (or right now, if you want). [08:56] we are, as they say, in violent agreement [08:56] Having a default and letting the user change it is not as trivial as it sounds. [08:57] it's Django, nobody expected it to be :) [08:57] tsss [08:57] Please. [08:57] That depends... without your branch done, it is simple. [08:57] * bigjools pokes at the raw nerve [08:57] It's making the default not be null that's difficult. Right? [08:57] The trick being that the system must enforce the invariant: there is one default and one default only. [08:58] We have to make sure the status 'default' cannot be removed without another zone being selected as the default first. [08:58] We have to prevent the default from being deleted. [08:58] That sort of things. [08:58] In general, we have to fix the deletion of zones. [08:59] Because it nulls the existing Node.zone fields. [08:59] For the zone you're deleting, that is. [08:59] Indeed. [08:59] And it's much simpler to do than what has been done thus far :) [08:59] i.e. no need to override zone.delete. [08:59] Really? [09:00] jtv: https://docs.djangoproject.com/en/dev/ref/models/fields/#django.db.models.ForeignKey.on_delete [09:00] Ah, there's a policy? [09:00] jtv: more precisely https://docs.djangoproject.com/en/dev/ref/models/fields/#django.db.models.SET_DEFAULT [09:00] Yep [09:00] I've fixing this as a drive-by in my branch. [09:00] Then it comes back to how to set the default. [09:00] Which is an already existing problem. [09:01] And that can be a callable, like Zone.objects.get_default_zone [09:01] Ah good. [09:01] Then I don't know what needs doing for this card I picked up... [09:01] Nothing, if you ask me :) [09:01] Right. The option's already there. [09:01] * jtv deletes [09:02] That said, I am under instructions to help you clear this lane, so if there's anything I can do for you... [09:03] Well, let's talk about this, I'd be happy to run things by you. [09:06] You want to hang out? [09:06] jtv: yep, let's do that. [09:08] Damn. That means moving hardware around again. Hang on. [09:12] jtv: ready when you are [09:12] Oh come on, I used that network cable in that very port earlier today. I *know* it works. [09:12] Ah. [09:12] Slow DHCP response. [09:41] Shall we just call the default zone "default"? [09:43] You mean, make 'default' be its default name? [09:44] That's what I have in the data migration script that I created: http://paste.ubuntu.com/6702219/ [09:45] Perfect. [09:47] jtv: well, I'll have to change it now… you can see the presence of the 'default' boolean column in that migration. [09:47] No worries, I just meant the name. === marcoceppi_ is now known as marcoceppi [17:54] 2013-12-22 11:20:04,813 - url_helper.py[DEBUG]: Attempting to open 'http://172.16.1.21/MAAS/metadata//2012-03-01/user-data' with 1 attempts (0 retries, timeout=None) to be performed [17:54] 2013-12-22 11:20:04,856 - url_helper.py[DEBUG]: Failed reading from http://172.16.1.21/MAAS/metadata//2012-03-01/user-data after 1 attempts [17:54] 2013-12-22 11:20:04,856 - url_helper.py[DEBUG]: 1 errors occured, re-raising the last one [17:54] someone now anything about this? === allenap_ is now known as allenap === CyberJacob is now known as CyberJacob|Away === CyberJacob|Away is now known as CyberJacob [23:32] anyone around? I have MAAS set up on a machine running 13.10, but it appears that there is no tftp server installed... should that have been pulled in when I installed maas, maas-cluster-controller or maas-region-controller? [23:40] I really want to like MAAS, but wow am I having issues.. When commissioning 15 nodes, 5 of them just didn't turn on (IPMI never got hit, I guess), 4 had GRUB errors, the rest of them were stuck on cloud init and couldn't get an IP address [23:40] When I manually turned on the 5 that never came on, they all couldn't get anything from PXE [23:52] I don't even know where to begin with debugging [23:53] Same exact hardware, all Dell PowerEdge R620 nodes [23:53] Same RAID configuration, same NIC configuration