[03:12] <arun__> #roaksoax will you able to share one sample config file for rackd.conf, it will be very helpfull
=== Beret- is now known as Beret
=== frankban|afk is now known as frankban
[09:59] <tosaraja> Is there a reason why power_parameters_power_address can't be read from the CLI? Or is it just me now knowing how to read it?
=== frankban is now known as frankban|afk
[15:10] <mup> Bug #1751300 opened: [2.4] No way to enable dynamic worker creation <MAAS:Triaged> <https://launchpad.net/bugs/1751300>
[15:10] <roaksoax> tosaraja: maas admin machine power-parameters <machine_system_id>
=== frankban|afk is now known as frankban
=== frankban is now known as frankban|afk
=== zeestrat_ is now known as zeestrat
=== neith_ is now known as neith
=== zsmithnyc_ is now known as zsmithnyc
=== coreycb_ is now known as coreycb
[20:03] <utriple> hi I'm having an issue where maas doesn't pick up any storage device in my super micro box
[20:08] <utriple> https://drive.google.com/file/d/1zYRzNHj6m5sw8i0TOmXViSEaYKg44nSV/view
[20:13] <utriple> I had this issue a while ago and posted in here ~1 month back
[20:20] <utriple> this the testing hardware stage of doing a commision a server
[20:40] <utriple> let me find the command it was failing on
[21:29] <xygnal> roaksoax: in bug report you gave example command to generate 500 fake nodes, but it seems not all of the data needed to try it ourselves is there.     you also mention you do this after running 'make run', which is perhaps what we are missing.
[21:29] <xygnal> 1744765, actually it was mike :)
[21:29] <xygnal> mpontillo:
[21:30] <xygnal> can you help me to fill out the missing peice to do that?  a co-worker is trying to test that out.
[21:30] <xygnal> comment #7
[21:33] <mpontillo> xygnal: that comment was probably specific to the MAAS dev env; your coworker might want to read through https://github.com/maas/maas/blob/master/HACKING.rst
[21:41] <utriple> my bug report is on that google drive link if anyone is curious
[21:43] <xygnal> mpontillo: ty sir :)
[21:50] <mpontillo> xygnal: sure. keep in mind that you will need to develop on Xenial in order to work with MAAS 2.3 sources, and on Bionic to work with MAAS 2.4 sources
[21:50] <mpontillo> xygnal: so if you are working on 2.3 code on Xenial, that's fine, just remember to check out the 2.3 branch
[21:51] <xygnal> will we need to upgrade to bionic to be able to use 2.4 prod?
[21:53] <roaksoax> xygnal: yes
[21:53] <roaksoax> 2.4 wont be backported to xenial
[21:54] <xygnal> will that also be the migration to snaps? or is that not here yet
[22:29] <roaksoax> xygnal: we will continue to produce debs, at least for 2.4
[22:29] <roaksoax> xygnal: and we are evaluating making 2.4 available in xenial only as a snap
[22:30] <roaksoax> so lts users dont have to upgrade the underlying os
[22:30] <roaksoax> as snaps give that flexibility
[23:00] <utriple> nvm I figured it out