[05:46] <mup> Bug #1578059 opened: Default route not coming up with juju 1.25.5 and bonding <canonical-bootstack> <MAAS:New> <https://launchpad.net/bugs/1578059>
=== frankban_ is now known as frankban
[14:24] <mup> Bug #1578230 opened: MAAS only learns of new hardware by delete and re-add <canonical-bootstack> <MAAS:New> <https://launchpad.net/bugs/1578230>
[14:54] <mup> Bug #1578230 changed: MAAS only learns of new hardware by delete and re-add <canonical-bootstack> <MAAS:New> <https://launchpad.net/bugs/1578230>
[15:29] <neiljerram> Would you expect a MAAS controller on Trusty to be able to deploy a Xenial distro onto a node?
[17:12] <mup> Bug #1578309 opened: Node model allows blank hostnames <MAAS:Triaged by lamont> <https://launchpad.net/bugs/1578309>
[17:57] <mup> Bug #1578333 opened: node with unconfigured bonded nic can't be reached <landscape> <MAAS:New> <https://launchpad.net/bugs/1578333>
[18:07] <Gryd3> any reason a Vm environment would be unfit for evaluating MaaS?
[18:08] <meepmeep22> Heh
[18:08] <meepmeep22> it depends on your usage
[18:08] <meepmeep22> Are you using it for deployment?
[18:09] <mup> Bug #1578333 changed: node with unconfigured bonded nic can't be reached <landscape> <MAAS:New> <https://launchpad.net/bugs/1578333>
[18:10] <Gryd3> nope. want to spin up VMs for management nodes, and try to test fire a single physical node to see what kind of control I have
[18:11] <meepmeep22> MaaS is relatively easy to setup. You can start it using VM's, but you must have a large block of IP's and resources for it to use
[18:12] <meepmeep22> If your fluent with Debian variant systems you should be able to get it done in a couple hours.
[18:13] <mup> Bug #1578333 opened: node with unconfigured bonded nic can't be reached <landscape> <MAAS:New> <https://launchpad.net/bugs/1578333>
[18:51] <roaksoax> Gryd3: you can test MAAS against VM's in KVM
[18:52] <roaksoax> Gryd3: for example, install MAAS on the host, and have it manage KVM's created in libvirt as machines
[19:01] <mup> Bug #1578347 opened: Can't configure an ssd into a cache set while node is allocated <MAAS:New> <https://launchpad.net/bugs/1578347>
[19:13] <mup> Bug #1578347 changed: Can't configure an ssd into a cache set while node is allocated <MAAS:New> <https://launchpad.net/bugs/1578347>
[19:22] <mup> Bug #1578347 opened: Can't configure an ssd into a cache set while node is allocated <MAAS:New> <https://launchpad.net/bugs/1578347>
[19:29] <brendand> Gryd3, i'm doing the same at the moment
[19:29] <brendand> just had some success
[19:43] <Gryd3> roaksoax and brendand . Thanks, I'm planning on spinning something up to see how I  like it
=== test is now known as Guest29082
[20:40] <Guest29082> maas fail to deploy
[20:41] <Guest29082> Problem during bootstrap: '{'err': 'Bootstrapping environment "maas"\nStarting new instance for initial state server\nLaunching instance\nWARNING no architecture was specified, acquiring an arbitrary node\nWARNING no architecture was specified, acquiring an arbitrary node\nWARNING no architecture was specified, acquiring an arbitrary node\nWARNING no architecture was specified, acquiring an arbitrary node\nWARNING no architecture w
[20:42] <alanv72> when running openstack-install with autopilot.. how long does it normally take for the juju bootstrap process take?
[20:43] <Guest29082> exit
[20:53] <brendand> all my nodes are up and at the login screen but show the status as 'failed commisioning' (and with a green dot next to them?)
[21:28] <mup> Bug #1578395 opened: Changing minimum commissioning kernel in UI gives unexpected result <oil> <MAAS:New> <https://launchpad.net/bugs/1578395>
[21:59] <roaksoax> Gryd3: that seems like an issue with Juju maybe
[21:59] <roaksoax> err
[21:59] <roaksoax> Gryd3: sry :)
[22:00] <Gryd3> haha. no prob
[22:00] <roaksoax> brendand: means the machine failed to commission for whatever reason but they are ON
[22:10] <brendand> roaksoax, ok - you'll have to explain me the difference between 'commisioning' and 'installing'