Thursday, 2015-02-19

*** dttocs has quit IRC00:09
*** markvoelker has quit IRC00:19
*** shamail has quit IRC00:25
*** sarob has quit IRC00:27
*** stevelle has joined #openstack-meeting-400:31
*** david-lyle is now known as david-lyle_afk00:41
*** ajmiller has quit IRC00:43
*** stevelle has left #openstack-meeting-400:45
*** markvoelker has joined #openstack-meeting-400:52
*** dannywilson has quit IRC00:56
*** GavinPratt_ has quit IRC00:57
*** GavinPratt has quit IRC00:57
*** markvoelker has quit IRC00:59
*** sigmavirus24 is now known as sigmavirus24_awa01:02
*** banix has joined #openstack-meeting-401:04
*** ivar-laz_ has quit IRC01:25
*** ivar-lazzaro has joined #openstack-meeting-401:26
*** ivar-lazzaro has quit IRC01:28
*** markvoelker has joined #openstack-meeting-401:29
*** ivar-lazzaro has joined #openstack-meeting-401:29
*** banix has quit IRC01:30
*** ivar-lazzaro has quit IRC01:40
*** ivar-lazzaro has joined #openstack-meeting-401:41
*** s3wong has quit IRC01:50
*** krtaylor has joined #openstack-meeting-402:09
*** banix has joined #openstack-meeting-402:16
*** klamath has quit IRC02:19
*** Aish has joined #openstack-meeting-402:22
*** SridharRamaswam1 has quit IRC02:25
*** salv-orlando has quit IRC02:40
*** banix has quit IRC02:44
*** banix has joined #openstack-meeting-402:52
*** galstrom_zzz is now known as galstrom03:23
*** salv-orlando has joined #openstack-meeting-403:41
*** banix has quit IRC03:41
*** yamahata has quit IRC03:54
*** jckasper has joined #openstack-meeting-403:56
*** jckasper has quit IRC03:56
*** jckasper has joined #openstack-meeting-403:56
*** mwang2 has quit IRC03:57
*** Aish has left #openstack-meeting-404:01
*** fnaval has quit IRC04:04
*** galstrom is now known as galstrom_zzz04:09
*** fnaval has joined #openstack-meeting-404:17
*** mwang2 has joined #openstack-meeting-404:24
*** ivar-laz_ has joined #openstack-meeting-404:25
*** ivar-lazzaro has quit IRC04:29
*** ivar-laz_ has quit IRC04:30
*** salv-orlando has quit IRC04:31
*** markvoelker has quit IRC04:42
*** markvoelker has joined #openstack-meeting-404:42
*** markvoelker has quit IRC04:46
*** asselin_ has joined #openstack-meeting-405:00
*** asselin_ has quit IRC05:02
*** ajmiller has joined #openstack-meeting-405:06
*** markvoelker has joined #openstack-meeting-405:13
*** markvoelker has quit IRC05:17
*** VW_ has joined #openstack-meeting-405:19
*** yamahata has joined #openstack-meeting-405:19
*** VW_ has quit IRC05:21
*** VW_ has joined #openstack-meeting-405:22
*** numan has joined #openstack-meeting-405:31
*** mwang2 has quit IRC05:34
*** mwang2 has joined #openstack-meeting-405:37
*** mwang2_ has joined #openstack-meeting-405:45
*** mwang2 has quit IRC05:47
*** mwang2_ has quit IRC05:51
*** mwang2 has joined #openstack-meeting-405:54
*** zigo has quit IRC05:54
*** zigo has joined #openstack-meeting-405:55
*** mwang2 has quit IRC06:02
*** markvoelker has joined #openstack-meeting-406:13
*** salv-orlando has joined #openstack-meeting-406:15
*** SridharRamaswamy has joined #openstack-meeting-406:16
*** markvoelker has quit IRC06:18
*** SridharRamaswam1 has joined #openstack-meeting-406:21
*** SridharRamaswamy has quit IRC06:22
*** belmoreira has joined #openstack-meeting-406:26
*** VW_ has quit IRC06:28
*** dannywilson has joined #openstack-meeting-406:34
*** SridharRamaswam1 has quit IRC06:40
*** dannywilson has quit IRC06:41
*** dannywilson has joined #openstack-meeting-406:42
*** yamahata has quit IRC06:51
*** yamahata has joined #openstack-meeting-406:52
*** markvoelker has joined #openstack-meeting-407:14
*** pkoniszewski has joined #openstack-meeting-407:19
*** markvoelker has quit IRC07:19
*** fnaval has quit IRC07:21
*** salv-orlando has quit IRC07:26
*** VW_ has joined #openstack-meeting-407:27
*** VW_ has quit IRC07:27
*** VW__ has joined #openstack-meeting-407:28
*** kobis has joined #openstack-meeting-408:14
*** markvoelker has joined #openstack-meeting-408:15
*** markvoelker has quit IRC08:20
*** salv-orlando has joined #openstack-meeting-408:25
*** evgenyf has joined #openstack-meeting-408:37
*** salv-orlando has quit IRC08:52
*** salv-orlando has joined #openstack-meeting-408:52
*** matrohon has joined #openstack-meeting-409:14
*** markvoelker has joined #openstack-meeting-409:16
*** dannywilson has quit IRC09:18
*** markvoelker has quit IRC09:21
*** salv-orlando has quit IRC09:29
*** salv-orlando has joined #openstack-meeting-409:33
*** VW__ has quit IRC09:34
*** yamahata has quit IRC09:39
*** VW_ has joined #openstack-meeting-409:39
*** VW_ has quit IRC09:48
*** VW_ has joined #openstack-meeting-409:49
*** pkoniszewski has quit IRC10:08
*** markvoelker has joined #openstack-meeting-410:17
*** palendae has quit IRC10:21
*** markvoelker has quit IRC10:22
*** palendae has joined #openstack-meeting-410:26
*** numan has quit IRC10:36
*** numan has joined #openstack-meeting-410:37
*** VW_ has quit IRC10:39
*** rfolco has joined #openstack-meeting-410:42
*** pkoniszewski has joined #openstack-meeting-410:50
*** VW_ has joined #openstack-meeting-411:07
*** salv-orlando has quit IRC11:11
*** salv-orlando has joined #openstack-meeting-411:12
*** markvoelker has joined #openstack-meeting-411:18
*** markvoelker has quit IRC11:23
*** VW_ has quit IRC11:25
*** VW_ has joined #openstack-meeting-411:27
*** VW_ has quit IRC11:27
*** VW_ has joined #openstack-meeting-411:28
*** salv-orlando has quit IRC11:31
*** bobmel has quit IRC11:31
*** bobmel has joined #openstack-meeting-411:31
*** salv-orlando has joined #openstack-meeting-411:31
*** kobis has quit IRC11:35
*** kobis has joined #openstack-meeting-411:35
*** pkoniszewski has quit IRC11:47
*** mwang2 has joined #openstack-meeting-411:59
*** mwang2 has quit IRC12:03
*** wojdev has joined #openstack-meeting-412:03
*** wojdev has quit IRC12:03
*** banix has joined #openstack-meeting-412:16
*** banix has quit IRC12:19
*** dannywilson has joined #openstack-meeting-412:19
*** markvoelker has joined #openstack-meeting-412:19
*** dannywilson has quit IRC12:23
*** markvoelker has quit IRC12:24
*** VW_ has quit IRC12:29
*** VW_ has joined #openstack-meeting-412:30
*** salv-orlando has quit IRC12:31
*** salv-orlando has joined #openstack-meeting-412:31
*** numan has quit IRC12:36
*** SridharRamaswamy has joined #openstack-meeting-412:38
*** salv-orlando has quit IRC12:40
*** salv-orlando has joined #openstack-meeting-412:41
*** SridharRamaswamy has quit IRC12:42
*** VW_ has quit IRC12:47
*** salv-orlando has quit IRC12:49
*** pkoniszewski has joined #openstack-meeting-412:52
*** galstrom_zzz is now known as galstrom12:54
*** markvoelker has joined #openstack-meeting-413:02
*** ajmiller has quit IRC13:30
*** stevelle has joined #openstack-meeting-413:35
*** sballe__ has quit IRC13:37
*** markvoelker_ has joined #openstack-meeting-413:42
*** markvoelker has quit IRC13:42
*** palendae has quit IRC13:48
*** palendae has joined #openstack-meeting-413:49
*** salv-orlando has joined #openstack-meeting-413:50
*** sigmavirus24_awa is now known as sigmavirus2413:52
*** galstrom is now known as galstrom_zzz13:54
*** klamath has joined #openstack-meeting-413:55
*** klamath has quit IRC13:55
*** klamath has joined #openstack-meeting-413:56
*** lakshmiS has joined #openstack-meeting-414:02
*** lakshmiS has quit IRC14:07
*** VW_ has joined #openstack-meeting-414:22
*** banix has joined #openstack-meeting-414:23
*** VW_ has quit IRC14:26
*** banix has quit IRC14:30
*** banix has joined #openstack-meeting-414:32
*** VW_ has joined #openstack-meeting-414:33
*** palendae has quit IRC14:38
*** markvoelker_ has quit IRC14:38
*** palendae has joined #openstack-meeting-414:38
*** salv-orlando has quit IRC14:39
*** markvoelker has joined #openstack-meeting-414:39
*** salv-orlando has joined #openstack-meeting-414:40
*** kobis has quit IRC14:41
*** kobis has joined #openstack-meeting-414:41
*** hemanth__ has joined #openstack-meeting-414:46
*** fnaval has joined #openstack-meeting-414:46
*** hemanth__ is now known as hemanthm14:46
*** pennerc has joined #openstack-meeting-414:48
*** TravT has joined #openstack-meeting-414:50
*** krykowski has joined #openstack-meeting-414:54
*** carl_baldwin has joined #openstack-meeting-414:57
*** yamahata has joined #openstack-meeting-414:57
*** jokke_ has joined #openstack-meeting-414:58
*** rosmaita has joined #openstack-meeting-414:59
kragnizglancers?15:00
*** ativelkov has joined #openstack-meeting-415:00
nikhil_k#startmeeting Glance15:00
openstackMeeting started Thu Feb 19 15:00:28 2015 UTC and is due to finish in 60 minutes.  The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
ativelkovo/15:00
*** openstack changes topic to " (Meeting topic: Glance)"15:00
openstackThe meeting name has been set to 'glance'15:00
mfedosinyup15:00
jokke_o/15:00
kragnizo/15:00
stevelleo/15:00
mfedosino/15:00
nikhil_khttps://etherpad.openstack.org/p/glance-team-meeting-agenda15:00
rosmaitao/15:00
*** lakshmiS has joined #openstack-meeting-415:01
nikhil_kLet's get started15:01
*** TravT_ has joined #openstack-meeting-415:01
nikhil_k#topic Glance review guidelines15:01
*** openstack changes topic to "Glance review guidelines (Meeting topic: Glance)"15:01
nikhil_khemanthm: mfedosin ?15:01
mfedosinokay15:01
mfedosinbefore I begin I have some good news15:01
hemanthmnikhil_k, o/15:01
*** wayne_ has joined #openstack-meeting-415:02
mfedosinNow we have a dedicated technical writer for Glance15:02
kragnizwoo!15:02
mfedosiner name is Lena and she has big experience in writing documentation - over 7 years.15:02
TravT_\o/15:02
jokke_ \\o \o/ o// o/715:02
mfedosinUnfortunately she's on vacation this week, but I hope next time she can join us and introduce herself.15:02
kragnizthat sounds great15:02
nikhil_kNice, good news indeed15:03
mfedosinyeah, she's good15:03
rosmaitamfedosin: that is really good news, we need someone to get the docs straightened out15:03
*** TravT has quit IRC15:03
pkoniszewskio/15:03
mfedosinso, about review guide...15:03
pennerco/15:03
mfedosinI want to show you draft of the review guidelines. It still needs some work, but you can read it and leave your comments.15:04
mfedosinhttps://docs.google.com/document/d/1Iia0BjQoXvry9XSbf30DRwQt--ODglw-ZTT_5RJabsI/edit?usp=sharing15:04
mfedosinI think Hemanth as a author can say a couple of words about it15:05
mfedosinI have several questions:15:05
*** dannywilson has joined #openstack-meeting-415:05
mfedosinDo we need examples there? And what kind of...15:05
sigmavirus24o/15:05
mfedosin1. example of good and bad code15:05
mfedosin2. successful corrections15:06
mfedosin3. bad reviews15:06
mfedosinAnd do we need another paragraphs there?15:06
hemanthmIf we want it to be educational, I'd say lets leave examples there15:06
nikhil_kSince this is the first draft. 1 -> good to have but not necessary15:06
sigmavirus24Yeah I think examples will help more than hurt15:07
hemanthmat least for some glance specific practices  like wrapping and reraising exceptions15:07
nikhil_kcan you please elaborate on 2 ?15:07
kragnizmore examples are good15:07
sigmavirus24Yeah 2 is a bit vague15:07
mfedosinnikhil_k, links for good reviews15:08
mfedosinand 3 links for bad reviews15:08
nikhil_kah15:08
nikhil_kI don't think we want 315:08
ativelkovstatus:merged should be such a link15:08
hemanthmhehe15:08
lakshmiSi think some troubleshooting tips/scenarios will be good if it helps in the context15:08
mfedosinativelkov, ;)15:08
nikhil_kwe can have something that says what are nitpicks , corner cases, some bikeshedding examples, etc15:09
hemanthmlakshmiS, good idea but that can do in the dev guide maybe? mfedosin is going to talk about it next15:09
hemanthm*can go15:09
*** dannywilson has quit IRC15:09
jokke_mfedosin, hemanthm: Is there a reason to have the non-glance-specific stuff there to keep in sync rather than improving the OS wiki regarding those?15:09
lakshmiShemanthm, as long as it's there in some doc, that will be helpful15:09
nikhil_kbut we *DONOT* want to point out someone publicaly and condemn them15:10
mfedosinhemanthm, yes, so I think we need 1, and reject 2 and 315:10
hemanthmjokke_, yeah we could always point to appropriate wikis, but the idea was to share a few commonly found patterns and then link to the wikis for more info15:11
nikhil_kNew reviewers are not going to like that and our objective is, to be inclusive as far as possible15:12
mfedosinjokke_, Hemanth is right. There is a small description of this guide and what is is for...15:12
kragnizis this planned to be placed on the wiki at some point?15:13
hemanthmkragniz, yes, that's the idea15:13
kragnizcool15:13
mfedosinand as I mentioned all your thoughts  and suggestions are appreciated :)15:14
sigmavirus24The other thing we might want to do is discuss certain special cases15:14
jokke_I would prefer the approach that Hacking doc has as in just header pointing to the OS general guidelines, and telling to read them first, then reading them again and then coming back to the glance specific stuff (keeping the later part as small as possible)15:14
sigmavirus24So I was reviewing one of sabari's changes in glance_store and learned that for driver-specific changes, nova asks the driver name be first (which contradicts with the general style guide)15:15
sigmavirus24do we want to do the same, etc15:15
sigmavirus24(that's the value add I see in doing this separately first)15:15
hemanthmsigmavirus24, +1, could you please add any special cases you are aware of15:16
jokke_sigmavirus24: could you explain this "nova asks the driver name be first"? Be first where, how?15:16
sigmavirus24hemanthm: well I think they're things we should decide as a community which is why I brought that up15:16
sigmavirus24jokke_: so in the subject it would be "VMware: Do x y z and update foo bar bogus"15:17
nikhil_k== sigmavirus2415:17
sigmavirus24That breaks the general style rule of "Imperative subjects" i.e. "Change VMWare driver to do x y z and update foo bar bugs"15:17
nikhil_kOur commits are often not par with such standards but we've improving for sure15:17
sigmavirus24On the one hand: The former gives the reader an immediate understanding that this is VMWare specific, on the other it breaks with the generic style guide15:18
nikhil_kiiuc, that is a general git rule15:18
nikhil_ksigmavirus24: I think openstack breadth asks for breaking that rule15:18
jokke_sigmavirus24: well I think that's the problem ... it gives impression something being VMWare specific, which it might not be15:18
nikhil_kjokke_: that would be a corner case when you change the interface code15:19
nikhil_kI think we need to move on15:19
sigmavirus24yeah15:19
nikhil_kLet's discuss this on the docs/comments/email etc15:20
* sigmavirus24 didn't mean for this to be a full discussion at this point in time15:20
sigmavirus24email is best15:20
sigmavirus24:)15:20
nikhil_k#topic Glance developer documentation15:20
*** openstack changes topic to "Glance developer documentation (Meeting topic: Glance)"15:20
jokke_nikhil_k: looking how much we have refactoring around oslo etc. I think it has been more rule than exception for example on our vmware driver lately :P15:20
nikhil_kjokke_: ah ok15:20
mfedosinyep15:20
nikhil_kmfedosin: any specific inputs on this topic?15:20
mfedosinhttps://docs.google.com/a/mirantis.com/document/d/10OVbGkVTYOIF9_SnXHWlupiQBaVGIBtbroP0jewgPsU/edit?usp=sharing15:20
mfedosinThere is not so much currently, but you already can get a picture what it'll be.15:20
sigmavirus24mfedosin: need access15:21
kragnizmfedosin: it wants access15:21
nikhil_kmfedosin: can you please move that to google domain?15:21
nikhil_kit's on mirantis one, atm15:21
mfedosindone15:21
mfedosinsorry :)15:21
nikhil_knp15:21
mfedosinWe started it with Lena last week and there will be 4 or 5 parts.15:22
ativelkov#link https://docs.google.com/document/d/10OVbGkVTYOIF9_SnXHWlupiQBaVGIBtbroP0jewgPsU/edit15:22
mfedosinFirst one about Architecture like http://docs.openstack.org/developer/nova/devref/architecture.html but much better :)15:22
kragnizmfedosin: looks pretty nice!15:23
* jokke_ likes the first impression ... thanks115:23
mfedosinSecond is optional and I have some concerns about its including in the documentation. It's  about inner structure of glance utils like scrubber, pruner and replicator. I suppose not so many people need this kind of documentation and if they need, they can easily find out for themselves.15:23
*** ivasilevskaya has joined #openstack-meeting-415:23
mfedosinThird is about structure of domain and its layer. Plus there will be Repo API and description of Factory, Gateway and Image class15:23
mfedosin*layers15:24
sigmavirus24mfedosin: this sounds awesome15:24
mfedosinForth for what domain model is. Proxy classes and Helpers15:24
kragnizI really like the high level view15:24
mfedosinAnd the last one describes DB API and organization of the tables.15:24
nikhil_kmfedosin: Looks really good.15:25
TravT_This is really great!15:25
mfedosinthanks, it will be better15:25
nikhil_kWe may want to avoid showing DB schema like this (created manually)15:25
kragnizthis is going to be part of the glance documentation?15:26
nikhil_kIf we can get some doc strings on the schema specification in the code, that would be better15:26
hemanthmWhile this is really useful, documentation like this tends to go out of sync very quickly if we don't maintain it. That's definitely a cost involved with it15:26
mfedosinyes, I see15:26
mfedosinhemanthm, and that's why we have Lena as a technical writer15:27
nikhil_kyeah, also the pipeline makes it difficult to determine the correlation of the doc with the deployment15:27
jokke_while there is cost involved I really like that ... this is like first human readable version of what's going on there I've seen ;)15:27
mfedosinYou can look and comment as well as the review guide. Everyone is welcome.15:28
sigmavirus24mfedosin++ Lena++15:28
TravT_schema could be generated by raw output from describing it.15:28
mfedosinyes, but I want it to be pretty looked picture15:29
nikhil_kjokke_: true but human readable does not guarantee the authenticity and that can be bad sometimes15:29
mfedosinbut I agree - maintain all the migrations is annoying15:30
nikhil_kfor example the image status transitions are not complete here http://docs.openstack.org/developer/glance/statuses.html15:30
sigmavirus24:(15:30
mfedosinAnd also I want to know about the timing. Until what date should it be completed?15:31
nikhil_kmfedosin: yes, good point15:31
kragnizmfedosin: having it for the kilo release would probably be great15:31
sigmavirus24Do we want it in time for the summit so we can show it off?15:31
nikhil_kmfedosin: I don't think we have a _completion_ date however, good to have a small first version (minimal style)15:31
sigmavirus24or what kragniz said ;)15:31
mfedosin13, March?15:31
nikhil_ksure15:31
sigmavirus24should we set a k-1 milestone for it before that to solicit feedback on a near-final draft?15:32
kragnizsigmavirus24: shipping it with kilo would be kindest to ops :P15:32
nikhil_kk3 you mean?15:32
sigmavirus24kragniz: wait, you mean ops aren't just imaginary things? They're real humans? *mindblown* =P15:32
kragnizsigmavirus24: k3 you mean?15:32
sigmavirus24kragniz: well k-1 would be the milestone for the document, doesn't need to coincide with k-315:32
sigmavirus24it can15:32
nikhil_kI don't think we can timeslide back15:33
kragnizsigmavirus24: k1 has been and gone :P15:33
sigmavirus24well we're releasing the document for kilo15:33
nikhil_kyes, so k315:33
sigmavirus24the document's development didn't start with the rest of kilo15:33
mfedosinbtw, what will be after Z?15:33
sigmavirus24so document-relative k-115:33
nikhil_kthose are informal milestones so do not matter officially15:33
mfedosinA again?15:33
sigmavirus24mfedosin: AA ;)15:33
sigmavirus24then AB, then AC =P15:33
mfedosinthen we have to wait 13 years15:34
* sigmavirus24 doesn't actually know15:34
nikhil_kgreek characters15:34
nikhil_kwe need to move on15:34
sigmavirus24nikhil_k: by then certainly everyone will support unicode ;)15:34
mfedosinnikhil_k, :D15:34
nikhil_k#topic stable/juno requirements sync with global requirements15:34
*** openstack changes topic to "stable/juno requirements sync with global requirements (Meeting topic: Glance)"15:34
nikhil_kativelkov: ?15:34
ativelkovyup15:34
jokke_#link https://review.openstack.org/#/c/154728/15:34
ativelkovah, great15:35
jokke_that's capping the requirements (finally)15:35
ativelkovjust wanted to ask what is the correct practice here15:35
jokke_ativelkov: bot proposes, we verify that it does not break the hell loose and merge ;)15:36
ativelkovis that the same for stable branches?15:36
nikhil_kalso, we are midful about the release date and freeze time15:36
nikhil_kmindful*15:36
sigmavirus24ativelkov: yes mostly because unexpected releases have been breaking things (see: half of oslo and eventlet for examples)15:37
jokke_ativelkov: bot proposes to the stable/* just stable team +2+2+A15:37
nikhil_kativelkov: there was some discussion about not having to maintain 3 branches simultaneously. You might want to be on the lookout there. Try asking in cross project meetings on the upto data info.15:37
ativelkovgot it, thanks15:38
sigmavirus24there's also a discussion on the ML about how we maintain stable/* requirements lists in openstack/requirements15:38
jokke_nikhil_k: I think the unfortunate reality what has been promised to explore is 4 releases when Kilo comes out :(15:38
sigmavirus24(you might notice some of these deps are equivalent to pins)15:38
nikhil_kjokke_: wow, that's not fun!15:39
kragnizjokke_: the more releases, the more fun!15:39
nikhil_kcan we move one?15:39
jokke_nikhil_k: it's transition, but still15:39
jokke_I think so15:39
ativelkovyup15:39
nikhil_kthanks15:39
nikhil_k#topic Abandoning stale PS from review15:39
*** openstack changes topic to "Abandoning stale PS from review (Meeting topic: Glance)"15:39
nikhil_kjokke_: was that you?15:39
jokke_yeah15:39
nikhil_khttp://comments.gmane.org/gmane.comp.cloud.openstack.devel/4635215:40
nikhil_khttps://etherpad.openstack.org/p/glance-cleanout-of-inactive-PS15:40
jokke_so Nova is doing this automated (IIUC) after 4 weeks, Swift is sending chase e-mail out after 4 weeks and abandoning manually if no activity in 2 weeks from that15:40
jokke_The take from the mailing list and X-project meeting at Tue was that it's reasonable and at least for now there won't be OS wide governing for this15:41
*** banix has quit IRC15:41
kragnizjokke_: I thought nova stopped doing the automated abandon?15:41
jokke_kragniz: at least what I understood from sdague's comment at tue it's scripted15:42
jokke_kragniz: OS stopped the automatic 2week abandon which was on all15:42
kragnizokay15:42
* sigmavirus24 wonders if there's a way to automate a message to the ML asking for sponsors for older patch sets before abandoning15:42
nikhil_kplease no, that would create so much spam15:43
kragnizsigmavirus24: the question is more can you do that without annoying everyone15:43
jokke_sigmavirus24: I'd certainly not spam mailing list with any automation like that15:43
sigmavirus24kragniz: it should be obvious that I care not about annoying people ;)15:43
nikhil_kheh15:43
kragnizI personally think the older reviews are not causing any trouble15:44
nikhil_kjokke_: worth creating a poll on the ML discussion?15:44
* sigmavirus24 realizes that it's probably best just to set up a collection of dashboards for people to use 15:44
jokke_also the main concern on the mailing list feedback in short was that someone might hurt their feelings if we drop their change after they have not responded to us for weeks ... which was at least on X-proj meeting pretty much discarded15:44
kragnizsigmavirus24: (plug for http://goo.gl/eS05pD)15:45
nikhil_kheh, I think gerrit can support such a filter (but not sure if one already exists/can be enabled)15:45
jokke_again using automated filters removes all flexibility and smartness ... makes the situation just worse15:45
ativelkovIf I remember correctly, the concern was also about loosing real user-stories if we abandon something15:46
*** fnaval has quit IRC15:46
jokke_if someone wakes up at the point when the change gets abandoned there is simple way to restore it without hassle15:46
nikhil_kyes, that's the case. However, if we can omit WIP patch sets from being abandoned then it would solve it, right?15:46
nikhil_kand that can be mentioned in the good practice guideline15:47
ativelkovWe may suggest the reviewers to create a launchpad bug or BP (if relevant) before abandoning the changes, so noce-to-have features remain in backlog15:47
kragnizjokke_: yes, but it's a harder for someone else to find it later if it's abandoned15:47
*** ajmiller has joined #openstack-meeting-415:47
nikhil_kok, we need to move on15:47
nikhil_kLet's continue on the ML for now and get back on this next week if necessary15:47
*** mdorman has joined #openstack-meeting-415:48
nikhil_k#topic Catalog Index service reviews15:48
*** openstack changes topic to "Catalog Index service reviews (Meeting topic: Glance)"15:48
nikhil_khttps://etherpad.openstack.org/p/catalog-index-service15:48
TravT_On the follow page is a little diagram showing the patches related to index service: https://etherpad.openstack.org/p/catalog-index-service15:48
TravT_You might need to zoom out a bit for the diagram to render correctly15:48
TravT_One is really just an update on metadefs functionality (adding notifications), but is pretty much ready: https://review.openstack.org/#/c/148546/15:48
TravT_Others are functionally very close to completion and serious test writing is starting up.15:49
nikhil_khttps://review.openstack.org/#/c/148546/15:49
TravT_Would be much better to get reviews now so comments can be addressed before the mad end of cycle zuul rush where it takes multipe days to just check a patch.15:49
nikhil_kcool, so we need reviews15:49
* sigmavirus24 was working on that yesterday I think15:49
nikhil_k#help review catalog index service patches15:50
TravT_Thanks!15:50
nikhil_kTravT_: do we have more updates or should we move on?15:50
nikhil_k#topic glanceclient sorting15:50
*** openstack changes topic to "glanceclient sorting (Meeting topic: Glance)"15:50
*** klindgren__ has joined #openstack-meeting-415:50
nikhil_kPlease help mfedosin review https://review.openstack.org/#/c/120777/15:50
*** rackertom has joined #openstack-meeting-415:50
nikhil_kThat was my addition and that's pretty much it for now.15:51
mfedosincurrently we don't have support for sorting in glance client15:51
jokke_mfedosin: when did that break?15:51
mfedosinthis patch implement it15:51
jokke_mfedosin: or is our sorting done on the API server end?15:52
mfedosinin v2 there is no sorting15:52
mfedosinin client15:52
nikhil_kanyways, we can discuss this on the review itself15:53
nikhil_k#topic Reviews for zero downtime config reload15:53
*** openstack changes topic to "Reviews for zero downtime config reload (Meeting topic: Glance)"15:53
mfedosinthanks :) I will be appreciate15:53
nikhil_kI think we need to get some feedback to these folks15:53
nikhil_khttps://review.openstack.org/#/c/127238/15:54
nikhil_khttps://review.openstack.org/12218115:54
nikhil_k#topic Open discussion15:54
*** openstack changes topic to "Open discussion (Meeting topic: Glance)"15:54
kragnizwe need reviews on the last couple of glanceclient patches for the next release15:55
nikhil_kkragniz: do you have links handy so that people can see in the meeting logs?15:55
kragniz#link https://launchpad.net/python-glanceclient/+milestone/v0.16.015:55
nikhil_kcool15:55
jokke_nikhil_k: quick update request, what's the status on our client and store releases?15:55
nikhil_kgood enough15:55
mfedosinfolks, there is my spec about new sorting syntax https://review.openstack.org/#/c/155841/ can you check it out?15:55
nikhil_kfor store we were waiting on stuart's patch for ativelkov 's copy-from fix15:55
kragnizalso15:56
kragniz#link https://review.openstack.org/#/c/157372/15:56
nikhil_kbut we can release today if that's not ready15:56
kragniznikhil_k: stuart's not going to have that ready in time15:56
hemanthmnikhil_k, reminder:  maintainer for glance_store15:56
nikhil_kokay15:56
nikhil_koh yes15:56
wayne_any thoughts on this one would be appreciated: https://review.openstack.org/#/c/154229/15:56
nikhil_kis anyone willing to volunteer as a maintainer for glance_store repo15:56
ativelkovA question to sigmavirus24 and rosmaita: are we done with the semver discussion? :)15:56
nikhil_kthat way we can have multiple point of contacts for the release process15:57
kragnizsigmavirus24: would that be mostly release management?15:57
hemanthmnikhil_k, I'd be interested15:57
nikhil_k hemanthm, you were interested, right?15:57
nikhil_kokay, thanks15:57
nikhil_kanyone else?15:57
sigmavirus24ativelkov: if the plan is to support something in a broader scheme after adding semver (to at least get artifacts rolling) that's fine15:57
jokke_nikhil_k: I think I have my hands full with current promises ;)15:57
kragniznikhil_k: I can do release stuff15:57
ativelkovsigmavirus24: exactly15:57
sigmavirus24Otherwise I still object to the fact that we're limiting artifacts versioning to such an extremely narrow group of potential users (since semver has no users at the moment, all users are potential)15:58
nikhil_kativelkov: it's upto sigmavirus24 now. rosmaita and I are on agreement15:58
*** alaski has joined #openstack-meeting-415:58
*** b3rnard0 has joined #openstack-meeting-415:58
sigmavirus24s/semver/artifacts/15:58
nikhil_kjokke_: ok, thanks!15:58
nikhil_kkragniz: noted15:58
nikhil_k#action add kragniz and hemanthm for glance_store release management15:58
sigmavirus24nikhil_k: I can help if necessary but it sounds like hemanthm and kragniz are good15:58
ativelkovnikhil_k: could you please comment on https://review.openstack.org/#/c/151466/ ? It has got 2 +2 but no +A, and it is blocking us15:59
sigmavirus24ativelkov: probably people are waiting for the spec to be approved first15:59
kragnizwe're out of time, so move to #openstack-glance?15:59
jokke_ok, time!15:59
jokke_Thanks all15:59
*** fnaval has joined #openstack-meeting-416:00
nikhil_kativelkov: yes, I was waiting on the discussion. Thanks for the reminder!16:00
nikhil_kThanks all..16:00
nikhil_k#endmeeting16:00
kragnizthanks16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
ativelkovthanks!16:00
openstackMeeting ended Thu Feb 19 16:00:16 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-02-19-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-02-19-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-02-19-15.00.log.html16:00
*** pennerc has left #openstack-meeting-416:00
*** wayne_ has left #openstack-meeting-416:00
*** cloudnull has joined #openstack-meeting-416:00
VW_now, on to large deployments... :)16:00
* sigmavirus24 waits for os-ansible-deployment to start16:01
rosmaitasigmavirus24: where are you located that's -15 degrees?16:01
sigmavirus24rosmaita: MSN16:01
b3rnard0#startmeeting OpenStack Ansible Meeting16:01
openstackMeeting started Thu Feb 19 16:01:49 2015 UTC and is due to finish in 60 minutes.  The chair is b3rnard0. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: OpenStack Ansible Meeting)"16:01
*** Apsu has joined #openstack-meeting-416:01
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:01
*** jokke_ has left #openstack-meeting-416:01
b3rnard0#link https://wiki.openstack.org/wiki/Meetings/openstack-ansible#Agenda_for_next_meeting16:02
b3rnard0#topic RollCall16:02
*** rosmaita has left #openstack-meeting-416:02
*** openstack changes topic to "RollCall (Meeting topic: OpenStack Ansible Meeting)"16:02
*** ivasilevskaya has left #openstack-meeting-416:02
cloudnullpresent16:02
b3rnard0presente16:02
stevellepresent16:02
VW_hmm - we have meeting room conflict16:02
sigmavirus24gift16:02
*** lakshmiS has quit IRC16:02
sigmavirus24VW_: os-ansible-deployment has had this room for >1 month I think16:03
*** mattt has joined #openstack-meeting-416:03
palendaepresent16:03
VW_yeah, we had it back in December16:03
VW_but we are alternating timeslots16:03
*** erikmwilson has joined #openstack-meeting-416:03
sigmavirus24VW_: interesting we haven't run into each other yet16:03
b3rnard0VW_: what time is your meeting?16:04
*** alextricity has joined #openstack-meeting-416:04
alextricityMorning16:04
sigmavirus24o/ alextricity16:04
*** david-lyle_afk is now known as david-lyle16:04
VW_16:00 UTC, sigmavirus24 / b3rnard016:04
VW_it's new as of December, though16:04
VW_you guys carry on16:04
VW_I'll see what I can do to work around16:05
b3rnard0VW_: sorry about the confusion16:05
mdormanVW_:  reasonable to move to #openstack-operators?16:05
d34dh0r53presente16:05
b3rnard0cloudnull: we didn't have any action items from last week, do we want to just jump onto contributor guidelines discussion?16:06
*** Sam-I-Am has joined #openstack-meeting-416:06
Sam-I-Amhi16:06
belmoreiraVW_: fine for me16:07
VW_cool16:07
b3rnard0thanks VW_16:07
*** git-harry has joined #openstack-meeting-416:07
cloudnullVW_ belmoreira mdorman i dont see anything on https://wiki.openstack.org/wiki/Meetings for your meeting at this time, but we can move our meeting to another time slot / room moving forward if needed.16:08
b3rnard0#action b3rnard0 Make sure there are no meeting conflicts and update meeting time if necessary.16:08
cloudnullany who, lets get started?16:09
VW_nah - we'll sort it out, cloudnull16:09
cloudnullalright, sorry for the confusion :)16:09
cloudnullso lets get right into Contributor guidelines discussion16:10
b3rnard0#topic Contributor guidelines discussion16:10
*** openstack changes topic to "Contributor guidelines discussion (Meeting topic: OpenStack Ansible Meeting)"16:10
b3rnard0#link https://etherpad.openstack.org/p/ansible-contrib16:10
cloudnullmancdaz started ^16:10
*** mdorman has left #openstack-meeting-416:10
cloudnulli think we need to lay out specific guidelines for contributions and begin adhering to them.16:11
cloudnulland i know that i've been part of the problem16:11
cloudnullso moving forward, i like where this is going. but i'd like to get everyone to start looking at that and add bits that may be missing.16:12
*** KLevenstein has joined #openstack-meeting-416:12
cloudnullanyone have any thoughts on taht ?16:12
cloudnullanyone here ?16:13
palendaeI agree with what mancdaz has outlined there16:13
ApsuPersonally, I think that there will probably be need for exceptions with respect to 1 blueprint = 1 feature = 1 patch set, mostly because "feature" is such a vague target.16:13
mattthere, and no real arguments w/ what is there16:14
ApsuBut I generally agree with it.16:14
ApsuThe whole blueprint/voting aspect is a given16:14
matttwe need clarification on whether features get backported too tho16:14
Sam-I-Ambluesprints/specs ?16:14
cloudnullso lets start with the etherpad and then once we have something that is mutually agreeable we should add it to the contributing guidelines.16:14
Apsu+116:15
mattt+116:15
Sam-I-AmApsu: a lot of bps generally have > 1 patch16:15
*** odyssey4me has joined #openstack-meeting-416:15
cloudnullso lets get eyes on that, and later today we'll pr to master in the contributing guidelines.16:15
Sam-I-Amsmaller patches are easier to vote on than huge ones16:16
odyssey4meo/ (sorry I'm late)16:16
cloudnullnp odyssey4me16:16
b3rnard0we forgive you odyssey4me16:16
ApsuSam-I-Am: I know, not really what I meant. I'm moreso talking about what constitutes a "feature" and whether a single bp should subsume multiple ones or not. But we can discuss that separately16:16
Sam-I-Ammmkay16:16
ApsuIf the feature is "restructure playbook style", you end up with a huge patchset. Some "features" are huge and invasive. That's what brought this issue up in the first place, so just pointing out that "feature" is vague and sometimes it hurts :)16:17
cloudnullok moving on to "Blueprints"16:18
b3rnard0#topic Blueprints16:19
*** openstack changes topic to "Blueprints (Meeting topic: OpenStack Ansible Meeting)"16:19
*** dannywilson has joined #openstack-meeting-416:19
b3rnard0#link https://blueprints.launchpad.net/openstack-ansible/+spec/additional-tempest-checks16:19
*** ativelkov has left #openstack-meeting-416:19
*** dannywilson has quit IRC16:19
cloudnullso i think that bp is in line with our whole, "if your not working on gating your not working" mantra. but the BP needs some more data.16:20
palendaeAre we conflating rackspace sprints with os-ansible-deployment goals then?16:20
b3rnard0also, did we want to start using a blueprint or spec template?16:20
hughsaundersthis patch should be more inline with that bp https://review.openstack.org/#/c/156831/16:21
cloudnullpalendae no, the integration with tempest should be a project goal .16:21
cloudnulli think if we're going to have a successful project we need better testing and per OpenStack tempest == testing.16:22
palendaeSure, not saying that16:22
palendaeI'm more confused where the mantra came from - don't remember it as part of the last os-ansible-deployment meeting16:22
palendaeAnyway16:23
*** dannywilson has joined #openstack-meeting-416:23
palendaeMore testing more good16:23
ApsuAmerica16:23
Sam-I-Amwho is testing the tests?16:23
d34dh0r53going to update that BP today to the spec format that cloudnull uses16:24
d34dh0r53btw16:24
cloudnulld34dh0r53 great16:24
ApsuSam-I-Am: Quis custodiet ipsos custodes?16:24
d34dh0r53cloudnull: I can haz link to gist?16:24
sigmavirus24== Sam-I-Am16:24
b3rnard0d34dh0r53: what is the link to the spec format so that we can add that to the guidelines?16:24
sigmavirus24Apsu: the cores are the watchpersons and the community watches them16:24
*** krtaylor has quit IRC16:25
d34dh0r53b3rnard0 meet cloudnull16:25
cloudnulld34dh0r53: https://gist.githubusercontent.com/cloudnull/91f23c49c2a86ffd1309/raw/bea7862563c53553df1eaaf490ba5d249d75b985/blueprint-template.rst16:25
Apsusigmavirus24: Slightly creepy. But I can dig it16:25
odyssey4meI think that perhaps we need to figure out, for this project, what sort of change to the project requires a blueprint and what can simply be logged as a bug.16:25
b3rnard0#link https://gist.githubusercontent.com/cloudnull/91f23c49c2a86ffd1309/raw/bea7862563c53553df1eaaf490ba5d249d75b985/blueprint-template.rst16:25
d34dh0r53👍16:25
Sam-I-Amfeatures usually = bp, bugs usually = bugs ?16:25
cloudnullso this brings up another issue around Blueprints / Specs. I feel like we should be using specs and abandon blueprints.16:25
Apsuodyssey4me: Simple. If it's a bug, fix it. If it's a feature, blueprint it. Pefectly clear, right?16:25
b3rnard0d34dh0r53: meet action item16:26
b3rnard0#action d34dh0r53 update blueprint with template from cloudnull16:26
stevelleIt seem the scope of the fix should influence that decision odyssey4me16:26
d34dh0r53thank you sir, may I have another?16:26
Sam-I-Amcloudnull: for upstream, we have a BP for general management, but it links to a spec for the actual discussion/voting16:26
cloudnullyes that ^16:26
palendaeSounds like a good appraoch. BPs don't really allow for discussion16:27
cloudnullin this way we'd have a repo of specs that people can comment and vote on.16:27
cloudnullat present the launchpad whiteboard is terribad.16:27
Sam-I-Amlaunchpad doesnt understand specs, but it does know how to manage targets and stuff.16:27
b3rnard0+1 to specs16:27
Sam-I-Amlaunchpad is the b3rnard0 of feature management16:27
hughsaunderscloudnull: could we have in-repo specs to save having another repo?16:27
b3rnard0Sam-I-Am: and you are the diagram editor for os-ansible?16:28
cloudnullhughsaunders sure.16:28
palendaehughsaunders: So we get specs on every checkout?16:28
Sam-I-Amb3rnard0: say my name!16:28
cloudnull^ palendae  beat me to my comment on that.16:28
palendaeEr, clone16:28
hughsaundersyeah, I guess they would be quite small, and it would save having another repo to keep track of16:29
hughsaundersbut git-harry tells me that all the openstack projects use external specs repos, so maybe we should follow suit?16:29
Sam-I-Ammost of the upstream projects have separate repos16:29
Sam-I-Amlike -specs16:29
odyssey4mein-repo may mean that the automated spec building may not work - assuming that this can be done for stackforge projects16:30
*** alaski has left #openstack-meeting-416:30
odyssey4mealso, perhaps the approvers for specs should be different to the approvers for the code?16:30
sigmavirus24odyssey4me: I think it can16:30
sigmavirus24odyssey4me: specs live on specs.openstack.org16:30
Sam-I-Amodyssey4me: +116:30
sigmavirus24odyssey4me: typically there's overlap but they're not the same team16:30
palendaeWell, if the goal is to be more like upstream OpenStack, then separate repos sounds like the way to go16:30
cloudnullso lets ping "jhesketh" to see about getting another repo.16:30
*** klindgren__ is now known as klindgren16:32
*** Apsu has left #openstack-meeting-416:32
*** Apsu has joined #openstack-meeting-416:32
b3rnard0#info palendae: Well, if the goal is to be more like upstream OpenStack, then separate repos sounds like the way to go; cloudnull: so lets ping "jhesketh" to see about getting another repo.16:32
b3rnard0who would like to ping jhesketh for the repo?16:33
cloudnullill hit him up today .16:33
cloudnullbut he's likely sleeping right now.16:33
cloudnullanything else we want to talk about regarding blueprints ?16:33
cloudnullok moving on16:34
b3rnard0#action cloudnull ping jhesketh about creating a separate repo16:34
b3rnard0#topic Milestones16:34
*** openstack changes topic to "Milestones (Meeting topic: OpenStack Ansible Meeting)"16:34
b3rnard0#link https://launchpad.net/openstack-ansible/+milestone/next16:34
cloudnullpresently we have 2 milestone. 10.1.2 and 9.0.716:34
cloudnullimo 10.1.2 is close to being done.16:35
cloudnullwhile 9.0.7 has a few items that need to go in, IE tempest commit_aio testing.16:35
*** BjoernT has joined #openstack-meeting-416:35
cloudnullfor the most part things are passing, that said we need reviewers.16:36
cloudnullplease do the needfuls on items in https://review.openstack.org/#/q/status:open+project:stackforge/os-ansible-deployment,n,z16:36
cloudnullthere are 7 commits for icehouse16:36
b3rnard0#link https://review.openstack.org/#/q/status:open+project:stackforge/os-ansible-deployment,n,z16:36
cloudnull5 for juno.16:37
cloudnullodyssey4me do we know when infra will can get our gate change commit in ?16:37
odyssey4mecloudnull it's been waiting in the queue since monday... I'm trying to be patient and wait for a week before starting to escalate. :p16:38
cloudnullthats fair.16:38
cloudnulli think we've bothered them a enough for a while :)16:38
odyssey4methe supposed expected time for a review to sit in the queue is 5-7 days16:39
cloudnullodyssey4me you have the link for that review .16:39
odyssey4me#link https://review.openstack.org/15622916:39
cloudnullif we can get some other reviewers on that ^ it would also be great.16:39
*** yamahata has quit IRC16:39
ApsuAlready doing16:39
cloudnullso anything else regarding present milestones?16:41
cloudnullok moving on16:42
b3rnard0#topic Open discussion16:42
*** openstack changes topic to "Open discussion (Meeting topic: OpenStack Ansible Meeting)"16:42
BjoernTSo pinning will be backported to icehouse branch and we will use the same versions as 10.1.2?16:42
cloudnullBjoernT it looks like it.16:43
odyssey4meBjoernT yes, the patches are already in-flight16:43
cloudnullodyssey4me has put through that work .16:43
cloudnull^ what odyssey4me  said :)16:43
BjoernTNice16:43
cloudnullBjoernT if you have time please review the open PRs @ https://review.openstack.org/#/q/status:open+project:stackforge/os-ansible-deployment,n,z we'd love some external feedback .16:44
odyssey4meBjoernT obviously the openstack service versions will not be the same - the pinning backport and version pin will only apply to the infrastructure16:44
BjoernTok, I'llk do16:44
BjoernTsure16:44
BjoernTis there a reason why we didn't backport 1410437 to icehouse ? or are we reducing development on 9.x ?16:45
cloudnullBjoernT 9.x is in maintenance.16:45
b3rnard0#action BjoernT to help out with reviewing open PRs https://review.openstack.org/#/q/status:open+project:stackforge/os-ansible-deployment,n,z16:45
BjoernTWhat issues are fixed in that state ?16:45
cloudnullcritical / some high16:46
cloudnullthat said odyssey4me : do we think getting that in for 9.0.7 is a worthwhile effort?16:46
BjoernTOK, we talked internally yesterday and we think 1410437 is critical (PATH missing in keystone token_flush cronjob)16:47
odyssey4mewhat are we talking about here?16:47
odyssey4meoh - the keystone path thing?16:47
BjoernTI meant the support team talked internally about what can happen to customer environments if the token table grows to big16:47
cloudnullBjoernT: from the prospective of the deployer , we dont know what pains you unless you and others join in here, in the community forum16:47
*** krtaylor has joined #openstack-meeting-416:48
odyssey4mewell, I don't think it was backported in the previous run because nobody lobbied to have that done - it was never marked as backport potential for icehouse (until today)16:48
BjoernTyes I know that's why we talked about it yesterday. is 9.0.7 already frozen?16:48
odyssey4meit's probably an easy backport16:48
BjoernTCan I mark bugs myself as backport potential ?16:48
Sam-I-Amimho, the token-flush thing is a pretty big issue16:48
stevelleaction item?16:48
odyssey4meI did try to cherry-pick through gerrit already, and it doesn't... so there's clearly a conflict.16:49
cloudnullso lets prioritize it and get it in for 9.0.716:49
*** mestery has quit IRC16:49
odyssey4meBjoernT it would often be best to include the versions that you think it applies to in the description or a follow-on message.16:49
BjoernT+116:49
cloudnullthat said , BjoernT can you talk to your team about joining the tuesday triage meeting?16:50
odyssey4meThat way the bug triage can target it in the process.16:50
BjoernTyes it is usually me but this week was bad, we will have a secondary joining16:50
odyssey4meand yeah, join the meetings and advocate16:50
cloudnullok.16:50
cloudnullanything else?16:50
BjoernTNot from me16:51
b3rnard0 thanks BjoernT16:51
cloudnullok , lets call it16:51
b3rnard0thanks everyone16:51
cloudnullthanks everyone16:51
*** IRTermite has joined #openstack-meeting-416:51
BjoernTThanks16:51
b3rnard0#endmeeting16:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:51
openstackMeeting ended Thu Feb 19 16:51:53 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:51
*** BjoernT has left #openstack-meeting-416:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-02-19-16.01.html16:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-02-19-16.01.txt16:51
*** krykowski has quit IRC16:51
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-02-19-16.01.log.html16:51
*** odyssey4me has left #openstack-meeting-416:52
*** sballe__ has joined #openstack-meeting-416:52
*** salv-orlando has quit IRC16:52
*** git-harry has left #openstack-meeting-416:52
*** Sam-I-Am has left #openstack-meeting-416:53
*** cloudnull has left #openstack-meeting-416:53
*** stevelle has left #openstack-meeting-416:53
*** erikmwilson has left #openstack-meeting-416:58
*** kobis has quit IRC16:58
*** carl_baldwin has quit IRC17:02
*** mgagne has joined #openstack-meeting-417:03
*** Mudpuppy has joined #openstack-meeting-417:05
*** yamahata has joined #openstack-meeting-417:10
*** pkoniszewski has quit IRC17:12
*** SridharRamaswamy has joined #openstack-meeting-417:27
*** banix has joined #openstack-meeting-417:34
*** SridharRamaswamy has quit IRC17:36
*** banix has quit IRC17:39
*** yapeng has joined #openstack-meeting-417:40
*** matrohon has quit IRC17:42
*** carl_baldwin has joined #openstack-meeting-417:42
*** salv-orlando has joined #openstack-meeting-417:52
*** SumitNaiksatam has joined #openstack-meeting-417:55
*** s3wong has joined #openstack-meeting-418:00
*** ivar-lazzaro has joined #openstack-meeting-418:03
*** belmoreira has quit IRC18:11
*** mwang2 has joined #openstack-meeting-418:17
*** yapeng has quit IRC18:37
*** yapeng_ has joined #openstack-meeting-418:37
*** pkoniszewski has joined #openstack-meeting-418:38
*** SridharRamaswamy has joined #openstack-meeting-418:39
*** evgenyf has quit IRC18:47
*** salv-orlando has quit IRC18:57
*** galstrom_zzz is now known as galstrom19:00
*** SridharRamaswamy has quit IRC19:02
*** SridharRamaswamy has joined #openstack-meeting-419:03
*** SridharRamaswamy has quit IRC19:05
*** s3wong has quit IRC19:10
*** mestery has joined #openstack-meeting-419:12
*** sarob has joined #openstack-meeting-419:19
*** VW_ has quit IRC19:22
*** SridharRamaswamy has joined #openstack-meeting-419:24
*** salv-orlando has joined #openstack-meeting-419:32
*** SridharRamaswamy has quit IRC19:33
*** SridharRamaswamy has joined #openstack-meeting-419:36
*** krtaylor has quit IRC19:38
*** mestery has quit IRC19:44
*** yapeng_ has quit IRC19:52
*** SridharRamaswamy has quit IRC19:54
*** TravT_ has quit IRC20:03
*** SridharRamaswamy has joined #openstack-meeting-420:08
*** VW_ has joined #openstack-meeting-420:12
*** mestery has joined #openstack-meeting-420:13
*** krtaylor has joined #openstack-meeting-420:16
*** VW_ has quit IRC20:18
*** VW_ has joined #openstack-meeting-420:19
*** rfolco has quit IRC20:22
*** VW_ has quit IRC20:31
*** yamahata has quit IRC20:51
*** mwang2 has quit IRC20:51
*** Mudpuppy has quit IRC21:02
*** mwang2 has joined #openstack-meeting-421:16
*** yapeng has joined #openstack-meeting-421:39
*** ivar-laz_ has joined #openstack-meeting-421:41
*** ivar-lazzaro has quit IRC21:43
*** ivar-laz_ has quit IRC21:46
*** ivar-lazzaro has joined #openstack-meeting-421:46
*** sarob has quit IRC21:46
*** ivar-lazzaro has quit IRC21:47
*** ivar-lazzaro has joined #openstack-meeting-421:48
*** IRTermite has quit IRC22:02
*** dannywil_ has joined #openstack-meeting-422:02
*** dannywilson has quit IRC22:04
*** SridharRamaswamy has quit IRC22:04
*** carl_baldwin has quit IRC22:07
*** carl_baldwin has joined #openstack-meeting-422:09
*** SridharRamaswamy has joined #openstack-meeting-422:10
*** openstackstatus has joined #openstack-meeting-422:15
*** ChanServ sets mode: +v openstackstatus22:15
*** klindgren has left #openstack-meeting-422:26
*** SridharRamaswamy has quit IRC22:29
*** SridharRamaswamy has joined #openstack-meeting-422:36
*** VW_ has joined #openstack-meeting-422:46
*** matrohon has joined #openstack-meeting-422:56
*** pkoniszewski has quit IRC22:58
*** dannywil_ has quit IRC23:04
*** sarob has joined #openstack-meeting-423:07
*** yapeng has quit IRC23:08
*** hemanthm has quit IRC23:15
*** KLevenstein has quit IRC23:20
*** carl_baldwin has quit IRC23:22
*** dannywilson has joined #openstack-meeting-423:30
*** bobmel has quit IRC23:31
*** bobmel has joined #openstack-meeting-423:31
*** salv-orlando has quit IRC23:39
*** salv-orlando has joined #openstack-meeting-423:40
*** carl_baldwin has joined #openstack-meeting-423:43
*** IRTermite has joined #openstack-meeting-423:44
*** carl_baldwin has quit IRC23:45
*** markvoelker has quit IRC23:49
*** wojdev has joined #openstack-meeting-423:54
*** matrohon has quit IRC23:56
*** dannywilson has quit IRC23:58

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