[08:25] <sgmoore> arraybolt3: Wonderful!!! Thank you so much for all the great work!
[08:32] <sgmoore> valorie: <3
[08:37] <valorie> sgmoore: I still never found a link to the email about LFNW funding
[08:38] <valorie> wrote to him, got no reply
[08:38] <valorie> but it's only Monday....
[08:39] <valorie> bedtime for me; I have a morning call
[08:39] <sgmoore> valorie: how very strange. Are you on matrix? that is where he tracked me down.
[08:39] <valorie> nope, not on matrix
[08:40] <valorie> maybe that's a task for tomorrow
[08:40] <valorie> niters
[08:40] <sgmoore> I gotcha. I will ping him today to see whats up. Night :)
[14:09] <BluesKaj> Hi all
[23:16] <arraybolt3> sgmoore: kubuntu-installer-prompt has passed NEW review and there are MPs for plugging it into the Kubuntu ISO in-flight. If you could seed it, that would be awesome.
[23:17] <arraybolt3> actually, I think you don't even have to seed it
[23:17] <arraybolt3> I can just add it as a dep of calamares-settings-kubuntu... hmm, that seems backwards though.
[23:17] <arraybolt3> ok so changed my mind again :P If you could seed it, that would be great.
[23:17] <arraybolt3> (or anyone else with seed access)
[23:18] <arraybolt3> (speaking of... do I have seed access...?)
[23:18] <arraybolt3> *checks*
[23:19] <arraybolt3> meh, busy, can't find the seed right away


[01:03] <TheLordOfTime> well, Eeebottu's gone again from -bugs-announce
[01:03] <TheLordOfTime> figures.
[01:52] <TheLordOfTime> hggdh, welcome back.
[01:53] <TheLordOfTime> hggdh, mind giving me sone insight on Eeebotu?
[01:53] <TheLordOfTime> regarding what you use for bug announcements (what plugins/botframework/etc)
[02:49] <hggdh> TheLordOfTime: darn!
[02:49] <hggdh> I am losing internet here, forgot to restart it
[11:57] <Kaapa> hey there - been asked to fill more information about the package that my bug refers to
[11:57] <Kaapa> on my case it's https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1094800 . is "linux" the correct keyword for a kernel related issue?
[11:57] <ubot2> Launchpad bug 1094800 in linux (Ubuntu) "Toshiba z930 fails to resume after second suspend on kernel >=3.4" [Undecided,New]
[11:57] <Kaapa> not sure if I shuold add something like powersave or something
[19:35] <penguin42> hmm with Debian frozen it's nigh on impossible to get anything fixed there and I guess it's going to be a while before that sorts itself out
[19:36] <TheLordOfTime> mhm
[19:36] <TheLordOfTime> only thing i've seen are things pushed to unstable, and that's usually nginx
[19:37] <penguin42> well at least that's something
[19:38] <TheLordOfTime> but unstable's only partly frozen i think
[19:38] <TheLordOfTime> and i know experimental's not frozen, there was a ZNC upload post-freeze.
[19:42] <penguin42> TheLordOfTime: sid is supposed to be frozen as well
[19:42] <TheLordOfTime> when i talked to the mentors, they said it was semi-frozen
[19:42] <TheLordOfTime> "no new features"
[19:42] <TheLordOfTime> but "bugfixes accepted"
[19:42] <TheLordOfTime> kind of how any given ubuntu release is :P
[19:42] <TheLordOfTime> but that was at least 3 weeks ago
[19:43] <penguin42> hmm ok, asking on #debina-bugs taffit said 'people are not supposed to push changed to sid that are not release material'
[19:43] <penguin42> so I guess that depends how they call it
[19:43] <TheLordOfTime> well i know nginx had a segfault bug fixed
[19:43] <TheLordOfTime> and that got in :P
[19:44] <penguin42> yeh I guess the problem with my bugs is they don't seg on Debian
[19:44] <TheLordOfTime> yeah, critical bugs i think get fixed
[19:44] <TheLordOfTime> most of the bugfixes for Ubuntu nginx though i pull from upstream
[19:44] <TheLordOfTime> and reverse-engineer/backport as necessary
[21:56] <penguin42> wow, google archives of mail-archive.com are fast enough that it finds a hit from a change to a bug 10 minutes ago
[21:56] <ubot2> Launchpad bug 10 in Launchpad itself "It says "displaying matching bugs 1 to 8 of 8", but there is 9" [Medium,Invalid] https://launchpad.net/bugs/10
[22:33] <melodie> hello
[22:36] <melodie> bb in 2013 :)
[23:26] <penguin42> bug 1094278 and bug 584787 confuse me; I don't think I see why the fix given in 584787 fixes the other
[23:26] <ubot2> Launchpad bug 1094278 in uucp (Ubuntu) "cu doesn't connect properly to a serial console" [Medium,Triaged] https://launchpad.net/bugs/1094278
[23:26] <ubot2> Launchpad bug 584787 in uucp (Ubuntu) "cu 1.07-20build1 mispackaged" [Medium,Confirmed] https://launchpad.net/bugs/584787


