[07:20] <spaok_> does anyone know why a bunch of machines would go allocated but not start deploying? We had 5 servers from 25 deploy, but the rest are stuck in allocated
[09:19] <spaok_> we seems to be having an issue with MAAS not releasing Ip's it has observed, does anyone have an ideas on how to flush observed ip's from a subnet's ip use?
[10:10] <spaok_> we hacked the DB to make it work
[11:12] <mah> Hi all, I is it possible to increase a VM RAMS after the maas deployment ?
[11:45] <brendand> mah, probably, but may require recommissioning for maas to detect it
[11:45] <brendand> maybe not
[11:46] <mah> when I tried to edit it from the maas UI
[11:47] <mah> I found it blocked can not be edited
[11:47] <mah> So is there another way to configure it
[11:47] <mah> or I have to deploy MAAS again from begining ?
[11:48] <brendand> mah, oh well maas does not control the RAM, you would have to do that with the VM management sw
[11:48] <brendand> maas is not creating the machines
[11:48] <mah> hmmm
[11:48] <brendand> mah, which virtualization sw are you using?
[11:48] <mah> and after that I have to do commissioning ?
[11:49] <brendand> mah, maybe - maas may just detect the change, but i doubt that it will unless the machines changes state, e.g. by recommissioning or deploying
[11:50] <mah> in that case I need to do recommissionig the changed machine only not all the nodes
[11:50] <mah> right ?
[11:50] <brendand> mah, oh for sure
[11:50] <mah> ok fine
[11:50] <brendand> mah, it will only be needed for that node
[11:50] <mah> Thanks a lot
[11:51] <mah> I have node 0 and it has 3 VMs
[11:51] <mah> but I will do these changes on one VM only
[11:51] <mah> so just recommissiong that VM not all the 3
[11:52] <mah> I am using Virtual Machine Manager
[11:53] <brendand> mah, right, so kvm - you can either modify the ram through the ui or use the virsh command line tool
[11:53] <mah> Ok
[11:53] <mah> thanks
[11:56] <brendand> mah, bonus - here's how to change the memory on a running machine:
[11:57] <brendand> virsh destroy vm-name
[11:57] <brendand> virsh setmaxmem vm-name 4GB
[11:57] <mah> it is not running  :)
[11:57] <brendand> virsh start vm-name
[11:57] <mah> but thanks for that bonus too
[11:57] <brendand> virsh setmem vm-name 4GB
[11:58] <brendand> setmem only works when it's running
[11:58] <mah> hmmm
[11:58] <brendand> and setmaxmem doesn't
[11:59] <mah> so setmaxmem works when it is not running ?
[12:19] <brendand> mah, yes - you can't setmaxmem on a running vm
[13:23] <mup> Bug #1637182 opened: Help and documentation 'list of unicodes' inconsistent <MAAS:New> <MAAS 1.9:New> <MAAS 2.0:New> <MAAS 2.1:New> <https://launchpad.net/bugs/1637182>
[13:23] <mup> Bug #1637183 opened: New subnets and not_subnets allocate params missing from help and docs <MAAS:New> <MAAS 2.0:New> <MAAS 2.1:New> <https://launchpad.net/bugs/1637183>
[13:32] <mup> Bug #1637192 opened: Allocate using subnets or not_subnets with space fails <MAAS:New> <MAAS 2.0:New> <MAAS 2.1:New> <https://launchpad.net/bugs/1637192>
[13:53] <mup> Bug #1637183 changed: New subnets and not_subnets allocate params missing from help and docs <MAAS:New> <MAAS 2.0:New> <MAAS 2.1:New> <https://launchpad.net/bugs/1637183>
[13:53] <mup> Bug #1637198 opened: Unrecognised params silently ignored over api <MAAS:New> <https://launchpad.net/bugs/1637198>
[13:53] <mup> Bug #1637203 opened: Allocate using subnets params gives unhelpful errors <MAAS:Triaged> <https://launchpad.net/bugs/1637203>
[15:31] <solefald> so, a slightly philosophical question here... should i have MAAS do as much setup as possible or should i have Ansible or Puppet do things after the server boots up?
[15:31] <solefald> I've always been a proponent of having a server boot up in a ready state, ready to go, but i am having issues achieving some things with MAAS.
[15:32] <solefald> for example, I need to install Mellanox 40 gigabit interface drivers but ,unfortunately, it bombs in MAAS because Mellanox installer needs to compile a bunch of stuff
[15:34] <roaksoax> solefald: i'd suggest get maas to do as much setup as possible
[15:34] <solefald> and without having 40 gig network, I cant configure and install a few things, which holds me back from installing some other things.
[15:34] <roaksoax> solefald: that would match what MAAS knows about vs what the machine actually reflects
[15:38] <mup> Bug #1637198 changed: Unrecognised params silently ignored over api <MAAS:New> <https://launchpad.net/bugs/1637198>
[16:03] <mup> Bug #1637246 opened: MaaS should use configured names for VLAN interfaces <MAAS:Confirmed> <MAAS 2.0:Confirmed> <MAAS 2.1:Confirmed> <maas (Ubuntu):New> <https://launchpad.net/bugs/1637246>
[16:03] <mup> Bug #1637246 opened: MaaS should use configured names for VLAN interfaces <MAAS:Confirmed> <MAAS 2.0:Confirmed> <MAAS 2.1:Confirmed> <maas (Ubuntu):New> <https://launchpad.net/bugs/1637246>
[16:30] <mup> Bug #1637256 opened: MaaS might disrupt network connectivity by probing DHCP services <maas (Ubuntu):New> <https://launchpad.net/bugs/1637256>
[16:45] <mup> Bug #1637198 opened: Unrecognised params silently ignored over api <MAAS:New> <https://launchpad.net/bugs/1637198>
[16:51] <mup> Bug #1637198 changed: Unrecognised params silently ignored over api <MAAS:New> <https://launchpad.net/bugs/1637198>
[17:12] <mup> Bug #1637198 opened: Unrecognised params silently ignored over api <MAAS:New> <https://launchpad.net/bugs/1637198>
[17:15] <mup> Bug #1637198 changed: Unrecognised params silently ignored over api <MAAS:Confirmed> <https://launchpad.net/bugs/1637198>
[18:31] <shubjero> solefald: im finding it easier to have maas just do a minimal install and ansible do everything else
[18:35] <solefald> shubjero: yeah, im leaning this way. i can get way fancier with Ansible and keep everything in one place.
[18:36] <shubjero> same
[18:37] <shubjero> some of the stuff maas uses like curtin is poorly documented, i cant make heads or tails of things
[18:37] <solefald> shubjero: i think you meant "not documented at all" :)
[18:37] <shubjero> or the way maas does certain things like nic bonding, jumbo frames.. doesnt work properly
[18:37] <shubjero> so we deploy it with maas but then use ansible to overwrite /etc/network/interfaces with a config that seems to work better
[18:38] <solefald> thats exactly where im stuck now. converting it all to Ansible at the moment
[18:38] <shubjero> lots of little things
[18:40] <solefald> installing mellanox 40 gig drives  and bonding into 80 gig interface, and changing MTU's everywhere, etc.  MAAS just bombs.
[18:40] <solefald> plus i hate the fact that there is no easy way to test the preseed file. have to release/deploy my test box literally 100 times a day
[18:41] <solefald> 1 typo and 20 minutes are gone
[18:43] <shubjero> haha yeah, espescially painful with bare metal
[18:43] <shubjero> you can only test so many things with a vm
[18:43] <shubjero> at some point you need to move to the real thing where you have like you say, unique 40g interfaces & etc
[18:43] <shubjero> btw, im curious what you are doing with servers equipped with 80Gbps
[18:44] <shubjero> I work in cancer research and admin a large openstack cluster, our servers are 10Gbps and 40(4x10) connected
[18:44] <shubjero> 40Gbps for ceph nodes
[18:44] <shubjero> 10Gbps for compute nodes
[18:47] <solefald> deep learning cluster. rendering and compute nodes
[19:29] <GA> Hi, I'm trying to pass a "mount" command using /etc/maas/presseed/curtin_userdata, but - it fails the deployment. I've tried multiple syntax'es, no success though.
[19:30] <GA> e.g   mount_data: ["curtin", "in-target", "--", "sh", "-c", "mount", "192.168.1.1:", "/data", "/data"]
[19:30] <GA> I was able to install nfs-common via presseed, so the nfs client is there (the provisioned system).
[19:31] <shubjero> oh, curtin
[19:58] <solefald> GA: try specifying filesystem
[21:01] <mup> Bug #1621507 opened: initramfs-tools configure_networking() fails to dhcp ipv6 addresses <maas-ipv6> <verification-failed> <MAAS:In Progress by lamont> <initramfs-tools (Ubuntu):In Progress by cyphermox> <isc-dhcp (Ubuntu):Fix Released by cyphermox> <klibc (Ubuntu):Won't Fix> <open-iscsi
[21:01] <mup> (Ubuntu):Fix Released> <initramfs-tools (Ubuntu Xenial):Triaged> <isc-dhcp (Ubuntu Xenial):Fix Released> <klibc (Ubuntu Xenial):Won't Fix> <open-iscsi (Ubuntu Xenial):Fix Released> <initramfs-tools (Ubuntu Yakkety):In Progress by cyphermox> <isc-dhcp (Ubuntu Yakkety):Fix Released by cyphermox>
[21:01] <mup> <klibc (Ubuntu Yakkety):Won't Fix> <open-iscsi (Ubuntu Yakkety):Fix Released> <klibc (Debian):New> <https://launchpad.net/bugs/1621507>
[21:04] <mup> Bug #1621507 changed: initramfs-tools configure_networking() fails to dhcp ipv6 addresses <maas-ipv6> <verification-failed> <MAAS:In Progress by lamont> <initramfs-tools (Ubuntu):In Progress by cyphermox> <isc-dhcp (Ubuntu):Fix Released by cyphermox> <klibc (Ubuntu):Won't Fix> <open-iscsi
[21:04] <mup> (Ubuntu):Fix Released> <initramfs-tools (Ubuntu Xenial):Triaged> <isc-dhcp (Ubuntu Xenial):Fix Released> <klibc (Ubuntu Xenial):Won't Fix> <open-iscsi (Ubuntu Xenial):Fix Released> <initramfs-tools (Ubuntu Yakkety):In Progress by cyphermox> <isc-dhcp (Ubuntu Yakkety):Fix Released by cyphermox>
[21:04] <mup> <klibc (Ubuntu Yakkety):Won't Fix> <open-iscsi (Ubuntu Yakkety):Fix Released> <klibc (Debian):New> <https://launchpad.net/bugs/1621507>
[21:07] <mup> Bug #1621507 opened: initramfs-tools configure_networking() fails to dhcp ipv6 addresses <maas-ipv6> <verification-failed> <MAAS:In Progress by lamont> <initramfs-tools (Ubuntu):In Progress by cyphermox> <isc-dhcp (Ubuntu):Fix Released by cyphermox> <klibc (Ubuntu):Won't Fix> <open-iscsi
[21:07] <mup> (Ubuntu):Fix Released> <initramfs-tools (Ubuntu Xenial):Triaged> <isc-dhcp (Ubuntu Xenial):Fix Released> <klibc (Ubuntu Xenial):Won't Fix> <open-iscsi (Ubuntu Xenial):Fix Released> <initramfs-tools (Ubuntu Yakkety):In Progress by cyphermox> <isc-dhcp (Ubuntu Yakkety):Fix Released by cyphermox>
[21:07] <mup> <klibc (Ubuntu Yakkety):Won't Fix> <open-iscsi (Ubuntu Yakkety):Fix Released> <klibc (Debian):New> <https://launchpad.net/bugs/1621507>
[22:16] <mup> Bug #1636969 opened: [1.9] Multiple negative spaces constraints given and rejected by MAAS <ci> <jujuqa> <maas-provider> <networking> <juju:Triaged> <MAAS:Fix Committed> <MAAS 1.9:Invalid> <https://launchpad.net/bugs/1636969>
[22:28] <mup> Bug #1636969 changed: [1.9] Multiple negative spaces constraints given and rejected by MAAS <ci> <jujuqa> <maas-provider> <networking> <juju:Triaged> <MAAS:Fix Committed> <MAAS 1.9:Invalid> <https://launchpad.net/bugs/1636969>
[22:34] <mup> Bug #1636969 opened: [1.9] Multiple negative spaces constraints given and rejected by MAAS <ci> <jujuqa> <maas-provider> <networking> <juju:Triaged> <MAAS:Fix Committed> <MAAS 1.9:Invalid> <https://launchpad.net/bugs/1636969>