[00:00] <Dr{Who}> found it :( ok is this in the pg database or what?
[00:00] <bigjools> there's a whole page of network settings in ther
[00:00] <mwhudson> yeah, i'll be in pg
[00:00] <Dr{Who}> i sooooo prefer a file I can edit.
[00:00] <mwhudson> *it'll
[00:02] <bigjools> the web page has validation so you don't do something stupid
[00:04] <Dr{Who}> k. I found the bad ip chnaged it but its still off. rebooting
[00:04] <Dr{Who}> ya sorry i had been playing with 12.04 maas and it had 0 ui fields so I didnt even think to dig :(
[00:05] <Dr{Who}> nope still wrong :(
[00:09] <bigjools> it's supposed to be a url to the settings page
[00:09] <bigjools> there's some django magic going on, so.... sigh
[00:10] <mwhudson> django usually gets the host for urls it generates from the http host header
[00:10] <mwhudson> i think?
[00:12] <bigjools> Dr{Who}: it's coming from DEFAULT_MAAS_URL in the settings
[00:12] <bigjools> I thought dpkg-reconfigure sorted that out
[00:13] <Marlinc> How do I setup virsh on MAAS? What do I need to add to the power management settings. What would driver, address, username and power id be?
[00:14] <bigjools> driver = qemu:// address = qemu host, username is the qemu user, power id is the host name
[00:16] <Marlinc> Can I use qemu+ssh:// too as driver?
[00:16] <Marlinc> as driver too*
[00:16] <bigjools> yes
[00:17] <Marlinc> If I use qemu+ssh what ssh private key would be used?
[00:17] <Marlinc> What use connects to qemu and stuff
[00:18] <bigjools> look in the power template, you might need a custom one
[00:22] <Marlinc> How do you mean bigjools ?
[00:22] <bigjools> power is all done in the template scripts, if you want to set up an ssh key I expect you'll need to edit the template
[00:23] <bigjools> very little testing was done for virsh, it was a developer tool
[00:23] <bigjools> so it kinda works
[00:23] <bigjools> but nothing guaranteed
[00:24] <Marlinc> What would be the way that works out of the box the easiest you think?
[00:25] <bigjools> the testing was done with qemu running locally, so assume that works
[00:25] <Marlinc> Ah.. I'm running a separate machine
[00:27] <bigjools> then you might be able to set up remote qemu access
[00:28] <Marlinc> I'm search for that right now
[00:36] <roaksoax> mwhudson: here.. but just for a few
[00:36] <roaksoax> bigjools: howdy!
[00:36] <roaksoax> bigjools: are you feeling ok for a couple reviews?
[00:36] <mwhudson> roaksoax: bigjools dobbed you in as the person to talk to about deploying disk images with maas
[00:36] <bigjools> roaksoax: hey
[00:36] <mwhudson> (as opposed to running d-i)
[00:36] <bigjools> roaksoax: looking at one of yours right now :)
[00:37] <bigjools> he's talking about FPI
[00:37] <roaksoax> bigjools: cool! the other one is trunk-fpi.. take a look if that pleases your eyes bette,r and if it does I'll add the tests
[00:37] <roaksoax> mwhudson: yeah, so give me a sec
[00:40] <roaksoax> bigjools: so I stripped out the xinstall stuff from here, and should be clean enough to go in: https://code.launchpad.net/~andreserl/maas/trunk-fpi/+merge/152039
[00:40] <roaksoax> bigjools: note that I didn't add a preseed because it is basically a shell script
[00:40] <bigjools> roaksoax: ok will look in 5
[00:41] <roaksoax> bigjools: and we have instructions to get it enabled
[00:41] <roaksoax> bigjools: and no worries, take your time
[00:41] <roaksoax> i'm off for tonight so won't look at it till tomorrow
[00:41] <bigjools> roaksoax: get it enabled?
[00:42] <roaksoax> bigjools: i mean since we are not shipping the xinstall stuff and a preseed in the MP, we need the instructions to install using FPI
[00:42] <bigjools> ok
[00:44] <Dr{Who}> bigjools: is "settings" a text config file or a database table? i have looked at all the files in /etc/maas and that address does not exist.
[00:45] <bigjools> Dr{Who}: it's a Django text config file
[00:45] <roaksoax> bigjools: ok i'll probably be on and off but if you need anything I'll probably be around to take care of things
[00:45] <bigjools> roaksoax: ok
[00:45] <roaksoax> bigjools: thanks :)
[00:45] <roaksoax> mwhudson: so that's all that you should need
[00:47] <bigjools> Dr{Who}: dpkg-reconfigure maas-region-controller should update this setting, no?
[00:48] <Dr{Who}> nope.. did it 10 times
[00:48] <bigjools> roaksoax: ^ ?
[00:48] <Dr{Who}> that fixed most issues but this one url is still wrong on that page.
[00:48] <bigjools> grep for DEFAULT_MAAS_URL
[00:49] <Dr{Who}> i grepped the entire disk for that. found a few but fixed and rebooted still the same.
[00:50] <mwhudson> roaksoax: 'that' as in https://code.launchpad.net/~andreserl/maas/trunk-fpi/+merge/152039 ?
[00:51] <mwhudson> ah, i see what you mean
[00:51] <roaksoax> mwhudson: yeah wjats in the link + maas in raring
[00:52] <roaksoax> contains whats in that branch
[00:52] <mwhudson> ok
[00:52] <mwhudson> err, hang on
[00:52] <mwhudson> apt-get install maas in raring has this fpi stuff?
[00:53] <roaksoax> Dr{Who}: what url is wtong where
[00:53] <roaksoax> mwhudson: correct.. but you need to enable it by using the info on the link
[00:53] <mwhudson> ok
[00:53] <Dr{Who}> ok the settings page. Some cluster controllers are missing boot images. Either the import task has not been initiated (for each cluster, the task must be initiated by hand the first time), or the import task failed.
[00:53] <bigjools> roaksoax: it's one that gets generated via DEFAULT_MAAS_URL
[00:53] <mwhudson> roaksoax: i'm running on precise unf
[00:53] <bigjools> he changed his machines IP and is now saying the URL is wrong
[00:53] <Dr{Who}> the url on that line should take me to the page to click and start the download of isos.
[00:53] <mwhudson> i guess i can work on that
[00:53] <Dr{Who}> but it goes to the wrong ip.
[00:54] <Dr{Who}> I greeped the entire disk for 10.10.0.3 and only place it shows up is
[00:54] <Dr{Who}> Binary file /var/lib/postgresql/9.1/main/base/16385/17041 matches
[00:54] <Dr{Who}> Binary file /var/lib/postgresql/9.1/main/pg_xlog/000000010000000000000001 matches
[00:54] <bigjools> roaksoax: I thought dpkg-reconfigure changed DEFAULT_MASS_URL
[00:54] <roaksoax> mwhudson: we havent backport the fpi
[00:54] <roaksoax> bigjools: it should
[00:54] <bigjools> Dr{Who}: don't grep for the IP grep for DEFAULT_MAAS_URL
[00:55] <bigjools> roaksoax: he's saying it's not working
[00:55] <Dr{Who}> that shows up all over but every result shows the correct ip 10.10.0.210
[00:56] <Dr{Who}> although some pyc files have it
[00:56] <Dr{Who}> and they are bin's
[00:56] <roaksoax> ill take a look when i get back since im on my way out
[00:56] <roaksoax> Dr{Who}: restart apache2
[00:56] <Dr{Who}> ya rebooted 10 times too :(
[00:56]  * mwhudson lunches
[00:56] <roaksoax> if not pastebin logs and maas settings file and maas_cluster file
[00:57] <Dr{Who}> k.
[01:00] <Dr{Who}> what logs would help? i have maas_local_settings.py and maas_cluster.conf
[01:04] <bigjools> Dr{Who}: I think he meant the logs under /var/log/maas
[01:05]  * bigjools heads to lunch
[01:25] <Dr{Who}> http://pastebin.com/HXup5XPQ
[01:30] <Dr{Who}> http://pastebin.com/eUyXySSB updated this one has logs
[01:33] <Dr{Who}> because this button on the page for importing images does not seem to work I am running manually for now 'maas-import-pxe-files' hope that is the right command.
[01:35] <bigjools> Dr{Who}: what makes you think the button doesn't work?
[01:36] <Marlinc> It now works bigjools :')
[01:37] <Marlinc> Using this as 'address'  qemu+ssh://maas-qemu@192.168.1.21:2001/system?keyfile=/etc/maas/id_rsa
[01:37] <bigjools> great
[01:40] <Marlinc> Thanks for the template tip because of that tip I was able to figure this out
[01:40] <Marlinc> Lets hope it wont break :P
[01:54] <Dr{Who}> bigjools: hmm will i pushed it and did not see any processes that looked like they were downloading.
[01:54] <Dr{Who}> and I saw no network traffic.
[01:54] <bigjools> Dr{Who}: check in the celery.log to see if the job was received on the cluster
[01:54] <Dr{Who}> tcpdump is my friend.
[01:54] <bigjools> it should start a long running wget
[01:55] <Dr{Who}> i am running in from console but did just push the button wail tailing the /var/log/cleery-region.log and nothing showed up
[01:56] <mwhudson> roaksoax: have you thought about the fun fun fun combination of fpi and ARM at all?
[02:03] <Dr{Who}> well something is disconnected. The import finished but I still see the warning about needing to do it by hand.
[02:06] <bigjools> Dr{Who}: I am wondering if your cluster is configured to talk to the right region
[02:06] <bigjools> since you changed the IP and all
[02:21] <Dr{Who}> define region? again I only have 1 system "but" I am trying to make this MAAS box multihomed trusted IP is on a 10.10 MAAS pxe network is 172.16
[02:22] <bigjools> the region controller, ie the api/web
[02:22] <bigjools> and db
[02:22] <bigjools> clusters can run on the same box but they are logically separate
[02:22] <bigjools> if you changed the DEFAULT_MAAS_URL it's likely to have broken the cluster
[02:23] <bigjools> so try reconfiguring it
[02:23]  * bigjools has to go
[02:42] <Dr{Who}> what is the dhcp daemon name I should see in process list used by maas on 13.04
[10:06] <ehw> hey, guys, how do I de-allocate a node in the maas gui?  I just hit "start node", and now it seems to be permanently 'allocated to root'
[10:32] <rbasak> ehw: have you hit bug 997092 perhaps? Also look at the duplicates which have different explanations that might help.
[10:33] <rbasak> bug 1061869 in particular
[10:33] <bigjools> you have to use maas-cli
[10:34] <ehw> rbasak: looks like it; thanks
[10:39] <rbasak> bigjools: any chance of someone who knows how to do it documenting the exact workaround steps in the bug, please? It's a bit of a trap for someone experimenting with MAAS for the first time. It's not particularly useful but the button is quite enticing and looks like it should be pressed.
[10:39] <bigjools> rbasak: the missing thing is a "stop" button
[10:39] <rbasak> bigjools: yes, but I presume that writing a paragraph in the bug is easier than adding a "stop" button? :)
[10:40] <bigjools> rbasak: marginally :)
[14:13] <roaksoax> ehw: you have to do it from the CLI or maas shell
[14:17] <ehw> roaksoax: thanks, I feel betrayed by that big, candy-like "Start Node" button :-(
[14:17] <roaksoax> ehw: heh i feel the same thing :)
[14:18] <roaksoax> ehw: so if you do it from maas shell
[14:18] <roaksoax> from maasserver.models import Node
[14:18] <roaksoax> node = Node.objects.get(hostname='XYZ')
[14:18] <roaksoax> node.release()
[14:18] <roaksoax> that should do it
[14:19] <ehw> roaksoax: ok; that will de-allocate or delete from MAAS?
[14:19] <roaksoax> ehw: de-allocate
[14:22] <rbasak> roaksoax: thanks - I'll add that to the bug
[14:23] <roaksoax> :)
[15:08] <ehw> roaksoax: worked a treat, thanks o/
[15:08] <roaksoax> ehw: \o/!
[16:09] <AskUbuntu> How do I enable tftp on the second nic on the maas controller in 13.04? | http://askubuntu.com/q/289816
[16:09] <AskUbuntu> Can I use Juju/MAAS on VPSes? | http://askubuntu.com/q/290122
[17:46] <Dr{Who}> going to start all over. this time only one network interface then once its working I will add my trusted network interface see if that works.
[18:22] <roaksoax> Dr{Who}: ok so you are using single node maas? or multinode maas?
[18:30] <Dr{Who}> I want a multihomed maas box one interface my local office network the other the pxe boot dhcp etc network.
[18:30] <Dr{Who}> but that may be just too complex to start with. so I am going to just do it all with 1 interface and add a virtual router to access the maas box.
[18:37] <roaksoax> ok
[18:38] <Dr{Who}> just finished the fresh install of maas on 13.04 going to see what is next in the install process. Afaik I need to now install dhcp and dns. Yesterday on the last try I could not even find pxe daemon running so at that point I was done with that try
[18:46] <roaksoax> Dr{Who}: so you installed sudo apt-get install maas ? then maas-import-pxe-files ?
[18:46] <roaksoax> Dr{Who}: have you installed maas-dhcp too?
[18:46] <Dr{Who}> 1. i installed from cd then added maas-dns and maas-dhcp although I think dns was missing? i forget. then import pxe
[18:47] <Dr{Who}> usually when I will build a recipe to reproduce a build process in my wiki. But.. i have yet to have a solid build so I have only done some sparce notes on the steps.
[18:48] <roaksoax> Dr{Who}: the install from the cD does not install maas-dns nor maas-dhcp IIRC
[18:48] <roaksoax> Dr{Who}: so basically: 1. sudo apt-get install maas maas-dhcp maas-dns
[18:49] <roaksoax> 2. sudo maas-import-pxe-files
[18:49] <roaksoax> 3. Configure DNS/DHCP on the WebUI or on the CLI
[18:49] <roaksoax> the Tftp server listens to all interfaces
[18:49] <Dr{Who}> cool. will do just that. Just finishing up on the firwall/router setup.
[18:50] <Dr{Who}> iptables rules fun.. yay!
[19:41] <Dr{Who}> roaksoax: why would i do apt-get install maas? isnt that installed when I use 13.04 cd and install MAAS?
[19:42] <roaksoax> Dr{Who}: yeah
[19:47] <Dr{Who}> ok first i did apt-get update then install maas-dhcp and maas-dns. shoudl I reboot or continue presuming everything is now running? This run I am building my full procedure so everything will be recorded even a reboot.
[19:47] <Dr{Who}> afaik sudo maas createsuperuser needs to be run
[19:48] <roaksoax> Dr{Who}: yeah you need to run that too
[19:48] <roaksoax> so install maas-dns, maas-dhcp
[19:48] <roaksoax> then maas createsuperuser
[19:48] <Dr{Who}> any reason not to stick with root? i have been changing it from the default.
[19:48] <roaksoax> then maas-import-pxe-files
[19:49] <roaksoax> Dr{Who}: stick with root what?
[19:49] <Dr{Who}> createsuperuser
[19:49] <roaksoax> you can create the user you want
[19:50] <roaksoax> so if you wanna call it roo,t you can call it root
[19:50] <Dr{Who}> ok cool.
[19:50] <roaksoax> that's the maas user only sois different from system users
[19:50] <roaksoax> ok so once you've done all of the above
[19:50] <roaksoax> go to the WebUI
[19:50] <roaksoax> then clic on the settings Icon
[19:50] <Dr{Who}> importing now.
[19:51] <roaksoax> Under "Cluster Controller"
[19:51] <roaksoax> there would be something like "Cluster 931660ae-6624-46a7-a977-b2f9b04bb2bf"
[19:51] <roaksoax> and clic on the icon to edit the cluster
[19:52] <roaksoax> then edit DNS zone name with the name you want to use, change the default 'master' to other thing
[19:52] <roaksoax> then edit any "Unmanaged" interface
[19:52] <roaksoax> where is the place where you can configure to manage DNS/DHCP
[19:52] <roaksoax> and that should be all you need
[19:53] <Dr{Who}> yep. saw that. when should I create and upload my ssl keys?
[19:53] <roaksoax> Dr{Who}: ssh keys under the user>preferences add a new SSH Key
[19:53] <Dr{Who}> ya just not sure when its really needed I have been doing it early on.
[19:55] <roaksoax> Dr{Who}: you wont be able to deploy machines until you add the SSH key
[19:55] <roaksoax> so anytime before deploying is fine
[21:39] <Dr{Who}> ok so system starts up gets the boot image downloaded then it seems to get stuck connecting back to iscsi
[21:51] <Dr{Who}> I am getting an arp from it so its alive and on the same network segment.
[22:08] <Dr{Who}> http://imgur.com/50Bwz1S thats as far as it gets. Maybe a problem with the kernel and this hardware?
[22:10] <Dr{Who}> its an HP-DL360g5
[23:12] <Dr{Who}> looks like it may be a vlan problem with my switch.. ok just for future. is it possible to have this stage of the install use vlan tagging or setup the interfaces to use vlans?