=== vladk|offline is now known as vladk === CyberJacob|Away is now known as CyberJacob === CyberJacob is now known as CyberJacob|Away [07:37] dimitern: we have a scheduling conflict for a 08:00 UTC call. Can we have it at 09:00 UTC like we said originally? [07:40] jtv, yes, I don't know what happened :/ I remember setting it for an hour later, will reschedule [07:40] dimitern: thanks [07:42] Thanks dimitern [07:42] jtv, rvba, if you refresh do you see it scheduled correctly this time? [07:42] dimitern: yes [07:42] Yes. [07:42] good :) === vladk is now known as vladk|offline === vladk|offline is now known as vladk [08:26] can someone help me with the installation of JuJu with MaaS ? [08:28] I have an actual Ubuntu machine setup, installed MaaS on it, trying to bootstrap juju but it returns with 409 CONFLICT error [09:06] hardware drivers are still not documented, are they? [09:07] jake6a: did you enlist any nodes to maas yet? 409 means maas can't find a suitable node to allocate to juju [09:07] I did not [09:08] I tried doing so in the MaaS web interface but they get stuck in "Commissioning" [09:08] what sort of nodes are you adding? [09:08] and power types? [09:09] I did a wake-on-lan [09:09] I'll tell you my setup [09:10] I'm using a Mac and I have another Ubuntu machine setup with Maas installed, I want to run a Juju-maas environment so I can run services like mysql and wordpress for example [09:11] I've installed Juju on the Mac and Maas on the Ubuntu machine [09:11] what are you going to use as nodes? [09:12] I was planning on using the Ubuntu machine [09:12] you can't do that, you installed maas on it [09:12] Is it even possible to use the same machine as a node to the Maas server? [09:12] I see [09:12] Ok then, can I install a VM Ubuntu on my mac, and act that as a node for example? [09:12] you need a machine with nothing on it, maas will control it entirely [09:12] yes, VMs are fine [09:12] there is a section in the documentation on how to set that up [09:13] please follow it carefully [09:13] Alright, I am installing the virtual machine now [09:13] Could you link me to that section please? [09:13] sure [09:13] http://maas.ubuntu.com/docs1.5/nodes.html#virtual-machine-nodes [09:15] So after adding that node, Juju bootstrap should work fine? [09:15] yes [09:15] as long as the node was commissioned [09:15] and goes READY [09:15] you'll need a second one to deploy a charm [09:16] So I'll need one more VM ? [09:17] as many VMs as you want charms deployed [09:17] I see [09:18] So for one charm setup, I will use [09:18] 1- Ubuntu server with Maas [09:18] 2- Ubuntu VM as a node [09:18] 3- Juju on Mac [09:18] correct? [09:18] you can run juju anywhere [09:18] well, the cmd line I mean, it then installs itself on the bootstrap node [09:21] Cool, I'll try this now, thanks a lot bigjools [09:21] welcome [09:21] I might be having some little trouble with the configurations though, is it okay if I report back? [09:21] in my own setup I run juju on the maas server [09:21] I won't be around, I'm leaving now, but someone may help [09:22] Alright, thanks a lot [10:38] allenap, jtv, rvba: Can has review? https://code.launchpad.net/~gmb/maas/static-ip-sanity-checks/+merge/225935 [10:38] Oh, hang on [10:38] conflicts [10:39] gmb: Claimed! [10:39] Drat. [10:39] allenap: Ta. Conflicts fixed. [10:39] * gmb -> lunch [10:40] * jtv → different lunch [10:57] bigjools: still there? [11:01] Why would MAAS suddenly start complaining about RPC information for a cluster controller not being available? [11:05] Apparently re-enlisting the node makes everything work again. === vladk is now known as vladk|offline === vladk|offline is now known as vladk === vladk is now known as vladk|offline [12:06] allenap: Have replied to your review. Thankee :) === vladk|offline is now known as vladk [13:44] allenap: rvba: here is the fix for the migration https://code.launchpad.net/~blake-rouse/maas/append-current-dir-for-boot-images-migration/+merge/225972 [13:45] blake_r: I’m otp, but I’ll look when I’m done. [13:45] allenap: cool [13:46] blake_r: cool, I'll have a look. [13:46] rvba: thanks [13:46] rvba: sorry for the bad code, previously [13:46] blake_r: no worries, it happens to everyone. [14:37] blake_r: testing your fix now [14:47] rvba: is it working? [14:49] blake_r: still importing the images with MAAS 1.5… [14:49] rvba: okay === vladk is now known as vladk|offline === vladk|offline is now known as vladk [14:59] blake_r: after the upgrade, I'm seeing http://paste.ubuntu.com/7765995/ in celery.log [15:03] rvba: that was an issue with bigjools added subarches to maas.meta [15:03] rvba: need to handle that key missing [15:04] This means the reporting of the images didn't happen. And thus we cannot QA your change properly. [15:04] Okay, I will update the branch to check for key. One sec [15:04] I still think your branch is sane… but we need to get to a state where we can do a full QA. [15:05] blake_r: can you explain why the key is missing? [15:06] rvba: because when bigjools add the supported_subarches column to the database, it needs to be reported every time the report_boot_images is called [15:06] rvba: in 1.5 that wasn't there [15:06] I see [15:06] rvba: so for 1.6 he added a maas.meta file under boot-resource/current [15:06] rvba: that contains the subarches key [15:07] bigjools: what about the upgrade path for this? ^ [15:08] rvba: http://paste.ubuntu.com/7766045/ [15:08] rvba: try that fix to see if ti fixes it [15:09] rvba: i can add it to my branch it it does [15:09] Testing it now… [15:14] blake_r: it fixed the crash… [15:17] rvba: okay I will include it in my branch [15:17] rvba: let me add a test as well [15:18] Cool; I cleared the BootImage table, let's see if it gets re-populated correctly when the parsing task runs. [15:18] Yep, it worked okay. [15:19] Awesome [15:20] blake_r: please add a comment in the code for the 'subarches = mapping.mapping[image]['subarches']' statement; why we need to do this is non-obvious. [15:21] blake_r: The branch linked to https://bugs.launchpad.net/maas/+bug/1319143: is that really related to that bug? [15:21] Ubuntu bug 1319143 in MAAS "move supported operating system into cluster using RPC" [Critical,Triaged] [15:21] rvba: okay [15:21] Ta [15:22] the boot-image-xinstall? [15:22] no it was linked to RPC os [15:23] it fixed an issue to not needing RPC for every curtin request [15:23] idk why it was moved [15:26] blake_r: Do you know what bug number that other bug has? I’ll move it (because I want to steal bug 1319143). [15:26] bug 1319143 in MAAS "move supported operating system into cluster using RPC" [Critical,Triaged] https://launchpad.net/bugs/1319143 [15:26] oh wait sorry, it is related to that bug [15:27] without that branch an RPC cal was going to be needed [15:53] allenap: can we get this one merged, https://code.launchpad.net/~blake-rouse/maas/license-key-views/+merge/224808 [15:53] allenap: since your working on the PRC stuff [15:53] allenap: RPC* [15:57] blake_r: I’ve added a comment saying I think it’s okay to land. [15:58] allenap: awesome thanks === gaughen_ is now known as gaughen [16:51] hey guys, I have a maas created on a server, and then I try to add a node by enlisting it with ubiquity, but it just doesn't appear, any ideas on what may be going on? [16:51] like, the server turns off but I don't get the node on the maas === vladk is now known as vladk|offline === roadmr is now known as roadmr_afk === slobo_ is now known as slobo === jfarschman is now known as MilesDenver === roadmr_afk is now known as roadmr [18:19] http://paste.ubuntu.com/7766897/ [18:19] nevermind that... === CyberJacob|Away is now known as CyberJacob === vladk|offline is now known as vladk === jfarschman is now known as MilesDenver === CyberJacob is now known as CyberJacob|Away === vladk is now known as vladk|offline === vladk|offline is now known as vladk === vladk is now known as vladk|offline === jfarschman is now known as MilesDenver [23:56] Evning, im planning on installing ubuntu-maas and on top of that virtual box for different servers. I wonder if thats a good solution to have and if the hardware power from the computers are spread across the computers so if one hardware goes offline the virtual machine are not troubled by that.