[02:05] <mup> Bug #1671672 opened: Default routes on multiple networks (including public Internet) are not honoured <networking> <MAAS:New> <https://launchpad.net/bugs/1671672>
[09:08] <mup> Bug #1671672 changed: Default routes on multiple networks (including public Internet) are not honoured <networking> <MAAS:Invalid> <https://launchpad.net/bugs/1671672>
[09:14] <mup> Bug #1671672 opened: Default routes on multiple networks (including public Internet) are not honoured <networking> <MAAS:Invalid> <https://launchpad.net/bugs/1671672>
[09:17] <mup> Bug #1671672 changed: Default routes on multiple networks (including public Internet) are not honoured <networking> <MAAS:Invalid> <https://launchpad.net/bugs/1671672>
[09:17] <mup> Bug #1664698 opened: No documented way to set the MAC for a bridge or bond <maas> <MAAS:Triaged> <netplan:In Progress by cyphermox> <https://launchpad.net/bugs/1664698>
[09:17] <mup> Bug #1671453 opened: Some ifupdown/ifenslave parameters have no netplan equivalent <maas> <MAAS:Triaged> <netplan:New> <https://launchpad.net/bugs/1671453>
[09:30] <mup> Bug #1664698 changed: No documented way to set the MAC for a bridge or bond <maas> <MAAS:Triaged> <netplan:In Progress by cyphermox> <https://launchpad.net/bugs/1664698>
[09:30] <mup> Bug #1671453 changed: Some ifupdown/ifenslave parameters have no netplan equivalent <maas> <MAAS:Triaged> <netplan:New> <https://launchpad.net/bugs/1671453>
[09:39] <mup> Bug # opened: 1664698, 1664806, 1671453, 1671756
[09:48] <mup> Bug #1664844 opened: No distinction between link-up and link-down interfaces <maas> <MAAS:Triaged> <netplan:Incomplete by cyphermox> <https://launchpad.net/bugs/1664844>
[10:52] <kklimonda> I'm testing maas 2.2b2, and it seems to be losing network configuration for nodes, is this a know issue?
[10:56] <roaksoax> kklimonda: maybe something change in cloud-init/curtin
[10:56] <roaksoax> kklimonda: but no, we have been testing b3 for release right now
[10:56] <roaksoax> nothing of that sorts
[12:31] <cnf> so if MAAS assigned a wrong IP to a server, how can I change this?
[12:39] <cnf> it tries to assign a static ip to a machine, instead of a dynamic, and I don 't understand why
[12:40] <roaksoax> cnf: becuase you configured the interface that way
[12:40] <roaksoax> cnf: if your interface is configured to 'Auto Assign', maas will chose the IP
[12:41] <roaksoax> cnf: if you select 'Static', you can select the IP and will be statically confiured in e/n/i
[12:41] <cnf> i didn't, i let it auto discover
[12:41] <cnf> yeah, it's set to auto assign
[12:41] <cnf> and it's wanting to give it an ip NOT in the dynamic pool
[12:41] <roaksoax> cnf: if you select 'DHCP' the interface will be configured as 'dhcp' in e/n/i
[12:41] <roaksoax> cnf: that's correct
[12:41] <roaksoax> cnf: the dynamic pool is for a different purpose
[12:42] <roaksoax> cnf: so if you subnet is 10.10.10.0/24
[12:42] <roaksoax> cnf: and you define dynamic pool as  .10 - .100
[12:42] <roaksoax> cnf: and the free range is .101 to .245
[12:42] <roaksoax> cnf: maas will auto assign ips on the "free range"
[12:42] <roaksoax> and use the dyanmic pool for randomg stuff, like commissioning
[12:42] <roaksoax> or enlistment
[12:42] <roaksoax> or other devices that pxe boot from maas
[12:43] <cnf> i only have interfaces beiung pxe booted off
[12:43] <cnf> atm
[12:44] <cnf> i don't think i understand the difference between free and dynamic...
[12:45] <roaksoax> cnf: so for example, when you commission a machine, the machine PXE boots of the 'dynamic' range
[12:45] <roaksoax> cnf: once the machine is Ready , and you deploy it
[12:45] <roaksoax> cnf: maas auto-assigns an IP from the 'free' range, pxe boots the machine with the IP, and e/n/i results using that IP
[12:45] <cnf> what is e/n/i ?
[12:47] <roaksoax> cnf: /etc/network/interfaces
[12:47] <cnf> ah
[12:48] <cnf> so my other machines use the same IP as they pxe boot off
[12:48] <cnf> it doesn't change after that
[12:48] <cnf> is that not what is supposed to happen?
[13:24] <pmatulis> cnf, yes, if the node is set to 'DHCP'
[13:24] <cnf> pmatulis: i didn't set any node, i left them as discovered?
[13:26] <pmatulis> cnf, the node shows up as 'Deployed'?
[13:26] <pmatulis> in the web UI ('Nodes' page)
[13:27] <cnf> yes
[13:30] <pmatulis> cnf, when you click on that node what value shows up under the 'IP Address' column?
[13:31] <cnf> ok, so i have basically before my entire range locked as "dynamic"
[13:31] <cnf> so i think maas was just using the last IP it got in dhcp and reusing it?
[13:31] <cnf> i have a bunch of free ip's now
[13:31] <cnf> see how things change
[13:32] <pmatulis> ohh, you selected your entire subnet as 'dynamic'?
[13:32] <cnf> pretty much
[13:32] <pmatulis> interesting
[13:32] <cnf> i thought that was what it was for
[13:32] <cnf> and it worked, at first
[13:32] <cnf> so i didn't get this was a problem
[13:32] <pmatulis> cnf, curious, did you follow the docs at all?
[13:33] <pmatulis> maybe that can be made much clearer
[13:33] <cnf> i did, but i ran in a lot of problems, so i had to jump around a lot
[13:33] <cnf> there is no direct link between me and the MAAS setup, so i am jumping through a lot of ssh tunnels
[13:33] <pmatulis> cnf, i would love to get your overall feedback on the docs
[13:33] <cnf> that took me a while to get working
[13:33] <pmatulis> cnf, do you think you could put together some notes?
[13:34] <pmatulis> and then create a docs bug?
[13:34] <cnf> uhm, i think i have one open already
[13:34] <cnf> on the use of proxies
[13:34] <pmatulis> recently opened?
[13:34] <cnf> a week or so ago?
[13:34] <cnf> +-
[13:34] <pmatulis> in GitHub or Launchpad?
[13:35] <cnf> i think it was on github
[13:36] <cnf> the maas doc wasn't too bad, the juju docs on the other hand...
[13:36] <cnf> pmatulis: my biggest problem with maas was there are a lot of assumptions that are not communicated, and which are not true in my setup :P
[13:37] <pmatulis> cnf, i cannot locate your bug :(
[13:37] <cnf> hmm
[13:38] <cnf> what was the repo url again?
[13:38] <pmatulis> for the maas docs?
[13:38] <cnf> yeah
[13:38] <pmatulis> https://github.com/CanonicalLtd/maas-docs
[13:38] <cnf> hmm
[13:39] <pmatulis> or maybe
[13:39] <pmatulis> https://bugs.launchpad.net/maas
[13:39] <pmatulis> (for software bugs)
[13:40] <cnf> i can't remember where it was filed...
[13:40] <pmatulis> darn
[13:41] <pmatulis> cnf, if you want to add details to your experience with the docs you can put them here: https://github.com/CanonicalLtd/maas-docs/issues/new
[13:41] <cnf> k
[13:42] <cnf> well, i did totally miss i was supposed to keep a free range
[13:42] <cnf> i read the docs on static and dynamic, and then understood to have a dynamic range as large as possible
[13:45]  * cnf sighs
[13:45] <cnf> HP servers take so long to boot :P
[13:46] <cnf> so how large should your dynamic pool be?
[13:47] <pmatulis> it depends how many nodes you intend on having. and whether you will ever use 'DHCP' for deployed nodes
[13:48] <cnf> uhm, unknown... i'm evaluating maas/juju for deploying openstack
[13:48] <pmatulis> if not for the latter (DHCP), just remember that the addresses will only be used temporarily (enlistment and commissioning)
[13:48] <pmatulis> and them be available for re-use
[13:49] <cnf> right, so just enough to cover booting machines
[13:49] <pmatulis> yeah, booting machines until they get to the 'Ready' state
[13:50] <cnf> ah, if they boot from ready, they don't get one of those ip's either?
[13:50] <cnf> so it's only for on-boarding, basically?
[13:50] <pmatulis> unless you've set them to 'DHCP' like i said
[13:50] <cnf> right
[13:50] <pmatulis> right, on-boarding
[13:51] <cnf> ok
[13:53] <cnf> yeah, it might be nice to state that machine ip's should be free here https://docs.ubuntu.com/maas/2.1/en/intro-concepts
[13:53] <cnf> it is explained if you click through, it seems
[13:53] <cnf> i missed that
[13:55] <cnf> so can juju configure network settings on different interfaces separate from maas? or does maas need to be aware of it?
[13:59] <pmatulis> what sort of network settings?
[14:00] <cnf> so all my machines have a 2 x 10G LAG
[14:00] <cnf> which carries a bunch of tagged vlans
[14:00] <cnf> depending on what functionality gets deployed, you need one of those vlans to connect to things
[14:01] <cnf> but i don't want all machines to always have an IP in every vlan
[14:02] <cnf> maas is on a separate link (tried pxe booting on the LAG, but never got that working)
[14:21] <pmatulis> cnf, i'm not sure. i suggest asking in #juju
[14:21] <cnf> i did :P
[14:22] <cnf> but people only become active there when my workday is done
[14:45] <myra> hello, I want to know if there's anyway I could deploy a raw image that I made with MaaS
[14:46] <myra> I mean I made it with openstack and I want to deploy it with maas
[14:54] <mup> Bug #1671839 opened: ssh keys view needs improvement <MAAS:New> <https://launchpad.net/bugs/1671839>
[15:08] <pmatulis> cnf, mailing list?
[15:08] <cnf> hmm
[15:21] <mup> Bug #1671844 opened: [UI, 2.1.3] MAAS API key name not exposed in the UI. <MAAS:Triaged> <https://launchpad.net/bugs/1671844>
[18:06] <mup> Bug #1671891 opened: [2.2 beta3] Node failed to be deployed, because of the following error: {"gateway_link_ipv4": ["Static IP Address instance with id 248066 does not exist."]} <cdo-qa-blocker> <oil> <MAAS:New> <https://launchpad.net/bugs/1671891>
[18:33] <mup> Bug #1671897 opened: ui to browse combos of tags is inconsistent with juju's notion of combos of tags <ui> <uosci> <MAAS:New> <https://launchpad.net/bugs/1671897>
[19:35] <Guest67780> hello I created a raw image and I want to deploy it with maas, is there a command line or something to do so? because in the web interface I couldnt find anything.
[19:39] <stormmore> anyone seen kiko today?
[20:01] <stormmore> I really hate inconsistent failures :-/
[20:09] <Guest67780> I created a raw image and I want to deploy it with maas, is there a command line or something to do so? because in the web interface I couldnt find anything.
[21:13] <kukacz> kiko: some days ago I've reported failing PXE UEFI boot - stuck in Grub - on Dell servers
[21:15] <kukacz> kiko: just wanted to share that BIOS (for Dell R630 servers) update fixed that. NIC firmware (Intel X520) was latest already
[21:15] <kukacz> kiko: thanks for help!
[21:16] <stormmore> kiko, so far today I haven't been able to reproduce the problem I have been having. I am wondering if it is bandwidth related somehow
[21:16]  * stormmore is graham in case you didn't know
[21:55] <stormmore> OK maybe, just maybe my intermittent issue might be resolved and we will never know what it was :-/