/srv/irclogs.ubuntu.com/2018/05/30/#maas.txt

=== hazmat_ is now known as hazmat
=== tai271828_ is now known as tai271828
=== setuid_ is now known as setuid
=== mwhudson is now known as Guest96057
=== Guest96057 is now known as mwhudson
=== frankban|afk is now known as frankban
mupBug #1774135 opened: [2.5, snap] dhcpd wasn't started after enabling dhcp on a subnet <MAAS:New> <https://launchpad.net/bugs/1774135>07:39
mupBug #1774135 changed: [2.5, snap] dhcpd wasn't started after enabling dhcp on a subnet <MAAS:New> <https://launchpad.net/bugs/1774135>07:48
mupBug #1774135 opened: [2.5, snap] dhcpd wasn't started after enabling dhcp on a subnet <MAAS:New> <https://launchpad.net/bugs/1774135>07:51
=== popey_ is now known as popey
bjarneHi, I saw that 2.4.0-6981-g011e51b7a-0ubuntu1~18.04.1 was availeble in next repo, but  seems  like 2.4.0~rc2 isn't releaset yet. Which branch is that build based on?11:45
=== narinder` is now known as narindergupta
roaksoaxbjarne: ? 2.4.0~rc2 -> 2.4.013:01
roaksoaxbjarne: its the same , its just renamed14:03
mupBug #1774206 opened: MAAS denies recursive DNS queries from subnets it doesn't know about <cdo-qa> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1774206>14:49
mupBug #1774186 opened: curtin does not recognize / partition created in MAAS <cdo-qa> <cdo-qa-blocker> <cpe-onsite> <foundations-engine> <curtin:Triaged> <MAAS:New> <https://launchpad.net/bugs/1774186>16:04
=== frankban is now known as frankban|afk
xygnalis 2.4.0 final out?18:21
=== ferdz61 is now known as f3rdy
xygnalAbility to increase the number of regiond workers19:31
xygnalFollowing the improved way MAAS daemons are run, further internal changes have been made to allow the number of regiond workers to be increased automatically. This allows MAAS to scale to handle an increased number of internal operations in larger environments.19:31
xygnaldoes this affect more than UI?19:31
roaksoaxxygnal: yes19:45
roaksoaxxygnal: /win 319:46
roaksoaxerr19:46
roaksoaxxygnal: it allows for more workers communicate with the DB, but would require to increase the amximum number of db connections postgresql accepts19:47
roaksoaxxygnal: but at the same, your issues with the UI should be considerably improved in 2.419:47
roaksoaxxygnal: without increasing the number of workers19:48
xygnalyes. impressive release notes sir.20:15
xygnallooking forward to a lot20:15
mupBug #1774266 opened: Validate boot images are available for applicable rack controllers only <MAAS:Triaged> <https://launchpad.net/bugs/1774266>20:16
bdxconcerning 3rd party drivers21:29
bdxhere is my commissioning script https://paste.ubuntu.com/p/V7RZBRRqtq/21:29
bdxI've tried a few different paths, but can't get maas to pick up the mellanox interfaces in commissioning21:30
bdxeven though the driver install succeeds, and I can ssh into the node following commissioning and see the physical interfaces are there21:31
bdxno matter what I do, I can't seem to get maas to pick up the mellanox interface in commissioning21:31
bdxany ideas?21:31
bdxbug?21:31
roaksoaxbjarne: whats the name of your script ?21:32
roaksoaxerr21:32
roaksoaxbdx: ^^ what's the name of your script ?21:32
bdx00-install-xenial-mlnx-drivers21:32
bdxthe name in the metadata21:33
roaksoaxbdx: maas should be grabbing the interface information from 'ip addr'21:35
roaksoaxbdx: so that could mean there's no 'ip addr' info for your interface ?21:36
bdxroaksoax: the node isn't powered on anymore, but a few moments ago this is what `ip a` showed https://paste.ubuntu.com/p/6CjG9MKWPq/21:37
bdxenp130s0 and enp130s0d121:37
bdx^ the mellanox21:37
roaksoaxbdx: check the output in  99-maas-03-network-interfaces21:38
bdxroaksoax: it shows the mellanox nic21:41
bdxhttps://imgur.com/a/c3XoTcY21:42
roaksoaxbdx: and it is not shown on the interfaces tab ?21:42
bdxcorrect21:42
roaksoaxbdx: and when you commissioning, are you selecting 'Retain network configuration' ?21:43
bdxI have been, let me run another commissioning with that checked just for an isolated test21:44
bdxjesus21:47
bdxthey just showed up in the interfaces tab21:47
bdxahh21:47
bdxI think I know what changed21:47
bdxpreviously, I wasn't adding the metadata tag to recommission21:48
roaksoaxah gotcha21:48
bdxas well as checking "retain network"21:48
bdxroaksoax: thanks21:48
bdxroaksoax: now I have the drivers being installed during commissioning, and the interfaces recognized21:49
bdxis my next step to get the drivers into the image at deploy time to build a deb and add them to the drivers.yaml?21:49
roaksoaxbdx: i would probably recommend you install them the same way you are doing in the ephemeral enviromment21:53
roaksoaxbdx: via curtin preseeding21:53
roaksoaxbdx: i have  quesiton though, are these drivers not available in Ubuntu at all ?21:53
bdxroaksoax: correct21:53
roaksoaxso i guess mellanox has not upstreamed these drivers into the linux kernel?21:54
bdxalso correct21:54
roaksoaxok gotcha21:54
bdxhttp://www.mellanox.com/related-docs/prod_software/Mellanox_EN_for_Linux_User_Manual_v4_3.pdf - chapter 2.9 "Installing using apt-get"21:55
bdxthey suggest building a deb with the included packaging and serving them up from a local file repo21:55
bdxI have been trying to build the deb and upload it to launchpad under my own ppa21:56
bdx^ then I could just create an entry in drivers yaml21:56
bdxthe preseed may be easier for sure21:56
bdxbecause the packaging doesn't build successfully on launchpad21:56
roaksoaxright21:56
bdxI've been trying to fix/hack it21:57
roaksoaxyeah the preseed may be straightforward since you already have such script21:57
roaksoaxyou could just run that script in a late_command21:57
roaksoaxinside the installed target21:57
bdxtotally21:57
bdxI've done this before back in 1.7 or something ..... are the preseeds under SNAP_COMMON now I take it?21:58
bdxI can setup a new apt installed maas22:03
bdxI want to deploy all my new things under maas 2.4 anyway22:03
roaksoaxprobably not, since we are still working on getting the snap done for 2.4, we haven't made changes wrt to the snap in 2.322:03
bdxok22:04
bdxI may want to use maas from apt is what you are saying22:04
bdxgot it22:04
roaksoaxindeed22:04
bdxok22:04
roaksoaxbdx: you could then migrate to a 2.4 snap, once ready, pointing it to your current DB22:04
bdxroaksoax: totally22:05
bdxwell, I have the two entirely decoupled22:05
bdxso that will probably be even easier22:06
bdxroaksoax: how do I migrate the db from 2.3.x -> 2.4 ?22:07
mupBug #1771885 opened: bionic: static maas missing search domain in systemd-resolve configuration <bionic> <network> <cloud-init:New> <juju:Fix Committed by ecjones> <juju 2.3:Fix Released by ecjones> <MAAS:New> <https://launchpad.net/bugs/1771885>22:29
roaksoaxbdx: i would suggest you backup your db22:38
roaksoaxbdx: once that's done, isntall maas from packages22:38
roaksoaxsudo service maas-regiond stop22:38
roaksoaxbdx: then configure /etc/maas/regiond.conf to point to where the 2.3 db is22:38
roaksoaxbdx: and then run: sudo maas-region dbupgrade22:39
roaksoaxbdx: then: sudo service maas-regiond restart22:39
roaksoaxbdx: you /may/ need to rm -rf /var/lib/maas/secret and let maas re-create a new one22:39
bdxok, awesome22:40
bdxroaksoax: my maas is currently deployed to a xenial box, and my postgresql is on another xenial box22:40
bdxroaksoax: is 2.4 compatible with xenial, or should I deploy a bionic host to install maas from apt on?22:41
roaksoaxbdx: you'd need bionic22:41
bdxthats what I thought22:41
roaksoaxbdx: i'll check what the status of the snap is tomorrow though, since we were dependent on core18 changes22:41
roaksoaxs/core18/base1822:41
bdxgreat, thanks for all of this22:43
roaksoaxnp!22:50

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!