[02:57] <RAOF> Could we please get a prod for https://answers.launchpad.net/launchpad/+question/185490 ?
[03:18] <spm> RAOF: is done
[07:40] <czajkowski> aloha
[14:35] <rick_h> adeuring: sorry, missed relieving you
[14:35] <adeuring> rick_h: np problem
[15:32] <mpt> Is it still possible to sort bug listings by date of last activity?
[15:37] <rick_h> mpt: with the new bug listing turned live today you can add the "date last updated" and sort on that
[15:37] <mpt> Oh I see
[15:37] <mpt> thanks rick_h
[15:37] <rick_h> np
[17:21] <YokoZar> How long after I delete a package in a PPA will it take before I can upload a different same-version .orig.tar.gz?
[17:22] <bigjools> YokoZar: never
[17:22] <tumbleweed> until the heat death of the universe
[17:22] <bigjools> https://answers.launchpad.net/launchpad/+faq/990
[17:22] <YokoZar> That's...not intuitive.  You should mention that here: https://help.launchpad.net/Packaging/PPA  (this is the help page linked when you delete a package)
[17:24] <YokoZar> It also bothers me that I've now permanently wrecked my staging PPA :/
[18:50] <spena> here's some feedback to launchpad. I see the new colors you used for bugs section, but "fix committed" & "in progress" have the same color. I have many bugs on those states and it confuses me. Same for "confirmed" and "triaged".
[18:52] <spena> is there a way I can change those colors?
[18:52] <rick_h> thanks spena, there's a bug about that and I know there's disucssion underway https://bugs.launchpad.net/launchpad/+bug/908127
[18:54] <spena> rick_h: thanks for the update
[18:55] <rick_h> spena: np. and sorry, the colors aren't customizable currently
[19:14] <blueyed> I am getting an error when trying to upload to a ppa: http://paste.ubuntu.com/814593/
[19:15] <micahg> bug 798957
[21:10] <ChrisGagnon> I just ran in to this bug https://bugs.launchpad.net/launchpad/+bug/798957, it says to report it here on freenode
[21:14] <abentley> ChrisGagnon: Okay, I'll see what I can do.
[21:22] <abentley> ChrisGagnon: The FTP server has been restarted.
[21:25] <blueyed> 798957 is fixed for me. Thanks.
[21:28] <ChrisGagnon> abentley: 798957 is fixed for me too, thanks.
[21:28] <abentley> ChrisGagnon, blueyed: you're welcome.


