Thursday, 2017-01-05

ekcs#startmeeting congressteammeeting00:00
openstackMeeting started Thu Jan  5 00:00:17 2017 UTC and is due to finish in 60 minutes.  The chair is ekcs. Information about MeetBot at http://wiki.debian.org/MeetBot.00:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.00:00
*** openstack changes topic to " (Meeting topic: congressteammeeting)"00:00
openstackThe meeting name has been set to 'congressteammeeting'00:00
ekcsWelcome back everyone! Hope everyone had a nice break.00:00
*** ijw has quit IRC00:00
aimeeuHello all - Happy 2017!00:01
ekcshello aimeeu happy 2017!00:01
*** thinrichs1 has joined #openstack-meeting00:01
ekcsAgenda items for today:00:02
ekcs- Extra-ATC00:02
ekcs- Ocata-3 schedule00:02
ekcs- Ocata-3 QA00:02
ekcs- Name and ID in API00:02
ekcs- status and open discussion00:02
ekcsanything else to add?00:02
masahitohi00:02
masahito happy new year00:02
thinrichs1Happy New Year everyone!00:02
ekcshappy new year masahito !00:02
ekcshappy new year thinrichs1 !00:03
*** gouthamr has quit IRC00:04
ekcsok then. let’s move right along  = )00:04
ekcs#topic extra-ATC00:04
*** openstack changes topic to "extra-ATC (Meeting topic: congressteammeeting)"00:04
ekcsExtra-ATC proposal is due Friday. My bad for not having brought it up earlier.00:04
ekcsAnyone has an extra-ATC to propose?00:04
thinrichs1Not me.00:05
*** ansmith has quit IRC00:05
*** saisrikiran has joined #openstack-meeting00:05
ekcsme neither. Well please let me know today or tomorrow if you do have someone to propose.00:06
ekcs#topic Ocata-3 schedule00:06
*** openstack changes topic to "Ocata-3 schedule (Meeting topic: congressteammeeting)"00:06
ekcsOcata-3 release and final client release are officially due on the week of Jan 23.00:06
ekcs#link https://releases.openstack.org/ocata/schedule.html00:07
ekcsHere is a proposed schedule for us leading up to that.00:07
ekcs1. Submit/revise patches for review by Jan 1200:07
ekcs2. Target merging by Jan 1600:07
ekcs3. Ocata-3 QA and fixes Jan 16 - Jan 2000:07
ekcs4. Target Jan 23 for release (allowing a few days slack room if we experience delays like bug fixes that take longer)00:07
ekcsDoes that sound reasonable? Any thoughts or comments?00:07
thinrichs1Sounds reasonable to me.00:09
*** fnaval has quit IRC00:09
*** jrist_ has joined #openstack-meeting00:09
ekcsgot it thinrichs100:10
masahitoSounds good to me.00:10
*** jrist has quit IRC00:10
ekcsDoes anyone anticipate having difficulty getting Ocata patches submitted/revised by Jan 12?00:10
ekcsFeel free to let people know so we can help = )00:10
*** thorst_ has quit IRC00:10
*** tommylikehu_ has joined #openstack-meeting00:11
ekcsok then. let’s aim to get our patches in by Jan 12 (next meeting).00:12
*** Swami_ has joined #openstack-meeting00:12
ekcs#action everyone submit/revise ocata patches00:12
ekcsany other comments on ocata-3 schedule before we move on?00:13
*** yangyape_ has quit IRC00:13
ekcs#topic Ocata-3 QA00:14
*** openstack changes topic to "Ocata-3 QA (Meeting topic: congressteammeeting)"00:14
ekcsI've set up some QA related tasks for Ocata-3.00:14
ekcs#link https://bugs.launchpad.net/congress/+bugs?field.tag=qa00:14
ekcsCould we take a quick look and see if they make sense?00:15
*** Swami__ has joined #openstack-meeting00:15
ekcsAny comments on what to add/remove/restructure?00:15
*** Swami has quit IRC00:15
*** spzala has quit IRC00:15
*** tommylikehu_ has quit IRC00:15
*** tdasilva has quit IRC00:16
masahitoHow about adding a test that check datasource failover?00:17
masahitoThe list looks good to me. So this is an additional test for release.00:18
thinrichs1Do we know what other teams do for QA?  Are they manually setting up different setups?  Or are they automating all that and putting it into the gate?00:18
*** Swami_ has quit IRC00:18
*** absubram has quit IRC00:20
*** rfolco has joined #openstack-meeting00:20
ekcsmasahito: sounds like a good idea. you want to go ahead and add a task for that?00:20
*** rfolco has quit IRC00:20
ekcsthinrichs1: I’m not sure. I imagine the more we can push into gate the better.00:21
masahitoekcs: sure.00:21
*** sdague has quit IRC00:21
ekcsthinrichs1: I just know from last cycle that we needed additional testing to catch many of the bugs.00:22
thinrichs1Agreed.  I was trying to figure out if it's feasible to move toward pushing more into the gate.00:23
ekcsthinrichs1: so the thinking is we can do some manual tests and try to generalize that to gate. some we can do right away while testing for ocata-3. (say setting up devstack test with postgres should be straight forward). some we can do during RC period.00:24
ekcsthe task for collecting manual testing scripts would be a good start to strengthening integrated tests at gate.00:25
thinrichs1All sounds good to me.00:25
ekcsalright feel free to make additional comments/changes on the tasks and also to sign up.00:26
ekcslet’s move on then.00:27
*** jrobinson is now known as jrobinson-afk00:27
ekcs#topic Name and ID in API00:27
*** openstack changes topic to "Name and ID in API (Meeting topic: congressteammeeting)"00:27
ekcsWe had a discussion on this patch regarding accepting (policy & datasource) name and ID in API.00:28
ekcs#link https://review.openstack.org/#/c/412303/00:28
ekcsThe main issue is that as implemented, names and UUIDs can clash, causing ambiguity and misinterpretation of caller intent.00:30
ekcsI think everyone agrees we want to accept both name and UUID in the API calls, just not sure whether to disambiguate implicitly or explicitly.00:31
ekcsFrom the discussion I think we may have the following consensus:00:31
ekcs1. legislate and enforce that names cannot have hyphens00:32
ekcs2. legislate and enforce that IDs must have hyphens (or be disjoint from the space of names another way)00:32
ekcs3. For historical and compatibility reasons, APIs will accept a name_or_id parameter and disambiguate based on which space the param belongs to (ie. whetehr it has hyphens)00:33
thinrichs1I think that's right.  Though I don't know how high on the priority list this is.  The chances that someone wants to use something that looks like a UUID for a policy/datasource name is small IMO.00:34
*** amotoki has quit IRC00:34
thinrichs1The part of this that I think is higher-priority is ensuring that policy names and datasource names are valid identifiers in the policy language.00:35
thinrichs1There are tests in there now for the policy names, but they don't seem to reject what they should.00:35
ekcsthinrichs1: got it. yes I agree that enforcing no-hyphens in identifiers is high priority. more likely to affect people. get it enforced sooner rather than later to avoid upgrade problems down the road.00:36
ekcsmasahito , aimeeu do you have any thoughts?00:37
masahitoit makes sense.00:38
aimeeuI do agree with getting the no-hyphens enforced sooner rather than later00:38
ekcsthinrichs1: and the discussion it’s only high priority because if we go a different way, we want to stop the spread of name_or_id use in the API right now.00:39
*** dimtruck is now known as zz_dimtruck00:39
*** hongbin has quit IRC00:40
ekcsthe main argument I can see against this proposal is that it places restrictions on the form of the ID that we can’t change later without breaking API. So say openstack decides for some reason to universally adopt a different form of ID that doesn’t have dashes, then we have to break the API.00:40
ekcsbut it’s unlikely and even if it happens we can deal with it then.00:40
*** mriedem has quit IRC00:41
ekcsanyway ok. sounds like we’re all on board. ramineni too judging from her patches.00:41
ekcsthinrichs1: do you have any thoughts on how the hyphens are being let through in policy names?00:41
*** jrobinson-afk is now known as jrobinson00:42
thinrichs1No idea.  I imagine the check isn't running when new policies get created.00:42
thinrichs1I'm pretty sure the check will fail if you give it a uuid00:43
ekcsok. well hopefully we can figure this out and patch it up for ocata-3. I’ll do some more testing.00:43
thinrichs1To run that check on datasource creation too, we'll want to pull it out into somewhere that the datasource creation code can easily import it.00:44
thinrichs1I'll try to take a look tonight after the meeting.00:44
*** neiljerram has quit IRC00:44
ekcsright. that’s a question: should the check be done via compiler code or another code or both.00:44
ekcsok then. let’s move on for now. thanks thinrichs1 !00:44
ekcs#topic open discussion00:45
*** openstack changes topic to "open discussion (Meeting topic: congressteammeeting)"00:45
ekcsany topics on your mind or statuses you’d like to update?00:45
*** gongysh has quit IRC00:47
ekcsit’s still fairly rough right now, but if you get a chance, some early feedback on this patch would be helpful: #link https://review.openstack.org/#/c/416777/00:48
ekcsI struggled with how to resolve this bug for quite a while. there are many many options and none of them really that great.00:48
*** Leo_ has joined #openstack-meeting00:49
*** Leom_ has quit IRC00:49
ekcsok if there is nothing more to discuss, let’s end the meeting early. speak up in the next couple minutes if you want to talk about something  = )00:49
thinrichs1Can you give an overview of what that patch is doing?00:50
ekcsyup. two main things:00:51
ekcs1. lock rules table in DB00:51
ekcs2. synchronize rules00:51
ekcsbefore each rule insert.00:51
ekcsit’s conceptually the simplest solution. a little bit messy because of db sessions and db specific locks and unlocks and all that stuff.00:52
thinrichs1That seems like it should work.  You said it wasn't great.  Is it just messy?  Or is there a problem it doesn't solve?00:53
ekcsi don’t like ti because it requires locking and syncing before every rule insert in prevent something (recursion) that has very low chance of happening.00:53
ekcssyncing is expensive, and locking prevents us from supporting multi-master HA DBs00:53
thinrichs1Is it just recursion?00:54
ekcsat this point it’s just recursion I think.00:54
*** thorst_ has joined #openstack-meeting00:54
ekcsif we decided to allow recursion then there is stratification to check.00:54
ekcsbut there will always be something.00:54
thinrichs1I guess recursion is a special instance of 2 people using the same table-name for different things. (Unless they're actively trying to break the system.)00:55
thinrichs1If it's just recursion, we could change eval to fail when it recurses instead of infinite looping.00:56
thinrichs1Then people would figure it out on their own.00:56
ekcsyea that’s a possibility.00:56
thinrichs1And then in this wacky case where 2 people accidentally create recursion, they'd end up having to dig into the problem anyway.00:57
thinrichs1And someone trying to break the system couldn't.00:57
ekcsdownside there is it would look like your rule got in there and you may expect it is being used/enforced/monitored.00:57
ekcswe could also back out the latest rule by timestamp when recursion detected.00:58
thinrichs1Sure, but it's broken anyway b/c someone else used the same tablename for their own thing.00:58
thinrichs1So you wouldn't get the results you want in any case.00:58
ekcsactually people can use the same table for the same thing and still cause recursion.00:58
thinrichs1It's just that on the off-chance 2 people use the same tablename for different things AND they happen to refer to each other's recursively that we catch the bug at the time the policy is inserted.00:58
ekcsa may say p => q and b may say q => p. both meaning the same thing just defining in diff direction.00:59
thinrichs1Not in datalog they can't.00:59
*** dongfeng has left #openstack-meeting00:59
thinrichs1p :- q and q :- p mean  different things.00:59
thinrichs1Anyway, out of time.01:00
ekcsyea.01:00
ekcsok then! maybe we can talk more about it outside.01:00
thinrichs1I'm in #congress if want to continue01:00
ekcsgreat.01:00
ekcsthanks all! have a great week!01:00
ekcs#endmeeting01:00
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"01:00
openstackMeeting ended Thu Jan  5 01:00:57 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)01:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/congressteammeeting/2017/congressteammeeting.2017-01-05-00.00.html01:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/congressteammeeting/2017/congressteammeeting.2017-01-05-00.00.txt01:01
openstackLog:            http://eavesdrop.openstack.org/meetings/congressteammeeting/2017/congressteammeeting.2017-01-05-00.00.log.html01:01
masahitobye01:01
*** saisrikiran has quit IRC01:02
*** huanxuan has joined #openstack-meeting01:08
*** yamamoto has joined #openstack-meeting01:09
*** VW has joined #openstack-meeting01:11
*** liuyulong has joined #openstack-meeting01:14
*** VW has quit IRC01:15
*** fitoduarte has quit IRC01:16
*** ijw has joined #openstack-meeting01:17
*** yamamoto has quit IRC01:18
*** yamamoto has joined #openstack-meeting01:18
*** ijw has quit IRC01:20
*** thinrichs1 has left #openstack-meeting01:20
*** sdake has quit IRC01:21
*** lhx_ has joined #openstack-meeting01:23
*** yangyapeng has joined #openstack-meeting01:25
*** beagles_biab is now known as beagles01:26
*** Swami__ has quit IRC01:28
*** kevinz has joined #openstack-meeting01:30
*** mriedem has joined #openstack-meeting01:31
*** Leo_ has quit IRC01:33
*** yamamoto has quit IRC01:33
*** Leo_ has joined #openstack-meeting01:34
*** yamamoto has joined #openstack-meeting01:34
*** bobmel has quit IRC01:35
*** saisrikiran has joined #openstack-meeting01:40
*** bkopilov has quit IRC01:41
*** yamamoto has quit IRC01:43
*** lhx_ has quit IRC01:44
*** kjorgens_ has quit IRC01:47
*** epico has joined #openstack-meeting01:47
*** yamamoto has joined #openstack-meeting01:49
*** kjorgens_ has joined #openstack-meeting01:51
*** bkopilov has joined #openstack-meeting01:52
*** yamamoto has quit IRC01:52
*** yamamoto has joined #openstack-meeting01:54
*** baoli has joined #openstack-meeting01:55
*** yangyape_ has joined #openstack-meeting01:55
*** kjorgens_ has quit IRC01:56
*** yangyapeng has quit IRC01:58
*** gongysh has joined #openstack-meeting02:00
*** nadya has joined #openstack-meeting02:02
*** guoshan has joined #openstack-meeting02:02
*** baoli has quit IRC02:06
*** nadya has quit IRC02:07
*** guoshan has quit IRC02:09
*** bzhao has joined #openstack-meeting02:09
*** guoshan has joined #openstack-meeting02:09
*** saisrikiran has quit IRC02:10
*** ijw has joined #openstack-meeting02:10
*** yamamoto has quit IRC02:11
*** ijw has quit IRC02:11
*** Leo_ has quit IRC02:14
*** Leo_ has joined #openstack-meeting02:15
*** unicell has quit IRC02:20
*** lhx_ has joined #openstack-meeting02:20
*** zz_dimtruck is now known as dimtruck02:22
*** unicell has joined #openstack-meeting02:23
*** kjorgensen has joined #openstack-meeting02:29
*** lhx__ has joined #openstack-meeting02:32
*** kjorgensen has quit IRC02:34
*** Leo_ has quit IRC02:34
*** lhx_ has quit IRC02:35
*** Leo_ has joined #openstack-meeting02:35
*** yangyapeng has joined #openstack-meeting02:36
*** s3wong has quit IRC02:37
*** yangyape_ has quit IRC02:40
*** ljxiash has joined #openstack-meeting02:41
*** unicell has quit IRC02:42
*** baoli has joined #openstack-meeting02:42
*** Julien-zte has joined #openstack-meeting02:51
*** baoli has quit IRC02:55
*** baoli has joined #openstack-meeting02:58
*** kjorgensen has joined #openstack-meeting03:00
*** jrobinson is now known as jrobinson-afk03:01
*** bkopilov has quit IRC03:04
*** kjorgensen has quit IRC03:05
*** rmk has quit IRC03:05
*** harlowja has quit IRC03:05
*** tonyb has quit IRC03:05
*** rhagarty has quit IRC03:05
*** acoles_ has quit IRC03:05
*** mugsie|alt has quit IRC03:05
*** jgriffith has quit IRC03:05
*** mminesh has quit IRC03:05
*** gothicmindfood has quit IRC03:05
*** yantarou has quit IRC03:05
*** nibalizer has quit IRC03:05
*** mminesh` has joined #openstack-meeting03:05
*** mugsie|alt has joined #openstack-meeting03:05
*** tonyb has joined #openstack-meeting03:05
*** yantarou has joined #openstack-meeting03:05
*** gothicmindfood has joined #openstack-meeting03:05
*** nibalizer has joined #openstack-meeting03:05
*** mminesh` is now known as mminesh03:05
*** jgriffith has joined #openstack-meeting03:06
*** rhagarty has joined #openstack-meeting03:06
*** kaisers1 has joined #openstack-meeting03:06
*** acoles_ has joined #openstack-meeting03:06
*** acoles_ is now known as acoles03:06
*** rmk has joined #openstack-meeting03:07
*** rmk has quit IRC03:07
*** rmk has joined #openstack-meeting03:07
*** ekcs has quit IRC03:08
*** diablo_rojo has quit IRC03:13
*** thorst_ has quit IRC03:14
*** thorst_ has joined #openstack-meeting03:15
*** Leo_ has quit IRC03:15
*** ljxiash has quit IRC03:15
*** Leo_ has joined #openstack-meeting03:15
*** hongbin has joined #openstack-meeting03:15
*** ljxiash has joined #openstack-meeting03:15
*** mriedem has quit IRC03:16
*** baoli has quit IRC03:18
*** baoli has joined #openstack-meeting03:19
*** thorst_ has quit IRC03:19
*** gouthamr has joined #openstack-meeting03:19
*** yamamoto has joined #openstack-meeting03:20
*** ljxiash has quit IRC03:20
*** zhurong has joined #openstack-meeting03:21
*** iyamahat has quit IRC03:22
*** yamahata has quit IRC03:22
*** yangyape_ has joined #openstack-meeting03:22
*** sudipto_ has joined #openstack-meeting03:24
*** sudipto has joined #openstack-meeting03:24
*** dimtruck is now known as zz_dimtruck03:24
*** yangyapeng has quit IRC03:24
*** thorst_ has joined #openstack-meeting03:25
*** thorst_ has quit IRC03:25
*** amotoki has joined #openstack-meeting03:30
*** ljxiash has joined #openstack-meeting03:31
*** jrobinson-afk is now known as jrobinson-03:31
*** jrobinson- is now known as jrobinson03:31
*** julim has joined #openstack-meeting03:32
*** Leo_ has quit IRC03:35
*** Leo_ has joined #openstack-meeting03:35
*** baoli has quit IRC03:36
*** links has joined #openstack-meeting03:40
*** zhurong has quit IRC03:41
*** lhx__ has quit IRC03:43
*** askb has quit IRC03:43
*** VW has joined #openstack-meeting03:45
*** r-mibu has quit IRC03:47
*** bobmel has joined #openstack-meeting03:47
*** r-mibu has joined #openstack-meeting03:47
*** bobmel has quit IRC03:52
*** ijw has joined #openstack-meeting03:53
*** askb has joined #openstack-meeting03:55
*** bkero has quit IRC03:56
*** ricolin has joined #openstack-meeting03:56
*** guoshan has quit IRC03:57
*** thorst_ has joined #openstack-meeting04:01
*** thorst_ has quit IRC04:01
*** ljxiash has quit IRC04:04
*** ljxiash has joined #openstack-meeting04:04
*** ljxiash has quit IRC04:09
*** csomerville has joined #openstack-meeting04:14
*** janki has joined #openstack-meeting04:14
*** cody-somerville has quit IRC04:17
*** vishnoianil has quit IRC04:23
*** saisrikiran has joined #openstack-meeting04:24
*** masahito has quit IRC04:24
*** qpqp has quit IRC04:29
*** bkopilov has joined #openstack-meeting04:30
*** kenji-i has quit IRC04:33
*** bswartz_ has joined #openstack-meeting04:35
*** gouthamr has quit IRC04:43
*** ijw has quit IRC04:45
*** ijw has joined #openstack-meeting04:49
*** VW has quit IRC04:52
*** ljxiash has joined #openstack-meeting04:53
*** ljxiash has quit IRC04:57
*** guoshan has joined #openstack-meeting04:57
*** guoshan has quit IRC05:02
*** sudipto has quit IRC05:02
*** sudipto_ has quit IRC05:02
*** nadya has joined #openstack-meeting05:05
*** yangyapeng has joined #openstack-meeting05:06
*** ljxiash has joined #openstack-meeting05:06
*** yangyap__ has joined #openstack-meeting05:07
*** yangyape_ has quit IRC05:09
*** nadya has quit IRC05:09
*** yangyap__ has quit IRC05:09
*** yangyape_ has joined #openstack-meeting05:09
*** yangyapeng has quit IRC05:11
*** kjorgensen has joined #openstack-meeting05:12
*** claudiub has quit IRC05:15
*** ykatabam has quit IRC05:17
*** kjorgensen has quit IRC05:17
*** ricolin has quit IRC05:17
*** saisrikiran has quit IRC05:21
*** hongbin has quit IRC05:24
*** sudipto has joined #openstack-meeting05:27
*** sudipto_ has joined #openstack-meeting05:27
*** prateek has joined #openstack-meeting05:28
*** jchhatbar has joined #openstack-meeting05:29
*** prateek has quit IRC05:30
*** janki has quit IRC05:30
*** lhx__ has joined #openstack-meeting05:30
*** prateek has joined #openstack-meeting05:30
*** yangyape_ has quit IRC05:35
*** guoshan has joined #openstack-meeting05:38
*** yangyapeng has joined #openstack-meeting05:39
*** salv-orlando has joined #openstack-meeting05:41
*** unicell has joined #openstack-meeting05:41
*** dfflanders has quit IRC05:41
*** Cibo_ has joined #openstack-meeting05:41
*** guoshan has quit IRC05:43
*** guoshan has joined #openstack-meeting05:43
*** ayogi has joined #openstack-meeting05:48
*** ykatabam has joined #openstack-meeting05:51
*** guoshan has quit IRC05:55
*** jchhatbar has quit IRC05:58
*** jchhatbar has joined #openstack-meeting05:58
*** ljxiash_ has joined #openstack-meeting05:59
*** thorst_ has joined #openstack-meeting06:02
*** ljxiash has quit IRC06:02
*** guoshan has joined #openstack-meeting06:06
*** VW has joined #openstack-meeting06:06
*** thorst_ has quit IRC06:07
*** Julien-zte has quit IRC06:09
*** aeng has quit IRC06:09
*** lhx__ has quit IRC06:11
*** unicell has quit IRC06:14
*** gouthamr has joined #openstack-meeting06:14
*** unicell has joined #openstack-meeting06:14
*** ekcs has joined #openstack-meeting06:17
*** guoshan has quit IRC06:19
*** ljxiash_ has quit IRC06:22
*** ljxiash has joined #openstack-meeting06:22
*** ekcs has quit IRC06:24
*** unicell1 has joined #openstack-meeting06:27
*** thorst_ has joined #openstack-meeting06:28
*** unicell has quit IRC06:29
*** nadya has joined #openstack-meeting06:30
*** nadya has quit IRC06:31
*** thorst_ has quit IRC06:33
*** guoshan has joined #openstack-meeting06:35
*** nkrinner_afk is now known as nkrinner06:40
*** ensyde has joined #openstack-meeting06:41
*** ensyde has left #openstack-meeting06:41
*** sridharg has joined #openstack-meeting06:43
*** bobmel has joined #openstack-meeting06:47
*** sdake has joined #openstack-meeting06:51
*** bobmel has quit IRC06:51
*** rbudden has quit IRC06:58
*** pcaruana has joined #openstack-meeting07:05
*** tesseract has joined #openstack-meeting07:09
*** yuval has joined #openstack-meeting07:11
*** ykatabam has quit IRC07:12
*** salv-orl_ has joined #openstack-meeting07:13
*** salv-orl_ has quit IRC07:13
*** salv-orlando has quit IRC07:16
*** lpetrut has joined #openstack-meeting07:16
*** rcernin has joined #openstack-meeting07:17
*** nadya has joined #openstack-meeting07:18
*** Julien-zte has joined #openstack-meeting07:23
*** jrobinson has quit IRC07:24
*** lijinghong has joined #openstack-meeting07:24
*** kjorgensen has joined #openstack-meeting07:24
*** rbartal has joined #openstack-meeting07:25
*** guoshan has quit IRC07:26
*** guoshan has joined #openstack-meeting07:27
*** X-dark_ has joined #openstack-meeting07:28
*** sdake_ has joined #openstack-meeting07:28
*** ad_rien_ has joined #openstack-meeting07:28
*** kjorgensen has quit IRC07:29
*** armax has joined #openstack-meeting07:30
*** sdake has quit IRC07:30
*** X-dark has quit IRC07:30
*** adisky_ has joined #openstack-meeting07:30
*** X-dark has joined #openstack-meeting07:30
*** X-dark_ has quit IRC07:32
*** nadya has quit IRC07:33
*** VW has quit IRC07:33
*** ad_rien_ has quit IRC07:33
*** rasca has joined #openstack-meeting07:35
*** anilvenkata has joined #openstack-meeting07:36
*** zhurong has joined #openstack-meeting07:37
*** e0ne has joined #openstack-meeting07:37
*** lijinghong has quit IRC07:39
*** yamahata has joined #openstack-meeting07:39
*** jchhatbar is now known as janki07:41
*** nadya has joined #openstack-meeting07:47
*** vishnoianil has joined #openstack-meeting07:50
*** Julien-zte has quit IRC07:51
*** gouthamr has quit IRC07:53
*** gouthamr has joined #openstack-meeting07:54
*** matrohon has joined #openstack-meeting07:55
*** Julien-zte has joined #openstack-meeting07:56
*** lpetrut has quit IRC07:58
*** gouthamr has quit IRC08:06
*** fzdarsky|afk has joined #openstack-meeting08:08
*** fzdarsky|afk is now known as fzdarsky08:09
*** armax has quit IRC08:13
*** ijw has quit IRC08:15
*** ad_rien_ has joined #openstack-meeting08:16
*** armax has joined #openstack-meeting08:22
*** khushbu_ has joined #openstack-meeting08:24
*** thorst_ has joined #openstack-meeting08:29
*** rasca has quit IRC08:32
*** thorst_ has quit IRC08:34
*** rasca has joined #openstack-meeting08:34
*** rasca has quit IRC08:40
*** rasca has joined #openstack-meeting08:47
*** janki has quit IRC08:52
*** sdake_ is now known as sdake08:54
*** jtomasek has quit IRC08:58
*** nadya has quit IRC09:03
*** jtomasek has joined #openstack-meeting09:05
*** janki has joined #openstack-meeting09:10
*** yamamoto has quit IRC09:14
*** armax has quit IRC09:14
*** bobmel has joined #openstack-meeting09:14
*** bvandenh has joined #openstack-meeting09:15
*** claudiub has joined #openstack-meeting09:16
*** lhx_ has joined #openstack-meeting09:18
*** bobmel has quit IRC09:18
*** lhx__ has joined #openstack-meeting09:20
*** lhx_ has quit IRC09:23
*** imcsk8 has quit IRC09:27
*** hashar has joined #openstack-meeting09:27
*** ad_rien_ has quit IRC09:29
*** ad_rien_ has joined #openstack-meeting09:30
*** jtomasek has quit IRC09:33
*** VW has joined #openstack-meeting09:33
*** yamahata has quit IRC09:34
*** iyamahat has joined #openstack-meeting09:34
*** toscalix has joined #openstack-meeting09:34
*** kjorgensen has joined #openstack-meeting09:36
*** jtomasek has joined #openstack-meeting09:36
*** VW has quit IRC09:38
*** Douhet has quit IRC09:38
*** Douhet has joined #openstack-meeting09:39
*** zhurong has quit IRC09:40
*** kjorgensen has quit IRC09:40
*** sdake_ has joined #openstack-meeting09:43
*** ricolin has joined #openstack-meeting09:43
*** sdake has quit IRC09:44
*** dbecker has joined #openstack-meeting09:45
*** Julien-zte has quit IRC09:46
*** lpetrut has joined #openstack-meeting09:48
*** neiljerram has joined #openstack-meeting09:52
*** amotoki has quit IRC09:55
*** yamamoto has joined #openstack-meeting09:59
*** nadya has joined #openstack-meeting10:01
*** khushbu_ has quit IRC10:01
*** yamamoto_ has joined #openstack-meeting10:02
*** sheel has joined #openstack-meeting10:03
*** egallen has joined #openstack-meeting10:03
*** yamamoto has quit IRC10:06
*** sdake_ has quit IRC10:06
*** epico has quit IRC10:07
*** yamamoto_ has quit IRC10:08
*** neiljerram has quit IRC10:12
*** yangyapeng has quit IRC10:12
*** iyamahat has quit IRC10:13
*** openstack has joined #openstack-meeting10:14
*** ChanServ sets mode: +o openstack10:14
*** sudipto_ has quit IRC10:16
*** sudipto has quit IRC10:16
*** kevinz has quit IRC10:17
*** ad_rien_ has left #openstack-meeting10:18
*** tiantian has quit IRC10:20
*** jchhatbar has joined #openstack-meeting10:23
*** janki has quit IRC10:25
*** thorst_ has joined #openstack-meeting10:30
*** gongysh has quit IRC10:31
*** jchhatbar_ has joined #openstack-meeting10:33
*** yamamoto has joined #openstack-meeting10:34
*** thorst_ has quit IRC10:35
*** jchhatbar has quit IRC10:36
*** guoshan has quit IRC10:41
*** neiljerram has joined #openstack-meeting10:43
*** rfolco has joined #openstack-meeting10:49
*** salv-orlando has joined #openstack-meeting10:52
*** salv-orlando has quit IRC10:57
*** mickeys has quit IRC10:57
*** salv-orlando has joined #openstack-meeting10:57
*** korzen has joined #openstack-meeting10:58
*** nadya has quit IRC10:59
*** sudipto has joined #openstack-meeting11:00
*** sudipto_ has joined #openstack-meeting11:01
*** Leo_ has quit IRC11:02
*** salv-orlando has quit IRC11:02
*** Leo_ has joined #openstack-meeting11:02
*** janki has joined #openstack-meeting11:02
*** jchhatbar_ has quit IRC11:03
*** bobmel has joined #openstack-meeting11:04
*** salv-orlando has joined #openstack-meeting11:04
*** armax has joined #openstack-meeting11:05
*** arxcruz has quit IRC11:15
*** amotoki has joined #openstack-meeting11:16
*** ansmith has joined #openstack-meeting11:16
*** sudipto_ has quit IRC11:16
*** sudipto has quit IRC11:16
*** salv-orlando has quit IRC11:19
*** salv-orlando has joined #openstack-meeting11:19
*** ijw has joined #openstack-meeting11:20
*** sambetts|afk is now known as sambetts11:20
*** Leo_ has quit IRC11:23
*** Leo_ has joined #openstack-meeting11:23
*** salv-orlando has quit IRC11:24
*** arxcruz has joined #openstack-meeting11:25
*** ijw has quit IRC11:26
*** armax has quit IRC11:26
*** lpetrut has quit IRC11:29
*** lpetrut has joined #openstack-meeting11:31
*** guoshan has joined #openstack-meeting11:42
*** ansmith has quit IRC11:44
*** gongysh has joined #openstack-meeting11:45
*** bobmel has quit IRC11:46
*** guoshan has quit IRC11:47
*** bobmel has joined #openstack-meeting11:47
*** Leo_ has quit IRC11:50
*** Leo_ has joined #openstack-meeting11:50
*** bobmel has quit IRC11:50
*** matrohon has quit IRC11:55
*** mdovgal has quit IRC11:55
*** ankur-gupta-f has quit IRC11:55
*** tdurakov has quit IRC11:55
*** grumpycatt has quit IRC11:55
*** sambetts has quit IRC11:55
*** zhhuabj has quit IRC11:55
*** dougshelley66 has quit IRC11:55
*** dteselkin has quit IRC11:55
*** jgrassle1 has quit IRC11:55
*** tlbr_ has quit IRC11:55
*** mtreinish has quit IRC11:55
*** sileht has quit IRC11:55
*** afazekas has quit IRC11:55
*** bauzas has quit IRC11:55
*** dansmith has quit IRC11:55
*** loquacities has quit IRC11:55
*** hughhalf has quit IRC11:55
*** kaisers has quit IRC11:55
*** htruta has quit IRC11:55
*** topol has quit IRC11:55
*** haukebruno has quit IRC11:55
*** rarora has quit IRC11:55
*** devananda has quit IRC11:55
*** smcginnis has quit IRC11:55
*** timrc has quit IRC11:55
*** dosaboy has quit IRC11:55
*** Anticimex has quit IRC11:55
*** dteselkin_ has joined #openstack-meeting11:55
*** jgrassler has joined #openstack-meeting11:55
*** htruta has joined #openstack-meeting11:55
*** afazekas has joined #openstack-meeting11:55
*** haukebruno has joined #openstack-meeting11:55
*** dosaboy has joined #openstack-meeting11:55
*** hughhalf has joined #openstack-meeting11:55
*** sambetts_ has joined #openstack-meeting11:55
*** smcginnis has joined #openstack-meeting11:55
*** topol_ has joined #openstack-meeting11:55
*** dougshelley66 has joined #openstack-meeting11:55
*** timrc has joined #openstack-meeting11:55
*** bauzas has joined #openstack-meeting11:56
*** loquacities has joined #openstack-meeting11:56
*** kaisers has joined #openstack-meeting11:56
*** mdovgal has joined #openstack-meeting11:56
*** matrohon has joined #openstack-meeting11:56
*** zhhuabj has joined #openstack-meeting11:56
*** dansmith has joined #openstack-meeting11:56
*** devananda has joined #openstack-meeting11:56
*** mtreinish has joined #openstack-meeting11:56
*** sileht has joined #openstack-meeting11:56
*** dansmith is now known as Guest4110011:56
*** armax has joined #openstack-meeting11:56
*** sambetts_ is now known as sambetts11:56
*** tdurakov has joined #openstack-meeting11:56
*** ankur-gupta-f has joined #openstack-meeting11:56
*** tlbr has joined #openstack-meeting11:57
*** bobmel has joined #openstack-meeting11:58
*** mickeys has joined #openstack-meeting11:58
*** serverascode has quit IRC11:59
*** caiobrentano has left #openstack-meeting11:59
*** serverascode has joined #openstack-meeting12:01
*** mickeys has quit IRC12:03
*** jkilpatr has joined #openstack-meeting12:04
*** JoseMello has joined #openstack-meeting12:05
*** kevinz has joined #openstack-meeting12:05
*** hashar is now known as hasharLunch12:10
*** Leo_ has quit IRC12:10
*** rarora has joined #openstack-meeting12:11
*** Leo_ has joined #openstack-meeting12:11
*** links has quit IRC12:13
*** rtheis has joined #openstack-meeting12:14
*** gongysh has quit IRC12:14
*** Leo_ has quit IRC12:18
*** Leo_ has joined #openstack-meeting12:18
*** bkopilov has quit IRC12:20
*** nadya has joined #openstack-meeting12:21
*** ijw has joined #openstack-meeting12:21
*** hwoarang has quit IRC12:22
*** hwoarang has joined #openstack-meeting12:22
*** links has joined #openstack-meeting12:25
*** yangyapeng has joined #openstack-meeting12:26
*** ijw has quit IRC12:27
*** hwoarang_ has joined #openstack-meeting12:28
*** hwoarang has quit IRC12:31
*** ljxiash has quit IRC12:31
*** ljxiash has joined #openstack-meeting12:32
*** yamamoto has quit IRC12:36
*** ljxiash has quit IRC12:36
*** yamamoto has joined #openstack-meeting12:38
*** Leo_ has quit IRC12:38
*** Leo_ has joined #openstack-meeting12:39
*** nadya has quit IRC12:46
*** thorst_ has joined #openstack-meeting12:46
*** sdague has joined #openstack-meeting12:51
*** janki has quit IRC12:51
*** yamamoto has quit IRC12:52
*** sdague_ has quit IRC12:54
*** ljxiash has joined #openstack-meeting12:54
*** armax has quit IRC12:54
*** links has quit IRC12:55
*** sdague_ has joined #openstack-meeting12:56
*** sdague_ has quit IRC12:56
*** pradk has joined #openstack-meeting12:58
*** ljxiash has quit IRC12:59
*** mickeys has joined #openstack-meeting12:59
*** askb has quit IRC12:59
*** jftalta has joined #openstack-meeting13:00
ianychoi#startmeeting OpenStack I18n Meeting13:00
openstackMeeting started Thu Jan  5 13:00:48 2017 UTC and is due to finish in 60 minutes.  The chair is ianychoi. 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: OpenStack I18n Meeting)"13:00
openstackThe meeting name has been set to 'openstack_i18n_meeting'13:00
ianychoiHello jftalta!13:01
jftaltaHello ianychoi !13:01
jftaltaall my best for 2017 !13:02
*** dprince has joined #openstack-meeting13:02
ianychoi2017 has already come !13:02
*** eumel8 has joined #openstack-meeting13:02
eumel8morning!13:02
ianychoiHi eumel8 !13:02
jftaltaHi eumel813:02
eumel82 minutes late13:03
jftalta;)13:03
*** mickeys has quit IRC13:03
ianychoiThat's fine :) Okay.. let's first start with general meeting logistics so that we can have more time on discussion13:03
ianychoi#topic Review on last meeting actions13:04
*** openstack changes topic to "Review on last meeting actions (Meeting topic: OpenStack I18n Meeting)"13:04
ianychoi#link http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/openstack_i18n_meeting.2016-12-22-13.03.html13:04
*** sudipto_ has joined #openstack-meeting13:04
*** sudipto has joined #openstack-meeting13:04
ianychoiOne action from ianychoi and jftalta was to apply themes on French landing page after current patch is merged. I will start to do after this week13:04
jftaltaOk. The french version of Mitaka installation guide is on line, indeed.13:06
ianychoijftalta, that's nice!13:06
ianychoi#topic Zanata upgrade status13:06
*** openstack changes topic to "Zanata upgrade status (Meeting topic: OpenStack I18n Meeting)"13:06
ianychoi#link https://etherpad.openstack.org/p/i18n-zanata-test-for-translate-dev13:07
jftalta#link http://docs.openstack.org/fr/13:07
ianychoijftalta, helped to test #13 and 15. Thanks a lot!13:07
*** links has joined #openstack-meeting13:07
ianychoi#link http://lists.openstack.org/pipermail/openstack-i18n/2016-December/002632.html13:07
eumel8what is work status O?13:09
ianychoiSteve Kowalik suggested good test items. Although I am not currently familiar with some of the parts too much, I will take care of this.13:09
ianychoieumel8, 'O' means that test has performed and it works well!13:09
eumel8ah, very good13:09
*** hasharLunch is now known as hashar13:09
amotokihi, happy new year13:10
ianychoiamotoki, hello!13:10
jftaltaHi amotoki !13:11
eumel8hi amotiki, you too13:11
amotokiglad to hear that French team has a new landing page :)13:11
*** ansmith has joined #openstack-meeting13:12
eumel8ianychoi: something to help? or it seems all tests pass through13:12
ianychoiAfter Zanata test, then I will discuss with clarkb to upgrade to newer version of Zanata13:12
ianychoieumel8, two parts are mainly remained: 1) po file import & export and 2) seeing Zanata raw log messages for warning and/or errors13:13
jftaltaNew Zanata version witj glossary management feature !13:13
jftalta*with13:13
ianychoiFor 1), I am finding how I am able to use current infra scripts with translate-dev.o.o and for 2), Alex Eng said that he will be able to help it13:13
eumel8ok13:14
ianychoi#link https://translate.zanata.org/13:14
amotokiUpgrading zanata sounds nice. however let me raise one question.13:14
amotokithe soft string-freeze is now two week away.13:14
*** nadya has joined #openstack-meeting13:14
amotokido we have enough time to test a new translation infra?13:14
ianychoiAnd.. this from Zanata team has 3.9.6 version, which may be a good reference13:15
ianychoiamotoki, I really wanted to incorporate newer version of Zanata before Soft StringFreeze. However, it seems that we do not have enough time..13:15
amotokiI might be conservative. I am playing such role :)13:16
ianychoiThat's fine :) Now I do not want to change Zanata version in translate.o.o within Pike cycle13:17
ianychoiSorry Ocata cycle13:17
amotokiwe have three weeks before the final RC week. we can be optimistic :)13:17
amotoki#link https://releases.openstack.org/ocata/schedule.html13:18
ianychoiIt actually depends on how we test completely with newer version of Zanata and Xenial..13:18
ianychoiamotoki, thanks a lot for such remainder13:18
ianychoiGood news is that clarkb is kindly waiting for current test results to upgrade newer version of Zanata13:19
ianychoi(I have seen his IRC meeting on infra channel yesterday night - UTC based)13:19
ianychois/meeting/message13:19
amotokiianychoi: is there a way to revert the translate site to the current version if we have some critical problem?13:20
amotokiif we have a feasible way, IMHO it sounds good to move it forward.13:20
ianychoiamotoki, oh good question. Since Zanata installation is based on Puppet, I think it is possible but we need to check database side.13:21
*** prateek has quit IRC13:21
amotokiwhat in my mind is our translation memory and related stuff.13:21
ianychoieumel8, could you look at how database backup is done in puppet-zanata?13:22
*** pradk has quit IRC13:23
amotokiand our comments and history on Zanata. I am not sure that puppet installation can help it.13:23
*** ijw has joined #openstack-meeting13:23
ianychoiI need to figure out 1) which database configuration is used in translate-dev and translate.o.o and 2) how database can be backed up and restored from..13:24
amotokiI think nobody knows it now. I believe it is worth checked before the upgrade!13:24
amotokiianychoi: totally agree13:24
*** pradk has joined #openstack-meeting13:24
ianychoiOkay, then I will ask with infra team members thanks a lot, amotoki !13:24
ianychoi#action ianychoi will figure out how Zanata database can be backed up and restored from old backup(s) regarding Zanata upgrade13:25
*** Anticimex has joined #openstack-meeting13:25
amotokianyway we don't lose all. we have PO files in our git repos.13:25
*** ayogi has quit IRC13:25
ianychoiamotoki, thanks a lot for this important point!13:25
ianychoiThen.. moving on the next topic?13:26
jftaltaok for me13:26
ianychoi#topic Pike PTG13:26
*** openstack changes topic to "Pike PTG (Meeting topic: OpenStack I18n Meeting)"13:26
ianychoi#link http://www.openstack.org/ptg13:27
eumel8couldn't see anything regarding backups: https://git.openstack.org/cgit/openstack-infra/system-config/tree/modules/openstack_project/manifests/translate.pp13:27
ianychoieumel8, thanks!13:27
eumel8normaly it would be configured in mysql class13:27
ianychoiI am planning to go to PTG and I will usually stay in Doc team's room but I will also go to infra, Horizon, and other team's rooms13:28
eumel8mysql::backup - something like that13:28
*** ijw has quit IRC13:28
amotokiianychoi: do you mean you stay Atlanta on Mon and Tue?13:28
ianychoiSo now I will propose to specify "Documentation / I18n" in PTG homepage, although I need to confirm again with Lana, Docs team PTL.13:29
eumel8ianychoi: what's with your PTL nomination? :-)13:29
ianychoiamotoki, Mon and Tue are definitely and I am now arranging my schedule up to Wed and Thu13:29
ianychoieumel8, PTL nomination for Pike cycle?13:30
eumel8sure13:30
amotokiI will be there but perhaps I will join OSC and horizon on Mon/Tue and neutron on Wed-Fri.13:30
ianychoieumel8, now I want to do also with Pike cycle, if you and other members agree and nominate me :)13:31
ianychoiamotoki, oh nice! Let's meet in Atlanta then.. although we each may be busy :)13:32
amotokiianychoi: you can nominate yourself anyway though :)13:32
jftalta+113:32
ianychoieumel8, but I think it is difficult for me to run for next Q-cycle13:32
eumel8ianychoi: we count on you and I think you have already decided this for you13:33
*** pradk has quit IRC13:33
ianychoisince I am supposed to server Korean user group leader up to next year. Last December, there was an election in Korean community13:33
ianychoiSo I think it is difficult for me to run for next Q-cycle13:34
*** liusheng has quit IRC13:34
*** d0ugal has quit IRC13:34
amotokiit sounds interesting too :)13:34
eumel8so, we have a plan and can work through the PTG13:34
*** tommylikehu_ has joined #openstack-meeting13:35
eumel8ianychoi: you have our support all the time :)13:35
ianychoiFor me, P cycle is relatively short and I want to make a good transition with upcoming Forum13:35
*** d0ugal has joined #openstack-meeting13:35
ianychoieumel8, thanks a lot :)13:35
*** tommylikehu_ has quit IRC13:35
ianychoi#link http://lists.openstack.org/pipermail/openstack-dev/2017-January/109658.html13:35
ianychoiThe link is what I wrote and shared with you today13:35
*** tommylikehu_ has joined #openstack-meeting13:35
eumel8yeah13:36
ianychoiIn my opinion, our voice in this transition period (Ocata and Pike cycle) would be so important13:36
*** tommylikehu_ has left #openstack-meeting13:36
-amotoki- personally cannot be a translator for O cycle but will help the community from other sides13:36
*** Julien-zte has joined #openstack-meeting13:37
ianychoiamotoki, I appreciate your kind help from various sides all the time13:37
eumel8ianychoi: you have still some ideas for the Forum?13:37
amotokiI can leave a comment on the forum at Boston and later, but I hope more feedback from translators!13:38
ianychoiOne idea is to propose extra AUCs for translators who highly influence with local communities13:38
amotokiI have many hats and mainly my hat is a developer, so more global inputs would be appreciated.13:38
jftaltaamotoki: what kind of inputs do you need ?13:39
amotokijftalta: inputs on a topic ianychoi raised at the above mail13:40
ianychoiAUCs and ATCs are different. For I18n, currently translating more than 300 words within latest two cycles are regarded as ATCs. However, some aspects for translators may be related with AUCs13:40
amotokiwe need to gather feedbacks from the i18n/l10n communities and input them to the foundation so that the summit will be more comfortable and useful for translators.13:42
jftaltaDon't you think that 300 words is a too low limit ?13:42
amotokithat's the background of this discussion.13:42
ianychoijftalta, I agree with this. Which number of words would be appropriate?13:43
amotokiIMHO 300 words is a reasonable threshold for ATC, but I am not sure it is reasonable for AUC.13:43
amotokiBased on my impression, folks recognized as AUC contributed more (in the past)13:44
*** abalutoiu has joined #openstack-meeting13:44
amotokiof course the criteria of AUC is under discussion (I think(13:44
ianychoiFor developers, ATCs are regarded with at least one commit within latest 2 release cycles. 300 words would be too small comparing to 1 commit?13:45
*** number80 has quit IRC13:45
ianychoiThe criteria of ATC is related with question.13:45
jftaltaReviews also matter, not only translations13:45
ianychoi#link http://lists.openstack.org/pipermail/openstack-docs/2016-November/009294.html13:46
amotokijftalta: really good point!13:46
ianychoiAnd this is for AUC criteria, then IMO 300 words may be too small..13:47
jftaltaianychoi: +113:47
persiaReviews don't grant ATC (which has been a discussion point about ATCs in the past).  Some software commits are lots less than 300 words.  Rather than mirroring other processes, I strongly recommend selecting new ones that include anyone who should be considered a translator.13:47
ianychoijftalta, then 300 words for translation or review would be a good idea for ATC recognition?13:47
amotokimy vote is more words for reviews, e.g. 600 or 1000 words13:48
ianychoipersia, Thanks. I understand your point but some translation review may change all the sentences..13:48
amotokibut a bigger question is how to evaluate the number of reviews with quality13:48
*** bobh has joined #openstack-meeting13:48
*** tovin07 has joined #openstack-meeting13:48
ianychoijftalta, amotoki : question: how review quality will be measured?13:49
ianychoior at least translation quality?13:49
amotokipersia: good point. so far "review" is not a requirement of ATC. IMO it is better to follow the other criteria applied to other projects.13:50
jftaltaianychoi: quality ? no idea...13:50
ianychoijftalta, Haha neither from me13:50
amotokiianychoi: it is a difficult question. JP community has a difficulty on how to evaluate potential "reviewers"......13:51
*** pradk has joined #openstack-meeting13:51
*** baoli has joined #openstack-meeting13:51
amotokiit is not easy to share/see review comments of others on the current Zanata platform.13:51
*** jamesdenton has joined #openstack-meeting13:52
ianychoiBy the way, when I see https://releases.openstack.org/ocata/schedule.html amotoki shared,13:52
ianychoiTomorrow is the deadline for extra ATC13:52
amotokicore reviewers of other projects can see other reviewers' comments on the gerrit, but it is not easy on our Zanata :(13:52
*** tovin07 has quit IRC13:53
ianychoiI will take care of proposing extra ATCs by seeing Zanata statistics13:53
amotokiianychoi: I think it is better to follow the conventions on the extra ATC for Ocata.13:53
*** cdelatte has joined #openstack-meeting13:53
amotokitime check: 5 minites left13:54
ianychoiamotoki, yep following the current logistics for proposing extra ATCs would be better now..13:54
ianychoi#topic Discussing core reviewers with language teams13:54
*** openstack changes topic to "Discussing core reviewers with language teams (Meeting topic: OpenStack I18n Meeting)"13:54
*** jprovazn has joined #openstack-meeting13:54
jftaltatime flies13:55
ianychoiI wanted to raise this topic but I will postpone it to the next week13:55
ianychoi#topic13:55
*** openstack changes topic to " (Meeting topic: OpenStack I18n Meeting)"13:55
ianychoi#topic Asking for reviewing i18n-specs13:55
*** openstack changes topic to "Asking for reviewing i18n-specs (Meeting topic: OpenStack I18n Meeting)"13:55
*** yamamoto has joined #openstack-meeting13:55
ianychoi#link https://review.openstack.org/#/q/project:openstack/i18n-specs13:55
ianychoiPlease also review i18n-specs :)13:55
*** salv-orlando has joined #openstack-meeting13:56
amotokihow about sending topics proposed in i18n-specs to the i18n ML?13:56
*** nadya has quit IRC13:56
ianychoiAlthough my work is a little bit slow, I am polishing i18n-specs to well display in specs.openstack.org13:56
ianychoiamotoki, can I see some examples how proposed topics are sent to mailing lists?13:57
ianychoifrom other projects maybe?13:57
amotokiianychoi: I don't know how to automate it. I think we need to send them manually13:57
*** qwebirc353 has joined #openstack-meeting13:57
*** sankarshan_away is now known as sankarshan13:57
ianychoiamotoki, aha I see13:57
amotoki:)13:58
*** qwebirc353 has quit IRC13:58
ianychoiThen the next step for i18n-specs will be to fill out with content: https://etherpad.openstack.org/p/i18n-specs-use-cases would be examples13:58
*** fguillot has joined #openstack-meeting13:59
ianychoiOkay.. no time is left..13:59
ianychoiIf you have more things to be discussed, please call me in #openstack-i18n channel.13:59
ianychoiThanks a lot today, jftalta , eumel8 , and amotoki !13:59
eumel8thx, bye :)14:00
*** mickeys has joined #openstack-meeting14:00
ianychoi#endmeeting14:00
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"14:00
openstackMeeting ended Thu Jan  5 14:00:05 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
jftaltathx, bye14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/openstack_i18n_meeting.2017-01-05-13.00.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/openstack_i18n_meeting.2017-01-05-13.00.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/openstack_i18n_meeting.2017-01-05-13.00.log.html14:00
*** eumel8 has quit IRC14:00
*** jftalta has quit IRC14:00
amotokiianychoi and all: thanks!14:00
*** rfolco has quit IRC14:01
*** number80 has joined #openstack-meeting14:01
*** links has quit IRC14:02
*** number80 has quit IRC14:03
*** number80 has joined #openstack-meeting14:04
*** ykatabam has joined #openstack-meeting14:04
*** mickeys has quit IRC14:05
*** spzala has joined #openstack-meeting14:09
*** bkopilov has joined #openstack-meeting14:10
*** yamamoto has quit IRC14:10
*** efried has joined #openstack-meeting14:10
*** ricolin has quit IRC14:12
*** pkoniszewski has quit IRC14:15
*** luzC has quit IRC14:15
*** luzC has joined #openstack-meeting14:15
*** pkoniszewski has joined #openstack-meeting14:15
*** baoli has quit IRC14:17
*** baoli has joined #openstack-meeting14:17
*** hoangcx has joined #openstack-meeting14:17
*** xyang1 has joined #openstack-meeting14:18
*** ijw has joined #openstack-meeting14:24
*** yamamoto has joined #openstack-meeting14:27
*** ijw has quit IRC14:30
*** lblanchard has joined #openstack-meeting14:33
*** eharney has joined #openstack-meeting14:37
*** VW has joined #openstack-meeting14:38
*** efried has quit IRC14:41
*** lamt has joined #openstack-meeting14:42
*** efried_ has joined #openstack-meeting14:44
*** saju_m has joined #openstack-meeting14:45
*** mriedem has joined #openstack-meeting14:45
*** thorst_ is now known as thorst_afk14:50
*** salv-orlando has quit IRC14:50
*** hongbin has joined #openstack-meeting14:51
*** efried_ has quit IRC14:52
*** nadya has joined #openstack-meeting14:52
*** efried has joined #openstack-meeting14:52
*** sankarshan is now known as sankarshan_away14:57
*** absubram has joined #openstack-meeting14:58
*** mickeys has joined #openstack-meeting15:00
*** spotz_zzz is now known as spotz_15:01
*** anilvenkata has quit IRC15:02
*** cleong has joined #openstack-meeting15:03
*** bobmel has quit IRC15:05
*** mickeys has quit IRC15:06
*** edtubill has joined #openstack-meeting15:10
*** Leo_ has quit IRC15:12
*** prateek has joined #openstack-meeting15:13
*** d34dh0r53 has quit IRC15:14
*** d34dh0r53 has joined #openstack-meeting15:14
*** Guest41100 is now known as dansmith15:15
*** hashar has quit IRC15:15
*** lamt has quit IRC15:15
*** dansmith is now known as Guest5735515:15
*** hashar has joined #openstack-meeting15:16
*** lamt has joined #openstack-meeting15:16
*** Guest57355 is now known as dansmith15:16
*** ljxiash has joined #openstack-meeting15:16
*** kevinz has quit IRC15:17
*** Julien-zte has quit IRC15:18
*** spzala has quit IRC15:19
*** sdake has joined #openstack-meeting15:20
*** Julien-zte has joined #openstack-meeting15:20
*** Julien-zte has quit IRC15:20
*** bobmel has joined #openstack-meeting15:21
*** Julien-zte has joined #openstack-meeting15:22
*** Julien-zte has quit IRC15:22
*** sridharg has quit IRC15:22
*** tdasilva- is now known as tdasilva15:23
*** sdake_ has joined #openstack-meeting15:23
*** zz_dimtruck is now known as dimtruck15:23
*** yuval has quit IRC15:24
*** prateek has quit IRC15:24
*** imcsk8 has joined #openstack-meeting15:24
*** fnaval has joined #openstack-meeting15:25
*** bobmel has quit IRC15:25
*** sdake has quit IRC15:25
*** joadavis has joined #openstack-meeting15:26
*** ijw has joined #openstack-meeting15:26
*** rbartal has quit IRC15:27
*** fnaval_ has joined #openstack-meeting15:27
*** jaugustine has joined #openstack-meeting15:28
*** fnaval__ has joined #openstack-meeting15:28
*** fnaval__ has quit IRC15:28
*** Cibo_ has quit IRC15:28
*** rfolco has joined #openstack-meeting15:29
*** prateek has joined #openstack-meeting15:30
*** fnaval has quit IRC15:30
*** bobmel has joined #openstack-meeting15:30
*** fnaval has joined #openstack-meeting15:31
*** ijw has quit IRC15:31
*** prateek has quit IRC15:31
*** saju_m has quit IRC15:31
*** prateek has joined #openstack-meeting15:32
*** nadya has quit IRC15:32
*** fnaval_ has quit IRC15:33
*** salv-orlando has joined #openstack-meeting15:34
*** jaypipes has joined #openstack-meeting15:35
*** tonytan4ever has joined #openstack-meeting15:37
*** d0ugal has quit IRC15:38
*** nadya has joined #openstack-meeting15:40
*** d0ugal has joined #openstack-meeting15:41
*** nadya has quit IRC15:44
*** guoshan has joined #openstack-meeting15:46
*** VW has quit IRC15:49
*** reedip_outofmemo has joined #openstack-meeting15:49
*** guoshan has quit IRC15:50
*** spzala has joined #openstack-meeting15:52
*** bobmel has quit IRC15:53
*** spzala has quit IRC15:53
*** spzala has joined #openstack-meeting15:53
*** salv-orl_ has joined #openstack-meeting15:53
*** thorst_afk is now known as thorst_15:53
*** VW has joined #openstack-meeting15:54
*** ekcs has joined #openstack-meeting15:54
*** salv-orlando has quit IRC15:56
*** nkrinner is now known as nkrinner_afk15:59
*** ljxiash has quit IRC16:00
*** bobh has quit IRC16:01
*** sdake_ has quit IRC16:02
*** sdake has joined #openstack-meeting16:03
*** VW_ has joined #openstack-meeting16:03
*** Leom has joined #openstack-meeting16:03
*** mickeys has joined #openstack-meeting16:03
*** VW_ has quit IRC16:05
*** VW_ has joined #openstack-meeting16:05
*** ijw has joined #openstack-meeting16:05
*** Leo_ has joined #openstack-meeting16:06
*** VW has quit IRC16:06
*** rcernin has quit IRC16:07
*** mickeys has quit IRC16:08
*** Leom has quit IRC16:08
*** ijw has quit IRC16:10
*** TxGirlGeek has joined #openstack-meeting16:10
*** csomerville has quit IRC16:13
*** csomerville has joined #openstack-meeting16:13
*** VW_ has quit IRC16:14
*** VW has joined #openstack-meeting16:15
*** yamamoto has quit IRC16:16
*** sdake has quit IRC16:16
*** lhx__ has quit IRC16:17
*** lhx__ has joined #openstack-meeting16:19
*** tesseract has quit IRC16:21
*** VW_ has joined #openstack-meeting16:22
*** VW has quit IRC16:23
*** tobybot11 has joined #openstack-meeting16:23
*** myoung|afk is now known as myoung16:23
*** hoangcx has quit IRC16:29
*** kjorgensen has joined #openstack-meeting16:29
*** baoli has quit IRC16:31
*** jprovazn has quit IRC16:32
*** hwoarang_ is now known as hwoarang16:36
*** weshay is now known as weshay_errand16:37
*** jungleboyj has joined #openstack-meeting16:37
*** prateek_ has joined #openstack-meeting16:46
*** gouthamr has joined #openstack-meeting16:46
*** unicell1 has quit IRC16:47
*** artom has joined #openstack-meeting16:49
*** prateek has quit IRC16:49
*** iyamahat has joined #openstack-meeting16:49
*** VW_ has quit IRC16:51
*** e0ne has quit IRC16:52
*** VW has joined #openstack-meeting16:52
*** sdake has joined #openstack-meeting16:54
*** amotoki has quit IRC16:55
*** pcaruana has quit IRC16:58
*** jordanP has joined #openstack-meeting16:59
*** lhx__ has quit IRC16:59
*** matrohon has quit IRC17:00
oomichi#startmeeting qa17:00
openstackMeeting started Thu Jan  5 17:00:52 2017 UTC and is due to finish in 60 minutes.  The chair is oomichi. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: qa)"17:00
openstackThe meeting name has been set to 'qa'17:00
oomichihi who join the meeting today?17:01
*** rbudden has joined #openstack-meeting17:01
*** singlethink has joined #openstack-meeting17:01
*** tobybot11 has quit IRC17:01
jordanPhi17:01
*** ijw has joined #openstack-meeting17:01
jordanPmtreinish, andreaf gmann you here ?17:02
*** spzala has quit IRC17:02
*** bobh has joined #openstack-meeting17:02
*** iyamahat has quit IRC17:02
oomichiping mtreinish, andreaf, masayukig17:02
*** spzala has joined #openstack-meeting17:02
mtreinisho/17:02
oomichiok, lets start meeting17:03
oomichi#link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_January_5th_2017_.280900_UTC.2917:03
oomichi^^^ is today agenda17:03
oomichi#topic PTG17:03
*** openstack changes topic to "PTG (Meeting topic: qa)"17:03
jordanPquestion about the PTG, should we expect design sessions or coding/handson session ?17:03
oomichijordanP: I feel that is design session17:04
oomichiaccording to https://www.openstack.org/ptg/17:04
*** spzala_ has joined #openstack-meeting17:04
oomichi"project teams will meet in person to discuss priorities for the upcoming cycle, iterate quickly on solutions for complex issues, and make fast progress on critical items."17:04
jordanPok, but that won't last a full day, we have only 3 proposed "sessions" now17:04
*** mickeys has joined #openstack-meeting17:04
mtreinishoomichi: well it is free form. We get a room, so it's up to us to decide the format17:05
oomichijordanP: yeah, I see the 3, thanks for proposing17:05
mtreinishoomichi: have you put the etherpad on the ml?17:05
jordanPyes, I've seen it on the ML17:05
oomichimtreinish: can we arrange the slots as we like17:05
oomichi?17:05
mtreinishoomichi: there are no slots, we get a room for a block of time17:05
oomichimtreinish: yeah, I have posted it on ml17:05
oomichimtreinish: that means we can use a room for a single QA project 2 full days?17:06
clarkbone thing I was thinking about was potentially setting aside time for infra/qa to work with other projects on dealign with gate failures, reading logs, using elastic-recheck etc17:06
mtreinishok, I must ahve just missed it because of my time off, or the holidays17:06
mtreinishclarkb: yeah that's a good idea17:06
oomichiclarkb: cool17:07
mtreinishclarkb: that was part of the reason why it's horizontal teams only the first couple of days17:07
clarkbmtreinish: yup17:07
mtreinishto try and get more people involved in stuff :)17:07
*** spzala has quit IRC17:07
*** bobh has quit IRC17:08
oomichiyes, it is nice to write ideas for involving17:08
*** spzala_ has quit IRC17:08
jordanPfor Tempest, I would like to spend most of my time coding with you. But I am open for discussions too :)17:08
oomichimtreinish: again: we can use a room for a single QA project 2 full days?17:08
*** mickeys has quit IRC17:09
clarkboomichi: that is my understanding17:09
oomichijordanP: TBH, +1 for coding :)17:09
clarkb(I don't know if it will be one team to one room though, but you should have space for that 2 days dedicated to qa)17:09
oomichiclarkb: I got it, so we can manage how to use the room as we can17:09
oomichithat is nice :)17:10
jordanP*as we want :)17:10
oomichiyes :)17:10
*** arxcruz has quit IRC17:10
oomichiok, are there another topic related to PTG?17:10
oomichiok, lets move on17:11
mtreinishoomichi: I think it might be worthwhile to ask on the ML about specifics for topics about getting involved17:11
mtreinishlike are there things people would like to learn about qa and/or infra17:11
mtreinishjust to collect a slightly different set of topics people might be interested in17:12
oomichimtreinish: ah, that seems a general session a little bit like the summit?17:12
*** korzen has quit IRC17:12
jordanPyeah, but smaller and more interactive17:12
mtreinishjordanP: right17:13
oomichifor learning qa/infra in general session, not design session17:13
*** sambetts is now known as sambetts|afk17:13
mtreinishoomichi: I was thinking along the same lines as clarkb, part of the reason for having 2 dedicated days with horizontal teams was to get more people involved17:13
mtreinishso getting some idea of what people would like to learn might give us some more ideas on how to organize the ptg time17:13
oomichimtreinish: that would be productive17:14
jordanPok:17:15
oomichiok, please write some ideas on the etherpad to do that and I will send a mail to get more attention17:15
jordanP#action oomichi to ask on the ML if people are interested in some general qa/infra sessions17:15
jordanPsomething along those lines :)17:15
oomichijordanP: yeah, that is my homework17:16
jordanPlet's move on17:16
*** yamamoto has joined #openstack-meeting17:16
oomichiis it ok to move on ?17:16
oomichigot it17:16
oomichi#topic Specs Reviews17:16
*** openstack changes topic to "Specs Reviews (Meeting topic: qa)"17:16
oomichismall number of specs on #link https://review.openstack.org/#/q/status:open+project:openstack/qa-specs,n,z17:17
*** yamahata has joined #openstack-meeting17:17
*** nadya has joined #openstack-meeting17:17
oomichiHA spec seems needed to be updated17:17
*** dbecker has quit IRC17:18
*** tonytan4ever has quit IRC17:18
oomichiresource one also needs to be updated, but I'd like to skip it on this Ocata cycle due to less time17:18
*** tonytan4ever has joined #openstack-meeting17:18
mtreinishoomichi: well we can prod andreaf some more to still revise it17:19
mtreinishhaving it in good shape before the ptg would be best I think17:19
oomichimtreinish: now the resource spec is owned by me, and yeah it is nice to prepare for PTG before17:19
mtreinishoomichi: ah, ok. I forgot you took it over17:20
oomichiyeah, it is easy to forget that due to different owner :)17:20
oomichiincluding me17:21
oomichiok, lets move on if we dont have more items about spec17:21
oomichi#topic Tempest17:22
*** openstack changes topic to "Tempest (Meeting topic: qa)"17:22
oomichiThe bug triage seems in very good progress from https://github.com/oomichi/bug-counter#current-graph17:22
oomichinow the bug number is less 15017:23
*** tonytan4ever has quit IRC17:23
*** tonytan4ever has joined #openstack-meeting17:23
oomichiThis week bug triage is done by chandankumar17:24
*** prateek_ has quit IRC17:24
oomichibut he doesnt seem online today17:24
*** sdake has quit IRC17:24
mtreinishheh, someone was busy right before the holidays. That's quite the drop off17:24
oomichimtreinish: yep, that is :)17:24
oomichido we have topics about Tempest today?17:25
jordanPnope, but I'd like some reviews on https://review.openstack.org/#/c/413739/17:26
jordanPPort object_storage tests to Py3.17:26
jordanPnothing urgent though17:26
*** yamamoto has quit IRC17:26
mtreinish#link https://review.openstack.org/#/c/413739/17:26
mtreinishjordanP: cool, I'll take a look17:27
*** annegentle has joined #openstack-meeting17:27
mtreinishjordanP: so you're running tempest with py3 locally?17:27
oomichijordanP: I got it, btw do we run Tempest on the gate with both py3 and py2?17:27
mtreinishoomichi: only in unit tests17:27
jordanPmtreinish, yeah, I did run tempest on py3 locally17:28
mtreinishoomichi: tempest runs are still only py217:28
jordanPresults are encouraging17:28
mtreinishjordanP: oh, cool. It's been a while since I last tried that, it wasn't in the best shape back then17:28
jordanPI say we are very close to having it running fine, at least locally17:28
oomichiI did breke some gate before due to this kind  of patches on Nova side, so I'd like to confirm that17:28
mtreinishoomichi: dims is working on getting devstack running in the gate with py317:29
jordanPI am running tempest wirh py3, all other services running Py217:29
mtreinishalthough that technically isn't a blocker for running tempest under py317:29
oomichijordanP: oh, awesome.17:29
*** sdake has joined #openstack-meeting17:29
mtreinishit does make it easier from a gating perspective to just have a global flag USE_PYTHON3 in devstack17:29
oomichimtreinish: that is good work17:29
oomichiok, I will review it later anyways17:30
oomichilets move on if we don't have more topics related to Tempest today17:31
oomichi#topic DevStack + Grenade17:32
*** openstack changes topic to "DevStack + Grenade (Meeting topic: qa)"17:32
oomichido we have disussion items about them?17:32
oomichithere are a lot of +2ed patches on the devstack queue anyways17:33
oomichi#link https://review.openstack.org/#/q/project:openstack-dev/devstack+status:open17:33
jordanPyep17:33
oomichijordanP: ah, you are deprecating a lot of Tempest options and that would require Devstack patches also for removing the options17:34
*** anilvenkata has joined #openstack-meeting17:34
jordanPyeah, yeah, devstack changes have been proposed already17:35
mtreinishoomichi: there is the py3 work dims was doing that I mentioned earlier17:35
oomichijordanP: cool, I will see them17:35
mtreinishbut I think all the patches he had up for that are already approved17:35
oomichimtreinish: https://review.openstack.org/#/c/416064/ is ?17:36
mtreinishoomichi: that's the latest patch yes17:36
mtreinishthere were others that I think have already merged17:36
oomichimtreinish: are there patches for Tempest?17:37
*** lpetrut has quit IRC17:37
mtreinishnot that I've seen17:37
mtreinishwell besides jordanP's from earlier :)17:38
*** iyamahat has joined #openstack-meeting17:38
oomichihehe, I got it17:38
oomichiok, lets move on to the next topic17:39
oomichi#topic openstack-health17:39
*** openstack changes topic to "openstack-health (Meeting topic: qa)"17:39
jordanPthere have been a mass +2 on devstack changes17:39
*** unicell has joined #openstack-meeting17:40
*** matrohon has joined #openstack-meeting17:40
*** unicell has quit IRC17:40
oomichijordanP: yeah, thare is a lot17:40
*** unicell has joined #openstack-meeting17:40
mtreinishI have nothing on openstack-health this week. I think things have been pretty quiet on it lately17:41
oomichimtreinish: yeah there are not so many active patches today on https://review.openstack.org/#/q/project:openstack/openstack-health+status:open17:41
oomichiok, lets move on17:41
oomichi#topic Critical Reviews17:41
*** openstack changes topic to "Critical Reviews (Meeting topic: qa)"17:41
oomichido we have patches needed to be reviewed asap today?17:42
oomichifrom my side, I don't have17:43
jordanPthere was https://review.openstack.org/#/c/417009/ earlier17:43
jordanPwhich got abandonned, but asks a question17:43
jordanPwhat should we do if we break a project because they improperly imported/used non tempest/lib code ?17:43
*** anilvenkata has quit IRC17:44
oomichijordanP: Ideally, that should be fixed on project side, IMO17:44
oomichilike this case17:44
mtreinishjordanP: normally there is a quick fix in the consuming project because there is a supported way of doing it17:44
mtreinishbut if there isn't a quick fix I think a revert is appropriate17:44
oomichibut if the effect is so big, it is possible to revert it case by case17:45
jordanPok, we are on the same page17:45
jordanPoomichi, https://review.openstack.org/#/c/415532/17:45
jordanPand https://review.openstack.org/#/c/405691/17:45
jordanPthey are duplicates17:45
jordanPbut yours depend on a patch that is not going to be merged soon :)17:46
jordanPanyway, it's not critical, we can discuss this in #qa17:46
oomichijordanP: I win the race, but yeah that contains problem as you said ;)17:46
mtreinishoomichi: heh, I like how sdague +2'd both :)17:47
oomichijordanP: I drop it now :)17:47
*** Kevin_Zheng has quit IRC17:47
oomichihaha, that is not good17:47
*** guoshan has joined #openstack-meeting17:47
jordanPsdague, was like 'let's see who wins this !'17:47
oomichijordanP: yeah, then you win now17:48
jordanPbottom line is, we should all do more devstack reviews :)17:48
*** rtheis has quit IRC17:48
oomichijordanP: btw you seem to check unnecessary options of Tempest, the check is done already ?17:48
jordanPI think I have it all covered yes17:49
jordanPbut a second pair of eyes always help17:49
oomichijordanP: cool, thanks so much for that17:49
jordanPI've only done half of the job, the rest is to actually delete the options17:49
jordanPnow they are just deprecated17:49
oomichiyeah, they are nice steps17:50
oomichido we have more patches to be reviewed today?17:51
oomichi#topic Open Discussion17:51
*** openstack changes topic to "Open Discussion (Meeting topic: qa)"17:51
mmedvedehi, I'd like to request permission for voting on DevStack patches for IBM PowerKVM CI, is there a quorum here for a decision?17:51
*** guoshan has quit IRC17:52
oomichimmedvede: is that stable now?17:52
mmedvedeit is mostly stable, 7 day history: http://ci-watch.tintri.com/project?project=devstack&time=7+days17:52
mmedvedeI'd say it sometimes gives a false negative, but it is not much worse than jenkins at that, and we try to recheck when it happens17:53
*** tonytan4ever has quit IRC17:54
*** tonytan4ever has joined #openstack-meeting17:54
jordanPI am not found of the idea17:54
jordanPwe already have a hard time we the community gate17:55
jordanPmmedvede, why do you want to make it voting ?17:55
jordanPI mean, if we broke you and you are known here we can quickly work together17:55
jordanPto come up with a fix17:55
mmedvedeIt does catch valid problems sometimes for the platform (KVM on Power)17:55
*** fitoduarte has joined #openstack-meeting17:55
mtreinishjordanP: fwiw, voting doesn't really mean much. It just means it can leave a -1 on the patch, but it doesn't block anything17:56
mmedvedevoting gives  a bit more visibility, that is what voting for, right? :)17:56
jordanPyour CI should give you confidence about the stuff you deliver to your customers, why involve the community ?17:56
jordanPmtreinish, I didnt know that17:56
jordanPI though it would blocl17:56
jordanPblock17:56
mmedvedejordanP: yes, it would not block the gate17:56
jordanPthen, I am not against having it voting17:57
jordanPit's something :)17:57
oomichiif that would be voting and give -1 on unrelated patches, that makes the review process slow17:57
*** mickeys has joined #openstack-meeting17:58
oomichibecause reviewers tend to avoid -1 voting patches17:58
*** yamahata has quit IRC17:58
oomichiand patch owners start getting angry to the CI which gives -117:58
mmedvedethat is correct, but our CI is stable enough17:59
*** yamahata has joined #openstack-meeting17:59
*** VW_ has joined #openstack-meeting17:59
*** VW_ has quit IRC17:59
jordanPwe are out of time, sorry...17:59
mmedvedeand we also disable reporting when we catch our ci going haywire17:59
oomichimmedvede ok, let's discuss it more on qa channel due to the time17:59
mmedvedeok17:59
oomichi#endmeeting17:59
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"17:59
openstackMeeting ended Thu Jan  5 17:59:59 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/qa/2017/qa.2017-01-05-17.00.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/qa/2017/qa.2017-01-05-17.00.txt18:00
oomichithanks all :)18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/qa/2017/qa.2017-01-05-17.00.log.html18:00
*** VW_ has joined #openstack-meeting18:00
*** galstrom_zzz is now known as galstrom18:01
*** nadya has quit IRC18:01
*** jkilpatr has quit IRC18:01
*** Swami has joined #openstack-meeting18:02
*** VW has quit IRC18:02
*** bobh has joined #openstack-meeting18:03
*** jordanP has quit IRC18:04
*** spzala has joined #openstack-meeting18:04
*** SumitNaiksatam has joined #openstack-meeting18:07
*** bobh has quit IRC18:08
*** saisrikiran has joined #openstack-meeting18:09
*** weshay_errand is now known as weshay18:17
*** jkilpatr has joined #openstack-meeting18:17
*** nadya has joined #openstack-meeting18:19
*** tonytan4ever has quit IRC18:19
*** tonytan4ever has joined #openstack-meeting18:20
*** nadya has quit IRC18:22
*** Leo_ has quit IRC18:26
*** hashar has quit IRC18:26
*** LiberalCarrot has joined #openstack-meeting18:29
*** LiberalCarrot has left #openstack-meeting18:29
*** kjorgensen has quit IRC18:29
*** kjorgensen has joined #openstack-meeting18:30
*** rbudden has quit IRC18:32
*** kjorgensen has quit IRC18:34
*** saisrikiran has quit IRC18:35
*** ekcs has quit IRC18:35
*** VW has joined #openstack-meeting18:35
*** VW has quit IRC18:40
*** TikTok has joined #openstack-meeting18:40
*** toscalix has quit IRC18:41
*** baoli has joined #openstack-meeting18:43
*** kjorgensen has joined #openstack-meeting18:54
*** reedip_outofmemo has quit IRC18:54
*** acoles is now known as acoles_18:57
*** ayogi has joined #openstack-meeting19:00
*** s3wong has joined #openstack-meeting19:00
*** VW has joined #openstack-meeting19:00
stevemaro/19:01
*** jkilpatr_ has joined #openstack-meeting19:01
*** shaohe_feng has quit IRC19:02
*** fzdarsky is now known as fzdarsky|afk19:03
dtroyero/19:03
dtroyer#startmeeting openstackclient19:03
openstackMeeting started Thu Jan  5 19:03:32 2017 UTC and is due to finish in 60 minutes.  The chair is dtroyer. Information about MeetBot at http://wiki.debian.org/MeetBot.19:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:03
*** openstack changes topic to " (Meeting topic: openstackclient)"19:03
openstackThe meeting name has been set to 'openstackclient'19:03
*** shaohe_feng has joined #openstack-meeting19:03
stevemarhowdy19:04
*** eliqiao has quit IRC19:04
dtroyerThanks to stevemar and huanxuan we have an actual agenda at19:04
dtroyer#link https://etherpad.openstack.org/p/osc-weekly-meeting19:04
*** eliqiao has joined #openstack-meeting19:04
huanxuano/19:04
huanxuanhi dtroyer and stevemar19:04
stevemarhi huanxuan!19:05
*** jkilpatr has quit IRC19:05
dtroyercourtesy meeting ping: dhellmann, rtheis,, sheel,, thingee, ankur-gupta-f19:05
dtroyer#topic releases19:05
*** openstack changes topic to "releases (Meeting topic: openstackclient)"19:05
dtroyerLets start with a release bit first though, should be quick19:05
huanxuanok19:05
dtroyerI'd like to get two releases in before the freeze, one early next week and the second a week or so later19:06
dtroyerthis touches on ▪https://review.openstack.org/41261419:06
dtroyerin that introduces volume v3, but is not complete.19:06
stevemardtroyer: that sounds good. we're 2 weeks away from non-client library freeze, and 3 weeks aware from library freeze19:07
dtroyerdo we want to hold off on that until it is more complete?  I'm unsure about leaving something partly done like that in a stable release19:07
*** saisrikiran has joined #openstack-meeting19:07
stevemarhow is it "partly done" ?19:07
dtroyerAIUI it is just a clone of v2 at this point, no new changes19:08
huanxuanyes it almost is19:08
huanxuanthere are some new features in v319:09
dtroyerare those features im plemented in the initial review?19:09
stevemarno they are not19:09
dtroyerthat's what I mean about incomplete… that might give off bad expectations to say 'v3' and not have anything that really is v3 yet19:09
*** bobmel has joined #openstack-meeting19:10
stevemarwe've never claimed support for an entire API version as being "complete"19:10
dtroyerto flip the coin, will it be less frustrating for users to have a stable release with a) and incomplete v3 or b) no v3?19:10
dtroyerno, but it doesn't do _anything_ new yet19:10
stevemarwe claimed we had v2 support for cinder last release when we didn't have most of it done yet19:11
*** rcernin has joined #openstack-meeting19:11
dtroyerbut it used a v2 endpoint.19:11
stevemarthis one doesn't?19:11
dtroyersee? I can defend both positions here, somebody push me one way or the other! :)19:11
stevemari'm not sure how many users actually use volume api v319:12
dtroyerI don't think our volume discovery is 'done' and there is no microversioning yet19:12
*** eliqiao has quit IRC19:13
dtroyerwhat I'd like to do is have the next release be our stable (modulo bug fixes) and the release just before freeze be our continuing development to get us into a solid place during the freeze19:13
dtroyerlast cycle was frustrating with the amount of stuff that piled up, I'm thinking that's a great time to work on the tests (more to come on that later)19:14
dtroyerso here is a proposal:19:14
dtroyer* we hold off on the volume v3 review until after the next release19:14
stevemareh... i can go either way, i see the point of delivering something incomplete19:14
dtroyer* after the next release we only do bug fixes for a couple of days19:15
dtroyer* whatever we have there becomes stable (way early yes, but there is a reason)19:15
dtroyerthen we can get in the v3 and other new features and release the first post-stable before the freeze19:15
dtroyerthoughts?19:15
*** harlowja has joined #openstack-meeting19:16
stevemari can dig it19:16
huanxuanI agree19:16
stevemarwe're old and used by too many things to go crazy with features at the last minute19:16
*** saju_m has joined #openstack-meeting19:17
stevemarone release, then another release with bug fixes  => what we deliver for ocata ... sounds good to me19:17
dtroyerok, we'll run with that then…19:17
dtroyermoving on…19:17
dtroyer#topic bugs19:17
*** openstack changes topic to "bugs (Meeting topic: openstackclient)"19:17
dtroyerlets start with hhttps://bugs.launchpad.net/os-client-config/+bug/163569619:18
openstackLaunchpad bug 1635696 in os-client-config "Having a '{' or '}' in password causes formatting errors" [High,Confirmed]19:18
dtroyerno, that's not what I meant, but we'll go with it19:18
stevemarhmm?19:19
*** lpetrut has joined #openstack-meeting19:19
dtroyerthis one was introduced when o-c-c started using the new string substitution syntax19:19
dtroyerso we either need to undo that or start escaping strings19:19
stevemari'm not sure how impactful it is, so far 2 users have hit it19:20
*** sudipto_ has quit IRC19:21
*** sudipto has quit IRC19:21
dtroyerthat we know of…  yeah, not sure if it's High or Medium actually19:21
dtroyerbut it applies to _all_ config values that o-c-c handles, not just passwords19:21
*** nadya has joined #openstack-meeting19:21
stevemarlike username and such19:22
stevemarthough why you would have { or } in user or proejct name is beyond me19:22
dtroyerright, I don't know where else to expect to see this19:23
dtroyerwe should kick ot over with mordred and shrews and see of they've run across anything and have a preference19:23
stevemari don't know where the fix goes for this, otherwise i'd jump in19:23
dtroyerit's o-c-c, that is what introduced the issue19:24
dtroyerwe could work around it in osc or osc-lib, but we have a lot of that crap already that I'm trying to remove19:24
dtroyerI think since it isn't a top priority, we can take the time to talk with the other o-c-c cores19:25
*** Leo_ has joined #openstack-meeting19:25
mordredoh19:26
mordredwow19:26
mordredyeah. let's ... uhm ... fix that19:26
dtroyerhey mordred!  welcome…19:27
stevemar o/ mordred19:27
*** nadya has quit IRC19:27
*** Douhet has quit IRC19:27
*** Douhet has joined #openstack-meeting19:28
stevemarmordred: any take on this one? have you run into this issue in occ/shade?19:28
mordredI haven't - but then I also haven't had any { in passwords19:28
*** diablo_rojo has joined #openstack-meeting19:28
dtroyerI think it affects any config values, but we couldn't come up with a place that '{' chars might be common19:29
mordredpassword seems like the most likely place19:29
dtroyersince that's user-changeable I don't think this is a top priority19:29
mordredI wonder if maybe we just don't run the substitution on the password field :)19:29
stevemari would think the fix happens here: https://github.com/openstack/os-client-config/blob/master/os_client_config/config.py#L789-L82319:29
mordredI cna't come up with ANY reason for using substitution vars in your password19:30
stevemardefinitely not19:30
dtroyerstevemar: are there other auth password-like attributes that might need this fix?19:30
*** iyamahat has quit IRC19:31
stevemarmaybe if you are using ADMIN_TOKEN?19:31
dtroyerpkiz is old news, what is the char set for fernet tokens?  I think UUID is safe19:32
*** yamahata has quit IRC19:32
*** saisrikiran has quit IRC19:32
dtroyerI am OK with making a list of values to skip substitution on and going from there19:32
*** SumitNaiksatam has left #openstack-meeting19:33
stevemardtroyer: yah19:33
dtroyerok, lets keep going…19:33
dtroyernow for the fun one: https://bugs.launchpad.net/python-openstackclient/+bug/165231719:33
openstackLaunchpad bug 1652317 in Manila "OpenStackSDK refactoring caused various OSC networking commands to fail" [Critical,New]19:33
dtroyerWe missed this because our functional tests were no-ops for a few months :(19:34
dtroyerthat's been fixed, and SDK 0.9.11 was blacklisted in parallel with us skipping the broken tests19:34
dtroyerso we still have 7 tests to fix (sdk 0.9.12 is out and will either break or get blacklisted again when it hits u-c)19:35
dtroyerI was thinking about pinging the folks that originally write those tests to follow up with them and fix them19:35
dtroyerunless someone just wants to pick it up?19:35
stevemari've got a full plate :(19:36
huanxuanI think I can do it19:36
*** unicell has quit IRC19:37
stevemardtroyer: i'd say these are must-fix bugs19:37
dtroyeryes, I'd like to have this done for stable release, we should be back on latest SDK for stable19:37
dtroyerhuanxuan: thanks, you don't need to to the full rewrite that I've started for this, just make them work19:38
huanxuanok, zhiyong, jiahui and I will try to fix them19:39
*** gouthamr has quit IRC19:39
dtroyerand finally, https://bugs.launchpad.net/python-openstackclient/+bug/165002619:40
openstackLaunchpad bug 1650026 in python-openstackclient "Trying to get help for a command errors out with "__init__() got an unexpected keyword argument 'project_name'"" [High,Confirmed]19:40
stevemaranother must-fix :(19:40
*** gouthamr has joined #openstack-meeting19:40
dtroyerI have not looked in to this one… is it still happening as reported?19:40
*** salv-orl_ has quit IRC19:41
stevemari think so, i checked it last week or so19:41
sshankdtroyer, I ran into issue that when I was testing my neutron dhcp patch.19:42
stevemarit does only affect networking commands19:43
dtroyerI have not come across it in the network func test work I've been doing19:44
dtroyerfiwi, I'm using a devstack config from clouds.yaml, not env vars19:44
dtroyerI wonder if env vars is the common thread?19:44
dtroyersshank: ^^^ ???19:45
sshankdtroyer, I sourced from openrc. Maybe that's causing the issue.19:45
dtroyerso was mriedem in the bug report19:45
dtroyerI'll try that too19:45
stevemarpossible, i was using env. vars too19:46
dtroyerlet's follow up in the bug with that…19:47
mriedemyeah i do: source devstack/openrc admin19:48
mriedemthen all hell breaks loose19:48
dtroyerFWIW, I see it too using openrc19:48
mriedemnote that i get a warning about OS_TENANT_NAME or something when sourcing that way19:48
mriedemmight be ID19:49
mriedembut guessing that's somehow related19:49
dtroyermriedem: is there a chance you can try using clouds.yaml to verify that it doesn't see the problem?19:49
mriedemdtroyer: probably not today19:49
dtroyerI think the OS_TENANT_NAME is just a hard-coded warning in openrc19:49
dtroyermriedem: no worries, we can follow up in the bug19:49
dtroyerthanks19:49
stevemardtroyer: thats correct, its an openrc warning19:49
dtroyer#topic OSC metapackage19:50
*** openstack changes topic to "OSC metapackage (Meeting topic: openstackclient)"19:50
dtroyerstevemar: enlighten us!19:50
*** abalutoiu has quit IRC19:50
stevemaroh right19:51
*** tonytan4ever has quit IRC19:51
*** kjorgensen has quit IRC19:51
*** iyamahat has joined #openstack-meeting19:51
stevemari've got the infra and governance patches done19:51
stevemarjust needs an initial commit -- https://review.openstack.org/#/c/414380/19:51
stevemarbut a passing one :)19:51
dtroyercoolness19:52
stevemarnot sure how i bungled the doc build, but i managed to19:52
*** kjorgensen has joined #openstack-meeting19:52
*** sdake has quit IRC19:52
dtroyerI'll throw some eyes on it later19:52
stevemarlocally, the docs are being generated one folder up from where they should be19:52
stevemari imagine it's a case of a missing ".."19:52
stevemaror one too many19:52
stevemaronce that passes we could technically "release" it at any time19:53
*** cleong has quit IRC19:53
dtroyerhow do you feel about doing a stable release of this?  we could wait until the last minute to get some more time with it?19:54
*** Swami has quit IRC19:54
dtroyerbut promoting it (eventually) as the documented way to get OSC19:54
stevemarprobably best to get more time with it, i have no idea what the ramifications are of installing it19:55
dtroyerfor Ocata19:55
dtroyerok, I can live with that19:55
stevemaryou mean Pike?19:55
dtroyerwell, yes, now for Pike19:55
stevemarwe can modify the install docs and such for Pike19:55
*** e0ne has joined #openstack-meeting19:56
*** kjorgensen has quit IRC19:56
dtroyerok, 4 minutes, one more thing...19:56
dtroyer#topic functional tests19:56
*** openstack changes topic to "functional tests (Meeting topic: openstackclient)"19:56
dtroyerI was just wondering if there was anything to add to the functional test rewrites I've started.19:56
dtroyerI have seen a couple of reviews with devs starting to change to that format19:57
*** mtanino has joined #openstack-meeting19:57
dtroyer\o/19:57
stevemaroh?19:57
huanxuanyes19:57
stevemari thought it was just you? :P19:57
dtroyerapparently I'm not as far off the trail as I thought?19:57
huanxuanjiahui and zhiyong will doing that as well19:58
stevemarthe new changes are good to me19:58
dtroyeranyway, anything to add to that?  I've noted wanting to add some alternate output format testing19:58
stevemaradd it to the backlog19:58
dtroyerand I just pushed up a rewrite for (compute) flavor to add a check for the bug Jens fixed this morning19:58
stevemarare we good with using the etherpad for the meeting agenda?19:59
dtroyerI do not plan to do all of these myself, but want to target the one we have or think we may have issues with19:59
*** markvoelker has quit IRC19:59
dtroyerI am…was the issue with the wiki the locking down of account creation?19:59
stevemaryeah, and just annoying to update tbh19:59
*** markvoelker has joined #openstack-meeting19:59
stevemarwe've been using it in keystone for about a year20:00
stevemar8 months20:00
dtroyerit is fine with me… I've started doing non-openstack stuff with folk in etherpads, it's becoming my more common doc environment!20:00
huanxuanyes, it is good20:00
dtroyerok, with that we're out of time20:00
dtroyerthanks everyone!20:01
huanxuanyes20:01
dtroyer#endmeeting20:01
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"20:01
stevemarsee ya20:01
openstackMeeting ended Thu Jan  5 20:01:04 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:01
huanxuanThanks!20:01
sshankThanks20:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstackclient/2017/openstackclient.2017-01-05-19.03.html20:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstackclient/2017/openstackclient.2017-01-05-19.03.txt20:01
openstackLog:            http://eavesdrop.openstack.org/meetings/openstackclient/2017/openstackclient.2017-01-05-19.03.log.html20:01
*** rfolco has quit IRC20:01
*** cleong has joined #openstack-meeting20:02
*** Sukhdev has joined #openstack-meeting20:02
*** huanxuan has quit IRC20:04
*** bobh has joined #openstack-meeting20:05
*** TxGirlGeek has quit IRC20:06
*** TxGirlGeek has joined #openstack-meeting20:06
*** rfolco has joined #openstack-meeting20:07
*** rfolco has quit IRC20:07
*** egallen has quit IRC20:09
*** bobh has quit IRC20:09
*** yamahata has joined #openstack-meeting20:10
*** jaugustine has quit IRC20:12
pabelangergreghaynes: is DIB meetings a thing any more?20:12
*** asselin has joined #openstack-meeting20:14
*** bobmel has quit IRC20:15
*** bobmel has joined #openstack-meeting20:15
*** bobmel has quit IRC20:20
*** gibi has joined #openstack-meeting20:21
*** VW has quit IRC20:21
*** VW has joined #openstack-meeting20:23
*** ayogi has quit IRC20:23
*** asselin has quit IRC20:24
*** unicell has joined #openstack-meeting20:25
*** VW has quit IRC20:26
*** VW has joined #openstack-meeting20:27
*** bvandenh has quit IRC20:27
*** rasca has quit IRC20:28
*** TxGirlGeek has quit IRC20:30
*** tovin07 has joined #openstack-meeting20:33
*** e0ne has quit IRC20:36
*** kjorgensen has joined #openstack-meeting20:36
*** unicell has quit IRC20:37
*** sdake has joined #openstack-meeting20:42
*** dbecker has joined #openstack-meeting20:42
*** bvandenh has joined #openstack-meeting20:43
*** bvandenh has quit IRC20:48
*** guoshan has joined #openstack-meeting20:49
*** diana_clarke has joined #openstack-meeting20:52
*** takashin has joined #openstack-meeting20:53
*** eharney has quit IRC20:53
*** guoshan has quit IRC20:54
*** dbecker has quit IRC20:55
*** Vek has joined #openstack-meeting20:55
*** askb has joined #openstack-meeting20:58
*** cdent has joined #openstack-meeting20:58
mriedem#startmeeting nova21:00
openstackMeeting started Thu Jan  5 21:00:21 2017 UTC and is due to finish in 60 minutes.  The chair is mriedem. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: nova)"21:00
openstackThe meeting name has been set to 'nova'21:00
* Vek waves21:00
takashino/21:00
macsz\o21:00
dansmithmoo/21:00
tovin07o/21:00
dansmithum, I did not mean to moo21:00
edleafe\o21:00
macszcowsay? ;)21:00
*** dtp has joined #openstack-meeting21:00
thorst_o/21:00
dtpo/21:00
diana_clarkeo/21:00
bauzas\o21:00
cdento/21:01
Vekhaha :)21:01
*** lblanchard has quit IRC21:01
mriedemsince i just broke the nova gate let's get this party started21:01
mriedem#link meeting agenda https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting21:02
Vekheh21:02
mriedem#topic release news21:02
*** openstack changes topic to "release news (Meeting topic: nova)"21:02
efriedo/21:02
mriedem#link Ocata release schedule: https://wiki.openstack.org/wiki/Nova/Ocata_Release_Schedule21:02
mriedem#info Jan 19: final non-client library release (oslo)21:02
mriedem^ is the next upcoming major deadline21:02
mriedemif you have changes that depend on a library patch to get released, that library release has to happen by the 19th21:02
mriedemi know we at least have one for os-vif21:03
mriedem#info Jan 26: o-3 milestone, final python-novaclient release, FeatureFreeze, Soft StringFreeze21:03
mriedemso one week after lib freeze is feature freeze and the o-3 milestone21:03
mriedemon a side note i'm on vacation that week so bauzas is going to handle the o-3 release tag21:03
mriedemand jaypipes is also on vacation that week21:03
* melwitt o/21:03
mriedemquestions about dates?21:04
mriedemwe've got 3 weeks until feature freeze and a lot to do yet21:04
mriedem#link Ocata blueprints https://blueprints.launchpad.net/nova/ocata21:04
*** ykatabam has quit IRC21:04
mriedem #info 70 total blueprints, 16 implemented, 5 not started, 38 need code review21:04
jaypipeshey, sorry, was out last few hours. back now.21:04
mriedemso we've got about 23% of our blueprints completed21:04
mriedemthere are a few out there which need a final +221:05
mriedem#link Details on remaining blueprints: https://etherpad.openstack.org/p/nova-ocata-feature-freeze21:05
bauzasI guess we could have a review day?21:05
mriedemif you didn't see the ML thread, ^ is a thing i did last week21:05
mriedembauzas: getting there :)21:05
*** TxGirlGeek has joined #openstack-meeting21:05
bauzasoh yeah, just saw the agenda21:06
mriedemi categorized the remaining blueprints and added notes on where i thought each was progress-wise in that etherpad21:06
mriedemi plan on scrubbing through it again tomorrow21:06
mriedemmore on that later21:06
mriedemany release questions?21:06
mriedem#topic bugs21:06
*** openstack changes topic to "bugs (Meeting topic: nova)"21:06
mriedemwell21:07
mriedemhttps://bugs.launchpad.net/nova/+bug/165439321:07
openstackLaunchpad bug 1654393 in OpenStack Compute (nova) ""keystoneauth1.exceptions.catalog.EmptyCatalog: The service catalog is empty." in test_cinderclient_unsupported_v1" [High,Confirmed]21:07
mriedem^ is new as of today, bouncing changes21:07
mriedemand is my fault21:07
*** bvandenh has joined #openstack-meeting21:07
mriedemi suspect a racy global mock in the test added today21:07
mriedemif no one else figures it out anytime soon i'll be working on that tonight21:07
mriedemotherwise we're pretty good on gate status21:08
mriedemanything else on bugs?21:08
mriedem#topic reminders21:08
*** openstack changes topic to "reminders (Meeting topic: nova)"21:08
mriedemthe usual21:08
mriedem#link Ocata review priorities https://etherpad.openstack.org/p/ocata-nova-priorities-tracking21:08
mriedem#topic Stable branch status: https://etherpad.openstack.org/p/stable-tracker21:09
*** openstack changes topic to "Stable branch status: https://etherpad.openstack.org/p/stable-tracker (Meeting topic: nova)"21:09
mriedemthere are some things getting into stable/newton that i'm looking to release soon, maybe next week21:09
mriedemone is for fixing an upgrade issue from mitaka21:09
mriedemso would like to get that released soon21:09
mriedem#topic subteam highlights21:09
*** openstack changes topic to "subteam highlights (Meeting topic: nova)"21:09
mriedemdansmith: cells v2?21:10
dansmithwe had a meeting,21:10
dansmithseveral things up for review, all on the priorities tracker page21:10
dansmithquota stuff, multicell stuff, and some other minor things we need to change21:10
dansmiththat's pretty much it21:10
mriedemmain thing looking at right now is cells v1 job with cells v221:11
mriedemat least for dansmith21:11
dansmithyeah, getting there.. have a debug patch up and slogging through21:11
mriedemok thanks21:11
mriedemedleafe: scheduler?21:11
edleafeI was out Monday, so jaypipes or cdent can fill you in21:11
cdentjaypipes: ran the meeting and went through all the relevant reviews21:11
cdentand that's about it21:11
bauzaswas on PTO21:12
cdentWe introduced some new contributors to the lay of the land21:12
cdentnice way to start year21:12
jaypipesmriedem: briefly talked about the issue with NUMA objects being recreated every time update_available_resource() is called and the trouble that causes trying to add a uuid field to the NUMA cell.21:12
mriedemok, so for placement, the main focus right now is going to be on getting https://review.openstack.org/#/c/392569/ in which is needed for the scheduler to use the placement API21:12
jaypipesmriedem: yep ++21:12
mriedemand then bauzas is going to have a change up for the scheduler21:13
mriedemany minute now... :)21:13
mriedemand that's the main goal for placement in ocata21:13
mriedemthere are of course lots of other patches up21:13
bauzasyeah, the scheduler change should come up soon21:13
mriedemok moving on21:14
mriedemis tdurakov or pkoniszewski around?21:14
mriedemfor live migration21:14
mriedemguess not21:14
mriedemok, api21:14
*** salv-orlando has joined #openstack-meeting21:14
mriedemsdague: were you at the api meeting this week?21:14
mriedemwell,21:15
mriedemtwo things,21:15
cdentlots of discussion about capabiities spec under review in api-wg21:15
mriedemthe query parameters validation changes are in and merged21:15
cdentsome discussion on how to manage the fixes to filtering (avoiding joins and whatnot)21:15
mriedemcdent: yeah i expect that'll be a cross-project discussion at the PTG21:15
mriedemi'm not sure if i can call it cross project or not, the PTG rules are new and scary21:16
cdentquite21:16
bauzasthere is now a wiki AFAIK21:16
mriedemthe other thing for ocata api stuff is the server sort/filter patches that Kevin Zheng is working on21:16
bauzashttps://wiki.openstack.org/wiki/Forum21:17
mriedemthose changes are here https://review.openstack.org/#/q/topic:bp/add-whitelist-for-server-list-filter-sort-parameters+status:open21:17
mriedemlooks like i need to talk to alex_xu and Kevin about what's going on there21:17
mriedemmoving on21:17
mriedemi don't see anyone around for the sriov/pci meeting, if there was one this week21:18
mriedemgibi: notifications updates?21:18
gibishort one21:18
gibinothing has been finished but everything is moving21:18
gibithe first patch of the instance action notification extensions for searchlight has been merged21:18
gibinot the whole bp scope will be finished for Ocata but we still have some patch that has chance21:18
gibijson-schema-for-versioned-notifications still has some dependency on ovo lib due to https://review.openstack.org/#/c/411822/21:18
gibiso this has less and less chance to be finished in Ocata21:19
gibithe flavor notification bp has code up and it is getting in a good shape21:19
*** cdelatte has quit IRC21:19
mriedemyeah i need to get back on https://review.openstack.org/#/c/398171/21:19
mriedembut it's close21:19
gibithe priority etherpad is up to date21:19
gibithat is all21:19
mriedemok thanks gibi21:19
mriedem#topics PTG planning21:20
*** rbudden has joined #openstack-meeting21:20
mriedem#topic PTG planning21:20
*** openstack changes topic to "PTG planning (Meeting topic: nova)"21:20
mriedem#link Pike PTG planning: http://lists.openstack.org/pipermail/openstack-dev/2017-January/109594.html21:20
mriedemi've started an etherpad to jot down topics21:20
mriedemi'm still just trying to figure out myself how this thing is going to work21:21
mriedembut with wed-friday being like a normal midcycle i guess i'm going to start out by treating it that way, mostly open-ended21:21
mriedembut we'll need to be discussing things for Pike deliverables for sure since it's at the start of Pike21:21
mriedemany questions on the PTG?21:22
mriedem#topic stuck reviews21:22
*** openstack changes topic to "stuck reviews (Meeting topic: nova)"21:22
mriedemthere was nothing in the agenda - anyone have something for this?21:22
*** armax has joined #openstack-meeting21:22
mriedem#topic open discussion21:22
*** openstack changes topic to "open discussion (Meeting topic: nova)"21:22
mriedema few items21:22
mriedemI plan on scrubbing https://etherpad.openstack.org/p/nova-ocata-feature-freeze  before next week to maybe drop things that haven't started but to also  highlight things that need review and are close if given a good push.21:22
mriedemGiven that, I'm proposing a review sprint for next week on Wednesday  1/11 which leaves about a week before library release freeze and two  weeks before feature freeze.21:23
mriedemare people ok with that date for a blueprint code review sprint?21:23
mriedemi can't do monday or tuesday21:23
cdentwednesday++21:23
bauzascool by me21:24
mriedemok - it's going to be mostly harassment in the nova channel21:24
mriedem#info if you've got a blueprint up for review, be in the channel on wednesday 1/11 in case there are questions21:24
mriedem#undo21:24
openstackRemoving item from minutes: #info if you've got a blueprint up for review, be in the channel on wednesday 1/11 in case there are questions21:24
*** JoseMello has quit IRC21:25
mriedem#info if you've got a blueprint up for review, be in the openstack-nova channel on wednesday 1/11 in case there are questions21:25
mriedem (efried / thorst) PowerVM Update21:25
thorst_I’ll give a powervm CI update.  efried will do a powervm driver review update.21:25
thorst_We hit an issue where we need to change the name space of our out of tree driver so that in tree can just be ‘powervm’.  We’re working through that joy...  Affected our CI.21:25
thorst_We’re also working through a keystone issue now, so while we’re running nova jobs, we shut off publishing so we don’t flood red to each patch (even if non-voting).  Plan to turn back on soon.21:25
*** aeng has joined #openstack-meeting21:26
thorst_that's about it for where we are w/ CI.21:26
mriedemok21:26
efriedFour outstanding change sets for the PowerVM driver:21:26
efried#link https://review.openstack.org/#/q/powervm-nova-compute-driver+status:open21:26
efriedFirst one is a bit large (+1732 at current patch set).21:27
efried#link https://review.openstack.org/#/c/391288/21:27
efriedWould like to get some feedback from those present as to whether we should attempt to split this up further.  This won't be trivial, or we would have done it already, but I'm sure we can figure it out if it's going to make the difference getting core reviews.21:27
*** jungleboyj has quit IRC21:27
mriedemso,21:27
*** jkilpatr_ has quit IRC21:27
mriedemthis is actually paired down from when i first looked at it,21:27
mriedembefore it had tests :)21:27
*** Leo_ has quit IRC21:28
mriedemso now the first one is just spawn/destroy + infra21:28
mriedemwhen i looked last week, the powervm ci was running wayyyy more tests than i thought it would for just spawn/destroy21:28
mriedemwhich was probably why a ton of it was failing21:28
efriedCorrect.  If we were gonna split it further, it would be infra with no functionality, then spawn/destroy in a subsequent.21:28
thorst_mriedem: so that's the issue we're working on.  The OOT was what ran on that21:28
efriedWell, we have a question about the CI in a sec.21:28
mriedemi would prefer to have spawn/destroy minimal in the first change21:28
thorst_we will have a second CI for the in tree...but its a bit of a chicken / egg there on the CI and driver there.21:29
mriedemif there is something in there that looks like it could be split out, people can comment as such21:29
efriedSounds good to me.21:29
mriedemthorst_: i'd expect that ci to just run on these patches21:29
*** ykatabam has joined #openstack-meeting21:29
mriedemnot other nova patches21:29
thorst_the in tree or out of tree?21:30
mriedemand not be doing anything with volumes, or attaching interfaces, pause/suspend, any of that stuff21:30
mriedemthe in-tree21:30
*** reed has quit IRC21:30
mriedemi expect the in-tree ci to only be running on the patches for the in-tree driver right now21:30
mriedemit doesn't really make sense otherwise21:30
thorst_OK - yeah, we are setting up the skip lists and config for that one in parallel21:30
mriedemok21:30
thorst_its...fun...21:30
mriedemi had figured the tests being run were for the out of tree driver, which didn't make sense for the in-tree patches21:30
mriedemthorst_: honestly i'd probably start with a whitelist21:31
mriedemand build that up21:31
efriedRight, so the question is whether we need to have (a drastically pared-down version of) our CI actually passing before we can expect to merge each change?21:31
mriedemefried: well i expect to see the powervm ci reporting on those changes to show green21:31
mriedemif that means you're only running 20 tempest tests for spawn/destroy, so be it21:31
efriedOkay, that's what I figured, and that's totally reasonable.21:31
thorst_sounds good21:32
mriedemstart small and build out the test set21:32
mriedemotherwise you're going to die21:32
*** reed has joined #openstack-meeting21:32
efriedFor the other change sets, we expect to be able to wipe the WIP off in the next week or two.21:32
efriedRealizing this means some of this function will probably slip to pike.21:32
mriedemjust to level set expectations, i think getting the first patch for spawn/destroy in this release is going to be an achievement21:32
thorst_understood.21:33
mriedemok let's move on21:33
mriedemthanks for the updates guys21:33
mriedem(tovin07): OSprofiler support in Nova is almost done and marked as good progress.21:33
thorst_thx21:33
tovin07yes21:33
tovin07i just want to get some attention for this patch21:33
tovin07#link osprifiler in nova review: https://review.openstack.org/#/c/254703/21:33
tovin07patch in novaclient is OK now, waiting for patch in nova...21:34
mriedemyeah it'd be nice to get that in finally, but i haven't gone through it since newton i don't think21:34
mriedembut i know we relied on it heavily for our cloud performance testing21:34
tovin07yup, i see it too21:34
mriedemso, be around in the nova channel on wed 1/11 in case questions come up21:34
mriedemor issues21:34
mriedemok, anyone else have anything to discuss?21:35
tovin07okay, sound good :D21:35
tovin07thanks21:35
mriedemi'm not hearing anything, and we're already about 20 minutes over where dansmith wanted this to be, so thanks everyone21:35
dansmithyup.21:35
mriedem#endmeeting21:35
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"21:35
openstackMeeting ended Thu Jan  5 21:35:56 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova/2017/nova.2017-01-05-21.00.html21:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova/2017/nova.2017-01-05-21.00.txt21:36
openstackLog:            http://eavesdrop.openstack.org/meetings/nova/2017/nova.2017-01-05-21.00.log.html21:36
* Vek waves again21:36
*** dtp has left #openstack-meeting21:36
*** Vek has left #openstack-meeting21:36
*** saju_m has quit IRC21:36
*** cdent has left #openstack-meeting21:36
*** takashin has left #openstack-meeting21:36
*** bvandenh has quit IRC21:37
*** eharney has joined #openstack-meeting21:41
*** ansmith has quit IRC21:42
*** diana_clarke has left #openstack-meeting21:42
*** jaugustine has joined #openstack-meeting21:42
*** tovin07 has left #openstack-meeting21:42
*** dimtruck is now known as zz_dimtruck21:50
*** guoshan has joined #openstack-meeting21:50
*** salv-orl_ has joined #openstack-meeting21:53
*** cleong has quit IRC21:54
*** guoshan has quit IRC21:55
*** salv-orlando has quit IRC21:56
*** Leo_ has joined #openstack-meeting21:58
*** dprince has quit IRC21:58
*** boden has joined #openstack-meeting22:00
*** Leo_ has quit IRC22:00
*** zz_dimtruck is now known as dimtruck22:01
*** dbecker has joined #openstack-meeting22:03
*** thorst_ has quit IRC22:04
*** X-dark has quit IRC22:06
*** darrenc is now known as darrenc_afk22:07
*** X-dark has joined #openstack-meeting22:09
*** jkilpatr_ has joined #openstack-meeting22:10
*** boden has left #openstack-meeting22:12
*** dimtruck is now known as zz_dimtruck22:13
*** sneti has joined #openstack-meeting22:17
*** matrohon has quit IRC22:21
*** edtubill has quit IRC22:22
*** darrenc_afk is now known as darrenc22:25
*** baoli has quit IRC22:26
*** salv-orl_ has quit IRC22:33
*** bobmel has joined #openstack-meeting22:34
*** designbybeck has joined #openstack-meeting22:35
*** salv-orlando has joined #openstack-meeting22:36
*** rbudden has quit IRC22:36
*** jamesdenton has quit IRC22:37
*** bobmel has quit IRC22:39
*** sdake has quit IRC22:39
*** jungleboyj has joined #openstack-meeting22:39
*** fguillot has quit IRC22:40
*** bobmel has joined #openstack-meeting22:43
*** pots has joined #openstack-meeting22:43
*** zz_dimtruck is now known as dimtruck22:45
*** guoshan has joined #openstack-meeting22:51
*** mriedem has quit IRC22:54
*** tommylikehu_ has joined #openstack-meeting22:54
*** guoshan has quit IRC22:56
*** tommylikehu_ has quit IRC22:57
*** lpetrut has quit IRC22:58
*** claudiub|2 has joined #openstack-meeting23:01
*** spotz_ is now known as spotz_zzz23:01
*** claudiub has quit IRC23:01
*** ekcs has joined #openstack-meeting23:02
*** sdake has joined #openstack-meeting23:03
*** designbybeck has quit IRC23:03
*** TxGirlGeek has quit IRC23:04
*** jrobinson has joined #openstack-meeting23:05
*** jrobinson_ has joined #openstack-meeting23:06
*** xyang1 has quit IRC23:06
*** tommylikehu_ has joined #openstack-meeting23:08
*** jaugustine has quit IRC23:08
*** galstrom is now known as galstrom_zzz23:09
*** ekcs has quit IRC23:11
*** tommylikehu_ has quit IRC23:12
*** sneti has quit IRC23:13
*** ekcs has joined #openstack-meeting23:19
*** gouthamr has quit IRC23:21
*** gouthamr has joined #openstack-meeting23:22
*** Sukhdev has quit IRC23:22
*** absubram has quit IRC23:28
*** annegentle has quit IRC23:32
*** unicell has joined #openstack-meeting23:34
*** TikTok has quit IRC23:34
*** jungleboyj has quit IRC23:35
*** unicell has quit IRC23:36
*** unicell has joined #openstack-meeting23:42
*** adiantum has joined #openstack-meeting23:45
*** salv-orlando has quit IRC23:45
*** spzala has quit IRC23:46
*** jrobinson_ has quit IRC23:46
*** jrobinson has quit IRC23:46
*** VW has quit IRC23:48
*** ekcs has quit IRC23:48
*** unicell1 has joined #openstack-meeting23:48
*** unicell has quit IRC23:49
*** claudiub|2 has quit IRC23:49
*** singlethink has quit IRC23:51
*** guoshan has joined #openstack-meeting23:52
*** Sukhdev has joined #openstack-meeting23:53
*** baoli has joined #openstack-meeting23:56
*** guoshan has quit IRC23:57

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