| jose | marcoceppi: around? | 01:20 |
|---|---|---|
| === menn0 is now known as menno0-afk | ||
| === urulama is now known as uru-LJ | ||
| jamespage_ | lazyPower, designated: I do have a plan to work on that this cycle - we had some work done for a customer to enable this but I was not happy it was up for general use. | 05:51 |
| jamespage_ | I have a proposed reference network topology and approach - basically you would be able to specify which network is used for each type: | 05:52 |
| jamespage_ | admin-network: 10.5.5.0/24 | 05:52 |
| jamespage_ | for example | 05:52 |
| jamespage_ | and the charm will figure out which configured network interface should be used for internal/admin traffic | 05:52 |
| jamespage_ | there is already stuff in charm-helpers to discover network interfaces by cidr | 05:53 |
| jamespage_ | I think its still up to MAAS/juju to actually configure the nics... the charms will not do that | 05:53 |
| === CyberJacob|Away is now known as CyberJacob | ||
| Mosibi | designated lazyPower jamespage :: that's functionality we also like to have in the openstack charms. We are working with the openstack charms and for example we have a VLAN interface where we want the tenant/neutron traffic to go/flow over | 06:44 |
| Mosibi | Besides that, in our previous (pre-juju) deployment, we used vlan for the tenant networks. We would love to have that possibility in the charms. | 06:45 |
| Mosibi | As i mentioned yesterday on this channel, a colleage started working on the charms (for some other things we need) and when he has working code, he will submit it | 06:47 |
| jamespage | Mosibi, sounds good - I have a design in mind for a reference network architecture based on best practices I've seen | 06:48 |
| jamespage | Mosibi, once I have a little more polished I'll circulate it | 06:49 |
| jamespage | Mosibi, juju + MAAS are due to grow first class support for managing network connectivity which will help alot | 06:49 |
| jamespage | Mosibi, configuring the charms themselves is not actually that hard - the work done before was implemented on a deployment with bonded 10G nics, with traffic separation via VLAN | 06:50 |
| === CyberJacob is now known as CyberJacob|Away | ||
| === vladk|offline is now known as vladk | ||
| === gmb`` is now known as gmb | ||
| stub | Freshly bootstrapped local provider with 1.18.4, I get a happy machine 0, status etc. working. But I can't deploy a service. The new machine just hangs 'pending', and there are no logs. | 10:52 |
| stub | Any hints on diagnosing this further? | 10:53 |
| stub | The jujud process is regularly kicking in chewing a little CPU, but no idea what it is doing. | 10:53 |
| stub | Looks like the machine is created, but ssh is failing. All my keys being refused, including ~/.juju/ssh/juju_id_rsa | 10:59 |
| === vladk is now known as vladk|offline | ||
| === vladk|offline is now known as vladk | ||
| === vladk is now known as vladk|offline | ||
| stub | machine-0: no kvm containers possible ? | 11:45 |
| === vladk|offline is now known as vladk | ||
| === psivaa is now known as psivaa-lunch | ||
| stub | So for those reading along at home, ufw had been enabled and my lxc stuff on 10.0.3.* was unable to talk to my main lxc IP, including the log messages. | 12:21 |
| lazyPower | jamespage: thats awesome to hear. Thank you for the follow up | 12:50 |
| lazyPower | stub: ah, good catch. I haven't heard of any UFW based issues in a bit. Looks like its back to haunting around and stirring up trouble. | 12:51 |
| lazyPower | stub: did you see jorge's fix for rsyslog-forwarder? https://code.launchpad.net/~niedbalski/charms/precise/rsyslog-forwarder/lp-1323627/+merge/221903 | 13:04 |
| stub | yeah. I was copying from the charm, as it seemed to be the only place the syslog interface was documented | 13:05 |
| stub | I'd review it but I have no idea what the double @@ or lack thereof would do | 13:07 |
| lazyPower | stub: i'm looking at it myself - it appears to just change the port on the destination | 13:08 |
| lazyPower | from 10514 to 514 | 13:08 |
| lazyPower | niedbalski_: any light wrt the @@ in the config change proposed for rsyslog-forwarder? | 13:11 |
| === tedg is now known as ted | ||
| === psivaa-lunch is now known as psivaa | ||
| === ted is now known as tedg | ||
| stub | lazyPower: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/573461 , fixed in utopic but trouble for me | 13:32 |
| _mup_ | Bug #573461: UFW blocks libvirt bridged traffic <amd64> <apport-bug> <lucid> <ufw (Ubuntu):Fix Released> <https://launchpad.net/bugs/573461> | 13:32 |
| lazyPower | bizarre. Apparently I'm running the devel release | 13:33 |
| lazyPower | i thought i was on 1.18.4, nope. 1.19.3 | 13:33 |
| niedbalski__ | lazyPower, ,@host is udp, @@host is TCP, now by default is forwarding to UDP (ref: http://www.rsyslog.com/doc/rsyslog_conf_examples.html) | 13:34 |
| lazyPower | ahhhhh ok. | 13:34 |
| stub | I knew that. | 13:38 |
| === alexisb_out is now known as alexisb | ||
| lazyPower | stub: haha :) | 14:41 |
| lazyPower | that's amusing. I got bit by that earlier today too. knowing something but not knowing it. | 14:42 |
| khuss | i am installing havana openstack on Ubuntu 12.04 using juju. How do I find the compatible ceph version | 14:44 |
| khuss | does a juju charm install the actual package or is it done outside the charm? | 15:14 |
| lazyPower | khuss: the charm is responsible for installing any packages required to run the service. | 15:17 |
| khuss | lazyPower: the cs:precise/ceph is installing the very old version of ceph.. | 15:18 |
| khuss | lazyPower: the charm is the latest though... i;m wondering how to upgrade the ceph itself | 15:19 |
| khuss | lazyPower: the readme doesn;t say what version of the ceph is installed by this charm | 15:19 |
| lazyPower | khuss: it may be prudent to open a bug against the precise ceph charm to have the ceph version updated. | 15:19 |
| lazyPower | I know the openstack charmers are really responsive on the bug tracker. | 15:19 |
| khuss | lazyPower: is there a way to manually update the ceph version | 15:20 |
| lazyPower | khuss: it's recommended that you use the charm to perform any upgrades, to keep support consistent. If a newer version of ceph breaks the charm functionality, teh charm itself would need to be upgraded. I'm not that familiar with ceph, so its hard for me to say what the implications are with just cowboying an update. | 15:21 |
| khuss | lazyPower: are you aware about any irc channel for juju openstack charms | 15:21 |
| lazyPower | khuss: they are in #juju | 15:24 |
| khuss | lazyPower: if I can find them :) | 15:24 |
| lazyPower | niedbalski_: approved LP221903 | 15:26 |
| elarson | would a charm be the correct unit to release an app? I say "app" in the sense that "services" deployed with juju might be mongo or hadoop where as the "app" would be an application that is used by the organization and is their code. | 15:39 |
| * elarson is just starting with juju and trying to understand where it fits | 15:40 | |
| khuss | lazyPower: i've a charm in a weird state. there are no machines associated it with. juju destroy-service doesn't remove it so I'm not able to deploy the new charm. here is the output from juju status: ceph: charm: cs:precise/ceph-26 exposed: false life: dying relations: client: - glance | 15:44 |
| lazyPower | khuss: is there a dependent service that's related to ceph in an error state? | 15:55 |
| lazyPower | if hook relations fail, the charm will be stuck in a dying state pending you resolving them. | 15:55 |
| khuss | lazyPower: well there is a broken relationship but it is almost like a deadlock. Both services can't be killed | 16:00 |
| lazyPower | khuss: have tried resolving on the service its related to? | 16:01 |
| lazyPower | juju resolved service/# | 16:01 |
| lazyPower | thats kind of risky if you're in ap roduction setup - as it may leave behind some traces that the charms departed hook performs. YMMV if you go this route. | 16:01 |
| lazyPower | it would probably be better to debug-hooks into the service and re-execute the hook to determine why its failing if its a production system. | 16:01 |
| khuss | lazyPower: i tried resloved but it didn't work.. may be I will do juju destroy-environment and start all over | 16:04 |
| designated | jamespage, That sounds awesome. You have already figured it all out or you'll be working on it? I'm interested in whatever information you can provide. | 16:32 |
| themonk | i am facing a problem with config-changed and relation-chabged, problem in i have a template in this template a variable is ip, this ip is dependent on relation-changed, when relation happen it comes from other service, but that template has other variable which are comes from config.yaml so if i change config after relation-changed ip will change to default 'localhost' and relation will bw broken, how do i fix this? | 16:34 |
| themonk | lazyPower: hi | 16:35 |
| themonk | marcoceppi: hi | 16:36 |
| lazyPower | themonk: you need to set some kind of a sentinel value, like touch $CHARM_DIR/relation-lock, and check for the presence of that sentinel to determine of the value should be updated. | 16:44 |
| lazyPower | thats one method, but this makes me pause to ask "Why are you exposing a configuration value that comes from a third party? Shouldn't this by definition be opinionated in the point its nto exposed to the user and only updated via relationship?. | 16:45 |
| themonk | lazyPower: my problem is elation related variables and config related variables both are in same config file template :( i cant change it | 16:48 |
| themonk | lazyPower: about the sentinel value method, in this way after relation happen, i cant change config values ryt | 16:49 |
| lazyPower | themonk: you're giving me a catch 22 that your config variable is overriding the incoming value from a remote service. You either need to unexpose teh configuration variable, or change the relationship variable. it's 'OK' to be opinionated in charm development. | 16:51 |
| lazyPower | we encourage it, as its spoon feeding the end user best practices with their deployments. | 16:51 |
| lazyPower | but without further context, i cant comment - if you have a branch to look at i'll be more than happy to review whats happening and make a proper suggestion. | 16:52 |
| james_w` | themonk: I think you need to store the relation variables in a file in relation-changed | 16:53 |
| james_w` | and then generate the template using that file and the config values | 16:53 |
| james_w` | and you can do that from both relation-changed and config-changed, and they both have all the values that they need | 16:54 |
| james_w` | unless you are talking about the relation value being for the same thing as one of the config values | 16:54 |
| james_w` | in which case it will be more work to get the behaviour you want | 16:55 |
| themonk | lazyPower: i cant show my code right now :( | 16:55 |
| themonk | james_w`: i concidered this option too like make a json file :) | 16:58 |
| Egoist | Hello | 16:58 |
| Egoist | i have a question, where is store information what hook is executed after start hook? | 16:59 |
| === salgado_ is now known as salgado | ||
| lazyPower | Egoist: depends on the next action that is triggered. The typical hook flow during deployment: install => config-changed => start -- afterwords, its dependent on the action that is taken. It could be any *-relation-joined, config-changed, or upgrade-charm hooks that are fired. | 17:04 |
| lazyPower | or stop, if the service is destroyed. | 17:04 |
| Egoist | is there any imformation stored about what happend when you deploy more than 1 instance? | 17:09 |
| Egoist | i mean something like this: | 17:09 |
| Egoist | juju deploy mysql -n 3 | 17:09 |
| lazyPower | Egoist: after the traditional deployment hook sequence is executed, the peer-relationship hook will be triggered on all 3 instances. | 17:10 |
| Egoist | is it possible to make changes in peer-relationship? | 17:11 |
| lazyPower | can you refine that a bit more? as 'make changes' is kind of open and broad, and could mean many things. | 17:11 |
| Egoist | i don't want to make relationship beetween this mysql instances that I mentioned earlier | 17:14 |
| Egoist | I just want to have 3 separate instance | 17:14 |
| lazyPower | Egoist: to that end, it would be better to deploy them as juju deploy mysql "alias" | 17:15 |
| lazyPower | they then become independent service units, without a peering relationship. | 17:15 |
| Egoist | ok, i get it | 17:16 |
| lazyPower | and can be independently scaled/managed | 17:16 |
| Egoist | may I ask one more question | 17:16 |
| lazyPower | sure | 17:16 |
| Egoist | why juju sometimes don't have relation in list, even if relation-set was executed? Is it possible that relation-set is return false because few instances try to executed this command in the same time? | 17:17 |
| lazyPower | Egoist: do you have an example? i'm not sure what you're saying. | 17:20 |
| lazyPower | s/saying/asking/ | 17:20 |
| Egoist | when i want to try make a relation beetwen two instance, and each instance execute relation-get and it's return nothing | 17:24 |
| gQuigs | I'm just curious and couldn't find backstory on the decision to move from lp to github, anyone know where it took place? | 17:29 |
| marcoceppi | gQuigs: for juju-core? | 17:29 |
| gQuigs | marcoceppi: yup | 17:30 |
| lazyPower | Egoist: relation-get returning nothing means it wasn't set on the other side. During which hook is this call being executed? It should be the relationship-changed hook and not the joined, as joined is pre-setup work like archiving an existing database provider or installing pre-req packages. | 17:30 |
| marcoceppi | gQuigs: it's been decided for a few months. Discussion would have happened on juju-dev mailing list | 17:30 |
| gQuigs | marcoceppi: yea, I've been looking over the mailing list... went back to oct 2013 | 17:31 |
| Egoist | ohh, ok, i get it. Thank you very much | 17:32 |
| Egoist | :_ | 17:32 |
| Egoist | :) | 17:32 |
| marcoceppi | gQuigs: ask in #juju-dev they should be able to enlighten | 17:32 |
| gQuigs | marcoceppi: ok, thanks! | 17:32 |
| jcastro | ... and all my stuff is stuck on pending today | 17:38 |
| lazyPower | jcastro: stub ran into an issue last night with UFW blocking his deployments. | 17:41 |
| lazyPower | have you disabled UFW to validate that's not the over-arching issue? his was specific to 1.18.4 i believe, as i'm on 1.19.x and haven't seen teh same behavior. | 17:41 |
| jcastro | my ufw is off | 17:41 |
| khuss | lazyPower: I've filed a bug regarding the ceph issue we are seeing - https://bugs.launchpad.net/juju-core/+bug/1326466 | 17:42 |
| _mup_ | Bug #1326466: Openstack install failing because of outdated Ceph charm? <juju-core:New> <https://launchpad.net/bugs/1326466> | 17:42 |
| lazyPower | khuss: brilliant. thanks for the bug report! | 17:43 |
| lazyPower | jcastro: boo :( | 17:43 |
| ahasenack | $ charm get ntp | 17:55 |
| ahasenack | (...) | 17:55 |
| ahasenack | bzr: ERROR: Transport operation not possible: http does not support mkdir() | 17:55 |
| ahasenack | really, no anonymous charm get? | 17:55 |
| jcastro | git clone https://github.com/charms/ntp.git | 17:59 |
| jcastro | :) | 17:59 |
| jcastro | ahasenack, that sucks though, can you file a bug on charm-tools? | 17:59 |
| ahasenack | ok | 18:00 |
| ahasenack | jcastro: I would need the ntp charm to be available on trusty, what are the steps to get that done? | 18:02 |
| jcastro | ahasenack, currently, ask marcoceppi to push it to trusty | 18:03 |
| ahasenack | marcoceppi: hi, are you in a position to do that? ^^^ | 18:04 |
| marcoceppi | ahasenack: have you tested it on trusty? | 18:05 |
| ahasenack | about to | 18:06 |
| ahasenack | hitting issues with charm get, and now a overzealous firewall that doesn't allow connections to bazaar.lp.net | 18:06 |
| ahasenack | marcoceppi: I can give both (ntp and ntpmaster) a shot and report back, then you can promote them to trusty if no blockers are found? Is that more or less the procedure? | 18:07 |
| marcoceppi | writing tests for it is the fastest way to get it in to trusty | 18:07 |
| ahasenack | oh, that | 18:07 |
| * marcoceppi looks at the charm | 18:07 | |
| ahasenack | I'd say it's a bit lacking in the unit test area | 18:09 |
| jcastro | ahasenack, yeah that's why we haven't mass-moved the charm store to trusty | 18:28 |
| ahasenack | still, it says "recommended" in the charm store ;) | 18:28 |
| jcastro | precise is recommended | 18:30 |
| nooky | Hello, I've a question about the Bundle import using charms that are local, when I try to import the bundle I'm getting errors on invalid configs. For example: An error occurred while deploying the bundle: Invalid config charm precise/true-node-app-1 app_url=https://github.com/zarffg/prototype Invalid config charm precise/true-node-app-1 app_name=prototype Invalid config charm precise/true-node-app-1 app_port=3000 | 18:34 |
| === roadmr is now known as roadmr_afk | ||
| jcastro | nooky, can you pastebin your bundle somewhere? | 19:22 |
| nooky | jcastro: yes, wait a minute | 19:23 |
| === roadmr_afk is now known as roadmr | ||
| nooky | jcastro: http://pastebin.com/PPAdNe8P | 19:30 |
| jcastro | I have " " around my charm: local/blah stuff | 19:32 |
| jcastro | I don't think that's your problem though | 19:33 |
| jcastro | marcoceppi, ideas? ^ | 19:33 |
| nooky | jcastro: yes, I've tried with double quotes around the charm definition, but isn't working | 19:33 |
| rick_h_ | nooky: what is 'bundle import'? How are you importing? | 19:33 |
| nooky | rick_h_: via juju gui | 19:34 |
| rick_h_ | nooky: the gui doesn't support deploying bundles with local charms currently | 19:34 |
| nooky | oh | 19:34 |
| nooky | rick_h_: juju deployer ? | 19:35 |
| nooky | or quickstart ? | 19:35 |
| rick_h_ | nooky: yep | 19:35 |
| nooky | fine | 19:35 |
| nooky | let me check | 19:35 |
| rick_h_ | sorry, juju has an issue we need to correct for that to work properly from the GUI at the moment | 19:35 |
| nooky | rick_h_: I've tried to deploy via juju-deployer and didn't work, the errors are the same that importing using juju-gui | 19:52 |
| rick_h_ | nooky: ok, well at least now have an idea that it's something that will work once the issue is worked out. | 19:53 |
| nooky | rick_h_: i need to use double quotes to charm and options definition? | 19:53 |
| rick_h_ | nooky: can try it. Not sure. It fussed about all three config options. Stuff like port shouldn't need the quotes, but it complained about that as well. | 19:55 |
| rick_h_ | does those cross refence to the charm itself exactly? | 19:56 |
| nooky | rick_h_: look at this: https://bugs.launchpad.net/juju-deployer/+bug/1297940 | 19:57 |
| _mup_ | Bug #1297940: deployer does not support a local: prefixed charm url. <api> <charms> <state-server> <juju-core:Triaged> <juju-deployer:Confirmed for hatch> <https://launchpad.net/bugs/1297940> | 19:57 |
| hazmat | nooky, its a different syntax | 20:00 |
| hazmat | nooky, that deployer file you pasted is wrong in a few ways | 20:01 |
| hazmat | nooky, s/charm: local:precise/true-varnish-0/charm: true-varnish | 20:01 |
| hazmat | you can also point to github repos as the charm branch | 20:01 |
| nooky | hazmat: ok, thanks, I'll try to replace the charm definition in the bundle file | 20:03 |
| hazmat | nooky, charm: <charm_name> should do the trick | 20:03 |
| nooky | great | 20:03 |
| nooky | hazmat: using the way charm: <charm_name>, I'm getting this error, 2014-06-04 20:06:58 Invalid charm specification true-varnish | 20:08 |
| nooky | hazmat: Is possible that the errors are because I'm using a new environment and not the environment where I've exported the Bundle? | 20:16 |
| hazmat | nooky, well with local charms you have to access to them... locally there not in the bundle | 20:17 |
| hazmat | gui exports of local charms are not functional | 20:17 |
| hazmat | nooky, i'd also toss a series: precise right under envExport | 20:18 |
| hazmat | you can specify branch: https://github.com/name/repo.git for the charms to pull them straight from vcs | 20:19 |
| nooky | hazmat: ok ok | 20:19 |
| nooky | so, can i define in this way? charm: https://github.com/name/repo.git | 20:20 |
| marcoceppi | nooky: not quite | 20:21 |
| marcoceppi | you would have to change charm to branch | 20:21 |
| nooky | marcoceppi: ok, thanks | 20:21 |
| * hazmat signs off | 20:41 | |
| === vladk is now known as vladk|offline | ||
| === menno0-afk is now known as menn0 | ||
| l1l | a mysql charm that sets up blank databases with no tables | 21:03 |
| === wallyworld is now known as Guest56344 | ||
| === wallyworld is now known as Guest68975 | ||
| === sebas538_ is now known as sebas5384 | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!