[05:33] <siva> newmember: I am using  MAAS 1.9.3 for trusty
[05:41] <newmember> siva, thanks
[05:41] <newmember> I am just installing MAAS from iso, instead of the autopilot package from the website
[05:44] <newmember> the version from the ubuntu website was using 1.8
[07:06] <newmember> okay now I am ver MAAS Version 2.0.0 (rc2+bzr5156)
[07:20] <newmember> okay
[07:20] <newmember> when adding vmware chassis I get this error:   Unable to find a rack controller with access to chassis 192.168.0.124
[07:20] <newmember> I can ping the vmware from maas
[07:25] <siva> newmember: Yes. At starting I also tried with MAAS from Iso. It was installing the version 1.8.
[07:48] <newmember> siva, did you add a esx chassis to your environment?
[07:50] <newmember> with a tcpdump i dont even see the maas host trying to connect to the esx server, no packets are sent
[08:17] <newmember> hmmmmm
[08:17] <newmember> dhcpd not running
[08:52] <siva> newmember: Actually, I didn't try On VMware VMs. I will try it later.
[08:57] <newmember> two issues now
[08:57] <newmember> 1.maas-dchp not running
[08:57] <newmember> 2.cant add vmware esx server to chassis
[08:58] <newmember> for #2 there is a cert error
[08:58] <newmember> for #1 still investigating
[09:00] <siva> newmember:  https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1608639 look at this once for adding certifications
[09:06] <newmember> root@MAAS:/home/support# maas profile machines add-chassis chassis_type=vmware username=root password=new.pass protocol='https+unverified' hostname=192.168.1.9 prefix_filter=node-
[09:06] <newmember> failed
[09:06] <newmember> argument COMMAND: invalid choice: 'profile' (choose from 'login', 'refresh', 'list', 'logout', 'apikey', 'createadmin', 'changepassword')
[10:16] <newmember> urgh
[11:16] <mup> Bug #1612620 opened: [API] MAAS server endpoint set_config operation returns OK rather than an object or redirect <MAAS:New> <https://launchpad.net/bugs/1612620>
[13:28] <Kyoku> can i install a custom freebsd iso on maas?
[13:53] <kiko> Kyoku, you may be able to, but you'll need to prepare it so curtin can install it
[13:53] <kiko> Kyoku, curtin basically takes an image and, dd-style, writes it to disk
[13:53] <kiko> smoser is the local expert
[13:53] <kiko> newmember, maas login first :)
[13:54] <kiko> newmember, and the CLI is very confusing, we'll fix it
[14:16] <mup> Bug #1612662 opened: strange raid(10) layout <MAAS:New> <https://launchpad.net/bugs/1612662>
[14:16] <mup> Bug #1612668 opened: [2.1 API] devices endpoint 'set_zone' operation returns null on success <MAAS:New> <https://launchpad.net/bugs/1612668>
[14:39] <smoser> Kyoku, freebsd would be tough.
[14:39] <smoser> if you could get a ddable image that would boot that'd be the easiest path.
[14:39] <smoser> theres just not been any time to document or clean up how non-ubuntu curtin installs should work.
[14:40] <mup> Bug #1612676 opened: [Card sorting] Move DNS to Networks or make it accessible from Networks <MAAS:New> <https://launchpad.net/bugs/1612676>
[14:40] <mup> Bug #1612680 opened: [Card sorting] Move DHCP configuration on a higher level in Networks or make it accessible from the Networks main page <MAAS:New> <https://launchpad.net/bugs/1612680>
[14:41] <Kyoku> smoser i have a bottable VMDK that i tried to import into AWS but AWS doesn't support GPT partitions
[14:42] <Kyoku> smoser so if there's a way to import VMDK into maas that might work if GPT is supported
[14:43] <smoser> i'm pretty sure there is not such a way.
[14:45] <Kyoku> seems to be very few cloud services that allow install from iso, and i'm not sure why
[14:46] <kiko> Kyoku, they all need special hooks to run cloud-init?
[14:47] <Kyoku> beyond me, i have no idea but to me bare metal as a service should allow me to install 'anything' - isn't that the point of calling it metal as a service?
[14:47] <smoser> Kyoku, its just very hard to do.
[14:48] <smoser> there is no standard way to boot an iso over a network
[14:48] <smoser> and to automate installation of it.
[14:48] <Kyoku> well it's easy in my head - you upload an iso and give me console to install to disk and it runs in cloud
[14:48] <Kyoku> lol
[14:48] <smoser> but even booting that iso is not easy
[14:49] <Kyoku> ravello do it, but it's stupid expensive and poor performance
[15:01] <mup> Bug #1612662 changed: strange raid(10) layout <MAAS:Invalid> <https://launchpad.net/bugs/1612662>
[15:01] <mup> Bug # opened: 1612681, 1612683, 1612685, 1612687, 1612689
[16:43] <mup> Bug #1612687 changed: Juju not showing real states of deployed nodes via MAAS. <juju-core:New> <https://launchpad.net/bugs/1612687>
[18:05] <jwitko> Hey All,  if I have a MaaS region/cluster controller setup on a single machine and the server shits the bed what would happen if I was to just create another one in its place with all the same settings?  Servers would reach out to the new DHCP server but it wouldn't know anything about their hostnames or current IPs would it?  Would this be disasterous or is there some sort of mechanism that
[18:05] <jwitko> comes into play here?
[18:17] <mup> Bug #1612755 opened: Xenial Deploy fails when using customized interfaces file (curtin, bonding) <canonical-bootstack> <MAAS:New> <https://launchpad.net/bugs/1612755>
[19:17] <kiko> jwitko, there is no mechanism that comes into play, you'll need to back up the SQL DB
[19:21] <jwitko> kiko, thanks!
[19:25] <kiko> jwitko, with MAAS 2.0, you can set up HA components, but you still need to make PostgreSQL HA
[19:25] <jwitko> yup, i think its time to give 2.0 a shot
[22:00] <mup> Bug #1229458 opened: grubnetx64.efi tftp client does not work over ipv6 <verification-needed> <MAAS:Confirmed for lamont> <grub2 (Ubuntu):Fix Released by cyphermox> <grub2-signed
[22:00] <mup> (Ubuntu):Fix Released> <grub2 (Ubuntu Xenial):Fix Committed by cyphermox> <grub2-signed (Ubuntu Xenial):Fix Committed by cyphermox> <https://launchpad.net/bugs/1229458>