[01:39] <beisner> dosaboy, wolsen, thedac or any os-charmers around:  this is all clear, ready for landing/review:  https://review.openstack.org/#/c/308339/
[01:39] <wolsen> beisner: let me take a look
[01:46] <beisner> wolsen, woohoo thx
[02:13] <beisner> cholcombe, trusty-icehouse metal is back in the green. :-)
[07:41] <jamespage> gnuoy, tinwood: good morning!
[07:58] <jamespage> urulama|____, morning
[07:59] <urulama> jamespage: hey. ingestion still not working (we're failing to restore parts of DB) ...
[08:07] <gnuoy> jamespage, morning
[08:09] <leon-tseng> Hi, is there anybody successfully use OpenStack as provider in juju 2.0 ?
[08:26] <tinwood> jamespage, morning :)
[08:27] <jamespage> tinwood, gnuoy, cargonza: pluggin details into https://wiki.ubuntu.com/ServerTeam/OpenStackCharms/ReleaseNotes1604
[08:27] <gnuoy> jamespage, argh, still says Immutable Page for me
[08:27] <jamespage> gnuoy, you need to login...
[08:28] <gnuoy> ...I...have...logged...in....
[08:28] <gnuoy> I...will...logout..and...login..again...
[08:29] <gnuoy> Ok, it helps if you let u1 tell the wiki about your team membership
[08:29] <jamespage> urulama, I'm reading that as well have to use push/publish for our charm release today?
[08:30] <urulama> jamespage: yes
[08:30] <tinwood> gnuoy, yes, I just found a little tick-box on the login to get the page to be editable.  However, it's not like Gdocs - we can't all edit it at once?
[08:30] <jamespage> tinwood, no its a wiki :-)
[08:31] <gnuoy> dosaboy, I've added a "Ceph Backup charm" section if you fancy adding some wordage ?
[08:32] <jamespage> gnuoy, +1
[08:32] <jamespage> add nova-lxd and opendaylight options as well
[08:33] <leon-tseng_> Does nova-compute-lxd work well in Canonical OpenStack now?
[08:34] <gnuoy> jamespage, do you think I should call out the switch to keystone in apache for liberty+ or is that just an implementation detail?
[08:34] <jamespage> gnuoy, implementation detail
[08:34] <jamespage> leon-tseng_, on xenial yes...
[08:35] <urulama> jamespage: when do you want to push it out? do you have another 2h? it looks like we've fixed it
[08:35] <urulama> (currently looks like it's ok)
[08:37] <jamespage> gnuoy, actually...
[08:37] <gnuoy> yes...
[08:37] <jamespage> urulama, we won't push until later today so that's find
[08:37] <jamespage> gnuoy, I think we should mention that
[08:37] <gnuoy> ok
[08:37] <jamespage> gnuoy, it would impact someone who has monitoring setup outside of juju for example
[08:38] <gnuoy> ack
[08:38] <jamespage> gnuoy, how are we on testing?
[08:39] <jamespage> gnuoy, if we're all done, I can cut the 16.04 branches now and re-open master for development...
[08:40] <gnuoy> jamespage, reading backscroll it looks like there were some issues with the Xenial + Mitaka + SSL test, but I've just run it myself and it worked...
[08:40] <jamespage> gnuoy, ack
[08:40] <gnuoy> jamespage, I think from the non-ceph side we're good
[08:41] <jamespage> gnuoy, I see 0 outstanding reviews...
[08:41] <gnuoy> jamespage, I'd like beisner to give the official green light but I see no harm in cutting the branches and we can backport any late breaking changes in the unlikely event that there are any...
[08:42] <jamespage> gnuoy, agreed - we'll hold the actual push to the charm store until later today anyway
[08:42] <gnuoy> kk
[08:42] <jamespage> we have to update the git->bzr migration tool to make that happen
[09:07] <jamespage> gnuoy, beisner: fell at the first hurdle
[09:07] <jamespage> can't create a stable/16.04 as 'stable' already exists...
[09:33] <jamespage> gnuoy, beisner: ok we'll not have stable branches for a bit - worked a migration plan out with yoland
[09:33] <jamespage> a
[09:53] <jamespage> gnuoy, beisner: ok implemented
[09:53] <jamespage> note - anyone who does a pull will need to "git remote prune origin"
[09:54] <jamespage> to get rid of the old stable branch references
[10:00] <jamespage> gnuoy, can you cut a new stable branch for charm-helpers please?
[10:00] <gnuoy> sure
[10:09] <gnuoy> jamespage, done
[10:09] <jamespage> gnuoy, awesome
[10:11] <jamespage> beisner, gnuoy: when we are ready to release:
[10:11] <jamespage> https://github.com/openstack-charmers/migration-tools/pull/3
[10:11] <jamespage> then git->bzr sync will pull from the new charm branches for stable/16.04
[10:11] <gnuoy> jamespage, fantastic, thank you for prep'ing the release
[10:11] <jamespage> gnuoy, this does not cover hacluster - will need todo that old-skool
[10:14] <gnuoy> jamespage, I'll prep hacluser.
[10:17] <jamespage> gnuoy, ta
[10:28] <gnuoy> jamespage, beisner, hacluster mp is ready  https://code.launchpad.net/~gnuoy/charms/trusty/hacluster/1604/+merge/292493
[10:37] <jamespage> gnuoy, +1 ack thanks
[10:37] <jamespage> gnuoy, I have commits ready on all of the stable/16.04 branches to switchover to stable ch and stable testing...
[10:38] <jamespage> but won't submit until we do our first sync from stable/16.04
[10:38] <gnuoy> ok...
[10:38] <jamespage> otherwise they will all just fail...
[10:38] <jamespage> urulama, how are we looking for injestion based release today?
[10:39] <urulama> jamespage: unfortunately not good. manual publishing remains the only way.
[11:00] <jamespage> urulama, just preppeing for push - how do we push/publish an 'official' charm?
[11:00] <jamespage> urulama, i.e one that was promulgated
[11:01] <urulama> jamespage: ok, which one will be first, let's do it step by step
[11:02] <jamespage> urulama, ok lets use ceilometer as an example
[11:02] <jamespage> urulama, currently cs:trusty/ceilometer
[11:02] <jamespage> oh I think I answered my own question
[11:02] <urulama> jamespage: ok. is ti multiseries charm?
[11:02] <jamespage> charm push . cs:trusty/ceilometer
[11:02] <urulama> noooo
[11:03] <jamespage> urulama, well it is but series in metadata landed way to late to get it in
[11:03] <urulama> jamespage: charm push . ~openstack-charmers/trusty/ceilometer
[11:03] <jamespage> urulama, ok so the current owner...
[11:03] <jamespage> check
[11:03] <urulama> jamespage: yes
[11:03] <urulama> jamespage: that'll give you revision
[11:03] <urulama> jamespage: publish that
[11:03] <urulama> jamespage: it should be promulgated already
[11:03] <subbie> freak yo !
[11:04] <jamespage> urulama, I have a handful of new charms to promulgate as well
[11:04] <jamespage> urulama, whats the promugation command these days?
[11:04] <urulama> jamespage: you don't have to do it if a charm is already promulgated
[11:04] <freak_> subbie , welcome to the group
[11:04] <jamespage> urulama, these are not
[11:04] <urulama> ceilometer?
[11:05] <urulama> ceilometer is ...
[11:05] <jamespage> urulama, well yes - but I have 26 charms to push out today
[11:06] <jamespage> 4 of them are not promulgated just yet...
[11:06] <urulama> jamespage: ok, the ones that are not, you should ping marcoceppi
[11:06] <urulama> jamespage: he has access to promulgate them
[11:10] <urulama> jamespage: when you're left with with only non-promulgated ones, ping rogpeppe1, he'll help you promulgate them
[11:11] <jamespage> urulama, http://paste.ubuntu.com/15963061/ look ok to you?
[11:12] <urulama> jamespage: charm grant is not needed
[11:12] <jamespage> urulama, default read acl is everyone right?
[11:12] <urulama> jamespage: it's set to that already
[11:12] <urulama> jamespage: it's not per revision
[11:12] <jamespage> urulama, for existing charms only, or does that apply to new charms as well?
[11:13] <urulama> jamespage: correct, just for existing
[11:13] <urulama> jamespage: that script looks ok
[11:14] <jamespage> urulama, ack - thanks for looking...
[11:14] <urulama> jamespage: i'd run it on one charm though first :)
[11:15] <jamespage> urulama, yup
[11:16] <jamespage> urulama, I suspect all our xenial series pushes will need promulgation as well...
[11:16] <jamespage> as we're not series in metadata yet
[11:17] <urulama> jamespage: all series have promulgation, it's not per series, it's per username + charm name
[11:17] <urulama> jamespage: so no need to promulgate xenial ones
[11:17] <jamespage> urulama, ok should be good there then - thanks for confirming
[11:20] <gnuoy> jamespage, do you know of a bug tracking the alarming ceilometer charm issue? I see nothing against the charm
[11:20] <jamespage> gnuoy, that aodh is not included by default right?
[11:21] <gnuoy> jamespage, right
[11:21] <jamespage> gnuoy, I don't think there is a bug
[11:43] <gnuoy> jamespage, I've added harening to the doc. If thats ok we should probably ask wolsen to add a few words
[11:44] <gnuoy> * Hardening
[11:55] <deanman> Hi, i just deployed munin and it seems that the charm is failing to configure properly the access rights. Anyone used this particular charm in the past?
[12:15] <ReSam> is there any more progress on https://bugs.launchpad.net/juju-core/+bug/1469193?
[12:15] <ReSam> I'm having the same problem, since my controller has 3 interfaces, and it always picks the wrong one
[12:15] <mup> Bug #1469193: juju selects wrong address for API <kvm> <local-provider> <lxc> <network> <sts> <juju-core:Expired> <https://launchpad.net/bugs/1469193>
[12:53] <jcastro> office hours in 2 hours!
[12:55] <jcastro> hatch: any of you ui folks wanna give us an update today?
[12:59] <jcastro> cory_fu: kwmonroe you guys got anything you been working on to show during office hours?
[13:02] <jamespage> gnuoy, idea for next cycle - action on keystone charm to get you a novarc
[13:07] <marcoceppi> jamespage: you need something promulgated?
[13:10] <jamespage> marcoceppi, not just yet
[13:11] <jamespage> but we will
[13:11] <jamespage> urulama, final check - injestion?
[13:11] <urulama> jamespage: still dead as a dodo
[13:16] <jcastro> cherylj: do you want to join us for office hours today?
[13:30] <beisner> gnuoy, jamespage - ready, set, green light go?
[13:31] <jamespage> beisner, I think gnuoy and I are +1 - just waiting on you for 3 makes a releases...
[13:31] <beisner> jamespage, gnuoy - yep i don't have any outstanding blockers :-)
[13:31] <beisner> fyi, i'll be working on ci mods for the new stable branch pivot today
[13:32] <jamespage> beisner, okies - so the first thing todo is
[13:33] <jamespage> beisner, https://github.com/openstack-charmers/migration-tools/pull/3
[13:33] <jamespage> beisner, you ok with that change?
[13:33] <beisner> man too bad we can't just cut the lp sync right now yah
[13:33]  * gnuoy holds on to his seat
[13:34] <jamespage> beisner, still need it for amulet...
[13:34] <beisner> yes, that is the only thing afaik
[13:34] <jamespage> beisner, indeed...
[13:35] <beisner> jamespage, those changes look sound
[13:35] <jamespage> beisner, hit merge then :-)
[13:36] <beisner> jamespage, poked
[13:36] <jamespage> beisner, I also have https://code.launchpad.net/~james-page/openstack-charm-testing/16.04-release/+merge/292497 for you to review
[13:36] <jamespage> beisner, ok - next step run the sync
[13:36] <jamespage> I'll do that now
[13:36] <beisner> dood sweet jamespage ! -- one thing on my afternoon list you've already proposed.  thx!
[13:36] <jcastro> beisner: buddy, you got time for office hours today? In 1.5 hours?
[13:37] <jamespage> beisner, I can sed with the best of them...
[13:37] <beisner> gnuoy, we'll need to do similar for os-mojo-specs ^
[13:37] <beisner> jcastro, i'm a maybe-to-probably-not with release day activities and post-charm release CI mod needs stacking up.
[13:37] <gnuoy> beisner, say what now?
[13:38] <beisner> gnuoy, we'll need to update mojo spec stable foo
[13:38] <jcastro> beisner: ok, I'll just summarize the mitaka charm release notes .. which I can find ... ?
[13:38] <bbaqar> hey guys .. using lxds .. when i run sudo -u nova lxc list  i get /root/.config/lxc/config.yml: permission denied  ... any idea wihch charm configures this file?
[13:38] <gnuoy> beisner, s!stable!stable/16.04! you mean ?
[13:38] <beisner> jcastro, they're still cooking.  i imagine we'll publish something late today
[13:39] <beisner> yyyyah gnuoy ;-)
[13:39] <gnuoy> beisner, on it!
[13:39] <jcastro> ack, do you have a draft I can stumble through?
[13:39] <beisner> gnuoy, rock on
[13:39] <jcastro> by still cooking you probably mean "I haven't started yet." :)
[13:39] <gnuoy> https://wiki.ubuntu.com/ServerTeam/OpenStackCharms/ReleaseNotes1604
[13:39] <beisner> jcastro, ^ :)
[13:39] <jcastro> thanks
[13:40] <jcastro> marcoceppi: ok so the community team guys inadvertantly announced a Q+A for the same time as our office hours but didn't see us on the calendar, how do you feel about a combo session?
[13:41] <marcoceppi> jcastro: seems odd, we'd probably just be sitting quietly while everyone asks about desktop stuff
[13:41] <jcastro> yeah, but the thing is, we announced so it's not like I can move it
[13:41] <jcastro> I guess I'll just ask them to delay an hour
[13:43] <jcastro> gnuoy: beisner: man, you guys did a TON this cycle
[13:43] <jcastro> it would take me an entire session just to glaze over the new stuff
[13:43] <gnuoy> I'm tired just thinking about it
[13:44]  * jcastro hugs
[13:44] <gnuoy> :-)
[13:46] <cory_fu> jcastro: kwmonroe is out today.  I think we'd want to talk about the conversion of the big data charms to layers, and the benefits to maintainability that provides, the in-progress Big Top charms, and maybe the in-progress HA work on the Apache Hadoop charms.  (Both in-progress items are close to being done, so I think I can get them deployed.)
[13:46] <cory_fu> Though I haven't deployed the big top charms yet.
[13:47] <jcastro> cory_fu: yeah that would be awesome, we're going live at 11am EDT if you can join us that would be great.
[13:47] <gnuoy> beisner, https://code.launchpad.net/~gnuoy/openstack-mojo-specs/mojo-openstack-specs-1604/+merge/292526
[13:49] <cory_fu> Uh, any idea how to fix this?  ERROR failed to bootstrap model: cannot start bootstrap instance: no "xenial" images in us-east-1 with arches [amd64 arm64 armhf i386 ppc64el s390x]
[13:50] <gnuoy> beisner, I'll do something a bit cleverer soon ie checkout the most recent stable branch then there should be no need for a mp for each release
[13:50] <jamespage> bbaqar, hey - you've caught us right in the middle of release - I would suspect that its probably the lxd or nova-compute charms by advent of using the lxc command
[13:50] <beisner> gnuoy, ack thx
[13:51] <jamespage> beisner, gnuoy: all of the github charms are trusty+xenial right?
[13:52] <jamespage> hmm
[13:52] <beisner> jamespage, p, t, w, x
[13:52] <jamespage> beisner, pxc is not p I think
[13:52] <jamespage> love codes...
[13:52] <beisner> right, it isn't.  good catch
[13:52] <jamespage> I think that's the exception...
[13:53] <jamespage> all others are everywhere
[13:53]  * beisner rechecks, sec..
[13:53] <jamespage> hacluster is trusty+xenial
[13:53] <gnuoy> Is that true for hacluster?
[13:53] <gnuoy> yeah
[13:53] <beisner> jamespage, *odl* is diff too
[13:53] <jamespage> yeah no precise testing I guess...
[13:53] <beisner> jamespage, lxd, x only
[13:53] <jamespage> right
[13:53] <jamespage> ok I need a map of this
[13:54] <beisner> other than that, p t w x is the norm
[13:54] <beisner> yah we do
[13:54] <jcastro> ERROR failed to bootstrap model: waited for 10m0s without being able to connect: Permission denied blickey,password).
[13:54] <jcastro> anyone know what would cause that on the lxd provider?
[13:56] <marcoceppi> jcastro: looks like you've got permission denied.
[13:59] <jcastro> marcoceppi: I know that. :) I am just wondering how I got into this state.
[14:08] <jcastro> jose: you said you wanted to host today?
[14:09] <jcastro> cherylj: I need to update the Juju release notes section for ubuntu, I am assuming it'll be beta4 for 16.04 today and then updated to final in a future date?
[14:11] <cherylj> jcastro: it should be beta5.  balloons - can you confirm?
[14:14] <jcastro> yeah because I see beta4 on my system still
[14:15] <balloons> beta5 is in proposed still I believe
[14:16] <jamespage> beisner, ok git->bzr ran - lxd and ceph-mon skipped due to missing /trunk branches - created those by hand ...
[14:16] <jamespage> from /next branches...
[14:16] <jamespage> beisner, next I'll put the reviews up for the stable branch changes
[14:17] <beisner> jamespage, i'd have expected cinder-backup to have the same issue.  or did we release that previously?
[14:17] <beisner> ah i think it was part of 16.01
[14:18] <jamespage> beisner, ok this will create some UOSCI noise - but does not gate release of charms - just houskeeping...
[14:18] <beisner> jamespage, actually i think i'll plug its ears for a few hrs
[14:18] <cherylj> balloons: so we'll have beta4 in xenial?
[14:18] <jcastro> I will say beta4 for now
[14:19] <balloons> I'm trying to find it's status.
[14:19] <balloons> Tests should pass and it should get into the archive proper
[14:20] <balloons> welp, it was rejected looks like.. hmm
[14:20] <beisner> jamespage, ok, osci will ignore gerrit msgs until i flip that back on.  just don't want a kazillion amulet jobs firing while we scoot things around.
[14:21] <jamespage> beisner, ok leave it off for now - seeming merge conflicts that don't make sense...
[14:21] <beisner> small impact is that if anyone devs @ master, we'll just have to do rechecks after we light it back up
[14:21] <jamespage> beisner, sure
[14:24] <cherylj> jcastro: and I guess I should go to the office hours to let people know that they're going to be getting xenial automagically now  :)
[14:24] <cherylj> jcastro: when is it?
[14:27] <jcastro> cherylj: ~30 minutes, top of the hour
[14:27] <jcastro> what do you mean by xenial automagically?
[14:27] <cherylj> jcastro: if you don't specify a default series, today it's going to be xenial
[14:27] <cherylj> happy release day
[14:29] <jcastro> !!
[14:29] <jcastro> but if xenial/charm doesn't exist, will it fall back to trusty/charm?
[14:32] <jamespage> jcastro, how many xenial charms do we have in charmstore?
[14:33] <jcastro> not many
[14:35] <cherylj> jcastro: no, no fallback
[14:37] <jamespage> urulama, is the charmstore api eventually consistent?
[14:37] <jamespage> I have trouble uploading and then setting info on the charm I just uploaded...
[14:38] <urulama> bac: ^
[14:38] <urulama> sorry OTP
[14:38] <jcastro> cherylj: ok so what happens when I `juju deploy mediawiki`
[14:38] <bac> jamespage: are you getting an error on the push?
[14:39] <jamespage> urulama, ack
[14:39] <jamespage> bac, yeah
[14:39] <jamespage> bac, https://github.com/openstack-charmers/release-tools/blob/master/push-and-publish
[14:39] <jamespage> script where using the publish
[14:39] <jamespage> bac,  I see different problems
[14:39] <jamespage> bac, sometimes
[14:39] <bac> jamespage: the charm binary in the PPA has a bug.
[14:40] <jamespage> bac, does the charm binary in xenial?
[14:40] <bac> jamespage: if you can build your own from master it'll work.  sorry for the inconvenience.
[14:40] <bac> jamespage: yes
[14:40] <cherylj> jcastro: if you have a controller that was bootstrapped before today, it's default series will still be trusty (unless it was specified by the user already)
[14:40] <jamespage> bac, point me at master...
[14:40] <cherylj> jcastro: but new bootstraps today will set their default-series to xenial if you don't override it
[14:41] <cherylj> jcastro: so 'juju deploy mediawiki' will try to deploy with xenial
[14:41] <jcastro> uggggggggggggg
[14:41] <bac> jamespage: https://github.com/juju/charmstore-client
[14:41] <cherylj> unless you have specified default-series=trusty
[14:41] <bac> jamespage: go get -u github.com/juju/charmstore-client
[14:41] <jamespage> bac doing so now!
[14:42] <jcastro> cherylj: so what happens exactly, an error or what?
[14:42] <bac> marcoceppi: ^^ ETA for charm ppa update in regards to the email i sent yesterday?
[14:43] <marcoceppi> bac: I want to do the right thing and have it in xenial first
[14:43] <marcoceppi> bac: so I'm applying it for an SRU
[14:43] <bac> marcoceppi: ok.  guess on how long?
[14:43] <marcoceppi> bac: minimum of 7 days?
[14:43] <bac> ok.  fun.
[14:43] <bac> thanks!
[14:44] <jamespage> bac,
[14:44] <jamespage> package github.com/juju/charmstore-client: no buildable Go source files in /home/jamespage/src/go/src/github.com/juju/charmstore-client
[14:44] <jamespage> ?
[14:45] <jcastro> jose: there?
[14:45] <cherylj> jcastro: I'm still bootstrapping a new controller to verify
[14:45] <bac> jamespage: looking
[14:45] <jcastro> I am concerned because this is a huge change in default behavior
[14:46] <jcastro> users will only be able to deploy a handful of charms, if that
[14:46] <jcastro> I mean, we'd have to go re-edit all the docs, blog posts, etc.
[14:46] <jose> jcastro: getting things set up
[14:47] <jcastro> <3 thanks
[14:47] <jose> np
[14:50] <cherylj> jcastro: looks like there may be a fallback.  new bootstrap deployed mediawiki
[14:50] <jcastro> ok
[14:51] <jcastro> on trusty?
[14:51] <cherylj> jcastro: it fell back to using trusty
[14:52]  * jamespage stops holding his breath
[14:52] <jcastro> ok
[14:52] <jcastro> man, I was going to pass out.
[14:53] <jose> jcastro: I'll have a link for you in just a sec
[14:53] <jcastro> awesome! finishing up a meeting
[14:53] <mbruzek> Hi jose!
[14:53] <jose> hey mbruzek :)
[14:54] <mbruzek> Are you going to be at our office hours hangout?
[14:55] <jose> yep
[14:55] <jose> getting it set up
[14:55] <mbruzek> awesome
[14:55] <jose> of course, if google weren't so slow...
[14:56] <bac> jamespage: http://pastebin.ubuntu.com/15966511/
[14:56] <mbruzek> Thanks for doing that, I just wanted to say hi, and figure out the next time I would see you
[14:56] <jcastro> jose: come on come on!
[14:56] <bac> jamespage: breathe....
[14:56] <jamespage> bac, thanks for the reminder...
[14:56] <mbruzek> jcastro:  it looks like jose is working on it
[14:56] <jamespage> ;-)
[14:59] <jose> you can join here https://plus.google.com/hangouts/_/hoaevent/AP36tYehhq8M1IOZr6T12q9bSs6tEn6l76nERbIE9gCP_NqwtnbK2A
[14:59] <jose> jcastro: ^
[15:00] <jamespage> bac, http://paste.ubuntu.com/15966593/
[15:00] <jamespage> any ideas?
[15:01] <bac> frankban_: ^^
[15:03] <bac> jamespage: `which charm`?  `hash -d charm` ?
[15:04] <bac> should be $GOPATH/bin/charm
[15:06] <mbruzek> For those who want to join office hours: https://plus.google.com/hangouts/_/hoaevent/AP36tYehhq8M1IOZr6T12q9bSs6tEn6l76nERbIE9gCP_NqwtnbK2A
[15:06] <urulama> jamespage: it wasn't pushed https://api.jujucharms.com/charmstore/v5/~openstack-charmers/xenial/swift-storage/meta/any
[15:06] <gil> hi does anyone have the link for the juju office hours going on now please, thanks!?
[15:06] <mbruzek> gil: https://plus.google.com/hangouts/_/hoaevent/AP36tYehhq8M1IOZr6T12q9bSs6tEn6l76nERbIE9gCP_NqwtnbK2A
[15:06] <urulama> jamespage: https://api.jujucharms.com/charmstore/v5/~openstack-charmers/trusty/swift-storage/meta/any this one works
[15:08] <jose> ubuntuonair.com if you want to watch
[15:10] <mbruzek> The ntp charm is available in xenial! That is awesome. Who maintains the ntp charm?
[15:13] <AuroraAvenue> QUESTION: I'm not a coder, but how do I get a 'Mediagoblin' charm going for Juju ? https://wiki.mediagoblin.org
[15:14] <jcastro> AuroraAvenue: ok I'll address that after marco
[15:14] <AuroraAvenue> jcsackett: np
[15:14] <AuroraAvenue> whoops
[15:14] <AuroraAvenue> jcastro: np
[15:14] <jcsackett> happens all the time. :)
[15:15] <AuroraAvenue> jcsackett: We all love you too :)
[15:15]  * jcsackett laughs
[15:16] <randall-buzzgen-> QUESTION: Now that Ubuntu 16.04 is out, what is the current best/easiest way for people who have never been "devops" folks or developers to get started with deploying Charms and bundles? (People new to this may want to quickly "kick the tires" and see what Juju is all about.)
[15:17] <AuroraAvenue> jcastro: So basically mediagoblin and https://ghost.org/ is all that I'm looking for in charms :)  for blogging etc.
[15:18] <jose> https://jujucharms.com/ghost/
[15:18] <AuroraAvenue> cheers for the ghost bit, cheers.
[15:19] <mbruzek> AuroraAvenue: https://jujucharms.com/q/ghost
[15:19] <mbruzek> The official ghost charm is precise only. Other ones are available for trusty
[15:19] <bdx> office-hours: how can I use JAAS to make charms that I develop under my namespace publicly accessible, do I need to push to a certain channel?
[15:19] <jcastro> hatch: update ghost to xenial pls
[15:20] <mbruzek> those are out of a personal namespace
[15:21] <cory_fu> There is also an old mediagoblin charm https://jujucharms.com/u/clint-fewbar/mediagoblin/precise/1 but it has not been reviewed and doesn't look like it's been maintained for some time.
[15:21] <hatch> jcastro: lol, maybe it needs to be a multi-series :)
[15:21] <jcastro> bdx: https://wiki.ubuntu.com/ServerTeam/OpenStackCharms/ReleaseNotes1604
[15:25] <thedac> beisner: gnuoy tinwood: If anyone has time https://code.launchpad.net/~thedac/openstack-mojo-specs/16.04-changes/+merge/292545
[15:25] <bdx> jcastro: awesome!
[15:26] <gnuoy> thedac, +1
[15:26] <thedac> gnuoy: ta
[15:28] <marcoceppi> bdx: https://jujucharms.com/docs/devel/authors-charm-store
[15:29] <gil> matt I have some questions but I was not able to unmute not sure why....
[15:29] <gil> ok it finally unmted - I can ask questions after corey
[15:29] <mbruzek> gil:  you don't look muted to me. Type your question here and Jorge can read it
[15:30] <gil> (1) I need the command to just push out the lxc-trusty-template to a maas-managed node - I saw this command somewhere but forgot to bookmark it and it's a hard one to find online.  this is just pusing out the template without pushing a charm
[15:31] <gil> (2) regarding openstack austin next week, what one day would be the best one to go for what I am interested in, and who from the charm team will be at austin?
[15:32] <gil> (3) need an update on doing charms that need to download secured content - for example oracle software which requries a  couple of export restrictions checkboxes...
[15:33] <AuroraAvenue> QUESTION: is it possible to run juju on one computer yet? in production i mean ?
[15:33] <jcastro> yep
[15:33] <AuroraAvenue> k , cheers.
[15:33] <jcastro> you would deploy in LXD containers
[15:33] <gil> corey/cory
[15:34] <AuroraAvenue> jcastro: So you can run it on one server, easily ?
[15:35] <bbaqar> jcastro: is it possible to run bootstrap on the node where juju-core is configured?
[15:37] <jcastro> AuroraAvenue: I hope that answers your question
[15:38] <AuroraAvenue> jcastro: Yes that is cool-beans, cheers.
[15:44] <AuroraAvenue> "comical" Ha! freudian slip !
[15:48] <marcoceppi> AuroraAvenue: ;)
[15:48] <AuroraAvenue> :)
[15:49] <jamespage> urulama, I must be missing something about setting meta data
[15:49] <jamespage> urulama, http://paste.ubuntu.com/15966593/
[15:49] <jamespage> there is a charm push just before I try to set it...
[15:50] <jamespage> mbruzek, that was me (ntp) we use it in all of our bundles...
[15:50] <urulama> jamespage: xenial charm doesn't exist
[15:50] <mbruzek> Thank you jamespage
[15:50] <urulama> jamespage: https://api.jujucharms.com/charmstore/v5/~openstack-charmers/xenial/swift-storage/meta/any {"Message":"no matching charm or bundle for cs:~openstack-charmers/xenial/swift-storage","Code":"not found"}
[15:50] <jamespage> urulama, "charm push swift-storage '~openstack-charmers/xenial/swift-storage'"
[15:50] <jose> gil: https://insights.ubuntu.com/event/openstack-summit-austin/ <-- you may find that useful
[15:51] <jamespage> urulama, does it have to be published first?
[15:51] <urulama> jamespage: no, push is first, publishe next
[15:51] <jamespage> urulama, yes I know
[15:51] <jamespage> urulama, before I can charm set, do I have to charm publish
[15:51] <mbruzek> gil<EMAIL_ADDRESS>[15:51] <urulama> jamespage: if you don't publish it, then ~openstack-charmers/xenial/swift-storage doesn't get resolved
[15:52] <urulama> jamespage: charm set '~openstack-charmers/xenial/swift-storage-0' would work in that case
[15:52] <jamespage> urulama, metadata is tied to revisions of a charm?
[15:53] <urulama> jamespage: ~openstack-charmers/xenial/swift-storage uses stable pointer to find revision
[15:53] <urulama> jamespage: you havent published it yet, so there is no pointer hence it doesn't know which revision to use and says it doesn't exist
[15:53] <jamespage> that's all I needed to know...
[15:54] <frankban_> hatch: could you please triage https://github.com/juju/juju-gui/issues/1581 , https://github.com/juju/juju-gui/issues/1582 and https://github.com/juju/juju-gui/issues/1583 ?
[15:54] <frankban_> ... and wrong channel
[15:54] <urulama> :)
[15:54] <hatch> frankban_: I can!
[15:54] <hatch> :)
[15:54] <frankban_> :-)
[15:55]  * hatch reaches for the duct tape
[15:55] <beisner> gnuoy, ah bugger.  our tempest testing and config scripts in o-c-t are suffering the ens2 change in xenial too.
[15:55] <beisner> rockstar, zul fyi ^
[15:55] <jamespage> bac, urulama: OK so I'm using charm built from master branch
[15:56] <urulama> jamespage: cool
[15:56] <jamespage> I've re-ordered our push-publish script to push/publish and then set metadata...
[15:56] <zul> beisner: craaaap
[15:56] <jamespage> and acls on new charms...
[15:56] <urulama> jamespage: sounds good
[15:56]  * beisner borrows duct tape from hatch
[15:57] <jamespage> urulama, however I still keep hitting
[15:57] <jamespage> ERROR cannot post archive: unauthorized: access denied for user "james-page"
[15:57] <jose> jamespage: charm login maybe?
[15:57] <hatch> :)
[15:57] <jamespage> jose, I would love if that was the case
[15:57] <jamespage> jose, runnnig exactly the same command again may or may not work...
[15:58] <jose> *sighs*
[15:58] <jamespage> ;)
[15:58] <beisner> zul, i'll be testing and proposing bundles/lxd* and profiles changes @ o-c-t
[15:58] <urulama> jamespage: yeah, we have update of services in the IS queue :-/
[15:59] <marcoceppi> Austin Convention Center - Level 4 - MR 12 A/B
[15:59] <jose> https://insights.ubuntu.com/event/openstack-summit-austin/
[15:59] <urulama> jamespage: i guess we could say "all hell broke loose" this week ...perfect timing
[16:00] <jamespage> urulama, that sounds like a great synopsis
[16:01] <jamespage> urulama, I'm not quite sure how I'm going to get our 96 charms pushed to the store without writing a script that dos's the API...
[16:01] <AuroraAvenue> jose, Cud you update the calendar, for the Next juju  meeting ? cheers
[16:02] <urulama> jamespage: i think it won't ... ingestion was much more invasive
[16:03] <urulama> jamespage: i'm more concerned that you'll hit the "unauthorized" errors which will be hard to track
[16:03] <aisrael> brb, going to Austin
[16:03] <aisrael> pop-up Austin sprint
[16:03] <mbruzek> They are giving away orange box! : https://pages.ubuntu.com/orange-box.html?utm_source=Insights&utm_medium=Landing%20Page&utm_campaign=FY17_ODS_Austin_OrangeBox&
[16:04] <AuroraAvenue> nice show guys.
[16:04] <AuroraAvenue> jose, jcastro Well done !
[16:07] <jcastro> thanks!
[16:12] <jamespage> urulama, ok I have written a retry handler around all my charm commands...
[16:13] <urulama> jamespage: kk, i'm also trying to pinpoint a unit that's misbehaving ...
[16:13] <jamespage> urulama, ok running now
[16:13] <jamespage> at least 96 charm publishing events to detect it :-)
[16:14] <urulama> jamespage: track them here https://api.jujucharms.com/charmstore/v5/changes/published?start=2016-04-21
[16:17] <urulama> jamespage: mh, it stopped ... did script break?
[16:17] <AuroraAvenue> jcastro: I'd really like to see mediagoblin as a charm, but as I say - I'm not a coder at all. Any chances of doing it yourself - if it only takes half an hour ?
[16:17] <jamespage> urulama, yes - needed to refine my grep a little for when charm push fails...
[16:19] <jamespage> urulama, running again now
[16:20] <urulama> jamespage: ok, few more charms added
[16:21] <jamespage> urulama, I seem to be spinning on charm push ceph-radosgw '~openstack-charmers/precise/ceph-radosgw'
[16:21] <urulama> yeah ,that was last in store
[16:21] <jcastro> AuroraAvenue: I am also not a coder, but I'll be on a lookout for someone who can help
[16:22] <AuroraAvenue> jcastro: Cheers jorge - It'll really help - Is there a discourse JuJu too ?
[16:23] <AuroraAvenue> https://jujucharms.com/q/discourse Can't see it.
[16:23] <AuroraAvenue> seems strange, as we have http://discourse.ubuntu.com/
[16:25] <jcastro> the charm is abandoned and old
[16:26] <jcastro> the discourse run by the discourse guys so it's not juju deployed
[16:26] <jcastro> at the time discourse was going a ton of change and keeping the charm up to date was difficult
[16:27] <urulama> jamespage: precise/ceph-radosgw is pushed and published, but failed to update revisions. maybe it's spinning there.
[16:28] <jamespage> hmm
[16:29] <marcoceppi> AuroraAvenue jcastro it's be nice, now that we have a docker layer, to re-do the discourse stuff
[16:29] <urulama> jamespage: maybe it gets error and retries with publishing over and over?
[16:29] <jcastro> it would indeed
[16:29] <urulama> jamespage: sorry, not publishing, pushing
[16:33] <jamespage> urulama, ok running again...
[16:33] <jamespage> urulama, hitting those unauthorized errors alot
[16:34] <jamespage> urulama, 10 tries on every charm command atm
[16:34] <jamespage> one succeeded on the 10ths...
[16:34] <urulama> jamespage: uf, that is weird :-/
[16:34] <jamespage> urulama, charm push must make a couple of api call right? sometimes the upload succeeds and then there is a
[16:35] <jamespage> ERROR cannot add extra information: unauthorized: access denied for user "james-page"
[16:35] <jamespage> upload succeeed == I get a url and status back...
[16:35] <urulama> jamespage: correct
[16:41] <urulama> jamespage: ok, precise charms are up :)
[16:41] <jamespage> urulama, yup
[17:05] <jamespage> marcoceppi, hey - I need the following charms under openstack-charmers promulgated please
[17:05] <jamespage> openvswitch-odl
[17:05] <jamespage> cinder-backup
[17:05] <jamespage> lxd
[17:05] <jamespage> neutron-api-odl
[17:05] <jamespage> ceph-mon
[17:06] <marcoceppi> jcastro: np, on it
[17:06] <marcoceppi> jamespage: are they all in the stable channels, etc?
[17:06] <jamespage> marcoceppi, yes
[17:11] <urulama> marcoceppi: fyi, thanks to jamespage's uploads, i was able to pinpoint the unit that was giving problems, so you shouldn't see any more "unaothorized" errors
[17:11] <marcoceppi> urulama: \o/
[17:11] <marcoceppi> jamespage: promulgated
[17:12] <jamespage> marcoceppi, ta
[17:12] <jamespage> rockstar, zul: congrats you are now live - https://jujucharms.com/lxd/
[17:12] <rockstar> \o/
[17:13] <urulama> jamespage, marcoceppi: verified that all those new promulgated are properly resolved by charmstore, all looks good
[17:13] <jamespage> urulama, yeah but tomorrow
[17:14] <jamespage> urulama, I was hoping todo that pm today, but...
[17:14] <jamespage> re bundles...
[17:25] <beisner> nice spike, jamespage urulama - thx much!
[17:25] <beisner> marcoceppi, you too ;-)
[17:55] <zul> jamespage: cool thanks
[20:46] <jasondotstar> qq about amulet- I'm in the middle of writing a test, and I'm attempting to make sure that I have the relation line in the code working. running into this error: ValueError: All relations must be explicit, service:relation
[20:49] <jasondotstar> how can i find out what the 'legal' relation values are for a given charm?  Is it the list of 'connects from' services from the charm documentation?
[21:11] <cory_fu> jasondotstar: The charm store lists the relations that a charm supports.  You can also see it in metadata.yaml
[21:11] <jasondotstar> cory_fu: thx
[21:13] <cory_fu> jasondotstar: E.g., on https://jujucharms.com/ganglia/ if you click See More under Connects from, you can see that ganglia-node would support :node, :ganglia-node, :master, and also from Connects to, :website and :head
[21:34] <beisner> jamespage, looks like after a recheck, your stable change merge conflicts are resolved.  i just triggered recheck on all of them.  if those come back +1 from infra CI, clear to land?
[21:46] <beisner> thedac, jamespage - with stable proposals stabilized, i'm turning the bot back on.   stable/xx.nn amulet tests, etc., may not be quite right just yet though.
[22:02] <beisner> thedac, jamespage - ok a zillion stable merges are heading in now.  c-h yaml and amulet stable bit flips.
[22:02] <thedac> beisner: ok
[22:02] <beisner> zul, o-c-t updated
[22:02] <thedac> is there a topic: list of them?
[22:03] <beisner> thedac, https://review.openstack.org/#/q/topic:16.04-updates
[22:03] <thedac> thanks
[22:03] <beisner> o/  i've gotta head out, back in later this eve
[22:04] <beisner> thedac, those won't hit the charmstore yet naturally.  we still have the push-a-charm-when-something-lands thing to nail down.
[22:04] <thedac> understood