[08:53] <mup> Bug #1600720 opened: Maas doesn't honor DNS settings for a subnet for DHCP <MAAS:New> <https://launchpad.net/bugs/1600720>
[13:38] <smoser> nturner, bah. in #cloud-init ping harlowja to get help or submit a merge proposal for 2.6 support. we do want to have that. sorry that it is broken.
[13:38] <smoser> nturner, but older cloud-inits *should* work with newer maas, as precise is still supported and it does not have the reporting stuff. not even sure if trusty does.
[16:11] <setuid> Where is 'maas-rack-controller', which provides 'maas-rack'? Doesn't seem to be in ANY repo or ppa.
[16:11] <setuid> I'm stuck on the install docs which require this step to get maas running
[16:12] <setuid> https://maas.ubuntu.com/docs/rack-configuration.html
[16:23] <roaksoax> setuid: nothing provides maas-rack
[16:23] <roaksoax> setuid: maas-rackd is a daemon
[16:23] <roaksoax> setuid: oh you mean the maas-rack binary
[16:23] <setuid> Right, the docs say to install maas-rack-controller, which does not exist
[16:23] <setuid> it provides the maas-rack binary to manage the rack
[16:24] <roaksoax> setuid: then you are not using 2.0
[16:24] <setuid> I feel like I'm going in circles
[16:24] <roaksoax> setuid: or xenial
[16:24] <setuid> Right, this is Trusty
[16:24] <setuid> Not going to Xenial until I know this works on Trusty
[16:24] <roaksoax> setuid: yeah, you are looking at trunk docs
[16:24] <roaksoax> setuid: https://maas.ubuntu.com/docs/rack-configuration.html
[16:24] <roaksoax> https://maas.ubuntu.com/docs2.0/rack-configuration.html
[16:24] <roaksoax> https://maas.ubuntu.com/docs1.9/rack-configuration.html -> doesn't exist
[16:24] <roaksoax> setuid: you wont be able to install MAAS 2.0 in trusty
[16:26] <setuid> Let me back up... I've been trying for a solid 4 weeks (since 6/6) to get Openstack installed, ANY version of Openstack (tried icehouse, jujo, kilo, liberty and mitaka) on ANY version of Ubuntu, using ANY version of these tools (openstack-install, conjure-up, juju, etc.)
[16:26] <setuid> So far, the entire scope of that matrix, has not resulted in a single successful install
[16:26] <setuid> I've tried on 3 baremetal Intel boxes, VirtualBox, VMware Workstation, ESXi and Fusion on Mac
[16:26] <roaksoax> setuid: if you are using trusty, you want MAAS 1.9 , with juju 1.25.X
[16:27] <setuid> Yep, it's whatever comes with the default repos + supported ppas
[16:27] <roaksoax> setuid: and if you are using autopilot, you /need/ MAAS 1.9/juju 1.25.x
[16:27] <setuid> the docs are wrong, the packages have missing components, it's a mess
[16:27] <setuid> I just found this, which I'm following now: http://dinosaursareforever.blogspot.com/2014/06/manually-deploying-openstack-with.html
[16:28] <roaksoax> setuid: right, so in MAAS, at least, you are looking at the wrong place
[16:28] <roaksoax> setuid: if you are in MAAS 1.9, you need to look at https://maas.ubuntu.com/docs1.9/
[16:29] <roaksoax> setuid: you may find some of the docs being out-of-date (we are fixing that), but the important stuff is there
[16:29] <roaksoax> setuid: also, you shouldn't need to "install-shared-secret"
[16:30] <roaksoax> setuid: if you are using a single MAAS, if you are using a MAAS with multiple rack/cluster controller, then you will need it
[16:32] <setuid> I have a single baremetal box upon which I need to install a working openstack, under 14.04. This machine also dual-boots 16.04, where I'll do the version of opensstack there also
[16:32] <setuid> So, so, SOOOO many gaps in almost every single howto and doc out there, it's really discouraging
[16:32] <setuid> You get to step 17, then things go off the rails and you're screwed
[16:36] <setuid> Stuck at creating the maas_internet host, the first maas server... because it doesn't tell you how or where to boot the machine, so DOA right there.
[16:36] <setuid> *sigh*
[16:41] <cafaroo> Hi, I'm using maas 1.9.3 for deployment of a HP C7000 enclosure. Is it possible to add the c7000 as a chassis or is chassis something else? (Im having errors with ipmi on the blades since they reset all users everytime i shut the chassis down)
[16:45]  * setuid facepalms
[16:58] <roaksoax> setuid: fwiw: http://maas.io/get-started
[16:58] <setuid> btdt
[16:58] <setuid> that's not relevant to 14.04
[16:59] <setuid> http://maas.ubuntu.com/docs1.9/
[16:59] <setuid> that's going to get me somewhat close
[16:59] <roaksoax> cafaroo: a chassis is like a "moonshot"
[16:59] <roaksoax> setuid: http://maas.io/get-started -> 14.04
[16:59] <setuid> but there's 19 different ways to install this and none of them are consistently documented, nor do they work... I've done about 150 separate installs/teardowns in the last 4 weeks on this
[16:59] <roaksoax> setuid: did you see http://maas.io/get-started ?
[17:00] <roaksoax> setuid: i wonder why are you trying to install a shared secret in a rack controller when you are installing MAAS 1.9 in trusty, that doesn't have rack controllers ?
[17:00] <roaksoax> for example
[17:00] <roaksoax> setuid: 1st. sudo apt-get install maas
[17:00] <setuid> I'm not even remotely close to the shared secret part of anything
[17:00] <roaksoax> that will pull maas-region-controller and maas-cluster-controller (in trusty, using 1.9 PPA)
[17:00] <roaksoax> setuid: exactly, cause you dont even need it
[17:00] <setuid> Let me tear this env down and start clean, again.
[17:01] <setuid> I should script this, I've done it a hundred times now... apt-get remove --purge, apt-get autoremove, dpkg -P, etc. lather. rinse. repeat.
[17:01] <roaksoax> setuid: also what you were foloowing says: "If you install your first Rack Controller on the same system as the Region Controller, as is the case when you install the full “maas” ubuntu package, it will be automatically accepted by default (but not yet configured, see below). Any other Rack Controllers you set up will show up automatically after they have been manually added to MAAS."
[17:02] <roaksoax> if you read, "Any *other* Rack Controllers you set up..."
[17:02] <setuid> At this point, getting a working maas where I can get to the web interface would be a big leap
[17:02] <roaksoax> setuid: so, on 14.04: sudo add-apt-repository ppa:maas/stable
[17:02] <roaksoax> setuid: sudo apt-get update
[17:02] <roaksoax> sudo apt-get install maas
[17:02] <roaksoax> sudo maas-region-admin createadmin
[17:02] <setuid> I've had the web interface working -once-, but couldn't provision machines, because the 'Minimum kernel' would not accept any of the choices proided
[17:02] <roaksoax> setuid: http://localhost:5240/MAAS
[17:03] <setuid> yep, that bit is wrong
[17:03] <setuid> nothing is ever listening on 5420, that's old doc
[17:03] <setuid> s
[17:03] <setuid> it's at https://public-ip/MAAS now
[17:03] <roaksoax> setuid: 5240 is the default port
[17:03] <roaksoax> setuid: /MAAS is apache *forwarding* to :5240
[17:03] <setuid> Not with the maas that is in the stable ppa which installs on trusty, nope
[17:03] <setuid> nothing is listening on 5420, so not sure how a web request would get a response on that port
[17:04] <setuid> localhost or any other interface
[17:04] <roaksoax> setuid: /maas-http.conf:    ProxyPass /MAAS/ws "ws://localhost:5240/MAAS/ws" disablereuse=on
[17:04] <setuid> give me a moment, tearing the env down and reinstalling from scratch
[17:04] <roaksoax> maas-http.conf:    ProxyPass /MAAS/ws "ws://localhost:5240/MAAS/ws" disablereuse=on
[17:04] <roaksoax> maas-http.conf:    ProxyPass /MAAS/ http://localhost:5240/MAAS/
[17:04] <roaksoax> maas-http.conf:    ProxyPass /MAAS http://localhost:5240/MAAS/
[17:08] <cafaroo> roaksoax: okey so i guess it will not work with c7000 then. Going to find another solution. Thanks!
[17:09] <roaksoax> cafaroo: i'm guessing that each blade on the c7000 should be seen as individual machines no ?
[17:09] <kiko> cafaroo, what roaksoax said -- it should work
[17:09] <kiko> cafaroo, you just can't use the "add chassis" functionality if we don't support it natively
[17:10] <kiko> but the individual nodes can just be PXE booted individually and that's it
[17:11] <cafaroo> Kiko: Thank you, i know, it works induvidually now but when I power down the chassis all the nodes get their user information wiped...
[17:12] <cafaroo> So i thought maybe chassis could work since the enclousure always has the same username/pw
[17:13] <cafaroo> But when i'm in production hopefully the chassis will never power down :)
[17:13] <kiko> cafaroo, does the enclosure username/password work to access the blades via IPMI?
[17:13] <kiko> cafaroo, if it does, you can use that account in the MAAS settings instead
[17:13] <kiko> otherwise, the chassis normally lets you create users
[17:15] <cafaroo> I'll try it with the default OA password, that will probably work!
[17:19] <setuid> roaksoax, configured the two interfaces (had an error that the internal one conflicted with the public one, deleted both, reconfigured exactly the same, now no error), now importing images. This is as far as I've gone before, so let's see what happens next.
[17:22] <cafaroo> kiko: Nope, OA does not pass its default username/password to the blades (perhaps a setting).
[17:23] <Karan> Does Maas need client machine need a harddrive to boot?
[17:24] <Karan> Does MAAS Client machine need a HDD to boot and run?
[19:11] <cafaroo> Kiko: So finally I got the ilo passwords for each induvidual blade (48x) and im putting them in maas :)..
[19:22] <cafaroo> Im getting a PXE error when I am relasing a node. It's when I have "Erase nodes' disks prior to releasing." enabled. When node pxe boots I get an error "Could not find kernel image: ubuntu/amd64/hwe-x/trusty/no-such-image/boot-kernel". Is this a bug or my setup?
[19:59] <setuid> If I'm adding new nodes through MAAS, on a host that has ZERO nodes running, how will I know the MAC address before the node is created by MAAS and booted?
[20:00] <setuid> Chicken and egg problem... "Provide us with the MAC address of a machine we haven't built and deployed yet."
[20:37] <roaksoax> setuid: did you try to "auto-enlist" them ?
[20:37] <roaksoax> setuid: typically, in most organizations (if not all) administrators already have a list of servers with mac address and relevant stuf
[20:37] <roaksoax> setuid: anyway, just let them pxe boot from MAAS and they will automatically appear there