=== racedo` is now known as racedo [14:15] Hello everyone [14:16] I just finished installing MAAS [14:16] I have a problem with the configuration of my nodes [14:16] is this the place to ask such questions? [14:16] :) === andreas__ is now known as ahasenack [14:50] i m having problem enlisting nodes when i m behind a proxy [14:51] i try to change /usr/share/maas/preseeds/generic so that i have "d-i mirror/http/proxy string http://http://my.proxy:8000/" [14:51] but when i enlist a node, it s console still show temporary failure resolving archive.ubuntu.com [14:52] did i do something wrong ? was i suppose to restart some service ? any hint as to what i may have missed ? [14:53] still, the node appears as declared. [14:57] racedo any idea ? ^ [15:11] still, i cannot bootstrap , i added the proxy def in the /usr/share/maas/preseeds/preseed_master file, but it does not seem to be used [15:16] lets try to set the proxy in enlist_userdata and re enlist the node then. [15:58] melmoth: yes [15:59] melmoth: enlistment doesn't use the normal preseeds, it uses enlist_userdata [15:59] enlisting worked, but now not the bootstraping. i m tryoing to add apt.conf manually in /var/lib/maas/ephemeral/precise/ephemeral/amd64/20121008/disk.img [16:00] melmoth: it is not bootstrapping because it is not accessing the ppa: [16:00] ? [16:00] no, i havent reach this stage yet. :) [16:00] that s what i want to try out, the workarond you mentionned last week [16:00] melmoth: there's no need to modify disk.img when you can modify the cloud init preseeds/user data to add the proxy [16:01] i try, i failed [16:01] melmoth: is this a customer? [16:01] no, its just me having nothing more urgent to play with [16:01] melmoth: ok, is this a lab i could access to? [16:01] yep, arion on boston. [16:02] hold on, just trying to bootstrap after my change in the image [16:03] melmoth: ok, butyou have to differentiate various things. 1. only enlisting and commissioning use the image 2. the installation process is done via normal installation (doesn';t use the image). [16:03] ah, then it ll failed.... [16:04] but i did put the porxy in the /usr/share/maas/preseeds/preseed_master [16:04] melmoth: preseed_master automatically uses the proxy in MAAS [16:05] i set apt_proxy: in /usr/share/maas/preseeds/enlist_userdata, and set the proxy in /usr/share/maas/preseeds/preseed_master [16:05] and in the image [16:09] melmoth: you don't need to modify preseed_master: http://paste.ubuntu.com/5625566/ [16:09] melmoth: http://paste.ubuntu.com/5625568/ [16:10] hmmmm, in enlist_userdata i did not put apt_proxy: http://{{server_host}}:8000/ but my proxy... [16:10] may be i should have just uncomment it without changing the server_hosr macro ? [16:10] melmoth: {{server_host}} refers to the address of the MAAS Region Controller [16:10] where the MAAS proxy is running (squid-deb-proxy) [16:11] ok... i ll try that out. from scratch again, just to be sure :) [16:11] i ll have more news by tomorrow. [16:11] thanks [16:11] melmoth: now you might find some situations on which it cannot import the gpg key for the PPA... that needs to be resolved differently and can't remember how is it that we did it [16:12] that s what i want to try out this week. [16:13] i bet i ll ask more help about it here in the near future.... [16:13] indeed === matsubara is now known as matsubara-lunch === matsubara-lunch is now known as matsubara [20:18] Hello. I'm trying to get MAAS up and running on Quantal to provision Quantal machines. I can't get the import pxe tool to download the quantal images but it doesn't by default and error if I add the config to the import-pxe config file [20:18] aberdine_: modify /etc/maas/import_pxe_files [20:19] aberdine_: and there would be something like #IMPORT_SQUASH_FS=0 remove the comment and try to import the images again [20:19] aberdine_: if it continues to fail, set that to 1 and that should be ir [20:19] be it [20:20] thanks roaksoax. It was failing at the squashfs import [20:20] it seems to be running now [20:24] Now I've just got to figure out why it things it's install the machine went it's done nothing [20:28] aberdine_: how so? [20:29] I do the first PXE boot, then accept it via the web interface. Reboot and boot of net and it keeps going with the enlist process [20:29] It never actually installs anything [20:31] aberdine_: so there's 3 steps in maas 1. enlistment. 2. commissioning 3. deployment (which leads to installation) [20:31] aberdine_: so you enlist a machine and it has a 'Declared' Status on the WebUI [20:31] aberdine_: you do "Accept & Commission" [20:31] yep, got that [20:31] and the second one [20:31] aberdine_: and it will accept the node, and it will commision [20:31] It's now saying 'ready' [20:32] aberdine_: ok so, how are you deploying it then? [20:32] via a PXE boot [20:32] aberdine_: right, but once 'Ready' you need to tell it to *deploy* via the WebUI, or via juju [20:32] i'd recommend juju [20:33] I don't see a deploy option [20:33] I have a greyed out start [20:33] I need to play with it a bit more I think [20:34] aberdine_: what meesage is shown when you put the mouse on top? I think you haven't added the SSH key for the MAAS user [20:34] that is deploying the system [20:34] you need to specify one [20:34] added the SSH key to…? [20:35] aberdine_: on the right corner, clic on the user [20:35] then go to Settings [20:35] err [20:36] PReferences [20:36] that needs my ssh public key in? [20:36] then 'Add SSH Key', which is your public key [20:36] what's that for? Post install config? [20:36] aberdine_: yes it needs your public ssh key, otherwise you won;'t be able to log into the server [20:37] ah :) [20:39] So, I've enlisted and commissioned the machine. It's on its second boot now [20:39] it has a hostname this time [20:39] hmm [20:39] this looks promising [20:39] it's downloading stuff [20:40] and shuts down [20:40] and start node [20:40] ahha [20:40] an installer :) [20:41] excellent. Thanks roaksoax [20:41] cool [20:42] on the road to building my own openstack cloud :) [20:43] cool :)