Wednesday, 2016-03-23

*** ddieterly has joined #openstack-meeting-400:01
*** salv-orl_ has joined #openstack-meeting-400:02
*** dims_ has joined #openstack-meeting-400:03
*** dims has quit IRC00:04
*** salv-orlando has quit IRC00:05
*** Sukhdev has joined #openstack-meeting-400:06
*** salv-orl_ has quit IRC00:07
*** baoli has quit IRC00:09
*** baoli has joined #openstack-meeting-400:10
*** iyamahat has quit IRC00:15
*** avarner_ has quit IRC00:17
*** iyamahat has joined #openstack-meeting-400:20
*** SumitNaiksatam has quit IRC00:26
*** sridhar_ram has joined #openstack-meeting-400:28
*** sshnaidm has quit IRC00:30
*** unicell has joined #openstack-meeting-400:31
*** baoli has quit IRC00:32
*** Swami has quit IRC00:32
*** thorst has joined #openstack-meeting-400:34
*** angdraug has quit IRC00:35
*** thorst_ has joined #openstack-meeting-400:35
*** saneax is now known as saneax_AFK00:37
*** thorst has quit IRC00:40
*** lakshmiS has joined #openstack-meeting-400:40
*** piet has joined #openstack-meeting-400:41
*** krotscheck has joined #openstack-meeting-400:42
*** reedip_away is now known as reedip00:49
*** sdake has quit IRC00:50
*** klamath has quit IRC00:50
*** klamath has joined #openstack-meeting-400:50
*** sdake has joined #openstack-meeting-400:51
*** klamath has quit IRC00:51
*** klamath has joined #openstack-meeting-400:52
*** daneyon has quit IRC01:00
*** unicell has quit IRC01:00
*** sridhar_ram has quit IRC01:03
*** SumitNaiksatam has joined #openstack-meeting-401:09
*** Sukhdev has quit IRC01:12
*** zhurong has joined #openstack-meeting-401:15
*** piet has quit IRC01:15
*** fawadkhaliq has quit IRC01:18
*** fawadkhaliq has joined #openstack-meeting-401:18
*** fawadkhaliq has quit IRC01:19
*** fawadkhaliq has joined #openstack-meeting-401:20
*** baoli has joined #openstack-meeting-401:24
*** lakshmiS has quit IRC01:25
*** thorst_ has quit IRC01:27
*** thorst has joined #openstack-meeting-401:27
*** daneyon has joined #openstack-meeting-401:29
*** baoli has quit IRC01:30
*** sshnaidm has joined #openstack-meeting-401:30
*** bobh has joined #openstack-meeting-401:31
*** bobh has quit IRC01:32
*** chigang has joined #openstack-meeting-401:33
*** baoli has joined #openstack-meeting-401:34
*** salv-orlando has joined #openstack-meeting-401:35
*** daneyon has quit IRC01:35
*** daneyon has joined #openstack-meeting-401:36
*** ddieterly is now known as ddieterly[away]01:36
*** thorst has quit IRC01:36
*** bobh has joined #openstack-meeting-401:37
*** IlyaG has joined #openstack-meeting-401:38
*** dims_ has quit IRC01:40
*** iyamahat has quit IRC01:42
*** salv-orlando has quit IRC01:42
*** yamahata has quit IRC01:43
*** bobh has quit IRC01:52
*** harshs has quit IRC01:52
*** s3wong has quit IRC01:59
*** fawadkhaliq has quit IRC02:01
*** fawadkhaliq has joined #openstack-meeting-402:02
*** ddieterly[away] is now known as ddieterly02:02
*** xarses has joined #openstack-meeting-402:03
*** bobh has joined #openstack-meeting-402:04
*** fawadkhaliq has quit IRC02:10
*** fawadkhaliq has joined #openstack-meeting-402:10
*** bpokorny_ has joined #openstack-meeting-402:11
*** bpokorny_ has quit IRC02:11
*** bryan_att has quit IRC02:12
*** ddieterly is now known as ddieterly[away]02:13
*** azbiswas has joined #openstack-meeting-402:14
*** bpokorny has quit IRC02:15
*** neelashah has joined #openstack-meeting-402:22
*** banix has joined #openstack-meeting-402:23
*** IlyaG has quit IRC02:24
*** vtech has quit IRC02:27
*** vtech has joined #openstack-meeting-402:27
*** thorst has joined #openstack-meeting-402:34
*** MarkAtwood has joined #openstack-meeting-402:40
*** thorst has quit IRC02:41
*** salv-orlando has joined #openstack-meeting-402:41
*** neelashah has quit IRC02:45
*** tfukushima has joined #openstack-meeting-402:47
*** salv-orlando has quit IRC02:51
*** fawadkhaliq has quit IRC02:51
*** askb has joined #openstack-meeting-402:52
*** fawadkhaliq has joined #openstack-meeting-402:52
*** iyamahat has joined #openstack-meeting-402:53
*** markvoelker has quit IRC02:59
*** fawadkhaliq has quit IRC03:01
*** fawadkhaliq has joined #openstack-meeting-403:01
*** fawadkhaliq has quit IRC03:01
*** fawadkhaliq has joined #openstack-meeting-403:02
*** bobh has quit IRC03:09
*** piet has joined #openstack-meeting-403:10
*** GB21 has joined #openstack-meeting-403:12
*** ddieterly[away] has quit IRC03:14
*** IlyaG has joined #openstack-meeting-403:22
*** piet has quit IRC03:23
*** yamahata has joined #openstack-meeting-403:26
*** azbiswas_ has joined #openstack-meeting-403:36
*** thorst has joined #openstack-meeting-403:39
*** azbiswas has quit IRC03:39
*** IlyaG has quit IRC03:42
*** GB21 has quit IRC03:44
*** thorst has quit IRC03:46
*** azbiswas_ has quit IRC03:46
*** baoli has quit IRC03:46
*** tfukushima has quit IRC03:57
*** markvoelker has joined #openstack-meeting-403:59
*** markvoelker has quit IRC04:04
*** azbiswas has joined #openstack-meeting-404:06
*** banix has quit IRC04:06
*** salv-orlando has joined #openstack-meeting-404:10
*** baoli has joined #openstack-meeting-404:13
*** salv-orlando has quit IRC04:14
*** baoli has quit IRC04:14
*** baoli has joined #openstack-meeting-404:15
*** fawadkhaliq has quit IRC04:17
*** fawadkhaliq has joined #openstack-meeting-404:17
*** mjblack has quit IRC04:20
*** baoli has quit IRC04:24
*** dave-mccowan has quit IRC04:24
*** yamamoto_ has joined #openstack-meeting-404:30
*** fawadkhaliq has quit IRC04:35
*** fawadkhaliq has joined #openstack-meeting-404:36
*** mjblack has joined #openstack-meeting-404:38
*** fawadkhaliq has quit IRC04:40
*** fawadkhaliq has joined #openstack-meeting-404:41
*** fawadkhaliq has quit IRC04:41
*** fawadkhaliq has joined #openstack-meeting-404:42
*** fawadkhaliq has quit IRC04:42
*** IlyaG has joined #openstack-meeting-404:42
*** fawadkhaliq has joined #openstack-meeting-404:43
*** thorst has joined #openstack-meeting-404:44
*** fawadkhaliq has quit IRC04:46
*** fawadkhaliq has joined #openstack-meeting-404:46
*** fawadkhaliq has quit IRC04:47
*** IlyaG has quit IRC04:47
*** fawadkhaliq has joined #openstack-meeting-404:48
*** fawadkhaliq has quit IRC04:48
*** fawadkhaliq has joined #openstack-meeting-404:49
*** thorst has quit IRC04:52
*** GB21 has joined #openstack-meeting-404:58
*** azbiswas has quit IRC05:00
*** azbiswas has joined #openstack-meeting-405:01
*** MarkAtwood has quit IRC05:04
*** GB21 has quit IRC05:07
*** GB21 has joined #openstack-meeting-405:07
*** sridhar_ram has joined #openstack-meeting-405:16
*** MarkAtwood has joined #openstack-meeting-405:36
*** saneax_AFK is now known as saneax05:38
*** iyamahat has quit IRC05:41
*** salv-orlando has joined #openstack-meeting-405:42
*** salv-orlando has quit IRC05:49
*** thorst has joined #openstack-meeting-405:49
*** thorst has quit IRC05:55
*** Sukhdev has joined #openstack-meeting-405:57
*** markvoelker has joined #openstack-meeting-406:00
*** fawadkhaliq has quit IRC06:03
*** fawadkhaliq has joined #openstack-meeting-406:04
*** markvoelker has quit IRC06:04
*** SumitNaiksatam has quit IRC06:10
*** azbiswas has quit IRC06:15
*** nkrinner has joined #openstack-meeting-406:17
*** azbiswas has joined #openstack-meeting-406:19
*** fawadkhaliq has quit IRC06:20
*** fawadkhaliq has joined #openstack-meeting-406:21
*** ihrachys has joined #openstack-meeting-406:22
*** IlyaG has joined #openstack-meeting-406:23
*** azbiswas has quit IRC06:24
*** fawadkhaliq has quit IRC06:25
*** fawadkhaliq has joined #openstack-meeting-406:25
*** fawadkhaliq has quit IRC06:26
*** fawadkhaliq has joined #openstack-meeting-406:26
*** fawadkhaliq has quit IRC06:27
*** anilvenkata has joined #openstack-meeting-406:28
*** azbiswas has joined #openstack-meeting-406:28
*** fawadkhaliq has joined #openstack-meeting-406:28
*** IlyaG has quit IRC06:28
*** fawadkhaliq has quit IRC06:28
*** fawadkhaliq has joined #openstack-meeting-406:29
*** azbiswas has quit IRC06:31
*** ihrachys has quit IRC06:31
*** sdake_ has joined #openstack-meeting-406:35
*** sdake has quit IRC06:36
*** azbiswas has joined #openstack-meeting-406:38
*** azbiswas has quit IRC06:38
*** sdake_ has quit IRC06:44
*** iyamahat has joined #openstack-meeting-406:44
*** sdake has joined #openstack-meeting-406:44
*** sridhar_ram has quit IRC06:46
*** MarkAtwood has quit IRC06:47
*** wanghua has joined #openstack-meeting-406:51
*** thorst has joined #openstack-meeting-406:53
*** salv-orlando has joined #openstack-meeting-406:58
*** thorst has quit IRC07:01
*** markvoelker has joined #openstack-meeting-407:01
*** vishnoianil has quit IRC07:05
*** watanabe_isao has joined #openstack-meeting-407:06
*** markvoelker has quit IRC07:07
*** vishwanathj is now known as vishwanathj_away07:12
*** hdaniel has joined #openstack-meeting-407:13
*** salv-orlando has quit IRC07:15
*** sridhar_ram has joined #openstack-meeting-407:19
*** sridhar_ram has quit IRC07:19
*** lazy_prince has quit IRC07:23
*** GB21 has quit IRC07:23
*** sdake has quit IRC07:23
*** Sukhdev has quit IRC07:25
*** GB21 has joined #openstack-meeting-407:25
*** davidlenwell has quit IRC07:26
*** lazy_prince has joined #openstack-meeting-407:26
*** vishnoianil has joined #openstack-meeting-407:32
*** davidlenwell has joined #openstack-meeting-407:34
*** kebray has quit IRC07:38
*** kebray has joined #openstack-meeting-407:41
*** vtech has quit IRC07:42
*** GB21 has quit IRC07:49
*** zeih has joined #openstack-meeting-407:55
*** thorst has joined #openstack-meeting-407:58
*** dtardivel has joined #openstack-meeting-408:00
*** vtech has joined #openstack-meeting-408:02
*** kebray has quit IRC08:04
*** thorst has quit IRC08:06
*** kebray has joined #openstack-meeting-408:10
*** nkrinner has quit IRC08:12
*** matrohon has joined #openstack-meeting-408:13
*** cemason has joined #openstack-meeting-408:14
*** zhurong has quit IRC08:16
*** nkrinner has joined #openstack-meeting-408:17
*** chem has quit IRC08:22
*** MarkAtwood has joined #openstack-meeting-408:26
*** jschwarz has joined #openstack-meeting-408:27
*** paul-carlton1 has joined #openstack-meeting-408:29
*** hdaniel has quit IRC08:29
*** ihrachys has joined #openstack-meeting-408:30
*** MarkAtwood has quit IRC08:31
*** mbound has joined #openstack-meeting-408:34
*** zhurong has joined #openstack-meeting-408:34
*** watanabe_isao has quit IRC08:39
*** hdaniel has joined #openstack-meeting-408:44
*** jed56 has joined #openstack-meeting-408:44
*** GB21 has joined #openstack-meeting-408:54
*** russellb has quit IRC08:58
*** paul-carlton1 has quit IRC08:58
*** itisha has quit IRC08:59
*** russellb has joined #openstack-meeting-409:00
*** evgenyf has joined #openstack-meeting-409:00
*** piet has joined #openstack-meeting-409:01
*** markvoelker has joined #openstack-meeting-409:03
*** thorst has joined #openstack-meeting-409:03
*** vtech_ has joined #openstack-meeting-409:06
*** vtech has quit IRC09:06
*** salv-orlando has joined #openstack-meeting-409:06
*** markvoelker has quit IRC09:08
*** zhurong has quit IRC09:09
*** hdaniel has quit IRC09:09
*** thorst has quit IRC09:11
*** zeih_ has joined #openstack-meeting-409:13
*** zeih has quit IRC09:13
*** piet has quit IRC09:16
*** yamahata has quit IRC09:27
*** May-meimei has quit IRC09:27
*** iyamahat has quit IRC09:28
*** sshnaidm has quit IRC09:56
*** sdague has joined #openstack-meeting-409:58
*** dims has joined #openstack-meeting-410:00
*** sambetts|afk is now known as sambetts10:00
*** janki91 has joined #openstack-meeting-410:02
*** wanghua has quit IRC10:04
*** GB21 has quit IRC10:05
*** thorst has joined #openstack-meeting-410:08
*** zhurong has joined #openstack-meeting-410:11
*** pbourke has quit IRC10:14
*** pbourke has joined #openstack-meeting-410:15
*** thorst has quit IRC10:16
*** askb has quit IRC10:19
*** GB21 has joined #openstack-meeting-410:22
*** hdaniel has joined #openstack-meeting-410:31
*** Jeffrey4l has joined #openstack-meeting-410:49
*** sshnaidm has joined #openstack-meeting-410:51
*** _degorenko|afk is now known as degorenko10:51
*** shaohe_feng_robo has quit IRC10:52
*** zeih_ has quit IRC10:58
*** zhurong has quit IRC10:59
*** zhurong has joined #openstack-meeting-411:02
*** MarkAtwood has joined #openstack-meeting-411:02
*** markvoelker has joined #openstack-meeting-411:04
*** dims_ has joined #openstack-meeting-411:05
*** dims has quit IRC11:06
*** MarkAtwood has quit IRC11:07
*** markvoelker has quit IRC11:08
*** Jeffrey4l has quit IRC11:10
*** GB21 has quit IRC11:15
*** Jeffrey4l has joined #openstack-meeting-411:17
*** Jeffrey4l has quit IRC11:28
*** thorst has joined #openstack-meeting-411:35
*** jinquan has joined #openstack-meeting-411:42
*** rtheis has joined #openstack-meeting-411:43
*** Jeffrey4l has joined #openstack-meeting-411:47
*** askb has joined #openstack-meeting-411:51
*** askb has quit IRC11:51
*** askb has joined #openstack-meeting-411:56
*** zeih has joined #openstack-meeting-411:57
*** Jeffrey4l has quit IRC11:58
*** david-lyle_ has joined #openstack-meeting-411:58
*** david-lyle has quit IRC12:00
*** salv-orl_ has joined #openstack-meeting-412:02
*** karenb has joined #openstack-meeting-412:04
*** salv-orlando has quit IRC12:04
*** annegentle has joined #openstack-meeting-412:12
*** markvoelker has joined #openstack-meeting-412:20
*** yamamoto_ has quit IRC12:20
*** GB21 has joined #openstack-meeting-412:21
*** annegentle has quit IRC12:23
*** karenb has quit IRC12:23
*** Jeffrey4l has joined #openstack-meeting-412:25
*** krtaylor has quit IRC12:32
*** piet has joined #openstack-meeting-412:36
*** woodard has joined #openstack-meeting-412:36
*** annegentle has joined #openstack-meeting-412:37
*** gmann_ has joined #openstack-meeting-412:38
*** Jeffrey4l has quit IRC12:38
*** baohua has joined #openstack-meeting-412:39
*** Jeffrey4l has joined #openstack-meeting-412:40
*** krtaylor has joined #openstack-meeting-412:46
*** Jeffrey4l has quit IRC12:47
*** baoli has joined #openstack-meeting-412:48
*** mbound has quit IRC12:49
*** MarkAtwood has joined #openstack-meeting-412:51
*** ddieterly has joined #openstack-meeting-412:52
*** klamath has quit IRC12:52
*** dave-mccowan has joined #openstack-meeting-412:52
*** klamath has joined #openstack-meeting-412:52
*** ddieterly is now known as ddieterly[away]12:53
*** ninag has joined #openstack-meeting-412:53
*** tojuvone has joined #openstack-meeting-412:54
*** cdent has joined #openstack-meeting-412:55
*** MarkAtwood has quit IRC12:55
*** oomichi_ has joined #openstack-meeting-412:57
*** zeih has quit IRC12:58
alex_xu#startmeeting nova api13:00
openstackMeeting started Wed Mar 23 13:00:02 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
oomichi_hi13:00
annegentleo/13:00
gmann_hi13:00
tojuvonehi13:00
sdagueo/13:00
Kevin_Zhenghi13:00
alex_xuwelcome everyone, let's start the meeting13:00
alex_xu#topic Nova Microversion testing in Tempest13:00
*** openstack changes topic to "Nova Microversion testing in Tempest (Meeting topic: nova api)"13:00
alex_xugmann_: your turn first13:01
*** vhoward has joined #openstack-meeting-413:01
gmann_ye13:01
cdento/13:01
annegentleanyone have a link to the agenda handy?13:01
alex_xuannegentle: https://wiki.openstack.org/wiki/Meetings/NovaAPI13:01
gmann_so all necessary patches are merged now.13:01
annegentlety!13:01
gmann_framework is in tempest/lib and 2.2 tests are already running on gate13:01
gmann_u2.10 and 2.20 are up13:02
alex_xugmann_: cool, I guess just need some review on specific version test13:02
*** karenb has joined #openstack-meeting-413:02
gmann_so basically microverions tests can be implemented13:02
gmann_yea13:02
oomichi_nice :-)13:02
gmann_creating doc for those also13:02
gmann_#link https://review.openstack.org/#/c/261426/13:02
gmann_oomichi_: Thanks for review. i updated that patch13:03
annegentlewoop woop doc :)13:03
oomichi_gmann_: ok, will review it again later13:03
*** ddieterly[away] has quit IRC13:03
gmann_That's all from my side13:03
alex_xugmann_: thanks for the works, really good progress!13:03
gmann_annegentle: :)13:03
gmann_alex_xu: npo13:03
gmann_np13:03
*** alexchadin has joined #openstack-meeting-413:03
alex_xu#topic API Doc13:04
*** openstack changes topic to "API Doc (Meeting topic: nova api)"13:04
alex_xu#link https://review.openstack.org/#/c/294078/13:04
* edleafe walks in late13:04
gmann_sdague: Thanks, i saw the devstack patch for capping the max microversion for mitaka.13:04
alex_xusdague: ^ I saw this in the agenda, so i start a separate topic for this, do you want to update something for this PoC13:04
sdaguealex_xu: yeh, we wanted to talk about this a bit for where we're getting13:05
sdagueI think this etherpad is probably a better link so far - https://etherpad.openstack.org/p/api-site-in-rst13:05
annegentlealso I invited karenb who has been working on fairy-slipper13:05
karenbhi13:05
* annegentle waves13:06
sdagueLast week I spent much of the week trying to see what it would look like to get our API docs over into RST more directly, plus a bit of structured content for things like tables13:06
karenbI just started to look at your patch13:06
*** david-lyle_ is now known as david-lyle13:06
sdaguehttp://docs-draft.openstack.org/51/294151/4/check/gate-nova-docs/c2a264a//doc/build/html/rest_api/servers.html is an example of what the output looks like for the servers resource13:06
* alex_xu poke oomichi_: we should have something similar with swagger also13:06
* johnthetubaguy nodding with respect at the etherpad13:06
sdaguekarenb: yeh, it's kind of a mess of a patch stack, so appologies in advance, this was mostly just pushing forward to see where we could get to13:07
karenbI am a bit behind in understanding how this fits together13:07
annegentlealex_xu: I think what we're finding though is swagger needs too much additional engineering to get an author/ publish workflow13:07
sdaguethe crux of this is - RST files that look like this - https://raw.githubusercontent.com/openstack/nova/e8afd02ca66a0801974ba2199c5323736c606257/doc/source/rest_api/servers.rst13:07
sdagueok, so how about I provide some common background13:07
karenbare you trying to automate the generation of parameter definitions13:07
annegentlekarenb: yeah sorry for the "oh geez context"13:07
sdague2 weeks ago I spent some time looking at swagger and how it would apply to a long standing api like compute13:08
annegentlemostly sdague and my concerns are around ongoing maintenance13:08
annegentleboth of content and tooling13:08
alex_xuannegentle: yes13:08
sdagueand the problem is that swagger (and raml) is an API design tool, that has the side benefit of a docs framework13:08
annegentlesdague: yeah it's the legacy APIs that aren't a fit13:08
sdaguehowever, if you don't start with swagger at your design, things like request parameter body is pretty rough to model13:09
karenbyes, agreed.  there is some mismatch13:09
annegentlekarenb has dug in and yeah...13:09
oomichi_sdague: yeah, I know13:09
alex_xusdague: yes13:09
sdaguebecause it expects a pretty strict model definition for in: body fields13:09
sdaguethat we just don't have13:09
*** banix has joined #openstack-meeting-413:09
sdaguehowever, the WADL stack we have today is definitely holding us back from having docs that people can use13:10
annegentleoh for sure13:10
alex_xusdague: wait, body just a json-schema, why we said it is rough to model?13:10
*** alexchadin has quit IRC13:10
johnthetubaguyadding microversion to WADL seem like a backwards step, so we need another route13:10
sdagueso... could we have a nearish term solution of getting over to RST13:10
oomichi_sdague: I have another idea now, my prototype is trying to create swagger data from api router info instead of the code13:10
*** rbak has joined #openstack-meeting-413:10
sdaguealex_xu: it's not just jsonschema13:11
oomichi_sdague: https://review.openstack.org/#/c/296146/13:11
annegentleoomichi_: that's the idea for fairy-slipper too but the engineering burden is then high13:11
karenbjson schema should be able to model the api, no?13:11
sdaguekarenb: parts of it, probably13:11
annegentlekarenb: at least the request/ responses in this case I believe13:11
sdagueour jsonschema changes based on microversion though13:11
annegentle(nova has those defined?)13:11
annegentlesdague: ah ok13:11
sdaguesome of them13:11
oomichi_annegentle: yeah, we need to find a nice way to avoid it13:11
*** neelashah has joined #openstack-meeting-413:11
*** yamamoto has joined #openstack-meeting-413:12
oomichi_and I am trying to create a prototype for action api which is most difficult api for us13:12
sdagueanyway, I feel like the trap that WADL provided us was that we assumed that if we had some machine format, and a tooling pipeline, we end up with good docs13:12
oomichi_to avoid the big burden13:12
sdaguebut, it puts all the burden on the tooling pipeline13:12
gmann_in json schema we can add description for each param etc but those are not yet complete info we can put there13:12
annegentlethe original idea for fairy-slipper was to automate making the reference info. however, in practice nothing was structured enough for "prose plus examples" I believe, and migrating showed us that.13:12
sdagueand doesn't let humans realize that sometimes things have to be explained differently to make sense13:13
annegentleoomichi_: right on the /actions POST, ack13:13
sdaguethere is very little human judgement on the output13:13
oomichi_my idea is to provide swagger definition from REST API directly13:13
sdagueso, let's see what a content first approach looks like13:13
johnthetubaguyso I think we need to have a concrete problems to focus on here, my choice would be: "how do we doc the microversions ASAP" and "how do we replace WADL quickly"?13:13
oomichi_like kurbenetes13:13
johnthetubaguysdague: +1 lets look at that13:13
*** pmesserli has joined #openstack-meeting-413:14
sdagueso, that would be RST that looks like this - https://raw.githubusercontent.com/openstack/nova/e8afd02ca66a0801974ba2199c5323736c606257/doc/source/rest_api/servers.rst13:14
sdagueand you will notice there is a rest_parameters stanza13:14
sdaguewhich is a list of parameters and types, that look up in a different file13:14
karenbhave you determined that swagger cannot replace wadl for compute?13:14
oomichi_johnthetubaguy: nice point. I am thinking swagger definition of microversionscan be gotten easily if REST API13:14
oomichi_johnthetubaguy: because we can specify microversion on nova api13:15
annegentlekarenb: it can, but only with a lot of extensions and then we have toolchain maintenance13:15
sdaguethis is "just enough structure" to make generating tables in RST13:15
*** rbak_ has joined #openstack-meeting-413:15
annegentleoomichi_: also, these parameters.yaml files could be built from Swagger's parameters sections13:15
sdagueoomichi_: I 100% believe that swagger on the compute API is a wild goose chase. You are going to need to hack up swagger way outside the spec to make it work13:15
sdaguethen you have to own an entire swagger publish toolchain13:15
sdaguewe do not have the engineering for that13:16
gmann_sdague: in that rst, can we use json schema for pram definition ?13:16
*** rbak has quit IRC13:16
annegentle#link http://paste.openstack.org/show/491575/13:16
annegentlethis is an example of some yaml pulled from a wadl migration13:16
sdaguegmann_: maybe, it actually looks very much like what fairy-slipper was producing in the wadl -> swagger conversion13:16
*** baoli_ has joined #openstack-meeting-413:16
sdaguehttps://github.com/openstack/nova/blob/e8afd02ca66a0801974ba2199c5323736c606257/doc/source/rest_api/parameters.yaml13:17
annegentleyeah13:17
sdagueI snagged the in: idea from swagger13:17
annegentleto me, this might be an ideal way to prioritize "more contributors by getting off of wadl" while still borrowing what we can from swagger13:17
alex_xuone idea is we generate swagger from code, and generate api doc like sdague's way13:17
annegentlealex_xu: yeah but we've not got the engineering time for that13:18
sdaguehere is the thing, generating swagger from code is engineering effort beyond getting content to the user13:18
annegentlealex_xu: I mean, I would love if we could generate parameters.yaml from code!13:18
annegentlethat would be really cool13:18
johnthetubaguyso I like sdague's approach as it opens up more options for the future, gets us microversion docs, and kills the WADL issue13:18
annegentlebut swagger from code, not so much13:18
sdaguemy concern is what is the shortest path to get off WADL in a content first approach13:18
alex_xuannegentle: ah, yes, something like that13:18
*** zeih has joined #openstack-meeting-413:19
johnthetubaguyyeah, lets get some docs where we control the tooling better, then start iterating some improvements, I love it13:19
sdagueand, because of the way we plug structured data into the RST with things like the rest_parameters stanza, that could clearly be swapped out later for other kinds of structured data13:19
oomichi_another merit of swagger is for client api also if we provide it with rest api13:19
annegentleand I know this is a nova-centric meeting, but of course I have to be the voice of reason for "ALL THE APIS" and I'm okay with RST plus YAML instead of RST plus Swagger for the legacy APIs that don't fit the model well.13:19
oomichi_not only for doc13:19
sdagueoomichi_: all of those are theoretical benefits13:19
alex_xusdague: yes, and we won't generate another huge work for migating wadl to something else13:19
*** baoli has quit IRC13:19
annegentleoomichi_: yeah I know, but most people I talk to aren't huge fans of the generated clients13:19
annegentleoomichi_: believe me, I've asked and asked13:19
annegentleanother thing this makes a bit harder is a "try it out" site13:20
oomichi_because client code also can be genereted from swagger definition via rest api13:20
annegentlebut again, we would need more engineering time13:20
*** mbound has joined #openstack-meeting-413:20
johnthetubaguyso the problem we have is all our new APIs have zero docs13:20
sdagueoomichi_: that I think is the huge falacy that gave us WADL13:20
johnthetubaguyRST gets us there real quick13:20
sdagueWADL was used for the same assumptions13:20
annegentleoomichi_: yes but not unless you use x-post (an extended definition) and then engineer all tools specifically for your extensions13:20
sdagueand it turns out the consumers of our API docs are.... humans13:20
karenbdo you plan on using the sphinx tools to generate html from the rst13:21
annegentleWADL was used for filtering requests13:21
sdagueand we are serving them well13:21
sdaguekarenb: yes13:21
annegentleand we need something that does one thing not multiple13:21
sdaguethis is a normal sphinx pipeline from rst forward13:21
annegentlekarenb: yeah, there is a need for a sphinx extension to make nice tables from yaml13:21
annegentlekarenb: when sdague has created13:21
johnthetubaguyannegentle: yeah, we need the docs, the other stuff we can worry about later13:21
sdagueif you pull that nova branch and run tox -e docs, it will build this html locally13:22
annegentlejohnthetubaguy: agreed, outcome is developer.openstack.org that's useful13:22
annegentlekarenb: what I'd like to do this week is try to use the openstackdocstheme and better CSS for tables13:22
annegentlebut want to be sure we have agreement on the path in general of course13:22
annegentlewe'll also talk about it at the API WG meeting this week13:22
sdagueright13:23
oomichi_annegentle: aren't there any projects which use swagger yet?13:23
sdagueI think the important thing to focus on is how soon can we get real docs to our users13:24
johnthetubaguyit feels like this is our only chance of getting good microversion docs by the end of the cycle, so it excites me13:24
johnthetubaguysdague: +113:24
annegentleoomichi_: magnum has a swagger file, but their API might be redesigned13:24
oomichi_annegentle: ah, ok. thanks for the info13:24
annegentleoomichi_: and sahara has one generated with a pecan plugin I believe13:24
karenbdo you have detailed docs on the use of microversions13:24
karenbI am not sure how that is related to your api model13:25
annegentleoomichi_: we have a patch in progress to build the migrated swagger files13:25
annegentle#link http://docs-draft.openstack.org/59/286659/9/check/gate-build-swagger/95e743a/swagger/compute-v2.1-swagger/index.html13:25
oomichi_annegentle: cool, thanks again :-)13:26
sdaguekarenb: what kind of info are you looking for?13:26
johnthetubaguykarenb: I tend to point people at sdague's blog post: https://dague.net/2015/06/05/the-nova-api-in-kilo-and-beyond-2/13:26
sdagueyeh, that link is good background13:26
alex_xukarenb: and this is also one http://developer.openstack.org/api-guide/compute/microversions.html13:26
sdagueand then there are details in the tree a bit on the ones we've landed13:26
*** trozet_ has joined #openstack-meeting-413:26
annegentle#link http://docs.openstack.org/developer/nova/api_microversions.html13:26
karenbwhat resources are available on what version, how do you access these versions, etc13:26
annegentle^^ yeah that one is for contributor devs13:26
*** GB21 has quit IRC13:27
johnthetubaguyhttp://developer.openstack.org/api-guide/compute/microversions.html13:27
johnthetubaguyoh wait, yeah, thats the same thing, the API user guide13:27
*** banix has quit IRC13:27
alex_xuah, looks like we already have a lot of doc for microverions :)13:27
gmann_:)13:28
sdagueexcept for the user :)13:28
alex_xusdague: this is for user http://developer.openstack.org/api-guide/compute/microversions.html13:28
annegentleonly one for the user and no reference info :)13:28
johnthetubaguyyeah, no reference info yet, thats the aim here13:28
annegentlebut honestly, this is firstly about maintainable content13:28
sdagueoomichi_: we will not that on http://docs-draft.openstack.org/59/286659/9/check/gate-build-swagger/95e743a/swagger/compute-v2.1-swagger/index.html doesn't have response parameters13:28
gmann_yea13:28
sdaguealex_xu: it's not, it doesn't tell them what's in the various microversions13:29
oomichi_sdague: yeah, nice point.13:29
alex_xusdague: ah, I got it13:29
annegentleoomichi_: and that's part of the findings as we got deeper into swagger...13:29
annegentlewhat got us here won't get us there? Or something?13:29
oomichi_sdague: we need to migrate jsonschema from tempest if swagger13:29
oomichi_sdague: then the ownership of jsonshema discussion again..13:30
sdagueoomichi_: again, that's a whole lot of engineering effort before we ever actually solve any problems for our users13:30
alex_xuoomichi_: ah, yes, that is another huge work for support swagger :(13:30
sdaguewe have to be user centric here13:30
annegentleright...13:30
sdaguehow do we solve that fact that anyone who wants to write an application with nova has to read the nova source code today13:30
sdaguesolve for that first13:30
sdaguethen look at ways we might optimize our storage / generation of some of that data13:31
oomichi_sdague: yeah, I know. maybe swagger thing is long-term work on nova. not so soon ;-)13:31
*** jmckind has joined #openstack-meeting-413:31
annegentleoomichi_: yeah, that's my sense of it13:31
alex_xubut I also hope we can show json-schema in the doc, even with sdague's propose13:31
sdaguealex_xu: as a phase 2, probably13:32
gmann_ alex_xu yea that will be nice13:32
karenbsomehow it would be good to generate a schema to a specification whether swagger or something else13:32
annegentlealex_xu: yeah I don't sense we're cutting off innovations there13:32
karenbit makes your api interoperable13:32
annegentlekarenb: yeah, and interoperability is needed for OpenStack DefCore13:33
annegentlemeeting the tests.13:33
oomichi_but here are tempest-cores also, it is not so hard :)13:33
sdaguekarenb: I agree13:33
*** GB21 has joined #openstack-meeting-413:33
annegentleoomichi_: good :)13:33
sdaguehowever, I want to make sure we don't get caught up on the schema before the user docs13:33
alex_xucurrent odc didn't tell user what is request and response format13:33
*** seanmurphy has joined #openstack-meeting-413:34
alex_xusdague: yea, got it, step by step13:34
alex_xus/odc/doc/13:34
sdagueas a for instance, just telling people 3 of the server parameters are only available in later versions of nova13:34
gmann_sdague: but if we do schema thing later then would not it be duplicate effort to put all those param info in rst and yaml13:34
sdaguehttp://docs-draft.openstack.org/51/294151/4/check/gate-nova-docs/c2a264a//doc/build/html/rest_api/servers.html#id513:35
gmann_and then ref those to schema13:35
*** ninag has quit IRC13:35
sdaguegmann_: we can either optimize for getting working docs, or optimize for data formats13:35
annegentlemaintainable docs13:36
gmann_sdague: from schema ('required'), we can show the mandatory and optional param there13:36
sdagueand I believe that if we optimize for working docs, we'll open up the api docs to new contributors that can help13:36
annegentle(not arguing, heh)13:36
sdagueinstead of kicking them in the face with a pile of hard to understand sgml13:36
*** ninag has joined #openstack-meeting-413:36
gmann_humm13:36
*** ninag has quit IRC13:37
edleafeannegentle: if they aren't maintainable, they won't be working (for long)13:37
*** ninag has joined #openstack-meeting-413:37
annegentleaww sdague there are still over 100 contribs to the WADL each release, but yes we need to get off of it13:37
sdagueannegentle: they are, and I commend their hero level of dedication to get there13:37
annegentleone other Q I want to ask this group, is it easier in some ways to contribute to YAML and json schema files instead of RST due to English-as-a-second language?13:37
annegentleI want to consider that many many contributors to the API reference don't mind it because it's like filling in a form.13:38
annegentleswagger would have given us the "form"13:38
annegentlebut... the API doesn't quite fit.13:38
annegentledoes that make any sense or is it a needless worry?13:38
sdagueannegentle: possibly, but at the end of the day you still need to write english on descriptions13:39
alex_xuEnglish will always a problem, you need English explain the thing13:39
annegentlesdague: so, so true13:39
* alex_xu 's problem13:39
annegentlealex_xu: yeah... I don't want to be inconsiderate of a big group of contributors here just because I write a ton13:39
oomichi_annegentle: it is easy to understand the code (json-schema, also) than English for me always :)13:40
gmann_apart from english, i feel each developer like json nd yaml format(even with description  than witting all in rst :)13:40
annegentlegmann_: :)13:40
alex_xuoomichi_: me too :)13:40
edleafeoomichi_: me too, sometimes :)13:40
annegentleok yeah... to me, this does mean it's worthwhile to eventually enable something like Swagger.13:40
alex_xuedleafe: when you ready my commit message13:40
sdaguehowever, so far that has failed to make an API site that anyone would use13:40
annegentlebut! There's a ton of work on parameters.yaml to get those up to par13:41
annegentleyeah I think this is a decent compromise13:41
edleafealex_xu: :)13:41
oomichi_annegentle: yeah, it is easy to understand api design from sample files actually13:41
alex_xuparameters.yaml should convert from wadl?13:41
oomichi_the body structures can be understandable from sample files13:41
karenbgetting the content pieces right (req+response examples, params) is important13:41
annegentlealex_xu: well, I'd like to find someone who would investigate13:41
annegentlemaybe it's sdague?13:41
sdaguekarenb: yes, absolutely13:41
sdaguealex_xu: I would hope so13:42
oomichi_karenb: agree13:42
annegentlemaybe karenb can take a look?13:42
sdagueI believe the fairy-slipper wadl -> swagger built content almost exactly like it13:42
sdagueand we can tweak things to make that match13:42
karenbI need to look at parameters.yaml13:43
sdaguethis was an attempt to build a semi structured format that would be readonable to get over from our current bits13:43
annegentlesdague: for now, parameters.yaml was just one idea right?13:43
annegentlesdague: ok13:43
sdagueso that the conversion could be quick13:43
sdagueannegentle: yes, it's just the current thing I built that worked13:44
oomichi_sdague: yeah, I agree13:44
karenbwadl-> swagger has a model that is slightly different than swagger13:44
sdagueif we need field changes in it, that's all negotiable13:44
karenbyou could do anything with it13:44
annegentlemalleable!13:44
sdaguekarenb: yeh, annegentle showed me the json there and it looked really similar to https://github.com/openstack/nova/blob/e8afd02ca66a0801974ba2199c5323736c606257/doc/source/rest_api/parameters.yaml13:44
*** piet has quit IRC13:45
sdagueand the content / structure of that file is just inside the rest_parameters sphinx extension, we can make it whatever makes sense13:45
sdagueI also expect that the tools will get us about 90% of the way in a conversion, then we'll just have to clean up the final bits in a sprint13:46
annegentlethere will definitely be cleanup13:46
annegentlebut a sprint per project would get us there13:46
karenbsure.  swagger2rst from fairy-slipper also creates custom rst directives and13:47
karenbcollects the various rst pieces together13:47
karenbthe parsing is not complicated13:47
sdaguekarenb: cool13:47
annegentlekarenb: oh yeah13:47
annegentle(were there other agenda items?)13:48
alex_xuyes13:48
sdagueyeh, we kind of monopolized here :)13:49
annegentleok didn't want to take over :) sorry13:49
alex_xuif we are cool for the doc, then we jump to open13:49
sdaguesorry, but it was a big change in direction and wanted to get discussion going13:49
*** GB21 has quit IRC13:49
annegentleyeah appreciate it all13:49
alex_xusdague: yes, anyway we want to discuss newton work, the doc is part of that13:49
alex_xu#topic open13:50
*** openstack changes topic to "open (Meeting topic: nova api)"13:50
alex_xuI think we didn't have time discussion other newton item today. Let us go through those next week13:50
cdentafter discussion yesterday with sdague I've created this: https://github.com/cdent/microversion-parse13:50
cdentthat might be relevant to some folk13:50
sdaguecdent: thanks again for that13:51
sdaguealex_xu: do you have the etherpad linke for newton api items?13:51
cdentit's pending infra-ness at https://review.openstack.org/29604613:51
alex_xusdague: https://etherpad.openstack.org/p/newton-nova-api-ideas13:51
*** avarner_ has joined #openstack-meeting-413:51
alex_xujohnthetubaguy also put something in https://etherpad.openstack.org/p/newton-nova-summit-ideas13:51
sdaguewe should put the standard header parsing as an item13:51
alex_xusdague: microversion's header?13:52
*** oomichi_ has quit IRC13:52
sdaguethe new guideline on OpenStack-API-Version13:52
alex_xusdague: ah, yea13:53
alex_xusdague: it's in line 2313:53
sdaguethat's what cdent's library helps with13:53
alex_xucdent: cool13:53
gmann_cdent: looks interesting , will check in detail tomorrow.13:54
cdentthank alex_xu, gmann_13:54
cdentthanks :)13:54
gmann_so it will be candidate for all project's microversion header parsing right13:54
sdaguegmann_: yes13:55
gmann_i mean for api-wg13:55
*** bobh has joined #openstack-meeting-413:55
*** annegentle has quit IRC13:55
gmann_sdague: ok, will be good for tempest microversion testing too13:55
*** bobh has quit IRC13:55
*** bobh has joined #openstack-meeting-413:55
alex_xuif any people have real 'open' item, please bring up, otherwise you will lose the chance :(13:55
*** piet has joined #openstack-meeting-413:57
alex_xuok, I guess no...13:57
alex_xuKevin_Zheng: there is one https://review.openstack.org/#/c/293790/ I guess you put it here13:57
Kevin_Zhengyes13:57
Kevin_Zhengif there is still time13:57
alex_xuKevin_Zheng: anything we can help?13:57
alex_xuKevin_Zheng: sorry, 3 mins :(13:58
Kevin_Zhengyes last week I talk about your ideas about force stop instances13:58
Kevin_ZhengI put up a spec13:58
*** xarses has quit IRC13:58
*** neelashah1 has joined #openstack-meeting-413:59
alex_xuKevin_Zheng: ah, cool13:59
*** tojuvone has left #openstack-meeting-413:59
alex_xuI will try to reach that13:59
Kevin_ZhengThanks, looks like you guys have alot of things important than this13:59
Kevin_Zhengyes, its not in a hurry13:59
Kevin_ZhengThanks again14:00
*** vincentfrancoise has joined #openstack-meeting-414:00
alex_xuKevin_Zheng: no worries, free to bring question at here14:00
alex_xusorry, it's time to close the meeting14:00
Kevin_ZhengNP14:00
alex_xuthanks all!14:00
alex_xu#endmeeting14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Wed Mar 23 14:00:31 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-03-23-13.00.html14:00
gmann_Thanks all14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-03-23-13.00.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-03-23-13.00.log.html14:00
acabot#startmeeting watcher14:00
openstackMeeting started Wed Mar 23 14:00:40 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
acabothi everyone14:00
jinquanhi14:00
edleafeo/14:00
vincentfrancoiseo/14:00
tpeopleso/14:00
vtech_o/14:01
seanmurphyhi all14:01
*** neelashah has quit IRC14:01
sballe_o/14:01
acabotagenda for today #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#03.2F23.2F201614:01
tkaczynskihi14:01
*** sigmavirus24_awa is now known as sigmavirus2414:01
*** hvprash has joined #openstack-meeting-414:01
jed56hi14:01
acabot#topic Announcements14:02
*** openstack changes topic to "Announcements (Meeting topic: watcher)"14:02
*** gmann_ has quit IRC14:02
*** cdent has left #openstack-meeting-414:02
*** alexchadin has joined #openstack-meeting-414:02
acabot#info we released Watcher RC-1 yesterday (3 days later than the official schedule)14:02
acabotsorry for that14:02
acabotour next target is RC-final (April 1st)14:03
acabotand its not a joke ;-)14:03
sballe_:)14:03
seanmurphy;-)14:03
alexchadinhi14:03
*** vtech_ has quit IRC14:03
hvprashhi14:04
*** vtech has joined #openstack-meeting-414:04
acabot#info Slides for the Austin summit are available for reviews #link https://docs.google.com/presentation/d/1xzuIgmvRXiwTxv4R0al8DZoFd7u6OA6hx6aUrid7JPw/edit?usp=sharing14:04
*** dims has joined #openstack-meeting-414:04
*** dims_ has quit IRC14:04
acabotsballe_: do you want me to integrate Joe & Sean comments ?14:05
acabotxavier already did updates yesterday14:05
sballe_yes thta is my plans. I have been sick the last 3 days14:05
sballe_but feeling better today14:05
acabot#action sballe_ integrate comments in Austin slides14:06
*** spotz_zzz is now known as spotz14:06
*** neelashah has joined #openstack-meeting-414:06
acabot#info PTL election has ended and I'm the only candidate so if anyone is against nominating myself, please say something now ;-)14:07
tpeoples:D14:07
*** neelashah1 has quit IRC14:07
sballe_I would nominate you too14:07
*** salv-orl_ has quit IRC14:07
sballe_you have done a great job14:07
acabotthx14:07
acabot#info acabot will be Watcher PTL for Newton14:08
tkaczynski+1 for acabot :)14:08
vincentfrancoise+214:08
sballe_+114:08
jinquan+114:08
alexchadin+114:08
*** openstack has joined #openstack-meeting-414:23
*** ChanServ sets mode: +o openstack14:23
acabotok in this case just synchronise yourself to avoid rebasing14:24
*** evgenyf has quit IRC14:24
vincentfrancoisegzhai2: I can push a first version by EOD so you can compare14:24
gzhai2vincentfrancoise: merged?14:24
vincentfrancoisegzhai2: but it's not ideal14:24
vincentfrancoiseno just push for review14:24
gzhai2ok. I'll have a look. Other issues do you have?14:25
tkaczynskivincentfrancoise: if we are talking about few days to implement that, it will not affect me really. I should be able to use your changes easily14:25
*** ddieterly is now known as ddieterly[away]14:25
*** jed561 has quit IRC14:25
acabot#action vincent francoise push code for 'Achieved goal should be returned by each strategy' asap14:25
vincentfrancoisegzhai2: I don't have any strategy_para_info14:25
acabot#action vincentfrancoise push code for 'Achieved goal should be returned by each strategy' asap14:26
vincentfrancoisetkaczynski: you are much less affected by this than gzhai214:26
gzhai2vincentfrancoise: I'll add it:) If we just conflict with strategy, I think it's ok.14:26
tkaczynskivincentfrancoise: this is why I'm saying I'm good :)14:26
acabot#action sballe_ jwcroppe BIG PRIORITY review https://review.openstack.org/#/c/293862/14:26
*** annegentle has joined #openstack-meeting-414:27
sballe_ok14:27
*** sdake has joined #openstack-meeting-414:27
acabotalexstav: https://review.openstack.org/#/c/286153/ needs a new PS based on last reviews14:27
acabot#action alexstav add a new PS for https://review.openstack.org/#/c/286153/14:27
alexchadinalexchadin*14:28
acabotWIP: Cluster model objects wrapper needs reviews https://review.openstack.org/#/c/287019/14:28
acabot#action alexchadin add a new PS for https://review.openstack.org/#/c/286153/14:28
tpeoples#action tpeoples to submit non-WIP review for https://review.openstack.org/#/c/287019/14:29
acabottpeoples: I think you can start working on work items14:29
alexchadinI'll add it tomorrow or by friday14:29
tpeoplesi will start on implementation this week as well14:29
acabottpeoples: cool14:29
seanmurphyregarding https://review.openstack.org/#/c/287019/ - i had point abt integration with notification system14:29
acabotplease update the BP status on launchpad14:29
tpeopleswill do acabot14:29
seanmurphyis this an architectural change?14:29
tpeoplesno seanmurphy, it has been part of the architecture plans14:30
seanmurphyok - i did not realize this14:30
tpeoplesthere was always an intention to have watcher connected to the same message bus as all other services14:30
seanmurphyok - got it14:30
*** IlyaG has joined #openstack-meeting-414:30
acabotAdd specification for Watcher Scoring Module needs reviews https://review.openstack.org/#/c/289880/14:31
acabotthanks tkaczynski for your detailed answers14:31
*** piet has quit IRC14:31
acabotit would be great to have more reviewers on the scoring module14:31
dtardivelacabot: I will review it14:32
tkaczynskiacabot: sure, I'm trying to keep this up to date and improve the spec. thanks to jed56 for his comments!14:32
acabot#action dtardivel acabot review https://review.openstack.org/#/c/289880/14:32
hvprashi will review too14:33
acabotProvide efficacy indicators is locked on licences discussion https://review.openstack.org/#/c/283449/14:33
acabot#action hvprash review https://review.openstack.org/#/c/289880/14:33
acabottpeoples : there is a concern from IBM about licenses14:34
acabottpeoples : any update on this ?14:34
tpeoplesacabot: no, let me ask joe when i talk to him next14:34
tpeopleshe's traveling internationally14:34
acabot#action jwcroppe clarify the license problem on https://review.openstack.org/#/c/283449/14:34
acabotthats it for specs14:35
tpeoplesjust took a look, don't think it'll be an issue really14:35
tpeoplesaren't other projects starting to look into using voluptuous as well?14:35
acabot#info regarding watcher and python-watcherclient, a couple of bugs have been fixed14:36
jed56I think zull14:36
jed56is using voluptuous14:37
tpeoplesyeah, i don't think there's an issue. i'll ask him what was up there14:37
acabotok thx14:37
jed56https://github.com/openstack-infra/zuul/blob/master/requirements.txt#L1214:37
*** anilvenkata has joined #openstack-meeting-414:37
acabot#topic Blueprint/Bug Review and Discussion14:37
*** openstack changes topic to "Blueprint/Bug Review and Discussion (Meeting topic: watcher)"14:37
acabotthe RC-final details are available at #link https://launchpad.net/watcher/+milestone/mitaka-rc-final14:38
*** piet has joined #openstack-meeting-414:38
jed56monasca is using also voluptuoushttps://github.com/openstack/monasca-api/blob/master/requirements.txt#L1814:38
acabotas you can see, we wont be able to deliver everything by end of next week !14:38
dtardivelvoluptuous was part of global requirement, before we decided to use it. Is it not a sufficient guarantee ? what is the condition to introduce new lib into global requirements ?14:38
tpeoplesit should be sufficient dtardivel. i don't know what jwcroppe had an issue with really14:39
*** MarkAtwood has joined #openstack-meeting-414:39
acabotgzhai2: do you plan to implement "Allow specification of threshold defining when optimization is needed" for rc-final ?14:39
gzhai2yes14:40
*** IlyaG has quit IRC14:40
*** andymaier has joined #openstack-meeting-414:40
gzhai2The due date?14:40
acabotwe need to have the code avaiable for review by EOW14:40
acabotto have one full week to review and merge14:41
gzhai2No problem.14:41
acabotthanks14:41
acabottpeoples: I suppose I can postpone the object wrapper to Newton right ?14:42
*** dingboopt has quit IRC14:42
acabottkaczynski : same for scoring module14:42
tpeoplesyeah. i'll start working on it but getting that done *and* reviewed by april 1st is not going to happen14:42
*** zhurong has quit IRC14:42
*** iyamahat has joined #openstack-meeting-414:42
*** dingboopt has joined #openstack-meeting-414:42
acabotseanmurphy: your code has been reviewed but dtardivel is still working on it14:43
seanmurphyok - cool - thanks14:43
acabotso we were not able to merge it last week14:43
acabotbut it will be merged for mitaka14:43
*** Swami has joined #openstack-meeting-414:43
tkaczynskiacabot: yes, scoring module (implementation) has no way to happen before April 1st. the spec is still not approved14:44
*** MarkAtwood has quit IRC14:44
acabotvincentfrancoise can you assign yourself "The achieved goal should be returned by each strategy" .14:44
acabot?14:44
vincentfrancoiseacabot: ok will do it now14:44
acabotalexchadin: when do you plan to submit your code for review ?14:44
*** kebray has quit IRC14:45
alexchadinOnce my spec pass, no?14:45
alexchadinI already have a code and unit-tests14:45
acabotalexchadin: I know that your code is already on github ;-)14:45
alexchadinyeeees14:45
sballe_lol14:45
*** cemason has quit IRC14:45
alexchadinShould I publish it?14:45
alexchadinTo the gerrit14:45
acabotalexchadin: you can submit it as WIP14:46
acabotand I will move the BP to Newton14:46
acabotas the specs need more work14:46
acabotI suggest to move all low priority bugs to Newton cycle14:46
alexchadinWhere can i submit it as WIP? At launchpad?14:47
*** david-lyle_ is now known as david-lyle14:47
acabotjust add a "WIP" at the beginning of your commit message14:47
acabotand submit it to gerrit14:47
dtardiveland pass WORKFLOW indicator tp -114:48
*** sdake_ has joined #openstack-meeting-414:48
dtardivelto -114:48
alexchadinOh, okay, i'll do it tomorrow14:48
acabot#action alexchadin submit the code for Watcher Overload standard deviation algorithm as WIP14:48
*** ninag has quit IRC14:48
acabot#action acabot clear the rc-final BP and bugs priorities according to meeting logs14:48
*** sdake has quit IRC14:49
acabot#topic Open Discussion14:49
*** openstack changes topic to "Open Discussion (Meeting topic: watcher)"14:49
acabotWhat is the good practice to re-assign a bug to someone ?14:49
*** ddieterly[away] is now known as ddieterly14:49
tpeoplesleave a comment on launchpad asking the status. if you don't hear within a reasonable time (a day, two days?) then just move it to the other person14:49
tpeoplesimo14:49
dtardiveltpeoples: +114:50
sballe_+114:50
*** zeih has quit IRC14:50
gzhai2yes. ask current owner if want to reassign.14:50
tpeoplesdon't want to just move it since the person may have a changeset locally they haven't pushed up yet14:50
jinquan+114:50
vincentfrancoise+114:51
*** ninag has joined #openstack-meeting-414:51
jed56+214:51
*** ninag has quit IRC14:51
*** ninag has joined #openstack-meeting-414:51
*** janki91 has quit IRC14:51
acabot#info when a bug should be reassigned, leave a comment on launchpad asking the status. if you don't hear within 2 days then just move it to the other person14:51
dtardivelCan we just remove the assignee, and let someone else take the bug later ?14:51
*** janki91 has joined #openstack-meeting-414:51
acabotdtardivel: IMO, you can set it as unassigned14:52
gzhai2 assigne to nobody should be ok.14:52
dtardivelperfect14:52
jinquanIt should also be acceptable14:52
tpeoplesi think that might make sense. i know looking at other projects i initially skip over looking to work on bugs that have owners14:52
tpeoplesso yeah14:52
*** Jeffrey4l has joined #openstack-meeting-414:52
*** sdake has joined #openstack-meeting-414:52
*** sdake_ has quit IRC14:53
acabotedleafe: I saw you got a -1 on https://review.openstack.org/#/c/276840/14:53
acabotdo you plan to get more reviewers on this ?14:54
dtardivelacabot: I will have a look on bugs and add re-assign comment if necessary14:54
edleafeacabot: yeah, now that Newton is open, I'll push more for it14:54
sballe_edleafe: thx +114:54
jinquanacabot:  Is appropriate to start coding now ? because https://review.openstack.org/#/c/283449/ has something need discuss14:55
acabot#action dtardivel reassign bugs after acabot priority check14:55
acabotedleafe : thx14:55
*** ninag has quit IRC14:55
vincentfrancoiseacabot: shouldn't we re-open undone Mitaka BPs to now target Newton in watcher-specs?14:55
acabotjinquan: I think you can start coding14:55
jinquanok14:56
acabotjinquan: there is a dependency on vincentfrancoise work14:56
jed56jinquan: IMHO, you need to discuss with vincentcrnoise14:56
acabotjinquan: I will add it in launchpad14:56
jinquanget it14:57
acabotjinquan: so please review vincentfrancoise code before starting implementing this14:57
vincentfrancoiseacabot: just added the dependency on launchpad14:57
jed56beacause there is dependency for getting the indicators from pythonwatcherclient14:57
jed56acabot :thansk14:57
acabotjinquan : there is an open BP with specs merged here https://blueprints.launchpad.net/watcher/+spec/select-destinations-filter14:57
acabotjinquan: it could be a good way to enter Watcher code14:58
acabotwith a bit of stevedore to deal with14:58
jinquanok  i will read it thank you14:58
*** yamahata has joined #openstack-meeting-414:59
acabotthank you14:59
acabottime to close the meeting14:59
jed56bye14:59
acabotbye14:59
vincentfrancoisebye everyone14:59
tkaczynskibye14:59
alexchadinину14:59
sballe_bye14:59
alexchadinbye14:59
*** annegentle has quit IRC14:59
hvprashbye14:59
gzhai2      bye14:59
seanmurphybye!14:59
acabot#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Wed Mar 23 14:59:46 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-03-23-14.00.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-03-23-14.00.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-03-23-14.00.log.html14:59
vtechbye14:59
*** vincentfrancoise has left #openstack-meeting-414:59
*** ninag has joined #openstack-meeting-415:00
*** bryan_att has joined #openstack-meeting-415:01
*** gzhai2 has left #openstack-meeting-415:02
*** banix has quit IRC15:02
*** baohua has quit IRC15:04
*** alexchadin has quit IRC15:04
*** chigang has quit IRC15:06
*** karenb has quit IRC15:07
*** jinquan has left #openstack-meeting-415:08
*** openstackstatus has joined #openstack-meeting-415:12
*** ChanServ sets mode: +v openstackstatus15:12
*** seanmurphy has quit IRC15:12
*** askb has quit IRC15:22
*** askb has joined #openstack-meeting-415:23
*** kebray has joined #openstack-meeting-415:25
*** vishwanathj_ has joined #openstack-meeting-415:26
*** haleyb_ has joined #openstack-meeting-415:30
*** iyamahat has quit IRC15:35
*** haleyb_ has quit IRC15:36
*** yamahata has quit IRC15:38
*** bpokorny has joined #openstack-meeting-415:38
*** akwasnie1 has joined #openstack-meeting-415:42
*** tpeoples_ has quit IRC15:42
*** Sukhdev has joined #openstack-meeting-415:44
*** cbouch has joined #openstack-meeting-415:45
*** zeih has joined #openstack-meeting-415:47
*** anilvenkata has quit IRC15:51
*** lakshmiS has joined #openstack-meeting-415:53
*** fawadkhaliq has quit IRC15:54
*** rbak has quit IRC15:56
*** rbak_ has joined #openstack-meeting-415:56
*** hdaniel has quit IRC15:57
*** sridhar_ram1 has joined #openstack-meeting-415:57
*** IlyaG has joined #openstack-meeting-415:59
*** iyamahat has joined #openstack-meeting-416:00
*** yamahata has joined #openstack-meeting-416:00
*** daneyon has quit IRC16:00
*** ALUVial has joined #openstack-meeting-416:03
*** anilvenkata has joined #openstack-meeting-416:04
*** ALUVial has quit IRC16:05
*** hvprash_ has joined #openstack-meeting-416:06
*** hvprash has quit IRC16:06
*** hvprash has joined #openstack-meeting-416:08
*** matrohon has quit IRC16:09
*** sshnaidm has quit IRC16:10
*** SimonChung2 has quit IRC16:10
*** zeih has quit IRC16:10
*** hvprash_ has quit IRC16:11
*** zeih has joined #openstack-meeting-416:13
*** kebray has quit IRC16:15
*** cemason has joined #openstack-meeting-416:18
*** kebray has joined #openstack-meeting-416:18
*** bobh has quit IRC16:20
*** andymaier has quit IRC16:22
*** MarkAtwood has joined #openstack-meeting-416:27
*** rhallisey has joined #openstack-meeting-416:28
*** sigmavirus24 is now known as sigmavirus24_awa16:29
*** vhosakot has joined #openstack-meeting-416:30
sdake#startmeeting kolla16:30
openstackMeeting started Wed Mar 23 16:30:28 2016 UTC and is due to finish in 60 minutes.  The chair is sdake. Information about MeetBot at http://wiki.debian.org/MeetBot.16:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:30
*** harshs has joined #openstack-meeting-416:30
*** openstack changes topic to " (Meeting topic: kolla)"16:30
openstackThe meeting name has been set to 'kolla'16:30
sdake#topic rollcall16:30
*** openstack changes topic to "rollcall (Meeting topic: kolla)"16:30
vhosakoto/16:30
SamYapleo/16:30
sdake\o/16:30
rhalliseyhi16:30
SamYaplepbourke: ping16:31
pbourkeo/16:31
*** fawadkhaliq has joined #openstack-meeting-416:31
*** inc0 has joined #openstack-meeting-416:31
inc0o/16:31
akwasnie1hi16:31
jpeelerhey16:31
nihiliferhi16:31
*** salv-orlando has joined #openstack-meeting-416:31
sdake#topic announcements16:32
*** openstack changes topic to "announcements (Meeting topic: kolla)"16:32
*** MarkAtwood has quit IRC16:32
sdakemitaka branch was created16:32
*** haleyb_ has joined #openstack-meeting-416:32
sdakei proposed onthe mailing list creating an rc2 this friday16:32
sdakeand heard no complaints16:33
sdakeso thats happening ;)16:33
sdakerc3 will still be end of march-april2ndish16:33
*** david-lyle has quit IRC16:33
sdakeany other announcements folks have?16:33
*** david-lyle has joined #openstack-meeting-416:33
*** spzala has quit IRC16:33
inc0how do we look like on 1.1.0 front?16:34
sdakethat is in the agenda inc016:34
sdake#topic  Liberty backport status16:34
*** openstack changes topic to "Liberty backport status (Meeting topic: kolla)"16:35
sdakeSamYaple any progress?16:35
sdakei think this work is sort of blocked on teh fact that percona broke our gating16:35
SamYaplesince the last meeting i have not touched liberty due to mitaka needing love16:35
*** fawadkhaliq has quit IRC16:35
*** carolbarrett has joined #openstack-meeting-416:36
SamYaplei havent tested centos, but the ubuntu stuff should be done by end of week assuming mitaka needs no more love16:36
*** izaakk has joined #openstack-meeting-416:36
SamYaplemy proirity is mitaka atm though16:36
*** pmesserli has quit IRC16:36
*** kebray has quit IRC16:36
*** fawadkhaliq has joined #openstack-meeting-416:36
sdakeagree mitaka is the priority16:36
dave-mccowano/16:36
sdakewe have `50 bugs in various states of being worked on16:36
*** pmesserli has joined #openstack-meeting-416:36
sdake#topic Bug tracking process [timebox 20 minutes]16:37
*** openstack changes topic to "Bug tracking process [timebox 20 minutes] (Meeting topic: kolla)"16:37
*** haleyb_ has quit IRC16:37
sdakeI'm not sure if evyerone reads the mailing list16:37
sdakeso I will just cut and paste my email here16:37
sdakejust  a moment16:37
SamYapleplease paste link :)16:37
*** zeih has quit IRC16:37
sdakeThierry (ttx in the irc log at [1]) proposed the standard way projects typically handle backports of newton fixes that should be fixed in an rc, while also maintaining the information in our rc2/rc3 trackers.16:38
sdakeHere is an example bug with the process applied:16:38
sdakehttps://bugs.launchpad.net/kolla/+bug/154023416:38
openstackLaunchpad bug 1540234 in kolla mitaka "rabbitmq cluster does not work with dashes in the hostname" [Critical,Confirmed] - Assigned to weiyu (weiyu)16:38
sdakeTo apply this process, the following happens:16:38
sdakeAny individual may propose a newton bug for backport potential by specifying the tag 'rc-backport-potential" in the Newton 1 milestone.16:38
sdakeCore reviewers review the rc-backport-potential bugs.16:38
sdakeCR's review [3] on a daily basis for new rc backport candidates.16:38
sdakeIf the core reviewer thinks the bug should be backported to stable/mitaka, (or belongs in the rc), they use the Target to series button, select mitaka, save.16:38
sdake copy the state of the bug, but set thte Mitaka milestone target to "mitaka-rc2".16:38
sdakeFinally they remove the rc-backport-potential tag from the bug, so it isn't re-reviwed.16:38
sdakeThe purpose of this proposal is to do the following:16:38
sdakeAllow the core reviewer team to keep track of bugs needing attention for the release candidates in [2] by looking at [3].16:38
sdakeAllow master development to proceed un-impeded.16:38
sdakeNot single thread on any individual for backporting.16:38
*** ddieterly is now known as ddieterly[away]16:38
sdakeI'd like further discussion on this proposal at our Wednesday meeting, so I've blocked off a 20 minute timebox for this topic.  I'd like wide agreement from the core reviewers to follow this best practice, or alternately lets come up with a plan b :)16:38
sdakeIf your a core reviewer and won't be able to make our next meeting, please respond on this thread with your  thoughts.  Lets also not apply the process until the conclusion of the discussion at Wednesday's meeting.16:38
sdakewoops too late ;)16:38
sdakeso lets talk about this in mor edetail16:38
sdakeafter irc catches up16:38
inc0really sdake...? not even paste.openstack.orh?16:38
SamYapleugh16:38
*** salv-orlando has quit IRC16:38
sdakeinc0 sorry - failure on my part ;(16:38
SamYapleyou didnt paste link16:38
*** akwasnie1 has quit IRC16:39
sdakeok, so everyone read throug hthat please16:39
*** vishwanathj_away is now known as vishwanathj16:39
*** spzala has joined #openstack-meeting-416:39
sdakethe basic idea is we are going to use bug tracking as defined by best practices of the general openstack community16:39
sdakethat email lcontains the details of what those best practices are16:40
*** akwasnie1 has joined #openstack-meeting-416:40
sdakethis is a proposal not a mandate16:40
sdakeso I'd like discussion around the idea16:40
sdakeand wide agreement that thee core reiviewers are on board16:40
sdakei've been using the process for 1-2 days, and it works very well for my needs16:41
jpeelerperhaps a bit clearer: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090146.html16:41
sdakeone of the nice htings is it gets rid of single threading16:41
sdakethanks jpeeler16:41
sdakeapologies for not linking that16:41
sdakecafeeine free diet ftl16:41
*** ddieterly[away] is now known as ddieterly16:41
*** banix has joined #openstack-meeting-416:42
*** salv-orlando has joined #openstack-meeting-416:42
sdakeare there any questions on the process?16:42
*** sbezverk has joined #openstack-meeting-416:43
sdakehey sbezverk welcome to our meeting :)16:43
sdakenobody has a single question?16:43
sbezverkHi sorry keep loosing channel name16:43
vhosakotsbezverk: https://wiki.openstack.org/wiki/Meetings/Kolla16:44
jpeelerisn't there some magic that happens if the commit message containers the backport potential tag? perhaps having to skip setting it in launchpad?16:44
jpeelercontainers lol, contains16:44
*** spzala has quit IRC16:44
sdakejpeeler no not at this time16:44
vhosakotsdake: so, "rc-backport-potential" is needed to backport changes to Mitaka or to Liberty ?16:44
sdakethe commit message doens't contain a backport potnetial flag16:44
*** Swami has quit IRC16:44
sdakethe bug tracker is set with that16:44
inc0we could perhaps write some magical filter to gerrit that will work16:45
sdakevhosakot only for people in the core review team16:45
sdakenot in the drivers team i mean16:45
vhosakotsdake: ah ok16:45
vhosakotcool16:45
sdakethe drivers team goes straight past that step vhosakot16:45
vhosakotsdake: ah ok16:45
sdakerc-backport-potential is meant for people outside the drivers team16:45
vhosakotsdake: didn't know there are two teams :)16:45
*** spzala has joined #openstack-meeting-416:45
sdakeya drivers team is responosible for launchpad16:46
vhosakotah ok16:46
sdakecore review team is responsible for reviews and policy setting16:46
vhosakotcool16:46
sdakedrivers team contains all core reviewers16:46
sdakeor it should :)16:46
sdakeas well as anyone else who shows an interest in the project16:46
sdakeay more questions?16:47
sdakeI'd like a rollcall vote of the core reviewers present here16:47
SamYaple==16:47
inc0<<16:47
sdakei am +1 for the proposal as worded in the email16:48
*** spzala_ has joined #openstack-meeting-416:48
pbourkesdake any chance you could do it on the ML?16:48
sdakepbourke i can but i want to ge tthe ball rolling16:48
pbourkenp16:48
sdakewe need this right now not in a week16:48
sdakei will follow up with a formal vote16:49
sdakeon the mailing list with a  1 week expiration16:49
sdakeif you want16:49
sdakebut id' like a vote on irc now16:49
rhalliseyhi16:49
sdakesounds like we have 3 in favor sdake, SamYaple inc016:49
*** SimonChung has joined #openstack-meeting-416:49
sdakeany others?16:49
nihilifer+1 fro me16:49
jpeeler+116:49
rhalliseyyes16:49
sdakeneed 1 more16:50
*** spzala has quit IRC16:50
pbourkecan people not just submit a review targeted at the branch16:50
pbourkeand core +/- 1 the usual way16:50
inc0+1 from me16:50
akwasnie1+116:50
SamYaplepbourke: this is about bugs specifically16:50
sdakepbourke the problem is around tracking16:50
elemoine_+116:50
inc0I was part of initial discussion16:50
sdakeok we have 7 votes os thats a majority16:51
sdakebut i wan tto make sure pbourke 's concerns are discussed16:51
SamYaplefor those wondering why this sounds, this was also discussed back in Dec, without the rc-backport tag16:51
*** gmmaha has joined #openstack-meeting-416:51
SamYapleso this just formalizes it all16:51
sdakepbourke this process results in a way to track a patch for master, as well as mitaka as well as liberty16:51
sdakepbourke if devs use cherry-pick only for backports there is no priortiization no tracking, no definition of done16:52
sdakewhich means backports get lost16:52
sdakewhich is precisely what happened in liberty16:52
pbourkeim sure its fine16:53
sdakethis process should fix that16:53
*** spzala_ has quit IRC16:53
sdakeand its relaly only onerou on the ptl16:53
*** cdelatte has joined #openstack-meeting-416:53
sdakeeveyrone else has minimal extra buttons to click during bug triage16:53
sdakeone thing id' ask16:53
sdakewhen doing reviews, click through the link kto the bug16:53
sdakeand decide if it should be backported16:53
*** spzala has joined #openstack-meeting-416:54
*** ntpttr has joined #openstack-meeting-416:54
sdakeif it should, mark it for mitaka16:54
sdakelets try notot bakcport the universe16:54
sdakebut any bug is fair game16:54
*** salv-orlando has quit IRC16:54
sdakeok any last thoguhts from anyone?16:54
*** Swami has joined #openstack-meeting-416:55
sdake#topic Brainstorming problems people have seen in etherpad [timebox 15 minutes]16:55
*** openstack changes topic to "Brainstorming problems people have seen in etherpad [timebox 15 minutes] (Meeting topic: kolla)"16:55
sdakethis is going to be a little bit of  a wierd session16:55
sdakei've never done anything ike this in the past16:55
SamYaplewe should all vote on the issues!16:55
sdakebut I keep hearingabout all sorts of random faiure scenarios that people know about16:55
sdakeno voting :)16:55
SamYaple:{16:56
*** anilvenkata has quit IRC16:56
sdakeso what I'd like is for people to write down in a lightweight  fashion any kind of oddness they find16:56
*** spzala_ has joined #openstack-meeting-416:56
rhalliseySamYaple, new voting?16:56
sdakeusing a etherpad16:56
SamYaplerhallisey: i think you mean "voting"16:56
sdakehttps://etherpad.openstack.org/p/kolla-mitaka-oddities16:56
inc0you want us to use etherpad to write down why etherpad isn't working?16:57
vhosakotsdake: is this etherpad for cores ?16:57
sdakeno anyone can participate16:57
vhosakotcool16:57
sdakevhosakot nothing is excluded from participation by others in our meetings except policy votess16:58
vhosakotah cool!16:58
*** spzala has quit IRC16:58
sdakeif you wnt to vote on the midcycle sessions as well, feel free ;)16:58
vhosakotah ok16:58
sdakeok we have until 15 after to finish this session16:59
sdakenothing may come of it16:59
sdakebut please try to think back to any of those one off fialure casess you hae had16:59
*** cbouch has quit IRC17:00
*** spzala_ has quit IRC17:00
*** krtaylor has quit IRC17:01
*** annegentle has joined #openstack-meeting-417:01
*** spzala has joined #openstack-meeting-417:02
*** vtech has quit IRC17:03
*** carolbarrett has quit IRC17:03
*** spzala_ has joined #openstack-meeting-417:04
*** MarkAtwood has joined #openstack-meeting-417:04
*** pmesserli has quit IRC17:04
sdakeok 10 minutes left17:05
*** dims_ has quit IRC17:05
sdakei'mg oing to gie it another 5 for foks to put in ideas17:06
sdakeif we have run out of iideas by then, we ca nmove on17:06
sdakeso please keep going ;)17:06
*** zeih has joined #openstack-meeting-417:06
*** spzala has quit IRC17:06
vhosakotshould the multinode issue where nuetron hosts must be present in a specific order due to Ansible bug be mentioned as an oddity ?17:06
sdakevhosakot yes17:06
*** dims has joined #openstack-meeting-417:06
sdakefolks this is brainstomring17:07
sdakeeven if your not sure, write it down :)17:07
*** Rockyg has joined #openstack-meeting-417:07
*** ajmiller has quit IRC17:07
*** vishnoianil has quit IRC17:08
*** spzala_ has quit IRC17:08
*** ajmiller has joined #openstack-meeting-417:08
*** spzala_ has joined #openstack-meeting-417:09
*** zeih has quit IRC17:10
*** zeih has joined #openstack-meeting-417:10
*** Rocky_g has joined #openstack-meeting-417:10
*** pmesserli has joined #openstack-meeting-417:10
*** Rockyg has quit IRC17:10
*** Rocky_g has quit IRC17:10
sdakeok i'm going t o file bugs on these issues17:10
sdakeand bring them into mitaka rc series17:10
sdakewe can kick them out later if we want17:10
*** pmesserli has joined #openstack-meeting-417:10
*** Rockyg has joined #openstack-meeting-417:11
sdakethey will start out in triaged state17:11
vhosakotare we moving to Ansible 2.0 in Newton ?17:11
SamYaplevhosakot: yes17:11
sdakevhosakot thats been discussed17:11
vhosakotcool17:11
inc0that is the plan17:11
vhosakotcool, just checking17:11
sdake#topic format of globals.yml17:12
*** openstack changes topic to "format of globals.yml (Meeting topic: kolla)"17:12
sdakethere have been lots of reviews about globals.yml17:12
sdakechanging things back and forth17:12
sdakei'd like to settle on a standard and get it in mitaka17:12
sdakesince its a critical piece of documentation17:13
*** krtaylor has joined #openstack-meeting-417:13
*** spzala_ has quit IRC17:13
sdakethe debate that came up in the review was whether the defaults should be listed17:13
SamYapleuseful defaults*17:13
sdakeand if the default commented value should be the same as the default or opposoite17:13
sdakeopposiet allows for easy config by remvoing a comment and space17:14
sdakeSamYaple agree, we dont want to expose everything17:14
sdakei am thinnking things like 'enable_heat"17:14
sdakewhich is in globals.yml17:14
sdakebut enable_swift is not17:14
SamYaplecomments in config files across all stable software show the default17:14
sdakeor maybe it was added17:14
sdakebut you get the idea17:14
*** spzala has joined #openstack-meeting-417:14
sdakeok that is a good attern to follow then17:14
sdakei'd ike to be consistent with other openstack projects17:15
sdakebut do we want the commented item to be the default or the opposite?17:15
sdakefor example we could do something like17:15
sdake# Descritpion17:15
sdake#  The default is XYZ17:15
sdake# enable_heat: yes17:15
sdakerather the default is no17:15
*** sshnaidm has joined #openstack-meeting-417:16
vhosakotshould a single variable be in all three files ? in globals.yml, all.yml and <service name>/defaults/main.yml ?17:16
sdakeatm we have comletely incosnsitency in thsi file17:16
sdakeand its 1 of 2 of our go to documents17:16
*** ihrachys has quit IRC17:16
sdakevhosakot yest hat is normal, globals.yml is for an ovveride17:16
*** jschwarz has quit IRC17:16
inc0I think way everyone do this is to comment on default17:17
inc0# enable_heat: no17:17
SamYapleinc0: correct17:17
SamYaplethough the eefault for heat is yes i believe17:17
vhosakotinc0: yes, that is good... and make globals.yml dictate the final values17:17
SamYaplebut yes, everyone comments out values that are defaults17:17
sdakei think we took heat out of yes default17:17
sdakeso maybe heat is a bad example17:17
sdakelets use manila instead  :)17:17
*** krtaylor has quit IRC17:17
SamYaplethere ya o17:17
SamYaplego*17:18
vhosakotyes, manila has good variables separation..17:18
sdakeok folks17:18
sdakewe are discussing multipe lthings17:18
sdakelets focus on one thing now17:18
sdakeenable_service17:18
sdakeshould the # enable_service be the default or opposite17:19
sbezverkwould it not be more straight forward not to rely on defaults but on explicitely enabled service?17:19
*** spzala has quit IRC17:19
inc0we can also point in docs that defaults are here: https://github.com/openstack/kolla/blob/master/ansible/group_vars/all.yml17:19
inc0so we won't do commented all.yml in globals.yml17:20
vhosakotsdake: I like all commented out variables _not_ default so that way an operator sees a different behavior when the comments var in uncommented17:20
inc0it will also be good documentation for what people can change17:20
sdakevhosakot i agree with that line of thinking17:20
*** spzala has joined #openstack-meeting-417:20
sdakeinc0 ddocumenting defaults as a link wfm17:20
SamYaplevhosakot: sdake then the operator has no idea what the default it17:21
SamYaplewhat if there are three options?17:21
vhosakotsdake: otherwise, the opearator not only has to uncomment, but also find out what non-deafalt value must be used after uncommenting to see new behavior17:21
inc0I'm -2 for commenting oposites17:21
SamYapleinc0: agreed -217:21
inc0this is now how ini configs works usually17:21
SamYaplewe have 2 places where we do it, and that should be fixed17:21
sdakeSamYaple please expand17:21
inc0if operator wants to see a change, it should be because he explicitly changed it17:21
SamYaplesdake: we have two places in globals.yml where we comment opposite, we should correct that17:22
sdakeSamYaple i agree its inconsistent17:22
inc0SamYaple, which ones? I think that was the question;)17:22
vhosakotah ok17:22
sdakethe purpose of this discussion is to come up with the definition of what consistent is17:22
SamYapleas stated several times, the _normal_ way to do this is to have a comment with teh default values17:23
sdakei like the commenting opposite personally17:23
inc0I think we should have commented defaults of most commonly changed options in globals.yml17:23
sdakebut understand inc0's pov17:23
inc0and point to all.yml17:23
pbourkecan we autogen gloabls in the same way as the build conf?17:23
vhosakotlet us follow what neutron. nova. glance, etc do for their *.ini files...17:23
SamYaplepbourke: not really. because its not jsut from all.yml17:23
SamYaplepbourke: its _all_ of ansible and that includes some vars set by tasks17:23
sdakevhosakot which is what?17:23
pbourkei see17:23
inc0vhosakot, and that is commented defaults17:24
pbourkethat said it should follow the same convention default wise17:24
*** krtaylor has joined #openstack-meeting-417:24
sdakeheres the deal, i am super keen to be consistent with other openstack projects17:24
SamYaplethen defaults it is17:24
vhosakotsdake: don't know.. need to check... inc0 confirmed that they comment out defaults17:24
sdakeok, then decision made17:24
inc0when I said everyone else does that, I meant it;)17:24
SamYaplehttps://review.openstack.org/#/c/294392/17:24
SamYaplethat review solves all of this conversation17:24
sdakethanks for that - now we all are on same page re how globals.yml should work :)17:25
sdakeI hope folks enforce that17:25
*** spzala has quit IRC17:25
sdake#topic open discussion17:25
*** openstack changes topic to "open discussion (Meeting topic: kolla)"17:25
sdakei am working on getting us to be able to apply for the assert upgrade tags in the governance repo17:26
inc0duh...17:26
inc0so this is tricky17:26
sdakeit requires alot of change to the governance repo and voting by the tc ;)17:26
sdakebut its in progress17:26
inc0because afaik it's based whether or not we upgrade using grenade17:26
sdakeinc0 the governance repo has not seen the end of my change reviews17:27
sdakethose documents are not final, they can be modified by anyone in the community17:27
inc0and well, we do not and never be, nor we should17:27
sdakeatm we are stuck on requriement 1: must be a type:service project17:27
inc0that being said17:27
inc0we don't really ugrade ourselves per se17:27
inc0nor support upgrade of kolla17:28
inc0we just...git reset --hard17:28
sdakeinc0 perhaps a new assertion tag is needed17:28
inc0yeah17:28
sdakeinc0 i'll sort it out17:28
inc0let me know if you need any help17:28
sdakealso going on, the vmt requires architecture diagrams17:28
*** spzala has joined #openstack-meeting-417:28
sdakei do need help wit hthe architecture diagrams17:28
sdakeI am using a web service called gliffy for shared document creation17:29
sdakethe downside of gliffy is you hae ot pay for it17:29
sdakethe upside is documents can be share-edited17:29
*** SimonChung has quit IRC17:29
*** SimonChung1 has joined #openstack-meeting-417:29
sdakethese arch diagrams are needed for the VMT tagging17:29
sdakei create some rough ones and send links out17:29
sdakeif people want to help and dont mind paying for gliffy, you can contribute17:30
sdakei know the pay bar sucks17:30
sdakeits not meant to exclude people17:30
inc0google docs are free..17:30
*** pc_m has joined #openstack-meeting-417:30
sdakeI just dont have a bettter way17:30
sdakegoogle docs doesn't diagram17:30
pbourkegoogle slides17:30
sdakeanyway meeting time is up17:30
sdakegoogle slides diagramming tools are bad pbourke compared to gliffy17:30
sdakeits nto super expensive17:30
pbourkefair enough17:31
sdake10 bucks a month or something17:31
sdakeanyway our time is up17:31
sdakelets overflow into #kolla17:31
sdake#endmeeting17:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:31
openstackMeeting ended Wed Mar 23 17:31:14 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-03-23-16.30.html17:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-03-23-16.30.txt17:31
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-03-23-16.30.log.html17:31
*** vhosakot has left #openstack-meeting-417:31
*** vtech has joined #openstack-meeting-417:31
dougwigo/ anyone around for networking_lib, or are ya'll sucked into mitaka rc land?17:31
*** akwasnie1 has quit IRC17:31
*** Kevin_Zheng has quit IRC17:32
HenryGI am here17:32
HenryGBut I don't have much to talk about17:33
*** spzala has quit IRC17:33
*** rhallisey has left #openstack-meeting-417:33
*** gmmaha has left #openstack-meeting-417:33
dougwigok, then we can punt the formal meeting  i'll ping kevin about your pagination review.  any eta on a respin of your other patch?17:33
HenryGI can get it up today I think17:34
dougwigok, i'll be looking forward to that.17:34
kevinbentonoy17:34
HenryGAny plans to switch neutron constants to lib?17:34
*** spzala has joined #openstack-meeting-417:34
dougwigi'm trying to get the abstracted models up first, then i script that if no one else has.17:35
dougwig /i/i'll/17:35
dougwigi noted some issues with folks thinking they had to land and release items in lib in order to make progress in neutron, which is not a scenario we want to let people fall into.17:35
HenryGright17:36
*** mbound has quit IRC17:36
*** fawadkhaliq has quit IRC17:36
dougwigyou did too, but i know you know the issues around that, so i didn't care.  :)17:36
*** fawadkhaliq has joined #openstack-meeting-417:37
*** unicell has joined #openstack-meeting-417:38
HenryGBut it means we will need to have most neutron core code import both neutron constants and neutron_lib constants17:38
*** mbound has joined #openstack-meeting-417:38
*** spzala has quit IRC17:39
*** fawadkhaliq has quit IRC17:39
*** akwasnie1 has joined #openstack-meeting-417:39
*** jmckind has quit IRC17:39
HenryGWe should start by getting the usage of lib constants to a point where we can re-enable the deprecation warnings17:39
*** fawadkhaliq has joined #openstack-meeting-417:39
*** vishnoianil has joined #openstack-meeting-417:40
dougwigagreed. and i don't have a problem with common.constants staying around for staging, though i know you wanted it gone.17:41
*** fawadkhaliq has quit IRC17:41
*** fawadkhaliq has joined #openstack-meeting-417:41
HenryGThat was before your devious python magic17:41
dougwiglol17:42
*** ddieterly is now known as ddieterly[away]17:42
*** bpokorny has quit IRC17:43
dougwigok, let's switch back to the neutron channel17:44
*** s3wong has joined #openstack-meeting-417:45
*** mdorman has joined #openstack-meeting-417:45
*** fawadkhaliq has quit IRC17:47
*** yamamoto_ has quit IRC17:47
*** fawadkhaliq has joined #openstack-meeting-417:47
*** salv-orlando has joined #openstack-meeting-417:48
*** spzala_ has joined #openstack-meeting-417:48
*** piet has quit IRC17:49
*** ntpttr has left #openstack-meeting-417:50
*** mbound has quit IRC17:51
*** bpokorny has joined #openstack-meeting-417:51
*** piet has joined #openstack-meeting-417:52
*** spzala_ has quit IRC17:52
*** yamamoto has joined #openstack-meeting-417:52
*** ninag has quit IRC17:54
*** angdraug has joined #openstack-meeting-417:54
*** spzala has joined #openstack-meeting-417:54
*** avarner_ has quit IRC17:54
*** daneyon has joined #openstack-meeting-417:54
*** vishwanathj_ has quit IRC17:54
*** askb has quit IRC17:55
*** spzala has quit IRC17:58
*** zeih has quit IRC18:00
*** zeih has joined #openstack-meeting-418:01
*** salv-orl_ has joined #openstack-meeting-418:01
*** salv-orlando has quit IRC18:04
*** avarner_ has joined #openstack-meeting-418:05
*** Sukhdev has quit IRC18:06
*** sigmavirus24_awa is now known as sigmavirus2418:06
*** spzala has joined #openstack-meeting-418:06
*** MarkAtwood has quit IRC18:08
*** piet has quit IRC18:10
*** janki91 has quit IRC18:12
*** pc_m has left #openstack-meeting-418:14
*** annegentle has quit IRC18:14
*** krotscheck has quit IRC18:14
*** krotscheck has joined #openstack-meeting-418:15
*** iurygregory has quit IRC18:15
*** cemason has quit IRC18:17
*** cemason has joined #openstack-meeting-418:17
*** klindgren has joined #openstack-meeting-418:18
*** MarkAtwood has joined #openstack-meeting-418:19
*** annegentle has joined #openstack-meeting-418:19
*** yamamoto has quit IRC18:19
*** yamamoto has joined #openstack-meeting-418:24
*** zeih has quit IRC18:24
*** ihrachys has joined #openstack-meeting-418:26
*** krotscheck has quit IRC18:26
*** krotscheck has joined #openstack-meeting-418:26
*** iurygregory has joined #openstack-meeting-418:27
*** piet has joined #openstack-meeting-418:28
*** mestery_ has joined #openstack-meeting-418:28
*** sambetts is now known as sambetts|afk18:31
*** yamamoto has quit IRC18:33
*** mestery has quit IRC18:33
*** mestery_ is now known as mestery18:33
*** angdraug has quit IRC18:33
*** yamamoto has joined #openstack-meeting-418:33
*** yamamoto has quit IRC18:33
*** yamamoto has joined #openstack-meeting-418:34
*** mestery_ has joined #openstack-meeting-418:34
*** unicell has quit IRC18:34
*** unicell has joined #openstack-meeting-418:34
*** haleyb_ has joined #openstack-meeting-418:34
*** sridhar_ram1 is now known as sridhar_ram18:37
*** yamamoto has quit IRC18:37
*** krotscheck has quit IRC18:38
*** krotscheck has joined #openstack-meeting-418:39
*** annegentle has quit IRC18:39
*** haleyb_ has quit IRC18:40
*** sdake_ has joined #openstack-meeting-418:41
*** ddieterly[away] has quit IRC18:43
*** akwasnie1 has quit IRC18:43
*** yamamoto has joined #openstack-meeting-418:44
*** yamamoto has quit IRC18:44
*** sdake has quit IRC18:44
*** yamamoto has joined #openstack-meeting-418:44
*** yamamoto has quit IRC18:45
*** mestery_ has quit IRC18:46
*** sdake has joined #openstack-meeting-418:47
*** angdraug has joined #openstack-meeting-418:49
*** sdake_ has quit IRC18:49
*** angdraug has quit IRC18:50
*** openstack has joined #openstack-meeting-419:23
*** ChanServ sets mode: +o openstack19:23
mriedemsure, i don't know when those sessions are though19:23
raginbajinWe could also use the OSOps repo's for capturing information as well.19:23
mriedemmonday?19:23
*** zhiyan_ is now known as zhiyan19:23
*** openstackstatus has joined #openstack-meeting-419:23
*** ChanServ sets mode: +v openstackstatus19:23
raginbajinThroughout the week and some of Friday19:23
mriedemok19:23
*** serverascode_ is now known as serverascode19:23
raginbajinBut it's just an idea. I'll raise a couple of question to the list and see what feedback comes out.19:24
mriedemsounds good19:24
raginbajinI'll hopefully have that email out by the weekend to the list.19:24
*** harmw has quit IRC19:24
*** sigmavirus24 has joined #openstack-meeting-419:25
mdormanback now.19:25
mriedemraginbajin: note that http://lists.openstack.org/pipermail/openstack-operators/2016-March/009942.html is already in the ops list19:25
*** harmw has joined #openstack-meeting-419:25
raginbajinOh good. I'll reference that as well.19:25
raginbajinThanks for dropping by.19:26
*** sbadia has joined #openstack-meeting-419:26
mriedemnp, i'd like to actually focus more in newton on communication between nova and ops19:26
mriedemso if there are issues from ops, getting those back in front of nova19:27
raginbajinThat would be great. That was one of the purposes of the OSOps groups.. Trying to figure out where we can bridge a lot of these ideas.19:27
mriedeme.g. things that a bunch of operators are struggling with or just having to patch themselves and need to integrate into nova19:27
raginbajinLets see if we can use this to start some discussions during some of these meetings and getting feedback that way.19:27
raginbajinUnless you (mriedem) want to discuss anything else, we'll get those emails out and see if we can start up some discussions and get some ideas going.19:29
mriedemi don't have anything else19:29
raginbajinCool. I think it's just you and me mdorman19:30
anteayathe meetbot is back19:30
anteayasorry it took so long19:30
klindgrenWe worked on getting some patches ops were caring into the tokyo summit19:30
klindgrenbut bascially I have bee nswamped and dropped the ball on all of that19:30
raginbajinanteaya: no problem..19:30
klindgrenits in an etherpad somewhere of common things more than one had done19:30
raginbajinklindgren: I remember seeing that somewhere and one from the mid-cycle as well.19:31
klindgren#end https://etherpad.openstack.org/p/operator-local-patches19:31
klindgrenargh19:31
klindgren#link https://etherpad.openstack.org/p/operator-local-patches19:31
klindgrenI think a few things in there are specific to nova19:32
klindgrensuch as extended validation on hostnames19:32
klindgrenalways generating the network template into config drive even if the neutron network is set to dhcp19:32
*** eil397 has joined #openstack-meeting-419:33
klindgrensome stuff around config drive and live migration - which I think was generally confirmed as new enough nova + new enough libvirt everything was probably resolved19:33
raginbajinSo, I think we have to think about how we make this easier for Nova guys to see this and for us to add this from these etherpad's so they get into a state that we can show them what we need19:33
*** annegentle has joined #openstack-meeting-419:34
raginbajinWe'll start the discussion on the Ops List and see what we get.  Then take these as well as others we have created, and find the best path to get these in front of the necessary teams.19:35
raginbajinThe last thing we have was about the updates to the PyPI that was sent around via email for the monitoring-for-openstack repo.19:35
mdormanseems like a good plan.   i think the major issue the last few months is just none of us have really had time to push on these things19:35
raginbajinAgreed. We should think about how we make it esaier.19:36
klindgrenso re: the monitoring-for-openstack19:37
raginbajinBut for the PyPI discussion - The basics was that someone was asking permission or if we could update a particular part of the monitoring-for-openstack repo.19:37
klindgrenseems like the guy who created that pypi repo no longer does tuff in the community anymore19:37
raginbajinAhh19:37
klindgrenand dropped it off into our repo when he left19:37
klindgrenas near as I can tell19:37
klindgrenatleast I remember something like that19:38
raginbajingotcha. Maybe we need to have some sort of disclaimer in the repo's that talk about that this is not an actively maintaned set of repo's and that it's a central source for finding tools19:38
*** inc0 has left #openstack-meeting-419:38
*** Sukhdev has joined #openstack-meeting-419:39
raginbajinor we just call this a one off and see if this comes up more.19:39
raginbajinI really just wanted to make sure the group knew about this more than anything.19:39
raginbajinMaybe nothing really needs any action at this ponit.19:39
raginbajinpoint*19:39
*** spzala has quit IRC19:40
raginbajinThat's the last thing on the list of items.. Unless anyone else has anything else, then that is it for today.19:40
mdormanthanks raginbajin19:41
klindgrenso actually re looking - looks like this was done by: Julien Danjou (jd)19:41
mriedemi have a question19:41
mriedemL116 in https://etherpad.openstack.org/p/operator-local-patches19:41
klindgrenhes still active maybe we can jsut ask him to cut a new release?19:41
raginbajinklindgren: The guy sent in a patch today. and it was approved and pushed19:42
raginbajinso it was done atleast in the repo's19:42
*** dims_ has joined #openstack-meeting-419:43
klindgrenmriedem, so all that stuff came from josh - and Y! has bascially stopped doing openstack stuffs except ironic as I understand it19:43
mriedemklindgren: plus harlowja isn't there anymore19:44
klindgrenyea hes with us now19:44
mriedemok, so, ....should the yahoo section be struck through?19:44
*** daneyon has quit IRC19:44
mriedemi remember going through this list at one point19:44
*** spzala has joined #openstack-meeting-419:44
klindgrenbascially everything that was line 93 and above was things that multiple people had done19:44
raginbajinI don't think it should be.  They have some interesting ideas that help other groups.19:45
*** daneyon has joined #openstack-meeting-419:45
*** dims has quit IRC19:45
*** yamamoto has joined #openstack-meeting-419:45
klindgrenor things that people had +1'd next to as in I dont have this but I want it19:46
raginbajinDoesn't sound like there is anything else.  Officially I will say that the meeting is over.19:47
mriedemok,19:47
mriedemi guess rolling the high priority ones up to nova is what i'm looking for in newton19:47
*** daneyon_ has joined #openstack-meeting-419:47
mriedemmight work in with the RFE process proposal19:47
raginbajin#endmeeting19:48
raginbajineven though it wasn't started.. just making sure for the next guy19:48
klindgrenyea - and anything thats godaddy related - I can get you patches for19:48
klindgrenraginbajin, you so nice19:48
raginbajin:)19:48
*** zeih_ has joined #openstack-meeting-419:49
*** spzala has quit IRC19:49
*** ninag has joined #openstack-meeting-419:50
*** daneyon has quit IRC19:50
mriedemi'll poke through this list and make notes where possible19:51
*** dims_ has quit IRC19:53
*** mriedem has left #openstack-meeting-419:53
*** yamamoto has quit IRC19:53
*** rocky_g has joined #openstack-meeting-419:54
*** zeih_ has quit IRC19:54
*** dims has joined #openstack-meeting-419:56
*** minwang2 has joined #openstack-meeting-419:56
*** ajmiller_ is now known as ajmiller20:00
rocky_ganyone here for logging?20:01
*** Sukhdev has quit IRC20:01
rocky_gping jokke_ rbradfor dhellmann ?  Or did I get the time messed up?20:02
*** yamahata has quit IRC20:04
*** ihrachys_ has joined #openstack-meeting-420:04
rbradforrocky_g, not sure with the TZ change.  I'm busy at present for rest for today.20:04
rocky_grbradfor, thanks.  Just an FYI for you.  I added you to a review on cross project config spec to replicate nova's efforts across all proj's20:05
*** ihrachys has quit IRC20:05
*** mdorman has left #openstack-meeting-420:07
*** zeih_ has joined #openstack-meeting-420:07
*** hvprash has joined #openstack-meeting-420:11
*** hvprash__ has quit IRC20:12
*** hvprash has quit IRC20:18
*** openstack has joined #openstack-meeting-420:33
*** ChanServ sets mode: +o openstack20:33
*** Sukhdev has quit IRC20:38
*** trozet_ is now known as trozet20:39
*** sdague has quit IRC20:44
*** jmckind has quit IRC20:44
*** jmckind has joined #openstack-meeting-420:47
*** angdraug has joined #openstack-meeting-420:50
*** fawadkhaliq has quit IRC20:53
*** fawadkhaliq has joined #openstack-meeting-420:53
*** david-lyle has quit IRC20:59
*** fawadkhaliq has quit IRC21:04
*** fawadk has joined #openstack-meeting-421:04
*** david-lyle has joined #openstack-meeting-421:05
*** rtheis has quit IRC21:06
*** spzala has joined #openstack-meeting-421:06
*** matrohon has joined #openstack-meeting-421:06
*** dtardivel has quit IRC21:08
*** spzala has quit IRC21:08
*** spzala has joined #openstack-meeting-421:08
*** zeih has quit IRC21:09
*** gmolson has joined #openstack-meeting-421:09
*** woodard_ has joined #openstack-meeting-421:10
*** thorst has quit IRC21:11
*** thorst has joined #openstack-meeting-421:12
*** woodard has quit IRC21:13
*** vhoward has quit IRC21:13
*** woodard_ has quit IRC21:14
*** thorst_ has joined #openstack-meeting-421:14
*** neelashah1 has joined #openstack-meeting-421:15
*** unicell has quit IRC21:15
*** unicell has joined #openstack-meeting-421:15
*** neelashah has quit IRC21:16
*** JRobinson__ has joined #openstack-meeting-421:16
JRobinson__Good morning,21:16
JRobinson__First of all apologise to the channel, there User Guide meeting has had a delayed start today, but will begin now21:16
*** thorst__ has joined #openstack-meeting-421:16
*** thorst has quit IRC21:17
gmolsonHi Joseph. I'm here.21:18
JRobinson__gmolson, hello, the DST change affected my time plan, unfortunately21:18
*** thorst_ has quit IRC21:18
gmolsonoh... boo. :(21:18
rocky_go/21:19
gmolsonheads up - I need to head out at the bottom of the hour.21:19
JRobinson__#startmeeting docuserguides21:20
openstackMeeting started Wed Mar 23 21:20:07 2016 UTC and is due to finish in 60 minutes.  The chair is JRobinson__. Information about MeetBot at http://wiki.debian.org/MeetBot.21:20
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:20
*** openstack changes topic to " (Meeting topic: docuserguides)"21:20
openstackThe meeting name has been set to 'docuserguides'21:20
*** thorst__ has quit IRC21:21
*** david-lyle has quit IRC21:21
JRobinson__#topic CLI chapter21:22
*** openstack changes topic to "CLI chapter (Meeting topic: docuserguides)"21:22
*** ddieterly has joined #openstack-meeting-421:22
JRobinson__So while I try and figure out what time the meeting should be starting now that DST has changed in the US, Well run through the agenda.21:22
JRobinson__This won't take long though. The first item is the cli chapter. gmolson thanks again for starting this part of the reorg.21:23
*** IlyaG has quit IRC21:23
JRobinson__bernd has taken on moving the second half, which included just the remaining cli common files.21:23
*** david-lyle has joined #openstack-meeting-421:23
gmolsonSounds good to figure out a new time. I'm not currently a fan of DST time change. ;)21:24
gmolsonNo problem - thanks for helping get them integrated.21:24
gmolsonSounds great that Bernd is working on the second half - common cli files.21:24
gmolsonI noticed your troubleshooting updates. Nice work!21:24
gmolsonThat is a good improvement.21:24
JRobinson__okay, I updated the file tracking table after the patch -21:25
JRobinson__#info double check the table to ensure no files were missed in the move21:25
*** lakshmiS has quit IRC21:26
gmolsonthanks21:26
*** Sukhdev has joined #openstack-meeting-421:26
JRobinson__#link https://wiki.openstack.org/wiki/Documentation/ReorganizeUserGuides#File_Tracking_Table21:26
JRobinson__#topic title change21:26
*** openstack changes topic to "title change (Meeting topic: docuserguides)"21:26
JRobinson__gmolson, thanks, the troubleshooting change is the second last reorg item next to the title change21:26
JRobinson__Change use of  'Cloud Admin Guide' to change to 'Administrator Guide'21:27
*** sdake has quit IRC21:27
JRobinson__#info Change use of  'Cloud Admin Guide' to change to 'Administrator Guide'21:27
*** klindgren has left #openstack-meeting-421:28
JRobinson__I will most likely need some help on this to change all the instances.21:28
JRobinson__Okay, last item21:29
JRobinson__#topic Release Notes Update21:29
*** openstack changes topic to "Release Notes Update (Meeting topic: docuserguides)"21:29
JRobinson__This is just a notice - I'll also be patching the release notes for the User Guides for Mitaka21:29
gmolsonWhen do the title reference changes need to be complete?21:29
JRobinson__The large changes are  Guides reorganised together, Consistent troubleshooting, Several edits for style and Grammar.21:30
JRobinson__Open discussion21:30
gmolsonsaw your update with draft bullets in your note. Looks good to me.21:30
JRobinson__thanks gmolson,21:30
*** ninag has quit IRC21:31
JRobinson__and the title change is going to start today, or early next week. As long as it is complete by the start of April to have all the major changes complete by the release.21:31
gmolsonok21:32
gmolsonNot sure how much time I will have to help out. Have some vacation scheduled next week and some ibm deadlines, but will see what I can do to assist. I'll also pass the word to Linette.21:32
JRobinson__I'll add some of the files changed to the file tracking table, just to keep the changes clear.21:32
gmolsonok21:33
JRobinson__gmolson, thanks, it's appreciated :)21:33
JRobinson__#topic Open Discussion21:33
*** openstack changes topic to "Open Discussion (Meeting topic: docuserguides)"21:33
JRobinson__So that was all, sorry for the high speed meeting,21:34
gmolsonWhat time is it for now?21:34
gmolson*you now?21:34
*** thorst has joined #openstack-meeting-421:34
JRobinson__Right now, 7:34 AM, so the meeting time is an hour earlier in the APAC timezone.21:35
JRobinson__is it around 3pm in the US?21:35
rocky_g2:35 in PDT, west coast21:35
gmolsonoh geez. my world clock on my phone is saying that it is 8:35 in Sydney.21:35
gmolsonit's 4:35 in CST21:35
JRobinson__rocky_g, thanks, thanks gmolson, that makes sense21:36
gmolsonsorry for the early meeting for you :/21:36
*** baoli has quit IRC21:36
rocky_gwhat gmolson said :-(21:36
*** ddieterly is now known as ddieterly[away]21:36
JRobinson__it's okay - it's workable since it's just fortnightly. Weekly might be a struggle21:36
gmolsonHope that you find some coffee (or your morning drink of choice) and have a good day!21:36
JRobinson__gmolson, thanks :)21:37
*** IlyaG has joined #openstack-meeting-421:37
JRobinson__also will you and Linette be at the summit in Austin?21:37
rocky_gI'd take a nap for you, but I think it would only help me ;-)21:38
*** thorst has quit IRC21:38
JRobinson__rocky_g, ha ha thanks :)21:40
*** ddieterly[away] is now known as ddieterly21:40
JRobinson__anyway gmolson I'll send out an email about title changes.21:41
gmolsonsorry - missed your question, Joseph21:42
JRobinson__gmolson, no problems21:42
gmolsonWe are hoping to be, but have not gotten the thumbs up at this point.21:42
JRobinson__Incidentally, this Friday and next Monday are public holidays in Australia, so most likely early next week for the last updates.21:43
gmolsonsounds good on the email with title changes21:43
JRobinson__gmolson, okay,21:43
gmolsongotcha, Joseph21:43
JRobinson__alright, I'll end the meeting for now21:43
JRobinson__#endmeeting21:44
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:44
openstackMeeting ended Wed Mar 23 21:44:28 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-03-23-21.20.html21:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-03-23-21.20.txt21:44
openstackLog:            http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-03-23-21.20.log.html21:44
*** rocky_g has quit IRC21:45
*** rocky_g has joined #openstack-meeting-421:45
*** matrohon has quit IRC21:49
*** banix has quit IRC21:49
*** matrohon has joined #openstack-meeting-421:50
*** gmolson has quit IRC21:50
*** zeih_ has quit IRC21:52
*** xarses_ has joined #openstack-meeting-421:52
*** xarses has quit IRC21:52
*** JRobinson__ is now known as JRobinson__afk21:55
*** jmckind has quit IRC21:55
*** sdake has joined #openstack-meeting-421:55
*** ihrachys_ has quit IRC21:56
*** xarses_ is now known as xarses21:56
*** vishnoianil has quit IRC21:56
*** IlyaG has quit IRC21:58
*** sigmavirus24 is now known as sigmavirus24_awa21:59
*** zeih has joined #openstack-meeting-421:59
*** JRobinson__afk has quit IRC22:04
*** bobh has joined #openstack-meeting-422:06
*** spzala has quit IRC22:07
*** spzala has joined #openstack-meeting-422:08
*** baoli has joined #openstack-meeting-422:09
*** JRobinson__ has joined #openstack-meeting-422:11
*** matrohon has quit IRC22:12
*** spzala has quit IRC22:12
*** pmesserli has quit IRC22:12
*** zeih has quit IRC22:18
*** baoli has quit IRC22:18
*** sdake_ has joined #openstack-meeting-422:29
*** sdake has quit IRC22:30
*** spotz is now known as spotz_zzz22:32
*** SimonChung1 has quit IRC22:35
*** SimonChung has joined #openstack-meeting-422:35
*** rocky_g has quit IRC22:39
*** spzala has joined #openstack-meeting-422:46
*** zehicle_ has quit IRC22:47
*** zehicle_ has joined #openstack-meeting-422:49
*** Jeffrey4l has quit IRC22:49
*** saneax_AFK is now known as saneax22:51
*** fawadk has quit IRC22:53
*** fawadkhaliq has joined #openstack-meeting-422:53
*** yamahata has joined #openstack-meeting-422:54
*** zehicle_ has quit IRC22:55
*** fawadkhaliq has quit IRC22:55
*** fawadkhaliq has joined #openstack-meeting-422:56
*** sdake_ is now known as sdake22:59
*** neelashah1 has quit IRC22:59
*** IlyaG has joined #openstack-meeting-422:59
*** SimonChung has quit IRC23:01
*** SimonChung has joined #openstack-meeting-423:01
*** zehicle_ has joined #openstack-meeting-423:01
*** ddieterly has quit IRC23:02
*** angdraug has quit IRC23:02
*** SimonChung has quit IRC23:03
*** SimonChung has joined #openstack-meeting-423:03
*** IlyaG has quit IRC23:04
*** darrenc_ has joined #openstack-meeting-423:05
*** sbog has quit IRC23:06
*** darrenc has quit IRC23:06
*** darrenc_ is now known as darrenc23:07
*** fawadkhaliq has quit IRC23:07
*** fawadkhaliq has joined #openstack-meeting-423:08
*** sbog has joined #openstack-meeting-423:08
*** zeih has joined #openstack-meeting-423:12
*** SimonChung has quit IRC23:14
*** SimonChung1 has joined #openstack-meeting-423:14
*** zeih has quit IRC23:18
*** openstack has joined #openstack-meeting-423:24
*** ChanServ sets mode: +o openstack23:24
*** sridhar_ram has quit IRC23:27
JRobinson__Hello everyone, I'll start the APAC user guide meeting now23:34
*** fawadkhaliq has quit IRC23:39
JRobinson__#startmeeting docuserguides23:39
openstackMeeting started Wed Mar 23 23:39:49 2016 UTC and is due to finish in 60 minutes.  The chair is JRobinson__. Information about MeetBot at http://wiki.debian.org/MeetBot.23:39
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.23:39
*** openstack changes topic to " (Meeting topic: docuserguides)"23:39
openstackThe meeting name has been set to 'docuserguides'23:39
JRobinson__okay, so it looks as though APAC attendance is lower than last meeting.23:40
JRobinson__Just to reiterate for anyone reading the logs or following along:23:43
JRobinson__#topic Create a command line chapter patch update23:44
*** openstack changes topic to "Create a command line chapter patch update (Meeting topic: docuserguides)"23:45
*** angdraug has joined #openstack-meeting-423:45
JRobinson__I have contacted the team to discuss this point.23:45
JRobinson__#topic Title change23:45
*** openstack changes topic to "Title change (Meeting topic: docuserguides)"23:45
JRobinson__The title and use of "Cloud Admin" for the Cloud Admin guide is set to change to "Administrator Guide" soon.23:45
JRobinson__#topic Release Notes Update23:45
*** openstack changes topic to "Release Notes Update (Meeting topic: docuserguides)"23:45
JRobinson__Changes for the Mitaka release wiill soon be added to the release notes23:46
JRobinson__Discussion within the team included noting the changes to:23:46
JRobinson__Admin Guide is now a part of the cloud admin guide23:47
JRobinson__The cloud admin guide has been renamed23:47
JRobinson__the administrator guide has consistent troubleshooting headings23:47
JRobinson__several chapters have had thorough edits to style and grammar to improve readability23:48
JRobinson__#topic open discussion23:48
*** openstack changes topic to "open discussion (Meeting topic: docuserguides)"23:48
JRobinson__Having said that, and recorded the discussion points for the meeting minutes, I'll close this short meeting down if there are no questions.23:48
*** fawadkhaliq has joined #openstack-meeting-423:49
JRobinson__okay, thanks everyone23:50
JRobinson__#endmeeting23:50
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:50
openstackMeeting ended Wed Mar 23 23:50:36 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-03-23-23.39.html23:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-03-23-23.39.txt23:50
openstackLog:            http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-03-23-23.39.log.html23:50
*** eil397 has quit IRC23:53
*** sridhar_ram has joined #openstack-meeting-423:53
*** galstrom_zzz is now known as galstrom23:57
*** Sukhdev has quit IRC23:57
*** spzala has quit IRC23:59
*** Sukhdev has joined #openstack-meeting-423:59
*** ajmiller has quit IRC23:59
*** sridhar_ram has quit IRC23:59

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