09:03:28 #startmeeting blazar 09:03:28 Meeting started Tue Nov 21 09:03:28 2017 UTC and is due to finish in 60 minutes. The chair is masahito. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:03:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:03:32 The meeting name has been set to 'blazar' 09:04:01 #topic RollCall 09:04:09 o/ 09:04:14 o/ 09:04:36 o/ 09:04:41 Today's agenda is 09:04:48 1. Q-1 release 09:04:56 2. Review meeting plan 09:04:59 3. AOB 09:05:03 anything else? 09:05:49 priteau, bertys, hiro-kobayashi: hello 09:06:15 ok, let's move on to first the topic. 09:06:26 #topic Q-2 release 09:07:09 Based on the queens schedule, Q-2 release milestone is coming in two weeks. 09:07:11 https://releases.openstack.org/queens/schedule.html 09:07:53 I plan to add 0.4.0-b2 tag in the milestone week. 09:08:21 Does anyone have specific patches that should be merged before the tag? 09:08:37 Or have any comment for the tag? 09:09:48 Isn't the tag supposed to be 0.4.0b2? 09:10:02 As per https://wiki.openstack.org/wiki/Branch_Model (not sure if that's the latest doc) 09:11:48 Also, other projects seem to be using four version numbers, should we do the same? 09:11:57 e.g. 7.0.0.0b1 09:12:32 oh, '-' looks not necessary. 09:13:12 We should follow the standard used in https://github.com/openstack/releases 09:13:28 IIRC, each team can decide the version number now. 09:14:15 I'll check which is latest doc and which is correct doc later. 09:14:59 Thanks masahito! 09:15:08 I thinks specs are better to be merged before Q-2. One spec is still under reviewing: https://review.openstack.org/#/c/516222/ 09:16:25 hiro-kobayashi: thanks for picking up it. 09:17:16 When I wrote the spec, I thought 'extra_spec' matches to ComputeHostExtraCapacity. 09:18:11 But bertys's comment reminds me that Nova's flavor also have same key name. Should I change the key name? 09:19:31 extra_spec can cause misunderstandings. Do you have other good name? 09:20:20 How about 'resource_properties' like the host plugin? 09:20:44 That's what I was thinking. 09:22:13 okay, I'll revise it with 'resource_properties'. 09:22:41 other comments for Q-2 release? if nothing, move on to next. 09:23:20 Not exactly related to the Q-2 release, but should we consider releasing python-blazarclient on PyPI? 09:23:47 Now that we have a fix for the auth method 09:24:10 priteau: Nice catch! 09:24:12 right. 09:24:57 My idea is adding 0.3.1 tag. How do you think? 09:25:49 Sounds good to me 09:26:11 +1 09:26:41 okay, I'll add the tag later 09:26:55 Thanks! 09:27:48 priteau: my pleasure 09:27:58 #topic Review meeting plan 09:28:42 We had the review meeting in Pike cycle. IMO, it was nice activity. 09:28:59 yes it was! 09:29:11 I'm thinking it's good to have this meeting for Queens cycle. 09:29:23 sounds good 09:29:45 My question is which week or day works for you? 09:30:13 I think most of us would take winter vacation in December. 09:30:24 Some time in early December would work best for me 09:30:43 So Jan 2018 seems to be good. 09:31:11 priteau: okay, how about Jan 2018? 09:31:22 Both of early Dec and Jan will work for me. 09:31:43 January I can do only from the 22nd 09:32:04 I am in the US early Dec. Second week in Jan or later 09:32:08 I've got many meetings in the first half of January already 09:32:10 would work for me 09:32:36 I have a plan of business trip 5th-7th. 09:32:43 thanks all. 09:33:33 So sounds like early or middle Dec. and later Jan. work for us. 09:33:56 Q-3 milestone is week of Jan 22th. 09:35:45 We could have two meeting. First one is in early Dec and second one is in later Jan. 09:36:55 First one mainly discuss spec or big changes. Second one mainly bug fix, etc. How do you think? 09:37:10 Sounds good to me 09:37:43 +1 09:38:33 ok 09:39:16 Is there any preference for the day? 09:39:40 If nothing, I'll send a mail to openstack-dev ML with some candidates for the meeting. 09:40:04 We could schedule it at the time of this weekly meeting 09:40:13 We know that everyone is available. 09:40:38 yup. 09:41:44 For the same time, 5th, 12th, 19th Dec for first meeting. 09:42:03 If on Dec 5th, could you start 1 hour earlier? It will be 1am in the US 09:42:47 I might be on vacation on the 19th 09:43:01 I'm not available on 19th 09:43:01 I would have another meeting at 5th. 09:43:18 12th looks fine 09:43:20 sounds 12th works for us. 09:43:53 12th works better, will be back home 09:44:24 okay, let's do the meeting on 12th Dec. 09:44:26 I can do the 12th 09:45:07 If we don't have much topics to discuss on the day, we can start it in weekly meeting. 09:46:57 For the second one, 23th Jan., 30th Jan. or 6th Feb. are candidates 09:48:08 IMO, 23th looks good from release schedule. 09:48:11 All of them works for me, maybe. 09:48:30 s/from/for/ 09:49:10 ok with Jan 23 09:50:10 priteau: you will be busy on 23th Jan.? 09:50:32 All three should work for me 09:51:05 okay. then second meeting will be on 23th Jan. 09:51:20 Any comments for the review meeting? 09:52:22 #topic AOB 09:52:31 last 10 mins. 09:52:48 Does someone have something to discuss/share/etc? 09:54:22 From my side, it's just fyi. 09:54:56 OPNFV started cross CI activities (XCI) recently. 09:55:01 https://etherpad.opnfv.org/p/xci-blazar 09:55:40 That's about NFV related scenario test with OpenStack and OPNFV. 09:57:05 The tests would be useful for Blazar itself, but the number of Blazar team is few members. 09:57:47 So I plan to raise it up after Queens cycle in Blazar team. 09:58:20 That's update from my side. 09:58:59 I would like to discuss something else 09:59:00 oh, And I pushed the patches related to deploy-api-with-wsgi. please review it. 09:59:22 Thanks masahito, will do! 09:59:30 Thanks for taking it! 09:59:44 blazar-nova gate jobs are failing. I posted the error in https://review.openstack.org/#/c/511163/ 10:01:01 Should we add required-projects to the blazar-nova jobs in project-config/zuul.d/projects.yaml? 10:01:34 It looks so. It's like the blazar-dashboard does. 10:02:07 looks like so. 10:02:27 But the blazar-nova section doesn't have any "check" job. Does it mean we have to copy the default "check" job to the blazar-nova section? 10:03:37 :q 10:03:49 I'm not familiar with zuulv3 yet. but if needed, we should do. 10:04:11 hiro-kobayashi: Do you remember how blazar-dashboard does? 10:04:50 I think we should add check section to blazar-nova 10:05:12 I will push a patch if no one plan to deal with it :-) 10:05:16 hmmm. time is up... 10:05:33 hiro-kobayashi: I'll try to fix it tomorrow 10:05:52 Thanks! 10:05:54 it's good chance to learn zuulv3. 10:05:58 hiro-kobayashi: I just can't find where the check-requirements template is defined. Is it in another repo? 10:07:03 I don't remember, sorry. 10:07:09 okay, then see you in next week! or at #openstack-blazar channel :-) 10:07:21 Thanks all! see you! 10:07:24 see you, bye 10:07:28 Thanks. 10:07:34 #endmeeting