Thursday, 2016-04-07

*** spotz_zzz is now known as spotz00:00
*** jlwhite_ has quit IRC00:11
*** pushkaru has quit IRC00:16
*** pushkaru has joined #osic00:25
*** pushkaru has quit IRC00:32
*** asettle has quit IRC00:32
*** sulo has joined #osic00:33
*** ediardo has quit IRC00:43
*** rmevans has joined #osic01:04
*** rmevans has quit IRC01:05
*** rmevans has joined #osic01:06
*** karthikp has joined #osic01:08
*** sgundur has left #osic01:16
*** kebray_ has quit IRC01:21
*** asettle has joined #osic01:22
*** muralia has joined #osic01:23
*** muralia_ has quit IRC01:23
*** rmevans has quit IRC01:24
*** rmevans has joined #osic01:26
*** asettle has quit IRC01:28
*** sgundur has joined #osic01:43
*** sgundur has left #osic01:44
*** muralia has quit IRC01:54
*** ravikamachi has quit IRC02:18
*** mdfuller has joined #osic02:20
*** asettle has joined #osic02:29
*** karthikp has quit IRC02:37
*** muralia has joined #osic02:51
*** spotz is now known as spotz_zzz02:54
*** muralia has quit IRC03:01
*** muralia has joined #osic03:02
*** JRobinson__ has quit IRC03:04
*** JRobinson__ has joined #osic03:08
*** karthikp has joined #osic03:08
*** nadeem has joined #osic03:11
*** prometheanfire has quit IRC03:22
*** prometheanfire has joined #osic03:23
*** karthikp has quit IRC03:31
*** karthikp has joined #osic03:32
*** karthikp has quit IRC04:05
*** nadeem has quit IRC04:10
*** rmevans has quit IRC04:17
*** asettle has quit IRC04:17
*** asettle has joined #osic04:18
*** asettle has quit IRC05:02
*** asettle has joined #osic05:03
*** asingh has quit IRC05:08
*** asingh has joined #osic05:16
*** asingh has quit IRC05:17
*** JRobinson__ is now known as JRobinson__afk05:39
*** JRobinson__afk is now known as JRobinson__06:15
*** asettle has quit IRC06:20
*** asettle has joined #osic06:33
*** asettle has quit IRC06:37
*** woodster_ has quit IRC06:57
*** mdfuller has quit IRC07:16
*** JRobinson__ has quit IRC07:28
*** asettle has joined #osic07:42
*** asettle has quit IRC07:45
*** alex_xu has quit IRC09:32
*** alex_xu has joined #osic09:36
*** mdfuller has joined #osic10:18
*** alex_xu has quit IRC10:55
*** alex_xu has joined #osic10:57
*** muralia_ has joined #osic11:20
*** muralia has quit IRC11:22
*** sfinucan has joined #osic11:33
*** alex_xu has quit IRC11:41
*** alex_xu has joined #osic11:43
*** jhesketh has quit IRC12:07
*** jhesketh has joined #osic12:07
*** ravikamachi has joined #osic12:31
*** mdfuller has quit IRC12:41
*** sigmavirus24_awa is now known as sigmavirus2412:47
*** jimbaker has quit IRC13:14
*** jimbaker has joined #osic13:17
*** jimbaker has quit IRC13:17
*** jimbaker has joined #osic13:17
*** inc0 has joined #osic13:19
dstanekdolphm: so basically with key-mgmt spec we want to implement SAML2 so that we don't need an Apache module?13:22
clacomornings13:23
*** mdfuller has joined #osic13:30
*** inc0 has quit IRC13:30
lbragstado/13:30
electrocucarachamorning13:30
*** inc0 has joined #osic13:31
dstanekmorning13:31
*** b3rnard0_away is now known as b3rnard013:33
*** rderose has joined #osic13:37
*** KrishR has joined #osic13:37
sigmavirus24electrocucaracha: probably has the most memorable name here13:38
sigmavirus24also, good morning all13:38
*** KLevenstein has joined #osic13:38
electrocucarachahahaha at least helps to identify me13:38
sigmavirus24maybe also no\name\entername  (to avoid highlighting them unnecessarily)13:38
electrocucarachasigmavirus24: I assume that you speak spanish13:38
sigmavirus24Just a little13:39
electrocucarachajust enough to know what electrocucaracha means haha13:39
*** homerp_ has joined #osic13:39
sigmavirus24Exactly :D13:40
*** rderose has quit IRC13:47
*** mdfuller has quit IRC13:47
sarafrajmorning13:47
*** homerp_ has quit IRC13:48
*** woodburn1 has joined #osic13:49
*** rderose has joined #osic13:49
*** homerp_ has joined #osic13:50
*** woodburn has quit IRC13:50
*** mdfuller has joined #osic13:51
*** jthorne has joined #osic13:53
*** ametts has joined #osic13:56
*** sgundur has joined #osic13:58
sfinucankencjohnston: You here?13:59
kencjohnstonsfinucan I am...14:03
sfinucankencjohnston: Got a few questions about the decision to move to JIRA. Seems you're the person to talk to? This the right forum, if so?14:04
kencjohnstonsfinucan Any forum works, and I might not be the best but I can certainly try14:04
* kencjohnston pokes at ametts 14:05
*** cloudtrainme has joined #osic14:05
amettssfinucan: What's on your mind?14:05
sfinucankencjohnston: Here will do so :)14:06
sfinucankencjohnston: ametts: I wasn't able to attend the all hands yesterday, but it seems the decisions been made to move from Trello to JIRA for OSIC backlogs14:07
sfinucanWhile I agree that Trello is probably not scaling well, I really don't think JIRA is the right path14:07
sfinucanWould like to know how "set in stone" this decision is, and if there's any wiggle room on that14:08
sfinucanI can give my reasons/experiences, as necessary :)14:09
dolphmametts: i was curious what requirements jira fills that trello doesn't - you mentioned a lack of "structure" and something else yesterday (perhaps data insights?), but there are all sorts of trello extensions out there as well14:10
dolphmi have no issues with jira, other than the notion of having to connect to it from a whitelisted IP - that just means i won't keep jira open all day like i do with trello14:11
kencjohnstondolphm sfinucan are there trello extensions for "linking" cards into epics? That has been a pain point14:11
kencjohnstonor let me ask a better question - can you point me to some of the helpful extensions you've seen used in the past?14:12
dolphmkencjohnston: like this? https://trello.com/c/wREoDMTL/17-idfedn-identity-federation14:12
dolphmkencjohnston: i've got all the epics cross linked with their component cards14:12
amettssfinucan: Well one of the reasons we built everything out in Trello is to make sure we could take our time getting the "permanent" tool right.  The plan is to work on the best configuration we can muster, and do a pilot test of the new configuration before moving everyone.14:12
dolphmkencjohnston: i'd refer you to b3rnard0, who probably knows what's out there far better than i14:13
kencjohnstondolphm - really? Now I have to talk to b3rnard0?14:13
* kencjohnston sighs14:13
dolphmlol14:13
kencjohnstonj/k b3rnard014:13
sfinucankencjohnston: I've not much experience with Trello personally, so I certainly won't defend it or be able to suggest ways to get it fit for purpose14:14
* b3rnard0 quietly leaves through fire exit14:14
kencjohnstondolphm is there a trick/shortcut for easily referencing other cards within cards? You seem to do that prolifically and it would seem time-consuming the way I would do it14:14
kencjohnstonwhich is to go find the URL for thecard I want to reference and paste it in...14:15
dolphmkencjohnston: copy a link to card from your url bar, paste the link to that card anywhere else in plain text14:15
sfinucanI just know that JIRA has...not been pleasant for us devs to use. IMO it tries to be too many things for too many people14:16
dolphmkencjohnston: https://trello.com/c/i81m8RZS/164-trello-card-dependency14:16
b3rnard0kencjohnston: ametts: sfinucan: i'm in a meeting right now but can definitely help with questions14:16
dolphmsfinucan: that's definitely true, but i also find that true of most project organization tools :P14:16
dolphmthere's always more features than anyone needs14:16
amettssfinucan: In my own experience, I've run the gamut from super heavyweight systems, to extensive use of trello (which became a mess, eventually) -- and then landed on Jira as a happy middle ground.  It can be relatively painless if you set it up right.14:16
dolphmwhich is why people get frustrated and "just build their own," and eventually re-invent the wheel14:17
sfinucandolphm: Heh, very true14:17
sfinucanametts: dolphm: Totally true, but JIRA is an issue tracker14:17
sfinucanI've worked with tools like Pivotal Tracker, and found them much better suited to storing feature backlog14:18
dolphmsfinucan: but we're not just tracking issues, we're tracking all sorts of stuff :P14:18
amettsdolphm:  true -- the key is to configure it in the way you want to use it, and hide the complexity you don't want or need.14:18
sfinucandolphm: My point exactly14:18
sfinucan:)14:18
dolphmametts: kencjohnston: are y'all familiar with storyboard? https://storyboard.openstack.org/#!/page/about14:18
sfinucanWe have launchpad for issue tracking ;)14:18
dolphmametts: absolutely, i give jira points in that regard14:18
*** rromans_ is now known as rromans14:19
amettsJira does track issues, but also has excellent Agile storyboarding with reporting and parent-child relationships.14:19
dolphmametts: it's got a TON of complexity but you can hide al ot14:19
dolphma lot*14:19
kencjohnstondolphm I am, I talked to the Storyboard folks at the Ops Summit14:20
amettsIn any case, we'll solicit feedback with a pilot configuration before trying to do a big bang and move everyone.14:20
inc0dolphm, but jira has a vim plugin;)14:20
kencjohnstonsadly, it is not ready for prime time, they don't even have proper install docs last time I checked14:20
dstanekinc0: for what?14:21
amettsTrello is super-convenient for devs, but when you're trying to manage two-dozen projects and 150 people, it lacks a few things. :)14:21
dolphmkencjohnston: that might be the first time i've heard of anyone wanting to deploy it for themselves (and thus looking for install docs)14:21
inc0https://github.com/mnpk/vim-jira-complete14:21
dolphmkencjohnston: i'm sure we could deploy it if we want to invest in the project -- long term, openstack sorely needs something besides launchpad14:21
kencjohnstondolphm funny story, the install docs, at the time had you install an apt package that wasn't even for their software. whoops.14:21
dstanekinc0: that's an interesting idea14:22
kencjohnstonthat might be fixed now, when I pointed it out to them there was much embarrassment.14:22
dolphmkencjohnston: i believe that14:22
dolphmdstanek: i knew you'd jump on that14:23
inc0I myself ended up writing yaml -> jira issue management14:23
sfinucandolphm: dogfooding _the_ OpenStack issue tracker sounds like a good idea14:23
inc0we can make common efford and make proper vim plugin;) then it will be as good as we want it to be14:23
sfinucanthough maybe a bit too much effort when we need something now :)14:23
dolphmsfinucan: referring to launchpad or storyboard?14:23
*** KLevenstein has quit IRC14:24
sfinucandolphm: storyboard14:24
kencjohnstonsfinucan the current install docs read - verbatim - "Install StoryBoard. [TODO: More details]"14:24
kencjohnstonhttp://docs.openstack.org/infra/storyboard/install/manual.html14:24
sfinucankencjohnston: eek. Maybe not yet...14:25
kencjohnstonBut yes if we want to have a crack team working on the side to setup an instance I'd like to support that effort and use it eventually.14:25
*** Mudpuppy has joined #osic14:25
sfinucanEh, main point I'm trying to make is to take a long hard look before committing to JIRA14:25
*** Mudpuppy has quit IRC14:25
dolphmjust looking at the list of requirements, it needs a mysql server, a wsgi server, and probably somewhere to send mail - deployed!14:25
sfinucanI mean, it's certainly not free and in my experience it's definitely not the best tool for agile-y feature tracking14:25
*** Mudpuppy has joined #osic14:25
dolphmkencjohnston: did you ever get it installed?14:26
kencjohnstondolphm nope.14:26
kencjohnstonI didn't try much after my first failure though.14:27
kencjohnstontbf14:27
amettssfinucan:  Will do.  And we definitely want you to provide feedback on any pilot or test configurations we put up.14:27
sfinucanametts: Sure thing14:28
*** spotz_zzz is now known as spotz14:28
*** asingh has joined #osic14:28
sfinucanametts: and is there a path forward if people like me start whining about JIRA? :)14:28
kencjohnstonsfinucan ear plugs? :)14:29
sfinucani.e. other tools you'll consider (again - Pivotal has been the best I've seen, but per dolphm there are many options)14:29
sfinucan:D14:29
dolphmsfinucan: pivotal is a cool name, let's use that :D14:30
hockeynutthis is for bug tracking and not a Trello replacement?14:30
dolphmhockeynut: as a trello replacement, yes14:30
* hockeynut sheds a tear14:30
sfinucanhockeynut: Yeah, we have Launchpad for bugs for better or worse14:30
dasmgood morning14:30
kencjohnstonsfinucan Pivotal link?14:31
sfinucankencjohnston: http://www.pivotaltracker.com/why-tracker/14:31
amettssfinucan:  We'll certainly try to get ourselves to the best possible place -- just keep in mind that devs aren't the only stakkeholders.... so any tool not only has to be good for running the boards, but needs good aggregation features, reporting, administration tools, etc.14:31
hockeynutwe used this back in the early days of Barbican.  Moved to JIRA before I got familiar with it, but figured I'd toss it out there - http://www.scrumdo.com/14:32
dolphmametts: how is trello not meeting those needs?14:32
sfinucankencjohnston: long story short - it's _designed_ for agile workflows, rather than issue tracking w/ agile tacked on14:32
*** karthikp has joined #osic14:33
sfinucanametts: Totally understand. Balance between what PMs want and what devs want is key14:33
*** mdfuller has quit IRC14:34
kencjohnstonright, gotcha. I'm not an expert on any of these tools but I do think there is a valid concern that using Jira out of the box is as ametts described too "heavyweight"14:34
kencjohnstonsounds like there is also concern that no matter what we try we might not be able to make it "mediumweight"14:35
kencjohnstonor is it welterweight?14:35
* kencjohnston is obviously not a boxer14:35
sigmavirus24since osic is doing sprints, sprint.ly might work better in the workflow14:37
sigmavirus24it has subtasks too14:37
sigmavirus24also ways to define tasks as blocked by other tasks14:37
*** spotz is now known as spotz_zzz14:38
sigmavirus24(which last I checked neither PT nor Trello have)14:38
kencjohnstonthanks sigmavirus2414:38
* sigmavirus24 is likely irritating b3rnard0 by bringing up his knowledge of "agile" tooling :P14:39
sigmavirus24(aka fulfilling his designed role in the #osic channel)14:39
*** spotz_zzz is now known as spotz14:41
sfinucankencjohnston: Exactly. Let's try avoid paying any support contracts til you've got the right tool :P14:41
sfinucankencjohnston: ametts: ...and thanks for taking the input on board too! :)14:41
amettsdolphm: Between you, me, and the fencepost (and the 109 other people on this channel), I'm not completely unhappy with the way Trello is working for us right now.  We don't have everything we want from a reporting standpoint , but I do plan to spend some time with the APIs between now and whatever is next.  We're sorta doing the parent-child epic stuff in a kludgey way, which will probably bite us eventually.14:43
amettssfinucan: certainly!14:43
hockeynutTrello does have a thriving plugin ecosystem as well14:44
hockeynut(and the opportunity to hack something together if we need something more fit to purpose might be a fun hackday project)14:44
*** mdfuller has joined #osic14:45
amettshockeynet:  Yes... we should definitely make sure we can't morph into what we want through plugins and the APIs.14:45
amettsAnd by doing the JIRA stuff on the side, we can have something to compare against and choose what's best for everyone.14:46
*** ametts has quit IRC14:48
b3rnard0sfinucan: ametts: i'm definitely interested in helping out where i can. what types of metrics are we looking at tracking? i've been able to extract CFD and cycle time and other metrics directly from Launchpad. (thanks to sigmavirus24)14:48
hockeynutmaybe an etherpad is in order to brainstorm what we need?  IRC discussions tend to fade into the ether14:48
kencjohnstonb3rnard0 any luck getting those metrics from Trello?14:49
*** ametts has joined #osic14:49
b3rnard0kencjohnston: yup14:49
b3rnard0trello, github, and launchpad14:49
kencjohnstonhockeynut - not really ether... http://eavesdrop.openstack.org/irclogs/%23osic/ but I get your point14:49
sigmavirus24hockeynut: do you want user stories to find a metrics tool?14:50
sigmavirus24That seems silly :P14:50
sfinucanAn etherpad would be a good idea14:51
b3rnard0kencjohnston: i really think there's more value in tracking kanban based metrics to offer the type of forecasting we are looking to have for the various osic projects. and since the bulk of the work happens in launchpad, we may be able to keep trello and still track the things launchpad14:51
hockeynutkencjohnston yes, that's true.  I just tend to find IRC as a great starting point for discussions, then we take them elsewhere to fine tune.14:51
sfinucanagain - what devs want are very different to what PMs want. Got to satisfy both audiences to get paid ;)14:51
rosmaitasfinucan: vidyo won't let me write in the chat for some reason, just wanted to say: fight the good fight!14:53
b3rnard0tracking the work in the least disruptive way is always a plus. i've had adoption challenges when you end up creating too many overheads for teams, i.e., having to update Launchpad while having to maintain a second or third tracking tool14:54
*** ediardo has joined #osic14:54
*** sigmavirus24 is now known as sigmavirus24_awa14:55
*** sigmavirus24_awa is now known as sigmavirus2414:55
hockeynutb3rnard0 you got the key there "least disruptve"14:56
*** ametts has quit IRC14:57
dstaneki wish we could treat trello/jira/whatever more like just an organizational/reporting tool rather than a place that needs my attention in addition to community tools14:57
hockeynutwe don't want to get to the point where we have "status" as a deliverable :-)14:57
*** ametts has joined #osic14:58
*** mdfuller has left #osic14:58
b3rnard0hockeynut: +114:59
sfinucan+114:59
*** woodster_ has joined #osic15:00
b3rnard0if there is good team adoption, trello or whatever tool we use could provide enough status to circumvent "status" reports. we know developer x is working on 2 bugs because those are assigned to him/her, etc.15:00
kencjohnstonb3rnard0 +115:03
hockeynut+ oo15:03
spotzheheh15:04
sfinucanb3rnard0: but if you don't have pretty graphs, does it matter? ;)15:04
spotzb3rnard0 can make pretty graphs!15:04
b3rnard0sfinucan: my main point is that you can get pretty graphs with very litte disruption :-)15:04
hockeynutb3rnard0 if not, its a SMOP15:06
hockeynut*SMOP = Simple Matter Of Programming15:06
b3rnard0if we know an osic team x has a specific cycle time that amounts to about 10 bug smashes per week over time, we can use that to forecast future work and scope. we can also use a cfd to determine if things are going hairy or not15:07
b3rnard0the business side will always want to know what we can do by a certain date so the bulk of that information can be extracted from launchpad activity right now.15:08
kencjohnstonb3rnard0 the team works on more than bugs...15:10
b3rnard0kencjohnston: i realize that, it's just an example15:10
*** onthecly has joined #osic15:13
*** anush_ has joined #osic15:19
*** dwalleck has joined #osic15:19
hockeynutanyone else out there a fan of mind maps?15:19
hockeynutI've been using xmind for a few years and love it (was using MindManager before that).  Great for note taking, brainstorming, etc15:20
dstanekhockeynut: xmind is one of my favorite tools15:20
dstanekhockeynut: i use it at conferences to record my notes15:21
hockeynutdstanek EXACTLY!15:21
anushi use xmind too dstanek and hockeynut15:24
nortmanI like org-mode in Emacs.15:24
hockeynutI always publicize it to teams I'm working on in the hope that maybe it would be a good collaboration tool, but IIRC the brainstorming mode would require folks to upgrade to Pro (which I find a bargain at $99)15:24
nortmanThere's something that can generate mind maps from org files.15:25
*** alex_xu has quit IRC15:25
sfinucankencjohnston: b3rnard0: yeah, let's keep bug tracking out of whatever we use15:25
anushnortman emacs FTW15:25
lbragstaddstanek hockeynut how is the free version?15:25
dstaneklbragstad: great15:26
lbragstaddstanek is that what you used or did you pay for it?15:26
hockeynutthe basic functionality is all there in the free version..  I paid for the extras (more export options, etc).  http://www.xmind.net/pricing/15:27
dstaneklbragstad: i paid because i wanted presentation mode and the export options, but i don't really use those anymore15:27
lbragstaddstanek I've been trying to find a good tool for taking notes at the summits15:27
hockeynutlbragstad its brilliant for that!15:27
*** cloudtrainme has quit IRC15:28
dstanekfor a while i was using mindjet on my android devices because it exported to xmind, but the interface just didn't do it for me15:28
pdardeauputting tools debate aside, i'm most shocked at reading that we're doing agile and sprints15:28
*** alex_xu has joined #osic15:29
sfinucanpdardeau: ooh, controversial15:29
sfinucanpdardeau: I've a lot of opinions here. What's your thoughts on the matter15:29
pdardeaugiven my limited experience with osic and openstack, i don't think it bears any resemblance to agile or sprints15:30
pdardeaumaybe it's just cause i have different definitions of agile and sprint15:30
sfinucanpdardeau: Couldn't agree more. It's a pity ankurgupta isn't here15:31
pdardeautruth be told, i believe things are closer to waterfall (in many ways) than to agile15:31
*** cloudtrainme has joined #osic15:31
pdardeauand that waterfall is not necessarily an evil word15:31
dstanekpdardeau: i think sprints can work fine to carve up and execute stories, but the review process is where we may get hung up15:32
sfinucanpdardeau: It's 50:50, IMO. We do a lot of upfront planning, but once the cycle starts we do seem to be quite adaptive15:32
anushpdardeau - given my even limited experience with osic and openstack, doesnt each release get split into 6 week iterative releases until it gets to production15:33
anushcertainly not a true agile process15:33
sfinucandstanek: When we started in OSIC, we did something like Kanban15:34
anushbut we seem to build a release iteratively through these 6 week cadences15:34
sfinucanYou had a rough idea of what you were working on, and added stories (all bug fixing-related) as they popped up15:34
*** jlwhite has joined #osic15:34
sfinucanvs. knowing exactly what you were doing for the next two weeks15:34
pdardeauthe process i see is nearly the same as i saw in mainframe development 20 years ago (no joke)15:35
sfinucanIMO, it worked exceptionally well when you were subject to the influence of outside parties15:35
pdardeauwithout the community interaction15:35
hockeynutthere are blueprints which act as a kind of epic but beyond that it really isn't terribly agile15:35
sfinucanfrom the perspective of reviews (this comment has come in and I need to address it *now*) or customers (customer X need help with Y)15:36
sfinucanscrum, with its two week fixed cycles, really doesn't work by comparison15:37
sfinucan...though that's just my 2cents anyway15:37
pdardeauanush: btw, i haven't seen 6 week releases in swift15:37
b3rnard0scrum is very particular methodology that doesn't work for most environments/teams. believe, i've tried! ;-)15:38
*** dwalleck has quit IRC15:38
sigmavirus24kencjohnston: I got the sense that the team didn't work on bugs as part of OSIC FYI15:38
kencjohnstonsigmavirus24 uhh.. no we work on bugs15:39
anushhttp://releases.openstack.org/newton/schedule.html pdardeau15:39
anushnot sure how close this is followed across the projects15:39
sigmavirus24kencjohnston: ah, then they just don't get prioritized? I've tried to suggest some in the past and told that the priority list wasn't exactly for bugs15:40
sigmavirus24¯\_(ツ)_/¯15:40
hockeynutI would think management of an opensource project where contributors are generally on their own schedule would make sticking to *any* methodology a challenge15:41
sfinucanb3rnard0: It works excellently if you own the entire process https://github.com/adobe/brackets/wiki/Release-Notes:-Sprint-3815:41
palendaehockeynut: Yep, but OSIC doesn't seem to want contributors owning their schedule15:42
mwturveyb3rnard0: I've also see it work really well at Intel, but only when you have the support of management.  Totally failed when management tried to define a detailed agile "process"15:42
anush+1 mwturvey - with flow charts that is :-)15:43
*** jlwhite has quit IRC15:44
*** jlwhite has joined #osic15:44
mwturveyanush LOL-- 20-page powerpoint eye charts with detailed flow diagrams, gate keepers, etc. <shudders>15:44
b3rnard0sfinucan: can we say we'll own the entire process for the osic work?15:46
b3rnard0flow charts is what makes it agile :-D15:46
sfinucanb3rnard0: not even close. At the very least, we're beholden unto cores/other reviewers15:47
sfinucanIn my case, customers w/ support requests also15:47
sfinucanA well-groomed backlog and a good tracker for work planned and in flight will never go amiss though, regardless of what you want to call that15:48
*** asingh has quit IRC15:49
*** asingh has joined #osic15:49
* sfinucan dashes off to a meeting15:52
*** sfinucan has left #osic15:52
sigmavirus24hockeynut: that's why so many companies have problems with upstream developers though. This is why Mirantis threatens its employees with termination if a feature isn't completed by end of $cycle15:53
hockeynutinteresting...15:53
*** mdfuller has joined #osic15:54
b3rnard0sigmavirus24: +115:54
sigmavirus24The Artifacts work in glance was driven by threats to the employees working on it and their please to the rest of us15:54
*** dolphm_bot has joined #osic16:00
dolphm_botlbragstad, navidp, rderose, sonus: Keystone standup!16:00
dolphm_botWhat are you working on today, and what do you need help with?16:00
lbragstadtoday I'm working on more capstone deploying tooling. I'm also looking at the remaining issues for getting fernet to be the default for keystone.16:01
*** ccneill has joined #osic16:01
dstaneki am looking at the SAML2 story and the relevant spec16:01
*** ametts has quit IRC16:01
*** jlwhite_ has joined #osic16:02
*** jlwhite has quit IRC16:02
*** jlwhite_ has quit IRC16:02
*** jlwhite_ has joined #osic16:03
*** dwalleck has joined #osic16:03
*** jlwhite_ has quit IRC16:07
*** jlwhite has joined #osic16:07
rderosetoday I'm pushing up a couple bug patches and finishing setting up my dev environment using Intel's cloud16:11
dolphm_botThank you, dstanek, lbragstad, rderose!16:15
*** dolphm_bot has quit IRC16:15
*** dwalleck has quit IRC16:16
*** jlwhite has quit IRC16:16
*** jlwhite has joined #osic16:16
*** ametts has joined #osic16:17
*** dwalleck has joined #osic16:20
*** anush_ has quit IRC16:23
*** anush_ has joined #osic16:24
*** asingh has quit IRC16:24
*** onthecly has quit IRC16:24
*** onthecly has joined #osic16:25
*** jlwhite has quit IRC16:27
*** jlwhite has joined #osic16:28
*** jlwhite has quit IRC16:29
*** jlwhite has joined #osic16:30
*** jlwhite has quit IRC16:30
*** jlwhite has joined #osic16:30
*** karthikp has quit IRC16:32
*** karthikp has joined #osic16:33
*** nadeem has joined #osic16:36
*** nadeem has quit IRC16:36
*** david-lyle has quit IRC16:36
*** nadeem has joined #osic16:37
*** KLevenstein has joined #osic16:37
*** karthikp has quit IRC16:37
*** karthikp has joined #osic16:38
kencjohnstonHappy Release Day Everyone! http://www.openstack.org/software/mitaka/16:40
*** karthikp has quit IRC16:41
*** karthikp has joined #osic16:41
spotzwoot!16:42
*** karthikp has quit IRC16:44
*** karthikp has joined #osic16:44
*** nadeem has quit IRC16:47
*** karthikp has quit IRC16:50
*** karthikp has joined #osic16:51
*** asingh has joined #osic16:51
*** karthikp has quit IRC16:52
*** jlwhite has quit IRC16:52
*** jlwhite has joined #osic16:52
*** karthikp has joined #osic16:52
*** cloudtrainme has quit IRC16:57
*** asingh has quit IRC17:01
*** asingh has joined #osic17:01
*** karthikp has quit IRC17:02
electrocucaracha\o/17:02
*** david-lyle has joined #osic17:06
*** ametts has quit IRC17:07
*** jlwhite has quit IRC17:07
*** onthecly has quit IRC17:09
*** david-lyle has quit IRC17:11
*** karthikp has joined #osic17:13
*** david-lyle has joined #osic17:17
*** nadeem has joined #osic17:20
*** ametts has joined #osic17:20
*** nadeem has quit IRC17:21
*** david-lyle has quit IRC17:23
*** nadeem has joined #osic17:26
*** anush_ has quit IRC17:32
*** anush_ has joined #osic17:33
*** anush_ has quit IRC17:50
*** anush_ has joined #osic17:50
lbragstadpumaranikar https://www.openstack.org/summit/austin-2016/summit-schedule/events/6868?goback=117:57
*** david-lyle has joined #osic17:58
*** pushkaru has joined #osic17:58
*** cloudtrainme has joined #osic18:01
*** anush_ has quit IRC18:02
*** mdfuller has quit IRC18:03
*** onthecly has joined #osic18:04
*** onthecly has quit IRC18:05
*** rahulunair has joined #osic18:08
*** ankur-gupta-f has joined #osic18:11
*** mdfuller has joined #osic18:14
*** anush_ has joined #osic18:19
dstanekdolphm: let me know when you have a few mins to discuss a card18:19
*** ccneill has quit IRC18:22
*** mdfuller has quit IRC18:23
*** homerp_ has quit IRC18:23
*** ccneill has joined #osic18:31
sigmavirus24dstanek: can I guess the card? Is it the Queen of Hearts/18:34
*** homerp_ has joined #osic18:36
dstanekace of spades18:39
*** dwalleck has quit IRC18:41
clacowell now I have to go listen to that album18:49
*** dwalleck has joined #osic18:49
*** dwalleck has quit IRC19:00
*** pushkaru has quit IRC19:03
*** david-lyle_ has joined #osic19:13
*** david-lyle has quit IRC19:15
*** sigmavirus24 is now known as sigmavirus24_awa19:17
kencjohnstonclaco https://www.youtube.com/watch?v=iqu132vTl5Y ?19:19
*** david-lyle_ has quit IRC19:19
*** pushkaru has joined #osic19:21
*** david-lyle has joined #osic19:29
*** david-lyle has quit IRC19:31
*** david-lyle has joined #osic19:31
*** david-lyle has quit IRC19:37
*** cloudtrainme has quit IRC19:37
*** ccneill has quit IRC19:38
*** ccneill has joined #osic19:39
*** jlwhite has joined #osic19:51
*** alex_xu has quit IRC19:54
*** rderose has quit IRC19:55
*** alex_xu has joined #osic19:55
*** rderose has joined #osic19:55
*** anush_ has quit IRC19:58
*** anush_ has joined #osic20:00
*** ametts has quit IRC20:01
*** cloudtrainme has joined #osic20:08
*** ametts has joined #osic20:17
*** karthikp has quit IRC20:29
*** jthorne_ has joined #osic20:31
*** jthorne has quit IRC20:31
*** ametts has quit IRC20:41
*** david-lyle has joined #osic20:56
*** rderose has quit IRC20:58
*** nadeem has quit IRC20:59
*** rderose has joined #osic21:00
*** Mudpuppy has quit IRC21:18
*** KLevenstein_ has joined #osic21:18
*** Mudpuppy has joined #osic21:19
*** KLevenstein has quit IRC21:21
*** KLevenstein_ is now known as KLevenstein21:21
*** rderose has quit IRC21:21
*** rderose has joined #osic21:22
*** Mudpuppy has quit IRC21:23
*** karthikp has joined #osic21:23
*** spotz is now known as spotz_zzz21:30
*** b3rnard0 is now known as b3rnard0_away21:35
*** karthikp has quit IRC21:35
*** karthikp has joined #osic21:36
*** homerp_ has quit IRC21:36
*** dwalleck has joined #osic21:38
*** karthikp has quit IRC21:41
*** cloudtrainme has quit IRC21:41
*** karthikp has joined #osic21:41
*** asingh has quit IRC21:41
*** asingh has joined #osic21:42
*** ravikamachi has quit IRC21:48
*** karthikp has quit IRC21:50
*** karthikp has joined #osic21:50
*** rderose has quit IRC21:51
*** jthorne_ has quit IRC21:51
*** rderose has joined #osic21:51
*** jlwhite has quit IRC21:52
*** jlwhite has joined #osic21:52
*** jlwhite_ has joined #osic21:59
*** karthikp has quit IRC21:59
*** karthikp has joined #osic22:00
*** jlwhite has quit IRC22:02
*** nadeem has joined #osic22:03
*** pushkaru has quit IRC22:08
*** jplopezgu_ has joined #osic22:10
*** dani_castellanos has joined #osic22:11
*** dwalleck has quit IRC22:11
*** ediardo has quit IRC22:11
*** lcazares has joined #osic22:14
*** asingh has quit IRC22:14
*** ntpttr_ has joined #osic22:14
*** mmotiani_ has joined #osic22:15
*** ntata- has joined #osic22:17
*** saisrikiran has joined #osic22:17
*** jlwhite_ has quit IRC22:18
*** inc0 has quit IRC22:19
*** JRobinson__ has joined #osic22:19
*** JRobinson__ has quit IRC22:20
*** jlwhite_ has joined #osic22:20
*** sneti_ has joined #osic22:21
*** aunnam_ has joined #osic22:22
*** nadeem has quit IRC22:31
*** cloudtrainme has joined #osic22:31
*** cloudtrainme has quit IRC22:32
*** rderose has quit IRC22:32
*** cloudtrainme has joined #osic22:32
*** ntpttr_ has quit IRC22:35
*** dani_castellanos has quit IRC22:35
*** sneti_ has quit IRC22:35
*** lcazares has quit IRC22:35
*** saisrikiran has quit IRC22:35
*** jplopezgu_ has quit IRC22:35
*** mmotiani_ has quit IRC22:35
*** ntata- has quit IRC22:35
*** aunnam_ has quit IRC22:35
*** cloudtrainme has quit IRC22:37
*** aunnam_ has joined #osic22:37
*** jplopezgu_ has joined #osic22:38
*** kprabhuv has joined #osic22:38
*** dani_castellanos has joined #osic22:38
*** ntpttr_ has joined #osic22:40
*** lcazares has joined #osic22:42
*** pumarani- has joined #osic22:42
*** mmotiani_ has joined #osic22:43
*** saisrikiran has joined #osic22:43
*** ntata- has joined #osic22:43
*** jlwhite_ has quit IRC22:46
*** sneti_ has joined #osic22:47
*** KrishR has quit IRC23:05
*** smurke_ has joined #osic23:05
*** KLevenstein has quit IRC23:12
*** muralia_ has quit IRC23:19
*** muralia has joined #osic23:19
*** vjmorale has joined #osic23:20
*** aunnam_ has quit IRC23:22
*** smurke_ has quit IRC23:22
*** kprabhuv has quit IRC23:22
*** dani_castellanos has quit IRC23:22
*** saisrikiran has quit IRC23:22
*** mmotiani_ has quit IRC23:22
*** vjmorale has quit IRC23:22
*** sneti_ has quit IRC23:22
*** ntata- has quit IRC23:22
*** ntpttr_ has quit IRC23:22
*** lcazares has quit IRC23:22
*** jplopezgu_ has quit IRC23:22
*** pumarani- has quit IRC23:22
*** akrish9 has joined #osic23:23
*** akrish9 has quit IRC23:23
*** akrish9 has joined #osic23:23
*** jplopezgu_ has joined #osic23:25
*** dani_castellanos has joined #osic23:26
*** lcazares has joined #osic23:26
*** mmotiani_ has joined #osic23:27
*** akrish9 has quit IRC23:27
*** dani_castellanos has quit IRC23:27
*** jplopezgu_ has quit IRC23:27
*** mmotiani_ has quit IRC23:27
*** lcazares has quit IRC23:27
*** nadeem has joined #osic23:29
*** anush_ has quit IRC23:43
*** ccneill has quit IRC23:50

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