[00:59] how does one query the api using curl ? [01:02] I tried curl -u "username:password" "http://machine/MAAS/api/1.0/nodes/?op=list and got" "Unrecognised signature" [01:33] anybody deploy openstack with landscape / maas? I can get the OS deployed on the first node, but juju just sits there waiting for something [01:34] I have two network on the juju / landscape VM, and all of the hosts have 2 NIC's in them [01:34] do I need to define the networks in maas? the instructions aren't really clear [01:36] ahh, it wants to lookup the host with a hostname... gotta flip the DNS on I think [01:58] now it's stuck on deploying landscape... one wall at a time :) [02:06] so I have two nics on the landscape/juju VM, and I have both networks defined in maas... do I need to put that second nic on the network? do I need to put the maas on that second network too? or does it just manage the nics on the target nodes with that second defined network? [02:30] seems to be doing better with the second nic on the nodes attached at the maas level [02:39] meh.... gotta have 5 machines.... only got 4 :( === zerick_ is now known as zerick === zz_CyberJacob is now known as CyberJacob === CyberJacob is now known as zz_CyberJacob === racedo_ is now known as racedo === woop is now known as Guest39074 === Guest39074 is now known as woopwoop === woopwoop is now known as woopw00p === wojdev_ is now known as wojdev [17:01] hi. looking for help with MAAS 1.7. Seems to be some internal communications issue after initial image download [17:02] socket.error: [Errno 104] Connection reset by peer [17:05] johng, can you give me more detail? [17:06] in a proxy environment, all in one on a KVM vm. All setup works, set proxy via UI, can see image downloads happen. after image downloads, i get tjhis error in the logs and cluster is out of sync [17:07] see images are there on the systems.. download works fine [17:07] 2015-02-04 12:07:25-0500 [-] Logged OOPS id OOPS-d8256ede274f6493daf4df634b69b74c: error: [Errno 104] Connection reset by peer [17:08] johng, can you show me a screenshot of your /images page? [17:08] what do you mean when you say "download works fine"? [17:10] I can see heavy activity tomy proxy with iftop [17:10] and images screen gets to 2/2 [17:10] I see [17:10] johng, can you show me a screenshot of your /images page? [17:11] not sure how to get it to you via this freenode web.. [17:12] it shows the 1404 amd64 image is there [17:12] no custom images [17:12] 1404 and amd64 are all that is selected [17:12] what is the proper way to query "http://myIP/MAAS/api/1.0/nodes/?op=list" ? a regular curl -X GET doesn't work. [17:13] SimplySeth, when you say "doesn't work" what do you mean? [17:13] there is a python stack with the error as well... [17:14] Kiko ... the response is :Unrecognised signature: GET [17:18] kiko: works in chrome just fine though [17:18] SimplySeth, are you on 1.7 or 1.5? [17:18] experts, am using ubunt openstack-installer to install openstack, I keep getting this complaint that there are not 5 nodes that have more than one disk. I have given each node 2 disks each 20GB partions. Please advise [17:18] I think the issue is that nodegroups is the new black [17:19] no, that's not it, you're right [17:20] SimplySeth, I will tell you in a sec [17:20] kiko: 1.7 ... I think is what comes with 14.04LTS [17:22] SimplySeth, no, 14.04 currently has 1.5.4 [17:23] kiko: then it's 1.5 [17:23] ok [17:23] really been stuck at this for more than a day and I don't know how to even login to the nodes since I don't have a username and password on the node that is commissioned by maas. [17:24] Once maas commissions a node how can anyone login to it to for debug purposes.. (I need to see if the VM has 2 disks or not) pleae help [17:24] saltlake: did you set up an ssh key in maas? if so, you can simply ssh to nodes, that key would give you access [17:25] SimplySeth, I think the issue may be the lack of a cookie. /nodes/ does not allow anonymous requests [17:25] raodmr: I will try that right away. But if you can it is possible to check this VM xml to see if I have the 2 disks setup right ? http://pastebin.com/RbeMVGTH [17:26] kiko: okay [17:26] grep sdb5. I don't why openstack would not see this this [17:26] SimplySeth, I can reproduce by using a private browser window and going to the URL [17:26] Unrecognised signature: GET list [17:27] and why openstack-install repeatedly complains of the node not having more than one disk [17:27] SimplySeth, I think an ansible controller for maas would be killer! [17:28] saltlake: hm, per this, this node has hda, vda and vdb disks, right? I don't know if this will confuse maas but it certainly confuses me :) [17:28] kiko: that's why I'm trying to learn the secret sauce to querying the API [17:29] roadmr: I changed vda and vbd to hdb and hdc resp and tried as well (since /dev/sdb5 is a physical parition .. not formatted) [17:30] roadmr: I changed bustype from virtio to idea as well for those 2 disks vba and vdc but that failed commmisioning. Do you have a sample xmls for a node you created for openstack ? [17:30] xmls-> xml [17:30] saltlake: sorry, I've only ever used bare metal with maas :/ no idea about virsh nodes [17:31] Oh no!! [17:31] ok raodmr: I will try ssh ing to see if that tells me anything [17:31] saltlake: did you find out where to add the key? [17:31] I had added the key in the maas preference page [17:31] but I rebooted the server and it won't come back up.. [17:31] saltlake: go to your account details, you'll find an "SSH Keys" section there with a button, then put your public key there [17:32] then ssh to the IP address for that node [17:32] saltlake: yes, once the node is up you can ssh directly to its ip [17:32] saltlake: (or even to its blahblah.maas hostname if you're in the maas node itself) [17:33] SimplySeth, let me research and I'll post an answer to your askubuntu question [17:33] just a sec [17:33] kiko: I would greatly appreciate it. [17:34] SimplySeth, meanwhile, see SimplySeth, not answering your ansew [17:34] err [17:34] SimplySeth, meanwhile, see http://blog.allenap.me/2013/06/workaround-for-uploading-files-to-maas.html [17:35] kiko: cool thanks [17:35] SimplySeth, note the use of the python client api [17:36] kiko: I might have go directly to python instead of playing with BASH [17:37] SimplySeth, the issue is that the API uses OAuth [17:38] SimplySeth, I will still get you a more complete answer [17:38] kiko: thanks [17:40] my python error with the connection resets: [17:40] 2015-02-04 12:38:31-0500 [-] Unhandled Error [17:40] File "/usr/lib/python2.7/dist-packages/provisioningserver/boot/uefi.py", line 134, in download_grubnet [17:41] johng, can you put the whole traceback in a pastebin? [17:41] sure - how do I do that? [17:42] googled it [17:42] see if this works [17:42] http://pastebin.com/Snh4nBAi [17:43] johng, what version of maas? [17:44] ii maas 1.7.1+bzr334 all MAAS server all-in-one metapackag [17:44] same for dhcp and dns there as well [17:45] interesting [17:45] johng, it seems to me that the problem is that the UEFI download is not being done through the proxy [17:45] johng, can you check to see if my hunch is correct? [17:46] yes, it seems so [17:46] shucks [17:46] so my LTS image downloads, but boot does not? there is only one place to set proxy [17:46] yes [17:47] it seems to be a bug in maas [17:47] is it an easy edit somewhere that I can fix it? or shoudl O gi use 1.5? [17:48] I am not sure 1.5 would work tbh [17:49] very much apprecite you identifying it. much much appreciate if you can provide workaround. :-0 [17:52] johng, can you confirm first that the proxy is not getting the request for the grubnetx64.efi.signed file? [17:54] I don't have access to the proxy. What can I get fro yuo from the box? [17:57] johng, what port is the proxy listening on? [17:57] 8080 [17:58] guys i need some help i got maas going fine and it runs through an install from pxe boot but once done i just come to a black screen but power is still on and i can even send control alt delete and reboot the box why cant i see anything? [17:59] magicninja, this is at the end of installation, when the node would normally power off? is this maas 1.5 or 1.7? [17:59] johng, I guess a packet capture of anything going through your default route and going to port 80 would be useful [18:00] maas 1.7 i just installed the whole thing yesterday and it does shut down after the install but when it boots back up to my hdd it goes to a black screen [18:00] johng, because that would indicate we are trying to fetch resources directly [18:00] thx kiko [18:00] magicninja, at which point does it go to a black screen? [18:00] ok. I'm set up for that. be back in a few [18:00] thanks [18:00] thanks [18:01] after install is done it powers off then back up it boots my newly installed hdd but then just goes to a black screen [18:01] magicninja, does it for instance go through grub? do you see kernel messages? [18:01] but the computer is still on [18:01] i dont see grub like normal [18:01] it doesnt show up it just goes straight to black screen [18:01] magicninja, that's weird. perhaps the grub install failed? [18:01] but i can still press control alt delete and it will reboot [18:01] right [18:01] landscape isn't liking the hosts in maas.... all nodes had 2 x nics and 2 scsi disks, but landscape still complains that they don't have 2 disks [18:02] malikeye, Beret might be able to help you, but I think he'd EOD now [18:02] i tried reinstalling it from a rescue usb but no dice there either i can get to grub then but after i say boot ubuntu in grub... black screen [18:02] lsblk certainly shows 2 disks [18:02] reinstalling grub that is [18:03] i have another problem too if i try to do this install from a virtual box vm it boots into the image pxeboot goes fine but about halfway through starts saying ifconfig failed giving up after 60 seconds [18:03] any ideas there im all ears [18:04] physical machines have first problem vms just wont go past that spot they drop me to initramfs [18:07] just ran through the automated install process again finishing up now [18:07] doubt there will be any change though [18:07] magicninja, the ipconfig issue is a typical networking problem related to your bridge [18:08] it's very common [18:08] but it does let me pxeboot [18:09] it starts the image and everything just halfway through says that [18:09] do i have to do this on like a nat virtual network to make those work [18:09] i dont know why it wouldnt work though [18:09] i mean how i have it now with paravirtualized devices is how im running my server [18:10] the maas server is a vm and i just plug a box into our network and it pxeboots right away [18:10] with hardware it even goes through the whole process [18:10] magicninja, right, it's because dhcp is not very robust to packet droppage [18:10] with my hardware issue could it be because the drive in the box im installing is 3TB [18:10] so if the bridge for some reason drops or delays a packet [18:10] then the ipconfig will fail [18:11] ah [18:11] so do it on a nat'ed virtual network and that should make the vms work? [18:11] magicninja, another situation where this happens is when the node has multiple interfaces [18:11] oh and what is the best idrac etc to use for maas [18:11] yeah node doesnt have multiple interfaces [18:11] magicninja, any IPMI-compliant BMC should be fine [18:11] its a vm lol [18:12] a VM with multiple NICs [18:13] nope just one nic [18:13] i made sure after scouring the internet [18:17] okay [18:18] ill let you know what my hardware box does in just a minute [18:18] im not totally sure if this would cause a problem but... [18:18] the hardware machine i am testing with has intel chipset [18:19] but on the frontend when i click on the node i had it marked as amd64 after noticing this after my last attempt i changed it started it again and am almost done with the fresh install [18:19] sure is nice to have a chat room to talk this over with someone who knows about t [18:19] this stuff [18:19] ill try and stick around and give what support i can [18:21] i gotta admit with the architecture marked differently the install process sure did change [18:22] SimplySeth, http://askubuntu.com/questions/581444/how-to-query-maas-api-with-curl/581688#581688 [18:22] after a node installs it *should* come to a login prompt right? [18:22] magicninja, yes, but you should have uploaded an SSH key at this point which will allow you to ssh in, as no user is enabled to log in with a password by default [18:22] kiko: thank you [18:23] yeah i have one out there [18:23] SimplySeth, let me know if you get stuck; I tried hard to find a good way to do it with curl but it seemed like a bit too much work [18:23] i just dont see anything on the screen so i cant tell if i have a video problem or something is wrong wrong [18:25] magicninja, my hypothesis is that the bootloader isn't getting installed [18:25] magicninja, that would lead to the machine hanging at a blank screen [18:25] when it ran through the process it said it was installing it [18:26] ill pop in a live cd and reinstall it to the sda drive and reboot and let you know what happens [18:26] and even after this latest install i still get the same thing [18:28] magicninja, yeah, boot into a usb stick and chroot into the installed partition [18:28] magicninja, a grub-install should work [18:29] Kiko .. I'm perfectly comfy with Python .. thx [18:29] magicninja, having said that, AIUI for a 3TB frive it needs to be a GPT partition and UEFI boot [18:30] SimplySeth, okay -- if there are issues with the API let me know, because I don't know how many users we have that don't use the `maas` commandline client [18:30] if its not gpt would that cause a problem [18:30] magicninja, I think 2TB+ drives require GPT to be bootable [18:31] roadmr: I tried ssh to the client machine but it isn't possible to do so !! [18:31] The ssh key is for the maas node not the the other client nodes that are commissioned [18:32] saltlake: oh! maybe the key didn't get copied if deployment failed :( [18:32] the commissioning worked fine [18:32] saltlake: hm, all deployed nodes should have that key added to them [18:32] apparently its not up in any way cause i cant ping or anything after it goes to black screen but keyboard still functions [18:32] saltlake: yes, the key won't be added until they're actually started or provisioned, I think [18:32] saltlake, did you ssh as the ubuntu user? [18:32] roadmr is correct, the node needs to be deployed [18:33] I can't "deployment" to happen since the installer can't see 2 disks on the VM client [18:33] if you have only commissioned then you won't be able to connect [18:33] saltlake: you could "start" one node to then SSH into it and verify the disk configuration, maybe [18:33] +1 [18:34] tcpdump done. lots of files donwloaded, until we get to that grubx64.efi.signed file... proxy send about 4k then sends a reset wiht TSval and TSecr in the packets... [18:34] roadmr: How do Issh to it ? I don't have the username and password since it is pxe booted and commissioned from MAAS [18:35] saltlake: in the maas web UI, go to the node's page, there's a "start" button there [18:35] Ahh like that I was doing a virsh start node [18:35] saltlake: use that to start the node, it should boot up and install the operating system, it will be left in a "ready" state I think [18:35] saltlake: yes, once maas tells you the node is ready (or deployed, perhaps), then, from the maas server's terminal, you should be able to ssh ubuntu@NODE_IP [18:36] saltlake: it shouldn't ask for a password then, assuming you have the keys set up correctly [18:36] ok me trying.. it is just starting up. [18:36] ubuntu [18:36] sorry ignore.. wrong window [18:38] :D [18:39] johng, interesting -- seems to me like your proxy may be causing the issue (it might for instance not like the filetype or extension) [18:39] or content [18:39] radmr: after the node is started should it reboot ? (I am seeing the virtual window) Also should I levae network as the first boot option after the VM is commissioned ? [18:39] saltlake, the node will not reboot once started; it will be left running [18:40] saltlake, the boot option is irrelevant as we instruct the node to chain boot to the disk [18:41] kiko are you some kinda dev or something? [18:41] roadmr: kiko: thank you. [18:41] roadmr: it booted up and I see this : cat /proc/partitions [18:41] major minor #blocks name [18:41] 253 0 20971520 vda [18:41] 253 16 20971520 vdb [18:41] 8 0 31457280 sda [18:41] 8 1 31456256 sda1 [18:42] saltlake: I'd say it has 3 disks,right? [18:42] magicninja, product owner [18:42] roadmr: Yes it does.. so my xml is correct [18:43] roadmr: However the ubuntu installer compains "Atleast 5 nodes need more than 1 disk) and I have 8 nodes setup exaclty like this!! [18:43] ubuntu installer - > openstack-install [18:43] saltlake: which installer are you using? I wonder if the vda nomenclature confuses it somehow [18:43] saltlake: maybe it expects the disks to be sd* or hd* but I don't know the installer, where can I find it? [18:44] roadmr: I actually put hdb, hdc in the xml but the VM shows it thus!! [18:45] roadmr: http://pastebin.com/TM5EAzZR [18:45] saltlake: in the xml you showed me, the target names are vda and vdb; if you want them to show as hda/hdb in the VM, you have to change the [18:45] saltlake: ohh I see you changed it then [18:45] saltlake: after you changed the xml, did you undefine the VMs? otherwise they'll continue to use the old configuration. [18:46] roadmr: No I only edited and restarted [18:46] saltlake: I think you have to virsh undefine the nodes for the new config to take effect [18:47] saltlake: hehe I also haven't worked a lot with virsh (I suck, really), but my sequence is: virsh define blah.xml; virsh start vm-name; work work; virsh destroy vm-name; virsh undefine vm-name [18:47] saltlake: if I just start/destroy/start the vm, it doesn't reread the xml, uses the one I had when I defined it [18:48] roadmr: I will try that and give u the status.. .. the installer is fromthis : sudo apt-get install openstack; sudo openstack-install.. It goes through 20 min and then fails on the drive issue [18:48] ok I will be back after undefining everything in a little bit [18:49] saltlake: yo could undefine just one, then redefine it, and restart it with maas, just to ensure it changes as you expect [18:50] saltlake: once you're sure, do the others [18:50] roadmr: I just the dumped the xml for that client an I see the tag "backingstore" for those disks.. is that normal ? [18:51] saltlake: it should be OK, just specifies which storage mechanism to use [18:51] ok will try [18:52] johng, can you check with them? [18:52] I tried a diff proxy, got same error [18:53] where is the log written about an install of node [18:53] var log something? [18:53] I'm diggin into packet capture now to see exactly why I got a reset [18:54] magicninja, on the maas side or on the node side? [18:55] roadmr: I just undefined the VM, redined it. restarted the node from the MAAS server. sshd to it and I still see the same thing for /proc/partitions. [18:56] saltlake: that's weird.. [18:56] roadmr: i did not reprovision it from MAAS.. maybe that is requierd. [18:57] saltlake: did you destroy the vm? it should not show if you do 'virsh list' [18:57] gosh i did not .. sorry .. [18:57] :D === mmcc` is now known as mmcc [19:06] ok so i ran grub-install /dev/sda and now rebooting [19:07] magicninja, is it a GPT partition table btw? [19:07] oh you know what i didnt think to check while i was in there [19:08] heh [19:08] fdisk -l should show me right? [19:08] i mean i figure that it is otherwise i dont know how it could have installed there in the first place [19:08] yep [19:09] ok going back in to check before i boot it [19:09] it's mostly curiosity [19:09] im curious now too [19:09] and only takes a sec to go back and check [19:11] kiko - I see some double slashes in the url being requested [19:11] johng, that shouldn't matter -- you should be able to wget it from another machine (not behind a proxy) to test. [19:12] trying now [19:12] johng, double-slashes are generally folded in URLs [19:12] yeah my /dev/sda is gpt [19:13] roadmr: Its the same after the destroy/recommission - restart http://pastebin.com/Mfmm08cS [19:14] saltlake: damn :) can you pastebin the complete .xml file? [19:14] Yes It on that linkk with the /proc/paritions below the xml [19:15] roadmr: Oh it didn't put the whole file 1 sec [19:15] saltlake: :) [19:15] magicninja, okay, so maas got that right at least [19:15] roadmr: http://pastebin.com/xgN4rUqf [19:15] magicninja, does it contain a UEFI partition? [19:15] kiko. get network error on my local pc, as well as wget from the maas box [19:16] no just EFI i believe [19:16] http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/uefi/grub2-amd64/current/grubnetx64.efi.signed is the url [19:16] thats prob why but how do i manipulate that [19:16] magicninja, it should work [19:17] johng, 2015-02-04 17:17:08 (376 KB/s) - ‘grubnetx64.efi.signed’ saved [1001336/1001336] [19:17] works from here behind my proxy [19:17] kiko@gasolinux:~$ wget http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/uefi/grub2-amd64/current/grubnetx64.efi.signed [19:17] --2015-02-04 17:17:05-- http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/uefi/grub2-amd64/current/grubnetx64.efi.signed [19:17] Connecting to 192.168.99.4:3128... connected. [19:17] Proxy request sent, awaiting response... 200 OK [19:17] [...] [19:17] johng, looks like a local issue. can you check with the proxy gods if they can unblock the issue? [19:18] saltlake: something continues to be very weird, you're declaring hda, hdb, hdc in your .xml, but the partitions file shows vda, vdb, sda, which is completely different. [19:18] johng, I' m surprised you are getting a network error on your local box, though, unless you are behind the same proxy. [19:19] if you are, then you've nailed the problem :) [19:19] roadmr: I don't get it either.. I think I should deleter the physical location of the client1 img with ha [19:19] sda!! [19:19] roadmr: Does having the virtio bustype matter vs ide / [19:20] roadmr: I will actually define a completely new name and stop using client1 and use it to see if there is any diff [19:21] saltlake: sounds good. From what I just read, you should always try to use virtio [19:21] totally [19:21] if you don't mind sharing the source of the link.. it is not so apparent from virt-install --help [19:22] thanks for helping kiko. It was failing with nework error in chrome. after you tried i tried IE and it works. now it downloads in chrome as well.. go figure. no MAAS for me. guess I'll go staight juju rather than fight the peoxy-people.. [19:22] wget still fails... [19:22] Proxy request sent, awaiting response... 206 Partial Content [19:23] johng, how will you go straight juju without installing the nodes? [19:23] that's not a failure [19:23] partial content means that you already have part of the file locally [19:23] Read error at byte 842669/1001336 (Connection reset by peer). Retrying. [19:23] get lots of those.. [19:24] that's wget. [19:24] johng, and the proxy is mandatory, IOW, you can't issue requests directly? [19:24] i just dont get it i dont know what more to check even after installing grub still no dice [19:24] its in a lab. [19:24] johng, is it always at that location? [19:25] magicninja, I am a bit unclear as to what the boot process looks like on your node -- is it attempting to PXE-boot first, and then going blank? [19:25] need openstack on trusty. hoping I can just juju deploy stuff without MAAS. I have cobbler there.. [19:25] new to juju and MAAS if you could not tell) [19:25] i can make it do that but as i am through the install process even if i pxe boot it just boots my hdd [19:26] magicninja, that's correct [19:26] it connects then mass tells it to boot the hard drive [19:26] but then just blank screen [19:26] johng, you can't juju deploy without a provider [19:26] but keyboard still works and box still on [19:26] just no screen [19:26] does not respond to ping either [19:26] magicninja, hmm, to rule out anything else, does a USB install on that system works? [19:26] work [19:27] kiko I saw there was a manual provider but have not researched... will that not allow juju without MAAS for openstack deploy? [19:27] thats what im trying now but im pretty sure it will [19:27] am I going to have to build openstack from scratch? (uck) === roadmr is now known as roadmr_afk [19:29] inside the usb install when i hit partitioning it looks like maas set up three partitions one 3TB ext4 and one swap for 2.1GB and i think i did one called biosgrub 1MB [19:29] magicninja, that seems correct, it's a UEFI install IOW [19:29] magicninja, is your BIOS set up to boot in EFI mode btw? [19:29] hmmm not sure [19:30] johng, I think you are likely to suffer more than if you just get this file to come through :-) [19:30] before i reinstal let me check [19:30] johng, you can set up a local mirror and tell maas to use that [19:30] magicninja, that can make a difference [19:30] kiko - am I able to put the file there manually and avoid that last part of the download? [19:31] in bios i have a pci rom priority it was set to efi compatible but the only other option is legacy rom [19:31] johng, I'm not entirely sure of the answer to that :) [19:31] magicninja, pci rom? not boot? [19:31] magicninja, https://wiki.archlinux.org/index.php/beginners%27_guide#Troubleshooting_boot_problems [19:31] debmirror is on my list to learn.. is that what your referring to? [19:32] johng, well, I was actually referring to a simplestreams mirror, but I need help from a dev to give you a more complete answer [19:32] johng, well.. you could definitely hack the source and avoid the need to download that file :) [19:33] johng, look at uefi.py in provisioningserver/boot [19:34] just comment out the block from line 206 to 213 [19:36] and put the file in the right place [19:36] i.e. [19:37] var/lib/maas/boot-reources/snapshot*/grubx64.efi [19:38] that should be enough -- it's the last file of the boot resources you need to download [19:40] roadmr: same stuff with a new client that never existed so far.. I am confused.. Do you happen to have a virt-install command line you could share on how you might set up a disk .. is it because the source directory /dev/sdc5/ /dev/sdb5 are logical volumes on a physical disk ? [19:44] wow, I guess I have tried a lot. I have about 40 snapshots in there [19:48] johng, we download those once a day IIRC [19:48] All mine are dated today. :-) [19:51] you actually need 5 nodes for OS itself... the landscape / juju stuff sits on it's own node... so I'm using a huge blade to host landscape / juju [19:53] johng, gar! [19:53] malikeye: Can you share how you created the VM nodes ? [19:53] well after reinstalling grub i can get into grub now but when i boot ubuntu it just goes to same ol black screen [19:53] johng, I need to split, but if you still have issues, could you email maas-devel and we'll look at it overnight? [19:53] thanks [19:53] i just know this is something stupid [19:53] I didn't use VM's... I have UCS blades... I would've liked for landscape / juju to live in a VM though [19:54] you can't choose where it gets deployed I don't think [19:54] magicninja, did you see the URL I posted to you? [19:54] yeah havent gone through it yet though [19:54] kiko cluster howing sync after a reboot.. [19:54] magicninja, https://wiki.archlinux.org/index.php/Kernel_mode_setting#Disabling_modesetting [19:54] johng, synced! cool :) [19:55] I need to split, catch you all tomorrow [19:55] * kiko waves [19:55] do you know if the process will go back directories and find the grub file, or do I need to keep it in the latest one somhow? [19:56] malikeye: I have a large server and am working with VM ndose for everything. I don't care for performance. [19:56] later kiko! thanks a bunch [19:56] johng, the latter [19:56] I want the controllers to be VM and the nodes to be raw KVM [19:56] malikeye: I really hope to have a basic openstack install done else I get fired.. but if I figure it out I will share it on a blog for sure [19:56] k [19:57] these are 32-cre 256GB blades... so a whole blade for landscape / juju is a waste [20:07] saltlake: just make sure you have 5 nova nodes, 2 disks on each node, and 2 nics on each node [20:07] there is no way around that, unless you do the all-in-one === roadmr_afk is now known as roadmr [20:10] hmm, this is weird... maas only sees half the ram on these blades [20:10] Now I am quite certain that this is an issue with openstack-install and that it is unable to see 2 disks on the VM nodes and its complaint about "Atleast 5 nodes should have more than 1 disk) is unfounded. I have to be NOT THE first person who is facing this. [20:11] you need 5 nodes dedicated to nova with 2 disks [20:11] then you need a node for landscape / juju... you can run maas on that node I believe [20:11] if not on that same node, another for maas [20:11] == 7 [20:11] I have 8 VM nodes with 2 disks each. But the openstack-install has that gripe [20:11] are you using virtio? [20:11] 1 of those -> landscape. But there are 7 more [20:12] saltlake2: you never told me where to get openstack-install :) I can try to see how it checks for number of disks, see if your configuration is confusing it in any way [20:12] I think it needs to be scsi disks.... it doesn't like virtio [20:12] saltlake2: what confuses *me* is why you get those very weird disk names. I've never used virt-install, I have a hand-hacked .xml file :/ [20:14] malikeye: I have not eplored the scsi disk thing at ALL!! [20:14] that could make sense [20:14] roadmr: sorry. this is how I got openstack-install http://www.ubuntu.com/download/cloud/install-ubuntu-openstack [20:14] point 4 [20:15] malikeye: I will try to ee if making those disks scsi helps.. I hope those sources can be logical partitions. [20:15]