[04:03] hi does charm-nova-compute support VMware? [04:05] or have to use this charm - nova-compute-vmware? It seems nova-compute-vmware has no update since 2014-06-24. https://code.launchpad.net/~openstack-charmers/charms/precise/nova-compute-vmware/trunk [04:06] @jamespage [04:06] jamespage, Do you have an answer about the above question? thanks. [04:07] jianghuaw: It will probably be a few more hours before he's around (assuming he's not travelling at the moment) [04:07] blahdeblah, thanks for the information. [05:36] menn0: if you're around https://github.com/juju/txn/pull/32 allows us to use RemoveAll($in) instead of Bulk when Bulk isn't really supported [07:32] hey guys [07:32] allah is doing [07:32] sun is not doing allah is doing [07:32] to accept Islam say that i bear witness that there is no deity worthy of worship except Allah and Muhammad peace be upon him is his slave and messenger [07:45] Good morning Juju world! === frankban|afk is now known as frankban [11:31] is it possible to access relation conversations from multiple charms related using the same interface? [11:31] or is it only possible to access one conversation at a time? [11:37] SimonKLB: I think you have access to a list of all conversations [11:37] let me grab an exmple of that [11:39] SimonKLB: https://github.com/juju-solutions/interface-dfs/blob/master/provides.py#L37 [11:40] kjackal: this is only going to grab the conversations of the units, not multiple charms, right? [11:40] of the units (in one charm)* [11:44] i believe a mix of relation_ids() and relation_get() will do the trick [11:50] SimonKLB: you are right this will give you the conversations the unit participates in. I've never seen a unit grabbing conversations of other units. [11:51] kjackal: no that is not what i want, i want all of the conversations between a charm and other charms related with a specific relation [11:52] for example, if wordpress was related to both mysql and mariadb, i would like the username and password from both databases in wordpress [11:53] i see [11:55] looks like youre blocked from accessing the relation when it's not in the correct context though === bdx_ is now known as bdx [17:10] SimonKLB: so long as you're in reactive, and using reactive states, you can iterate through the cached conversation data objects [17:10] thats something cory work on when implementing reactive, was to remove the requirement to be in context to access that data. [17:10] s/work/worked/ [17:11] SimonKLB: an example case: https://github.com/juju-solutions/interface-elasticsearch/blob/master/requires.py#L48-L51 === frankban is now known as frankban|afk [18:08] cory_fu: question on conjure-up. Is it posible for a partner to create a spell that would modify an already deployed k8s cluster? [18:18] So, there's this: https://github.com/conjure-up/conjure-up/issues/624 [18:18] That was planned for 2.2 but I really doubt that's going to happen. [18:18] But it's definitely in the plan. [18:20] Though, I realize that maybe that's not exactly what you were asking about. Are you talking about capturing a non-Juju deployed k8s cluster? [18:20] kjackal: ^ [18:21] I guess it's actually targeted at 2.2.1 and not 2.2.0 [18:22] cory_fu: well its targeted at milestone: later [18:22] is it later yet? [18:23] Oh yeah, apparently I can't read. [18:25] <3 [18:25] just poking at ya buddy :) [18:25] :) [18:25] cory_fu: lazyPower: so if a partner just wants to "kubectl create -f " he could write up a spell to do so? [18:25] I believe that's possible today, you skip the yaml def and only declare the scripted spell componentry, right cory_fu? [18:26] or am i making too many assumptions here, because there are a lot compacted into that statement [18:27] lazyPower: I don't know if it's possible to skip the deployment portion completely, but you also can't choose an existing deployed model in the GUI yet, either. [18:27] ah right thats only headless with flags [18:27] That was going to be part of that issue [18:27] Right [18:27] well, for POC they could get started... [18:27] but you're right the curses portion is going be a trail of tears [18:28] lazyPower: There's nothing technically challenging about that feature, it's just a matter of designing the user experience and the prioritization of it, though stokachu might correct me on that [18:29] yea thats pretty much it === med_ is now known as Guest76746 [19:02] cory_fu: CORYYYYYY [19:02] got a sec? :) [19:03] omg [19:03] What's up? [19:03] cory_fu: can you join us in the group hangout? [19:03] Yeah, one sec [19:03] Erin's on the phone in the background, but I'll use headphones so hopefully it won't be an issue