[00:02] <_mup_> juju/relation-hook-context r504 committed by jim.baker@canonical.com [00:02] <_mup_> relation_ident refactoring [00:38] <_mup_> juju/relation-hook-context r505 committed by jim.baker@canonical.com [00:38] <_mup_> Cache all relation contexts associated with a HookContext [00:42] marcoceppi: I've had some issues with the file storage thing. Try re-running destroy-environment. [01:40] <_mup_> Bug #963640 was filed: Implement external relation id support < https://launchpad.net/bugs/963640 > [02:42] <_mup_> juju/scheduler-peek-list r479 committed by kapil.thangavelu@canonical.com [02:42] <_mup_> merge trunk [02:50] <_mup_> juju/scheduler-peek-list r480 committed by kapil.thangavelu@canonical.com [02:50] <_mup_> address some review comments [02:55] <_mup_> juju/scheduler-peek-list r481 committed by kapil.thangavelu@canonical.com [02:55] <_mup_> address review comments [02:56] <_mup_> juju/trunk r503 committed by kapil.thangavelu@canonical.com [02:56] <_mup_> merge scheduler-peek-list [02:56] <_mup_> This is a rewrite of the relation hook scheduler for simplicity and greater tolerance [02:56] <_mup_> of errors, along ith greatly expanded test coverage. [05:38] <_mup_> juju/relation-hook-context r506 committed by jim.baker@canonical.com [05:38] <_mup_> Use correct unit in tests now that relation hook caching forces greater strictness === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away === almaisan-away is now known as al-maisan === TheMue_ is now known as TheMue [09:37] Hi, I have been looking and searching and does not seem to be able to find any documentation of how to add a relation between keystone and nova-cloud-controller if that's possible, correct me if I'm wrong, but shouldn't these two have a relation in order for the cloud-controller to create instances on the compute-nodes? [09:41] sc-rm: interesting question [09:43] sc-rm: nova-cloud-controller (in precise) requires {identity-service: {interface: keystone}} [09:44] sc-rm: so in theory, they do relate to one another. :) [09:44] sc-rm: http://jujucharms.com/interfaces/keystone [09:45] ok.. its nearly 3am.. time for me to stop :) [09:45] sc-rm: if you can stick it out for a while, adam gandelman will be on in about 6-7 hours, and he can explain the whole thing [09:46] anyway, sleep beckons [09:47] SpamapS: Thanks, I'll stick here, it's only 12am here ;-) [09:51] sc-rm, are you working with oneiric or precise? [09:57] jamespage: I'm working with precise [09:59] I have set up an entire structure with, cloud-controller, 2xcompute, mysql, rabbitmq, glance and then keystone, but adding the relation for the keystone is the only one that I'm having trouble adding correctly despite relation to mysql [09:59] sc-rm: we use these charms for automated testing of openstack [09:59] https://jenkins.qa.ubuntu.com/view/Precise%20OpenStack%20Testing/job/precise-openstack-essex-deploy/18277/console [09:59] juju add-relation nova-cloud-controller:identity-service keystone:identity-service === al-maisan is now known as almaisan-away [10:01] jamespage: that was also the command I fired the first time and then I get "No matching endpoints" [10:03] sc-rm: odd - the endpoints should match [10:03] can you check which versions of the charms you are using? [10:05] jamespage: revisions: keystone 135, cloud-controller 55, glance 31, compute 49 [10:06] sc-rm, hmm - looks like they might have changed a bit - worth pulling in the latest updates from the precise branches for each one [10:07] I know adam_g is working on them still for precise [10:07] but they should work [10:10] jamespage: I'm not that used to chamrs yet, so how do I update my charms the best way? I guess I can do that with some bzr command or juju? [10:11] sc-rm, if you drop into the specific charm directory and do 'bzr pull' it should yank down the latest goodness [10:17] jamespage: If it do that I get: "No revisions or tags to pull." But it also says "Using saved parent location: http://bazaar.launchpad.net/~charmers/charms/oneiric/ so I guess this is the problem [10:17] sc-rm, yes [10:17] you might want to grab a fresh copy of the precise charms [10:18] bzr branch lp:~charmers/charms/precise/XXX/trunk XXX [10:24] jamespage: that seems to give me a lot newer revisions, but it seems like I can not do that with mysql, get "bzr: ERROR: Invalid url supplied to transport: "bzr+ssh://bazaar.launchpad.net/~charmers/charms/precise/mysql/trunk": no supported schemes" [10:26] sc-rm, just use the mysql charm from oneiric for precise - it works just fine [10:29] jamespage: thanks, I'm bootstrapping from scratch to check it out :-) [11:36] jcastro, SpamapS, m_3: openerp + znc charms reviewed - feedback provided to author! === asavu_ is now known as asavu [12:04] jamespage: now it's able to do the add-relation, but the keystone host does not support "keystone-manage token add 999888777666 admin admin 2015-02-05T00:00" for instance, according to http://wiki.openstack.org/OpenStackDashboard so my guess is that to create the initial keystone accounts the keystone-manage command has changed. [12:29] jamespage: thanks man! [12:30] sc-rm, hmm - thats a bit beyond my knowledge I'm afraid - glad you got the charm working tho [12:31] #openstack or #ubuntu-server would be good places to ask [12:31] m_3: no problemo! [12:32] jamespage: Thanks, I'll try those channels instead... [12:32] sc-rm, hmm - just -reread you message [12:33] sc-rm, are the notes in http://charms.kapilt.com/charms/precise/keystone pertinent to that issue? [12:33] Cool, local provider is broken and I can't use port 22 with the convention center's wifi. This is going to be a fun charm school :) [12:38] Sorry, local provider isn't working on my machine, it's not necessarily broken [12:53] Hey hazmat you around? [13:06] marcoceppi, barely holding on [13:06] but yes [13:06] * hazmat is under the weather [13:08] hazmat: I think we figured it out [13:08] we were having some problems with lxc [13:08] but then realized he had series:oneiric in some places [13:09] gotcha [13:10] SpamapS, Hi; what's the news on getting the python charm-tools stuff packaged (and by extension getting python-shelltoolbox into the archive)? Is there anything ~yellow can do to help? [13:14] hazmat: hope you feel better soon dude! === almaisan-away is now known as al-maisan [13:48] <_mup_> juju/relation-hook-context r507 committed by jim.baker@canonical.com [13:48] <_mup_> Remaining relation_ident refactoring [13:53] bbcmicrocomputer, hive hwi is no longer supported as far as I can tell [13:53] at least it refuses to work === zyga is now known as zyga-afk [14:24] jamespage: really? wow, that's a shame [14:26] jamespage: yeah, looks like you're right [14:27] bbcmicrocomputer, oddly the war file still ships from upstream - it just does not work.... [14:27] quack quack ooopppss [14:28] jamespage: yeah, that's crap [14:28] jamespage: mind you, most of the main site looks unmaintained === al-maisan is now known as almaisan-away [14:31] bbcmicrocomputer, I have to admit that I found the documentation rather confusing [14:32] maybe that is why... [14:33] jamespage: same.. I had to source three books and some examples online before I could get a feel for it [14:34] jamespage: was pleasantly surprised when my test queries actually worked with the Hadoop cluster :) [14:34] bbcmicrocomputer, :-) [14:34] bbcmicrocomputer, I'm going to push hadoop 1.0.2 RC2 to the dev PPA later today - includes support for snappy native compression which should improve performance [14:35] jamespage: ah nice! === carif_ is now known as carif [15:47] gmb: its been pre-empted by getting more urgent stuff into the distro (since we can ship charm-tools in the PPA) [15:48] gmb: (re the python-shelltoolbox) [15:48] SpamapS: Okay, fair enough. Thanks. [15:49] gmb: I do hope to get it done soon. :) [15:49] Okay, cool. Thanks SpamapS. === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away [17:46] <_mup_> juju/trunk r504 committed by kapil.thangavelu@canonical.com [17:46] <_mup_> [trivial] change store url to correct location [19:31] <_mup_> txzookeeper/managed-watch-and-ephemeral r49 committed by kapil.foss@gmail.com [19:31] <_mup_> minor refactoring of client to assist in managed session client subclass to override nesc bits [19:50] hi, I have a question: I'm running juju on my beefy desktop machine, I'm using the local container based implementation there [19:50] now I'd like to connect to that system from my laptop [19:51] (specifically to the machines running on that server) [19:51] I've added relevant routing [19:51] but I still get nothing [19:52] I can easily connect from the actual machine there [19:52] and I've also enabled ipv4 routing via sysctl [20:05] <_mup_> txzookeeper/managed-watch-and-ephemeral r50 committed by kapil.foss@gmail.com [20:05] <_mup_> add managed session client, wip [20:46] zyga: when you say you've added the necessary routing, what do you mean? [20:46] zyga: the simplest thing would be to DNAT the ports you want to connect on [20:48] SpamapS: I've added route to the network used by the container [20:49] zyga: that should be enough.. [20:49] zyga: have you tried using tcpdump on your beefy machine to see the flow of packets back and forth? [20:50] no, let me try that [22:09] marcoceppi: rockin! [22:10] I hear the juju talk was awesome [23:49] hazmat: http://paste.ubuntu.com/904753/ ... looks like charmrunner needs an update for the new status code