| smoser | roaksoax, are you around ? | 00:43 |
|---|---|---|
| smoser | roaksoax, there are two MP there. i'm really ok with you chosing either one. | 00:48 |
| === freeflying_away is now known as freeflying | ||
| === freeflying is now known as freeflying_away | ||
| === freeflying_away is now known as freeflying | ||
| === julian__ is now known as julianwa | ||
| roaksoax | smoser: sorry wasn | 03:29 |
| roaksoax | feeling so good | 03:29 |
| roaksoax | smoser: i'll take a look tomorrow | 03:29 |
| === CyberJacob|Away is now known as CyberJacob | ||
| androoo | hey, is anyone here willing to help out a noobie? | 07:29 |
| racedo | ping rvba | 08:31 |
| rvba | racedo: Hi (otp right now). | 08:32 |
| racedo | rvba: oh sorry | 08:32 |
| racedo | rvba: quick one when you can | 08:32 |
| racedo | rvba: when splitting maas region controller and maas cluster controller into different servers, the juju client will never talk directly to the maas cluster controller, right? | 08:33 |
| rvba | racedo: correct | 08:43 |
| racedo | rvba: many thanks :) | 08:43 |
| rvba | Welcome :) | 08:43 |
| racedo | rvba: and we can have just one juju bootstrap node for all the maas cluster controllers? | 08:44 |
| racedo | rvba: or should we commission one per cluster controller? | 08:45 |
| rvba | racedo: yes, as long as all the nodes managed by all the cluster controllers can talk to each other. | 08:45 |
| racedo | rvba: ok, so multiple juju bootstrap nodes is kind of pointless then | 08:45 |
| rvba | Yes. | 08:45 |
| racedo | cool, thanks again rvba | 08:45 |
| === CyberJacob is now known as CyberJacob|Away | ||
| === freeflying is now known as freeflying_away | ||
| AskUbuntu | Migration from generic OpenStack to Ubuntu Openstack | http://askubuntu.com/q/353127 | 12:10 |
| === freeflying_away is now known as freeflying | ||
| roaksoax | rvba howdy | 13:15 |
| rvba | Hi roaksoax | 13:15 |
| roaksoax | rvba: hold on those ladt two mps | 13:15 |
| roaksoax | last* | 13:15 |
| rvba | roaksoax: don't worry, I don't intend to land them now. | 13:15 |
| roaksoax | rvba: ok ;) ill review them in a bit | 13:15 |
| rvba | roaksoax: they are mostly to get us started on testing the new script. | 13:16 |
| roaksoax | rvba: ok but im releasing maas again today | 13:16 |
| rvba | Okay. | 13:17 |
| roaksoax | rvba: ok, commented on them | 13:48 |
| roaksoax | rvba: other than that if they can be merged today | 13:48 |
| roaksoax | rvba: it would be great | 13:48 |
| rvba | roaksoax: Thanks for the review. We will need more testing before we land it; in particular, we want to make sure the old config gets migrated ok. | 13:50 |
| roaksoax | rvba: ok | 13:50 |
| roaksoax | rvba: though it would have been simple to keep the old config style as it is with import_pxe_files | 13:51 |
| roaksoax | y | 13:51 |
| rvba | roaksoax: we will rewrite maas-import-pxe-files in Python too. We thought it was a better idea to unify the configs. | 13:51 |
| roaksoax | rvba: ok | 13:52 |
| freeflying | rvba, if import-pxe-files support specify mirror, might be more convenient | 14:37 |
| rvba | freeflying: true, we're still working on maas-import-ephemerals and import-pxe-files is our next target but you're right, we need to be able to configure where simplestreams will fetch its information. | 14:40 |
| === freeflying is now known as freeflying_away | ||
| stokachu | is the web interface the only way to manually enlist nodes? | 16:26 |
| kurt_ | roaksoax: ping | 17:00 |
| roaksoax | kurt_: pong | 17:38 |
| roaksoax | stokachu: if you have a live image on the node, you could install maas-enlist | 17:39 |
| stokachu | roaksoax: ok ill try that | 17:41 |
| kurt_ | roaksoax: something I was thinking through with MAAS/juju - there is no way to guarantee a particular node with particular resources is used for a enlistment/commission/juju deployment - is that right? | 17:43 |
| kurt_ | if you don't have control over WOL, you are in bad shapee | 17:44 |
| kurt_ | shape | 17:44 |
| kurt_ | actually that doesn't even matter from juju's perspective it seems | 17:45 |
| roaksoax | kurt_: ideally you need control over ipmi, but enlistment/commuissioning are steps that have to be done in order for the machines to be available to juju | 17:46 |
| roaksoax | kurt_: now, you would need to add tags to the noeds to identify them based on constraints | 17:47 |
| roaksoax | and that way, when you juju deploy something you can gfarantee that a particular node with mparticular hw detauls is assigned to juju by specifying the constraints | 17:47 |
| kurt_ | tags? | 17:47 |
| kurt_ | first I'v heard of this | 17:48 |
| roaksoax | kurt_: http://maas.ubuntu.com/docs/tags.html | 17:48 |
| kurt_ | thanks I'll have a look - that integrates with juju? | 17:49 |
| === matsubara is now known as matsubara-lunch | ||
| kurt_ | ahhh…I seee | 17:50 |
| * kurt_ lightbulb lights up | 17:50 | |
| smoser | stokachu, you can enlist nodes with the cli too | 17:53 |
| stokachu | smoser: i was able to get it to work with maas-enlist, is there another preferred way? | 17:56 |
| roaksoax | stokachu: maas-nelist when manually | 17:56 |
| roaksoax | stokachu: it is much easier, and that's what it is actually used when running the enlistment process | 17:56 |
| stokachu | cool that worked like a champ | 17:56 |
| smoser | stokachu, are you using real nodes ? | 17:57 |
| === CyberJacob|Away is now known as CyberJacob | ||
| stokachu | smoser: virtualbox atm | 17:57 |
| smoser | virtualbox. | 17:57 |
| smoser | for real? | 17:57 |
| smoser | are you running this on windows! | 17:57 |
| stokachu | haha | 17:58 |
| kurt_ | smoser: I have been very successful with VMWare workstation too | 17:58 |
| stokachu | im trying to automate a maas+10 node setup | 17:58 |
| kurt_ | and Fusion on Mac OSX | 17:58 |
| kurt_ | I'm in the middle of blogging the experience | 17:58 |
| smoser | stokachu, http://bazaar.launchpad.net/~virtual-maasers/charms/precise/virtual-maas/trunk/files | 17:58 |
| smoser | see README-nojuju.txt | 17:58 |
| smoser | that is basically what you're after | 17:58 |
| smoser | and you dont have to use virtualbox | 17:59 |
| stokachu | ok ill try that way next | 17:59 |
| kurt_ | what does virtual-maas do differently? | 17:59 |
| stokachu | uses kvm | 17:59 |
| kurt_ | in what way? I've got a hypervisor | 18:00 |
| stokachu | you manage all your nodes and maas server with libvirt | 18:01 |
| kurt_ | regulär maas has that built in too, does it not? | 18:01 |
| smoser | maas has support for "power" control via virsh | 18:01 |
| smoser | virtual-maas just uses that. | 18:01 |
| smoser | and http://bazaar.launchpad.net/~virtual-maasers/charms/precise/virtual-maas/trunk/files | 18:02 |
| smoser | has tools to create nodes and insert them into maas. | 18:02 |
| smoser | and remove them. | 18:02 |
| kurt_ | ok because virsh is a part of libvirt | 18:02 |
| stokachu | kurt_: this helps you automagically deploy maas+nodes | 18:02 |
| smoser | virsh is a part of libvirt, yes. it wouldn't be hard to extend maas's power control to cover virtualbox. | 18:02 |
| kurt_ | ok, I just figured out how to do this all manually on my own, so I'm curious about the benefit | 18:03 |
| smoser | and if you have some reason that you want virtualbox (like you want to use this on a mac) then that might make sense to re-invent things. | 18:03 |
| smoser | but what is there in 'virtual-maas' is very close to "just works". | 18:03 |
| smoser | as a "all in one maas" with virtual nodes. | 18:03 |
| kurt_ | for some reason I remember reading virtual-maas not going to be updated too | 18:04 |
| stokachu | kurt_: i posted a blog article on setting up maas within lxc | 18:04 |
| kurt_ | stokachu: I'm working on blogging my results too | 18:04 |
| stokachu | kurt_: http://astokes.org/running-maas-vagrant/ | 18:04 |
| kurt_ | I'll have a look | 18:04 |
| smoser | kurt_, sothere are some parts of virtual-maas that are hacky. | 18:05 |
| smoser | its basically all in one. | 18:05 |
| smoser | it doesn't survive reboot | 18:05 |
| smoser | those htings can be fixed for sure | 18:05 |
| kurt_ | I just found out about the tagging thing, which will make life exponentially better | 18:05 |
| kurt_ | I've managed to get MAAS/Juju and Openstack fully up and running | 18:06 |
| kurt_ | on VMWare Fusion and Workstation that is | 18:06 |
| kurt_ | anyways - you have now piqued my curiosity | 18:07 |
| kurt_ | to see how much work I did for NOTHING :D | 18:07 |
| kurt_ | lol | 18:07 |
| kurt_ | smoser: so is virtual-maas officially supported on precise? | 18:08 |
| smoser | "officially", no | 18:09 |
| smoser | it will probably work. | 18:09 |
| smoser | its really a development thing. | 18:09 |
| kurt_ | right | 18:09 |
| smoser | but there is a lot of generally usable things there. | 18:10 |
| smoser | ie, scripts to add a node to libvirt with 2 disks and X memory and then shove that node into maas | 18:10 |
| smoser | and then (generically) power that machien on and install it with release X | 18:10 |
| smoser | the only hacky things really are in getting maas up and going and listening on the maasbr0 network and the networking involved. | 18:11 |
| kurt_ | ok. | 18:11 |
| stokachu | so has anyone run maas in virtualbox on windows? :) | 18:11 |
| kurt_ | workstation :) | 18:11 |
| smoser | kurt_, really. give it a try. if you have a system with 8G memory, its fairly easy. | 18:11 |
| stokachu | kurt_: did you use vagrant or just manually through vmware? | 18:11 |
| smoser | slow, but easy. | 18:11 |
| smoser | and you can play. it is a very easy way to get a juju going | 18:12 |
| kurt_ | manually | 18:12 |
| kurt_ | as I said, it works quite well | 18:12 |
| stokachu | kurt_: ok, ive got a pretty automated thing ive setup if you dont mind testing on windows | 18:12 |
| stokachu | im not done yet but hopefully tomorrow | 18:12 |
| stokachu | it would use virtualbox though | 18:12 |
| kurt_ | stokachu: thing = a package, scripts? | 18:13 |
| stokachu | kurt_: yea using vagrant+virtualbox | 18:14 |
| stokachu | but automated | 18:14 |
| stokachu | just curious if it is portable across mac/windows | 18:14 |
| kurt_ | if it means I have to take down my workstation install, I'm afraid its going to have to wait - I'm knee deep in blogging | 18:15 |
| stokachu | it wont touch your vmware stuff | 18:16 |
| stokachu | in any case just let me know when/if youre interested | 18:16 |
| kurt_ | ok. I'm playing with ceph next too | 18:16 |
| stokachu | kurt_: nice, dont forget to write your findings i'd be interested in looking at that too | 18:17 |
| === matsubara-lunch is now known as matsubara | ||
| kurt_ | will do ;) | 18:23 |
| stokachu | is there a way to alter the preseed file or do i need to edit it manually | 19:14 |
| stokachu | http://maas.ubuntu.com/docs/development/preseeds.html i see this page | 19:15 |
| stokachu | im trying to force the enlist server to be on a specific network device | 19:18 |
| stokachu | seems to default to the first device no matter what | 19:18 |
| stokachu | whats the best way to override http://paste.ubuntu.com/6189451/ | 19:20 |
| stokachu | thats from maas_local_settings.py | 19:20 |
| kurt_ | stokachu: can't you go in to the interface and specify which device its doing dhcp on? | 19:30 |
| kurt_ | interface = web gui | 19:30 |
| stokachu | lemme check | 19:30 |
| stokachu | eth1192.168.50.255/24Manage DHCP and DNS | 19:31 |
| kurt_ | right | 19:31 |
| stokachu | so its using eth1 | 19:31 |
| kurt_ | correct | 19:31 |
| stokachu | but the default maas url is set to 10.0.2.15 | 19:31 |
| stokachu | which is eth0 | 19:31 |
| kurt_ | you need to dpkg-reconfigure | 19:31 |
| kurt_ | set it to the IP of the maas url you want | 19:31 |
| stokachu | in my dhcpd.conf? | 19:32 |
| kurt_ | no | 19:32 |
| kurt_ | hang on | 19:32 |
| stokachu | dpkg-reconfigure maas-region-controller lets me change the maas url | 19:33 |
| kurt_ | right | 19:33 |
| kurt_ | that's what I meant | 19:33 |
| stokachu | ah ok, how do i do this programmatically though | 19:33 |
| kurt_ | you mean from the maas-cli? | 19:33 |
| stokachu | sure or any other avenue | 19:34 |
| * kurt_ crickets | 19:34 | |
| stokachu | lol | 19:34 |
| stokachu | hmm if only i could pass an ip to dpkg-reconfigure | 19:35 |
| stokachu | during setup | 19:35 |
| kurt_ | there has to be a way | 19:35 |
| kurt_ | did you fully research the maas-cli options? | 19:35 |
| stokachu | ill look through it again and see if im missing something | 19:35 |
| kurt_ | hmm…well that wouldn't work too well | 19:35 |
| kurt_ | because the authentication is tied in to the url for the maas-cli | 19:36 |
| stokachu | i found this http://paste.ubuntu.com/6189525/ | 19:37 |
| kurt_ | that's a roaksoax or bigjools question | 19:37 |
| stokachu | not sure if enlistment_domain would work or not | 19:38 |
| kurt_ | why do you need to change the maas url once or twice? | 19:38 |
| stokachu | so when i install maas onto a server with eth0 and eth1 i need mass to only listen and respond on eth1 | 19:39 |
| stokachu | for whatever reason eth0's ip is being picked for the maas default url | 19:39 |
| kurt_ | you could hack IP forwarding to make it not matter :) | 19:39 |
| stokachu | true | 19:40 |
| kurt_ | which is what I've done as I recall | 19:40 |
| stokachu | ive edited the maas_local_settings.py for now which seems to provide a proper preeseed | 19:40 |
| kurt_ | but I've always just gone back in and reconfigured as you put in above | 19:40 |
| stokachu | ok | 19:41 |
| kurt_ | I need IP forwarding on my virtual network anyways | 19:41 |
| kurt_ | that's the only way my maas nodes are going to get access to the internet | 19:41 |
| kurt_ | so its always just worked for me | 19:41 |
| kurt_ | stokachu: btw this is the best guide on easy IP forwarding in case you didn't have an easy source | 19:47 |
| kurt_ | http://askubuntu.com/questions/95199/two-network-cards-and-ip-forwarding | 19:47 |
| stokachu | thanks | 19:48 |
| stokachu | i think cloud-tools archive died | 20:26 |
| stokachu | The following packages have unmet dependencies: maas : Depends: maas-region-controller but it is not going to be installed | 20:41 |
| stokachu | smoser: ^ was there a recent push to archive | 20:42 |
| stokachu | guess that should be roaksoax ^ | 20:47 |
| dpb1 | should this work? curl http://169.254.169.254/2009-04-04/meta-data/ (from a maas node) ? | 21:04 |
| stokachu | bah ithink the archive is broken :( | 21:08 |
| dpb1 | Anyone seen this error with juju/maas from the UCA: agent-state-info: '(error: could not access file ''tools/juju-1.14.1-precise-i386.tgz'': | 21:16 |
| dpb1 | gomaasapi: got error back from server: 401 UNAUTHORIZED (Nonce already used: | 21:16 |
| dpb1 | 33410643))' | 21:16 |
| dpb1 | machines 1-18 went fine, on deploying this one, I got this error. | 21:16 |
| === CyberJacob is now known as CyberJacob|Away | ||
| === matsubara is now known as matsubara-afk | ||
| stokachu | is anyone else using the cloud-tools archive? | 23:21 |
| stokachu | it seems to be busted | 23:21 |
| stokachu | roaksoax: ^ | 23:48 |
| roaksoax | stokachu: why is that? | 23:51 |
| roaksoax | stokachu: what are you experiencing? | 23:51 |
| roaksoax | 5 | 23:52 |
| roaksoax | 4 | 23:52 |
| roaksoax | 3 | 23:52 |
| roaksoax | 2 | 23:52 |
| roaksoax | 1 | 23:52 |
| * roaksoax dead | 23:52 | |
| roaksoax | :) | 23:52 |
| stokachu | roaksoax: sec | 23:53 |
| stokachu | roaksoax: http://paste.ubuntu.com/6190310/ | 23:54 |
| roaksoax | stokachu: are you using saucy? | 23:55 |
| stokachu | this is on precise using the cloud-tools repo | 23:55 |
| roaksoax | this seems because tierh package has a higher version and it is trying to install a lower version | 23:55 |
| roaksoax | stokachu: weird, I'll test later | 23:55 |
| roaksoax | gotta go | 23:55 |
| stokachu | ok | 23:55 |
| stokachu | deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/cloud-tools main | 23:56 |
| stokachu | deb-src http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/cloud-tools main | 23:56 |
| stokachu | thats my sources.list | 23:56 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!