=== freeflying_away is now known as freeflying
cjohnstonDoes anyone have any experience with using salt in a charm?00:52
sidneicjohnston: ping noodles775 in the morning01:14
sidneicjohnston: though he (and me and hazmat) favours ansible01:14
cjohnstonsidnei: ya. was hoping for someone tonight..01:14
sidneilet me see if i can find you an example01:15
hazmatcjohnston, there's support for it in charmhelpers01:15
cjohnstonhazmat: right.. I'm having a specific issue, but I know that not many people have experience with it01:15
hazmatcjohnston, traceback?01:16
hazmatcjohnston, i'm happy to take a look, but no guarantees. i haven't used the combo, though i'm familiar with both.01:17
cjohnstonhazmat: http://paste.ubuntu.com/6440481/  I believe the issue is with my attempt at getting relation info.01:17
cjohnstonI'm trying to get the postgres host, grains.get('postgres:host'),  is what I'm using01:18
hazmatcjohnston, hmm.. it looks something wrong in the template expression01:19
hazmatcjohnston, do you have a minimal file that reproduces ?01:20
hazmatcjohnston, one that you can share that reproduces?01:20
cjohnstonits supposed to be producing django DATABASES = {}01:21
cjohnstonone sec01:21
cjohnstonhazmat: http://paste.ubuntu.com/6440506/01:24
hazmatcjohnston, the sls file for it?01:26
cjohnstonI think I may have just figured something out... hrm.. lemme see what it does, if not I'll paste01:27
hazmatcjohnston, any luck?01:35
cjohnstonwell, the traceback is gone, but I have 'None' instead of real data01:38
hazmatcjohnston, are you using the charm-helpers salt support? ie. http://bazaar.launchpad.net/~charm-helpers/charm-helpers/devel/view/head:/charmhelpers/contrib/saltstack/__init__.py01:40
cjohnstonhazmat: http://paste.ubuntu.com/6440556/01:41
hazmatcjohnston, so the relation data isn't there yet, which hook is that being run in?01:47
cjohnstondb-relation-joined and db-relation-changed... if I do relation-get it returns the correct data01:48
cjohnstonhazmat: is ('postgres:host') correct? should postgres be something else maybe?02:03
hazmatcjohnston, the grains with the data  are in /etc/salt/grains ..02:05
hazmatcjohnston, it looks like you need a prefix from http://bazaar.launchpad.net/~charm-helpers/charm-helpers/devel/view/head:/charmhelpers/contrib/templating/contexts.py#L3402:06
=== gary_poster is now known as gary_poster|away
=== thumper is now known as thumper-afk
=== freeflying is now known as freeflying_away
=== jono is now known as ubuntu-goldfish
=== freeflying_away is now known as freeflying
=== CyberJacob|Away is now known as CyberJacob
=== thumper-afk is now known as thumper
InformatiQi'm working on a trac charm using ansible07:54
noodles775InformatiQ: Excellent! Just ping with any questions... I guess you saw that the extra ansible support landed yesterday in charm-helpers.07:54
InformatiQdoes anyone have any pointer how the juju_state_to_yaml outputr looks like07:55
InformatiQnoodles775: i was waiting for it to start writing my code ;)07:55
InformatiQI have been using ansible for a while now and I can see a lot of potential for combining it with juju07:56
InformatiQalthough i still struggle a bit with juju concepts07:56
noodles775Yep - I think the combination has lots of potential to simplify charms too (and make them much more flexible out-of-the-box).07:56
noodles775InformatiQ: so do you want a paste of an example yaml file that's outputted by the function (I can do that, just wondering why you need it, normally you wouldn't need the file itself, as it's just used to provide context for your templates). Ah, probably the key names...07:58
noodles775cjohnston: Did you find the data you were looking for? FWIW, I'd recommend checking the actual grains written to the file in /etc/salt/grains as hazmat suggested (or alternatively using a pdb when running your hook in the debug-hook window) to confirm the actual keys, but they should be "reln_type:reln_key" (where reln_type is just os.environ.get('JUJU_RELATION_ID'))08:00
noodles775cjohnston: er, os.environ.get('JUJU_RELATION'), sorry (ie. output of charmhelpers.core.hookenv.relation_type())08:00
=== rogpeppe1 is now known as rogpeppe
InformatiQnoodles775: yes I need that file to know what are the  vars that are available08:16
InformatiQnoodles775: i would appreciate if you could paste one for me or just tell me how to generate it08:16
noodles775InformatiQ: Cool, so in the long run it'd be best to look at the one generated automatically by your charm, as it is just a json dump of the charm configuration (which is very dependent on the charm you're using). But as an example, if I was working with a charm which had these options in the config.yaml:08:26
noodles775then the file contents are just a dump of the charms config, eg: http://paste.ubuntu.com/6441675/08:27
noodles775The juju_state_to_yaml helper also adds 'charm_dir', 'local_unit', as well as relationship data (which is only present once those relationships are added).08:28
noodles775(for all the details, see http://bazaar.launchpad.net/~charm-helpers/charm-helpers/devel/view/head:/charmhelpers/contrib/templating/contexts.py ), but otherwise, let me know when you've got a simple install hook which just installs ansible, and I'll show you how you can inspect the real file yourself.08:29
InformatiQnoodles775: are you the author of the blog micknelson.wordpress.com08:33
noodles775InformatiQ: yep, you can blame me for any errors there :)08:34
InformatiQnoodles775: just that i left a comment and it is still waiting moderation ;)08:34
InformatiQnoodles775: so I followed your example and have that hooks.py and install/start/stop/etc and links to it08:35
noodles775InformatiQ: It should be there, I approved it 15mins ago or so.08:35
InformatiQnow I am working on an ansible playbook08:35
noodles775InformatiQ: Great. Just start with something really simple (ie. something that has a single task tagged with 'install'), then we can start the deploy/debug-hook cycle so you can see how to debug and test as you go.08:36
noodles775s/something that/a playbook that/08:36
InformatiQnoodles775: ok should have the needed stuff there08:47
InformatiQnoodles775: so what is the path to testing the hook without really deploying?08:48
noodles775InformatiQ: So I tend to write unit-tests to test things like "calling the install hook installs ansible", but there's not a lot more you could unit-test (perhaps with ansible, we could add some helpers that ensure your playbook is formatted correctly etc.). When developing your charm though, you really want to be deploying to test it. Do you have an environment bootstrapped?08:50
InformatiQnoodles775: yes I have a local env08:51
noodles775Great. So you can try deploying your charm (if you can push your branch somewhere, I can follow along/help a bit more).08:52
noodles775InformatiQ: hah - thanks for the flowers :-) (the tweet)08:57
InformatiQnoodles775: pushed current code to https://github.com/InformatiQ/charm-trac09:03
InformatiQnoodles775: i got 2013-11-19 09:01:01 ERROR juju.worker.uniter uniter.go:350 hook failed: fork/exec /var/lib/juju/agents/unit-trac-0/charm/hooks/install: exec format error09:03
noodles775InformatiQ: Perfect, let's find out why...09:03
* noodles775 grabs the charm09:04
noodles775InformatiQ: Ok, I'm guessing the error is that we've not yet imported charmhelpers (nor is it yet available in the charm - it's not included automatically). But let's actually confirm that the right way. In a separate terminal, run `juju debug-hooks trac/0`09:08
InformatiQnoodles775: ok that dropped me in a shell on the new machine09:09
noodles775Then in your original terminal, do `juju resolved --retry trac/0`09:10
noodles775When you switch back to the debug-hooks window, it should now be ready to run the install hook.09:10
noodles775Run `hooks/install` to see the error.09:11
InformatiQnoodles775: syntax error at line 409:12
noodles775Yep, let's back out a bit (it was just worth seeing how to use debug-hooks). Basically, hooks/install is currently running your hooks/hooks.py as a bash script.09:13
noodles775So edit the file (right there on the unit, so we can iterate quickly)09:13
InformatiQyeah got that and now add the hash bang for python?09:14
noodles775Yep, then you'll see the error related to charmhelpers being missing.09:14
* noodles775 looks up the latest and greatest way to include those in your charm.09:14
InformatiQyup charmhelpers not defined09:15
=== freeflying is now known as freeflying_away
noodles775jamespage: hi! I'm just looking for the best way to pull charmhelpers into a charm (to help InformatiQ). I notice in your swift-proxy charm you've got a charm-helpers.yaml defining the import, and in the Makefile the sync target calls charm-helper-sync... where does charm-helper-sync come from?09:25
* noodles775 normally does it with a much uglier Makefile target.09:26
InformatiQthis is looking a bit complicated for me09:28
* InformatiQ is a code monkey not a developer09:28
noodles775InformatiQ: hah. New things are always tricky at first. We can do it a simpler way. Just do `bzr branch lp:charm-helpers /tmp/charm-helpers && cp -R /tmp/charm-helpers/charmhelpers hooks`09:31
noodles775InformatiQ: that'll put the current charmhelpers python library in your hooks directory so we can use it.09:31
noodles775InformatiQ: oh, and if it's not clear, this is on your development machine, you can exit out of the debug-hooks.09:32
InformatiQnoodles775: ok so now I need to redeploy?09:36
=== freeflying_away is now known as freeflying
noodles775InformatiQ: You can just upgrade the charm too `juju upgrade-charm trac --repository....`09:37
* noodles775 is just testing the updated hooks.py before pasting it.09:38
noodles775InformatiQ: so this is what your hooks.py should look like - I'll update the blogpost with the imports and the main section, note you also had site.yaml rather than sites.yaml too: http://paste.ubuntu.com/6441930/09:48
noodles775InformatiQ: also, in your playbooks/sites.yaml, you've got "lates" instead of "latest".09:50
InformatiQnoodles775: cool things are moving ahead09:56
noodles775Yep. I'm still just looking at an issue I'm seeing (not an issue of yours, but with the ansible support that I've added). So don't worry if it gets stuck. (It's worthwhile to me because I'm keen to iron out issues in the ansible support :-) ).09:58
InformatiQwhere should the playbook dir reside? in the hooks ?09:59
noodles775It's fine where you've got it.10:00
InformatiQi am getting file not found10:00
noodles775Did you fix the "playbooks/site.yaml" to "playbook/sites.yaml"?10:00
noodles775(in hooks/hooks.py, that is)10:01
InformatiQyes i have10:01
InformatiQhttp://paste.ubuntu.com/6441986/ that is the traceback10:02
noodles775InformatiQ: hrm - that's not related to your playbook. Checking the line that's failing from your tracebook says that it's trying to run `juju-log` and not finding it. But I don't know why that would be (ie. why a juju unit wouldn't have juju-log available).10:06
InformatiQjuju-loh is not even available on my juju host10:13
InformatiQis it deprecated now?10:13
InformatiQi am using the ppa version of juju10:14
InformatiQon saucy10:15
noodles775No, it's still very much a part of juju. I'm using the same ppa (on saucy), and this is the output I see on the trac unit: http://paste.ubuntu.com/6442038/10:15
noodles775InformatiQ: I'm not sure how you ended up with a juju unit without juju-log, but it might be worth redeploying...10:16
InformatiQnoodles775: just sshed into one of the successfully deployed machine and juju-log cmd is not available too10:19
noodles775Ahh - hangon.10:19
InformatiQalthough actually the install hook for that service had juju-log in there10:20
noodles775InformatiQ: Cool, confirmed: it's not an installed command available whenever you log in. But it is available when you're running a hook. So first, make sure you're in a `juju debug-hooks trac/0` session (even if it's not currently within a hook)10:22
InformatiQnoodles775: juju-log is supposed to be here /var/lib/juju/tools/
InformatiQand that is probably not in the path10:22
InformatiQnoodles775: i guess you either extend PATH in the charmhelpers/core/hookenv.py or explicutly use the full path for juju-log10:23
InformatiQbecause I am in juju debug-hooks for that service10:24
noodles775InformatiQ: you won't need to. It'll be available when you're actually running a hook. Great (that you're in the debug-hooks session), we just need to trigger a hook first. Try:10:24
noodles775InformatiQ: back in your other terminal, run `juju set trac tracadmin_user=foo` (it'll just cause the config-changed hook to be triggered)10:25
noodles775InformatiQ: when you switch back to your debug-hooks terminal, you should see it's updated and juju-log will be on the path.10:25
InformatiQwell that didn't help either but I set it manually10:27
InformatiQand now a new failure related to config-get i guess because it doesnot have the needed configs10:28
InformatiQi guess i now cleanup, fix sources push to git and retry10:28
noodles775InformatiQ: Yeah - I'm still investigating something with the ansible support, but I'll create a pull-request demoing the stubbed charm once it's working. Thanks for your patience :)10:30
InformatiQnoodles775: ok, i guess that was a good drill i have updated the charm on github10:32
InformatiQlet me know when it is ready to proceed10:32
InformatiQi need to get back to my dayjob now10:33
noodles775Great, will do. Enjoy :-)10:33
davecheney^ sorry, it has the wrong mime type10:36
davecheneyi'll have to fix my client10:36
davecheneyignore, wrong chan10:36
jamespagenoodles775, its in charm-helpers11:07
jamespage(yeah - I know thats a bit sucky)11:08
jamespagenoodles775, http://paste.ubuntu.com/6442249/11:08
noodles775Thanks jamespage11:08
* noodles775 wonders if a simple Makefile might provide a good bootstrap to pull that one file from the branch, sync charmhelpers, and create a stubbed (but working) basic charm.11:11
noodles775InformatiQ: The issue I thought I was looking out was a typo on my part (I had sites.yaml, rather than sites.yml). Here's an example of your charm being deployed: http://paste.ubuntu.com/6442336/11:38
noodles775InformatiQ: What you had in your branch was fine as is, all I needed to do was remove the unused hooks: https://github.com/InformatiQ/charm-trac/pull/111:39
* noodles775 -> lunch11:39
AskUbuntujujud hangs when connecting to the mongo,maybe tls handshake error | http://askubuntu.com/q/37932511:53
jamespagenoodles775, ooo - now that is an idea12:29
InformatiQnoodles775: great thanks12:33
InformatiQnow I need to figure out what to do about those db relations12:33
* InformatiQ wonders what subordinates are12:33
InformatiQto the docs12:33
InformatiQnoodles775: one more thing related to the state_to_yaml what you pasted earlier had the config vars, but what about relation vars?12:37
noodles775InformatiQ: they'll also be in the file once you add a relation hook and it's called (the helper updates the vars file based on the current config and current relation just before running the playbook with the tag)12:56
=== gary_poster|away is now known as gary_poster
cjohnstonnoodles775: I finally figured it out ;-)13:15
noodles775cjohnston: great :-) Let me know if it's something that could have been avoided by better docstrings in the charmhelper modules.13:16
cjohnstonnoodles775: it was figuring out grains.get('db:database')  (the 'db' part), I didn't find anything that said what it should have been13:18
noodles775cjohnston: Right - I'll update the docstring to make that explicit.13:21
gnuoyif a unit dies unexpectedly does that trigger cluster relation departed on the other units in the same server ? I thought it would but I don't seem to be seeing that13:34
hazmatgnuoy, it used to with pyjuju.. in juju-core the signaling is explicit after the admin does juju remove-unit.13:57
gnuoyhazmat, ah ok, thanks13:57
InformatiQI have a " agent-state-info: 'hook failed: "install"'"14:03
InformatiQhow do i get it fixed after i have fixed my hook14:04
InformatiQi did try juju resolved14:05
InformatiQbut didn't get that fixed14:05
InformatiQok aparantly me being in debug hooks prevented it from continuing14:06
InformatiQall good now14:06
SuperMattI'm having trouble using this: https://juju.ubuntu.com/docs/howto-node.html with my own node app. I don't particularly care for the mongodb integration, so how could I tweak the charm for what I need?15:18
marcoceppihey SuperMatt, so you can fork the charm, using charm-tools (available from ppa:juju/stable), just run juju charm get node-app, edit the metadata.yaml file to include additional interfaces you wish to communicate with, then write the hooks for those relations15:28
SuperMattthanks :)15:28
SuperMattI think I discovered why the charm hasn't really been working for me15:29
marcoceppiSuperMatt: We do have people working on the node-app charm to make it more robust, but that's a way for you to patch in the mean time15:29
SuperMattthere's a lot of stuff in the config.yaml that the tut doesn't really mention15:29
marcoceppiSuperMatt: Must have changed since the tut was written15:30
marcoceppiSuperMatt: I'll also include https://juju.ubuntu.com/docs/charms-deploying.html#local in case you didn't already know how to deploy a charm from a local repo15:30
SuperMattmarcoceppi: if you don't mind, I'm going to just have a bash at tweaking this thing, and I'll let you know what I discover :)15:31
marcoceppiSuperMatt: sure! if your changes can benefit the larger community, feel free to submit a merge req back in to the store15:32
SuperMattwell, I don't know about that ;)15:32
SuperMattI imagine it's a good idea to have the charm allow you to pick if you want to have mongodb, rather than it being required15:32
marcoceppiSuperMatt: you can submit for a review anywasys :_15:32
SuperMattI'm kinda just learning about juju right now15:33
SuperMattso it's all a bit up in the air for me15:33
SuperMattif I manage to do something cool I'll merge back15:33
SuperMattthanks for the help though, I didn't realise you could simple pull out a charm and modify it15:34
SuperMattI actually typed :q there15:34
SuperMattmarcoceppi: I've just spotted exactly what I needed to change to make the installer work for me. Thanks a lot15:42
marcoceppiSuperMatt: NP! Glad I could help15:42
SuperMattall right, here goes nothing15:47
=== Beret- is now known as Beret
=== adam_g is now known as adam_g_afk
=== jamespag` is now known as jamespage
noodles775jamespage: trivial one-liner if you've a few secs: https://code.launchpad.net/~michael.nelson/charm-helpers/remove-saltstack-import-from-ansible-support/+merge/19581716:23
jaywinkhi .. anyone with knowledge whether on azure "force-image-name" config can be used to use an image captured into personal gallery? I cannot really find image names..16:25
jaywinkand I'm interested in freezing an image to use for deployments anyhow16:25
=== CyberJacob is now known as CyberJacob|Away
InformatiQnoodles775: according to your patch https://code.launchpad.net/~michael.nelson/charm-helpers/ansible-tags/+merge/194324 line 201 + ("{relation_type}{namespace_separator}{key}".format(16:49
InformatiQnoodles775: the relation vars are prefixed with relation_type16:49
InformatiQhow do i get the relationtype?16:49
InformatiQso i can formulate the var name16:49
InformatiQnoodles775: or how can i print the vars.yml so I can inspect it16:51
SuperMattmarcoceppi: my juju experiments are going very well now. Thank you for your help17:02
InformatiQnoodles775: ok found out what type it is from env var17:02
marcoceppiSuperMatt: awesome, let us know if you have any other questions :)17:02
SuperMattsure thing17:02
SuperMattI think I'm going to stay in here17:02
InformatiQbut ansible complains about variable not defined17:02
SuperMattI think learning juju, lxc, cgroups and maybe a little openstack are going to make me indispensible in the future17:03
jamespagenoodles775, merged17:04
jamespage(implicit approval)17:04
InformatiQSuperMatt: indeed17:05
=== SpamapS_ is now known as SpamapS
InformatiQnoodles775: it seems ansible does not like vars with '-' as in the case with private-address so simply also key.replace('-','_') as you did for the relation_type17:36
=== _jmp__ is now known as _jmp_
InformatiQnoodles775: check my git repo hooks/charmhelpers/contrib/templating/contexts.py to see the small chnage needed18:25
=== CyberJacob|Away is now known as CyberJacob
InformatiQhey guys, some advice needed19:41
InformatiQworking on a trac charm19:41
InformatiQshould i make mysql an optional db ?19:41
InformatiQi was thinking to make sqlite default backend and make mysql optional19:42
jcastroInformatiQ, yes, that sounds great19:48
jcastrothat's what the etherpadlite charm does19:48
jcastrothat way if someone wants to run "small" on one instance they can do so19:48
jcastroand then expand out to mysql later19:48
InformatiQjcastro: good to see someone up19:48
InformatiQjcastro: the proble is that trac is not quite kind when it comes to migrating dbs19:49
jcastroI would leave a note in your README though, reminding people that if they add the mysql relation that their data will not magically be migrated to the new DB19:49
jcastroyeah so I would just mention that in the README19:50
InformatiQjcastro: good isea19:50
jcastromaybe link to db migration docs if trac has them or something19:50
InformatiQjcastro: so hooks would be19:50
InformatiQinstall to get all installed19:51
InformatiQconfig-changed to init the env and db using sqlite19:51
InformatiQif relation added19:51
InformatiQthen keep the sqlite db and reconfigure to point to mysql and then people need to do the work to get it migrated19:51
InformatiQjcastro: what do you think? (my first charm))19:52
jcastroyeah, sec, I am looking at http://bazaar.launchpad.net/~charmers/charms/precise/etherpad-lite/trunk/view/head:/hooks/hooks.py19:52
jcastroI think that would be in relation changed?19:53
jcastromarcoceppi,  is that right?19:53
InformatiQjcastro: yeah that would be db-relation-changed19:54
jcastrooh interesting, I didn't know trac did postgresql too19:54
marcoceppiInformatiQ: jcastro: sure, that's one way to approach it19:55
jcastro(just searching for other charms that support multiple DBs)19:55
marcoceppijcastro: typically, you'd make sure the data migrated between sets19:57
InformatiQhei guys, so I start a new project and start creatingthe infra with juju say a wordpress + mysql19:57
InformatiQthen i need to add plugins and a new theme to wordpress and whatever19:57
InformatiQsoe of these changes are on filesystem19:57
InformatiQnow when do add-unit wordpress that won't take my chnages19:58
marcoceppiInformatiQ: check the readme, there is a way to make that happen19:58
marcoceppiInformatiQ: you either need to place your plugins and themes in a repository OR use an NFS charm to share the files across a mount19:59
InformatiQmarcoceppi: well that is a general case notspeciic to wordpress19:59
marcoceppiInformatiQ: it's what teh wordpress charm does20:00
InformatiQmainly about the lifetime and repeatability of a juju infra20:00
InformatiQi am sysadmin20:00
marcoceppiInformatiQ: what's your question?20:00
marcoceppii'm not quite grasping what you're trying to ask20:01
InformatiQi use ansible to deploy services, and whenver i want to change my infra i update the ansible scripts and redeploy20:01
sarnoldInformatiQ: perhaps you're looking for juju subordinate charms to deploy different wordpress plugins?20:02
InformatiQI am trying to understand how does juju handle changes to infra?20:02
jcastroso you could fork the wordpress charm, make the changes you want, and deploy20:03
jcastrohowever, juju has a concept of subordinate charms20:03
jcastrowhich "bolt on" to existing charms20:03
InformatiQjcastro: yeah i am trying to understand that now20:04
jcastroso you could have "wordpress" and say "all-my-custom stuff charm"20:04
jcastrohowever with this particular charm marco made it so you could do plugins and custom things on disk without having to do that20:04
jcastroyou basically deploy the NFS charm as a subordinate of wordpress20:04
jcastroand then when you add unit of wordpress it'll also pull in nfs and have the right things on disk for the new unit20:05
InformatiQso a subordinate sticks to the service and get redeployed whenver a unit is added20:07
jcastrothe relationship is made between the services, not the machines20:08
InformatiQjcastro: yup got that20:08
jcastroso any new unit you add will be like the others20:08
jcastrothe "single mode and the scale out" section explains the NFS bit with the wordpress charm btw20:09
jcastro(sorry we're in the middle of a team call right now, trying to respond as fast as I can)20:10
InformatiQjcastro: oh no worries i got enough to read already20:11
jcastroif we're not responsive over the next 2 days it's because we're doing a developer conference, but feel free to post on the mailing list!20:12
InformatiQjcastro: one last question20:21
InformatiQin the case i want to add a monitoring agent to all my machines, then that is not a subordinate20:22
InformatiQand add-unit will not help get that agent to all machines right?20:22
jcastrook so let's say you have newrelic20:23
jcastrowe made that a subordinate so that anything you relate to newrelic will automatically get the agent deployed20:24
jcastrobut correct, if you don't have a relationship with the agent and the service on the machine then juju won't help in that case20:24
jcastrobut we want to get as many monitoring agents in the charm store as possible so that you can just relate them to whatever you want to monitor20:25
jcastrothe same thing would apply to say, backup agents too20:26
InformatiQjcastro: so the monitoring agent gets to be a subordinate of a service hmmm20:27
InformatiQmakes sense20:27
jcastrowhat agent do you use btw?20:28
jcastrooh, we have that!20:28
InformatiQi saw there is an agent already there20:28
InformatiQbut i am trying to get beyond just using things20:28
* jcastro nods20:28
InformatiQI am also thinking in terms of multiple services per machine20:30
InformatiQso that means what when each service has an agent attached to it20:30
=== mwhudson- is now known as mwhudson
jcastroarosales, gary_poster would like us to move bundle workflows so he can attend it, I was thinking swapping it out with automated charm testing.21:00
jcastrothis is for thursday21:00
gary_posterthank you for considering jcastro21:01
jcastrogary_poster, for the rest of the stuff you asked about we only have 2 "tracks" and we have to share with the rest of cloud/server, so that unfortunately is the case21:01
gary_posterjcastro, ack, figured it might be something like that21:02
arosalesjcastro, +121:02
jcastromarcoceppi, ok automated charm testing is an hour earlier than before on thursday21:05
marcoceppi jcastroack21:23
arosalesmarcoceppi, rick_h_ had a question on charm testing urls21:49
arosalesspecifically https://jenkins.qa.ubuntu.com/job/precise-openstack-charm-mysql  is 404'ing21:50
arosalesmarcoceppi, afik those URLs ~should~ still be valid, but wanted to confirm with you.21:50
arosalesmarcoceppi, I think we are not seeing testing results at jujucharms.com as some testing aren't running21:52
arosalesie https://jujucharms.com/fullscreen/search/precise/mysql-29/?text=mysql21:52
arosalesno test results21:52
arosaleshas test results21:52
unbreak-itWould this be a good place to get help on deploying juju on aws?21:56
marcoceppiunbreak-it: it would21:59
unbreak-itI can run `juju bootstrap` just fine, and an instance shows up in my EC2 management console. But when I run `juju status -v` it locks up after `INFO juju.state open.go:68 opening state; mongo addresses: ["ec2-54-226-186-205.compute-1.amazonaws.com:37017"]; entity ""`22:01
unbreak-itAny ideas what the issue could be?22:04
arosalesunbreak-it, can you pastebin.ubuntu.com the output of "juju --debug status"22:07
arosalesunbreak-it, also what juju version are you running?22:07
arosalesjuju --version22:07
=== thumper is now known as thumper-afk
=== bradm_ is now known as bradm
=== freeflying is now known as freeflying_away
=== CyberJacob is now known as CyberJacob|Away

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!