=== spammy is now known as Guest81296 | ||
=== jamespag` is now known as jamespage | ||
=== Guest81296 is now known as spammy | ||
mup | Bug #1603947 opened: ntp dhclient exit hook does not remove most servers <amd64> <apport-bug> <trusty> <MAAS:Triaged> <ntp (Ubuntu):New> <https://launchpad.net/bugs/1603947> | 11:23 |
---|---|---|
mup | Bug #1603947 changed: ntp dhclient exit hook does not remove most servers <amd64> <apport-bug> <trusty> <MAAS:Triaged> <ntp (Ubuntu):New> <https://launchpad.net/bugs/1603947> | 11:29 |
mup | Bug #1603947 opened: ntp dhclient exit hook does not remove most servers <amd64> <apport-bug> <trusty> <ntp (Ubuntu):New> <https://launchpad.net/bugs/1603947> | 11:44 |
mup | Bug #1603947 changed: ntp dhclient exit hook does not remove most servers <amd64> <apport-bug> <trusty> <ntp (Ubuntu):New> <https://launchpad.net/bugs/1603947> | 11:53 |
BlackDex | Hello there, can a normal user add a machine via MAC? If not, how can we let a normal user do that. | 11:59 |
BlackDex | To prevent changing default settings etc.. | 12:00 |
MonsieurBon | Hi guys. Is there a way to install maas < 2.0 on xenial? | 12:20 |
BlackDex | MonsieurBon: Nope, use 14.04 | 12:22 |
MonsieurBon | seriously? there is only a beta version available on an LTS server OS? that's a bit disappointing | 12:24 |
BlackDex | Ubuntu LTS Server isn't released yet | 12:24 |
BlackDex | atleast not fully | 12:25 |
BlackDex | that will happen with 16.04.1 | 12:25 |
MonsieurBon | I would call this released: http://www.ubuntu.com/server | 12:25 |
MonsieurBon | :) | 12:25 |
BlackDex | https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule | 12:26 |
BlackDex | True, but an upgrade for example isn't supported yet | 12:26 |
BlackDex | from 14.04 to 16.04 | 12:26 |
BlackDex | that will happen only when the PointRelease is done | 12:26 |
MonsieurBon | Ok, good to know | 12:27 |
BlackDex | maas currently is on 2.0rc2 | 12:27 |
BlackDex | so i think it will be final during that time | 12:28 |
MonsieurBon | ok. Hope the same applies to juju. Because juju 2.0 seems far from stable to me :) | 12:32 |
MonsieurBon | thx for the clarification anyway | 12:32 |
virginie__ | hi all, I am trying to boot ubuntu VM using iPXE with MaaS | 12:53 |
virginie__ | without success. The error is "no bootable device" | 12:53 |
brendand | virginie__, have you configured the vm to boot from the network interface - is it a kvm vm? | 13:22 |
virginie__ | brendand, I checked the box and the VM starts using iPXE but I got an error | 13:28 |
virginie__ | Maas created a bootstrap vm but I have got this error | 13:30 |
virginie__ | error 0x040ee119 | 13:32 |
virginie__ | the pb was that I have 3 different NIC and the iPXE boot on the wrong one. So I need to press F12 key to see boot menu and select the right interface | 14:10 |
virginie__ | also for the minimum kernel, I had to set "trusty" rather than "no minimum" | 14:12 |
=== zz_CyberJacob is now known as CyberJacob | ||
roaksoax | ;/win 6 | 15:36 |
acovrig | is it possible to login to the provisioning environment? | 16:45 |
kiko | acovrig, yes | 17:26 |
kiko | acovrig, by provisioning, in maas-speak, do you mean deployment? or commissioning? | 17:26 |
acovrig | kiko: I netboot a new client, it boots to an ubuntu login prompt, how do I login to that? | 17:27 |
kiko | acovrig, I assume you uploaded SSH keys? | 17:28 |
acovrig | yes, and I tried logging in from that system as ubuntu and I think as root, what user should it be? | 17:29 |
acovrig | I’m trying this from 16.04, it hung somewhere on the boot process for quite a while, so I tried 14.04 then it hangs on the ubuntu login after trying to conenct to a 169.254.*.* for a long time | 17:31 |
acovrig | I just let a 16.04 go for several minutes an eventually got the ubuntu login prompt; how long should I expect it to sit at this prompt before it shutsdown after enrollment? | 17:31 |
kiko | acovrig, as ubuntu | 17:36 |
kiko | acovrig, hmmm. | 17:36 |
kiko | acovrig, I don't know in what phase you are getting stuck. are you enlisting the machine, commissioning or deploying? | 17:36 |
acovrig | kiko: I’m not sure either; from what I understand I can take a new piece of hardware, netboot it, then it will show up in the MAAS web interface so I can decide what OS and software to run on it. | 17:47 |
kiko | acovrig, correct. that first netboot is called "enlistment" | 17:47 |
acovrig | It’s getting stuck when I netboot it. I believe it’s supposed to enlist in MAAS then shutdown | 17:48 |
kiko | acovrig, once enlistment concludes the machine shuts down | 17:48 |
kiko | acovrig, ah. so enlistment is not concluding. is it the same for all your machines or do some enlist while others hang? | 17:48 |
acovrig | all machines | 17:48 |
kiko | ok | 17:49 |
kiko | acovrig, can the machines reach the internet? | 17:49 |
acovrig | currenlty I’m doing this in virtualbox on my macbook, but plan to use it to netboot and install MAAS on a physical server (because I have yet to have success installing from USB) | 17:49 |
acovrig | kiko: are they supposed to? the MAAS server has 2 nics, 1->internet, 2->internal network to the physical&VMs, but doesn’t have a router on it | 17:50 |
acovrig | am I supposed to manually create FW rules and ipv4_forward rules on the MAAS server so the clients have internet? | 17:50 |
kiko | acovrig, enlistment requires packages be installed, which could come from a proxy. the simplest way to ensure it works is to give clients internet access. | 17:51 |
acovrig | I’m a little confused on how that’s supposed to work: do I need to configure the MAAS server to be a router or not use DHCP on the MAAS server and configure a router to give the netboot DHCP option? | 17:52 |
kiko | acovrig, configure the MAAS server to provide DHCP on the segment your clients are on, and have it be a router, or indicate the correct default gateway | 17:56 |
kiko | (if you have another router on the segment) | 17:56 |
kiko | acovrig, does that make sense? | 17:56 |
acovrig | I think so, by default, does it configure itself as the router in DHCP, so if I add the FW rules and enable forwarding in the kernel it should work then? | 17:57 |
kiko | acovrig, I believe it does advertise itself as the router unless you specify otherwise in the settings page | 18:00 |
kiko | acovrig, by FW rules I assume you are going to NAT the clients? | 18:00 |
acovrig | yea, my plan is to make an openstack cluster between 3 servers (for failover); from what I undertand I can have 1 network for internet (LAN) and a few other networks for cluster management | 18:01 |
acovrig | currently my thought was to install ubuntu server from my laptop to the 3 servers over an unused cluster network then convert one of them to be the MAAS controller | 18:02 |
kiko | right, that works fine | 18:06 |
kiko | but indeed, the machines need external access, so you need to set up NAT and routing | 18:06 |
acovrig | :D I got my first machine to show up in MAAS! I guess I missed something in the docs, or something needs to be specified more clearly in the docs. It booted much quicker too, I guess it was trying to conenct for a while during the boot process | 18:09 |
kiko | cool! | 18:10 |
kiko | acovrig, yeah, the process and the failure more is still sadly invisible | 18:10 |
kiko | acovrig, fortunately once it works it really does work | 18:10 |
acovrig | yea, unfortunately I’ve been testing this w/a VM nic bridged to a host VLAN that goes to the server room, and I don’t think that will work, so I guess I need to untag my laptop on the cluter network to netboot the servers from my laptop :) | 18:11 |
kiko | heh | 18:12 |
acovrig | too bad virtualbox doesn’t do _real_ network bridges | 18:12 |
mup | Bug #1604103 opened: maas doesn't install in xenial unprivileged container <MAAS:New> <https://launchpad.net/bugs/1604103> | 18:21 |
=== wolverin_ is now known as wolverineav | ||
=== acovrig_ is now known as acovrig | ||
=== acovrig_ is now known as acovrig | ||
mup | Bug #1604111 opened: MAAS does not allow an interface to be "disconnected" and not have an associated (vlan, fabric) <MAAS:In Progress by blake-rouse> <https://launchpad.net/bugs/1604111> | 19:15 |
mup | Bug #1604103 changed: maas doesn't install in xenial unprivileged container <MAAS:Won't Fix> <https://launchpad.net/bugs/1604103> | 19:45 |
mup | Bug #1604128 opened: [2.0RC2] Unable to add a public SSH Key <MAAS:Triaged> <https://launchpad.net/bugs/1604128> | 19:45 |
mup | Bug #1604128 opened: [2.0RC2] Unable to add a public SSH Key due to lp1604147 <cdoqa-blocker> <MAAS:In Progress by allenap> <MAAS 2.0:New> <MAAS trunk:In Progress by allenap> <maas (Ubuntu):New> <maas (Ubuntu Xenial):New> <maas (Ubuntu Yakkety):New> <https://launchpad.net/bugs/1604128> | 21:24 |
mup | Bug #1604169 opened: maas login yields "ImportError: No module named 'maasserver'" <MAAS:New> <https://launchpad.net/bugs/1604169> | 22:01 |
mup | Bug #1604128 changed: [2.0RC2] Unable to add a public SSH Key due to lp1604147 <cdoqa-blocker> <verification-needed> <MAAS:In Progress by allenap> <MAAS 2.0:New> <MAAS trunk:In | 22:48 |
mup | Progress by allenap> <maas (Ubuntu):Fix Released> <maas (Ubuntu Xenial):Fix Committed> <maas (Ubuntu Yakkety):Fix Released> <https://launchpad.net/bugs/1604128> | 22:48 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!