[17:40] <thebozz> Hi guys, we're having trouble deploying Openstack over MAAS using openstack-install. We're using this tutorial: http://www.ubuntu.com/download/cloud/install-ubuntu-openstack . We're at step 4, and we're getting this output: http://pastebin.com/Byaxct7c
[18:58] <X-Rob> blake_r: since I'm writing script for you, is there anythign else you'd like the HDD detection stuff to do? 8)
[18:58] <X-Rob> ouput in JSON or something?
[18:59] <blake_r> X-Rob: I already have a script that will perform what I need
[18:59] <blake_r> X-Rob: http://paste.ubuntu.com/9531708/
[18:59] <X-Rob> blake_r: and you're handinging multi-level block devices? like the /dev/cciss/c0d0 ones?
[19:00] <blake_r> X-Rob: can you give that a try to see if that pulls the required data?
[19:00] <X-Rob> ooh, lsblk
[19:00] <X-Rob> that works too
[19:01] <blake_r> X-Rob: can you check that the information it pulls looks correct, and that the path is correct for that type of device
[19:01] <X-Rob> blake_r: yeah, trying now
[19:03] <X-Rob> device node not found from udevadm
[19:03] <X-Rob> lets see what it wants
[19:03] <blake_r> thebozz: also give #ubuntu-server a try as well, they might be able to help you more with the cloud installer as this channel is only for MAAS
[19:03] <thebozz> blake_r: thanks, I'll try there too.
[19:03] <X-Rob> blake_r: also, seriously, you guys need an option 'ENABLE PROXY FOR DEPLOYED CLIENTS'
[19:04] <X-Rob> I ended up rebuilding my root-tgz to add it to /etc/bash.bashrc
[19:04] <X-Rob> but I digress
[19:04] <blake_r> X-Rob: if you set the http_proxy on the settings page, the deployed nodes will use it
[19:04] <X-Rob> blake_r: wat. Really? Holy shit. Anyway, lemme do this disk stuff first
[19:04] <blake_r> X-Rob: haha.
[19:04] <blake_r> X-Rob: really
[19:05] <X-Rob> https://www.irccloud.com/pastebin/QHjV316V
[19:05] <X-Rob> blake_r: so you need to replace any !'s with /'s in the device before you run udevadm
[19:06] <X-Rob> this is the problem with these stupid RAID drivers.
[19:06] <blake_r> X-Rob: udevadm info -q all -n c0d0
[19:06] <blake_r> X-Rob: doesn;t work?
[19:07] <X-Rob> https://www.irccloud.com/pastebin/k50bZxcY
[19:07] <blake_r> ah I see
[19:07] <X-Rob> No, it tries to use cciss!c0d0
[19:07] <X-Rob> which is what is reported by lsblk
[19:07] <blake_r> X-Rob: udevadm info -q all -n cciss/c0d0
[19:07] <blake_r> X-Rob: does that work without the "/dev"
[19:07] <X-Rob> blake_r: yes
[19:08] <X-Rob> sorry, force of habit me typing /dev
[19:09] <blake_r> X-Rob: can you give this one a try to see if this fixes the issue
[19:09] <blake_r> X-Rob: http://paste.ubuntu.com/9531799/
[19:10] <X-Rob> https://www.irccloud.com/pastebin/kNfKnHRR
[19:11] <X-Rob> that looks prefect to me
[19:11] <X-Rob> perfect
[19:11] <blake_r> X-Rob: what do you think about fix the name as well
[19:11] <blake_r> X-Rob: should it stay with the "!" or "/"
[19:11] <X-Rob> blake_r: no, the name is correct, the sysdev all uses !
[19:11] <blake_r> X-Rob: okay
[19:11] <blake_r> X-Rob: thanks for helping me out
[19:12] <X-Rob> no probs
[19:12] <X-Rob> the one other thing you may want to do is explicitly EXCLUDE the virtual disk that's being used to comission the machine
[19:12] <blake_r> X-Rob: ah, true
[19:13] <X-Rob> there was a bug about that one that I found too
[19:14] <X-Rob> https://www.irccloud.com/pastebin/GWAF2M0H
[19:14] <X-Rob> I'm guessing that 'VIRTUAL-DISK' as a string and a size less than 5MB would be a good 'this is the installer disk, don't use me' checkj
[19:15] <blake_r> X-Rob: should be able to check using iscsi commands as well
[19:16] <X-Rob> Nod.
[19:18] <X-Rob> And now, when you've finished, you can go and lodge bugs against landscape, as that's using a lshw parser to determine disk sizes and types, too.
[19:18] <X-Rob> That was when I threw my hands up in the air and gave up
[19:19] <X-Rob> I would be going as far as removing any nodes with disk attributes from the lshw output, to catch anyone else who's trying to use it
[19:19] <X-Rob> but that's just me, and I'm a bastard.
[19:20] <blake_r> Haha.
[19:20] <blake_r> Landscape will need to be updated to use this information
[19:21] <X-Rob> OK, so, two questions. 1: I'm pretty sure the proxy settings don't actually get passed onto the clients. The field says " This will also be passed onto provisioned nodes instead of the default proxy (the region controller proxy)."
[19:21] <X-Rob> Their stuff wasn't getting proxied, when I was deploying them.
[19:21] <blake_r> What version of MAAS?
[19:21] <X-Rob> 2: How do you run a script after a machine is provisioned?
[19:22] <blake_r> 1.7?
[19:22] <X-Rob> yeah
[19:22] <X-Rob> there doesn't seem to  be an easy way to tell the version from the GUI
[19:22] <blake_r> It should be using the proxy, as we run are machines in the CI through the proxy
[19:22] <blake_r> X-Rob: no there is not an easy way in the GUI
[19:23] <X-Rob> blake_r: This is just me, from experience, saying that putting it in the GUI is a good idea.
[19:23] <X-Rob> I'm one of the devs of FreePBX
[19:23] <blake_r> X-Rob: if you want to run a script after it is provisioned you need to use the maas command line
[19:23] <blake_r> X-Rob: agreed it should be terhe
[19:24] <X-Rob> And having it easily visible to end users makes our life a lot easier
[19:24] <X-Rob> blake_r: so what command line? I really, honestly, went crawling through the documentation looking for this
[19:24] <blake_r> X-Rob: maas login admin http://localhost/MAAS $apikey
[19:27] <blake_r> X-Rob: maas admin node start $system_id user_data=$(base64 < test.sh)
[19:27] <X-Rob> ahha
[19:27] <X-Rob> so there's no 'Run this script every time a machine is started' option?
[19:28] <X-Rob> As a global setting
[19:28] <blake_r> X-Rob: no as MAAS is designed to be similar to a cloud, so any user can request a machine and set a script
[19:28] <blake_r> X-Rob: you can upload a commissioning script that will run when you commission the node
[19:29] <X-Rob> yeah, but that doesn't help with me wanting to run a script on EVERY machine after it's started
[19:29] <X-Rob> This is probably a feature request.
[19:30] <blake_r> Yeah if you need that type of feature please make a bug, as we currently dont support that
[19:30] <blake_r> Actually we do
[19:30] <blake_r> Sorry but its not that simple
[19:30] <X-Rob> This came about because I wanted to add 'export http_proxy=http://172.16.0.1:3128' to /etc/bash.bashrc
[19:30] <X-Rob> of every machine
[19:31] <blake_r> You can modify the /etc/maas/preseeds/curtin_userdata
[19:31] <blake_r> Look at the late_commands you can have a command run at the end of the installation
[19:32] <X-Rob> I found that, but was unsure of the syntax.
[19:34] <X-Rob> would it just be '  add_proxy: sh -c "/bin/echo 'http_proxy=http://172.16.0.1:3132 >> /etc/bash.bashrc''
[19:35] <X-Rob> ?
[19:35] <blake_r> no
[19:35] <blake_r> http://paste.ubuntu.com/9532088/
[19:35] <blake_r> you need the "curtin in-target --" so its placed into the installed system
[19:35] <X-Rob> aaah
[19:35] <X-Rob> blake_r: is there somewhere I can document this?
[19:37] <blake_r> X-Rob: https://bugs.launchpad.net/curtin/+bug/1351085
[19:37] <blake_r> X-Rob: we know its something that needs to be improved
[19:38] <X-Rob> I was hoping for a git repo so I could acutally write it and do a pull request
[19:38] <blake_r> X-Rob: you can do a MP on the curtin project but it uses "bzr"
[19:38] <X-Rob> Which I've never used
[19:39] <X-Rob> I'd just got to http://maas.ubuntu.com/docs/hacking.html