[00:00] <arosales> irossi, for upgrading from .7 to 1.x I am not sure of the steps needed
[00:19] <hazmat> irossi, there is no upgrade path atm between the two for live migration, you can export and import the topology (config, services, machines, relations) with something like juju-deployer or the gui (hotkey shift-D), but its a fresh start effectively.
[09:06] <rogpeppe> anyone know of a decent way of enumerating all the charms in the charm store? i did a screenscrape of the charm website ages ago and got 90, but i'd like to get as many as possible.
[09:07] <rogpeppe> currently my best guess is going through https://code.launchpad.net/charms and looking for all lp:charms/xxx branches, but there's surely a better way
[09:24] <axw> rogpeppe: charm-tool? "charm list" lists all the charm branches in https://code.launchpad.net/charms
[09:25] <axw> you'd need to clean them a bit
[09:25] <rogpeppe> axw: hmm, i didn't know about the charm tool
[09:25] <axw> rogpeppe: it's basically just scripting what you just said anyway
[09:26] <rogpeppe> axw: yeah, i've just done that anyway, but it would be nice to be able to make it automatic
[09:27] <rogpeppe> axw: where did you find the charm tool?
[09:27] <axw> rogpeppe: https://launchpad.net/charm-tools
[10:22] <geme> marcocepp1, picking up from yesterday. Looks like there's a typo index.sjson in the code. When I upload an index.sjson in the public-bucket the bootstrap completes
[10:48] <mattyw> I get permission denied (publickey, password) when try to juju ssh to local instance, have I missed something obvious?
[10:53] <geme> juju-core 1.13.1 won't bootstrap on private openstack. /var/log/cloud-init-output.log reports : ERROR juju open.go:89 state: connection failed, will retry: dial tcp 127.0.0.1:37017: connection refused. There's nothing running on this port.mongod is running on 27017 and 28017 thoght
[13:06] <geme> bootstrap problems behind the firewall : Is there away to set proxy so that cloud-init can hit external apt repositories ?
[13:13] <mgz> geme: if no one turns up, the best fallback is probably to describe your setup and issue on the juju mailing list, see lists.ubuntu.com
[13:27] <geme> thanks
[13:49] <geme> juju-core : what constraints are recogned ? instance-type doesn't appear to be.
[13:49] <geme> recognised
[13:49] <rick_h> geme: I believe you have to use ram/cpu
[13:52] <geme> rick_h: openstack uses flavors ( ram/cpu combos ) which was supported in the python version
[14:13] <geme> rick_h: you're correct --constraints "cpu-cores=8 mem=32G" picks the flavor. Thanks
[14:56] <jamespage> hazmat, has anyone mentioned packages jujuclient and juju-deployer officially for Ubuntu?  getting nearish feature freeze - so if we want something in distro now is good :-)
[15:04] <hazmat> jamespage, i haven't heard it mentioned but it sounds like a good idea, we've got ppa builds for both,  but  both are still under active dev. there's some new usage of core trunk features in a branch (api-endpoints, and switching out separate cli juju-plugins). what's nesc. to get a push into universe?
[16:27] <_mup_> Bug #1213169 was filed: DB instance loses zookeeper access and drops pg_hba.conf entries for appservers, juju status shows no errors <juju:New> <https://launchpad.net/bugs/1213169>
[16:54] <kurt__> Does anyone know the status of juju-gui in quantal?
[16:54] <kurt__> Is it working?
[16:55] <kurt__> I am trying to use it from here: cs:~pmcgarry/quantal/juju-gui and it appears to have some dependency reconcile issues
[16:56] <hazmat> kurt__, it should work, the best way might to pull the charm local into a different series dir.. ie mkdir charms/quantal && cd charms/quantal && bzr branch lp:charms/juju-gui && juju deploy --repository=../.. quantal/juju-gui
[16:59] <kurt__> Ok thanks.  I can try that.  The big problem I am running in to is nodejs conflicts with nom on the package install hook
[16:59] <kurt__> nom rather
[16:59] <kurt__> npm
[17:10] <kurt__> hazmat: sorry, I'm researching usage of deploying juju locally - but could you check your juju deploy command for accuracy?
[17:13] <kurt__> nevermind...
[17:20] <kurt__> Can someone confirm juju-gui needs full internet access to work?  That will create problems when using maas since the clients may not necessarily need have internet access.  I see the install script trying to do an apt-get update and it bails (install-error) when it can't do it.
[17:20] <kurt__> http://pastebin.ubuntu.com/5993501/
[17:20] <kurt__> Per hazmat's instructions, I am using latest quantal branch install
[17:20] <sarnold> kurt__: if your clients won't have internet access, you'll need a local mirror of some sort..
[17:21] <kurt__> sarnold: the script appears to be wanting to do an update though…when that fails, everything breaks - how do I resolve that part?
[17:23] <sarnold> kurt__: I'd investigate some way to provide a local mirror that can satisfy an apt-get update; I think quite a few pre-written charms will expect that to work. charms you write yourself, of course, can wget sources from wherever :) but most charm authors will expect apt-get to work.
[17:24] <kurt__> ugh, I think that breaks mass's cloud model
[17:24] <kurt__> maas's rather
[17:24] <sarnold> hrm. It might. :/
[17:25] <kurt__> wouldn't it be prudent to check somehow if maas is the deployment model and then do the apt-get update accordingly?
[17:27] <sarnold> another option is maas growing a debmirror function.
[18:08] <hazmat> kurt__, that branch is trunk, its used to cut the precise release, the instruction i had there is for creating a local charm repository  with the trunk branch setup as quantal.. i don't understand what you mean by local usage, you can deploy an lxc container of precise on a quantal host.
[18:09] <kurt__> I got it deployed
[18:09] <hazmat> cool
[18:09] <kurt__> thanks - but still dealing with the internet access problem for apt-get update
[18:09] <kurt__> trying to set up NAT
[18:26] <kurt__> sarnold: I now have internet issue solved, but same problem with juju-gui - I can post output from debug
[18:27] <sarnold> kurt__: please do.. I figured that getting access to the archive would let you past that.
[18:27] <kurt__> http://pastebin.ubuntu.com/5993717/
[18:29] <kurt__> and output from apt-get update in client node: http://pastebin.ubuntu.com/5993719/
[18:29] <kurt__> being run from a quantal client
[18:31] <sarnold> kurt__: hrm. did you use add-apt-repository to add the ppa?
[18:32] <kurt__> on the client? no - on the root node, yes
[18:33] <kurt__> and juju-gui was being installed from the bzr branch
[18:33] <kurt__> not that that matters
[22:42] <kurt__> sarnold: I managed to use precise and finally got juju-gui working :D
[22:43] <sarnold> kurt__: nice!
[22:44] <sarnold> kurt__: was there something specific that fixed it?
[22:46] <kurt__> I had to ensure the internal clients had internet access (NAT) and I used precise for the images instead of quantal
[22:47] <sarnold> hrm, it might be worth a bugreport against quantal juju or juju-gui if just changing between precise and quantal is enough to fix or break it.
[22:47] <kurt__> that allows the client's clock to sync properly.  Even though its in EST, it's still correct.
[22:47] <kurt__> that solved my OAuth problems
[22:48] <kurt__> there is no quantal release of juju-gui
[22:48] <sarnold> ah, makes it hard to file a bug then :)
[22:48] <kurt__> :D
[22:48] <kurt__> but, I don't know what the latest bzr branch is based on
[22:50] <kurt__> that is two weeks worth of work finally solved
[22:50] <kurt__> phewww....
[22:50] <sarnold> yeah, me neither. the juju team is in a bit of a tough spot since precise is where people will have deployed workloads that they need supported, but they are trying to make the next lts, 14.04, as awesome as they can. most people get to just maintain the old stuff, but they were ambitious and wanted new stuff on older platforms too..
[22:50] <kurt__> is 14.04 LTS?
[22:51] <sarnold> of course all the charms are another matter, people again have precise-based workloads, but some people wanted features from newer releases..
[22:51] <sarnold> kurt__: that's the current plan; I think it'd take an immense event to change it..
[22:51] <kurt__> right
[22:52] <sarnold> and since 13.10 appears to be shaping up well, every thing feels to be on track -- to me, anyway :)
[22:53] <kurt__> are you canonical?
[22:53] <kurt__> with rather
[22:53] <sarnold> kurt__: yes, I am, but not on the juju team, I'm just an enthusiast there :) hehe
[22:54] <kurt__> ah ok - what's your specialty then?
[22:54] <sarnold> kurt__: security
[22:54] <kurt__> i c