=== frankban|afk is now known as frankban [11:31] Hi everyone, I need to perform Ubuntu installation with MaaS. The prolem is that Node has like 25 disks which confuses installator, it expects for an answer where to install bootloader, so installation stucks. My question is following, how I can tell MaaS to install loader on certain drive, for exmple '/dev/sda' ? [11:34] slevchenko_, which version are you using? [11:34] 2.1 [11:35] slevchenko_, ok. did the machine commission? [11:35] i.e in Ready state [11:35] Yup, nodes were commisioned successfully [11:36] slevchenko_, ok [11:36] give me a minute while i check something [11:38] ok no problem [11:42] slevchenko_, under the machine 'Used disks and partitions, is anything selected?' [11:42] No [11:43] slevchenko_, no radio buttons under the 'boot' column? [11:44] There's: [11:44] Available disks and partitions [11:44] and radio-button next to each of 25 disks [11:45] radio-buttons in boot column [11:45] slevchenko_, but none of the radio buttons is selected? [11:45] Yes [11:45] slevchenko_, can you try selecting one and deploying again? [11:46] really it should select one by default but we can try and figure out why it didn't after we make sure this works [11:47] Before I'll try do you know is it possible to do through a cli ? [11:47] slevchenko_, yes [11:47] Asking because deploying 103 machines through UI would be kinda painful [11:48] oh then I'll try, thx [11:48] slevchenko_, indeed :) [11:48] Thank you very much Brendan [11:53] slevchenko_, let me know if it works, i might have an alternative suggestion if it doesn't [11:53] Sure, thanks again [12:00] Also Brandan, MaaS has hardcoded commisioning timeout in 20 minutes, and servers have no proper DNS yet, so sudoing takes like eternity :( [12:00] Is it possible to workaround it like this? [12:01] early_commands: [12:01] maas: [echo, '127.0.1.1 {{node.hostname}}' >> '/etc/hosts'] [12:02] This block will go to curtin installer [12:02] *preseed [12:04] slevchenko_, why 127.0.1.1? [12:07] just a placeholder for a sudo to resolve host faster [12:07] it can be 127.0.0.1 [15:13] Bug #1644856 opened: Issue with changing device naming of boot disk between commissioning and deployment === HB is now known as Guest78801 [15:20] Hi [15:20] Can any body have idea about MAAS 2.0 on Ubuntu 16.04 [15:21] i have installed and all machines are in ready status [15:21] now i would like to proceed further for openstack deployment [15:21] what are the next steps, seeking guidance for exact steps??? [15:27] Guest78801, have you considered using Juju to manage the services (e.g. openstack) that will run on the MAAS nodes? [15:29] (see #juju on freenode) [15:29] Yes but i assume as per documentation by installing openstack juju is implicitly installed [15:29] is this so??? [15:31] Guest78801, link to documentation that says that? [15:32] I dont have exactly the link but i read during searching [15:32] Guest78801, ok, so, no, openstack can be installed without juju [15:35] ok can u pls guide me after MAAS installation and machines readiness what are next steps [15:41] Guest78801, you will need to be willing to invest time into studying this stuff but for a possible quick win you can try http://conjure-up.io/ [15:42] ok thanks === frankban is now known as frankban|afk [21:41] Bug #1644920 opened: Image selection unclear [22:50] Hello, someone know how setting the power type of MAAS using VMware fusion? [22:57] Anyone can help me? [22:59] Fusion won't work with MAAS, doesn't have the SSL port used to configure vmware power type [23:05] @jhegge MAAS can work only with VMware Workstation and not with Fusion, is it right? [23:06] possibly Workstation, but more like ESXi or vSphere