[14:02] <marcoceppi> http://pad.ubuntu.com/uds-1311-t-cloud-juju-charm-quality-points
[14:03] <jcastro> https://jujucharms.com/precise/liferay-1/#bws-features
[14:17] <rick_h_> bah, how do I join the hangout? jcastro
[14:18] <jcastro> https://plus.google.com/hangouts/_/7acpjal1hv148g3i1sb5ktqf68?authuser=0&hl=en
[14:18] <jcastro> http://pad.ubuntu.com/uds-1311-t-cloud-juju-charm-quality-points
[15:02] <jcastro> https://plus.google.com/hangouts/_/72cpjufj5oc8omdro2acjh1vco?authuser=0&hl=en
[15:03] <jcastro> http://summit.ubuntu.com/uds-1311/meeting/22010/t-cloud-juju-charms-multiple-stable-releases/
[15:03] <jcastro> in ~3 minutes
[15:45] <jamespage> marcoceppi, jcastro, niemeyer: how would users upgrade from a precise based charm to a trusty based charm? LTS -> LTS
[15:45] <jamespage> i.e. series upgrade support in juju
[15:47] <jamespage> (that is a leading question)
[15:47] <jamespage> :-(
[15:47] <jamespage> my cloud users will love that
[15:48] <jcastro> yeah
[15:48] <jcastro> I hate this topic
[15:48] <jcastro> it just makes me hate software
[15:49] <jamespage> ubuntu has an upgrade story
[15:49] <jamespage> hmmm
[15:49] <jamespage> I think we are avoiding a hard subject
[15:49] <jcastro> I am not avoiding it, I'm just saying it's hard
[15:51] <jamespage> jcastro, ack
[15:53] <rick_h_> it moves a lot to the charm author since the charm has to be the one to know what files it touched, what's the difference between a precise mysql.ini and trusty one.
[15:54] <rick_h_> they'll just have two charms imo. Doing it in one and handling upgrades is a LOT more work, testing, etc
[15:55] <rick_h_> it's a really interesting problem though. Even with packages we just go "hey, the ini file has changed, keep, go default, see diff
[16:01] <mgz> is it possible to get audio-only for the session?
[16:02] <marcoceppi> mgz: not that I know of
[16:06] <jcastro> https://plus.google.com/hangouts/_/7ecpjmodidvjime8kk2kb7s28k?authuser=0&hl=en
[16:06] <jcastro> for this next session
[16:13]  * benji waves
[16:14] <arges-uds> HA == HAPPY
[16:14] <marcoceppi> What about cloud federation?
[16:18] <marcoceppi> :(
[16:20] <jamespage> QUESTION: will/is it possible to include manually provisioned machines as part of other providers
[16:20] <jamespage> say openstack or MAAS or local maybe
[16:21] <jamespage> jcastro, ^^
[16:21] <jcastro> got it
[16:25] <jamespage> w00t!
[16:26] <marcoceppi> jamespage: you can use juju add-machine, but that machine needs to be able to speak to the bootstrap node
[16:27] <jamespage> ack
[16:27] <marcoceppi> so as long as entworking exists, it shoudl work currently
[16:33] <jamespage> jcastro, gotta ask - ubuntu series upgrades, via juju?
[16:34] <jameinel> Upgrading from a cs:precise/postgres to cs:trusty/postgres
[16:34] <jameinel> AFAIK that is not planned in the 14.04 cycle
[16:36] <marcoceppi> jamespage: you can do a hulk smash, and just juju upgrade-charm --switch, but you won't upgrade the base in the process
[16:39] <jcastro> oh bummer
[16:39] <jcastro> do we not have a lunch break?
[16:39] <hazmat> marcoceppi, there's alot of distro series stuff that charm testing won't catch
[16:40] <hazmat> ie. i use btrfs for mysql in trusty, but for precise that might just blow up if used in the real
[16:40] <marcoceppi> yeah
[17:04] <jcastro> hey jamespage
[17:04] <jcastro> this is sort of your session I take it?
[17:04] <jcastro> juju in main basically?
[17:04] <jamespage> yup - but in +1 hour
[17:04] <jamespage> we get lunch
[17:04] <jcastro> oh!
[17:04] <jcastro> whew!
[17:54] <jamespage> jcastro, are you my mc?
[17:54] <jcastro> yessir!
[17:54] <jcastro> we start at :05 after, I'll fire it up in about 6 minutes
[17:55] <jamespage> ack
[17:56] <jamespage> jcastro, wow - juju -> main followed by mysql alternatives
[17:56] <jamespage> that's two tough sessions methinks
[18:02] <jcastro> https://plus.google.com/hangouts/_/76cpj5o91753ur5elerls6s99s?authuser=0&hl=en
[18:02] <jcastro> will be the session
[18:07] <doko> hangout URL?
[18:07] <mdeslaur> o/
[18:07] <jamespage> https://plus.google.com/hangouts/_/76cpj5o91753ur5elerls6s99s?authuser=0&hl=en
[18:07] <doko> jamespage, ^^^
[18:07] <jamespage> mdeslaur, please join
[18:07] <mdeslaur> hrm, ok
[18:07] <mdeslaur> one sec, combing my hair
[18:07] <jamespage> pretty please :-)
[18:08] <jamespage> just turn the video off
[18:17] <marcoceppi> jamespage: charms are backwards compatible from 0.1 onward
[18:17] <marcoceppi> natefinch: correct me if I'm wrong, but juju should never break charm compatibility
[18:18] <marcoceppi>  /charms are/charms should be/
[18:18] <natefinch> marcoceppi: I can't think of anything that would break charm compatibility
[18:19] <marcoceppi> I'd throw a hissy fit if you guys did ;)
[18:19] <natefinch> marcoceppi: certainly :)
[18:30] <mgz> presumably the libv8 security exposure is slightly different from chrome to mongo
[18:35] <sarnold> pkg_history shows four mongodb CVEs; one was REJECTED, one was for spidermonkey, one is v8 -- that looks like it wouldn't be exposed to users beyond juju authors, the fourth one looks like it might have been exposed to a juju use
[18:35] <sarnold> s/juju use/juju user/
[18:37] <mdeslaur> sarnold: interesting...at least if we isolate the v8/spidermonkey stuff it should definitely be easier to backport specific fixes
[18:37] <sarnold> mdeslaur: yeah
[18:37] <mgz> thanks everyone
[18:37] <mdeslaur> and if we hit a point where backporting isn't possible, upgrading the version would be limited to impacting juju, so we're in control of doing it
[18:37] <jamespage> yep - thanks!
[18:37] <mdeslaur> thanks mgz
[18:37] <mdeslaur> thanks!
[19:04] <jcastro> arosales, got a link?
[19:04] <arosales> jcastro, https://plus.google.com/hangouts/_/72cpi46knnik91tbt1c65dap7g?authuser=0&hl=en
[19:04] <arosales> and any other folks interested in joining :-)
[19:05] <arosales> blueprint, notes, hangout, and video are at http://summit.ubuntu.com/uds-1311/meeting/22006/t-cloud-juju-charm-audit/
[19:05] <arosales> Session is Charm Audit
[19:10] <arosales> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-audit-charms
[19:24] <marcoceppi> http://manage.jujucharms.com/tools/review-queue