Wednesday, 2017-01-04

*** spzala has quit IRC00:02
*** spzala has joined #openstack-meeting-300:02
*** sdake has quit IRC00:04
*** baoli has quit IRC00:05
*** dimtruck is now known as zz_dimtruck00:08
*** milan has joined #openstack-meeting-300:11
*** revon has quit IRC00:13
*** salv-orlando has quit IRC00:14
*** zz_dimtruck is now known as dimtruck00:15
*** yamamoto has joined #openstack-meeting-300:17
*** milan has quit IRC00:25
*** chyka has quit IRC00:28
*** milan has joined #openstack-meeting-300:31
*** Swami has quit IRC00:32
*** milan has quit IRC00:40
*** dimtruck is now known as zz_dimtruck00:44
*** milan has joined #openstack-meeting-300:51
*** hoangcx has joined #openstack-meeting-300:53
*** pt_15 has quit IRC00:54
*** milan has quit IRC00:55
*** Fdaisuke_ has joined #openstack-meeting-301:04
*** yamamoto has quit IRC01:04
*** Fdaisuke has quit IRC01:05
*** milan has joined #openstack-meeting-301:11
*** huanxuan has joined #openstack-meeting-301:14
*** salv-orlando has joined #openstack-meeting-301:15
*** salv-orlando has quit IRC01:20
*** milan has quit IRC01:25
*** eliqiao has quit IRC01:29
*** milan has joined #openstack-meeting-301:31
*** eliqiao has joined #openstack-meeting-301:33
*** sdake has joined #openstack-meeting-301:33
*** milan has quit IRC01:36
*** sdake_ has joined #openstack-meeting-301:50
*** milan has joined #openstack-meeting-301:51
*** sdake has quit IRC01:52
*** milan has quit IRC01:55
*** yamamoto has joined #openstack-meeting-302:02
*** milan has joined #openstack-meeting-302:11
*** zz_dimtruck is now known as dimtruck02:12
*** salv-orlando has joined #openstack-meeting-302:16
*** salv-orlando has quit IRC02:21
*** milan has quit IRC02:25
*** VW has joined #openstack-meeting-302:26
*** sdake_ has quit IRC02:29
*** VW has quit IRC02:30
*** mickeys has quit IRC02:31
*** milan has joined #openstack-meeting-302:31
*** _Fdaisuke_ has joined #openstack-meeting-302:39
*** mickeys has joined #openstack-meeting-302:39
*** milan has quit IRC02:40
*** Fdaisuke_ has quit IRC02:42
*** s3wong has quit IRC02:45
*** sdake has joined #openstack-meeting-302:49
*** milan has joined #openstack-meeting-302:51
*** milan has quit IRC02:55
*** milan has joined #openstack-meeting-303:11
*** milan has quit IRC03:25
*** milan has joined #openstack-meeting-303:31
*** prateek has quit IRC03:36
*** prateek has joined #openstack-meeting-303:36
*** milan has quit IRC03:40
*** prateek has quit IRC03:45
*** milan has joined #openstack-meeting-303:51
*** milan has quit IRC03:55
*** dimtruck is now known as zz_dimtruck04:00
*** zz_dimtruck is now known as dimtruck04:04
*** baoli has joined #openstack-meeting-304:10
*** milan has joined #openstack-meeting-304:11
*** baoli has quit IRC04:15
*** spzala has quit IRC04:16
*** psachin has joined #openstack-meeting-304:16
*** salv-orlando has joined #openstack-meeting-304:17
*** salv-orlando has quit IRC04:21
*** milan has quit IRC04:30
*** milan has joined #openstack-meeting-304:31
*** milan has quit IRC04:48
*** cartik has joined #openstack-meeting-304:50
*** milan has joined #openstack-meeting-304:51
*** milan has quit IRC04:55
*** VW has joined #openstack-meeting-305:00
*** reedip has joined #openstack-meeting-305:05
*** milan has joined #openstack-meeting-305:11
*** milan has quit IRC05:26
*** milan has joined #openstack-meeting-305:31
*** gouthamr has joined #openstack-meeting-305:36
*** milan has quit IRC05:41
*** pgadiya has joined #openstack-meeting-305:41
*** prateek has joined #openstack-meeting-305:44
*** s3wong has joined #openstack-meeting-305:46
*** milan has joined #openstack-meeting-305:51
*** pgadiya has quit IRC05:51
*** VW has quit IRC05:55
*** milan has quit IRC06:00
*** pgadiya has joined #openstack-meeting-306:05
*** gouthamr has quit IRC06:06
*** dimtruck is now known as zz_dimtruck06:08
*** milan has joined #openstack-meeting-306:12
*** kenji-i has joined #openstack-meeting-306:16
*** amotoki has joined #openstack-meeting-306:22
*** milan has quit IRC06:25
*** milan has joined #openstack-meeting-306:31
*** lpetrut has joined #openstack-meeting-306:36
*** milan has quit IRC06:40
*** salv-orlando has joined #openstack-meeting-306:43
*** usman has joined #openstack-meeting-306:46
*** zz_dimtruck is now known as dimtruck06:51
*** milan has joined #openstack-meeting-306:51
*** pcaruana has joined #openstack-meeting-306:51
*** milan has quit IRC06:55
*** dimtruck is now known as zz_dimtruck06:57
*** nkrinner_afk has quit IRC06:59
*** nkrinner has joined #openstack-meeting-306:59
*** milan has joined #openstack-meeting-307:11
*** milan has quit IRC07:25
*** lpetrut has quit IRC07:27
*** milan has joined #openstack-meeting-307:31
*** mickeys has quit IRC07:33
*** salv-orlando has quit IRC07:39
*** milan has quit IRC07:41
*** milan has joined #openstack-meeting-307:51
*** s3wong has quit IRC07:52
*** VW has joined #openstack-meeting-307:55
*** milan has quit IRC07:56
*** cartik has quit IRC07:59
*** matrohon has joined #openstack-meeting-307:59
*** VW has quit IRC08:00
*** milan has joined #openstack-meeting-308:11
*** rmart04 has joined #openstack-meeting-308:21
*** milan has quit IRC08:26
*** milan has joined #openstack-meeting-308:31
*** mickeys has joined #openstack-meeting-308:33
*** mickeys has quit IRC08:39
*** milan has quit IRC08:41
*** tuanluong has joined #openstack-meeting-308:45
*** anilvenkata has joined #openstack-meeting-308:45
*** usman has left #openstack-meeting-308:49
*** salv-orlando has joined #openstack-meeting-308:49
*** milan has joined #openstack-meeting-308:51
*** cartik has joined #openstack-meeting-308:53
*** milan has quit IRC08:56
*** iyamahat has joined #openstack-meeting-309:01
*** pgadiya has quit IRC09:02
*** iyamahat has quit IRC09:04
*** milan has joined #openstack-meeting-309:12
*** pgadiya has joined #openstack-meeting-309:17
*** lpetrut has joined #openstack-meeting-309:21
*** milan has quit IRC09:26
*** calbers has joined #openstack-meeting-309:30
*** mickeys has joined #openstack-meeting-309:36
*** mickeys has quit IRC09:41
*** salv-orl_ has joined #openstack-meeting-309:53
*** salv-orlando has quit IRC09:56
*** tobberydberg_ has joined #openstack-meeting-310:08
*** milan has joined #openstack-meeting-310:10
*** tobberydberg_ is now known as tobberydberg10:12
*** anilvenkata has quit IRC10:17
*** tuanluong has quit IRC10:21
*** zhurong has joined #openstack-meeting-310:26
*** anilvenkata has joined #openstack-meeting-310:29
*** ociuhandu has quit IRC10:31
*** hoangcx has quit IRC10:35
*** armax has joined #openstack-meeting-310:36
*** mickeys has joined #openstack-meeting-310:37
*** pgadiya has quit IRC10:38
*** mickeys has quit IRC10:41
*** yamahata has quit IRC10:42
*** yamamoto has quit IRC10:47
*** pgadiya has joined #openstack-meeting-310:51
*** shinya_kwbt has quit IRC10:52
*** tobberydberg has quit IRC10:53
*** huanxuan has quit IRC11:03
*** sdague has joined #openstack-meeting-311:04
*** sambetts|afk is now known as sambetts11:04
*** salv-orl_ has quit IRC11:05
*** matrohon has quit IRC11:09
*** zhurong has quit IRC11:19
*** milan is now known as food|milan11:23
*** salv-orlando has joined #openstack-meeting-311:28
*** anilvenkata has quit IRC11:32
*** mickeys has joined #openstack-meeting-311:38
*** yamamoto has joined #openstack-meeting-311:40
*** mickeys has quit IRC11:42
*** yamamoto has quit IRC11:46
*** anilvenkata has joined #openstack-meeting-311:46
*** yamamoto has joined #openstack-meeting-311:47
*** sdake has quit IRC11:49
*** huanxuan has joined #openstack-meeting-311:50
*** yamamoto has quit IRC11:51
*** sankarshan_away is now known as sankarshan12:03
*** neiljerram has joined #openstack-meeting-312:07
*** yamamoto has joined #openstack-meeting-312:17
*** rtheis has joined #openstack-meeting-312:26
*** alexismonville has joined #openstack-meeting-312:29
*** cartik has quit IRC12:30
*** rtheis_ has joined #openstack-meeting-312:30
*** rtheis has quit IRC12:33
*** mickeys has joined #openstack-meeting-312:39
*** rtheis has joined #openstack-meeting-312:40
*** rtheis_ has quit IRC12:42
*** yamamoto has quit IRC12:42
*** mickeys has quit IRC12:43
*** tobberydberg has joined #openstack-meeting-312:52
*** salv-orlando has quit IRC12:56
*** zhurong has joined #openstack-meeting-312:56
*** matrohon has joined #openstack-meeting-312:59
*** psachin has quit IRC13:00
*** psachin has joined #openstack-meeting-313:00
*** rmart04_ has joined #openstack-meeting-313:05
*** pgadiya has quit IRC13:05
*** rmart04 has quit IRC13:06
*** rmart04_ is now known as rmart0413:06
*** bobmel has joined #openstack-meeting-313:06
*** salv-orlando has joined #openstack-meeting-313:07
*** bobmel has quit IRC13:11
*** rmart04_ has joined #openstack-meeting-313:14
*** rmart04 has quit IRC13:15
*** rmart04_ is now known as rmart0413:15
*** yamamoto has joined #openstack-meeting-313:16
*** sdake has joined #openstack-meeting-313:16
*** tongli has joined #openstack-meeting-313:28
*** yamamoto has quit IRC13:28
*** mickeys has joined #openstack-meeting-313:39
*** prateek has quit IRC13:41
*** food|milan is now known as milan13:41
*** mickeys has quit IRC13:44
*** reedip_ has joined #openstack-meeting-313:47
*** logan- has joined #openstack-meeting-313:48
*** seanhandley has joined #openstack-meeting-313:50
*** zhipengh has joined #openstack-meeting-313:51
*** stevejims has joined #openstack-meeting-313:51
*** shinya_kwbt has joined #openstack-meeting-313:57
*** mattjarvis has joined #openstack-meeting-313:58
*** zhipengh has quit IRC14:00
mattjarvishello all14:00
seanhandleyhi matt14:00
mattjarvishey seanhandley !14:00
seanhandleySorry for missing the last one14:01
seanhandleyand happy new year!14:01
mattjarvissame to you :)14:01
tobberydbergHi!14:01
serverascodehi14:01
mattjarvishi serverascode hi tobberydberg14:01
tobberydbergA few more this time =)14:01
*** jjung has joined #openstack-meeting-314:01
mattjarvisyup, let's give it a couple of minutes before we start14:01
mattjarvisto give others a chance14:02
tobberydbergabsolutely14:02
rmart04Afternoon chaps14:03
rmart04(& and ladies!)14:03
mattjarvisok, lets get started then14:03
mattjarvis#startmeeting Public Cloud WG14:03
openstackMeeting started Wed Jan  4 14:03:47 2017 UTC and is due to finish in 60 minutes.  The chair is mattjarvis. Information about MeetBot at http://wiki.debian.org/MeetBot.14:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:03
*** openstack changes topic to " (Meeting topic: Public Cloud WG)"14:03
openstackThe meeting name has been set to 'public_cloud_wg'14:03
mattjarvisfirstly could everyone add their names to the ether pad attendees https://etherpad.openstack.org/p/publiccloud-wg14:04
*** zhipengh has joined #openstack-meeting-314:04
zhipenghhello14:05
mattjarvisstill quite a few down on the first meeting - hope others will join later14:05
mattjarvishi zhipengh14:05
*** aemile has joined #openstack-meeting-314:05
zhipenghhappy new year :)14:05
*** sankarshan is now known as sankarshan_away14:05
mattjarvissame to you :)14:06
*** reedip_outofmemo has joined #openstack-meeting-314:06
*** aemile has quit IRC14:06
*** yankcrime has joined #openstack-meeting-314:06
yankcrimeo/14:06
mattjarvishello nick14:06
* yankcrime really should put this in his diary14:06
mattjarvis#topic Time length for chair voting14:07
*** openstack changes topic to "Time length for chair voting (Meeting topic: Public Cloud WG)"14:07
mattjarvisjust a quick note, it's the participants section at the top of the ether pad, some folks are using the one from the last meeting14:07
mattjarvisso, on to voting for chairs14:07
mattjarvisthe Doodle poll has now been open for 15 days14:08
mattjarvisand we have 21 participants14:08
*** shinya_kwbt has quit IRC14:08
mattjarvisare we happy to close the poll now, or does anyone want to run longer ?14:08
*** baoli has joined #openstack-meeting-314:09
mattjarvisany thoughts either way ?14:09
*** baoli has quit IRC14:09
tobberydbergFine to close for me14:10
zhipenghi think we could close the polls now or by the end of this week14:10
mattjarvisok, let's put it to a vote then ( if I can remember the IRC fu )14:10
zhipenghi think we could close the polls now or by the end of this week14:10
*** baoli has joined #openstack-meeting-314:10
rmart04Have you got a link for that poll, didn’t see it on the etherpad14:10
rmart04can flick through the mailing list14:11
tobberydberghttp://doodle.com/poll/s63r5s4ghyucmnqu14:11
yankcrimei reckon a couple of weeks would usually have been sufficient, but given it's been holiday season leaving it to run until the end of the week seems reasonable to me14:11
mattjarvishttp://beta.doodle.com/poll/s63r5s4ghyucmnqu#table14:11
rmart04thanks14:11
mattjarvisyankcrime, that seems reasonable14:11
mattjarvisso lets vote for the end of the week14:12
zhipenghagree yankcrime14:12
mattjarvis#vote14:12
mattjarvis#startvote close the chair poll on Friday 4th Jan ? Yes, No14:12
openstackBegin voting on: close the chair poll on Friday 4th Jan ? Valid vote options are Yes, No.14:12
openstackVote using '#vote OPTION'. Only your last vote counts.14:12
mattjarvis#vote Yes14:12
*** julim has joined #openstack-meeting-314:12
yankcrime#vote yes14:13
tobberydberg#vote Yes14:13
zhipengh#vote yes14:13
tobberydberg...even though Friday is the 6th ;-)14:13
mattjarvissorry my bad :(14:13
mattjarviscorrection for the logs - Friday is the 6th Jan14:14
seanhandley#vote yes14:14
tobberydbergHehe, np14:14
zhipenghwe don't need a recount :P14:14
mattjarvis#endvote14:14
openstackVoted on "close the chair poll on Friday 4th Jan ?" Results are14:14
openstackYes (5): zhipengh, yankcrime, mattjarvis, seanhandley, tobberydberg14:14
mattjarvisok, carried :)14:14
mattjarvisI will close on Friday14:14
mattjarvis#topic Work output to create definitions and consituency on wiki page14:15
*** openstack changes topic to "Work output to create definitions and consituency on wiki page (Meeting topic: Public Cloud WG)"14:15
mattjarvisit would be good to get this put to bed now, we have some content added to the etherpad14:15
*** salv-orlando has quit IRC14:17
*** salv-orlando has joined #openstack-meeting-314:17
mattjarvisis everyone happy with the definitions section ? ( under Who is our Constituency )14:17
mattjarvisand I think we all agreed that we wouldn't necessarily be bound by the Marketplace14:17
mattjarvisone issue with not having the MP as part of the definition is that we now include operators who don't have the Powered by OpenStack certification14:18
yankcrimei like the NIST definition tbh14:18
mattjarvis+114:19
yankcrimenot sure i agree with the 'full api access' statement though14:19
zhipenghI agree that we should not be bound with MP14:19
mattjarvisyankcrime, can you explain a bit more ?14:19
yankcrimecould be public operators that can't provide 'full api access' for one reason or another, but those reasons could be of wider value14:20
zhipenghfull api access meaning full OpenStack API access ?14:20
serverascodefull api might not be the right phrase, publicly accessible api is what is meant?14:21
mattjarvisI think the intention of that statement was about OpenStack API's as opposed to proprietary wrappers14:21
yankcrimein which case you'd be excluding rackspace surely14:21
mattjarvisserverascode, yes I think so14:21
zhipenghsome of the apis will not be publicly accessable in nature (for public clouds)14:22
yankcrimeserverascode: that'd be ok14:22
tobberydbergPublic accessible native OpenStack APIs14:22
mattjarvistobberydberg, +114:22
mattjarviswould you mind updating the ether pad with that suggestion ?14:23
zhipengh+114:23
*** lblanchard has joined #openstack-meeting-314:23
tobberydbergSure!14:23
rmart04Happy wih the definition, aggree with YC.14:23
zhipenghjust don't restrict it to only native APIs14:23
yankcrimei think "publicly accessible apis" is sufficient14:23
mattjarvisok, I think there is enough there to create a definition and constituency section on the wiki14:24
mattjarviswould anyone like to take an action to take that and create something on our wiki page ?14:24
mattjarvishttps://wiki.openstack.org/wiki/PublicCloudWorkingGroup14:25
*** psachin has quit IRC14:25
mattjarvislol, ok I will take that as an action14:25
yankcrimei'm happy to write something up14:25
mattjarvissold14:25
yankcrimelol14:25
mattjarvis#action yank crime to create a consituency/definitions section on the wiki based on the content in the etherpad14:26
zhipenghwe need to agree the content in the etherpad, right ?14:26
*** bklei has joined #openstack-meeting-314:26
mattjarvissorry, yes let's make sure we are in agreement on that14:27
mattjarviswe are just talking about the Who is our Consituency section14:27
*** salv-orlando has quit IRC14:27
mattjarvis#startvote are we happy with the content in the constituency section being used to seed the wiki ? Yes, No14:28
openstackBegin voting on: are we happy with the content in the constituency section being used to seed the wiki ? Valid vote options are Yes, No.14:28
openstackVote using '#vote OPTION'. Only your last vote counts.14:28
mattjarvis#vote yes14:28
mattjarvis#vote Yes14:28
rmart04#vote Yes14:28
yankcrime#vote yes14:29
zhipengh#vote yes14:29
tobberydberg#vote Yes14:29
serverascode#vote yes14:29
mattjarvisany more ?14:29
mattjarvis#endvote14:29
openstackVoted on "are we happy with the content in the constituency section being used to seed the wiki ?" Results are14:29
openstackYes (6): rmart04, yankcrime, mattjarvis, tobberydberg, zhipengh, serverascode14:29
seanhandley#vote yes14:30
mattjarvis#topic Discuss purpose and goals14:30
*** openstack changes topic to "Discuss purpose and goals (Meeting topic: Public Cloud WG)"14:30
seanhandleyDamn. Need to be quicker on the draw.14:30
mattjarvissorry :(14:30
seanhandleyresounding yes anyway :)14:30
seanhandleymy bad - I'll be quicker14:30
mattjarvisso I think we have a pretty good definition of purpose in the section titled "Splitted concept of representation"14:31
mattjarviswhich Mariano from Enter provided I think14:31
mattjarvisand there is also some concepts under " Purpose of the publiccloud-wg" at the bottom14:31
mattjarviscould I ask that we all review both of those sections, add any new thoughts, and then we'll vote on adding that to the wiki also ?14:32
tobberydbergAgree that "Splitted concept of representation" looks good!14:32
mattjarvisI'll give everyone a couple of minutes to look at those sections14:32
*** qwebirc40067 has joined #openstack-meeting-314:32
mattjarvisI think they probably need merging together and a bit of editing, but I agree14:33
zhipenghtrue that14:34
yankcrimelgtm14:34
mattjarvisok, so lets vote on moving that section forward14:36
mattjarvis#startvote are we happy with the content we currently have to describe the purpose of the WG ? Yes, No14:36
openstackBegin voting on: are we happy with the content we currently have to describe the purpose of the WG ? Valid vote options are Yes, No.14:36
openstackVote using '#vote OPTION'. Only your last vote counts.14:36
mattjarvis#vote Yes14:36
yankcrime#yes14:36
yankcrime#vote yes14:36
zhipengh#vote yes14:37
seanhandley#vote yes14:37
tobberydberg#vote Yes14:37
serverascode#vote yes14:37
mattjarvisany more ?14:38
mattjarvis#endvote14:38
openstackVoted on "are we happy with the content we currently have to describe the purpose of the WG ?" Results are14:38
openstackYes (6): seanhandley, yankcrime, mattjarvis, tobberydberg, zhipengh, serverascode14:38
mattjarviswould anyone else like to take an action to distill those sections down into a Purpose section on the wiki ?14:38
mattjarvisI am happy to do so14:39
zhipenghI could help14:39
mattjarvisplease feel free zhipengh14:39
mattjarvishow about you take a first pass, and we can collaborate if needed afterwards ?14:39
zhipenghno problem14:40
mattjarvis#action zhipengh to distill Purpose sections down into a section on the wiki14:40
mattjarvistx :)14:40
*** mickeys has joined #openstack-meeting-314:40
mattjarvisso the last thing I wanted us to talk about today was about goals14:40
mattjarvisthere are obviously the overarching things which we have outlined under purpose14:41
mattjarvisbut taking input from others, the most successful working groups have set themselves achievable sets of goals within the release cycle timeframe14:41
mattjarvishere is what David Flanders sent to me this week regarding this :14:42
mattjarvisæFirst task is really to get two dedicated co-chairs who are going to be committed to bringing the group together via the regular drum-beat of IRC meetings.  Second is having a good scoping document 9slides) to announce at the forum(summit) along with 1-3 small activities.  That is about as much as you can hope for, a good start with some clear trajectories."14:42
mattjarvisthis sounds like a reasonable set of milestones to work towards initially14:42
tobberydbergagree14:43
zhipenghagree14:43
mattjarviswe obviously have the first underway, the second is tied up with some of the work we've just done on creating wiki content and defining things14:43
mattjarvisdoes anyone have any further thoughts on the third ?14:44
mattjarvisit's worth reading the "Things which public cloud have achieved this year" section on the etherpad14:44
mattjarviswhich does focus a lot on the app dev stuff, but still valid points14:45
*** mickeys has quit IRC14:45
*** VW has joined #openstack-meeting-314:45
mattjarvispersonally I'd be looking for SMART goals14:45
mattjarvisand fairly small scope for the first iteration14:46
*** cleong has joined #openstack-meeting-314:46
mattjarvisone thing that did seem achievable and fairly self contained was to produce some case studies14:47
mattjarviswhich could then become part of a larger white paper14:47
zhipenghhow should we categorize the cases ?14:48
*** VW has quit IRC14:48
*** VW has joined #openstack-meeting-314:48
mattjarvisI was thinking that if we could provide 3-4 case studies for large customers who use public cloud openstack and why they use it - along with any challenges that customer creates for the provider ?14:49
mattjarvisI can definitely think of 2 customers from DataCentred who would be interesting14:49
*** rhochmuth has joined #openstack-meeting-314:49
zhipenghI could have some from OTC customers I think14:50
*** bogdando has quit IRC14:50
mattjarvisif the selection could be cross-industry that would also be interesting I think14:50
mattjarvisso customers from different sectors14:50
zhipenghwe should also decide on a template for the case study document14:51
tobberydbergLike your suggestion Matt14:51
zhipenghwhat sections we should include in it for example14:51
mattjarviszhipengh, I agree14:52
mattjarviscould you add that to the ether pad so we capture it14:52
*** baoli has quit IRC14:52
yankcrimedeffo agree with case studies that speak to openstack's strengths for public cloud in general14:52
*** Fdaisuke has joined #openstack-meeting-314:52
mattjarviscoming back to Flanders suggestions - I think what we are talking about here is what he has under section e.14:53
mattjarvisI think we could also contribute to section d. - update, testing and screencasts of how various cloud app interfaces work atop openstack14:53
mattjarvisand to section c.14:53
mattjarvisparticipation at the summit OpenStack Academy* acting as mentors during the 'Training Games' and self-paced 'Cloud App Labs' lounge14:54
tobberydbergYes, participating and the OpenStack Academy with resources to execute sessions, labs or hackatons?14:55
mattjarvistobberydberg, yes exactly14:55
tobberydbergYes, participating and provide the OpenStack Academy with resources to execute sessions, labs or hackatons?14:56
tobberydberg...some lost words...14:56
*** rbak has joined #openstack-meeting-314:56
mattjarvisand also that would play into doing some work on section d. so that we ensure things actually work reliably across clouds14:56
mattjarvisso we are coming up to the hour now14:57
mattjarvisdoes anyone have any final thoughts for this weeks meeting ?14:57
mattjarvisI suggest we add the case study discussion to the agenda for next meeting, as it seems we are all fairly in agreement14:58
yankcrimeyeah, agreed14:58
*** baoli has joined #openstack-meeting-314:58
seanhandleysounds good mattjarvis14:58
*** bogdando has joined #openstack-meeting-314:58
tobberydbergagree14:58
zhipenghagree14:58
mattjarvisthank you all for your input - I think we've made progress this meeting. By next time we should have some additional wiki content and some other chairs !14:59
yankcrimethanks mattjarvis14:59
mattjarvis#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Wed Jan  4 14:59:20 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/public_cloud_wg/2017/public_cloud_wg.2017-01-04-14.03.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/public_cloud_wg/2017/public_cloud_wg.2017-01-04-14.03.txt14:59
*** witek has joined #openstack-meeting-314:59
openstackLog:            http://eavesdrop.openstack.org/meetings/public_cloud_wg/2017/public_cloud_wg.2017-01-04-14.03.log.html14:59
tobberydbergThank you!14:59
zhipenghthx everyone :)14:59
*** shinya_kwbt has joined #openstack-meeting-315:00
rhochmuth#startmeeting monasca15:01
openstackMeeting started Wed Jan  4 15:01:24 2017 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: monasca)"15:01
openstackThe meeting name has been set to 'monasca'15:01
rhochmutho/15:01
*** logan- has left #openstack-meeting-315:01
rbako/15:01
*** yankcrime has left #openstack-meeting-315:01
rhochmuthhttps://etherpad.openstack.org/p/monasca-team-meeting-agenda15:01
qwebirc40067o/15:01
bkleio/15:02
*** zhipengh has left #openstack-meeting-315:02
rhochmuthSome folks might still be out for the holidays so toadya's session might be light15:02
rhochmuthHere is the agenda15:02
rhochmuthAgenda for Wednesday January 4 2016 (15:00 UTC)15:02
rhochmuth1.Storyboard Project for Monasca?15:02
rhochmuth2.Anyone going to PTG? https://www.openstack.org/ptg/ 15:02
rhochmuth3.Release dates15:02
shinya_kwbto/15:03
rhochmuthso, let's get started15:03
rhochmuth#topic Storyboard Project for Monasca?15:03
*** openstack changes topic to "Storyboard Project for Monasca? (Meeting topic: monasca)"15:03
*** rmart04 has quit IRC15:03
rhochmuthWho would like to discuss this?15:03
stevejimsHi, this was mine15:04
rhochmuthstevejims: you have the floor15:04
stevejimsWas looking to create a storing for logging API to Storyboard, but I think a Monasca project needs to be created15:04
stevejimswasn't sure who was the right person to ask15:04
stevejims*story15:04
rhochmuthahhh, this is coming back15:05
rhochmuthyou were going to work on a query api15:05
rhochmuthand we sent you off to look at storyboard without knowing what that involved15:05
stevejimsYeah, we decided to try using Storyboard instead of a blueprint15:05
*** baoli has quit IRC15:05
rhochmuthunfortunately, i don't know what is involved either15:05
stevejimsha, yeah, all is forgiven15:06
*** rmart04 has joined #openstack-meeting-315:06
rhochmuthdoeas anyone else have any thoughts15:06
rhochmuthi don't want to hold up the process15:06
*** zhurong has quit IRC15:06
stevejimsLooks fairly straightforward to create stories and such, but need a project to attach stories to by the looks of it15:06
bkleii like the idea, just took a brief tour of it -- no objections15:06
rhochmuthi started to look at storyboard before the holidays and tried to track down what to do next15:07
rhochmuthunfortunately, i didn't find the details i was looking for15:07
witekI don't see the place where the project could be created15:07
rhochmuthhttps://wiki.openstack.org/wiki/StoryBoard15:08
rhochmuthhttp://docs.openstack.org/infra/storyboard/15:08
stevejimsYeah witek, I couldn't either15:08
rhochmuthhttp://docs.openstack.org/infra/storyboard/webapi/v1.html15:08
*** VW has quit IRC15:08
rhochmuththose are the links i saw15:08
*** baoli has joined #openstack-meeting-315:08
rhochmuthbut nothing on how to get started with a new project15:08
*** VW has joined #openstack-meeting-315:09
stevejimsThe API indicates only "admin" users can create projects, guess we have to find one of those15:09
witekthey have a meeting at #openstack-meeting just now, I reckon15:09
*** corey_ has joined #openstack-meeting-315:09
*** corey_ is now known as Guest4114715:09
*** rhochmuth1 has joined #openstack-meeting-315:11
*** cleong has quit IRC15:11
*** zz_dimtruck is now known as dimtruck15:12
rhochmuth1i can follow-up in irc or someone else can15:12
rhochmuth1There is this link too, https://github.com/openstack-infra/storyboard15:12
*** armax_ has joined #openstack-meeting-315:12
witekand  #storyboard15:12
rhochmuthi think the only other idea is to ask in the irc room15:13
rhochmuthfor some pointers15:13
rhochmuthif that doesn't go well, then probably should just go back to using launchpad15:13
*** VW has quit IRC15:13
*** rhochmuth has quit IRC15:13
*** armax has quit IRC15:13
*** calbers has quit IRC15:13
*** armax_ is now known as armax15:13
bkleiagree15:13
*** VW has joined #openstack-meeting-315:13
rhochmuth1stevejims: Do you want to follow-up in irc, or would you prefer that i do that15:13
*** wanghuagong has joined #openstack-meeting-315:13
*** calbers has joined #openstack-meeting-315:14
stevejimsHappy to enquire sure15:14
*** tongli has quit IRC15:14
rhochmuth1thx15:15
rhochmuth1if you need me to do anything please let me know15:15
stevejimsOK will do - how is best to get in touch?15:15
rhochmuth1for example, there might be a project that i need to submit a review to to addmonasca to storyboard15:15
rhochmuth1i'm also wondering what their recommendations are at this time15:16
*** spzala has joined #openstack-meeting-315:16
witekyou mean, what should be tracked with storyboard and what not?15:16
rhochmuth1correct15:16
rhochmuth1like how to use the tool15:16
rhochmuth1tutorial15:17
rhochmuth1guidelines15:17
rhochmuth1...15:17
witekyes, would be useful15:17
stevejimswitek - we were going to collaborate on some ideas for logging API - until we get the storyboard setup, how best would it be to coordinate - blueprint/email?15:17
rhochmuth1stevejims: rhochmuth in irc, or roland dot hochmuth at hpe dot com15:18
witekthe same for me15:18
stevejimsIRC, yes?15:19
witekand email15:19
*** mattjarvis has quit IRC15:19
rhochmuth1moving onto next topi15:20
stevejimsOK will do - thanks guys15:20
rhochmuth1thanks15:20
rhochmuth1#topic Anyone going to PTG? https://www.openstack.org/ptg/ 15:21
rhochmuth1yes, there are some folks going15:21
bkleirbak and myself are planning on going15:21
rhochmuth1who asked the question?15:21
bkleiwondering if it'll just be us staring at each other15:21
bkleime15:21
witekI won't be going, as of now15:22
bkleianyone else besides charter?15:22
shinya_kwbtI probably can't go this time.15:22
rhochmuth1i believe joachime from SAP might be going15:23
rhochmuth1sorry, joachim15:23
rhochmuth1that is all i know about15:23
bkleiany hpe?15:24
rhochmuth1i'm not exactly sure15:24
rhochmuth1most of the team involved in openstack is about to be transferred to SUSE15:24
*** huanxuan_ has joined #openstack-meeting-315:25
rhochmuth1I would expect involvement from SUSE15:25
rhochmuth1but, i don't know15:25
rhochmuth1i'll try and track down if there are any folks from the SUSE side that will be attending15:25
bkleicool15:25
rhochmuth1right now i don't have plans to attend either15:26
rhochmuth1but, i think we should look into a mid-cycle15:26
rhochmuth1a remote mid-cycle15:26
bkleiagree15:27
*** ativelkov_ has quit IRC15:27
*** huanxuan has quit IRC15:27
rhochmuth1i was wondering about projects instrumenting themselves15:27
*** srobert has joined #openstack-meeting-315:27
rhochmuth1possibly using the Prometheus Python client library15:28
*** wanghuagong has quit IRC15:28
*** Fdaisuke has quit IRC15:28
rhochmuth1or by developing a wrapper, possibly an oslo wrapper, that could be used to plugin Prometheus, Statsd or something else15:28
*** Guest66666 has quit IRC15:29
rhochmuth1i'm also wondering about involvement with other projects such as congress, watcher, vitrage, openstack ansible, …15:29
*** Guest66666 has joined #openstack-meeting-315:29
*** absubram has joined #openstack-meeting-315:30
rhochmuth1#topic Release dates15:30
rhochmuth1witek: Did you add this?15:30
witekyes15:30
witekwe are approaching the next dates in Ocata release15:31
*** rmart04 has quit IRC15:31
witekThe deadline for non-client library releases is R-5 (19 Jan)15:31
witekit is especially relevant for monasca-statsd, I think15:31
*** baoli has quit IRC15:31
witekas it has cross-dependencies15:32
*** ativelkov has joined #openstack-meeting-315:32
witekif I understand it correctly, we should have the final version of monasca-statsd for Ocata on 19 Jan15:33
*** wh has joined #openstack-meeting-315:34
rhochmuth1https://review.openstack.org/#/q/project:openstack/monasca-statsd+status:open15:34
*** spotz_zzz is now known as spotz_15:35
rhochmuth1Looks like mostly small items to possibly get in15:36
rhochmuth1if possible15:36
rhochmuth1this review looks like a good one to merge, https://review.openstack.org/#/c/407879/15:36
rhochmuth1this review is ready, https://review.openstack.org/#/c/356434/15:37
rhochmuth1The bot wants to remove the datadog copyright, https://review.openstack.org/#/c/394575/5/setup.py15:37
dirkrhochmuth1: yeah, I was wondering about that one, why -2'ing that?15:37
rhochmuth1i -2'd that review, because of the issues we ran into earlier15:38
dirkit certainly doesn't look like datadog did any copyrightable changes to that file15:38
*** srobert has quit IRC15:38
rhochmuth1well, technically, i think we could remove the copyright15:38
dirkright, since its coming from glocal requirements15:39
dirkglobal15:39
rhochmuth1i was just being cautious15:39
rhochmuth1since the agent and statsd was forked from datadog15:39
rhochmuth1and we recently had to address some issues aroudn this15:40
dirkright, but this file was not forked from them15:41
rhochmuth1i just changed to a +115:41
*** mickeys has joined #openstack-meeting-315:41
dirkbtw, is there a specific reason this still uses nosetests?15:41
rhochmuth1no reason, just technical debt15:41
*** rbak_ has joined #openstack-meeting-315:43
*** salv-orlando has joined #openstack-meeting-315:43
*** huanxuan has joined #openstack-meeting-315:43
witekthe next upcoming date is 26 Jan15:43
rhochmuth1witek: laszlo has this review up at, https://review.openstack.org/#/c/356469/15:43
rhochmuth1and this one too, https://review.openstack.org/#/c/356507/15:44
*** huanxuan_ has quit IRC15:44
rhochmuth1so, those would be nice to get merged15:44
witekI could have a look next week15:44
witekactually still in vacation now15:45
rhochmuth1ok, no problem, thanks for connecting in15:45
*** mickeys has quit IRC15:45
witekbut I'll ping Tomasz and Artur15:45
*** reedip_ has quit IRC15:45
rhochmuth1thx15:45
rhochmuth1i guess that is the end of the agenda15:46
witekOcata 3 Milestone, with Feature and Requirements Freezes: 26 Jan15:46
rhochmuth1sorry15:46
witek:)15:46
rhochmuth1you had other dates15:46
witekthat was the last one15:46
*** rbak has quit IRC15:46
rhochmuth1January 26th, already15:46
rhochmuth1So, is that meant to be a functional complete date for new features?15:47
witek No featureful patch should be landed after this point.15:47
*** salv-orlando has quit IRC15:48
rhochmuth1so, that leaves 3 weeks of development15:49
rhochmuth1that is not very much time15:49
witekI think we can be more flexible with most of the projects, as we don't have many cross-dependencies15:50
witekbut e.g. python-monascaclient has15:50
rhochmuth1thx witek15:52
*** marst has joined #openstack-meeting-315:52
rhochmuth1any other updates or topics to discuss15:52
rhochmuth1i guess we can end the meeting early then15:54
rhochmuth1thanks everyone15:54
witekthank you15:54
rhochmuth1#endmeeting15:54
*** wh has quit IRC15:54
bkleithx15:55
*** bklei has quit IRC15:55
*** caboucha has joined #openstack-meeting-315:55
shinya_kwbtwhy there is no minutes?15:55
shinya_kwbtI got it rhochmuth1 name was changed.15:56
dirkbecause rhochmuth needs to end the meeting15:56
dirkrhochmuth1: can you rename yourself and end it ? :)15:56
*** tobberydberg has quit IRC15:56
*** qwebirc40067 has quit IRC15:59
*** catherine has joined #openstack-meeting-315:59
*** catherine is now known as Guest5447016:00
markvoelker#startmeeting interopwg16:00
openstackmarkvoelker: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.16:00
markvoelkerUh-oh?16:00
*** milan is now known as milan|mgt16:00
*** yamahata has joined #openstack-meeting-316:00
*** Marcellin__ has joined #openstack-meeting-316:01
*** witek has quit IRC16:01
*** diablo_rojo_phon has joined #openstack-meeting-316:01
markvoelkerah, seems rhochmuth1 left the previous meeting open16:01
shinya_kwbtprevious meeting was ended. Could you end meeting?16:01
*** shamail has joined #openstack-meeting-316:01
markvoelkerI don't have the necessary superpowers, but let me ping infra and see if someone there does16:02
shinya_kwbtthx.16:02
*** cleong has joined #openstack-meeting-316:02
*** jjung has quit IRC16:02
*** Guest54470 has quit IRC16:03
*** Guest41147 has quit IRC16:03
*** catherineD_ has joined #openstack-meeting-316:03
*** pabelanger has joined #openstack-meeting-316:05
pabelanger#endmeeting16:06
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:06
openstackMeeting ended Wed Jan  4 16:06:12 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:06
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-01-04-15.01.html16:06
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-01-04-15.01.txt16:06
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-01-04-15.01.log.html16:06
eglutethanks pabelanger!16:06
markvoelkerThanks pabelanger!16:06
pabelangersure, np16:06
markvoelker#startmeeting interopwg16:06
openstackMeeting started Wed Jan  4 16:06:35 2017 UTC and is due to finish in 60 minutes.  The chair is markvoelker. Information about MeetBot at http://wiki.debian.org/MeetBot.16:06
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:06
*** openstack changes topic to " (Meeting topic: interopwg)"16:06
openstackThe meeting name has been set to 'interopwg'16:06
markvoelker#chair eglute hogepodge16:06
openstackCurrent chairs: eglute hogepodge markvoelker16:06
hogepodgeo/16:06
egluteo/16:06
markvoelkerHappy New Year folks!16:06
shamailHNY16:06
catherineD_o/16:06
markvoelker#link https://etherpad.openstack.org/p/DefCoreRoble.7 Today's agenda16:07
egluteHappy New Year everyone!!16:07
*** pabelanger has left #openstack-meeting-316:07
markvoelkerWe have a fairly short agenda today, so I'd like to take some time to hammer out the final changes for 2017.01.16:07
markvoelkerBut first...16:07
markvoelker#topic User Survey16:07
*** openstack changes topic to "User Survey (Meeting topic: interopwg)"16:07
markvoelkerApparently we have a window (which closes in five days) to submit a question to the user survey16:08
eglutewe have opportunity to add one question!16:08
*** corey_ has joined #openstack-meeting-316:08
egluteany suggestions on what we want to ask?16:08
markvoelkerSo we need to brainstorm fairly quickly on account of everyone being away for the holiday16:08
markvoelker(s)16:08
*** corey_ is now known as Guest4830916:09
*** cleong has quit IRC16:09
markvoelkerLet's use the etherpad for this16:09
*** shinya_kwbt has quit IRC16:09
markvoelkereglute: do we know if there's a particular format or formats we have to adhere to?16:09
eglutemarkvoelker good idea16:09
markvoelkerE.g. can we have open-ended, multiple choice, etc?16:09
eglutewe can determine format16:09
* shamail is in etherpad now16:10
shamailUsually the format can be multiple choice or a text box16:10
*** nkrinner is now known as nkrinner_afk16:11
egluteright, different forms of multiple choice or text.16:13
eglutecatherineD_ were you asked to provide a question to user survey as well?16:16
shamailcatherineD_: Does RefStack also get to choice a question?16:16
eglutefor refstack?16:16
shamailjinx!16:16
egluteshamail heheh16:17
hogepodgewe have a question to request test resukts16:17
shamailDo you recall how it’s phrased?  Will it help us identify why people may not be submitting as well?16:17
* catherineD_ on the bus to work .. connection is not good ..sorry16:19
eglutecatherineD_ no worries16:19
markvoelkerOk, looks like the pad is getting quieter and we have 5 or so suggestions.16:19
shamail+116:19
egluteright, lets narrow down16:19
hogepodgeI don't16:19
eglutewe can ask only 1 question. so what is most important?16:20
*** sdague_ has joined #openstack-meeting-316:20
*** huanxuan_ has joined #openstack-meeting-316:20
egluteI like this one: What barriers to interoperability are important to you?16:20
eglutebut we would need good answers to present16:20
markvoelkereglute: we could probably take some of those from the issues report16:20
eglutemarkvoelker agreed16:21
eglutewas just thinking that16:21
eglute"can offer up to six answer options. Use "other" as one of your answer options if you would like to offer an "other" text box."16:21
egluteI like the interop cases question as well16:22
eglutei think we could use our own section in the user survey :)16:22
markvoelkerYeah, I'm wondering if we can sort of already have some clues about that one though16:22
shamailI like the barriers to interop question… it lends itself well to this type of format16:23
*** huanxuan has quit IRC16:23
markvoelkerThe survey already asks some questions about why people are choosing OpenStack, and that question had a lot of those options IIRC16:23
markvoelkerE.g. avoiding vendor lock-in, etc16:23
eglutemarkvoelker good point16:23
egluteneed to look at all the other questions16:23
shamailI also think the question about whether “certification results” are used by customers is important info (e.g. is the Carrot/Stick working beyond vendors) but it is less crucial than the barriers one.16:24
* markvoelker notes that even though he wrote it, he does not like the phrasing of the barriers question and will want to work on that a bit16:24
*** neiljerram has quit IRC16:24
*** neiljerram has joined #openstack-meeting-316:25
eglutehow about we continue thinking about the questions, and then send some options to the mailing list, since we still have a few other things to cover in this meeting?16:25
*** garloff has joined #openstack-meeting-316:25
markvoelkereglute: I was about to suggest the same. =)  Let me record a couple of AI's.16:25
eglutethanks markvoelker16:25
markvoelker#action markvoelker to finalize wording of options and send doodle/email-asking-folks-to-vote-on-pad/etc this evening16:26
markvoelker#action markvoelker to close poll and finalize results by...Friday?16:26
markvoelkerThis seems like it should be a quick and easy thing for folks to vote on by the end of the week...any objections?16:27
* markvoelker hears none16:27
eglutenope16:27
eglutesounds good to me16:28
markvoelkerOk then, let's move on and you can look for an email from me tonight.16:28
eglutethank you markvoelker16:28
markvoelker#topic Finishing Up 2017.0116:28
*** openstack changes topic to "Finishing Up 2017.01 (Meeting topic: interopwg)"16:28
markvoelkerWe're a bit tardy finalizing a few things, so we need to hammer out the last couple of changes in the queue and create the doc for the BoD to review16:28
markvoelkerThe BoD meeting is January 24.16:29
markvoelkereglute: can you confirm if we're on the agenda?  Or has that been set yet?16:29
eglutenot set yet, but i will make sure we are!16:29
markvoelkerok, thanks16:30
markvoelkerSo, I think we just have a few changes left to land...16:30
markvoelker#link https://review.openstack.org/#/c/408427/ Cinder change16:30
*** tonytan4ever has joined #openstack-meeting-316:30
*** catherineD_ has quit IRC16:30
markvoelkerMy only real question on this one was whether or not should include the list-api-versions capability as advisory since there's no test for it16:31
shamailI made the changes to the notes in scoring.txt and also added a note about transition in the description for each capability16:31
markvoelkerIf we knew that was being worked on (or even if there was a bug filed/assigned?) I'd be a bit more comfortable...16:31
eglutei agree16:31
shamailIt’s another one of those markvoelker that highlight the transiition nature16:32
markvoelkerWell, listing api versions should work regardless of whether you're on v2 or v3 (or support both), right?16:32
markvoelkerSo, it's not really dependent on the major version transition, it's just that there's no test?16:32
*** catherineD has joined #openstack-meeting-316:34
markvoelkerThose tests are generally pretty easy to write (having written at least two of them myself)...16:34
hogepodgeI'd rather qualify the advisory as versionless, as tests should work for both v2 and v316:35
*** rhochmuth1 has quit IRC16:35
hogepodgeI see no reason to ever drop v2 support, and the distinction is as confusing as everything else about microversions is16:35
markvoelkerhogepodge: right, the intent here as I interpret it is basically testing GET /16:35
hogepodgeThis is kind of a side issue, in the addition of cinder-v3-* tests as advisory. I'd like to drop the v2 name (I can leave a comment in the review)16:36
hogepodgedrop the v3 name that is16:36
hogepodgeso cinder-*16:36
eglute+116:37
markvoelkerThe last few times we'd discussed this we'd decided to duplicate the names to be clear that we require v3 going forward (see note on line 231 of scoring.txt)16:38
shamaileglute: +116:38
markvoelkerE.g. we require microversion support going forward16:38
eglutemarkvoelker good point16:38
hogepodgethat's exactly what I don't want to do, though. If v2 and v3 are interoperable, we should capture that and not penalize or confuse anyone who's on v216:38
markvoelkerThey're separate endpoints though16:39
garloffhogepodge: +116:39
hogepodgethen we'll have an inflection point where we drop a bunch of interoperable products because they haven't updated fast enough, but not because they're not interoperable16:40
hogepodgebecause the v2/v3 is the only difference, and is highly discoverable16:40
garloffAt some point the API will start to evolve -- then this is the right time to mandate v3, no?16:40
* markvoelker notes that they'd be more discoverable if we had a test for listing api versions per above, but yes16:41
hogepodgeonly if we require capabilities from later microversions16:41
garloffsure16:41
hogepodgewhich will certainly run into loads of scoring issues16:41
markvoelkeryeah, I think that was part of the reason we'd decided to duplicate the names.  At some point we may actually want to drop v2 from being required.16:42
markvoelkerIf we list both explicitly, that's pretty easy to do16:42
markvoelkerIf we don't, we may develop some implicit dependencies on v3216:42
markvoelker*v316:42
hogepodgeI'm willing to be wrong on this, I just want to acknowledge that the strategy for cinder v2 -> v3 was carefully considered by that team to preserve interoperability, and I don't want to ignore the semantics of that effort because of syntax16:42
markvoelkerWe don't necessary have to drop v2 when we make v3 required, either...they can coexist as long as necessary16:43
hogepodgewhat does happen is we require vendors to provide both endpoints then16:43
shamailhogepodge: +116:43
*** sdake has quit IRC16:44
egluteif the cinder team worked hard to preserve interop, then we should drop v2/v3 at some point16:44
markvoelkerhogepodge: ack.  Is that not desirable?  E.g. are tools not told "here's an endpoint, go interact with it"?16:44
hogepodgeI don't want v3 to exclude v2 unnecessarily, that's my main point16:44
egluteuntil we need to introduce verstions again16:44
eglute+1 hogepodge16:44
* markvoelker also notes that the Cinder PTL +1'd this plan on line 233 of scoring.txt16:45
*** mickeys_ has joined #openstack-meeting-316:45
hogepodgeso we don't start telling a bunch of clouds that they're no longer openstack overnight because they're running a perfectly fine endpoint they haven't upgraded yet because business reasons16:45
*** ddyer has joined #openstack-meeting-316:46
markvoelkerWould that really happen considering the Powered program allows for older versions?  v3 couldn't even become required until it's in 3 releases.16:46
catherineDhogepodge: what is the different if they are not upgrade but still have to support v3 if we require both v2/v316:46
*** revon has joined #openstack-meeting-316:47
hogepodgeif it's the same tests, I guess it doesn't matter as long as version isn't explicitly tested16:48
egluteis the version being tested anywhere?16:48
hogepodgefor the time being, I would strongly -1 any endpoint version tests that didn't allow both v2 and v3, because they're compatible with one another16:48
catherineDIn tempest config  user have the options to enable both v2 and v316:49
egluteright now looks like same tests16:49
catherineDor either v2 or v316:49
markvoelkerThey are the same tests.  If you use a v2 endpoint, you don't get microversion headers (which the current tests don't rely on).16:50
*** huanxuan_ has quit IRC16:50
catherineDtest may be the same but path (FQN) maybe different16:50
markvoelkerAt some point it seems like we're going to want clouds to support the headers though16:50
*** rhochmuth has joined #openstack-meeting-316:50
catherineDand the guideline is based on FQN so they are treated as different tests16:50
markvoelkerBecause tools will be written to use them/change their behavior based on what versions are supported16:50
markvoelkerv2 is certainly not going to be "future direction" forever (though it may be supported for a long time)16:51
markvoelkerSo I've no problem at all with the same tests being used or requiring v2 and v3 for some amount of time16:51
hogepodgerequire v2 or v316:51
markvoelkerIf the day comes when we no longer require v2 though, I'd like that to be explicit to users16:51
hogepodgethe and vs or is a big difference, and I want a long lead time to let the transition happen in a reasonable way16:52
eglutesince the tests are the same for now, how about we keep both versions?16:52
hogepodgecutting off all v2 because they don't have v3, or cutting off all v3 because they don't run v2, is counter to the goal of guaranteeing interoperability between clouds.16:52
hogepodgeI agree it can't last forever, and v2 should be dropped at some point, but I want that point pushed out as long as the two work together, or the v2 endpoint is removed from service in covered releases16:53
garloff+116:54
markvoelkerhogepodge: point taken.  What are cinder's plans for removing v2?16:54
hogepodgev2 is listed as supported, I can check with thingee and sean about the team plans16:56
*** dtp has joined #openstack-meeting-316:56
eglutewe are almost out of time.16:57
egluteso for now we agree to remove versions for cinder?16:58
egluteor did i misread that16:58
hogepodgeI don't think there's agreement. :-D16:58
egluteok... so there is still nova and swift left. everyone, please review those16:58
markvoelkerI think we still want to make it clear that v3 is the way forward, we just need to figure out how to do it...can folks continue on #openstack-interop?  I've got a couple ideas...16:58
shamailI think keeping both for now (v2/v3) is important to highlight transition16:58
hogepodgeI'm just arguing strongly, but this is a group decision lead by eglute and markvoelker16:58
egluteand we can carry cinder discussion to our interop channel16:59
eglutehogepodge and markvoelker have both valid points16:59
markvoelkerOk, let's take the discussion there then (I can hang around for a bit)16:59
egluteme too16:59
markvoelker#action everyone finish reviews of the outstanding 2017.01 patches16:59
markvoelkerAnd with that we'll have to close16:59
eglutethanks!17:00
markvoelker#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
shamailthx17:00
openstackMeeting ended Wed Jan  4 17:00:08 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/interopwg/2017/interopwg.2017-01-04-16.06.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/interopwg/2017/interopwg.2017-01-04-16.06.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/interopwg/2017/interopwg.2017-01-04-16.06.log.html17:00
dansmith#startmeeting nova_cells17:00
openstackMeeting started Wed Jan  4 17:00:31 2017 UTC and is due to finish in 60 minutes.  The chair is dansmith. 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: nova_cells)"17:00
openstackThe meeting name has been set to 'nova_cells'17:00
*** mriedem has joined #openstack-meeting-317:00
mriedemo/17:00
dansmithohai17:00
dtphere17:00
melwitto/17:00
*** catherineD has left #openstack-meeting-317:00
dansmithcool17:01
dansmith#topic testing/bugs17:01
*** openstack changes topic to "testing/bugs (Meeting topic: nova_cells)"17:01
*** rhochmuth has quit IRC17:01
mriedemso,17:01
dansmithanything here? I've been disconnected for >2 weeks, so I wouldn't know if we have any fires burning,17:01
mriedemthere aren't fires17:02
mriedemjust a general nod that i need to get the nova-status upgrade check stuff into our ci system,17:02
mriedemi haven't yet dug into where to place that in the flow,17:02
dansmithokay17:02
mriedemi think it could be in grenade and/or devstack, because it also works for base installs17:02
mriedemi'm not sure at what point grenade has the ocata code pip installed but not started - i think that's devstack17:03
mriedemunless there is a post-install / pre-start hook17:03
mriedemif not, i might have to use a venv?17:03
dansmithhmm17:03
dansmithcan't imagine people being super excited about that.. I was thinking it would be in the pre-upgrade stuff in grenade where we have installed, but not started things yet17:03
dansmithand if that isn't actually a phase, then we probably need it to be17:04
*** salv-orlando has joined #openstack-meeting-317:04
mriedemheh yeah i'm not sure if that exists17:04
mriedembut i haven't dug into it yet either17:04
dansmithokay17:04
mriedemi can, and if i get stuck i'll bug sdague17:04
dansmithokay17:04
*** milan|mgt has quit IRC17:05
dansmithanything else here?17:05
dansmith#topic open reviews17:05
*** openstack changes topic to "open reviews (Meeting topic: nova_cells)"17:06
dansmithso, my mega series is becoming less mega, which is cool: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/cells-scheduling-interaction17:06
dansmithmerged another thing yesterday17:06
dansmiththe bottom patch is bumping up against the cellsv1 job not having cellsv2 mappings setu17:06
mriedemyeah....17:06
dansmithI've got a WIP against devstack to do that and see how it goes17:06
mriedemcool17:06
dansmithI *think* we left that unconverted just to have one job that wasn't or something17:07
dansmithhoping there's not something more complicated needed, but we'll see17:07
mriedemi don't think we put that much thought into it17:07
mriedemunless laski did17:07
mriedemi think we just did it because 'this probably blows up with cells v1 so let's not anger that troll yet'17:07
dansmithyeah, maybe17:07
melwittheh17:07
dansmithso, that's all from me.. who else has stuff up that needs calling out?17:08
dtphttps://review.openstack.org/#/c/415922/17:08
*** sdake has joined #openstack-meeting-317:08
dansmithsweet17:08
melwittI put up a first draft of the quota resource counting at https://review.openstack.org/#/c/416521/ this morning17:08
dansmithdtp: I'll take a look at that later today.. hopefully melwitt will as well17:09
dtpthanks17:09
melwittyeah, will do17:09
mriedemdtp: you need to fix the commit message :)17:09
mriedemthat's my review contribution17:09
dtpcan i edit this UI to word wrap? :P17:09
mriedemdtp: i'd do it locally17:09
dtpwill do17:10
dtpis that 80 chars too?17:10
dansmithokay, got both of those things on the priorities tracking etherpad17:10
mriedemdtp: whatever this says https://wiki.openstack.org/wiki/GitCommitMessages17:10
mriedemwrap at 7917:10
melwittI think it's more like 72 I think but I don't think anything checks17:10
*** VW has quit IRC17:10
mriedemyeah ^ says 7217:11
dtpokey dokey, thanks17:11
*** VW has joined #openstack-meeting-317:11
mriedemmelwitt: you had some WIP patches for moving quotas to the API DB17:11
mriedemi think lacking tests, was that all that was making them WIPs?17:11
melwittmriedem: yeah, still do. need to add a bunch o tests, and I think trim down the quota class migration to be only the default class maybe17:12
mriedemi guess we never settled on that17:12
mriedembut since custom quota classes aren't used anyway, i think that's fine17:13
melwittI also have this patch for adding message queue switching back to target_cell https://review.openstack.org/#/c/411543/17:13
*** sdake has quit IRC17:13
mriedembut i assume the migration code is rather generic anyway so i'm not sure how much it matters17:13
melwittyeah, the way I have it right now it'll migrate all quota classes the user has, which is maybe better anyway17:14
*** VW has quit IRC17:16
mriedemdansmith: another thing i thought about last night17:16
mriedemon your bottom patch for listing instances across cells,17:16
*** shamail has quit IRC17:16
mriedemwe talked about a dumb merge sort, is that later in the series?17:16
dansmithmriedem: not yet17:17
mriedemok. it also got me thinking,17:17
dansmithmriedem: figured we'd add that before we add a release note saying that multiple cells is technically supported17:17
mriedemsince we stack build requests then cell0 then cells instances,17:17
mriedemany sort order thing is out of whack today anyway17:17
mriedemso i guess it could just be considered a bug17:18
mriedemidk, my point is i'm not terribly concerned about it right now17:18
*** garloff has quit IRC17:18
dansmithso today you'll get the barber pole results across all cells, which I think is what you're getting at17:18
mriedemright17:18
dansmithpresumably some people will want to just disable the dumb sorting thing anyway17:18
mriedembut even with a single cell,17:18
dansmithright, I know17:18
mriedemok17:19
mriedemyeah my point being it's already 'busted'17:19
dansmithyeah17:19
mriedemsince newton17:19
mriedemok17:19
mriedemlucky for us everyone is still on <=mitaka17:19
dansmithheh17:19
mriedemok i don't have anything else17:19
melwitt"lucky" :)17:19
dansmithokay any other reviews up that need visibility?17:20
dansmith#topic open discussion17:20
*** openstack changes topic to "open discussion (Meeting topic: nova_cells)"17:20
dansmithanything else about anything?17:20
mriedemnope17:22
dtpnot me17:22
dansmithalrighty then17:22
dansmith#endmeeting17:22
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:22
openstackMeeting ended Wed Jan  4 17:22:48 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:22
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2017/nova_cells.2017-01-04-17.00.html17:22
*** VW has joined #openstack-meeting-317:22
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2017/nova_cells.2017-01-04-17.00.txt17:22
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2017/nova_cells.2017-01-04-17.00.log.html17:22
*** dtp has left #openstack-meeting-317:23
*** stevejims has quit IRC17:27
*** sdague_ has quit IRC17:30
*** matrohon has quit IRC17:31
*** reedip_outofmemo has quit IRC17:33
*** lpetrut has quit IRC17:34
*** Swami has joined #openstack-meeting-317:39
*** sdague has quit IRC17:39
*** Guest48309 has quit IRC17:40
*** cleong has joined #openstack-meeting-317:40
*** baoli has joined #openstack-meeting-317:45
*** VW_ has joined #openstack-meeting-317:48
*** tenobreg has joined #openstack-meeting-317:49
*** VW_ has quit IRC17:49
*** VW_ has joined #openstack-meeting-317:49
*** VW has quit IRC17:51
*** tellesnobrega has quit IRC17:52
*** yamahata has quit IRC17:54
*** mriedem has left #openstack-meeting-318:00
*** bobmel has joined #openstack-meeting-318:04
*** tonytan4ever has quit IRC18:07
*** tonytan4ever has joined #openstack-meeting-318:07
*** iyamahat has joined #openstack-meeting-318:11
*** tonytan4ever has quit IRC18:14
*** tonytan4ever has joined #openstack-meeting-318:15
*** stevejims has joined #openstack-meeting-318:15
*** VW_ has quit IRC18:20
*** lblanchard has quit IRC18:21
*** iyamahat has quit IRC18:21
*** VW has joined #openstack-meeting-318:22
*** VW has quit IRC18:22
*** VW has joined #openstack-meeting-318:23
*** iyamahat has joined #openstack-meeting-318:26
*** lblanchard has joined #openstack-meeting-318:28
*** lpetrut has joined #openstack-meeting-318:29
*** yamahata has joined #openstack-meeting-318:32
*** sdake has joined #openstack-meeting-318:36
*** stevejims has quit IRC18:38
*** spzala has quit IRC18:40
*** spzala has joined #openstack-meeting-318:41
*** spzala has quit IRC18:44
*** spzala has joined #openstack-meeting-318:44
*** yamahata has quit IRC18:46
*** yamahata has joined #openstack-meeting-318:47
*** galstrom_zzz is now known as galstrom18:48
*** pcaruana has quit IRC18:52
*** s3wong has joined #openstack-meeting-318:52
*** sdague has joined #openstack-meeting-318:52
*** sdake has quit IRC18:54
*** anilvenkata has quit IRC18:59
*** spzala has quit IRC19:01
*** sambetts is now known as sambetts|afk19:05
*** sdague_ has joined #openstack-meeting-319:10
*** alexismonville has quit IRC19:11
*** sdake has joined #openstack-meeting-319:15
*** sdake has quit IRC19:16
*** matrohon has joined #openstack-meeting-319:24
*** spotz_ is now known as spotz_zzz19:25
*** fitoduarte has joined #openstack-meeting-319:27
*** alexismonville has joined #openstack-meeting-319:29
*** sdake has joined #openstack-meeting-319:29
*** fitoduarte has quit IRC19:30
*** galstrom is now known as galstrom_zzz19:32
*** spzala has joined #openstack-meeting-319:32
*** galstrom_zzz is now known as galstrom19:32
*** galstrom is now known as galstrom_zzz19:33
*** spzala_ has joined #openstack-meeting-319:35
*** ttx has quit IRC19:36
*** ddyer has quit IRC19:36
*** SotK has quit IRC19:36
*** negronjl has quit IRC19:36
*** aignatov has quit IRC19:36
*** kevinbenton has quit IRC19:36
*** jschwarz has quit IRC19:36
*** mfranc213 has quit IRC19:36
*** lifeless has quit IRC19:36
*** vgadiraj has quit IRC19:36
*** dloi has quit IRC19:36
*** raj_singh has quit IRC19:36
*** doffm has quit IRC19:36
*** aslezil has quit IRC19:36
*** pshige_________ has quit IRC19:36
*** eglute has quit IRC19:36
*** mikal has quit IRC19:36
*** jamespd has quit IRC19:36
*** doffm has joined #openstack-meeting-319:36
*** mikal has joined #openstack-meeting-319:36
*** eglute has joined #openstack-meeting-319:36
*** SotK has joined #openstack-meeting-319:36
*** jschwarz has joined #openstack-meeting-319:36
*** jamespd has joined #openstack-meeting-319:36
*** mfranc213 has joined #openstack-meeting-319:36
*** spzala has quit IRC19:36
*** pshige_________ has joined #openstack-meeting-319:36
*** dloi has joined #openstack-meeting-319:36
*** lifeless has joined #openstack-meeting-319:36
*** aignatov has joined #openstack-meeting-319:36
*** ddyer has joined #openstack-meeting-319:36
*** ttx has joined #openstack-meeting-319:36
*** kevinbenton has joined #openstack-meeting-319:37
*** negronjl has joined #openstack-meeting-319:38
*** fitoduarte has joined #openstack-meeting-319:38
*** galstrom_zzz is now known as galstrom19:39
*** gary-smith has joined #openstack-meeting-319:41
*** clu_ has joined #openstack-meeting-319:42
*** raj_singh has joined #openstack-meeting-319:44
*** aslezil has joined #openstack-meeting-319:49
*** corey_ has joined #openstack-meeting-319:50
*** VW_ has joined #openstack-meeting-319:51
*** corey_ is now known as Guest374519:51
*** VW_ has quit IRC19:52
*** VW_ has joined #openstack-meeting-319:52
*** cleong has quit IRC19:53
*** VW has quit IRC19:54
*** ducttape_ has joined #openstack-meeting-319:55
*** spotz_zzz is now known as spotz_19:56
*** rdopiera has joined #openstack-meeting-319:56
*** VW_ has quit IRC19:56
*** gouthamr has joined #openstack-meeting-319:58
*** TravT has joined #openstack-meeting-320:01
betherlyHi sorry I'm late!20:04
david-lyleHi betherly, I think per the ML, no meeting today20:04
rdopieraI'm not sure there is a meeting20:04
rdopieradavid-lyle: I didn't see any cancelling e-mail20:05
betherlyAh ok! Sorry I missed that :) thanks for the heads up david-lyle and rdopiera20:05
david-lylewas sent some time ago20:05
david-lylehttp://lists.openstack.org/pipermail/openstack-dev/2016-December/109461.html20:06
*** VW has joined #openstack-meeting-320:07
david-lylewe can ad hoc if there's a need20:07
david-lyleor just talk in #openstack-horizon20:07
*** salv-orlando has quit IRC20:08
*** TravT has quit IRC20:08
rdopieraI don't have anything urgent20:11
*** liangy has joined #openstack-meeting-320:12
*** revon has quit IRC20:23
*** rdopiera has left #openstack-meeting-320:24
*** VW has quit IRC20:26
*** VW has joined #openstack-meeting-320:27
*** rtheis has quit IRC20:28
*** spotz_ is now known as spotz_zzz20:32
*** Guest3745 is now known as cleong20:33
*** spotz_zzz is now known as spotz_20:33
*** gary-smith has quit IRC20:33
*** caboucha has quit IRC20:34
*** tonytan4ever has quit IRC20:35
*** tonytan4ever has joined #openstack-meeting-320:36
*** mickeys_ has quit IRC20:39
*** d0ugal has quit IRC20:39
*** sdake has quit IRC20:40
*** spzala_ has quit IRC20:42
*** d0ugal has joined #openstack-meeting-320:55
*** rtheis has joined #openstack-meeting-321:04
*** rtheis has quit IRC21:04
*** spzala has joined #openstack-meeting-321:06
*** dimtruck is now known as zz_dimtruck21:10
*** cleong has quit IRC21:12
*** mickeys has joined #openstack-meeting-321:12
*** galstrom is now known as galstrom_zzz21:18
*** spzala has quit IRC21:19
*** julim has quit IRC21:20
*** salv-orlando has joined #openstack-meeting-321:23
*** ducttape_ has quit IRC21:26
*** tobberydberg has joined #openstack-meeting-321:28
*** sdake has joined #openstack-meeting-321:29
*** tobberydberg has quit IRC21:31
*** VW has quit IRC21:33
*** zz_dimtruck is now known as dimtruck21:42
*** salv-orl_ has joined #openstack-meeting-321:54
*** spotz_ is now known as spotz__21:56
*** spotz__ is now known as spotz_21:56
*** salv-orlando has quit IRC21:56
*** matrohon has quit IRC21:58
*** iyamahat has quit IRC22:03
*** chyka has joined #openstack-meeting-322:03
*** iyamahat has joined #openstack-meeting-322:03
*** VW has joined #openstack-meeting-322:03
*** VW has quit IRC22:06
*** VW has joined #openstack-meeting-322:06
*** lblanchard has quit IRC22:13
*** baoli has quit IRC22:29
*** baoli has joined #openstack-meeting-322:30
*** baoli has quit IRC22:33
*** baoli has joined #openstack-meeting-322:36
*** gouthamr has quit IRC22:36
*** rbak_ has quit IRC22:38
*** VW has quit IRC22:40
*** baoli has quit IRC22:40
*** VW has joined #openstack-meeting-322:44
*** alexismonville has quit IRC22:49
*** diablo_rojo_phon has quit IRC22:50
*** tonytan4ever has quit IRC22:50
*** VW has quit IRC22:51
*** clarkb has joined #openstack-meeting-322:51
*** VW has joined #openstack-meeting-322:51
*** openstack has joined #openstack-meeting-322:55
*** ChanServ sets mode: +o openstack22:55
*** VW has quit IRC22:57
*** VW_ has quit IRC22:58
*** amotoki has quit IRC23:00
*** amotoki has joined #openstack-meeting-323:02
*** armax has quit IRC23:04
*** lpetrut has quit IRC23:04
*** armax has joined #openstack-meeting-323:05
*** armax has quit IRC23:06
*** sdake has quit IRC23:09
*** VW has joined #openstack-meeting-323:14
*** spzala has joined #openstack-meeting-323:17
*** VW has quit IRC23:18
*** yamahata has quit IRC23:19
*** salv-orl_ has quit IRC23:20
*** sdake has joined #openstack-meeting-323:24
*** sdake has quit IRC23:26
*** yamahata has joined #openstack-meeting-323:26
*** amotoki has quit IRC23:26
*** sdake has joined #openstack-meeting-323:29
*** spotz_ is now known as spotz_zzz23:30
*** amotoki has joined #openstack-meeting-323:31
*** iyamahat_ has joined #openstack-meeting-323:34
*** iyamahat has quit IRC23:34
*** gouthamr has joined #openstack-meeting-323:38
*** spzala has quit IRC23:42
*** spzala has joined #openstack-meeting-323:45
*** gouthamr has quit IRC23:48
*** gouthamr has joined #openstack-meeting-323:52
*** iyamahat has joined #openstack-meeting-323:57
*** iyamahat_ has quit IRC23:57

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