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