[03:07] <pacavaca_> Am I right expecting MAAS in this case http://d.pr/i/1j30X to set default gateway to be the gateway of a single configured network and persist it in /etc/network/interfaces ?
[03:51] <pacavaca_> Ok, seems I've figured it out. Not sure if it's a bug or feature, I'll just leave it here: http://d.pr/i/1kvpd
[07:24] <jojden> hii
[07:24] <jojden> http://askubuntu.com/questions/792289/bson-data-iteration
[07:28] <jojden> when i call the resp = self.client.get(u"nodes/%s/" % node_id, "details")
[07:29] <jojden> print  resp.read()
[07:29] <jojden> I am getting following o/p
[07:29] <jojden> http://pastebin.com/QXEqEgn1
[07:29] <jojden> how can i iterate this
[07:32] <jojden> http://askubuntu.com/questions/792637/get-node-details
[08:56] <brendand> jojden, that's the lshw output, what are you trying to do with it? i didn't quite understand what you meant by 'iterate it'?
[08:58] <jojden> I want to iterate each node details from that
[08:58] <jojden> And that is combination of lldp and lshw o/p right ?
[08:58] <jojden> brendand
[09:00] <brendand> i'm not sure what lldp is, but yeah it looks like that
[09:02] <brendand> jojden, i'd need to check if the api provides a way to specify the output to be in json format but that would be the most straightforward. otherwise you need to use an xml parser, which are a bit of a pain to use for the most part
[09:02] <jojden> yes
[09:02] <jojden> https://maas.ubuntu.com/docs/api.html
[09:03] <jojden> here in API it saying that the o/p will be BSON istead of JSON
[09:03] <brendand> jojden, what are you trying to do exactly?
[09:03] <jojden> Returns a {detail_type: xml, ...} map, where detail_type is something like “lldp” or “lshw”.
[09:03] <jojden> Note that this is returned as BSON and not JSON. This is for efficiency, but mainly because JSON can’t do binary content without applying additional encoding like base-64.
[09:05] <jojden> What I need is, I need to iterate businfo, physid, description etc
[09:06] <jojden> Also if I have lldp details, then I need to iterate that also
[09:09] <brendand> jojden, oh right. while the content returned is BSON the lshw and lldp output are still in xml
[09:09] <jojden> yes
[10:24] <mup> Bug #1597266 opened: MAAS - multiple DNS zones with the same duplicated zone name <cpec> <maas> <MAAS:New> <https://launchpad.net/bugs/1597266>
[10:30] <mup> Bug #1597266 changed: MAAS - multiple DNS zones with the same duplicated zone name <cpec> <maas> <MAAS:New> <https://launchpad.net/bugs/1597266>
[10:42] <mup> Bug #1597266 opened: MAAS - multiple DNS zones with the same duplicated zone name <cpec> <maas> <MAAS:New> <https://launchpad.net/bugs/1597266>
[12:07] <f1gjam> 	hey guys, im releaseing a server and i have enabled erase disk in settings. Is there anyway i can track the progress of the erase task?
[12:22] <valeech> f1gjam: does /var/log/maas/rsyslog/[host].log show anything?
[12:22] <f1gjam> this is MaaS 1.9
[12:22] <f1gjam> rsyslog is empty
[12:22] <f1gjam> :'(
[12:25] <valeech> f1gjam: sorry, that was all I had :) I am pretty new to maas
[12:36] <mup> Bug #1597324 opened: [2.0b8] Unable to set default gateway interface <MAAS:New> <https://launchpad.net/bugs/1597324>
[12:48] <mup> Bug #1597324 changed: [2.0b8] Unable to set default gateway interface <MAAS:New> <https://launchpad.net/bugs/1597324>
[12:54] <mup> Bug #1597324 opened: [2.0b8] Unable to set default gateway interface <MAAS:New> <https://launchpad.net/bugs/1597324>
[13:01] <secate> hi there
[13:02] <secate> has anyone attempted to use "set-default-gateway" in a recent build of MAAS?
[13:02] <secate> I should have said; has anyone had success using "set-default-gateway" in a recent build of MAAS? :)
[13:09] <kiko> I've heard of problems with it
[13:09] <kiko> mpontillo may know more
[13:10] <f1gjam> Kiko any idea how to see how far disk erasing has gone?
[13:11] <kiko> f1gjam, blake_r_ would know, but what /I/ know is that it takes a LONG time
[13:11] <secate> thanks kiko
[13:11] <kiko> f1gjam, we have a feature request for this cycle to use SATA SE which would make it faster for most models
[13:12] <secate> I used it in an earlier release (can't remember if it was 1.9x or 2.0ax) but I'm testing beta8 now and it's not working
[13:12] <secate> filed a bug @ https://bugs.launchpad.net/maas/+bug/1597324
[13:15] <kiko> secate, thanks
[13:18] <mpontillo> thanks secate, I'll take a look
[13:35] <f1gjam> kiko thanks mate, so it was a bad idea to do it :(
[13:35] <kiko> f1gjam, if it helps, you can just abort it and move on :)
[13:36] <f1gjam> only problem now is to find out why landscape stops
[13:36] <kiko> f1gjam, it won't cause any problems to stop the process half-way
[13:36] <f1gjam> at 70%
[13:37] <mup> Bug #1597345 opened: maas 1.9.3: twistd high cpu usage <kanban-cross-team> <landscape> <MAAS:New> <https://launchpad.net/bugs/1597345>
[13:40] <mup> Bug #1597345 changed: maas 1.9.3: twistd high cpu usage <kanban-cross-team> <landscape> <MAAS:New> <https://launchpad.net/bugs/1597345>
[13:43] <mup> Bug #1597345 opened: maas 1.9.3: twistd high cpu usage <kanban-cross-team> <landscape> <MAAS:New> <https://launchpad.net/bugs/1597345>
[13:45] <secate> mpontillo: no worries, if you need anything more from me just let me know
[15:02] <sjl> is there a way maas can configure a node's IP without DHCP?  Trying to avoid having to require every tenant's network to support DHCP.
[15:43] <kiko> sjl, we need DHCP for the commissioning/deployment process, but not after that
[15:43] <kiko> sjl, can you explain what you're looking for?
[15:48] <sjl> we are expecting maas to configure our tenant machines networking (at most can have 3 ip's (private, public, and storage)), and with the exception of storage, each tenant has their own private and public vlan
[15:49] <sjl> having to have a rack controller listen on every tenant vlan seems too heavy, and also introduce an attack vector into maas.
[15:52] <sjl> atm looking at advanced curtin, which looks promising but requires some digging
[15:56] <kiko> sjl, with MAAS 1.9 and 2.0 you can attribute IPs without DHCP
[15:56] <kiko> sjl, they get written into the curtin config directly
[15:56] <kiko> have you tried that functionality?
[15:56] <kiko> sjl, that works for each interface the machine has
[15:56] <sjl> don't think so, that looks like what I need!
[15:58] <sjl> On a machine in the Ready state, I've changed its interface IP from "Auto assign" to "Static assign" but that static IP is still provided to the node via DHCP
[15:58] <sjl> is that what you meant?
[15:59] <sjl> or at least the static IP was DHCP Offered during PXE
[16:07] <sjl> kiko, hmm perhaps I've setup maas region controller incorrectly.  The vlan (untagged) I'm trying to allocate a static IP from is setup with DHCP in maas.  let me try a new vlan without DHCP enabled in maas, and see what happens.
[16:08] <kiko> sjl, ah
[16:08] <kiko> sjl, so PXE always uses DHCP
[16:08] <kiko> sjl, but once installed the machine no longer PXE boots
[16:40] <sjl> does maas 2.0 have an api method of configuring a node's vlan interfaces like this curtin example? https://github.com/battlemidget/astokes.org/blob/master/lib/posts/2013-10-09-customizing-fastpath-curtin-installations.md
[16:56] <mattrae> hi, i'm using MAAS 2.0 beta 8. when i check the box in settings for 'Enable the use of an APT and HTTP/HTTPS proxy', on the deployed nodes I am seeing the proxy added to the apt configuration.. but i don't see any http_proxy or https_proxy enviornment variables being set on the nodes
[16:56] <mattrae> should I expect to see http_proxy and https_proxy set on the deployed nodes?
[16:58] <mattrae> i don't see http_proxy or https_proxy added in /etc/environment either
[18:06] <nturner> smoser, so it turns out all I had to do to turn my AMI-compatible raw image into one that MaaS can deploy and boot was to create a shell script that just exits with success and put it in the image as  /curtin/curtin-hooks.
[18:07] <nturner> (and tar up the img file)
[18:08] <nturner> Of course, while it now boots, cloud-config does not appear to be finding a maas data source (it claims to be looking).
[18:08] <nturner> Anyone know if there is any special cloud-init configuration (or minimum version) needed for it to integrate with maas?
[18:09] <nturner> I'm using the version currently in CentOS (0.7.5-10.el6.centos.2)
[18:10] <smoser> nturner, well, that is what your /curtin/curtin-hooks would do
[18:10] <smoser> it is executed and can then seed the configuration of this instance into cloud-init in the installed system.
[18:14] <nturner> Do you mean something like write a new cloud.cfg to tell it where the maas controller is?
[18:16] <nturner> Does MaaS not provide some kind of user-data API (like EC2) where the data returned depends on the machine making the request?
[18:16] <mup> Bug #1597460 opened: MAAS 1.9 should only download filetypes from a SimpleStream is can process <MAAS:Triaged by ltrager> <https://launchpad.net/bugs/1597460>
[18:28] <sjl> are there any other docs that talk about advanced maas networking like this blog: https://insights.ubuntu.com/2016/01/31/nodes-networking-deploying-openstack-on-maas-1-9-with-juju/
[18:29] <nturner> OK, I see from DataSourceMAAS.py that it will read data files (in /var/lib/cloud/seed/maas?) if they exist, but also expects to have a metadata_url from which to fetch metadata. ..
[18:29] <sjl> in particular sample api client calls that do the same thing?
[18:29] <nturner> Does this metadata_url need to be manually configured?
[18:42] <nturner> OK, I see /etc/cloud/cloud.cfg.d/90_dpkg_maas.cfg does exactly this on a 'normally' installed Ubuntu guest... getting closer...
[20:05] <mup> Bug #1597498 opened: Failure to deploy due to iSCSI errors with daily images <MAAS:New> <https://launchpad.net/bugs/1597498>
[20:05] <f1gjam> hey guys how can i see why i cant access the landscape web page?
[20:05] <f1gjam> i can ping the box
[20:05] <f1gjam> even telnet to prt 80 and 443
[20:05] <f1gjam> but when trying to open in a browser it just hangs
[20:06] <f1gjam> ok i sovled that problem :)
[20:23] <bbaqar> hey guys .. is there any way to connect a bridge to a VLAN interface i have created using maas? i.e. bond0.120 -> br-mgmt
[20:55] <pacavaca_> Is there a way for user to Acquire & Power On the node without re-imaging?
[21:01] <jhegge> pacavaca_: I still haven't figured out what the Acquire state is for but with the API I'd guess you can power on any commissioned node (with power type set at least)
[21:04] <pacavaca_> jhegge: Acquired stated means one more thing I think: machine has an owner associated with it, which is important for the use case I'm trying to implement. Also you can't really power-on the machine even through cli until it's "Allocated"
[21:07] <nacc> hey folks, was just cleaning up some bugs and ran across: LP: #1321885. AIUI, it was fixed in MAAS and the other marked-as-affected packages are actually false and can either be deleted or maked as invalid?
[21:12] <jhegge> pacavaca_: Allocated sets an owner, too, so Acquire is change owner to my user. I was just going to check something but all my MAAS VMs just tanked VMWare...
[21:13] <pacavaca_> I think "Allocate" is what's called "Acquire" in UI
[21:15] <pacavaca_> but simply calling "power-on" still triggers the re-imaging process
[21:19] <jhegge> pacavaca_: Okay, that's confused me, I've been using the API lately, allocating.  Now, when I allocate with API, I didn't see a re-imaging, just a change from Ready to Allocated.  I've not used power-on separately (yet), just straight to deploy.
[21:20] <jhegge> pacavaca_: I was just thinking though that power-on w/o imaging and nothing installed could result in the machine booting the existing local disk.  MAAS would sort let it get away then.
[21:21] <pacavaca_> jhegge: I thought so too, but that's not what's happening. I'm trying a different flow right now: allocate -> mark broken -> power on -> mark fixed. Let's see whether it'll still boot into new image or not.
[21:30] <nturner> woohoo! success!
[21:31] <nturner> The process is pretty straightforward once I understood it. Essentially, all my custom curtin hook had to do was grab the resource specified on the kernel command line and stick it into a file in /etc/cloud/cloud.cfg.d.
[21:33] <nturner> So simple that one wonders if cloud-init should just check /proc/cmdline for a cloud-config-url itself...
[21:33] <nturner> (Maybe newer versions do?)
[21:34] <nturner> Anyway, thanks smoser for the pointers (and you know, all your work on this slick system).
[22:23] <mup> Bug #1597541 opened: cannot configure node networkings with multiple gateways <MAAS:Triaged> <https://launchpad.net/bugs/1597541>
[22:52] <pacavaca_> What's the process of forking a project on launchpad? Or, in other words, how can I have my own version of MAAS with some small changes (which may not be welcomed in the main repo, but I still need them)? Is it possible to fork -> make the changes -> get custom .deb packages installable from ppa in rather easy way?