[03:19] <mup> Bug #1557839 opened: machine_readable_bytes() accepts invalid and misleading SI prefixes <MAAS:Triaged> <https://launchpad.net/bugs/1557839>
[10:41] <mup> Bug #1558000 opened: [patch] Existing user "maas" is used/removed when installing/removing maas-common <MAAS:New> <https://launchpad.net/bugs/1558000>
[10:41] <neiljerram> Hi there, I'm struggling with MAAS networking after just upgrading to 1.9.1.  Is there anyone around who might be able to help?
[16:30] <mup> Bug #1538280 opened: MAAS 1.9.0+bzr4533 can not start HP ProLiant DL360 Gen9 servers over IPMI <MAAS:New> <https://launchpad.net/bugs/1538280>
[17:57] <mup> Bug #1558188 opened: during import images boostrap fails with gomaasapi: got error back from server: 400 BAD REQUEST ({"distro_series": ["'trusty' is not a valid distro_series.
[17:57] <mup> It should be one of: '', 'windows/win2012hvr2', 'ubuntu/precise'..."]}) <oil> <MAAS:Triaged> <MAAS 1.9:Triaged> <https://launchpad.net/bugs/1558188>
[18:26] <roaksoax> 4/win 7
[18:26] <jwitko> hey guys, can someone help me understand how maas works once I install it?   I have it installed on a machine with about 7 servers on the same subnet.  I thought once MAAS was installed they would be able to PXE boot via obtaining a DHCP lease.  Is this the expectation?  Do I need to go through and add them manually as nodes first to MAAS?
[18:28] <roaksoax> jwitko: you need to:
[18:28] <roaksoax> 1. import images (trusty at the very least)
[18:28] <jwitko> roadsoax,  did that
[18:28] <roaksoax> 2. configure a cluster controller interface to provide DHCP (if using <= 1.9), if using >2.0alpha1, you'd need to configure a VLAN to provide DHCP
[18:29] <jwitko> I also enabled the interface for DNS and DHCP
[18:29] <jwitko> I'm using 1.9
[18:29] <roaksoax> jwitko: right, so then that should be all you need
[18:29] <roaksoax> jwitko: to get it to PXE boot and register to MAAS
[18:29] <jwitko> roaksoax, ok great thanks.  So it looks like my issue is DHCP not coming across the network
[18:30] <jwitko> i reboot a server and it sends out a request, but tcpdump udp port 67 on my maas controller shows no traffic
[18:30] <roaksoax> jwitko: ps faux | grep dhcpd  to ensure it is running
[18:31] <roaksoax> jwitko: otherwise, maybe something with the networking?
[18:33] <jwitko> roaksoax, aye it is running and i see port 67 listening on netstat
[18:34] <jwitko> so Yea, I think the switch needs to be configured properly to allow dhcp traffic or something.  will investigate with network team
[18:34] <jwitko> thanks!
[18:34] <jwitko> roaksoax, one more question if you don't mind
[18:34] <jwitko> where would i be able to see incoming DHCPD logs?  /var/log/maas/maas.log ?
[18:35] <roaksoax> jwitko: syslog
[18:35] <jwitko> gracias
[18:36] <roaksoax> de nada :)
[18:38] <jwitko> yea, I can actually see a DHCPDISCOVER and DHCPOFFER in the logs,  just not from any of my blades lol
[18:38] <jwitko> from some unknown MAC
[18:38] <jwitko> but the point is it can see and act on DHCP
[18:40] <jwitko> roaksoax, so if this is just going to start PXE booting from the standard inventory download.... is there a default user/pass its setting?
[18:41] <roaksoax> jwitko: for IPMI based BMC's, it will create a 'maas' user with a random password, only internal to maas
[18:41] <jwitko> can I add customizations to that sort of stuff?  like a kickstart file ?   or is the only option to build a custom image and serve that ?
[18:42] <roaksoax> jwitko: what would you be trying to deploy ?
[18:42] <jwitko> just trying to spin up some standard ubuntu servers
[18:42] <jwitko> nothing fancy
[18:42] <jwitko> but I need to be able to access them once they're spun up  :)
[18:42] <roaksoax> jwitko: so /etc/maas/preseeds/curtin_userdata allows you to customize the install
[18:42] <jwitko> ah, awesome
[18:42] <roaksoax> jwitko: you will have to add your SSH key in MAAS
[18:43] <roaksoax> jwitko: and maas will install the SSH key on the system for the 'ubuntu' user
[18:47] <jwitko> roaksoax, do you have an example of this being done?  having a hard time finding one
[18:49] <roaksoax> jwitko: under the user settings page you will be able to add your ssh public key
[18:49] <roaksoax> jwitko: with that you will be able to deploy machines
[18:49] <jwitko> ahh
[18:49] <roaksoax> jwitko: maas will automatically import your key in the deployed system
[18:50] <jwitko> sorry I was trying to edit the files manually
[19:14] <Free99> hey everyone, I got my maas setup working! I have a bunch of nodes ready and deployed. Question: I need to make all of them mount an NFS share. how do I do that?
[19:20] <roaksoax> Free99: if they are already deployed and you did it with Juju, you could create a subordinate charm to do so. If they are not deployed by juju, you'll have to do that manually
[19:21] <roaksoax> Free99: if you ar eplanning to re-deploy them, you could customize /etc/maas/preseeds/curtin_userdata, to creata new, late_command for 'in-target' that would do something to the system, so that when it boots after it installs, it mounts the NFS share
[21:29] <dragnell87> hello everyone
[21:30] <dragnell87> there is any way to seize control of power managament for VM in Vpshere setup
[21:32] <dragnell87> i only have control over my VM using vmware cloud director, and i can find a way to properly add a note to maas cluster controller
[21:32] <dragnell87> *can't
[21:33] <dragnell87> *node
[22:25] <fritchie> is there a way to view the porogress when importing boot images to a new MAAS install - seems to be taking longer than I would imagine
[22:43] <roaksoax> fritchie: you can do it via the API, or hover over the spinner next to the image
[22:43] <roaksoax> next to the image being downloaded *
[22:58] <Discipulus> Quick question for you guys - how do I run MAAS with high availability? I saw that it was scheduled for 14.04 but I haven't seen anything in the documentation.
[23:02] <roaksoax> Discipulus: HA is for 16.04 and on 2.0, which is currently alpha
[23:02] <roaksoax> Discipulus: sitll no documentation available yet
[23:03] <fritchie> roaksoax, ty
[23:03] <roaksoax> fritchie: but it is fairly simple for the rack controllers
[23:03] <roaksoax> fritchie: just add more rack controller that is connected to the same VLAN
[23:04] <roaksoax> and when enabling DHCP you can select which one is primary and which one is secondary
[23:06] <Discipulus> Roaksoax, thanks.
[23:14] <fritchie> roaksoax, do you know where the boot image being downloaded is stored to disk?
[23:15] <roaksoax> fritchie: on the region controller they are stored in the DB< on the rack/cluster controller on /var/lib/maas/
[23:15] <roaksoax> fritchie: on the region controller they are stored in the DB< on the rack/cluster controller on /var/lib/maas/boot-resources/current
[23:15] <fritchie> ty
[23:22] <mup> Bug #1558314 opened: maas server is overloaded - twistd and postgres processes > 200% <oil> <MAAS:New> <https://launchpad.net/bugs/1558314>
[23:31] <mup> Bug #1558314 changed: maas server is overloaded - twistd and postgres processes > 200% <oil> <MAAS:New> <https://launchpad.net/bugs/1558314>
[23:34] <mup> Bug #1558314 opened: maas server is overloaded - twistd and postgres processes > 200% <oil> <MAAS:New> <https://launchpad.net/bugs/1558314>