| mbruzek | You have clicked on propose for merging? | 00:00 |
|---|---|---|
| apuimedo | basically to enable cassandra to work in lxc | 00:00 |
| apuimedo | yup | 00:00 |
| apuimedo | should I press again? | 00:00 |
| mbruzek | hrmm... usually that creates a new bug | 00:00 |
| mbruzek | I can't find the bug. | 00:00 |
| apuimedo | ok | 00:00 |
| apuimedo | I'll press again | 00:01 |
| apuimedo | I see "Charles Butler: Pending requested 2015-04-22 " | 00:01 |
| mbruzek | I will review it right away | 00:01 |
| apuimedo | I'll propose for merging putting you as a reviewer now | 00:01 |
| mbruzek | Yes I see that too. I don't see how to approve or review these changes | 00:01 |
| mbruzek | Propose for merging and I will have a look | 00:02 |
| apuimedo | it tells me "There is already a branch merge proposal registered for branch lp:~celebdor/charms/precise/cassandra/hostname_resolve to land on lp:charms/cassandra that is still active." | 00:03 |
| mbruzek | OK let me check by that branch | 00:03 |
| apuimedo | let's see if I can just add you as a reviewer of the current proposal | 00:03 |
| mbruzek | I just need a link to the merge proposal | 00:03 |
| apuimedo | there | 00:03 |
| apuimedo | added | 00:04 |
| apuimedo | https://code.launchpad.net/~celebdor/charms/precise/cassandra/hostname_resolve/+merge/257120 | 00:04 |
| mbruzek | OK that is a different link | 00:04 |
| mbruzek | The reason this one is not in the review queue, is because the status is in "Work in progress" | 00:04 |
| mbruzek | It needs to be in "Fix committed" for the queue to pick it up. | 00:04 |
| apuimedo | try now | 00:06 |
| apuimedo | I can only move it to "needs review" | 00:06 |
| mbruzek | Oh my mistake | 00:06 |
| apuimedo | mbruzek: if you want to try the pinning | 00:07 |
| apuimedo | you can run it like so | 00:07 |
| apuimedo | mbruzek: http://paste.ubuntu.com/11833500/ | 00:08 |
| apuimedo | configuration yaml for deploying | 00:08 |
| apuimedo | and target an lxc machine | 00:08 |
| mbruzek | apuimedo: I found a problem. | 00:15 |
| mbruzek | apuimedo: Adding a configuration option like this must be added to config-changed. | 00:16 |
| apuimedo | mmm | 00:17 |
| apuimedo | let me see | 00:17 |
| apuimedo | where's config-changed? mbruzek | 00:18 |
| mbruzek | apuimedo: It is cassandra-common. Let me comment in the bug and | 00:19 |
| mbruzek | I will explain. | 00:19 |
| apuimedo | ok | 00:19 |
| mbruzek | OK. | 00:23 |
| mbruzek | This new configuration option is ONLY read on the install hook. | 00:24 |
| apuimedo | yes | 00:24 |
| mbruzek | If cassandra charm is installed and a user changes the package_version only the config-changed hook is called. | 00:24 |
| mbruzek | So the user would not see any error and *assume* the version has changed | 00:25 |
| mbruzek | juju set cassandra package_version=2.11 | 00:25 |
| mbruzek | apuimedo: I put my review in the Merge Proposal https://code.launchpad.net/~celebdor/charms/precise/cassandra/hostname_resolve/+merge/257120 | 00:26 |
| apuimedo | thanks for the review | 00:27 |
| apuimedo | I'll look into the changes you propose tomorrow | 00:28 |
| apuimedo | I was under the impression that as it stood, the charm didn't reinstall even if you changed the repo | 00:28 |
| apuimedo | (which is an already present configuration option) so that's why I did not consider the need for taking the config change into account | 00:29 |
| apuimedo | mbruzek: ^^ | 00:29 |
| mbruzek | apuimedo: I understand your point, but the immutable configuration breaks user expectations | 00:31 |
| mbruzek | If the user sets the version after install they would have no way to know the version was not changed. | 00:32 |
| mbruzek | You could have the same logic in the configure_cassandra function to run apt-get to get a specific version. | 00:32 |
| mbruzek | Once you have the change put the Merge Proposal back in Ready for Review and give me a ping I will review it straight away. | 00:34 |
| === kadams54 is now known as kadams54-away | ||
| === scuttlemonkey is now known as scuttle|afk | ||
| === kadams54-away is now known as kadams54 | ||
| === kadams54 is now known as kadams54-away | ||
| === kadams54-away is now known as kadams54 | ||
| === kadams54 is now known as kadams54-away | ||
| === mhilton_ is now known as mhilton | ||
| === lukasa_ is now known as lukasa_away | ||
| === lukasa_away is now known as lukasa_ | ||
| === scuttle|afk is now known as scuttlemonkey | ||
| caribou | Hi, is there some specific helper to add debconf values before installing a package or we should just shell out the debconf-set-selections command ? | 13:08 |
| === kadams54 is now known as kadams54-away | ||
| === kadams54 is now known as kadams54-away | ||
| === psivaa-afk is now known as psivaa | ||
| caribou | Is the juju-reboot statement still valid in a charm ? If so does it require a prior import in python ? | 15:07 |
| caribou | nevermind, I was just being stoopid | 15:16 |
| === kadams54 is now known as kadams54-away | ||
| === scuttlemonkey is now known as scuttle|afk | ||
| === scuttle|afk is now known as scuttlemonkey | ||
| === scuttlemonkey is now known as scuttle|afk | ||
| === lukasa_ is now known as lukasa_away | ||
| cory_fu | stub: I think we lost you | 17:10 |
| === kadams54 is now known as kadams54-away | ||
| === kadams54 is now known as kadams54-away | ||
| === scuttle|afk is now known as scuttlemonkey | ||
| === kadams54-away is now known as kadams54 | ||
| wolverineav | hi, I have a question related to quantum-gateway charm, I hope this is the right channel for it. | 19:59 |
| wolverineav | I see the TODO item on https://jujucharms.com/trusty/quantum-gateway : 'Support VLAN in addition to GRE+OpenFlow for L2 separation.' | 20:00 |
| wolverineav | does that mean that currently you cannot override the default and set it to VLAN only? | 20:01 |
| wolverineav | if that's the case, I guess the first step would be to submit an upstream patch to add a new configurable property, right? | 20:03 |
| wolverineav | oh, some context - this property would apply to the ML2 plugin in neutron (quantum-gateway for juju), which is currently set to 'type_drivers = gre,vxlan,vlan,flat' | 20:04 |
| lazyPower | wolverineav: this is the correct channel, but most of our openstack charmers are EU based. That would be a great question for the list - and I'll make sure to circle back and piont them at it | 20:15 |
| === kadams54 is now known as kadams54-away | ||
| wolverineav | lazyPower: thanks, appreciate it! i'm in pacific time, so i would still be around late evening - midday EU. | 20:20 |
| lazyPower | yeah - we have some fresh blood just now ramping up in the OS charm space that should be able to lend a hand moving forward | 20:20 |
| lazyPower | but its too soon to tap on them for questions like that :) | 20:20 |
| lazyPower | ddellav: ^ we're coming for you @_@ | 20:20 |
| === kadams54-away is now known as kadams54 | ||
| ddellav | lol | 20:21 |
| ddellav | i'll do what I can | 20:21 |
| wolverineav | haha..I guess this might be the perfect fit for ramping up - how to add a new config property which is set in the *.ini file before the charm is first applied ;-) | 20:30 |
| wolverineav | i'm just browsing through the 'hooks' to see how its passed around.. | 20:32 |
| marcoceppi | wolverineav: we don't really use quantum-gateway anymore,a nd instead use nuetron-api | 20:39 |
| marcoceppi | is there a reason you need quantum? | 20:39 |
| marcoceppi | fwiw, I believe the neutron charm supports VLAN with openvswitch | 20:40 |
| wolverineav | ah, I guess the example I saw was an old one which used quantum-gateway. and since it had 'trusty' and supported juno, I assumed its up to date | 20:42 |
| wolverineav | marcoceppi: let me try it out with neutron-api. thanks! | 20:43 |
| === kadams54 is now known as kadams54-away | ||
| === kadams54-away is now known as kadams54 | ||
| wolverineav | marcoceppi: when specifying 'network-manager: Neutron' in nova-cloud-controller, it is mentioned "When using the Neutron option you will most likely want to use the neutron-gateway charm to provide L3 routing and DHCP Services." | 21:23 |
| wolverineav | when I search for neutron-gateway: https://jujucharms.com/q/neutron-gateway , I see three relevant charms - quantum-gateway, neutron-openvswitch and neutron-api | 21:24 |
| wolverineav | what is the recommended combination when deploying with L3 and DHCP service? | 21:25 |
| wolverineav | I'm guessing its nova-cloud-controller + quantum-gateway + neutron-api. and the last one (neutron-api) is what I was missing earlier | 21:26 |
| wolverineav | ah, actually no - nova-cloud-controller + neutron-api are part of openstack controller. neutron-openvswitch is on every compute node and the node where we deploy quantum-gateway. | 21:35 |
| === kadams54 is now known as kadams54-away | ||
| === kadams54-away is now known as kadams54 | ||
| === kadams54 is now known as kadams54-away | ||
| === kadams54 is now known as kadams54-away | ||
| === kadams54-away is now known as kadams54 | ||
| === kadams54 is now known as kadams54-away | ||
| marcoceppi | wolverineav: yes, sorry, seems liek you've gotten it now | 23:39 |
| marcoceppi | if it helps I can give you a bundle that is a reference architecture for OpenStack which includes how neutron-api works | 23:39 |
| wolverineav | marcoceppi: yes, that would be helpful :) | 23:41 |
| marcoceppi | wolverineav: https://jujucharms.com/openstack-base/ | 23:42 |
| marcoceppi | wolverineav: and here's the actual bundle https://api.jujucharms.com/charmstore/v4/bundle/openstack-base-34/archive/bundle.yaml | 23:43 |
| wolverineav | marcoceppi: this is great! thanks! | 23:55 |
| === kadams54 is now known as kadams54-away | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!