Wednesday, 2016-09-21

*** davidlenwell has quit IRC00:03
*** davidlenwell has joined #openstack-meeting-400:16
*** vishwanathj has quit IRC00:22
*** limao has joined #openstack-meeting-400:29
*** limao has quit IRC00:32
*** limao_ has joined #openstack-meeting-400:32
*** Sukhdev has joined #openstack-meeting-400:35
*** hujie has left #openstack-meeting-400:40
*** bobh has quit IRC00:44
*** tonytan4ever has joined #openstack-meeting-400:48
*** tonytan4ever has quit IRC00:52
*** bpokorny has joined #openstack-meeting-401:01
*** bobh has joined #openstack-meeting-401:02
*** zhurong has joined #openstack-meeting-401:13
*** bpokorny_ has joined #openstack-meeting-401:15
*** bpokorn__ has joined #openstack-meeting-401:18
*** bpokorn__ has quit IRC01:18
*** bpokorny_ has quit IRC01:18
*** bpokorny_ has joined #openstack-meeting-401:18
*** bpokorny has quit IRC01:19
*** sdake_ has joined #openstack-meeting-401:19
*** sdake has quit IRC01:21
*** britthou_ has joined #openstack-meeting-401:25
*** zhihui__ has joined #openstack-meeting-401:25
*** amotoki has joined #openstack-meeting-401:26
*** unicell has quit IRC01:27
*** britthouser has quit IRC01:28
*** Jeffrey4l has joined #openstack-meeting-401:37
*** s3wong has quit IRC01:38
*** salv-orl_ has joined #openstack-meeting-401:42
*** salv-orlando has quit IRC01:44
*** vishnoianil has quit IRC01:46
*** rainya has joined #openstack-meeting-401:49
*** tonytan4ever has joined #openstack-meeting-401:49
*** baoli has joined #openstack-meeting-401:51
*** tonytan4ever has quit IRC01:54
*** tuanla has joined #openstack-meeting-402:05
*** bobh has quit IRC02:10
*** qwebirc26281 has joined #openstack-meeting-402:13
*** qwebirc26281 has quit IRC02:20
*** bpokorny_ has quit IRC02:23
*** hemanthm|afk is now known as hemanthm02:23
*** tonytan4ever has joined #openstack-meeting-402:23
*** bpokorny has joined #openstack-meeting-402:23
*** amotoki has quit IRC02:25
*** rainya has quit IRC02:27
*** bpokorny has quit IRC02:28
*** caowei has joined #openstack-meeting-402:39
*** revon has quit IRC02:40
*** amotoki has joined #openstack-meeting-402:41
*** bobh has joined #openstack-meeting-402:43
*** amotoki has quit IRC02:49
*** amotoki has joined #openstack-meeting-402:49
*** amotoki has quit IRC02:54
*** amotoki has joined #openstack-meeting-402:58
*** jamespage has quit IRC03:00
*** jamespag` has joined #openstack-meeting-403:01
*** baoli has quit IRC03:01
*** bobh has quit IRC03:02
*** JRobinson__ is now known as JRobinson__afk03:03
*** david-lyle has quit IRC03:04
*** amotoki has quit IRC03:04
*** uxdanielle has quit IRC03:19
*** armax has quit IRC03:23
*** armax has joined #openstack-meeting-403:25
*** jiangjunyu has joined #openstack-meeting-403:27
*** JRobinson__afk has quit IRC03:33
*** jiangjunyu has quit IRC03:35
*** sdake_ has quit IRC03:42
*** rainya has joined #openstack-meeting-403:44
*** amotoki has joined #openstack-meeting-403:46
*** rainya_ has joined #openstack-meeting-403:48
*** rainya has quit IRC03:49
*** unicell has joined #openstack-meeting-403:50
*** rainya_ has quit IRC03:52
*** limao_ has quit IRC03:55
*** yingjun has joined #openstack-meeting-403:58
*** markvoelker has quit IRC04:03
*** yamamoto has joined #openstack-meeting-404:07
*** markvoelker has joined #openstack-meeting-404:10
*** syed_ has quit IRC04:13
*** Rockyg has quit IRC04:30
*** tuanla has quit IRC04:35
*** psachin has joined #openstack-meeting-404:38
*** psachin has quit IRC04:40
*** psachin has joined #openstack-meeting-404:41
*** psachin has quit IRC04:45
*** psachin has joined #openstack-meeting-404:47
*** yamamoto has quit IRC04:53
*** vishnoianil has joined #openstack-meeting-404:56
*** rainya has joined #openstack-meeting-404:58
*** limao has joined #openstack-meeting-405:04
*** prateek has joined #openstack-meeting-405:07
*** sc68cal_ has joined #openstack-meeting-405:09
*** woodster_ has quit IRC05:10
*** icey has quit IRC05:11
*** sc68cal has quit IRC05:11
*** icey has joined #openstack-meeting-405:17
*** caowei has quit IRC05:32
*** yamamoto has joined #openstack-meeting-405:38
*** unicell has quit IRC05:39
*** unicell has joined #openstack-meeting-405:41
*** JRobinson__afk has joined #openstack-meeting-405:42
*** unicell1 has joined #openstack-meeting-405:42
*** JRobinson__afk is now known as JRobinson__05:43
*** unicell has quit IRC05:43
*** gongysh has joined #openstack-meeting-405:47
*** janki has joined #openstack-meeting-405:47
*** Jeffrey4l has quit IRC05:49
*** Jeffrey4l has joined #openstack-meeting-405:51
*** caowei has joined #openstack-meeting-405:52
*** markvoelker has quit IRC06:01
*** markvoelker has joined #openstack-meeting-406:03
*** yingjun has quit IRC06:09
*** markvoelker has quit IRC06:11
*** tonytan4ever has quit IRC06:14
*** jschwarz|ooo is now known as jschwarz06:19
*** uck has quit IRC06:36
*** karthiks has joined #openstack-meeting-406:37
*** sshnaidm|afk is now known as sshnaidm06:44
*** limao has quit IRC06:48
*** limao has joined #openstack-meeting-406:49
*** liwei has joined #openstack-meeting-406:56
*** Rockyg has joined #openstack-meeting-406:56
*** tmetsch has joined #openstack-meeting-407:03
*** uck has joined #openstack-meeting-407:05
*** zenoway has joined #openstack-meeting-407:05
*** Sukhdev has quit IRC07:06
*** tmetsch has left #openstack-meeting-407:06
*** dtardivel has joined #openstack-meeting-407:09
*** uck has quit IRC07:10
*** markvoelker has joined #openstack-meeting-407:11
*** armax has quit IRC07:12
*** cartik has joined #openstack-meeting-407:12
*** pcaruana has joined #openstack-meeting-407:13
*** markvoelker has quit IRC07:16
*** matrohon has joined #openstack-meeting-407:20
*** acabot has joined #openstack-meeting-407:23
*** ricolin has joined #openstack-meeting-407:28
*** zenoway has quit IRC07:31
*** zenoway has joined #openstack-meeting-407:32
*** zenoway has quit IRC07:38
*** alexchadin has joined #openstack-meeting-407:38
*** zenoway has joined #openstack-meeting-407:40
*** salv-orlando has joined #openstack-meeting-407:42
*** tonytan4ever has joined #openstack-meeting-407:44
*** alexchadin has quit IRC07:44
*** alexchadin has joined #openstack-meeting-407:45
*** salv-orl_ has quit IRC07:45
*** tonytan4ever has quit IRC07:50
*** ifat_afek has joined #openstack-meeting-408:00
ifat_afek#startmeeting vitrage08:01
openstackMeeting started Wed Sep 21 08:01:09 2016 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot.08:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:01
*** openstack changes topic to " (Meeting topic: vitrage)"08:01
openstackThe meeting name has been set to 'vitrage_'08:01
ifat_afekhi everyone :-)08:01
*** elisha_r has joined #openstack-meeting-408:01
elisha_rHi08:01
*** eyalb has joined #openstack-meeting-408:01
eyalbhi08:01
*** idan_hefetz has joined #openstack-meeting-408:02
*** danoffek has joined #openstack-meeting-408:02
danoffekhi guys08:02
*** gongysh has quit IRC08:03
idan_hefetzHi all!08:03
ifat_afek#topic Status and Updates08:05
*** openstack changes topic to "Status and Updates (Meeting topic: vitrage)"08:05
ifat_afekNewton release schedule: As vitrage release mode in Ocata is cycle-with-intermediary, we have time until Sunday to release our final version for Newton08:05
ifat_afekI plan to do it tomorrow, and then ask to create stable/newton branch for vitrage projects.08:06
ifat_afekThe final release is scheduled for October 6.08:06
ifat_afekIn addition, I started checking our documentation. I submitted a change for adding vitrage developer guide documents under http://docs.openstack.org/developer/vitrage08:06
ifat_afek. I also want to check why vitrage bliueprints are not displayed nicely in https://specs.openstack.org/openstack/vitrage-specs/08:06
*** gongysh has joined #openstack-meeting-408:06
ifat_afekWho has other updates?08:07
elisha_rI do08:07
*** ricolin_afk has joined #openstack-meeting-408:08
elisha_rI would like to raise some thoughts and new directions regarding the entity graph horizon display, and as a result also the API support08:09
elisha_rCurrently, this screen shows the entire entity graph, regardless of size, complexity etc. As a result, for complex graphs, it is difficult to "find your way" within this graph08:09
elisha_rThis can be tackled in two ways. The first is to use smart graph layout, which will organize the graph in a more visually-appealing manner. For example, clustering vertices by type, hierarchies etc.08:11
*** ricolin has quit IRC08:11
elisha_rHowever, this approach will eventually run into difficulties as well - with large setups, this could still be TMI.08:11
elisha_rInstead, I think we should take the second approach: to present portions of the graph, allowing the user to select what types of resources/entities will be displayed08:12
elisha_rFor example, if the user selects a Heat stack, he would see the entity graph portion consisting of all the stack resources, alarms on these, and (possibly) the physical hosts of these virtual resources08:13
elisha_rselecting a different resource would show the "relevant" info for that resource08:14
ifat_afekelisha_r: interesting. so we will have a predefined set of portions?08:14
elisha_rThis, as a business-logic approach seems right to me.08:14
elisha_rifat_afek: good point, I've given that some thought as well08:15
elisha_rFor starters, we could of course have some "static" predefined scope. For example, showing everything within a few hops from the initial resource. This would not make sense "business wise", but it would still give a clearer picture of the system than what we have today08:16
ifat_afekbecause it would show a smaller graph?08:16
elisha_rExactly.08:16
elisha_rBut the real solution IMO is to build for each resource a template, just like the vitrage templates we have now, and treat this issue using subgraph matching (with some slight changes).08:17
ifat_afekcool, I like this idea08:17
ifat_afekbut it won’t be trivial to define or implement08:17
elisha_rNot so sure. To me it seems pretty straight forward. We would start of course with built-in templates. For example, you could build a structure like: stack-->instance-->host. When a user requests the heat stack entity graph, we would run subgraph matching as is starting from this stack in the graph, and it will return all the subgraphs of that structure. Then we only need to merge the graphs (simple union of sets), and w08:19
ifat_afekso you mean the api for get topology will accept a yaml file as an input?08:20
*** limao has quit IRC08:21
ifat_afekthis could work08:21
elisha_rThere is one difference from what we have in our current template matching - vitrage conditions need to match EXACTLY, whereas here we want also SUB-MATCHES of this structure. But knowing the code, I think it's a simple extension of what we have08:21
ifat_afekright08:21
elisha_rFor starters these will be in a folder, just like the vitrage templates are today, and would be added/removed manually. In the future we could allow crud, selection of policies etc - just like we plan to do with the current templates.08:22
ifat_afekcool08:22
ifat_afekI suggest we have a blueprint, and/or discuss it in the design session in Barcelona08:23
elisha_rOne last thing - I still think that having a view where we see everything is important. This view will function as a "heat-map", to detect problems or problematic "areas08:23
elisha_r"08:23
elisha_rbut perhaps there we need a different type of view.08:24
elisha_rAnyhow, yes, lets discuss it in Barcelona. Can we set up a BP with the intent of discussing it there?08:24
ifat_afekI completely agree08:24
ifat_afeksure08:24
ifat_afek#topic Preparations for Barcelona08:25
*** openstack changes topic to "Preparations for Barcelona (Meeting topic: vitrage)"08:25
ifat_afekI know that elisha_r, eyalb and myself are going to Barcelona. Anyone else?08:25
ifat_afekOpenStack published the suggested schedule for the design sessions:08:25
ifat_afek#link https://docs.google.com/spreadsheets/d/1TQ-RSlbiBBEclkonIbfUP7R1ExZSJylF1uiEKV2G_Cw/pubhtml?gid=1107826458&single=true08:25
ifat_afekI asked to move one of our Friday sessions to another day, and agreed to liberate the other one, so in total we will have three – one fishbowl session (in a bigger room) and two work rooms08:26
ifat_afekI created a new etherpad for planning the design sessions, please add your ideas:08:26
ifat_afek#link https://etherpad.openstack.org/p/vitrage-barcelona-design-sessions08:26
*** dshakhray has joined #openstack-meeting-408:27
*** limao has joined #openstack-meeting-408:27
*** JRobinson__ has quit IRC08:28
ifat_afekelisha_r and myself submitted two “brown bag” talk proposals. These are 10-minutes talks in smaller rooms than the regular sessions. We are waiting for the response.08:29
ifat_afek#topic Open Discussion08:29
*** openstack changes topic to "Open Discussion (Meeting topic: vitrage)"08:30
ifat_afekanything else?08:30
ifat_afekgoodbye then08:33
eyalbbye08:33
*** danoffek has left #openstack-meeting-408:33
ifat_afek#endmeeting08:34
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:34
openstackMeeting ended Wed Sep 21 08:34:13 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:34
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage_/2016/vitrage_.2016-09-21-08.01.html08:34
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage_/2016/vitrage_.2016-09-21-08.01.txt08:34
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage_/2016/vitrage_.2016-09-21-08.01.log.html08:34
*** eyalb has quit IRC08:36
*** ricolin has joined #openstack-meeting-408:40
*** ricolin_afk has quit IRC08:40
*** limao has quit IRC08:42
*** limao has joined #openstack-meeting-408:42
*** ricolin_afk has joined #openstack-meeting-408:43
*** ricolin_afk has quit IRC08:44
*** ricolin_afk has joined #openstack-meeting-408:45
*** ricolin has quit IRC08:47
*** elisha_r has quit IRC08:50
*** uck has joined #openstack-meeting-408:54
*** uck has quit IRC08:58
*** ifat_afek has quit IRC09:00
*** anilvenkata has joined #openstack-meeting-409:03
*** mfedosin has joined #openstack-meeting-409:21
*** idan_hefetz has left #openstack-meeting-409:25
*** ricolin_afk has quit IRC09:32
*** ricolin has joined #openstack-meeting-409:32
*** zenoway has quit IRC09:33
*** zenoway has joined #openstack-meeting-409:34
*** zenoway has quit IRC09:38
*** zenoway has joined #openstack-meeting-409:41
*** alexchadin has quit IRC09:44
*** alexchadin has joined #openstack-meeting-409:48
*** uck has joined #openstack-meeting-409:49
*** uck has quit IRC09:53
*** ricolin has quit IRC09:59
*** limao has quit IRC09:59
*** zhurong has quit IRC10:02
*** ifat_afek has joined #openstack-meeting-410:03
*** alexchadin has quit IRC10:13
*** ifat_afek has quit IRC10:15
*** ifat_afek has joined #openstack-meeting-410:19
*** jamespag` is now known as jamespage10:19
*** liuyulong__ has joined #openstack-meeting-410:25
*** liuyulong has quit IRC10:28
*** janki has quit IRC10:33
*** anilvenkata is now known as anilvenkata_afk10:34
*** sshnaidm has quit IRC10:37
*** sdague has joined #openstack-meeting-410:37
*** sshnaidm has joined #openstack-meeting-410:42
*** tonytan4ever has joined #openstack-meeting-410:46
*** Jeffrey4l has quit IRC10:50
*** Jeffrey4l has joined #openstack-meeting-410:50
*** tonytan4ever has quit IRC10:52
*** gongysh has quit IRC10:56
*** davidlenwell has quit IRC10:57
*** davidlenwell has joined #openstack-meeting-410:58
*** janki has joined #openstack-meeting-411:00
*** berendt has joined #openstack-meeting-411:03
*** rtheis has joined #openstack-meeting-411:08
*** yamamoto has quit IRC11:12
*** anilvenkata_afk is now known as anilvenkata11:15
*** baoli has joined #openstack-meeting-411:15
*** baoli_ has joined #openstack-meeting-411:18
*** baoli has quit IRC11:21
*** jed56 has quit IRC11:25
*** ifat_afek has quit IRC11:31
*** ifat_afek has joined #openstack-meeting-411:32
*** woodster_ has joined #openstack-meeting-411:40
*** sshnaidm is now known as sshnaidm|afk11:47
*** ifat_afek has quit IRC11:52
*** zhurong has joined #openstack-meeting-411:54
*** amotoki has quit IRC11:58
*** bobh has joined #openstack-meeting-411:59
*** ifat_afek has joined #openstack-meeting-412:00
*** coolsvap_ is now known as coolsvap12:00
*** ifat_afek has quit IRC12:13
*** woodard has joined #openstack-meeting-412:15
*** barmaley has joined #openstack-meeting-412:16
*** woodard has quit IRC12:17
*** kylek3h has joined #openstack-meeting-412:17
*** woodard has joined #openstack-meeting-412:17
*** wznoinsk has quit IRC12:21
*** kylek3h has quit IRC12:23
*** yamamoto has joined #openstack-meeting-412:26
*** bobh has quit IRC12:28
*** yamamoto_ has joined #openstack-meeting-412:28
*** wznoinsk has joined #openstack-meeting-412:28
*** LotharKAtt has joined #openstack-meeting-412:31
*** yamamoto has quit IRC12:32
*** sshnaidm|afk is now known as sshnaidm12:32
*** markvoelker has joined #openstack-meeting-412:33
*** barmaley has quit IRC12:33
*** cartik has quit IRC12:34
*** zhihui__ has quit IRC12:38
*** yamamoto_ has quit IRC12:42
*** automagically has left #openstack-meeting-412:43
*** zenoway has quit IRC12:44
*** zenoway has joined #openstack-meeting-412:45
*** mjturek has joined #openstack-meeting-412:46
*** yamamoto has joined #openstack-meeting-412:49
*** anilvenkata has quit IRC12:49
*** zenoway has quit IRC12:49
*** mjturek has quit IRC12:51
*** liwei has quit IRC12:54
*** cdent has joined #openstack-meeting-412:54
*** david-lyle has joined #openstack-meeting-412:56
*** krtaylor has joined #openstack-meeting-412:58
*** mriedem has joined #openstack-meeting-412:58
*** jichen has joined #openstack-meeting-412:58
alex_xu#startmeeting nova api13:00
openstackMeeting started Wed Sep 21 13:00:04 2016 UTC and is due to finish in 60 minutes.  The chair is alex_xu. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: nova api)"13:00
openstackThe meeting name has been set to 'nova_api'13:00
alex_xuwho is here today?13:00
mriedemo/13:00
cdento/13:00
edleafe\o13:00
*** liuyulong has joined #openstack-meeting-413:00
mriedemi know sdague is around13:00
johnthetubaguyo/13:00
alex_xuyea, I guess so :)13:00
sdagueo/13:01
mriedemis gmann here?13:01
jicheno/13:01
sdaguegmann is in germany I think for the infra/qa sprint13:01
mriedemah13:01
mriedemno wonder mtreinish has avoided me all week13:01
alex_xuso I didn't have specfic thing in the list, but there are have some of items from mriedem, so just let us go through your items?13:01
mriedemsure13:02
alex_xu#link https://review.openstack.org/#/c/301372/13:02
*** liuyulong__ has quit IRC13:02
alex_xumriedem: ^ the first one13:02
mriedemyeah so i need help with that one13:02
*** amotoki has joined #openstack-meeting-413:03
mriedemlike, i need some direction from sdague and/or ken'ichi13:03
mriedemon what they wanted to see there13:03
mriedembut this is the thing where the security_groups in a server create response are possibly wrong when using neutron13:03
mriedemso we want to return a link instead for security_groups13:03
johnthetubaguyshouldn't we just drop that feature in a new API version13:03
johnthetubaguyso don't add any security_groups be default? or does that break something else?13:04
sdaguemriedem: ok, this actually relates to a thing we were just talking about in #openstack-nova13:04
mriedemjohnthetubaguy: i thought about that too13:04
sdaguewhat would a real security_groups representation look like?13:04
johnthetubaguyit would look like a full proxy of neutron's APIs?13:05
alex_xulooks like just a wrap from per port to per instance13:05
johnthetubaguywhat I mean is, each port can have its own security group13:05
sdaguedo we have some examples of neutron vs nova?13:05
*** vishwanathj has joined #openstack-meeting-413:06
johnthetubaguyexamples of the current API response?13:06
sdagueok, personally I'd like to stare at the data comparisons a little bit before deciding what a best path forward is13:06
sdaguebecause we've got a related issue that a server get, with neutron service down, causes a 500, because of security group listing13:06
johnthetubaguyoh, good point13:07
sdagueand I think the eventual approach should cover both cases13:07
johnthetubaguyhonestly, it feels like security groups and floating ips should be removed from the get server response13:07
mriedemhttp://developer.openstack.org/api-ref/networking/v2/#security-groups-security-groups13:07
johnthetubaguynow that doesn't fix the older versions13:07
mriedemi feel like we're talking about different problems here,13:08
johnthetubaguyah, possibly13:08
sdaguemriedem: we are13:08
sdaguebut I think they are related13:08
mriedemthe point of the spec, and the bug, is that when creating the server, we're returning the default secgroup b/c nova adds that by default, but neutron may not actually set that up13:08
mriedemif the network doesn't have port security enabled13:08
sdaguemriedem: right13:08
mriedemso the spec was suggesting returning a link to the secgroup api for nova13:09
johnthetubaguyI guess I am questioning why nova sets the default security group any more13:09
mriedembefore 2.36 that was a proxy to neutron13:09
sdaguebut the case in both of these is that we're building a server document with information where the source of truth is from neutron13:09
*** claudiub has joined #openstack-meeting-413:09
sdagueand that goes wrong a few different ways13:09
sdaguebecause of timing, defaults, and service outages13:09
alex_xuI thought the security-group is really for nova-network13:09
sdaguealex_xu: neutron also has them, they act a little differently13:10
mriedemneutron applies a default secgroup by default i think13:10
mriedemif you have port security enabled on the network13:10
alex_xusdague: i'm curious what nova api show when we have two different security-groups for two ports which belong to one instance13:10
mriedemiff you don't provide a non-default secgroup13:10
johnthetubaguyah, that used to be us setting that, but I think we stopped doing that at some point13:11
*** bobh has joined #openstack-meeting-413:11
prateekjohnthetubaguy, regarding your comments on https://review.openstack.org/#/c/294513/18/nova/compute/api.py, what you wrote is definitely more elegant than what I did, but both excpetions had different attr when raising the exception, did that just slip by you or am I missing something13:11
mriedemprateek: we're not talking about that right now13:12
johnthetubaguyprateek: please ask questions in the nova channel, happily answer in there13:12
prateekohkk sorry13:12
prateeki didnt look at that channel13:12
mriedemso is the question if the server create response should even return security_groups at all?13:13
johnthetubaguythats where I am at, leave them out13:13
johnthetubaguyand don't allow users to pass them in, either13:13
alex_xuprefer to remove them13:13
mriedemwhy wouldn't we allow users to pass them in?13:14
mriedemthat seems odd13:14
mriedemwe allow you to pass in specific nics13:14
johnthetubaguyso it should be a per nic thing, if we wanted it13:14
johnthetubaguyreally I would want folks to set it on the port, and pass us the port_uuid13:14
sdaguejohnthetubaguy: it seems like we need to redo the expected way to pass things around13:14
mriedemcan we decouple the two issues for now?13:15
sdagueI feel like what we have is a flow from nova-network13:15
johnthetubaguysdague: yeah, +113:15
mriedemb/c my spec is not about redoing the entire server create api for how secgroups are passed in13:15
sdagueand at least 2 (probably more) issues with that flow13:15
johnthetubaguyI know, it just feels odd to allow people to pass things in, and not return them in any way13:15
sdagueand I think we should walk through what the flow should look like in the neutron world13:15
sdaguemriedem: honestly, I'm kind of -1 on doing that, because I think we're going to need to change a bunch of other stuff and there will end up being 4 microversions of fixing security groups13:16
sdaguejohnthetubaguy: do you have a more ideal flow in your head you could sketch out in an etherpad?13:17
johnthetubaguyhonestly, it feels like folks should just set this on their port outside of nova13:17
johnthetubaguyor we expand --nic to include a security group thingy, referencing the one in neutron13:18
sdaguejohnthetubaguy: ok, that's fine, can you write that up, and the point to all the ways we would change the API to enforce that?13:18
johnthetubaguyyeah, I should do that thing in some etherpad13:18
sdaguebecause this is going to unwind like the proxy deprecation did, I think there are second order impacts that will only be clear once we write the whole thing out13:18
johnthetubaguy#link https://etherpad.openstack.org/p/ocata-nova-security-groups13:18
*** klamath has joined #openstack-meeting-413:19
mriedemcan you use nova-network after 2.36? i can't remember13:19
sdagueok, lets let that churn for a couple of days13:19
mriedemhow the proxy api breaks using nova-net13:19
sdaguemriedem: you can't use nova-net after that13:20
mriedemeven on server create?13:20
mriedembecause the server api isn't deprecated13:20
sdaguewe didn't change the server representation13:20
sdaguebut the server representation never said "use_neutron"13:20
*** psachin has quit IRC13:21
mriedemright so i can create a server with nova-network and 2.latest13:21
johnthetubaguyI think you can boot an instance with default setting using nova-net, but the good stuff breaks, but I could be remembering that wrongly13:21
mriedembut if i try to list ips from that server at 2.latest with nova-network it should fail13:21
sdagueright13:21
sdaguemriedem: but server show still has them13:22
mriedemi would just like to be clear about what breaks if we change the server create api wrt secgroups13:22
sdaguemriedem: yes, agreed13:22
*** psachin has joined #openstack-meeting-413:23
mriedemok let's move on13:23
alex_xu#link https://review.openstack.org/#/c/350277/13:23
sdagueso... I think we should make security groups not be a lie with neutron, which they kind of are. I think a couple of days of johnthetubaguy and others trying to figure out where all the rough edges are will help get a handle on the problem.13:24
johnthetubaguyyeah, thats a fair summary I feel.13:24
mriedemWe have to think through this a bit since we should get it done in Ocata: https://review.openstack.org/#/c/350277/ - I like the suggestion from johnthetubaguy to model this like the volume attachments API.13:24
mriedem"Deprecate os-interface proxy API"13:24
mriedemthis is the thing we missed in 2.3613:24
mriedemwhere we have os-interface and os-virtual-interfaces13:24
mriedemos-virtual-interfaces is purely nova-net today13:25
mriedemb/c of the vifs in the nova db13:25
mriedemos-interface is the proxy to neutron for listing ports13:25
mtreinishmriedem: I've been avoiding you?13:25
mriedemand attach/detach ports13:25
johnthetubaguyyeah, it feels like the cinder volume model is what we should model for VIFs, flow wise13:26
mriedemmtreinish: yeah i've been driving by your house late at night and everything!13:26
mtreinishhah13:26
sdaguejohnthetubaguy: that seems reasonable13:26
mriedemjohnthetubaguy: yeah i like that too13:26
mriedemso you'd have basically show, list, attach/detach13:26
sdaguewe should realistically probably pile up somewhere the rest of the things we were going to deprecate but never got around to13:26
mriedemit was at least this and the image metadata proxy api13:27
mriedemoh but os-cloudpipe too and things like that13:27
*** khushbu_ has joined #openstack-meeting-413:27
alex_xualso multi-nic which johnthetubaguy point out few days ago13:28
mriedemso i think the path forward on https://review.openstack.org/#/c/350277/ is for me to rewrite it with this in mind:13:28
mriedem1. make os-interface more like os-volume_attachments13:28
johnthetubaguyyeah, there a few I keep finding when looking at the api-ref patches13:28
mriedem2. deprecate os-virtual-interface13:28
mriedemsince os-virtual-interface only works for nova-net, deprecating that shouldn't be a big deal, it should have happened in 2.3613:29
*** uck has joined #openstack-meeting-413:29
sdagueyeh, seems reasonable13:30
mriedemwe might also change os-interface GET/list to build that from the nova db model instead of a proxy to neutron13:30
mriedemi'd have to think that through13:30
mriedemwe might have to proxy for anything that was created before the 2.32 microversion13:30
mriedemanyway, i'll move forward with that and see what pits i fall into13:31
mriedemnext on the agenda:13:32
mriedemWe need someone to write a spec for supporting the standardized  (formerly v3) instance diagnostics compute API from the REST API with a  microversion, as a dependency for hyper-v to support that API: https://blueprints.launchpad.net/nova/+spec/hyperv-vm-diagnostics13:32
mriedemclaudiub was going to see if the person that was going to work on ^ was going to work on the api change13:32
mriedemi'm throwing it out here in case someone wants to get a head start on the spec13:32
mriedemthis is the thing that garyk worked on to create the standard instance diagnostics object in the virt layer13:33
mriedembut with the v3 api dropping out, we never ended up exposing that code from the REST API13:33
claudiubyeah, so that needs an api change as well. my coleague can take care of the hyper-v bits, but he's pretty loaded with tasks, and won't have enough time for the api changes, especially since ocata is so sohort13:33
mriedem#help need someone to write the spec for exposing the standardized instance diagnostics out of the REST API13:34
mriedemi guess i could get a spec started13:34
mriedemit's pretty straight-forward i think13:34
alex_xumriedem: I can do that13:34
mriedemok13:34
sdague#action alex_xu to work on generic diagnostics spec13:34
sdaguewe should also probably mark actions from before as well13:35
mriedemi think it's basically after microversion x you call nova.compute.api.API.get_instance_diagnostics13:35
alex_xuyea, i guess so13:35
mriedemsdague: i'm not sure what that means13:35
mriedemmark actions from before13:35
sdague#action johnthetubaguy to sketch out what an ideal security group workflow looks like in the nova api now with neutron as the presumed backend13:35
mriedemoh13:35
mriedemi see :)13:35
sdague#action mriedem to write up spec for os-virtual-interface deprecation13:36
mriedemnext topic13:36
sdaguethen they are recorded for revisit in next meeting13:36
mriedemDoes alex_xu have a spec for deprecating the proxy API for set/delete image metadata?13:36
mriedemalex_xu: i know you reported a bug for that13:36
alex_xumriedem: yea, I can begin to do that. so that need a separated microversion?13:37
alex_xudo we merge that with other thing we forget to deprecate? like multi-nic?13:37
mriedemalex_xu: we could lump it in with others if that is easy13:38
alex_xumriedem: ok, let me check how image metadata deprecation look like first13:38
mriedemthe novaclient changes are probably the worst part, but at least we know how to do those now13:38
*** prateek has quit IRC13:39
*** cartik has joined #openstack-meeting-413:39
mriedem#action alex_xu to write a spec for deprecating the proxy api to set/delete image metadata13:39
mriedemok, last item, i swear :)13:40
mriedemHow can we test swap volume from Tempest? gmann was trying that at one point.13:40
mriedem^ is why i was looking for gmann13:40
mriedemso apparently we regressed swap volume, which was already broken13:40
johnthetubaguyah bauzas was looking a some nasty bits around there recently13:40
sdaguemaybe mtreinish can take that back into the room there13:40
mriedemit's just a terrible terrible api which isn't tested13:40
*** liuyulong__ has joined #openstack-meeting-413:40
johnthetubaguydoes our default policy allow folks other than cinder to call it? I guess it does?13:41
mriedemi know gmann was working on a test for swap volume at one point and ran into an issue but i can't remember what it was now13:41
mriedemwe changed the default policy to be admin-only back in i think mitaka13:41
mriedemi thought gmann was running into policy issues13:41
johnthetubaguyyeah, I didn't think calling it directly was meant to be a thing13:41
sdaguemriedem: given the TZ delay, perhaps we stick it out on the mailing list?13:41
mriedemjohnthetubaguy: but it is13:41
*** janki has quit IRC13:41
mtreinishsdague: gmann isn't here, he couldn't make it13:41
mriedemjohnthetubaguy: nova volume-update :)13:41
mriedemmaybe i can just dig up his change in tempest13:41
johnthetubaguymriedem: yeah, that was a discovery for me13:41
mriedem#action mriedem to follow up with gmann about testing swap-volume in tempest13:42
*** salv-orl_ has joined #openstack-meeting-413:42
mriedemthe problem might have been he was using a non-admin to call nova, but then nova calls an admin api in cinder13:42
mriedemand it blow up13:42
mriedem*blew13:42
johnthetubaguyah13:42
mriedemthat should be fixed if you just use an admin throughout13:42
sdaguemriedem: is http://developer.openstack.org/api-ref/compute/?expanded=update-a-volume-attachment-detail the thing we're talking about?13:43
mriedemit would also be totally conditional on tempest since only libvirt supports the swap-volume method13:43
johnthetubaguywas there a reason disconnect one then attach another is no good?13:43
mriedemsdague: yes13:43
*** liwei_ has joined #openstack-meeting-413:43
sdaguejohnthetubaguy: yeh, that's a question for me, this seems a bit too magical13:44
johnthetubaguyI wonder if the answer is something about preserving device ordering, but I really have no idea13:44
sdagueok, well the action is out there13:45
johnthetubaguywell, a new day, a new crazy API found13:45
sdagueI have one thing13:45
alex_xu:)13:45
*** salv-orlando has quit IRC13:45
bauzasjohnthetubaguy: yeah https://review.openstack.org/#/c/373390/13:45
mriedemi think it has something to do with the blockRebase that's done https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L118113:45
sdagueI've been pondering API capabilities a bit, and am trying to figure out the best way to flesh out the approach13:45
mriedemswap-volume is really about an api flow for libvirt and certain cinder backends for migration i think13:46
sdagueit's not clear to me that there is time in ocata to do it, but we probably need a pretty detailed spec (and discussions) before we move forward13:46
johnthetubaguymriedem: its live-migration for the volume backend, for non-clustered storage, as I understood it13:46
sdagueso my thinking is an ocata spec13:46
alex_xubut I remember swap-volume works for normal-user, user can just pass a new volume, and that swap works.13:46
johnthetubaguysdague: +1 for moving forward on that13:46
johnthetubaguysdague: I think my problem is matching capabilities with the actual REST calls13:47
*** spzala has joined #openstack-meeting-413:47
sdagueand we can figure out if there is ground work that falls out13:47
johnthetubaguyI think there is a task to go back and add docs into our policy rules? maybe?13:47
mriedemthere is a task to build the default policy into the nova devref13:48
mriedemlike we have for the sample config13:48
johnthetubaguymriedem: +113:48
mriedemthe keystone guys showed up yesterday asking about putting comments in the policy.json with instructions on how to generate it,13:48
mriedemi'd prefer to just have a readme like we do for the nova.conf.sample that has those instructions13:48
*** baoli_ has quit IRC13:48
mriedemso we're consistent13:48
sdaguemriedem: yeh, given json doesn't support comments, I agree13:48
johnthetubaguymriedem: +113:48
johnthetubaguymaybe there is enough of "policy tidy ups" to be done13:49
johnthetubaguysdague: I don't remember spotting anything around that in the operator feedback, I guess its a release or two early for that?13:49
*** hvprash has joined #openstack-meeting-413:49
sdaguejohnthetubaguy: on policy, they liked our new approach, they were just concerned about docs13:50
*** uck has quit IRC13:50
sdagueit's in there13:50
mriedemsdague: might want to keep claudiub in the loop on any policy discoverability / capability stuff since i think he's also looking at that13:50
johnthetubaguysdague: right, thats fair13:50
claudiubo/13:50
mriedemi'll follow up on the readme for generating the default policy if ayoung didn't push that yet13:50
sdaguemriedem: sure, well, a spec will be a reasonable place to keep all that public and iterable13:50
johnthetubaguyah, so at the midcycle, we said we would try add two things for policy discovery13:50
johnthetubaguyI guess, we need a spec up with that, so we can discuss something concrete13:51
*** tri2sing has joined #openstack-meeting-413:51
sdague#action sdague to start in on a capabilities spec13:51
claudiubsorry, a bit out of the loop here. so, I have a WIP patch for matching policy rules and capabilities and different api endpoints.13:51
claudiubalso trying to take into account the given api microversion13:52
*** diga has joined #openstack-meeting-413:52
*** tonytan4ever has joined #openstack-meeting-413:52
sdagueclaudiub: where is that patch?13:53
claudiubit's a bit slow, but i have something that outputs what the nova-api docs have in about 75-80%13:53
*** diga_ has joined #openstack-meeting-413:53
claudiubhttps://review.openstack.org/#/c/280539/13:54
claudiubstill have to upload what i have in my work env13:54
claudiubi've changed things since then13:55
sdagueok, that's probably a bit different granularity than I was thinking13:55
alex_xu4 mins left13:55
claudiubi was planning to include the post method, api endpoint and request body in the output13:56
claudiubapi method *13:56
diga_alex_xu: Hi, https://blueprints.launchpad.net/nova/+spec/display-host-hypervisor-numa-topology can I submit the spec for this BP for ocata-113:56
claudiubor more like, the request body schema13:56
*** liwei_ has quit IRC13:56
alex_xudiga_: yea, sure, i think it is time to submit spec13:56
diga_alex_xu: Sure, thx!13:57
alex_xudiga_: np13:57
*** Yumeng has joined #openstack-meeting-413:58
diga_:)13:58
alex_xuok, 2 mins left13:58
alex_xuso let us back to the nova channel?13:58
*** tmetsch has joined #openstack-meeting-413:58
sdaguesounds good13:59
*** sdake has joined #openstack-meeting-413:59
alex_xuok, thanks all!13:59
alex_xu#endmeeting13:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:59
openstackMeeting ended Wed Sep 21 13:59:21 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-09-21-13.00.html13:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-09-21-13.00.txt13:59
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-09-21-13.00.log.html13:59
*** sdake has quit IRC13:59
acabot#startmeeting watcher14:00
openstackMeeting started Wed Sep 21 14:00:09 2016 UTC and is due to finish in 60 minutes.  The chair is acabot. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: watcher)"14:00
openstackThe meeting name has been set to 'watcher'14:00
*** sdake has joined #openstack-meeting-414:00
acaboto/14:00
*** kberger has joined #openstack-meeting-414:00
sballe_o/14:00
hvprashhi everyone14:00
YumengHi14:00
diga_o/14:00
edleafe\o14:00
sballe_I am woking with dtardivel  on something14:00
*** rbak has joined #openstack-meeting-414:00
acabotagenda for today #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#09.2F21.2F201614:00
*** hongbin has joined #openstack-meeting-414:01
acabot#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: watcher)"14:01
acabot#info Watcher Newton RC1 (v0.30.0) has been released, please follow instructions sent on the ML14:01
acabot#link http://lists.openstack.org/pipermail/openstack-dev/2016-September/103989.html14:01
*** jwcroppe has joined #openstack-meeting-414:01
*** woodard has quit IRC14:02
acabot#info Newton stable branches have been created by the TC for watcher & python-watcherclient14:02
jwcroppeo/14:02
dtardivelhi14:02
jwcroppehi14:02
acabotso if you file a bug that needs to be released in newton, please tag it as *newton-rc-potential*14:02
*** Yumeng_ has joined #openstack-meeting-414:02
*** licanwei has joined #openstack-meeting-414:02
acabotnow we will have to deal with a newton stable branch14:03
*** galstrom_zzz is now known as galstrom14:03
*** gzhai has joined #openstack-meeting-414:04
acabotwatcher-dashboard is still waiting for a rc-final release next week14:04
acabot#info we need your help to test the release and submit bugs before the final release next week14:04
acabot#info acabot will be Watcher PTL for Ocata cycle14:04
acabotas I'm the only candidate14:05
*** petergurinov_ has joined #openstack-meeting-414:05
jwcroppeacabot: congrats :)14:05
acabotso thanks for electing me :-D14:05
hvprashcongrats !14:05
*** vincentfrancoise has joined #openstack-meeting-414:05
sballe_+214:05
vincentfrancoiseo/14:05
diga_acabot: congrats!14:05
acabot#info design summit sessions timeslots are available on the dedicated etherpad14:05
acabot#link https://etherpad.openstack.org/p/watcher-ocata-design-session14:05
jwcroppesballe_: btw, the presentation looks good... few nits I'll send today/tomorrow14:06
*** andymaier has joined #openstack-meeting-414:06
sballe_jwcroppe: thx14:06
acabotas you may probably know, I wont be with you in Barcelona so I hope sballe_ can deal with PTL assignements during the summit14:06
sballe_acabot: I can drive the filling out of design sessions14:06
*** cdent has left #openstack-meeting-414:06
acabotsballe_ : definitely14:07
acabotthx14:07
sballe_I am the virtual acabot ... Pretty big shoes to fill ;-)14:07
acabot#action sballe_ start filling working sessions agenda in https://etherpad.openstack.org/p/watcher-ocata-design-session14:07
*** mriedem has left #openstack-meeting-414:07
acabotsballe_ : I'm sure you will fit the role ;-)14:08
sballe_thx14:08
acabotany other announcement ?14:08
*** Swami has joined #openstack-meeting-414:08
*** Swami_ has joined #openstack-meeting-414:08
*** Swami_ has quit IRC14:08
*** Swami has quit IRC14:08
acabotlets move on14:08
acabot#topic Review Action Items14:08
*** Swami has joined #openstack-meeting-414:09
*** openstack changes topic to "Review Action Items (Meeting topic: watcher)"14:09
acabotWatcher specs14:09
acabotResize instance base on workload needs a new PS and should be retargeted to Ocata14:09
acabot#link https://review.openstack.org/#/c/359690/14:09
*** marst has quit IRC14:09
acabotYumeng : are you working on it ?14:09
Yumeng_yep14:09
Yumeng_hanrong has uploaded a new patch about this spec. and some problems are reported in jekins. we will do more revision asap.14:09
acabotYumeng_ : please retarget it to Ocata in your next PS14:10
Yumeng_ok.14:10
Yumeng_i will do that14:10
acabot#action Yumeng_ hanrong retarget and update https://review.openstack.org/#/c/359690/14:10
acabotautomatic triggering of action plans for AUDIT needs reviews14:10
acabot#link https://review.openstack.org/#/c/342473/14:11
acabotdiga_ : I saw that you added a new PS, is that ready to be reviewed ?14:11
diga_acabot: yes14:11
vincentfrancoiseI made some comments on it already14:11
acabotok14:11
vincentfrancoisethere is 1 main question that still misses an answer14:12
acabotsballe_ jwcroppe hvprash : anyone who wants to review it ?14:12
sballe_I can d that14:12
hvprash+114:12
gzhai+114:13
jwcroppe+114:13
acabot#action hvprash sballe_ acabot gzhai jwcroppe review https://review.openstack.org/#/c/342473/14:13
*** cartik has quit IRC14:13
diga_vincentfrancoise: Your comment "How do plan on making sure there only one action plan that is executed at a time? "14:13
acabotLimit concurrent actions invoked by Watcher needs reviews14:13
acabot#link https://review.openstack.org/#/c/348049/14:14
acabotsorry I didn't have time to review it yet, anyone here who wants to review ?14:14
hvprashi can14:14
sballe_ditto14:14
acabot#action hvprash sballe_ review https://review.openstack.org/#/c/348049/14:15
diga_vincentfrancoise: we are introducing the AUTO_TRIGGER_ACTION_PLAN attribute in the AUDIT, only those Audits action plan executed14:15
acabothvprash : dont take too many reviews because you have a spec to write ;-)14:15
vincentfrancoisediga_: yes that's the one question that needs to be addressed14:15
hvprashthats fine acabot :)14:15
vincentfrancoisediga_: yes but if 2 action plans have that AUTO_TRIGGER_ACTION_PLAN flag, they will be concurrently executed and we don't want that14:16
hvprashbeen away for few weeks and was missing some action ;)14:16
acabothvprash ;-)14:16
acabotAdd team priorities for Ocata needs reviews and will be merged during the summit14:16
acabot#link https://review.openstack.org/#/c/372528/14:16
*** limao has joined #openstack-meeting-414:17
acabotI had a discussion with alexchadin about the watcher roadmap14:17
diga_vincentfrancoise: how many action plan we can execute for one audit, can we execute many action plan for audit ??14:17
acabotand realized that we didn't set priorities after the mid-cycle14:17
vincentfrancoisediga: we need to add some logic on the watcher-applier side to make sure that only 1 action plan can be executed at a time14:17
diga_vincentfrancoise: okay14:17
vincentfrancoisediga: 2 action plans from 2 different audits14:17
acabotdiga_ vincentfrancoise : could you please iterate through gerrit ?14:18
diga_acabot: okay14:18
vincentfrancoiseacabot: ok14:18
*** rainya has quit IRC14:18
acabotso I did a first draft of Ocata priorities, I could have missed some important BPs so please review it before the summit14:18
*** rainya has joined #openstack-meeting-414:18
acabotWe need a spec for Define grammar for workload characterization14:19
hvprashyes14:19
acabot#link https://blueprints.launchpad.net/watcher/+spec/workload-characterization-grammar14:19
hvprashworking on it14:19
sballe_+114:19
acabot#action sballe_ jwcroppe hvprash review https://review.openstack.org/#/c/372528/14:19
sballe_hvprash: pull me in14:19
acabot#action hvprash submit a spec for https://blueprints.launchpad.net/watcher/+spec/workload-characterization-grammar14:19
hvprashof course sballe_14:19
acabotmoving to Watcher14:20
acabotmany bug fixes merged last week14:20
*** limao_ has joined #openstack-meeting-414:20
acabotnow that we have a stable branch, we can start merging code for Ocata14:20
acabotAdd Audit Scope Handler needs reviews14:20
acabot#link https://review.openstack.org/#/q/status:open++topic:bp/define-the-audit-scope14:21
acabotwho wants to review the audit scope handler ?14:21
dtardivel+114:21
*** cbouch has joined #openstack-meeting-414:21
sballe_+114:21
acabot#action dtardivel sballe_ review https://review.openstack.org/#/q/status:open++topic:bp/define-the-audit-scope14:21
acabotGraph cluster model implementation needs reviews14:22
acabot#link https://review.openstack.org/#/c/362730/14:22
*** limao has quit IRC14:22
acabotwho wants to review the graph model ?14:22
vincentfrancoiseme14:22
*** marst has joined #openstack-meeting-414:22
dtardivelme14:22
acabot#action vincentfrancoise dtardivel review  https://review.openstack.org/#/c/362730/14:23
acabotWatcher dashboard14:23
acabotDashboard devstack plugin has been disabled until a bug is fixed in devstack14:23
acabot#link https://bugs.launchpad.net/devstack/+bug/154032814:23
openstackLaunchpad bug 1540328 in devstack "Devstack cannot install Horizon plugins using pip 8.x" [Undecided,Confirmed] - Assigned to YAMAMOTO Takashi (yamamoto)14:23
acabotit impacts many different projects14:23
acabotand our devstack setup does not work anymore14:24
acabot#topic Blueprint/Bug Review and Discussion14:24
*** openstack changes topic to "Blueprint/Bug Review and Discussion (Meeting topic: watcher)"14:24
dtardivelacabot: I would like to check watcher:stable/newton branch on devstack, but stable/newton branch on devstack is not yet available...14:24
*** mfedosin has quit IRC14:25
acabotas discussed last week, after the RC-1 release, all BPs targeted for Ocata were medium or low priority14:25
acabot#link https://blueprints.launchpad.net/watcher/ocata14:25
acabotso I tried to set a priority and a milestone for each BP14:26
acabotI'd like everyone to review it and check if the priority and milestone is ok14:26
*** aimeeu__ has quit IRC14:26
acabotwe have 17 BPs for Ocata (15 have been completed in Newton)14:27
acabotof course if I missed important BP in the list https://blueprints.launchpad.net/watcher please let me know asap14:27
sballe_this is a good cadense. pretty impressive14:28
*** limao_ has quit IRC14:28
*** limao has joined #openstack-meeting-414:28
*** mfisch has quit IRC14:28
*** yamahata has joined #openstack-meeting-414:28
acabotthe Ocata schedule is shorter than previous cycle14:28
acabotas there will be the PTG event in february14:28
*** iyamahat has joined #openstack-meeting-414:29
sballe_where is the PTG event? I forgot14:29
acabotAtlanta14:29
acabotscalability tests - platform status14:29
*** limao_ has joined #openstack-meeting-414:29
acabotdtardivel sballe_ gzhai : any updates on the platform ?14:30
sballe_yes14:30
dtardivelwe are going to check all the platform conf with Susanne14:30
*** psachin has quit IRC14:30
sballe_We have systems up and runnign with Monasca but dtardivel and I are debugging it14:30
sballe_Monacsa needs to be configured14:30
sballe_I have access to the systems now s we shoul dbe moving forward14:31
*** kylek3h has joined #openstack-meeting-414:31
sballe_a million thx to dtardivel for his help here14:31
acabothow many nodes do we have now ?14:31
sballe_12=1514:31
sballe_12+1514:31
sballe_and 3 as control plane14:31
*** mfisch has joined #openstack-meeting-414:31
*** caboucha has joined #openstack-meeting-414:31
acabotok14:31
*** jed56 has joined #openstack-meeting-414:32
*** mfisch has quit IRC14:32
*** mfisch has joined #openstack-meeting-414:32
*** liwei has joined #openstack-meeting-414:32
acabotany idea of when we will be able to run PKB ?14:32
*** mfedosin has joined #openstack-meeting-414:32
sballe_as soon as we have it debugged and ceilosca installd14:32
*** caboucha has quit IRC14:32
sballe_hopefuly next week14:32
acabotok14:32
*** yamamoto has quit IRC14:32
acabotMonday 26th14:33
sballe_dtardivel: and I still have some debugging to do14:33
*** limao has quit IRC14:33
dtardivelyep14:33
sballe_lol14:33
acabotsballe_ : we planned to have the platform until Monday 26th :-)14:33
sballe_I have been told we can have it unitl the end of october14:34
acabotsballe_ : good news14:34
acabotI hope we will be able to get metrics before the summit14:34
sballe_:-)14:34
acabot#topic Open discussions14:34
*** openstack changes topic to "Open discussions (Meeting topic: watcher)"14:34
acabotNotifications in Watcher is too big and need to be segmented14:35
acabot#link https://blueprints.launchpad.net/watcher/+spec/watcher-notifications-ovo14:35
acabotvincentfrancoise : your subject ;-)14:35
vincentfrancoisewell this BP is quite big and tackles many aspects of Watcher at the same time14:35
*** caboucha_ has joined #openstack-meeting-414:36
jed56+2 ;)14:36
vincentfrancoisefirst of there is the setup of the notification system14:36
*** liwei has quit IRC14:36
*** caboucha_ has quit IRC14:36
*** caboucha has joined #openstack-meeting-414:36
vincentfrancoiseand then we have to lay down all the notifications (and their respective payload) we want for each one of the Watcher objects14:36
vincentfrancoiseso I would suggest we use this BP to only create the common plumbing14:37
vincentfrancoiseand then create a separate BP for the Audit notifications, Action Plan notifications, and so on...14:37
*** caboucha has quit IRC14:38
*** rainya has quit IRC14:38
jed56this is a good idea14:38
*** caboucha has joined #openstack-meeting-414:38
*** woodard has joined #openstack-meeting-414:38
acabotvincentfrancoise : so you plan to have only the Audit updated in this BP ?14:38
acabot+ the plumbing14:38
vincentfrancoisewell I plan to do the common plumbing and the new audit-related notifications BP14:39
vincentfrancoiseso yes14:39
dtardivelvincentfrancoise: +114:39
acabotmy main concern would be, if we merge the Audit and then dont have time to update other Watcher objects, will Watcher still be usable ?14:40
vincentfrancoiseIMHO, the most important objects we need to focus on in ocata should be audit and action plan14:40
acabotas we will use 2 different mechanisms to deal with objects14:40
vincentfrancoisebecause Watcher actions involve Nova (e.g. for migrations or service state update)14:41
vincentfrancoiseand these already emit notifications of their own14:41
*** khushbu_ has quit IRC14:41
vincentfrancoiseand the audit template is pretty much copied as an audit before any action gets done so audit notifications should suffice14:42
acabotok14:42
acabotcould you please update the BP description and submit a draft of spec for it ?14:42
acabotvincentfrancoise : could you please update the BP description and submit a draft of spec for it ?14:43
*** syed_ has joined #openstack-meeting-414:43
vincentfrancoiseacabot: yes I will, I am still in an 'exploration' stage14:43
acabot#action vincentfrancoise update BP description and submit a draft spec for https://blueprints.launchpad.net/watcher/+spec/watcher-notifications-ovo14:44
*** diga has quit IRC14:44
acabotvincentfrancoise : ok thx14:44
acabotwe should provide a user documentation for each strategy14:44
vincentfrancoise+114:44
acabotas dtardivel was testing strategies last week, we realized that there is no dedicated doc for each strategy available in watcher14:45
*** cleong has joined #openstack-meeting-414:45
dtardivelacabot: yep. the main idea is to propose a template doc to explain a strategy14:45
acabotwhat do you think ?14:45
dtardivelacabot: and how to use it, what are required metrics, how to collect them ? ....14:46
vincentfrancoisethe most important bit was the metrics requirements14:46
acabotshould we let devs build there own doc when they submit a new strategy or should we guide them with a template ?14:46
vincentfrancoiseand then the parameter tunings14:47
dtardivelacabot: I prefer a template doc ... and an exemple14:47
hvprash+114:47
sballe_+114:47
*** ddieterly has joined #openstack-meeting-414:48
acabotok do we need a BP for that ? (I dont think so)14:48
dtardivelI created a wishlist bug14:48
vincentfrancoiseacabot: a BP might be needed to go through all existing strategies14:48
acabotits a doc improvement, I think a bug is sufficient14:48
*** caowei has quit IRC14:48
dtardivel+114:49
acabotvincentfrancoise : if we have a template, I think we can ask every strategy provider to add a doc14:49
*** ulik has joined #openstack-meeting-414:49
dtardivel+114:49
vincentfrancoise+114:49
acabotwho wants to start working on a template ?14:49
dtardivelI can try on basic consolisation strategy14:50
acabotok14:50
*** limao_ has quit IRC14:50
acabot#action build a template for strategy doc using basic consolidation as an example14:50
acabot#action dtradivel build a template for strategy doc using basic consolidation as an example14:50
*** limao has joined #openstack-meeting-414:50
*** iberezovskiy|off is now known as iberezovskiy14:51
acabot#action dtardivel build a template for strategy doc using basic consolidation as an example14:51
* acabot a bit tired...14:51
acabotfix requirements14:51
*** zhurong has quit IRC14:51
acabothttps://review.openstack.org/#/q/status:open+topic:tox/requirements14:51
acabot#link https://review.openstack.org/#/q/status:open+topic:tox/requirements14:51
*** jovon has joined #openstack-meeting-414:52
acabotdtardivel : do you want to explain this change sets ?14:52
dtardivelvincentfrancoise: please can you explain it ? :)))14:52
vincentfrancoisedtardivel: ok :p14:52
vincentfrancoiseso basically, these are needed to set precise requirement versions14:53
*** baoli has joined #openstack-meeting-414:54
vincentfrancoisee.g. for the stable/newton branch, this will guarantee that all test are passing with with the newton-capped package versions instead of beeing changed all the time14:54
acabotso now stable newton branch has fixed requirements right ?14:55
dtardivelstrict requirements are set in openstack/requirements github project, in the file upper-contraints.txt14:55
acabotso do we have to test it again with these requirements or it was already done ?14:55
vincentfrancoiserequirements.txt only defines the lower boundary for package requirements14:55
dtardivelSo we add into tox.ini a way to read this strict requirements and to update our dependencies versions while running unitary tests14:56
vincentfrancoisewith this, we now have the upper boundary14:56
acabotok14:56
acabot4 min left, any other discussion to open ?14:56
*** caboucha has quit IRC14:57
dtardivelacabot: I proposed a commit for stable/newton and master branches on watcher and python-watcherclient project14:57
dtardivels/commit/patchset14:58
acabotdtardivel : https://review.openstack.org/#/q/status:open++topic:tox/requirements14:58
acabotok thank you all14:58
acabothave a nice day/night14:59
vincentfrancoisebye14:59
hvprashbye14:59
acabot#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
jed56bye14:59
openstackMeeting ended Wed Sep 21 14:59:11 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-09-21-14.00.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-09-21-14.00.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-09-21-14.00.log.html14:59
*** openstack has joined #openstack-meeting-415:02
*** ChanServ sets mode: +o openstack15:02
serverascode#startmeeting operators_telco_nfv15:02
openstackMeeting started Wed Sep 21 15:02:33 2016 UTC and is due to finish in 60 minutes.  The chair is serverascode. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** openstack changes topic to " (Meeting topic: operators_telco_nfv)"15:02
openstackThe meeting name has been set to 'operators_telco_nfv'15:02
serverascode#topic agenda and roll all15:03
*** openstack changes topic to "agenda and roll all (Meeting topic: operators_telco_nfv)"15:03
*** bklei has joined #openstack-meeting-415:03
*** Yumeng_ has quit IRC15:03
serverascodeanyone here for the telecom/ops team meeting?15:03
serverascode#link https://etherpad.openstack.org/p/ops-telco-nfv-meeting-agenda15:03
serverascodewill give it a couple min to see if anyone drops in :)15:04
*** licanwei has quit IRC15:05
*** gzhai has left #openstack-meeting-415:05
*** bobh has quit IRC15:06
*** petergurinov_ has quit IRC15:06
serverascode#topic Barcelona15:07
*** diga_ has quit IRC15:07
*** openstack changes topic to "Barcelona (Meeting topic: operators_telco_nfv)"15:07
serverascode#info haven't heard back from user committee on space in BCN yet15:08
serverascodebut as soon as I do will let ppl know15:08
serverascodemay also be possible to get a room from the ops summit portion15:08
*** umbSublime has left #openstack-meeting-415:08
*** vincentfrancoise has left #openstack-meeting-415:08
serverascode#action Curtis let ppl know about BCN space15:09
serverascode#topic Increasing participation15:09
*** openstack changes topic to "Increasing participation (Meeting topic: operators_telco_nfv)"15:09
serverascodeGiven this is meeting #9 it's probably time to start looking into finding active participants15:10
*** galstrom is now known as galstrom_zzz15:10
ulik#info Uli Kleber15:10
serverascode#action Curtis contact OpenStack Foundation to find out how they may be able to help "get the word out"15:10
serverascodehi ulik :)15:10
ulikhi, sorry couldn't make for a few meetings.15:11
*** limao has quit IRC15:11
*** tmetsch has left #openstack-meeting-415:11
serverascodeno worries15:11
*** ddieterly is now known as ddieterly[away]15:12
*** limao has joined #openstack-meeting-415:12
serverascodeit's just you and me methinks15:12
*** ddieterly[away] is now known as ddieterly15:12
ulikbut I see main issue is low participation. Maybe Barcelona meeting can help to get people more aware.15:12
serverascodeyeah I hope so15:12
serverascodeI'm also going to contact a couple o fppl at the foundation to see if they can help15:13
ulikgreat.15:13
ulikOPNFV guys are very busy now finalizing the Colorado release15:13
serverascoderight yeah, I heard about the release15:14
*** andymaier has quit IRC15:14
*** yamamoto has joined #openstack-meeting-415:14
*** yamamoto has quit IRC15:14
serverascode#info OPNFV Colorado release is happening right now15:14
serverascode#topic Open Conversation15:15
*** openstack changes topic to "Open Conversation (Meeting topic: operators_telco_nfv)"15:15
ulikAnd we are trying 3rd party CI to do faster verification of openstack patches in OPNFV environment.15:15
serverascodecool yeah I need to check that out15:15
ulikIt is still at beginning.15:16
serverascodeI don't have anything else specific to discuss :)15:17
ulikme neither15:17
serverascodeok well thanks ulik for coming :) I will let you know what I hear from the user committe and foundation15:18
ulikthx15:18
*** pbourke has quit IRC15:18
serverascode#endmeeting15:18
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:18
openstackMeeting ended Wed Sep 21 15:18:46 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:18
openstackMinutes:        http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2016/operators_telco_nfv.2016-09-21-15.02.html15:18
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2016/operators_telco_nfv.2016-09-21-15.02.txt15:18
openstackLog:            http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2016/operators_telco_nfv.2016-09-21-15.02.log.html15:18
*** pbourke has joined #openstack-meeting-415:19
*** omnipresent has joined #openstack-meeting-415:24
*** yamamoto has joined #openstack-meeting-415:27
*** wznoinsk has quit IRC15:28
*** jwcroppe has left #openstack-meeting-415:28
*** liuyulong has quit IRC15:29
*** liuyulong has joined #openstack-meeting-415:29
*** ddieterly is now known as ddieterly[away]15:30
*** yamamoto has quit IRC15:32
*** galstrom_zzz is now known as galstrom15:32
*** limao has quit IRC15:32
*** limao has joined #openstack-meeting-415:33
*** ddieterly[away] is now known as ddieterly15:34
*** bklei has quit IRC15:36
*** duonghq has joined #openstack-meeting-415:36
*** bklei has joined #openstack-meeting-415:37
*** jichen has quit IRC15:37
*** tri2sing has quit IRC15:40
*** tri2sing has joined #openstack-meeting-415:40
*** d0ugal has quit IRC15:48
*** amotoki has quit IRC15:49
*** ulik has quit IRC15:49
*** d0ugal has joined #openstack-meeting-415:50
*** yamamoto has joined #openstack-meeting-415:52
*** spotz_zzz is now known as spotz15:53
*** limao has quit IRC15:54
*** bpokorny has joined #openstack-meeting-415:54
*** limao has joined #openstack-meeting-415:54
*** Julien-zte has joined #openstack-meeting-415:56
*** inc0 has joined #openstack-meeting-415:56
*** egonzalez90 has joined #openstack-meeting-415:57
*** wirehead_ has joined #openstack-meeting-415:58
*** zhubingbing has joined #openstack-meeting-415:59
zhubingbinghi guys15:59
*** vhosakot has joined #openstack-meeting-416:00
britthou_Hey zhubingbing16:00
zhubingbinghey16:00
*** jmccarthy has joined #openstack-meeting-416:00
*** britthou_ is now known as britthouser16:00
*** matrohon has quit IRC16:00
sdake#startmeeting kolla16:00
openstackMeeting started Wed Sep 21 16:00:45 2016 UTC and is due to finish in 60 minutes.  The chair is sdake. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: kolla)"16:00
openstackThe meeting name has been set to 'kolla'16:00
sdake#topic rollcall16:00
*** openstack changes topic to "rollcall (Meeting topic: kolla)"16:00
vhosakoto/16:00
egonzalez90o/16:00
duonghqo/16:00
pbourkeo/16:00
berendto/16:00
zhubingbingo/16:01
jmccarthyo/16:01
britthouser0/16:01
coolsvapo/16:01
Jeffrey4l\o/16:01
sdake\O/16:01
inc0o/16:01
sdake#topic annuncements16:01
*** openstack changes topic to "annuncements (Meeting topic: kolla)"16:01
sdake#undo16:01
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x7f66f51977d0>16:01
sdake#topic announcements16:01
*** uxdanielle has joined #openstack-meeting-416:01
*** openstack changes topic to "announcements (Meeting topic: kolla)"16:02
sdakeinc0 can you link the room alloction for summit plesae16:02
*** banix has joined #openstack-meeting-416:02
*** barmaley has joined #openstack-meeting-416:02
inc0#link https://etherpad.openstack.org/p/kolla-O-summit-planning16:03
sdakewhile inc0 digs up that link, we got received a significant amount of summit space for kolla16:03
britthouserw00t!16:03
sdakeI think 9 or 10 wr ssessions, 3 fisshbowl, and half day contributor meetup16:03
wirehead_o/16:03
sdakeif you compare to nova and neutron, we got a rockin amount of sessions16:03
zhubingbingi agree16:04
*** sbezverk has joined #openstack-meeting-416:04
sdakethat said, i want to ensure in today's meeting that all those sessions will be used appropriatelly, and if not consider giving 1 or 2 workroom sessions back to the organizers so that emerging projects have a chance at summit to get work done16:04
sdake#2. ptl elections are this week - don't forget to vote!16:05
sdakei'd like more then a 60% turnout on the vote then happened last time16:05
sdakemake your voice heard16:05
berendtdo we already have a list where we mapped our session to the work rooms?16:06
sdakeberendt that is the responsibility of the next ptl - that happens in two-3 weeks16:06
berendtbut how should we decide if we need all assigned work rooms without assigning our sessions?16:07
sdake#3. the release team has cut us a big bone and not branched kolla on rc116:07
sdakeberendt we havee a list of sessions16:07
sdakeberendt but no mapping to the workrooms - that is what we will sort out today (how many are ultimately necessary to achieve our summit planning)16:07
sdakeso on to #316:07
berendtah.. understood16:07
sdakewhat this means is master is not open for business as of yet16:08
*** barmaley has quit IRC16:08
*** uck has joined #openstack-meeting-416:08
sdakethe guidance I've recieved from the release team is to limit rcs16:08
*** baoli has quit IRC16:08
sdakein other words our rc2 should be our near final state that we intend to tag as 3.0.016:08
*** baoli has joined #openstack-meeting-416:09
sdakefinally branches happen only agianst tags not specific git hashes16:09
sdakeso lets sort out #3 first16:09
pbourkehave we tagged rc1?16:10
sdake#topic rc2 deadline planning and bug triage16:10
*** openstack changes topic to "rc2 deadline planning and bug triage (Meeting topic: kolla)"16:10
sdakerc1 was tagged within 1 hour of deadline16:10
sdakeso yes :)16:10
pbourkewhats the tag I dont see it16:10
*** bogdando has quit IRC16:10
berendtpbourke 3.0.0.0rc116:11
pbourkeah thanks16:11
egonzalez90https://github.com/openstack/kolla/tree/3.0.0.0rc116:11
zhubingbing3.0.0.0rc116:11
sdakepbourke https://github.com/openstack/kolla/releases/tag/3.0.0.0rc116:11
sdakewoops egonzalez90 faster at internets then me16:12
berendtfourtimes is enough ;)16:12
sdakeagree berendt16:12
sdakeok open up https://launchpad.net/kolla/+milestone/newton-rc216:13
sdake107 bugs16:13
sdakewhat I need of the core review team and anyone in the drivers team that can do the work is to go through this list and triage bugs16:13
sdakezhubingbing did a great first pass16:13
*** vkmc is now known as vkmc|afk16:14
sdakeat sortng out the maximum set of bugs to fix16:14
sdakelets sort out individually the minimum set of bugs to fix and make sure their priority is set16:14
sdakeI can't do this alone or in a vacuum16:14
sdakeuse your judgement and push things to o1 that make sense16:14
berendtdoes it makes sense to move wishlist bugs to the next cycle?16:15
sdakeultimately that bug list sshould be high or critical bugs only (to reduce the scope of  the work we have to do)16:15
sdakeberendt ^^16:15
sdakethe first step is making sure the priorities are correct16:15
zhubingbingi agree16:15
*** bdaca has joined #openstack-meeting-416:15
sdakei've done a rough pass over the 107 bugs as well16:15
*** pcaruana has quit IRC16:15
*** limao_ has joined #openstack-meeting-416:16
sdakeid like others to do the same - consider this a critical task ;)16:16
sdakesomething to be done today or thursday at latest16:16
sdakeanything not marked critical or high is being moved to ocatta thursday 00:00 UTC16:16
zhubingbing A lot more than 3 months of bug status is high16:16
*** limao has quit IRC16:16
sdakezhubingbing didn't parse, can you restate16:17
*** wznoinsk has joined #openstack-meeting-416:17
wznoinsklate hi16:17
sdakesup wznoinsk16:17
*** pcaruana has joined #openstack-meeting-416:17
sdakewe are just getting started - butyou missed the announcements - might want to read those in the log later16:17
wznoinskhi sdake, getting thru meeting logs16:17
sdakei thin kwe can handle about 50 bugs in the next month\16:18
inc0when is deadline for rc216:18
inc0?16:18
sdakebut if there are more that need to be handled, lets recognize that fact16:18
sdakethe deadline for rc2 is at our discretion16:18
sdake(according to the releae team)16:19
*** bklei has quit IRC16:19
sdakeso lets not slack in figuring out when that deadline should be16:19
sdaketo get to the deadline, lets sort out the prioirtieis and bug lisst16:19
sdakeand we can make a call from there16:19
duonghqzhubingbing: did you really triaged this bug: https://bugs.launchpad.net/kolla/+bug/160434316:20
openstackLaunchpad bug 1604343 in kolla "Fail to create instance on Ubuntu host" [Medium,Triaged]16:20
zhubingbingi fix now16:20
sdakewe have a hard deadline of oct7 for rc216:20
sdakei'd like to pull that in if possible16:20
sdakethat is what  this discussion is all about16:20
duonghqzhubingbing: you took this bug?16:21
sdakewe could bleed into the next week after if needed16:21
sdakelets try not to do that16:21
sdakeduonghq - bugs are roughly triaged16:21
sdakeduonghq if you want to help with triage i can add you to the drivers team and you can do whatyou think is right ;)16:21
duonghqsdake: sometime guys triaged bug by mistake16:22
sdakeone last peice of further guidance on triage16:22
sdakecritical = affects whole system16:22
duonghqso I want to make sure they truly triaged16:22
*** ddieterly is now known as ddieterly[away]16:22
sdakehigh = affects a component that results in nonfunctionality16:22
sdakeduonghq they are not16:22
sdakeduonghq that is what we need to do16:22
*** Yumeng has quit IRC16:23
berendtsdake shoud we a those defintiions to our docs?16:23
sdake[09:14:33]  <sdake>lets sort out individually the minimum set of bugs to fix and make sure their priority is set16:23
sdakeberendt makes sense to me16:23
sdakeberendt up to the core team really16:23
*** devananda|dinner is now known as devananda16:23
sdakeif yoou dont like my definitinos use your own ;)16:23
berendti think it is important to document it, that's the point..16:24
sdakeany further questions?16:24
berendti will open a review, we can discuss there16:24
sdakeberendt ok - wfm :)16:24
zhubingbingi thinks document is very important16:24
duonghqtotally agreed with zhubingbing16:25
zhubingbing About hub kolla on docker image management16:25
sdakeok any questions on the request or deadline for request?16:25
sdakezhubingbing - that is for open item discussion16:25
zhubingbinglong time not update16:25
*** ddieterly[away] is now known as ddieterly16:25
zhubingbinghmm16:26
sdakezhubingbing we only update *released* images in docker hub16:26
Jeffrey4lsdake, so we do not need a bug to track the trivial fix, right?16:26
sdakethat are *stable*16:26
sdakehence no rc16:26
Jeffrey4luntil rc216:26
pbourkeis it clear to people which bugs need to be pushed to ocata and which are to be fixed, and by when16:26
sdakeJeffrey4l roger16:26
pbourkeas for me, its not16:26
sdakepbourke high-critical stay in newton - everything else pushed to occata thurday16:27
Jeffrey4lbefore rc2, i think we can push some new feature :)16:27
sdakeno new features16:27
pbourkesdake: ok cool16:27
sdakerc2 is bug fix only16:27
Jeffrey4l ok16:27
sdakeenforce it in reviews please16:27
pbourkeso date date for rc2 is at our discretion16:27
berendtyes we have enought new features that are not working like expected16:27
pbourkewhat about the final release16:27
sdakepbourke the problem we have now is a lack of clarity about what is high/critical - i need core reviewt eam and drivers team to define that16:27
wznoinsksdake: how about the ironic-conductor/inspector fixes I@m on atm?16:28
sdakethe final release follows the ormal schedule which is october 20th16:28
Jeffrey4lwznoinsk, good point16:28
sdakewznoinsk those are ocata work16:28
sdakewznoinsk tht said if yuo fix a bug that isn't high or critical - good for you :)16:29
Jeffrey4lthen ironic will totally unused in newton :(16:29
wznoinskI need to seprate ironic-inspector from ironic (not to mix the rootwrap and other things as they are different projects), not a new feature, not the trivial bug either16:29
wznoinskJeffrey4l: that's what I'm worried about too, broken for last to release and so close to be working16:29
wznoinsks/to release/two releases16:30
sdakewhen i say ironic - i mean BMAAAS16:30
sdakeanything related to bifrost deployment is *CRITICAL*16:30
*** spzala has quit IRC16:30
sdakeok any further questions?16:31
*** spzala has joined #openstack-meeting-416:31
*** krtaylor has quit IRC16:31
inc0sdake, it will be related16:31
sdakemarching orders -> 1. triage bugs indepedently16:31
sdakelets start with #1 ;)16:31
*** galstrom is now known as galstrom_zzz16:31
sdake#2: i'll move bugs to ocata on thursday 00:00 utc16:31
sdakethat are not high/critical16:32
sdakethe goal of this effort is to reduce scope of rc216:32
sdakeand it is essential16:32
sdakeanyone lacking clarity nwo?16:33
sdakenow?16:33
pbourkesdake: sounds good thanks16:33
wznoinsksdake: 29th Sept you mean?16:33
sdakenice - moving on then :)16:33
zhubingbingagree16:33
sdakewznoinsk no - we have discretioin on our rc2 deadline16:34
*** limao_ has quit IRC16:34
sdake#3. I will set a hard rc2 deadline after #1 and #2 are completed above16:34
*** Swami has quit IRC16:34
*** iyamahat has quit IRC16:34
sdake#4. after thursday work on critical bugs first, high bugs second16:35
inc0wznoinsk, let's merge inspector before then and be done with it;)16:36
sdakewznoinsk works for m e - ue your judgement guys - if we didn't trust you you wouldn't be in the drivers team or core review tam16:36
*** Julien-zte has quit IRC16:37
*** yamahata has quit IRC16:37
*** spzala has quit IRC16:37
sdakeok now- moving on :)16:37
sdake#topic summit sessions fine tuning16:37
*** openstack changes topic to "summit sessions fine tuning (Meeting topic: kolla)"16:37
sdake#link https://etherpad.openstack.org/p/kolla-O-summit-planning16:38
sdakeopen that one up please16:38
zhubingbingok16:39
sdakelets walk one by one through these16:39
sdakeand determine if they are essential planning or not16:39
sdakeactually change in mind16:39
sdakelets work in the etherpad, nd place an "E" next to those you think is essential16:40
inc0lol16:40
sdakewe will then have a poll that inc0 will organize from the essential sessions16:40
inc0nah, I'll make poll of all of them16:40
inc0poll in a way that people will be able to prioritize on their own16:40
sdakeok that wfm16:41
sdakeinc0 need fast turnaround on that poll16:41
sdakeset a 7 day timer, please try to get it out today or tomorrow16:41
sdakei really have a strong desire to give back to the foundation16:42
inc0it'll hit the openstack-dev today16:42
sdakeinc0 roger16:42
sdakeeven if something is marked essential, if voting is low - it may be cut16:42
sdakepolled essential rather16:43
duonghqsdake: can you add note about E in the etherpad?16:43
sdakeok - well i hd planned to usse the rest of this meeting to sort that out, but since the poll solution is on the table, lets use that16:43
*** bjolo has joined #openstack-meeting-416:43
sdakeduonghq we have just made a decision to ue  openstack-dev poll via a web based voting service16:43
duonghqyay, so the etherpad just for reference?16:44
sdakemy brain not operating at full capcity atm - so the recommended one I'd use escapes me16:44
sdake(mornings ftl:(16:44
sdakeany questions?16:44
duonghqroger16:44
sdakeinc0 i'll sync up with you on the polling softtware i'd recommend using16:45
sdakeonce i access my mental mind palace ;)16:45
sdake#topic open discussion16:45
*** openstack changes topic to "open discussion (Meeting topic: kolla)"16:45
inc0I'll look on software which will use my favorite election type;)16:45
zhubingbing About hub kolla on docker image management16:46
sdakeinc0 just ue the standard pollilng software that other projects use16:46
zhubingbinghave long time update16:46
inc0yeah, that's the model I like;)16:46
sdakesean used it - it worked well iirc16:46
*** spzala has joined #openstack-meeting-416:46
berendthttp://civs.cs.cornell.edu16:46
sdakenot civs16:46
zhubingbing I think this should be updated regularly.16:47
sdakeif you want to go through the trobule of civs, that is fine, but that doesnt tell us what is essential vs what is noot16:47
sdakeit just orders talks in priority16:47
britthouseryeah CIVS picks one winner, not a priority list.16:47
sdakeit does prodduce a priority16:48
inc0sdake, everyone will sort it using preference16:48
inc0and we'll draw a red line at some point16:48
sdakebut it doesn't answer the equestion of "what is essential"16:48
sdakered line = you mean zero budget baseine ;)16:48
inc0exactly16:48
*** Swami has joined #openstack-meeting-416:48
*** liuyulong__ has quit IRC16:49
inc0and that will be up to next ptl;)16:49
sdakeok well knock yoursself out16:49
inc0whoever that might be;)16:49
britthouserHave we entered the #stumping part of the meeting? =P16:49
sdakei would offer guidance to the next ptl whoever that may be to follow community decision making on this topic16:49
sdakethats what I do - and it work well16:49
sdakevs some off-base agenda which doesn't include topics people are interessted in16:50
sdakein other words, refrence the etherpad16:50
sdakebritthouser don't think so16:50
sdakezhubingbing on to your topic16:50
sdakezhubingbing our proces around updating docker hub is as follows16:51
sdake1.1.0 released -> docker hub push16:51
sdake1.1.1 releaed -> docker hub push16:51
inc0also britthouser civs can do multiple winners - like TC eletion16:51
zhubingbing3.0.016:51
sdake1.1.2 releaeed -> docker hub push16:51
sdake2.0.0 released -> docker hub push16:51
Jeffrey4lthe poing is: should we push master image?16:51
sdake2.0.1 ereleased -> docker hub push16:51
zhubingbingyes16:51
sdake2.0.2 releaseed -> docker hub push16:51
sdake3.0.0 released -> docker hub push16:51
sdake3.0.0.0b1 releaseed - > NO docker hub push16:52
sdaketake my word for it, dont open that can of worms16:52
sdakeJeffrey4l in other words, no16:52
wznoinskJeffrey4l: is it a question about master or rcX?16:52
Jeffrey4lmaster branch i mean wznoinsk16:53
sdakeif you don't notice the pattern above, we only push to docker hub our stable images16:53
duonghqshoud the 3.0.0 images be uploaded to docker hub for a few months ago?16:53
Jeffrey4lhttps://hub.docker.com/r/kolla/centos-binary-nova-compute/tags/16:53
sdakemaster is not stable as referencced by the 107 bugs in rc216:53
Jeffrey4lwe already pushed some 3.0.0 image .16:53
sdakeduonghq 3.0.0 is unreleased16:53
duonghqso the 3.0.0 is pushed by mistake?16:54
sdakeif we pushed 3.0.0 images accidentally they should be deleted16:54
Jeffrey4lroger. i am agree not push unstable image.16:54
sdakewhoever created  that problem pleae fix it16:54
Jeffrey4lya.16:54
zhubingbingok16:54
zhubingbingi understand16:54
duonghqya, those images are placed for awhile16:54
pbourkeso will you send that poll via ML inc0 ?16:54
inc0pbourke, yeah16:55
pbourkeinc0: cool thanks16:55
*** iyamahat has joined #openstack-meeting-416:55
sdakepbourke he said it would hit ml today16:55
inc0I'll put ZBB with total number of sessions16:55
wznoinskJeffrey4l: +116:55
*** Swami_ has joined #openstack-meeting-416:55
sdakekeep in mind the zbb may change16:55
inc0if we decide to move it a bit up, to give back to foundation, we'll decide afterwards16:55
sdake;)16:55
sdakewe need  to make that decision now inc016:56
inc0I want to see priorities first16:56
sdakenot in 1 month16:56
*** yamamoto has quit IRC16:56
inc0poll will be open for 6 days and we'll decide on next meeting16:57
inc0fair enough?16:57
sdakewfm16:57
*** rhallisey has joined #openstack-meeting-416:57
britthouser+!16:57
britthouser+116:57
sdakeok any other business?16:57
rhallisey:)16:57
rhalliseyI'm here for the woot for kolla?16:57
rhalliseydid I miss it?16:58
sdakeone last thing - we have a half day contributor meetup16:58
inc0yes, woot for kola16:58
sdakewe can ue this spce however we like16:58
inc0thanks rhallisey16:58
inc0woot!!16:58
rhalliseywoot!16:58
sdakeso we can bleed our zbb into that if we need16:58
sdakelets woot later after 3.0.0 is completed :)16:58
berendt1 minute left16:59
*** egonzalez90 has quit IRC16:59
sdakeyup - time for concllsuion of the meeting16:59
sdakepleasse please help with prioritizatino of bugs16:59
sdakeand respond on the poll16:59
sdakeand vote for your ptl to serve as your future leader16:59
sdakethanks ;)16:59
sdake#endmeeting16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:59
openstackMeeting ended Wed Sep 21 16:59:42 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-09-21-16.00.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-09-21-16.00.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-09-21-16.00.log.html16:59
*** Swami has quit IRC16:59
zhubingbingleader17:00
*** wirehead_ has left #openstack-meeting-417:00
*** rhallisey has left #openstack-meeting-417:00
*** vhosakot has left #openstack-meeting-417:00
wznoinskthanks guys17:00
*** duonghq has left #openstack-meeting-417:01
*** bdaca has left #openstack-meeting-417:01
*** zhubingbing has left #openstack-meeting-417:02
*** krtaylor has joined #openstack-meeting-417:04
*** jichen has joined #openstack-meeting-417:04
*** bobh has joined #openstack-meeting-417:07
*** unicell1 has quit IRC17:10
*** Swami_ has quit IRC17:11
*** yamahata has joined #openstack-meeting-417:12
*** bobh has quit IRC17:13
*** LotharKAtt has quit IRC17:13
*** singlethink has joined #openstack-meeting-417:17
*** Swami has joined #openstack-meeting-417:24
*** jichen has quit IRC17:26
*** jichen has joined #openstack-meeting-417:28
*** cdelatte has joined #openstack-meeting-417:32
*** mfedosin has quit IRC17:32
*** ddieterly is now known as ddieterly[away]17:32
*** jichen_ has joined #openstack-meeting-417:32
*** jichen has quit IRC17:33
*** singleth_ has joined #openstack-meeting-417:33
*** jichen_ is now known as jichen17:33
*** jed56 has quit IRC17:35
*** pc_m has joined #openstack-meeting-417:35
*** pc_m has left #openstack-meeting-417:35
*** singlethink has quit IRC17:36
*** unicell has joined #openstack-meeting-417:36
*** iberezovskiy is now known as iberezovskiy|off17:38
*** njohnsto_ has joined #openstack-meeting-417:38
*** omnipresent has quit IRC17:39
*** zenoway has joined #openstack-meeting-417:39
*** pvaneck has joined #openstack-meeting-417:40
*** iyamahat has quit IRC17:43
*** iyamahat has joined #openstack-meeting-417:43
*** zenoway has quit IRC17:43
*** njohnsto_ has quit IRC17:43
*** inc0 has quit IRC17:47
*** degorenko is now known as _degorenko|afk17:47
*** sshnaidm is now known as sshnaidm|afk17:52
*** zenoway has joined #openstack-meeting-417:52
*** zenoway has quit IRC17:56
*** hemanthm is now known as hemanthm|lunch17:56
*** zenoway has joined #openstack-meeting-417:56
*** yamamoto has joined #openstack-meeting-417:57
*** LotharKAtt has joined #openstack-meeting-417:59
*** LotharKAtt has quit IRC17:59
*** LotharKAtt has joined #openstack-meeting-418:00
*** bpokorny_ has joined #openstack-meeting-418:00
*** zenoway has quit IRC18:01
*** bpokorny has quit IRC18:03
*** yamamoto has quit IRC18:05
*** vishnoianil has quit IRC18:07
*** rainya has joined #openstack-meeting-418:09
*** bobh has joined #openstack-meeting-418:10
*** vkmc|afk is now known as vkmc18:12
*** khushbu has joined #openstack-meeting-418:13
*** rainya has quit IRC18:14
*** tonytan4ever has quit IRC18:14
*** bobh has quit IRC18:14
*** tonytan4ever has joined #openstack-meeting-418:15
*** baoli has quit IRC18:19
*** baoli has joined #openstack-meeting-418:20
*** inc0 has joined #openstack-meeting-418:23
*** automagically has joined #openstack-meeting-418:26
*** sbezverk has quit IRC18:26
*** hemanthm|lunch is now known as hemanthm18:30
*** jichen has quit IRC18:31
*** jorgem[away] is now known as jorgem18:34
*** sdake has quit IRC18:39
*** vhoward has joined #openstack-meeting-418:41
*** khushbu has quit IRC18:46
*** klamath has quit IRC18:47
*** inc0 has left #openstack-meeting-418:48
*** uck_ has joined #openstack-meeting-418:49
*** uck has quit IRC18:49
*** ddieterly[away] is now known as ddieterly18:50
*** ig0r_ has joined #openstack-meeting-418:52
*** qwebirc15194 has joined #openstack-meeting-418:52
*** LotharKAtt has quit IRC18:53
*** vishnoianil has joined #openstack-meeting-418:54
*** qwebirc15194 has quit IRC18:55
*** sdake has joined #openstack-meeting-418:56
*** Kingsjo has joined #openstack-meeting-419:00
*** ddieterly is now known as ddieterly[away]19:06
*** bobh has joined #openstack-meeting-419:11
*** bobh has quit IRC19:16
*** ddieterly[away] is now known as ddieterly19:19
*** kingsjo_ has joined #openstack-meeting-419:23
*** Kingsjo has left #openstack-meeting-419:24
*** dtardivel has quit IRC19:27
*** iyamahat has quit IRC19:28
*** uck has joined #openstack-meeting-419:29
*** uck_ has quit IRC19:29
*** ddieterly is now known as ddieterly[away]19:30
*** ddieterly[away] is now known as ddieterly19:37
*** mfisch has quit IRC19:37
*** tonytan_brb has joined #openstack-meeting-419:41
*** salv-orlando has joined #openstack-meeting-419:42
*** tonytan4ever has quit IRC19:44
*** salv-orl_ has quit IRC19:46
*** vhoward has quit IRC19:47
*** kingsjo_ has quit IRC19:47
*** bjolo has quit IRC19:49
*** bjolo_ has joined #openstack-meeting-419:49
*** cdelatte has quit IRC19:54
*** prateek has quit IRC20:03
*** iyamahat has joined #openstack-meeting-420:21
*** barmaley has joined #openstack-meeting-420:31
*** baoli has quit IRC20:33
*** baoli has joined #openstack-meeting-420:33
*** Jeffrey4l has quit IRC20:35
*** banix has quit IRC20:36
*** Jeffrey4l has joined #openstack-meeting-420:37
*** revon has joined #openstack-meeting-420:38
*** ddieterly is now known as ddieterly[away]20:41
*** coolsvap has quit IRC20:42
*** wznoinsk has quit IRC20:44
*** wznoinsk has joined #openstack-meeting-420:45
*** uxdanielle has quit IRC20:55
*** krtaylor has quit IRC20:56
*** JRobinson__ has joined #openstack-meeting-420:59
JRobinson__Hello, The User Guide Speciality team meeting is starting now.21:00
*** bpokorny_ has quit IRC21:01
*** baoli has quit IRC21:02
*** bpokorny has joined #openstack-meeting-421:02
*** baoli has joined #openstack-meeting-421:02
JRobinson__#startmeeting docuserguides21:03
openstackMeeting started Wed Sep 21 21:03:33 2016 UTC and is due to finish in 60 minutes.  The chair is JRobinson__. Information about MeetBot at http://wiki.debian.org/MeetBot.21:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:03
*** openstack changes topic to " (Meeting topic: docuserguides)"21:03
openstackThe meeting name has been set to 'docuserguides'21:03
JRobinson__I've kept the agenda to the point today, so only a few items to choose from.21:04
*** cleong has quit IRC21:04
JRobinson__Any contributors here for the meeting?21:04
*** ddieterly[away] is now known as ddieterly21:07
*** cdelatte has joined #openstack-meeting-421:08
JRobinson__#topic Action items from last meeting21:08
*** openstack changes topic to "Action items from last meeting (Meeting topic: docuserguides)"21:08
JRobinson__No items to action.21:08
*** woodard has quit IRC21:08
JRobinson__#topic User Guide editing blueprint21:09
*** openstack changes topic to "User Guide editing blueprint (Meeting topic: docuserguides)"21:09
JRobinson__This is the key point that needs to be brought up for today.21:09
JRobinson__hmm, having trouble locating the blueprint itself21:12
JRobinson__#link https://blueprints.launchpad.net/openstack/?searchtext=user-guide-editing21:12
*** bobh has joined #openstack-meeting-421:13
JRobinson__However, the point stands that the one or two patches on the topic have had some great reviews from docs contributors suggesting content edits while they are at review.openstack21:13
JRobinson__#info Thanks to the contributor editing patches in review!21:13
JRobinson__#topic OpenStack command line client21:14
*** openstack changes topic to "OpenStack command line client (Meeting topic: docuserguides)"21:14
JRobinson__This was a short point - It's still a work item to remove the service specific clients from the User Guide, and replace them with the OpenStack cli.21:14
JRobinson__#info Using the content available at in the OpenStack CLI guide. Is this the best source of information on the new commands?21:15
JRobinson__^that was the one question to mention at the meeting.21:15
JRobinson__#topic Open Discussion21:15
*** openstack changes topic to "Open Discussion (Meeting topic: docuserguides)"21:15
JRobinson__Since it's just me today, I'm going to close the meeting, but if anyone reading or interested can answer the cli question above, please get in contact.21:16
JRobinson__details are here21:16
JRobinson__#link https://wiki.openstack.org/wiki/User_Guides#About_the_User_Guide_team21:16
JRobinson__Or the OpenStack docs mailing list.21:16
JRobinson__Thanks all o/21:16
JRobinson__#endmeeting21:16
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:16
openstackMeeting ended Wed Sep 21 21:16:47 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:16
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-09-21-21.03.html21:16
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-09-21-21.03.txt21:16
openstackLog:            http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-09-21-21.03.log.html21:16
*** bobh has quit IRC21:18
*** baoli_ has joined #openstack-meeting-421:19
*** baoli has quit IRC21:19
*** baoli_ has quit IRC21:19
*** baoli has joined #openstack-meeting-421:20
*** salv-orlando has quit IRC21:26
*** salv-orlando has joined #openstack-meeting-421:27
*** baoli has quit IRC21:28
*** baoli has joined #openstack-meeting-421:29
*** banix has joined #openstack-meeting-421:32
*** JRobinson__ is now known as JRobinson__afk21:33
*** banix_ has joined #openstack-meeting-421:35
*** banix has quit IRC21:37
*** banix_ is now known as banix21:37
*** rtheis has quit IRC21:39
*** krtaylor has joined #openstack-meeting-421:40
*** JRobinson__afk is now known as JRobinson__21:40
*** rcaballeromx has joined #openstack-meeting-421:44
*** ig0r_ has quit IRC21:45
*** dshakhray has quit IRC21:46
*** mfranc213 has quit IRC21:58
*** Swami has quit IRC21:58
*** armax has quit IRC21:59
*** armax has joined #openstack-meeting-422:00
*** mfranc213 has joined #openstack-meeting-422:03
*** ddieterly is now known as ddieterly[away]22:03
*** bpokorny has quit IRC22:05
*** spotz is now known as spotz_zzz22:07
*** klamath has joined #openstack-meeting-422:10
*** bobh has joined #openstack-meeting-422:10
*** hemanthm is now known as hemanthm|away22:17
*** bpokorny has joined #openstack-meeting-422:17
*** marst has quit IRC22:17
*** s3wong has joined #openstack-meeting-422:18
*** spzala has quit IRC22:20
*** spzala has joined #openstack-meeting-422:20
*** ddieterly[away] is now known as ddieterly22:21
*** claudiub has quit IRC22:23
*** spzala has quit IRC22:25
*** limao has joined #openstack-meeting-422:30
*** thorst has joined #openstack-meeting-422:31
*** limao_ has joined #openstack-meeting-422:32
*** limao has quit IRC22:35
*** jovon has quit IRC22:36
*** marst has joined #openstack-meeting-422:36
*** bobh has quit IRC22:37
*** banix has quit IRC22:39
*** ddieterly has quit IRC22:40
*** yamahata has quit IRC22:40
*** thorst has quit IRC22:41
*** thorst has joined #openstack-meeting-422:41
*** markvoelker has quit IRC22:43
*** Swami has joined #openstack-meeting-422:44
*** singleth_ has quit IRC22:45
*** thorst has quit IRC22:46
*** Swami has quit IRC22:46
*** Swami has joined #openstack-meeting-422:46
*** rcaballeromx has quit IRC22:47
*** Swami_ has joined #openstack-meeting-422:52
*** limao has joined #openstack-meeting-422:52
*** thorst has joined #openstack-meeting-422:54
*** barmaley has quit IRC22:54
*** Swami has quit IRC22:54
*** banix has joined #openstack-meeting-422:54
*** limao_ has quit IRC22:55
*** yamahata has joined #openstack-meeting-422:56
*** rbak has quit IRC22:57
*** thorst has quit IRC22:59
*** sdague has quit IRC23:00
*** banix has quit IRC23:00
*** baoli has quit IRC23:04
*** limao has quit IRC23:05
*** hongbin has quit IRC23:05
*** Julien-zte has joined #openstack-meeting-423:11
*** yamamoto has joined #openstack-meeting-423:17
*** klamath has quit IRC23:17
JRobinson__Hi All, the Second fortnightly User Guide team meeting is set to start soon, pending attendance.23:28
*** tri2sing has quit IRC23:28
*** bmoss has joined #openstack-meeting-423:32
*** Julien-zte has quit IRC23:36
*** uck_ has joined #openstack-meeting-423:38
*** uck has quit IRC23:38
JRobinson__Okay, since it seems fairly quiet, I'm going to call off the APAC User Guide team meeting.23:39
JRobinson__thanks all o/23:39
bmosso/23:41
*** bmoss has left #openstack-meeting-423:41
*** markvoelker has joined #openstack-meeting-423:44
*** zhurong has joined #openstack-meeting-423:46
*** markvoelker has quit IRC23:49
*** galstrom_zzz is now known as galstrom23:50
*** yamamoto has quit IRC23:53
*** zhurong has quit IRC23:57
*** JRobinson__ is now known as JRobinson__afk23:59

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