Wednesday, 2017-08-16

*** lyan has quit IRC00:00
*** Swami has quit IRC00:03
*** wanghao has quit IRC00:09
*** wanghao has joined #openstack-meeting-300:09
*** gouthamr has joined #openstack-meeting-300:13
*** lucasxu has joined #openstack-meeting-300:24
*** wanghao_ has joined #openstack-meeting-300:26
*** pvaneck has quit IRC00:27
*** wanghao has quit IRC00:29
*** markvoelker has quit IRC00:30
*** lyan has joined #openstack-meeting-300:39
*** cshastri has joined #openstack-meeting-300:48
*** lyan has quit IRC00:51
*** lyan has joined #openstack-meeting-300:51
*** stendulker has joined #openstack-meeting-300:52
*** lucasxu has quit IRC00:54
*** rama_y has joined #openstack-meeting-300:54
*** lyan has quit IRC00:56
*** lyan has joined #openstack-meeting-300:57
*** zhurong has joined #openstack-meeting-300:58
*** dixiaoli has joined #openstack-meeting-301:01
*** dixiaoli_ has joined #openstack-meeting-301:02
*** dixiaoli has quit IRC01:02
*** lyan has quit IRC01:11
*** lucasxu has joined #openstack-meeting-301:11
*** gouthamr has quit IRC01:13
*** lucasxu has quit IRC01:13
*** lhx_ has quit IRC01:14
*** wanghao_ has quit IRC01:16
*** wanghao has joined #openstack-meeting-301:17
*** wanghao has quit IRC01:17
*** rama_y has quit IRC01:17
*** wanghao has joined #openstack-meeting-301:17
*** gouthamr has joined #openstack-meeting-301:30
*** gcb has joined #openstack-meeting-301:32
*** yamahata has quit IRC01:35
*** slaweq has joined #openstack-meeting-301:42
*** tuanluong has joined #openstack-meeting-301:44
*** slaweq has quit IRC01:47
*** stendulker has quit IRC02:07
*** markvoelker has joined #openstack-meeting-302:31
*** gouthamr has quit IRC02:34
*** yamahata has joined #openstack-meeting-302:34
*** rama_y has joined #openstack-meeting-302:35
*** diablo_rojo has joined #openstack-meeting-302:35
*** krtaylor has joined #openstack-meeting-302:42
*** slaweq has joined #openstack-meeting-302:43
*** baoli has joined #openstack-meeting-302:47
*** baoli has quit IRC02:48
*** slaweq has quit IRC02:48
*** baoli has joined #openstack-meeting-302:48
*** baoli has quit IRC02:49
*** markvoelker has quit IRC03:04
*** rama_y has quit IRC03:10
*** dklyle has quit IRC03:12
*** vishwana_ has joined #openstack-meeting-303:18
*** vishwanathj has quit IRC03:21
*** esikachev has joined #openstack-meeting-303:27
*** stendulker has joined #openstack-meeting-303:28
*** david-lyle has joined #openstack-meeting-303:31
*** esikachev has quit IRC03:32
*** slaweq has joined #openstack-meeting-303:44
*** makowals has quit IRC03:47
*** slaweq has quit IRC03:49
*** makowals has joined #openstack-meeting-303:57
*** markvoelker has joined #openstack-meeting-304:01
*** david-lyle has quit IRC04:06
*** david-lyle has joined #openstack-meeting-304:08
*** esikachev has joined #openstack-meeting-304:10
*** esikachev has quit IRC04:15
*** dklyle has joined #openstack-meeting-304:15
*** david-lyle has quit IRC04:18
*** rama_y has joined #openstack-meeting-304:20
*** rama_y has quit IRC04:28
*** markvoelker has quit IRC04:34
*** MarkBaker has quit IRC04:41
*** slaweq has joined #openstack-meeting-304:45
*** slaweq_ has joined #openstack-meeting-304:50
*** slaweq has quit IRC04:50
*** slaweq_ has quit IRC04:55
*** esikachev has joined #openstack-meeting-305:12
*** esikachev has quit IRC05:16
*** knikolla has quit IRC05:22
*** reedip has quit IRC05:23
*** tobberydberg has joined #openstack-meeting-305:31
*** markvoelker has joined #openstack-meeting-305:32
*** anilvenkata has joined #openstack-meeting-305:37
*** reedip has joined #openstack-meeting-305:37
*** rama_y has joined #openstack-meeting-305:38
*** shuyingy_ has joined #openstack-meeting-305:40
*** shuyingya has quit IRC05:40
*** pcaruana has joined #openstack-meeting-305:45
reedipmeeting ?05:46
*** pgadiya has joined #openstack-meeting-305:50
*** slaweq has joined #openstack-meeting-305:51
*** esikachev has joined #openstack-meeting-305:53
*** slaweq has quit IRC05:56
*** esikachev has quit IRC05:57
*** marios has joined #openstack-meeting-306:00
*** shuyingya has joined #openstack-meeting-306:01
*** wanghao_ has joined #openstack-meeting-306:04
*** shuyingy_ has quit IRC06:04
*** markvoelker has quit IRC06:05
*** wanghao has quit IRC06:08
*** esikachev has joined #openstack-meeting-306:08
*** esikachev has quit IRC06:13
*** zhurong has quit IRC06:19
*** zhurong has joined #openstack-meeting-306:22
*** esikachev has joined #openstack-meeting-306:26
*** esikachev has quit IRC06:35
*** stendulker has quit IRC06:44
*** zhurong has quit IRC06:53
*** coolsvap has joined #openstack-meeting-306:54
*** pgadiya has quit IRC06:54
*** esikachev has joined #openstack-meeting-306:56
*** wanghao_ has quit IRC06:59
*** wanghao has joined #openstack-meeting-307:01
*** markvoelker has joined #openstack-meeting-307:02
*** pgadiya has joined #openstack-meeting-307:07
*** diablo_rojo has quit IRC07:12
*** wanghao has quit IRC07:16
*** ccamacho has joined #openstack-meeting-307:18
*** wanghao has joined #openstack-meeting-307:22
*** markvoelker has quit IRC07:36
*** wanghao has quit IRC07:38
*** rama_y has quit IRC07:44
*** abalutoiu has joined #openstack-meeting-307:51
*** slaweq_ has joined #openstack-meeting-307:53
*** slaweq_ has quit IRC07:58
*** abalutoiu has quit IRC08:01
*** wanghao has joined #openstack-meeting-308:03
*** ralonsoh has joined #openstack-meeting-308:04
*** ralonsoh has quit IRC08:12
*** ralonsoh has joined #openstack-meeting-308:12
*** yamamoto has joined #openstack-meeting-308:33
*** markvoelker has joined #openstack-meeting-308:33
*** dixiaoli has joined #openstack-meeting-308:34
*** dixiaoli has quit IRC08:36
*** dixiaoli_ has quit IRC08:38
*** esikachev has quit IRC08:44
*** wanghao has quit IRC08:45
*** yamamoto has quit IRC08:49
*** slaweq has joined #openstack-meeting-308:54
*** sambetts|afk is now known as sambetts08:58
*** slaweq has quit IRC08:59
*** stendulker has joined #openstack-meeting-309:05
*** markvoelker has quit IRC09:06
*** dixiaoli has joined #openstack-meeting-309:14
*** enolfc has joined #openstack-meeting-309:19
*** enolfc has quit IRC09:20
*** wanghao has joined #openstack-meeting-309:43
*** wanghao has quit IRC09:45
*** esikachev has joined #openstack-meeting-309:45
*** dixiaoli has quit IRC09:45
*** chyka has joined #openstack-meeting-309:46
*** cshastri has quit IRC09:47
*** dixiaoli has joined #openstack-meeting-309:48
*** chyka has quit IRC09:50
*** ociuhandu has quit IRC09:54
*** slaweq has joined #openstack-meeting-309:55
*** slaweq has quit IRC10:00
*** markvoelker has joined #openstack-meeting-310:03
*** dixiaoli has quit IRC10:03
*** ociuhandu has joined #openstack-meeting-310:12
*** abalutoiu has joined #openstack-meeting-310:15
*** lpetrut has joined #openstack-meeting-310:17
*** abalutoiu has quit IRC10:20
*** yamahata has quit IRC10:21
*** MarkBaker has joined #openstack-meeting-310:28
*** MarkBaker has quit IRC10:33
*** markvoelker has quit IRC10:38
*** abalutoiu has joined #openstack-meeting-310:40
*** ralonsoh has quit IRC10:44
*** ralonsoh_ has joined #openstack-meeting-310:44
*** stendulker has quit IRC10:49
*** MarkBaker has joined #openstack-meeting-310:49
*** tellesnobrega has quit IRC11:01
*** tuanluong has quit IRC11:04
*** gcb has quit IRC11:20
*** esikachev has quit IRC11:24
*** markvoelker has joined #openstack-meeting-311:35
*** esikachev has joined #openstack-meeting-311:37
*** pgadiya has quit IRC11:41
*** esikachev has quit IRC11:42
*** raildo has joined #openstack-meeting-311:54
*** MarkBaker has quit IRC11:55
*** lhx_ has joined #openstack-meeting-311:55
*** prometheanfire has joined #openstack-meeting-311:56
*** slaweq_ has joined #openstack-meeting-311:57
prometheanfire#startmeeting requirements12:00
openstackMeeting started Wed Aug 16 12:00:53 2017 UTC and is due to finish in 60 minutes.  The chair is prometheanfire. Information about MeetBot at http://wiki.debian.org/MeetBot.12:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
*** openstack changes topic to " (Meeting topic: requirements)"12:00
openstackThe meeting name has been set to 'requirements'12:00
prometheanfire#topic rollcall12:01
*** openstack changes topic to "rollcall (Meeting topic: requirements)"12:01
*** slaweq_ has quit IRC12:02
prometheanfireanyone else?12:02
prometheanfiregonna wait a couple of min before calling it12:02
dirko/12:08
*** markvoelker has quit IRC12:08
dirkprometheanfire: sorry, you forgot to ping people :)12:08
prometheanfireI did mention it, but ya12:08
prometheanfirekinda tired :P12:08
prometheanfiredone12:10
prometheanfire1-2 more min then12:10
*** toabctl has joined #openstack-meeting-312:11
toabctlhi12:11
dirkto be honest I have no topics, haven't followed g-r the last week or so12:11
prometheanfire#topic freeze12:12
*** openstack changes topic to "freeze (Meeting topic: requirements)"12:12
prometheanfirewe are still frozen, but can probably start doing GR updates soon12:12
prometheanfireI'll clear it with tonyb one more time though12:13
prometheanfireUpper-constraints is taken from the head of the branch (master in this case) directly by the gate, while global-requirements is taken 'gated' by the consuming project's core developers12:13
prometheanfireI think new reqs are probably fine too12:14
prometheanfireanything else for the freeze?12:14
prometheanfirek12:15
prometheanfire#topic known issues12:15
*** openstack changes topic to "known issues (Meeting topic: requirements)"12:15
prometheanfireonly thing I have here is the possible backport of blacklisting a known bad babel version12:16
prometheanfireit's not in UC, so UC won't change though, so it's usefulness is questionable12:16
prometheanfirehttps://review.openstack.org/49375112:16
prometheanfire#link https://bugs.launchpad.net/openstack-requirements/+bug/170919012:17
openstackLaunchpad bug 1709190 in OpenStack Global Requirements "[stable/ocata] Latest oslo.i18n version conflicts with latest Babel version" [Medium,Triaged]12:17
prometheanfire# https://review.openstack.org/49375112:17
prometheanfire#link https://review.openstack.org/49375112:17
prometheanfireso take a look if you want12:17
prometheanfire#topic ptg12:17
*** openstack changes topic to "ptg (Meeting topic: requirements)"12:18
prometheanfireptg schedule for us is here, we are sharing a room with relmgmt / stable12:18
prometheanfire#link https://etherpad.openstack.org/p/relmgt-stable-requirements-ptg-pike12:18
prometheanfirefeel free to update it12:18
prometheanfire#topic open floor12:19
*** openstack changes topic to "open floor (Meeting topic: requirements)"12:19
prometheanfiregonna leave it open for 1-2 more minutes before closing12:20
prometheanfire#endmeeting12:23
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"12:23
openstackMeeting ended Wed Aug 16 12:23:23 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/requirements/2017/requirements.2017-08-16-12.00.html12:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/requirements/2017/requirements.2017-08-16-12.00.txt12:23
openstackLog:            http://eavesdrop.openstack.org/meetings/requirements/2017/requirements.2017-08-16-12.00.log.html12:23
*** prometheanfire has left #openstack-meeting-312:23
*** shuyingya has quit IRC12:38
*** lyan has joined #openstack-meeting-312:38
*** calbers has joined #openstack-meeting-312:38
*** spzala has quit IRC12:51
*** slaweq_ has joined #openstack-meeting-312:58
*** markvoelker has joined #openstack-meeting-312:59
*** seanhandley has joined #openstack-meeting-313:00
*** slaweq_ has quit IRC13:03
*** baojg has joined #openstack-meeting-313:03
*** spzala has joined #openstack-meeting-313:12
*** spzala has quit IRC13:12
*** spzala has joined #openstack-meeting-313:12
*** gouthamr has joined #openstack-meeting-313:15
*** VW has joined #openstack-meeting-313:17
*** esikachev has joined #openstack-meeting-313:27
*** esikachev has quit IRC13:29
*** esikachev has joined #openstack-meeting-313:29
*** tellesnobrega has joined #openstack-meeting-313:30
*** MarkBaker has joined #openstack-meeting-313:37
*** cleong has joined #openstack-meeting-313:41
*** AndroUser2 has joined #openstack-meeting-313:50
*** zhipeng has joined #openstack-meeting-313:57
seanhandleyhey zhipeng tobberydberg o/13:58
zhipenghey o/13:58
tobberydberghi guys!13:59
*** slaweq_ has joined #openstack-meeting-313:59
tobberydberg#startmeeting publiccloud-wg14:00
openstackMeeting started Wed Aug 16 14:00:07 2017 UTC and is due to finish in 60 minutes.  The chair is tobberydberg. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: publiccloud-wg)"14:00
openstackThe meeting name has been set to 'publiccloud_wg'14:00
*** rama_y has joined #openstack-meeting-314:00
tobberydbergJust started the meeting, I guess we wait a couple of minutes to let everyone get online =)14:00
tobberydbergso, do we have any participants? =)14:01
Labedzhello14:01
tobberydberghi Labedz14:01
tobberydbergFor everyone that is here...please put your name at the etherpad14:03
tobberydbergAgenda and etherpad at #link https://etherpad.openstack.org/p/publiccloud-wg14:03
*** slaweq_ has quit IRC14:04
seanhandleyI'm on a train so I apologise for any long silences while me client reconnects to my IRC bouncer14:04
seanhandley*my14:04
*** qwebirc46285 has joined #openstack-meeting-314:04
tobberydberg"me client" sounded really British though =)14:05
tobberydbergOk, lets get going and the rest will have to join in later14:06
tobberydberg#topic   Review action points14:06
*** openstack changes topic to "Review action points (Meeting topic: publiccloud-wg)"14:06
tobberydberga. Sean to make a spec for the OpenStack passport (this will contain multiple proposed solutions)14:06
seanhandleyOk14:07
tobberydbergIs your connection ok to comment, or should I?14:07
seanhandleySo after much reading of documentation I've created our documents/specs repo on gerrit14:07
seanhandleyFeel free to summarise tobberydberg - it comes and goes by the minute14:08
Labedzseanhandley: could you share a link on etherpad?14:08
tobberydberg#link https://github.com/openstack/publiccloud-wg14:08
seanhandleySure Labedz14:08
seanhandley#link https://git.openstack.org/cgit/openstack/publiccloud-wg/14:09
tobberydbergSummary: the basics are there to start doing "real work" so to say!14:09
zhipeng#link https://review.openstack.org/#/q/project:openstack/publiccloud-wg14:09
tobberydbergReally great job seanhandley!14:09
zhipengi see cookiecutter patches14:09
zhipengno spec yet right ?14:09
seanhandleyI made an initial directory structure with cookie cutter. I guess most of it can be deleted14:09
seanhandleyand replace with a structure similar to the API WG14:10
seanhandley#link https://github.com/openstack/api-wg14:10
seanhandleyIf anyone wants to clone and submit gerrit reviews, you're very welcome to do so14:10
zhipenggreat14:11
seanhandleyCurrently tobberydberg and I have the +2 approval ability14:11
*** zhipeng has quit IRC14:11
*** zhipeng has joined #openstack-meeting-314:12
seanhandleyzhipeng: As a chair of the WG, you should have the ability to approve gerrit reviews too. What's your username for gerrit?14:12
zhipengjust search Zhipeng14:12
zhipengshould give you the auto complete14:12
tobberydbergSo, basically everything is in place for us to start writing specs14:12
tobberydberggreat job14:12
tobberydberg(this will cover no 2 on the agenda)14:13
seanhandleyzhipeng: Trying - connection is terrible14:13
tobberydbergb. Howard and Sean to begin writing up some public cloud WG14:13
zhipengyes we started with a google doc now14:13
zhipengwill have something concrete, say14:14
zhipengnext few months lol14:14
tobberydberghehe14:14
tobberydbergOk. lets keep that on here as a AP for upcoming meetings14:14
tobberydbergc. Update to active14:14
tobberydberg...well...not much work there, done! ;-)14:14
seanhandleyOk zhipeng - you should have the +2 ability now on gerrit :)14:15
tobberydberg2. publiccloud_wg is up and running - can start writing spes14:15
tobberydberg#topic 2. publiccloud_wg is up and running - can start writing spes14:15
*** openstack changes topic to "2. publiccloud_wg is up and running - can start writing spes (Meeting topic: publiccloud-wg)"14:15
zhipengthx sean !14:15
tobberydbergcovered above...or would you like to add something else to this?14:15
seanhandleyno, that's all so far I guess14:16
seanhandleyas an aside14:16
*** ralonsoh_ has quit IRC14:16
seanhandleyI aim to write some documentation re: creating a WG14:16
seanhandleyas it's a little different from creating an OpenStack code project14:16
seanhandleyand quite confusing14:16
tobberydbergThats a great contribution!14:16
*** qwebirc46285 has quit IRC14:16
seanhandleyI'll try to make time for it over the next month. Would be a service to the community to have it laid out clearly.14:17
tobberydbergabsolutely!14:17
tobberydberg#topic Passport - what to be done untli Sydney14:17
*** openstack changes topic to "Passport - what to be done untli Sydney (Meeting topic: publiccloud-wg)"14:17
tobberydbergso, to summarize ... a few things are happening  in the backgroud14:18
tobberydbergflanders is talking very well about this project to the foundation14:19
tobberydbergand, they like it very much this far14:19
tobberydbergso, we have put together a "potential timeline" that has been presented to them14:20
tobberydbergand the basic of that is to have a proposal of a design of the schema ready by Sydney to be able to recruit public clouds there to be a part of this14:21
tobberydbergwe will also need some webpages that show the whole concept14:22
zhipengdo we need the webpage by Sydney ?14:22
tobberydbergthat is what "Freemium page at each public clouds website" is - a page at each public cloud that describes how to get a code, how to use it, what you get etc etc14:23
zhipengokey14:24
tobberydbergalso, something at openstack.org/passport (for example) that list all participating clouds and the links to there description pages14:24
*** tellesnobrega has quit IRC14:24
tobberydbergwell, it will not be a final product, it will be conceptual14:24
tobberydbergseanhandley: did I miss something in that summary?14:24
*** lucasxu has joined #openstack-meeting-314:25
tobberydbergI commit that we have a page up and kicking with "what content we need" until Sydney14:26
*** rama_y has quit IRC14:26
tobberydbergNot much job for us, I know datcentred are in as well14:27
tobberydbergSo, if any of you can commit to this as well, put your name at the etherpad14:27
zhipengso a webpage from the foundation, and a webpage from the participants14:28
zhipengright ?14:28
tobberydbergyes14:28
zhipengcool14:28
tobberydberga small web at openstack.org/passport with descriptions etc14:28
tobberydbergand a page at each participating cloud14:29
tobberydbergand the commit I'm looking for now is "the page at each cloud"14:29
tobberydbergwith that said - What should it consist of?14:29
tobberydbergShould it be screencast how to get started using your code?14:30
Labedzidea description14:30
tobberydberg+114:30
zhipengsome basic description should be enough14:31
tobberydberg(please post all your ideas at the etherpad)14:31
tobberydbergso, basic description. Link back to the openstack.org/passport-page?14:32
tobberydbergHow to signup instruction for the individual cloud?14:32
zhipengyes that's a given I suppose14:32
tobberydbergShould we produce like a template of the "must-haves" ?14:32
*** esikachev has quit IRC14:35
tobberydbergOk. we can keep working on that, feel free to add thougts and "+1"s14:36
tobberydberg#topic Discussions of "Scheme basics"14:36
*** openstack changes topic to "Discussions of "Scheme basics" (Meeting topic: publiccloud-wg)"14:36
tobberydbergMoving on here...14:36
tobberydbergso, I just added some basic concepts about the scheme14:37
tobberydbergI would like you to comment on them, +1, -1, etc etc14:37
*** esikachev has joined #openstack-meeting-314:38
tobberydbergthese are what me and seanhandley believe are the most basic concepts that we need to decide upon to continue to specification14:39
*** shuyingya has joined #openstack-meeting-314:39
tobberydbergIt's totally fine to comment later after meeting as well if you can't come up with al feedback now=)14:40
Labedzabout 1) do we plan to put some code to execute on participant side?14:40
Labedzor we will adapt our billing systems to play with passport?14:40
Labedz(I belive that passport will give some basic REST API)14:41
tobberydbergexactly14:41
tobberydbergall codes managed by central passport service14:42
*** shuyingya has quit IRC14:44
*** srobert has joined #openstack-meeting-314:45
tobberydbergJut to have this said. I believe that the success here is to put as much power in the hands to the end users - and at the same time keep it as simple as possible for all participating clouds14:47
tobberydbergPleace continue to comment =)14:48
tobberydbergbut we can move on to cover the rest as well14:48
*** makowals has quit IRC14:48
tobberydberg#topic Other matters14:48
*** openstack changes topic to "Other matters (Meeting topic: publiccloud-wg)"14:48
tobberydberga. issues brief. Anyone iterested who is working on issues and how to deal with it? Maybe on other IRC #channel after meeting?14:48
tobberydbergLabedz: yours? =)14:48
Labedzyeap14:48
*** makowals has joined #openstack-meeting-314:49
LabedzI ment our meeting is time limited but for sure there is much to talk about14:49
zhipengon #openstack-publiccloud ?14:49
Labedzit would be great if anyone interested could talk about daily job :)14:49
zhipengis that channel registered ?14:49
Labedznot necessary14:49
tobberydbergyes14:49
Labedzjust want to gather OS Public CLoud operators online14:50
tobberydbergseanhandley has done that, and all merge messages etc will go there =)14:50
tobberydbergtotally agree, we should be better to hang out there!14:50
Labedzgreat14:50
tobberydbergb. telemetry - what are you using guys?14:51
Labedzso it's a topic for #openstack-publiccloud14:51
tobberydbergI posted a comment in the etherpad14:51
Labedzwe can go further14:51
tobberydbergok =)14:52
tobberydbergcool14:52
tobberydbergc. EU Meetup preps: venue information, promotion, recording/photo for Sydney Summit, ...14:52
tobberydbergzhipeng:14:52
zhipengyes14:53
tobberydbergThis one you added I guess =)14:53
tobberydberg#link https://etherpad.openstack.org/p/MEETUPS-2017-publiccloud-wg14:53
zhipengi meant we should start preparing14:53
zhipengwow14:53
tobberydbergAgree14:53
zhipenggreat tobias14:53
tobberydbergDid this some time ago but haven't had the time to do more, nd thought about this for todays agenda as well, but falled back to "Passport" =)14:54
*** zhipeng has quit IRC14:54
*** zhipeng has joined #openstack-meeting-314:54
zhipengshould we add OpenStack Day France as well?14:54
tobberydbergBut it can be used to collaborate around this14:54
tobberydbergWould have been nice, but I can't attend that one14:54
zhipengi think labdez could ?14:55
zhipengI could also ask around other guys14:55
tobberydbergsure, feel free14:55
Labedzfor sure somebody from OVH will be in OpenStack Days FR14:55
tobberydbergIf not many, nice just to meet and have a dinner! =)14:56
Labedzfor me probably OpenStack Nordic14:57
tobberydbergWould be nice to have one or two each cycle14:57
seanhandleySorry guys for flakiness guys - I'll read the logs and add to the etherpad where appropriate. My train's due to stop soon so time to pack up the laptop anyway. Speak more soon o/14:57
tobberydbergcool! for you guys, I have a promotion code for the fee...30% off14:57
tobberydbergthanks for joining14:58
tobberydbergI'll send you the code!14:59
Labedzthx14:59
tobberydbergThank you all for today! See you in the #openstack-publiccloud channel14:59
*** lhx__ has joined #openstack-meeting-315:00
tobberydberg#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Wed Aug 16 15:00:06 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/publiccloud_wg/2017/publiccloud_wg.2017-08-16-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/publiccloud_wg/2017/publiccloud_wg.2017-08-16-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/publiccloud_wg/2017/publiccloud_wg.2017-08-16-14.00.log.html15:00
*** slaweq has joined #openstack-meeting-315:00
*** spzala has quit IRC15:01
*** spzala has joined #openstack-meeting-315:01
*** lhx_ has quit IRC15:02
*** shuyingya has joined #openstack-meeting-315:03
*** zhipeng has quit IRC15:05
*** slaweq has quit IRC15:05
*** zhipeng has joined #openstack-meeting-315:05
*** shuyingya has quit IRC15:08
*** Labedz is now known as Labedz_15:11
*** tobberyd_ has joined #openstack-meeting-315:14
*** tobberydberg has quit IRC15:17
*** esikache1 has joined #openstack-meeting-315:17
*** tobberyd_ has quit IRC15:19
*** marst has joined #openstack-meeting-315:19
*** esikachev has quit IRC15:20
*** reedip_ has joined #openstack-meeting-315:21
*** Sukhdev has joined #openstack-meeting-315:22
*** baojg has quit IRC15:26
*** coolsvap has quit IRC15:27
*** baojg has joined #openstack-meeting-315:27
*** chyka has joined #openstack-meeting-315:31
*** Mole[m] has joined #openstack-meeting-315:36
*** Mole[m] has left #openstack-meeting-315:36
*** tellesnobrega has joined #openstack-meeting-315:36
*** donghao has joined #openstack-meeting-315:37
*** reedip_ has quit IRC15:42
*** ccamacho has quit IRC15:44
*** caboucha has joined #openstack-meeting-315:45
*** ccamacho has joined #openstack-meeting-315:46
*** yamahata has joined #openstack-meeting-315:47
*** zhipeng has quit IRC15:48
*** zhipeng has joined #openstack-meeting-315:49
*** tobberydberg has joined #openstack-meeting-315:49
*** spzala has quit IRC15:51
*** spzala has joined #openstack-meeting-315:51
*** marios has quit IRC15:51
*** Sukhdev_ has joined #openstack-meeting-315:53
*** rama_y has joined #openstack-meeting-315:55
*** spzala has quit IRC15:55
*** tobberydberg has quit IRC15:56
*** shuyingya has joined #openstack-meeting-315:56
*** ricolin has joined #openstack-meeting-315:56
*** pcaruana has quit IRC15:57
*** mugsie has joined #openstack-meeting-316:00
eglute#startmeeting interopwg16:00
openstackMeeting started Wed Aug 16 16:00:59 2017 UTC and is due to finish in 60 minutes.  The chair is eglute. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: interopwg)"16:01
openstackThe meeting name has been set to 'interopwg'16:01
markvoelkero/16:01
eglute#chair markvoelker16:01
openstackCurrent chairs: eglute markvoelker16:01
eglute#chair hogepodge16:01
openstackCurrent chairs: eglute hogepodge markvoelker16:01
zhipengo/16:01
egluteHello Everyone!16:01
eglute#topic agenda16:01
*** openstack changes topic to "agenda (Meeting topic: interopwg)"16:01
ricolino/16:01
*** slaweq has joined #openstack-meeting-316:01
eglutetoday's agenda, please update as needed: #link https://etherpad.openstack.org/p/InteropVertigo.1116:01
luzCo/16:02
mugsieo/16:02
eglute#topic ptg16:02
*** openstack changes topic to "ptg (Meeting topic: interopwg)"16:02
*** AndroUser2 has quit IRC16:02
*** tobberydberg has joined #openstack-meeting-316:02
eglutePTG less than a month away! Please let us know you are coming by updating etherpad for PTG: https://etherpad.openstack.org/p/InteropDenver2017PTG16:02
eglutealso, please add proposed topics16:02
hogepodgeo/16:03
eglute#topic  2017.09 Guideline16:03
*** openstack changes topic to "2017.09 Guideline (Meeting topic: interopwg)"16:03
hogepodgeI'm double booked this morning so my responses may be a bit delayed16:03
*** catherineD has joined #openstack-meeting-316:03
egluteSince the August board meeting was cancelled,  we will ask the board to approve the next guideline during the September board meeting16:04
eglutetherefore, the next guideline will be 2017.09 rather than 2017.0816:04
catherineDo/16:04
* markvoelker makes note to rename it16:04
*** lpetrut has quit IRC16:04
zhipengeglute could you explain a little bit on the reason for the naming ?16:04
eglute#action markvoelker to rename 2017.08 to 2017.0916:04
zhipeng2017.0916:05
eglutezhipeng we name the guidelines based on when they are approved,16:05
zhipengah right16:05
zhipeng:)thx16:05
egluteyear.month16:05
eglute:)16:05
egluteyeah, very simple convention, makes naming things easy16:05
*** shuyingya has quit IRC16:06
eglutethank you zhipeng for submitting bug report16:06
*** slaweq has quit IRC16:06
eglute#link https://storyboard.openstack.org/#!/story/200115616:06
eglutegood catch, wonder what happened there16:07
zhipeng:)16:07
zhipengsomething we catch during testing16:07
eglutewe need to fix this, any takers?16:08
zhipengnot sure if it is a bug or we misunderstand something16:08
zhipengeglute I could do it16:08
eglutei think they should be unique16:08
eglutezhipeng thank you!!16:08
catherineDactually not16:08
zhipengso I could remove those duplicated capabilites ?16:08
hogepodgeIf I understand some tests are overloaded, but that looks like an error. The fix should be to look at the code base and correspond the test names to the idempotent_id16:08
catherineDin RefStack we do not match output to ID16:08
catherineDwe match them to the FQN16:08
eglute#action zhipeng to fix duplicate test IDs16:08
zhipengokey I will submit a patch on this16:09
eglutezhipeng what hogepodge said.16:09
eglutezhipeng thank you!!!16:09
*** tobberydberg has quit IRC16:10
egluteany other questions or comments on the next guideline?16:10
hogepodgeduplicated capabilities should not be removed. Now, we may be in a situation where if the tests were being skipped in testing we might want to flag them for the current guidelines.16:10
catherineDsee the explaination of FQN vs ID in https://bugs.launchpad.net/refstack/+bug/170932316:10
openstackLaunchpad bug 1709323 in refstack "refstack-client removes tests which could be found by id (renamed tests)" [Undecided,New]16:10
zhipenghogepodge got it :)16:10
zhipengcatherineD thx will take a look at it16:10
catherineDthese are actually testing 2 different feature using the same test method16:11
catherineDit is like test the same thing in IPv4 vs IPv616:11
eglutecatherineD but different tests should have different ids, correct?16:11
hogepodgethat's a case of overload16:12
catherineDno ID is define at the test methid level16:12
hogepodgeeglute: in the code they don't16:12
catherineDInterop-WG define test at the test case leve16:12
hogepodgethe tests use different input parameters.16:12
catherineDsee the explaination in https://bugs.launchpad.net/refstack/+bug/170932316:12
openstackLaunchpad bug 1709323 in refstack "refstack-client removes tests which could be found by id (renamed tests)" [Undecided,New]16:12
hogepodgeWe might want to ask the tempest team if we should introduce wrapper methods16:12
eglutethanks catherineD16:13
egluteanything else related to this?16:13
catherineDRefStack dioes not use test ID for pass/fail evaluation at all . Tests are also mapping with FQM from testlist.16:14
eglutethank you catherineD16:14
eglutegood to know16:14
eglute#topic Extension programs16:14
*** openstack changes topic to "Extension programs (Meeting topic: interopwg)"16:14
eglutethank you hogepodge for submitting patches16:15
eglutehogepodge question: when do you want to get those approved? 2017.09 or 2018.01?16:15
* markvoelker is leaning toward advisory by 2017.09 given that we have the extra month, personally16:16
hogepodgeeglute: I'd like to present them to the board as advisory for 2017.09, with the intention to refine them for official approval in 2018.0116:16
markvoelker++16:16
hogepodgeeglute: refine them with community and vendor feedback16:16
egluteok, then should the capabilities be as "advisory"? right now all are required.16:17
hogepodgeThere's good discussion happening right now, which I want to encourage, but I'd also like them to be on track for board approval in early next year. I think that strikes a good balance between expediency and community review.16:17
hogepodgeeglute: probably. I struggled with how to handle this the first time around. But yes, I think that's the right way to go16:17
hogepodgeI can send up new patches.16:17
egluteyeah, we should decide how new programs should be handled. advisory is good, and if someone wants early designate/heat badge, they should pass all the advisory capabilities16:18
hogepodgeI'd also like to bring up the notion of criteria. Right now the only criteria I have is PTL suggested, but I'm wondering if during the advisory period if we need a new set of criteria for extensions.16:18
*** lyan has quit IRC16:19
markvoelkerhogepodge: I was noodling that a little this week too as I'm looking at verticals (for example: we've already been talking to OPNFV and I have some requirements suggested by ONAP now too)16:19
eglutehogepodge is that what you call achievements?16:19
zhipengmarkvoelker seems like ONAP is on a different level from OpenStack ?16:20
hogepodgeeglute: yes16:20
markvoelkereglute: see also: https://github.com/openstack/interop/blob/master/doc/source/schema/2.0.rst#criteria16:21
*** pbourke has quit IRC16:21
markvoelkerzhipeng: Yes, but they consume OpenStack via the multi-vim project.16:21
zhipengah understood16:22
eglutei think for criteria we should try to use the ones as we use for main guidelines, except as it relates to that particular project16:22
eglutemarkvoelker hogepodge has something called "achievements" in the json, but i wasnt sure what it tied to in teh schema16:23
*** pbourke has joined #openstack-meeting-316:23
*** tobberydberg has joined #openstack-meeting-316:23
hogepodgepart of our confusing lexicon, we say achievements when a capability achieves the criteria16:23
hogepodgeso there's a synonym there16:23
eglutehogepodge true16:24
eglutehogepodge how is that tied to schema16:24
markvoelkerhogepodge: I had noticed you added the "ptl_proposed" achievements in those patches and was trying to think if using it as a way to define a source ("who wants this") made sense16:24
egluteheh16:25
hogepodgemarkvoelker: I couldn't think of any other criteria. I asked project leaders for APIs they, as project leaders, thought represented the interoperable set according to our requirements (not admin, single user, etc)16:25
egluteperhaps ptls could score those capabilities on how important they are16:25
markvoelkerE.g. in the NFV vertical program case I might have some stuff we want to denote as "OPNFV needs this" and others as "ONAP needs this" or even specifically "ONAP multi-vim needs this".16:26
hogepodgeschema 2.0 was designed to allow for different sets of criteria to be used16:26
*** stendulker has joined #openstack-meeting-316:26
mugsiePTLs should know what capabilities will need to be used across clouds16:26
markvoelkerBut I'm not really sure that's what we want to use for achievements...my gut feel is to use similar criteria to what we use for Powered, but scope them to appropropriate audience16:26
hogepodgeand since the guideline is what's approved I put the criteria in the document so that they get pulled along with the approval. But I'm entirely happy to work on new criteria16:26
*** abalutoiu has quit IRC16:26
hogepodgerepurpose old, and so on16:27
eglutemarkvoelker hogepodge i think it would be good to have some official documentation/justification for including capabilities in these new programs.16:27
markvoelkerE.g. if a thing is needed by both OPNFV and ONAP it's widely deployed (among clouds used for NFV)16:27
eglutemarkvoelker i agree on " to use similar criteria to what we use for Powered, but scope them to appropropriate audience"16:27
markvoelker(kinda poor example but you get the picture)16:27
*** tobberydberg has quit IRC16:27
hogepodgeeglute: I would like the guidelines to contain all of the information, but I'd happily document it elsewhere16:28
eglutehogepodge i mean something similar to current scoring process16:28
eglutewe have all the capabilities scored, and comments on some why they were scored that way16:28
hogepodgesure, I just don't think that the criteria for the core programs is 100% applicable to the extension or vertical programs16:29
egluteso that next time we look, we have a reference point16:29
eglutehogepodge not even if it is scoped down?16:29
hogepodgeeglute: scoped down, yes16:29
eglutei think it would have to be scoped to that particular project. For example, for every cloud that deploys Heat, do most have X feature?16:30
hogepodgeI'm hearing that I need to update the two reviews and submit a third with proposed extension criteria?16:30
eglutewe need something that would justify why a set of capabilities are included16:32
hogepodgeIt's just so difficult to measure something like that, and my inclination is to drop a criteria like that. It's an extension which is a special case, and since it's optional being more strict on what has to be there makes more sense. I don't want a bunch of extensions that only add things in name16:32
*** ccamacho has quit IRC16:32
markvoelkerhogepodge: If we're going with the "same criteria, scoped to appropriate audience" then I'm not sure we need to doc them in a third patch...that's pretty much what we've presented to the BoD and community several times now.16:32
hogepodgeright now the justification is that project leaders have identified the capability as what's required for interoperable16:32
eglutehogepodge i think it is good enough for getting them as advisory16:33
hogepodgemarkvoelker: sure, but if we want external documentation that says something about why we chose a set of criteria for extensions we will have a one to many situation :-D16:33
eglutebut going forward, we will need some paper trail of why those particular capabilities were chosen16:33
markvoelkerhogepodge: If we're using the same criteria (but scoped) then we already have most of the doc though.16:35
hogepodgemarkvoelker: ok16:35
markvoelkerE.g. I'd be fine with a smallish doc that basically boils down to something along the lines of "same as https://github.com/openstack/interop/blob/master/doc/source/process/CoreCriteria.rst but with the audience scoped to the project in question"16:36
*** yamahata has quit IRC16:36
eglute+1.16:37
markvoelkerI'm not a big fan of "ptl_proposed" as I think it's too course.  The PTL probably has good reasons for proposing a capability, and I think if we use the core criteria (scoped) then it gives them a chance to back it with reasons rather than just being one person's opinion.16:38
hogepodgemarkvoelker: ok16:38
hogepodge(me saying ok like that makes it sound way more terse than I intend) :-D16:39
markvoelker=)16:39
eglutehogepodge i think we can work on those extra capabilities between now and next year, when the new programs become required16:40
eglutei think we should be able to get it approved as advisory next month16:40
hogepodgeEspecially since there's a conversation around heat that I was to give the full space to breathe16:41
*** zhipeng has quit IRC16:41
*** zhipeng has joined #openstack-meeting-316:41
egluteheat: #link https://review.openstack.org/#/c/490648/16:41
eglutei agree, good discussion there16:42
egluteanybody want to share their thoughts on heat or designate programs?16:43
ricolineglute, yes thanks guys to propose heat out:)16:44
egluteI think heat and designate are great add-ons to start with16:45
markvoelkerGenerally it seems like a reasonable start on both fronts, though personally I'd like to spend some time picking through some tooling around some of them.  Just elbow grease+time. =)16:45
eglutewe do want as much discussion as possible at this stage16:45
*** lpetrut has joined #openstack-meeting-316:45
eglutemarkvoelker what kind of tooling do you think we should work on?16:46
hogepodgeI think that's the intent of advisory, and we're in a good place to fulfill that intent16:46
markvoelkerWell, just generally I'm looking for justifications that the capabilities are useful, and tooling is often a good indicator: e.g. if tools that use (for ex.) Designate support a bunch of API's but not others, maybe we need to look a little more closely at those that no tools use and see if they're actually good, useful candidates.16:47
*** tobberydberg has joined #openstack-meeting-316:47
markvoelkerThe very fact that people are suggesting them is a good start, so just looking for some more backing for those opinions16:47
eglutehogepodge i agree, good start for advisory16:47
eglutemarkvoelker +116:47
markvoelkerSo basically the typical scoring process. =)16:48
mugsiemarkvoelker: sure - thats what we did when we suggested our (Designates) list16:48
markvoelker++16:49
*** lyan has joined #openstack-meeting-316:49
markvoelkermugsie: did you folks keep notes or something along the way?  Would love to take a peek if so.16:50
eglutemugsie thanks for working on the designate capabilities. we are just looking for additional documentation on why these particular capabilities were chosen. something like this: https://github.com/openstack/interop/blob/master/working_materials/scoring.txt16:50
mugsieunfortunatly not- we did it in person in boston16:51
mugsieAll i have is https://etherpad.openstack.org/p/BOS-Forum-DNS-InterOp16:51
markvoelkerAh, ok.  No worries.16:51
mugsieand https://etherpad.openstack.org/p/DNS-InterOp-Capabilities16:51
*** zhipeng has quit IRC16:52
*** tobberydberg has quit IRC16:52
*** spzala has joined #openstack-meeting-316:52
egluteso everyone ok with proposing heat and designate add-ons as advisory to the board in September?16:52
eglutemugsie do any of the tests require admin? do you know?16:53
mugsiethey do not16:53
eglutemugsie great, thank you16:53
mugsieits is just 2 endpoints - creating / update / deleting a DNS zone and modifying Records16:54
eglutemugsie thank you. seems like it covers essential interop for DNS16:55
hogepodgetime check five minutes16:55
egluteok, so everyone ok with proposing heat and designate add-ons as advisory to the board in September?16:55
markvoelkerYep (pending the iterations hogepodge mentioned)16:55
hogepodgeI can get to work on those for next week16:55
eglute+116:55
eglutethank you hogepodge16:55
hogepodgemugsie: if you can offer any insight into scoring, that would be really great16:56
mugsiesure - I will have a read of the methodolgy and comment in the review16:56
eglutemugsie let us know if you would like to understand scoring better, i can help16:56
hogepodgericolin: same with you16:57
mugsiegreat - if I have any questions, I will shout16:57
eglutemugsie perfect!16:57
ricolinhogepodge, sure16:57
eglutesince we are almost out of time, everyone, please be sure to review any outstanding patches16:58
hogepodgeThank you everyone, I think this is a really bold and important step forward, and I'm inspired by the interest in seeing it be successful.16:58
egluteas well as this RefStack patch:16:58
eglutehttps://review.openstack.org/#/c/480298/16:58
eglutehogepodge mugsie ricolin thank you so much for working on this16:58
*** tobberydberg has joined #openstack-meeting-316:58
egluteany last words?16:58
*** anilvenkata has quit IRC16:58
markvoelkerVeryvery quickly on the NFV vertical front: last week I spoke with some folks from ONAP multi-vim.  They have a rough list of stuff they need from OpenStack here that folks may want to look over: https://wiki.onap.org/pages/viewpage.action?pageId=822923516:58
ricolineglute, NP it takes entire heat team to make it:)16:59
markvoelkerI'll have that boiled down into actual API's by the time we get to Denver.16:59
eglutethank you markvoelker16:59
eglutericolin very true!16:59
eglute#action everyone look at https://wiki.onap.org/pages/viewpage.action?pageId=8229235 before next meeting16:59
egluteping us on interop channel or directly if needed.17:00
eglutethanks everyone!17:00
eglute#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
*** strigazi_OFF is now known as strigazi17:00
openstackMeeting ended Wed Aug 16 17:00:12 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-08-16-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/interopwg/2017/interopwg.2017-08-16-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/interopwg/2017/interopwg.2017-08-16-16.00.log.html17:00
*** tobberydberg has quit IRC17:02
*** slaweq has joined #openstack-meeting-317:03
*** Swami has joined #openstack-meeting-317:04
*** catherineD has left #openstack-meeting-317:06
*** diablo_rojo has joined #openstack-meeting-317:06
*** AndroUser2 has joined #openstack-meeting-317:07
*** slaweq has quit IRC17:07
*** lpetrut has quit IRC17:07
*** Sukhdev_ has quit IRC17:09
*** esikachev has joined #openstack-meeting-317:13
*** yamahata has joined #openstack-meeting-317:16
*** esikache1 has quit IRC17:16
*** lhx__ has quit IRC17:19
*** sambetts is now known as sambetts|afk17:23
*** tobberydberg has joined #openstack-meeting-317:29
*** MarkBaker has quit IRC17:29
*** Sukhdev has quit IRC17:32
*** tobberydberg has quit IRC17:33
*** spzala has quit IRC17:34
*** spzala has joined #openstack-meeting-317:35
*** spzala has quit IRC17:39
*** donghao has quit IRC17:39
*** tellesnobrega has quit IRC17:40
*** tellesnobrega has joined #openstack-meeting-317:42
*** ricolin has quit IRC17:46
*** stendulker has quit IRC17:50
*** lpetrut has joined #openstack-meeting-317:50
*** ociuhandu has quit IRC17:55
*** strigazi is now known as strigazi_OFF17:55
*** slaweq has joined #openstack-meeting-318:03
*** spzala has joined #openstack-meeting-318:03
*** slaweq has quit IRC18:09
*** pcaruana has joined #openstack-meeting-318:09
*** pboutin has joined #openstack-meeting-318:14
*** slaweq has joined #openstack-meeting-318:15
*** tobberydberg has joined #openstack-meeting-318:18
*** tobberydberg has quit IRC18:19
*** tobberydberg has joined #openstack-meeting-318:20
*** makowals_ has joined #openstack-meeting-318:21
*** ociuhandu has joined #openstack-meeting-318:21
*** tobberydberg has quit IRC18:22
*** tobberydberg has joined #openstack-meeting-318:22
*** tobberydberg has quit IRC18:26
*** AndroUser2 has quit IRC18:27
*** AndroUser2 has joined #openstack-meeting-318:27
*** esikachev has quit IRC18:31
*** AndroUser2 has quit IRC18:31
*** marst_ has joined #openstack-meeting-318:34
*** marst has quit IRC18:37
*** esikachev has joined #openstack-meeting-318:39
*** esikachev has quit IRC18:44
*** tobberydberg has joined #openstack-meeting-318:46
*** tobberydberg has quit IRC18:51
*** Sukhdev has joined #openstack-meeting-318:52
*** AndroUser2 has joined #openstack-meeting-319:06
*** armstrong has joined #openstack-meeting-319:11
*** shuyingya has joined #openstack-meeting-319:35
*** esikachev has joined #openstack-meeting-319:40
*** shuyingya has quit IRC19:40
*** e0ne has joined #openstack-meeting-319:42
*** Sukhdev has quit IRC19:43
*** esikachev has quit IRC19:44
*** rmascena has joined #openstack-meeting-319:48
*** raildo has quit IRC19:51
*** rdopiera_pto has joined #openstack-meeting-319:52
*** ying_zuo has joined #openstack-meeting-319:59
robcresswell#startmeeting horizon20:00
*** gary-smith has joined #openstack-meeting-320:00
openstackMeeting started Wed Aug 16 20:00:04 2017 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: horizon)"20:00
openstackThe meeting name has been set to 'horizon'20:00
* robcresswell is on time!20:00
gary-smith\o/20:00
makowals_Good evening everyone !20:00
e0nehi20:00
dklyleo/20:01
ying_zuohi everyone :)20:01
robcresswellI'll give everyone a couple of minutes to wander in20:01
rdopiera_pto \o\ \o/ /o/20:01
robcresswellHaha20:01
robcresswellrdopiera_pto dances in to the room20:02
ying_zuo:)20:02
rdopiera_pto_/o/~20:02
rdopiera_ptowalk like an egyptian20:02
robcresswellHaha20:02
robcresswell#topic Notices20:02
*** openstack changes topic to "Notices (Meeting topic: horizon)"20:02
robcresswellSo, a couple of things20:02
robcresswell#info RC2 tag soon. Need to sync with i18n on translations, and merge a couple of high priority bugs20:03
robcresswellThis will also the the last meeting I run, as ying_zuo will be stepping up :)20:04
e0nerobcresswell: are these bugs already backported?20:04
robcresswelle0ne: no20:04
e0ne:(20:04
e0nejust trying to understand what are priorities for stable/pike branch reviews20:05
robcresswellCheck the LP branch as usual20:05
e0neok, thanks20:05
robcresswellOn phone atm, if anyone has a link handy...20:05
robcresswellAnyway, backporting is trivial, it just adds to the gate time slightly20:06
rdopiera_ptohttps://launchpad.net/horizon/12.0.0-pike/pike-320:06
e0ne#link https://launchpad.net/horizon/+milestone/pike-rc220:06
robcresswellBut there are a couple patches at pike-rc220:06
rdopiera_ptono wait20:07
rdopiera_ptosorry20:07
robcresswellBoom, thanks e0ne20:07
robcresswell.... And thanks for trying rdopiera_pto20:07
e0nerobcresswell: np20:07
robcresswell;)20:07
robcresswellAs before, please test things out, check with product teams if possible, use horizon against staging / testing envs20:08
robcresswellThis is a good time to land any critical issues before the release goes out20:09
robcresswellWe aim to run against older clouds, so you don't need to test against pike clouds (could be N / O)20:10
e0ne#link https://releases.openstack.org/pike/schedule.html20:10
e0ne^^ maybe someone was was looking for it too20:10
robcresswellAnd finally, please take a look at the PTG planning etherpad; even if you're not attending, if you can describe an issue you think should be discussed, we can consider it20:11
robcresswell#link https://etherpad.openstack.org/p/horizon-ptg-queens20:11
robcresswellThanks e0ne20:11
robcresswellThat's everything from me :)20:11
robcresswell#topic Open Discussion20:11
*** openstack changes topic to "Open Discussion (Meeting topic: horizon)"20:11
makowals_Hi again, two patches would be happy to get some comments/actions20:12
* robcresswell just switched back to laptop20:12
makowals_https://review.openstack.org/#/c/418246/20:13
makowals_and https://review.openstack.org/#/c/426493/20:13
*** Sukhdev has joined #openstack-meeting-320:13
makowals_The latter was tagged as rc1 by the way20:13
*** srobert has quit IRC20:13
makowals_Don't know if not too late for any of them, but anyway, even if just for master, still good20:13
robcresswellhmm, that was me, I should've put that queen-1 though. Its feature work.20:14
robcresswellThe images bug could go in to Pike, however20:14
robcresswellyeesh that images code20:15
robcresswellOkay, I've starred it, thats going to take some time to get my head round20:15
robcresswellBoth are good patches though, thanks for the reminder20:16
makowals_Thanks ! Also one question from a different branch20:16
makowals_What I noticed -- or in fact users reported ;) -- when creating an instance, the panel does not validate name at all20:17
makowals_This is consistent with nova which also does not validate it at all; however at least in some cases it would make sense to put some regex validation against the name (as ex. in networking stages we have some restrictions)20:17
robcresswell:/20:17
robcresswellWhy would that "make sense"?20:18
makowals_Thus the question, would it make sense to make a patch with optional config option to enable validation agains some RFC ?20:18
makowals_If you try to create instance with the following name -- +1%&abc -- is it okay ?20:18
robcresswellmakowals_: Are your users regularly trying to launch instances with those names?20:18
dklylethe create instance code will check what nova checks IIRC which is not much20:19
rdopiera_ptowhat happens when horizon's validation doesn't match the service's requirements?20:19
robcresswellI mean I get the "people will break things however possible" but fixing that in the UI is not the way to do it. We can't sanitise APIs.20:19
makowals_Definitely not regularly, but we had few reports from users trying to use colon or semicolon20:19
rdopiera_ptoshouldn't that happen on the service side?20:19
dklylerdopiera_pto, we hope we are the more accepting of the two20:19
robcresswellmakowals_: What's the problem if they use a semicolon?20:20
rdopiera_ptoright, we would catch the error from the service and display it20:20
robcresswellI mean, I think we should just match the API personally. And if they dont validate, we shouldnt.20:20
makowals_Semicolon as a dns name, not really acceptable20:20
dklylenova bars very little, we had a bug capturing all that a couple of releases ago20:20
makowals_The case now it's nova does not catch any of those, so we have an errors in the next stages (registering instance in the dns)20:21
makowals_s/it's/is20:21
robcresswellRight20:21
dklylethen we can't create rules20:21
robcresswellgo yell at nova :)20:21
makowals_:D20:21
dklylechange should be made in nova20:21
dklylethen we could reflect that20:22
robcresswell+120:22
makowals_Yep, that's what I thought, nova first, horizon second20:22
dklyleif you wanted to add a mechanism to validate names, you could, but that leaves a big hole via the CLI and APIs20:22
dklylejust in horizon that is20:22
makowals_Okay, I will try to push nova guys for this then; anyway local patch is ready so it won't be any trouble to put it in here afterwards20:24
robcresswellSure20:24
lucasxuspeaking of which, will horizon support a ceph backend swift, or just the openstack swift only  :)20:24
robcresswelllucasxu: That depends if someone wants to implement it.20:25
dklylehorizon shouldn't care20:25
dklylewe only talk to the APIs20:25
lucasxurobcresswell, hmm, interesting. Thanks20:25
robcresswelldklyle: Yeah, I think we have some expectations that don't exist in Ceph20:25
e0nethe problem is ceph ragos-gw doen't implement 100% of swift API20:25
dklyleone header is all I recall20:25
lucasxudklyle, yeah, make sense20:26
robcresswelllucasxu: The issue is really about us not knowing how its broken and how to recreate those issues20:26
robcresswellBut otherwise, we should just support what the API does.20:27
lucasxukk, i am not that familiar with rgw though. A co-worker asked me this today since he found a bug. Horizon logged out him when he was trying to create a container that has the same name as that of an existing one. So..20:27
e0nerobcresswell: +120:27
robcresswellI imagine we are relying on some values existing that don't with a certain driver / plugin / backend, whatever.20:27
lucasxuthanks and make sense to me20:27
robcresswelllucasxu: Basically, yes, if support is broken, it is a bug. But realistically, that doesn't mean we can immediately support it. If you can work with us on it, we're happy to.20:28
robcresswellyou / your colleagues20:28
dklyleif there are optional parts of the API we are requiring then it would make sense to treat those as optional in Horizon rather than required20:28
robcresswelldklyle: ++20:28
robcresswellI would imagine thats what we're doing20:29
*** rmascena has quit IRC20:29
robcresswellexpecting fields / validation / APIs that aren't reliably there.20:29
lucasxurobcresswell, sounds good. I haven't looked further on that since to me, it is more like a ceph rgw bug since it returns a 401 and horizon receives that 401 then logs out the user. Which is the correct workflow.20:29
robcresswelllucasxu: Okay, well, feel free to open bugs etc.20:29
lucasxurobcresswell, sure, will look into that. I don't think it happens in the openstack swift. Will provide more details later.20:30
lucasxuthanks guys.20:30
robcresswellNo problem20:30
robcresswellAny other questions / bugs / patches etc?20:32
robcresswellAlright, I think we can call it there20:35
robcresswellThanks everyone!20:35
robcresswell#endmeeting20:35
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:35
e0nesee you next week20:35
openstackMeeting ended Wed Aug 16 20:35:16 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-08-16-20.00.html20:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-08-16-20.00.txt20:35
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-08-16-20.00.log.html20:35
makowals_Thanks, bye !20:35
*** makowals_ has quit IRC20:36
*** e0ne has quit IRC20:36
*** pcaruana has quit IRC20:41
*** esikachev has joined #openstack-meeting-320:41
*** gary-smith has left #openstack-meeting-320:43
*** esikachev has quit IRC20:45
*** gouthamr has quit IRC20:46
*** cleong has quit IRC20:51
*** diablo_rojo has quit IRC20:55
*** lpetrut has quit IRC20:56
*** diablo_rojo has joined #openstack-meeting-320:57
*** lucasxu has quit IRC20:57
*** lpetrut has joined #openstack-meeting-320:58
*** spzala has quit IRC20:58
*** spzala has joined #openstack-meeting-321:00
*** vishwana_ has quit IRC21:03
*** vishwanathj has joined #openstack-meeting-321:04
*** spzala has quit IRC21:05
*** slaweq has quit IRC21:06
*** AndroUser2 has quit IRC21:06
*** slaweq has joined #openstack-meeting-321:06
*** VW_ has joined #openstack-meeting-321:06
*** VW has quit IRC21:09
*** VW_ has quit IRC21:11
*** slaweq has quit IRC21:11
*** rama_y has quit IRC21:18
*** lpetrut has quit IRC21:34
*** slaweq has joined #openstack-meeting-321:36
*** bobh has joined #openstack-meeting-321:40
*** esikachev has joined #openstack-meeting-321:41
*** slaweq has quit IRC21:42
*** slaweq has joined #openstack-meeting-321:43
*** yamamoto has joined #openstack-meeting-321:44
*** yamamoto has quit IRC21:45
*** armstrong has quit IRC21:45
*** esikachev has quit IRC21:46
*** slaweq has quit IRC21:47
*** yamamoto has joined #openstack-meeting-321:51
*** vishwana_ has joined #openstack-meeting-321:54
*** caboucha has quit IRC21:54
*** yamamoto has quit IRC21:58
*** vishwanathj has quit IRC21:58
*** iyamahat has joined #openstack-meeting-322:07
*** VW has joined #openstack-meeting-322:33
*** VW has quit IRC22:35
*** esikachev has joined #openstack-meeting-322:42
*** VW has joined #openstack-meeting-322:42
*** bobh has quit IRC22:43
*** bobh has joined #openstack-meeting-322:43
*** VW has quit IRC22:45
*** esikachev has quit IRC22:47
*** bobh has quit IRC22:48
*** ying_zuo has left #openstack-meeting-322:52
*** marst_ has quit IRC23:06
*** makowals has quit IRC23:06
*** makowals has joined #openstack-meeting-323:11
*** notmyname has quit IRC23:19
*** notmyname has joined #openstack-meeting-323:23
*** gouthamr has joined #openstack-meeting-323:27
*** chyka has quit IRC23:32
*** chyka has joined #openstack-meeting-323:33
*** Swami has quit IRC23:33
*** spzala has joined #openstack-meeting-323:34
*** shuyingya has joined #openstack-meeting-323:37
*** spzala has quit IRC23:38
*** shuyingya has quit IRC23:41
*** esikachev has joined #openstack-meeting-323:43
*** chyka has quit IRC23:45
*** esikachev has quit IRC23:47

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