Tuesday, 2017-01-03

*** rbudden has quit IRC00:00
*** adreznec has joined #openstack-meeting00:01
*** bobmel has quit IRC00:12
*** yangyapeng has joined #openstack-meeting00:14
*** Julien-zte has joined #openstack-meeting00:17
*** yangyapeng has quit IRC00:18
*** rbudden has joined #openstack-meeting00:18
*** mickeys has quit IRC00:19
*** rbudden has quit IRC00:22
*** bobh has joined #openstack-meeting00:22
*** JRobinson__ has joined #openstack-meeting00:26
*** bobh has quit IRC00:27
*** VW has joined #openstack-meeting00:28
*** JRobinson__ has quit IRC00:29
*** VW has quit IRC00:30
*** VW has joined #openstack-meeting00:31
*** bobmel has joined #openstack-meeting00:31
*** rbudden has joined #openstack-meeting00:36
*** bobmel has quit IRC00:36
*** guoshan has joined #openstack-meeting00:38
*** rfolco has quit IRC00:42
*** bzhao_ has quit IRC00:44
*** rbudden has quit IRC00:44
*** Wenzhi has joined #openstack-meeting00:49
*** david-lyle has joined #openstack-meeting00:51
*** david-lyle has quit IRC00:55
*** zhonghua has quit IRC00:59
*** zhonghua has joined #openstack-meeting01:00
*** salv-orlando has joined #openstack-meeting01:00
*** salv-orlando has quit IRC01:02
*** salv-orlando has joined #openstack-meeting01:02
*** zhurong has joined #openstack-meeting01:05
*** markvoelker has joined #openstack-meeting01:05
*** oomichi has quit IRC01:05
*** salv-orlando has quit IRC01:07
*** oomichi has joined #openstack-meeting01:07
*** guoshan has quit IRC01:08
*** markvoelker has quit IRC01:09
*** oomichi has quit IRC01:13
*** VW has quit IRC01:14
*** oomichi has joined #openstack-meeting01:16
*** reedip_ has joined #openstack-meeting01:17
*** mickeys has joined #openstack-meeting01:20
*** yangyapeng has joined #openstack-meeting01:20
*** mickeys has quit IRC01:24
*** guoshan has joined #openstack-meeting01:34
*** zz_dimtruck is now known as dimtruck01:42
*** kevinz has joined #openstack-meeting01:49
*** huanxuan has joined #openstack-meeting01:51
*** yangyape_ has joined #openstack-meeting01:59
*** yangyapeng has quit IRC02:02
*** salv-orlando has joined #openstack-meeting02:03
*** markvoelker has joined #openstack-meeting02:05
*** clayton has quit IRC02:06
*** salv-orlando has quit IRC02:08
*** markvoelker has quit IRC02:10
*** sdake has joined #openstack-meeting02:11
*** sdake has quit IRC02:15
*** sdake has joined #openstack-meeting02:16
*** mriedem has quit IRC02:20
*** mickeys has joined #openstack-meeting02:21
*** hongbin has joined #openstack-meeting02:21
*** bobh has joined #openstack-meeting02:24
*** mickeys has quit IRC02:25
*** zhurong has quit IRC02:25
*** clayton has joined #openstack-meeting02:25
*** julim has joined #openstack-meeting02:26
*** bobh has quit IRC02:29
*** julim has quit IRC02:31
*** sdake has quit IRC02:31
*** gcb has joined #openstack-meeting02:36
*** mkrai has joined #openstack-meeting02:38
*** bobmel has joined #openstack-meeting02:40
*** guoshan has quit IRC02:45
*** bobmel has quit IRC02:45
*** cloud_player has joined #openstack-meeting02:51
*** david-lyle has joined #openstack-meeting02:52
*** dimtruck is now known as zz_dimtruck02:53
*** yangyapeng has joined #openstack-meeting02:54
*** neiljerram has quit IRC02:56
*** david-lyle has quit IRC02:57
*** yangyape_ has quit IRC02:58
*** Namrata has joined #openstack-meeting02:58
*** pksingh has joined #openstack-meeting03:00
hongbin#startmeeting zun03:00
openstackMeeting started Tue Jan  3 03:00:17 2017 UTC and is due to finish in 60 minutes.  The chair is hongbin. Information about MeetBot at http://wiki.debian.org/MeetBot.03:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.03:00
*** openstack changes topic to " (Meeting topic: zun)"03:00
openstackThe meeting name has been set to 'zun'03:00
pksinghpksingh03:00
hongbin#link https://wiki.openstack.org/wiki/Zun#Agenda_for_2017-01-03_0300_UTC Today's agenda03:00
hongbin#topic Roll Call03:00
*** openstack changes topic to "Roll Call (Meeting topic: zun)"03:00
NamrataNamrata03:00
WenzhiWenzhi03:00
pksinghHappy New Year to all03:00
mkraiMadhuri Kumari03:00
kevinzkevinz03:00
hongbinThanks for joining the meeting pksingh Namrata Wenzhi mkrai kevinz03:01
hongbinall, happy new year03:01
mkraiHappy New Year all :)03:01
Wenzhihappy new year!03:01
hongbin#topic Announcements03:01
*** openstack changes topic to "Announcements (Meeting topic: zun)"03:01
hongbini have no announcement03:01
hongbinanyone else has announcement?03:02
hongbin#topic Review Action Items03:02
*** openstack changes topic to "Review Action Items (Meeting topic: zun)"03:02
hongbin1. hongbin start a ML to osc team to discus the name collision issue (DONE)03:02
hongbin#link http://lists.openstack.org/pipermail/openstack-dev/2016-December/109259.html03:02
hongbinafter discussing with the osc team, we agreed to use the keyword 'appcontainer' to represent a zun container resource03:03
hongbine.g. openestack appcontainer create/delete/....03:03
hongbinany comment on this renaming?03:03
Namratathanks hongbin03:03
Wenzhinot beautiful, but acceptable :)03:03
hongbinp.s. it is renamed on osc only03:03
mkraiLGTM03:04
*** salv-orlando has joined #openstack-meeting03:04
hongbinNamrata: np at all03:04
hongbinok, sounds good03:04
hongbin#topic Set etcd as the default DB backend (Wenzhi)03:04
*** openstack changes topic to "Set etcd as the default DB backend (Wenzhi) (Meeting topic: zun)"03:04
hongbin#link https://review.openstack.org/#/c/412756/03:04
hongbinWenzhi: you want to drive this one?03:04
Wenzhisure03:05
Wenzhithe code for etcd data model (zun_service, container, image) and etcd db api has already been landed03:05
Wenzhithanks all for help on code review03:05
Wenzhiand I already submitted a patch to add a new pipeline to test etcd db backend03:06
Wenzhihttps://review.openstack.org/#/c/415391/03:06
*** markvoelker has joined #openstack-meeting03:06
WenzhiI did some manual tests, and found some bugs in etcd api, I have a WIP patch in hand to fix the bugs03:07
Wenzhiwill upload for review after the pipeline patch been merged03:07
mkraiWenzhi: What are the rationale to make etcd to default DB?03:07
mkraiIt will be better to write this in commit message so that reviewers understands the need for it03:08
Wenzhimkrai: we've discussed that in project plan at the very beginning of Zun project03:08
Wenzhithe main benefit is that etcd is more fast and flexible03:08
*** salv-orlando has quit IRC03:08
Wenzhimkrai: will do that03:08
mkraiI know few of them but it is worth writing in commit message to let others know03:09
hongbinWenzhi: do you have a pointer about the project plan discussion?03:09
mkraiWenzhi: Thanks03:09
Wenzhicontainers are different from VMs, the states of them changes a lot03:09
Wenzhihttps://etherpad.openstack.org/p/zun-container-state-management03:10
Wenzhihongbin: the link ^^03:10
hongbin#link https://etherpad.openstack.org/p/zun-container-state-management03:10
*** markvoelker has quit IRC03:10
hongbinWenzhi: thx03:11
Wenzhinp03:11
NamrataI can try to test this feature when Hongbin's multihost patch is landed03:11
*** zhangjl has joined #openstack-meeting03:12
mkraithat would be great Namrata03:12
hongbinWenzhi: ok, it looks the rational of setting etcd as default is: the container state are changing faster than vm03:13
Wenzhihonbin: yes03:13
*** epico has joined #openstack-meeting03:13
hongbinWenzhi: this rational seems valid, but not written down in the etherpad though03:13
Wenzhiwill update the etherpad03:14
hongbinthen, i wanted to get opinions from others03:14
mkraiIMO we can take decision on making it default only when we have tested it well03:14
mkraihongbin: Wenzhi What do you think?03:14
hongbinall, what do you think about changing the default db to etcd? good idea? bad idea?03:14
pksinghmkrai: +1, i need to think about it03:14
Wenzhimkrai: agreed03:14
mkraiRational seems valid but difficult to say yes now03:15
hongbinok, then we can defer the decision until the etcd backend is well tested03:15
mkraiYes03:15
pksinghagree03:15
Wenzhi+103:15
hongbinok, sound good03:15
hongbinnext topic03:16
hongbin#topic Support multi-host deployment (hongbin)03:16
*** openstack changes topic to "Support multi-host deployment (hongbin) (Meeting topic: zun)"03:16
hongbin#link https://blueprints.launchpad.net/zun/+spec/support-multiple-hosts The BP03:16
hongbin#link https://review.openstack.org/#/c/415554/ The patch03:16
*** noslzzp has joined #openstack-meeting03:16
hongbini have submitted several patches for this bp03:16
hongbinthe idea is to implement a simple scheduler, and specify the server in rpc03:17
hongbin#link https://review.openstack.org/#/c/415554/ the wip patch03:17
hongbinin before, the zun-api call zun-compute without picking a server03:18
*** bkopilov has quit IRC03:18
hongbinthen, the rpc request was sent to the first zun-compute that picked up the message03:18
hongbinafter the patch, the zun-api will pick a server to send the request03:18
hongbinthe goal is to make sure the rpc request will send the right host that runs the container03:19
mkraihongbin: What's the filter we are using with this patch?03:19
hongbinthat is the general idea03:19
hongbinmkrai: for scheduling? we didn't use any filter right now03:19
mkraiYes03:19
hongbinmkrai: we used a random scheduler, that basically randomly picking a host03:20
mkraiSo on what basis the compute is choosen?03:20
hongbinmkrai: randomly chosen :)03:20
mkraiOk for initial implementation it is fine03:20
hongbinyes03:20
pksinghwe need to extend the scheduler when scheduler bp is implemented , i guess03:20
Wenzhisure thing ^^03:20
hongbinyes, that could be a future work03:21
Wenzhiagreed03:21
kevinz+103:21
hongbinanother possibility is to switch to the placement service once it is splitted out from nova03:21
*** mickeys has joined #openstack-meeting03:21
pksinghi need to look about placement service03:22
hongbinp.s. nova is splitting their scheduler out as a independent placement api03:22
*** gongysh has joined #openstack-meeting03:22
hongbinok03:22
hongbinjust fyi03:22
mkraithat will be best for us03:22
hongbinyes, if the placement service is there, we could leverage it03:22
mkraihongbin: is there any link for the discussion?03:22
hongbinmkrai: there are several session in hte nova design summit in barcelona03:23
mkraiOk I will look at them03:23
hongbinmkrai: i attent some sessions, possibly, there are some etherpads there03:23
pksinghhongbin: can we use nova docker driver and our scheduler together, i think no , right?03:24
hongbinpksingh: my initial thought is to use force-host option when nova driver is enabled03:24
hongbinpksingh: e.g. zun picked a host -> call nova with force-host -> nova creates sandbox in the specified host03:25
pksinghhongbin: will it disbale nova scheduler?03:25
hongbinpksingh: yes03:25
pksinghhongbin: ok seems ok03:25
hongbinpksingh: there might be other options to enable nova scheduler, which could be discuss further03:26
pksinghok03:26
hongbinany other comment about the multi-host support?03:26
hongbin#topic Introduce pod (hongbin)03:27
*** openstack changes topic to "Introduce pod (hongbin) (Meeting topic: zun)"03:27
hongbin#link https://blueprints.launchpad.net/zun/+spec/introduce-pod The BP03:27
hongbini will work on this bp after the multi-host bp is done03:27
hongbinhowever, i am happy to offload the work if you interest to implement this feature03:27
hongbinjust let me know if you do03:27
*** links has joined #openstack-meeting03:28
hongbincomments?03:28
pksinghhongbin: i can help03:28
*** mickeys has quit IRC03:28
hongbinpksingh: ack03:28
hongbinpksingh: thx, will work with you later on this one03:29
hongbin#topic Support interactive mode (kevinz)03:29
pksinghhongbin: sure03:29
*** openstack changes topic to "Support interactive mode (kevinz) (Meeting topic: zun)"03:29
hongbin#link https://blueprints.launchpad.net/zun/+spec/support-interactive-mode The BP03:29
hongbin#link https://review.openstack.org/#/c/396841/ The design spec03:29
hongbinkevinz: ^^03:29
kevinzI'v finished the tty resize function and escape code decode03:29
kevinz https://github.com/kevin-zhaoshuai/container-interactive-client03:29
kevinzNow working on integration with zun ,03:30
kevinzpatch will ready this week03:30
hongbinawesome!03:30
pksinghkevinz: great :)03:30
hongbinlooking forward to the patch03:30
kevinzhongbin: pksingh: OK thanks~ :-)03:31
hongbinkevinz: just 2 cents, the first patch doesn't need to be perfect, it could be just a prototype.03:31
pksinghagree with hongbin03:31
kevinzYeah, I think so03:32
hongbinkevinz: it could help because reviewers could give you earlier feedback based on that03:32
hongbinkevinz: ok03:32
hongbinkevinz: thanks for your hard work on this one03:32
kevinzGood ~ I will firsh implement "zun attach" and then "run" and exec03:32
hongbinsound like a good plan03:33
kevinzhongbin: My pleasure~ Thanks for your help03:33
hongbinnp03:33
hongbinany other remark on this one?03:33
kevinzNo more comments now :-)03:34
hongbinthanks kevinz03:34
hongbin#topic Make Zunclient an OpenStackClient plugin (Namrata)03:34
*** openstack changes topic to "Make Zunclient an OpenStackClient plugin (Namrata) (Meeting topic: zun)"03:34
hongbin#link https://blueprints.launchpad.net/zun/+spec/zun-osc-plugin03:34
hongbinNamrata: ^^03:34
*** links has quit IRC03:34
*** clayton has quit IRC03:34
*** adreznec has quit IRC03:34
*** kevinz has quit IRC03:34
*** Julien-zte has quit IRC03:34
*** pksingh has quit IRC03:34
*** reedip_ has quit IRC03:34
*** tommylikehu_ has quit IRC03:34
NamrataI have submitted 4 osc command plugins03:34
*** kevinz has joined #openstack-meeting03:34
*** Julien-zte has joined #openstack-meeting03:35
*** links has joined #openstack-meeting03:35
*** clayton has joined #openstack-meeting03:35
*** adreznec has joined #openstack-meeting03:35
*** pksingh has joined #openstack-meeting03:35
*** reedip_ has joined #openstack-meeting03:35
*** tommylikehu_ has joined #openstack-meeting03:35
Namrataand simultaneously working on spec as suggested by stevemar03:35
hongbini see03:36
NamrataI will submit the spec this week03:36
hongbinNamrata: i think just a simple spec would be enough03:36
Namrataokay great.03:37
hongbinNamrata: i mean the design of the osc plugin is already clear, no need to spend too much time on the spec03:37
Namrataokay03:37
hongbinbtw, the 4 patches look good03:38
*** mickeys has joined #openstack-meeting03:38
NamrataThanks hongbin03:38
hongbinNamrata: thanks for working on this feature03:38
hongbincomments from others?03:38
*** baoli has quit IRC03:38
NamrataMy pleasure.thanks for reviewing03:39
*** baoli has joined #openstack-meeting03:39
hongbin#topic Open Discussion03:39
*** openstack changes topic to "Open Discussion (Meeting topic: zun)"03:39
hongbinanyone has additional topic to bring up?03:40
pksinghi agree with sudipta view on https://review.openstack.org/#/c/415704/03:40
pksinghcan we abandon this patch03:40
mkraiI think we all have the same thought on this03:41
hongbinpksingh: we can ask the contributor to abandon the patch03:41
pksinghyes, i agree03:41
hongbin+103:41
*** r-mibu has quit IRC03:42
hongbinany other topic03:42
hongbinok, all, thanks for joining the meeting03:43
hongbin#endmeeting03:43
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"03:43
openstackMeeting ended Tue Jan  3 03:43:09 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)03:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-01-03-03.00.html03:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-01-03-03.00.txt03:43
openstackLog:            http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-01-03-03.00.log.html03:43
*** zhangjl has left #openstack-meeting03:43
*** JRobinson has joined #openstack-meeting03:43
*** JRobinson has quit IRC03:44
*** jrobinson has joined #openstack-meeting03:44
*** r-mibu has joined #openstack-meeting03:47
*** sdake has joined #openstack-meeting03:51
*** pksingh has quit IRC03:52
*** sudipto_ has joined #openstack-meeting03:52
*** sudipto has joined #openstack-meeting03:52
*** Namrata has quit IRC03:55
*** sdake has quit IRC03:56
*** jrobinson has quit IRC03:58
*** baoli_ has joined #openstack-meeting04:00
*** baoli has quit IRC04:02
*** stanchan has quit IRC04:03
*** salv-orlando has joined #openstack-meeting04:05
*** baoli_ has quit IRC04:06
*** baoli has joined #openstack-meeting04:07
*** salv-orlando has quit IRC04:09
*** yangyapeng has quit IRC04:12
*** hongbin has quit IRC04:12
*** yangyapeng has joined #openstack-meeting04:14
*** sacharya has quit IRC04:15
*** sacharya has joined #openstack-meeting04:16
*** gongysh has quit IRC04:19
*** sheel has joined #openstack-meeting04:20
*** sacharya has quit IRC04:21
*** rbudden has joined #openstack-meeting04:21
*** Wenzhi has quit IRC04:23
*** Wenzhi has joined #openstack-meeting04:23
*** bobh has joined #openstack-meeting04:25
*** Wenzhi has quit IRC04:28
*** baoli has quit IRC04:28
*** bobh has quit IRC04:30
*** Wenzhi has joined #openstack-meeting04:31
*** reedip_ has quit IRC04:35
*** edtubill has joined #openstack-meeting04:38
*** bobmel has joined #openstack-meeting04:41
*** edtubill has quit IRC04:42
*** saisrikiran has joined #openstack-meeting04:42
*** gus has joined #openstack-meeting04:44
*** bobmel has quit IRC04:46
*** bkopilov has joined #openstack-meeting04:55
*** sdake has joined #openstack-meeting04:56
*** janki has joined #openstack-meeting05:00
*** noslzzp has quit IRC05:00
*** salv-orlando has joined #openstack-meeting05:05
*** salv-orlando has quit IRC05:10
*** sudipto has quit IRC05:16
*** sudipto_ has quit IRC05:16
*** sacharya has joined #openstack-meeting05:17
*** ayogi has joined #openstack-meeting05:19
*** sacharya has quit IRC05:22
*** Akis__ has joined #openstack-meeting05:28
*** Akis_ has quit IRC05:31
*** prateek has joined #openstack-meeting05:32
*** anilvenkata has joined #openstack-meeting05:37
*** ykatabam has quit IRC05:37
*** sdake has quit IRC05:42
*** edisonxiang has joined #openstack-meeting05:43
*** sudipto has joined #openstack-meeting05:51
*** sudipto_ has joined #openstack-meeting05:51
*** prateek has quit IRC05:53
*** Wenzhi has quit IRC05:58
*** Wenzhi has joined #openstack-meeting05:58
*** Wenzhi has quit IRC06:01
*** Wenzhi has joined #openstack-meeting06:01
*** Wenzhi has quit IRC06:01
*** salv-orlando has joined #openstack-meeting06:06
*** saisrikiran has quit IRC06:06
*** salv-orlando has quit IRC06:11
*** nadya has joined #openstack-meeting06:13
*** Wenzhi has joined #openstack-meeting06:18
*** ljxiash has joined #openstack-meeting06:20
*** sridharg has joined #openstack-meeting06:27
*** bobh has joined #openstack-meeting06:27
*** rbudden has quit IRC06:27
*** janki has quit IRC06:28
*** ricolin has joined #openstack-meeting06:29
*** bobh has quit IRC06:31
*** janki has joined #openstack-meeting06:32
*** korzen has joined #openstack-meeting06:32
*** jchhatbar has joined #openstack-meeting06:35
*** prateek has joined #openstack-meeting06:36
*** janki has quit IRC06:38
*** jchhatbar is now known as janki06:39
*** zhiyuan has quit IRC06:42
*** joehuang has quit IRC06:43
*** sridharg has quit IRC06:45
*** sridharg has joined #openstack-meeting06:45
*** lpetrut has joined #openstack-meeting06:50
*** sdake has joined #openstack-meeting06:53
*** salv-orlando has joined #openstack-meeting06:55
*** lhx__ has joined #openstack-meeting06:57
*** ljxiash has quit IRC06:58
*** guoshan has joined #openstack-meeting07:05
*** sdake has quit IRC07:06
*** yangyape_ has joined #openstack-meeting07:11
*** salv-orl_ has joined #openstack-meeting07:13
*** yangyapeng has quit IRC07:14
*** salv-orlando has quit IRC07:16
*** sacharya has joined #openstack-meeting07:18
*** nadya has quit IRC07:18
*** e0ne has joined #openstack-meeting07:18
*** yuval has joined #openstack-meeting07:18
*** matrohon has quit IRC07:19
*** jchhatbar has joined #openstack-meeting07:19
*** zhiyuan has joined #openstack-meeting07:20
*** ljxiash has joined #openstack-meeting07:20
*** janki has quit IRC07:21
*** jchhatbar_ has joined #openstack-meeting07:22
*** sacharya has quit IRC07:22
*** Akis_ has joined #openstack-meeting07:24
*** jchhatbar has quit IRC07:25
*** ljxiash has quit IRC07:25
*** jprovazn has joined #openstack-meeting07:26
*** Akis__ has quit IRC07:27
*** e0ne has quit IRC07:27
*** zhiyuan has quit IRC07:28
*** ykatabam has joined #openstack-meeting07:29
*** gongysh has joined #openstack-meeting07:30
*** tesseract has joined #openstack-meeting07:30
*** gongysh has quit IRC07:31
*** e0ne has joined #openstack-meeting07:31
*** nmagnezi has joined #openstack-meeting07:32
*** e0ne has quit IRC07:36
*** salv-orl_ has quit IRC07:37
*** e0ne has joined #openstack-meeting07:40
*** pcaruana has joined #openstack-meeting07:41
*** e0ne has quit IRC07:43
*** nkrinner_afk is now known as nkrinner07:46
*** e0ne has joined #openstack-meeting07:47
*** lpetrut has quit IRC07:48
*** takashi has joined #openstack-meeting07:51
*** e0ne has quit IRC07:54
*** dmellado has joined #openstack-meeting07:57
*** e0ne has joined #openstack-meeting07:58
*** e0ne has quit IRC08:00
*** rcernin has joined #openstack-meeting08:03
*** e0ne has joined #openstack-meeting08:05
*** gongysh has joined #openstack-meeting08:05
*** ayogi has quit IRC08:06
*** e0ne has quit IRC08:10
*** e0ne has joined #openstack-meeting08:13
*** zhiyuan has joined #openstack-meeting08:16
*** brault has joined #openstack-meeting08:17
*** X-dark has quit IRC08:18
*** X-dark has joined #openstack-meeting08:22
*** e0ne has quit IRC08:25
*** qwebirc69708 has joined #openstack-meeting08:25
*** Wenzhi has quit IRC08:26
*** Wenzhi has joined #openstack-meeting08:27
*** acabot has joined #openstack-meeting08:28
*** worry_ has joined #openstack-meeting08:29
*** e0ne has joined #openstack-meeting08:29
*** e0ne has quit IRC08:31
*** jchhatbar_ is now known as janki08:34
*** salv-orlando has joined #openstack-meeting08:38
*** qwebirc69708 has quit IRC08:38
*** cartik has joined #openstack-meeting08:40
*** kashyap has joined #openstack-meeting08:40
*** salv-orlando has quit IRC08:42
*** dbecker has joined #openstack-meeting08:45
*** kaisers has joined #openstack-meeting08:46
*** ricolin has quit IRC08:49
*** david-lyle has joined #openstack-meeting08:57
*** yinwei_computer has joined #openstack-meeting08:57
*** chenying_ has joined #openstack-meeting08:59
*** fzdarsky has joined #openstack-meeting08:59
*** Wenzhi has quit IRC09:00
saggi#startmeeting karbor09:00
openstackMeeting started Tue Jan  3 09:00:39 2017 UTC and is due to finish in 60 minutes.  The chair is saggi. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: karbor)"09:00
openstackThe meeting name has been set to 'karbor'09:00
saggiHi everyone09:00
yinwei_computerhi09:00
yuvalHey :)09:00
edisonxianghello09:01
*** leon_wang has joined #openstack-meeting09:01
zhonghuahi09:01
saggiTalking to you all from Chengdu09:01
saggi!09:01
*** zengchen has joined #openstack-meeting09:01
saggi🎉09:01
leon_wanghi09:01
*** ayogi has joined #openstack-meeting09:01
chenying_hi09:01
zengchenhey!09:01
zhonghuasaggi: :)09:01
*** david-lyle has quit IRC09:01
*** Wenzhi has joined #openstack-meeting09:02
yinwei_computerI'm on remote site09:02
saggiI've been busy this week so I didn't have a lot of time to review09:02
saggiThere also doesn't seem to be anything on the docket09:02
saggi#topic bugfixing09:03
*** openstack changes topic to "bugfixing (Meeting topic: karbor)"09:03
saggiHow is this been going? Any progress?09:03
yuvalwe have some dashboard things open09:03
yuvalhttps://bugs.launchpad.net/bugs/164333109:03
openstackLaunchpad bug 1643331 in Karbor "karbor-dashboard: provider is being get for each checkpoint" [Low,Triaged]09:03
yuvalhttps://bugs.launchpad.net/bugs/162259409:03
openstackLaunchpad bug 1622594 in Karbor "Update checkpoint status in checkpoint page" [Medium,Triaged] - Assigned to chenying (ying-chen)09:03
yuvalhttps://bugs.launchpad.net/bugs/164333809:03
openstackLaunchpad bug 1643338 in Karbor "karbor-dashboard: Missing Plan edit - change resource and parameters" [High,Triaged]09:03
saggiOnly one is assigned09:04
yuvalalso, protection plugin adjustment are required and I think work on them has already began by chenying09:04
*** toscalix has joined #openstack-meeting09:04
chenying_yuval: Yes I will work on the glance protection plugin adjustment first.09:05
*** absubram has joined #openstack-meeting09:05
yuvalxiangxinyong here?09:05
edisonxiangyeah, I am here09:06
*** Wenzhi has quit IRC09:06
saggiedisonxiang: can you work on the remaining bugs?09:06
yuvaledisonxiang: :)09:06
saggi1643338 and 164333109:06
edisonxiangsure09:07
yinwei_computerI find one bug unassigned, which I think Luobin or I could fix it.09:07
yinwei_computerhttps://bugs.launchpad.net/karbor/+bug/155485109:07
openstackLaunchpad bug 1554851 in Karbor "Support pagination for protectables" [Low,Triaged]09:07
edisonxianghttps://launchpad.net/karbor/+milestone/ocata09:07
edisonxiangevery thing is here.09:07
chenying_https://bugs.launchpad.net/karbor/+bug/1554851  I have addressed the comment in this bug. Maybe we need think more about  pagination for protectables API.09:08
chenying_Not all the protectables plugins can support pagination feature.09:08
yinwei_computerchenying_, we could talk about the bug offline09:08
chenying_yinwei_computer: Ok09:08
yinwei_computergot your point, if plugins don't support list with anchor, there's no way to support pagination @chenying_09:10
*** jchhatbar has joined #openstack-meeting09:10
chenying_https://bugs.launchpad.net/karbor/+bug/1650239 This bug will be submitted base on chenzeng's client patch.09:10
openstackLaunchpad bug 1650239 in Karbor "Support clients with privileged user in karbor" [Undecided,New] - Assigned to chenying (ying-chen)09:10
chenying_yinwei_computer: Yes.09:10
zengchenI hope everyone can reivew my patch on the bug https://bugs.launchpad.net/karbor/+bug/156679309:10
openstackLaunchpad bug 1566793 in Karbor "authenticate in protection service client" [High,In progress] - Assigned to zengchen (chenzeng2)09:10
edisonxiang1643338 and 1643331 have already been assigned to me:)09:11
yuvalzengchen: which? I found two, but both are workflow -109:12
saggi😁09:12
*** janki has quit IRC09:12
zengchenyuval:you can see them listed in the comments at 'https://bugs.launchpad.net/karbor/+bug/1566793'. yes, 2 patches of them are workflow -1, but other ones are ready.09:14
openstackLaunchpad bug 1566793 in Karbor "authenticate in protection service client" [High,In progress] - Assigned to zengchen (chenzeng2)09:14
yuvalzengchen: will take a look09:14
zengchenyuval:like https://review.openstack.org/#/c/404644/. thank you.09:15
*** qwebirc62300 has joined #openstack-meeting09:15
*** jtomasek has quit IRC09:17
yuvalzengchen: https://review.openstack.org/#/c/407990/ is in merge conflict09:17
yuvalzengchen: so is https://review.openstack.org/#/c/408382/09:17
zengchenyuval:ok, I will update them.09:17
yinwei_computertwo patches on this bug? @zengchen09:17
zengchenyinwei_computer:there are 4.09:19
*** sacharya has joined #openstack-meeting09:19
zengchenyinwei_computer:you can review  https://review.openstack.org/#/c/404644/ first.09:20
yinwei_computerI see those 4 in launch pad.09:21
yinwei_computerthanks for fixing it!09:21
zengchenyinwei_compute:yes, if you have time, review them. thanks.09:22
saggiAnything important for me to go over?09:22
yuvalwe should starting closing the multi tenant isolation09:22
yinwei_computer@zengchen, I will09:23
yinwei_computeris there any bug I or Luobin could help on? @yuval @saggi09:23
*** sacharya has quit IRC09:23
saggiyuval: ^^09:24
*** tinwood has joined #openstack-meeting09:24
yuvalsaggi: I don't really recall where we were on the multi tenant issue09:24
yuvalsaggi: ¯\_(ツ)_/¯09:24
saggiWe have a spec up09:24
yuvalsaggi: will have to read the spec again09:24
chenying_yinwei_computer: You can see the bugs list in launchpad. Some of them are not marked 'Assigned'.09:25
yuvalಥ_ಥ09:25
saggiThe main objection is that it requires creating a lot of providers.09:25
saggiSince we can't figure out how to do templating09:25
saggiThe current solution can evolve to templated providers if we ever figure it out so it shouldn't block the spec.09:26
saggiIMHO09:26
yinwei_computermaybe we could have more details on how to map keystone users/groups to bank users/groups09:27
*** lpetrut has joined #openstack-meeting09:28
yinwei_computerin the spec09:28
*** links has quit IRC09:29
chenying_We also need think about the datbase bank use case .09:29
yinwei_computerwhat's your opinion on tenant isolation (cross site authentication), chenying_09:29
saggiThe spec purposefully ignores this since it's a policy issue. We don't know how the admin would decide to map those with providers. I could add an example.09:29
*** bobh has joined #openstack-meeting09:29
yinwei_computeryes, that'll be better09:30
saggiI'll add a comment09:31
saggiso I don't forget09:31
chenying_yinwei_computer: I have addressed some comments, I will review it again if it have been updated. My oppion is that we need think over about the cross-site use case first.09:31
edisonxianghttps://review.openstack.org/#/c/372846/ I saw this patch is submitted by leon_wang.09:32
chenying_saggi have updete the newest patch about it.09:33
saggiedisonxiang: I took over it09:33
*** gongysh has quit IRC09:33
*** lpetrut1 has joined #openstack-meeting09:33
edisonxiangsaggi: understood.09:33
*** lpetrut has quit IRC09:34
*** lpetrut1 is now known as lpetrut09:34
*** bobh has quit IRC09:34
*** Cibo_ has joined #openstack-meeting09:34
saggiI think we are done with bugs for today09:35
*** salv-orlando has joined #openstack-meeting09:35
saggi#topic Open Discussion09:36
*** openstack changes topic to "Open Discussion (Meeting topic: karbor)"09:36
saggiAnything else?09:36
*** Kevin_Zheng has quit IRC09:37
saggiOK09:38
saggiThanks everyone!09:38
saggi#endmeeting09:38
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"09:38
openstackMeeting ended Tue Jan  3 09:38:28 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:38
openstackMinutes:        http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-01-03-09.00.html09:38
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-01-03-09.00.txt09:38
openstackLog:            http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-01-03-09.00.log.html09:38
edisonxiang:) bye09:38
*** bobmel has joined #openstack-meeting09:39
*** edisonxiang has left #openstack-meeting09:41
*** takashi has quit IRC09:43
*** askb has quit IRC09:52
*** salv-orlando has quit IRC09:53
*** salv-orl_ has joined #openstack-meeting09:53
*** wanghao_ has joined #openstack-meeting09:54
*** julim has joined #openstack-meeting09:55
*** guoshan has quit IRC09:57
*** e0ne has joined #openstack-meeting09:57
*** guoshan has joined #openstack-meeting09:57
*** david-lyle has joined #openstack-meeting09:58
*** julim has quit IRC10:00
*** lhx__ has quit IRC10:00
*** david-lyle has quit IRC10:02
*** ljxiash has joined #openstack-meeting10:06
*** matrohon has joined #openstack-meeting10:07
*** ljxiash has quit IRC10:08
*** ljxiash has joined #openstack-meeting10:09
*** markvoelker has joined #openstack-meeting10:10
*** lhx__ has joined #openstack-meeting10:10
*** markvoelker has quit IRC10:15
*** kevinz has quit IRC10:15
*** Julien-zte has quit IRC10:17
*** Julien-zte has joined #openstack-meeting10:19
*** yangyape_ has quit IRC10:23
*** kashyap has left #openstack-meeting10:24
*** sambetts_ is now known as sambetts10:27
*** JoseMello has joined #openstack-meeting10:28
*** yamamoto has joined #openstack-meeting10:28
*** epico has quit IRC10:31
*** matrohon has quit IRC10:31
*** yamamoto has quit IRC10:32
*** guoshan has quit IRC10:34
*** spotz is now known as spotz_zzz10:39
*** ykatabam has quit IRC10:45
*** qwebirc62300 has quit IRC10:54
*** sudipto_ has quit IRC10:55
*** sudipto has quit IRC10:55
*** mickeys has quit IRC11:01
*** janki has joined #openstack-meeting11:02
*** jchhatbar has quit IRC11:02
*** jchhatbar has joined #openstack-meeting11:05
*** janki has quit IRC11:07
*** ayoung has joined #openstack-meeting11:10
*** bobmel has quit IRC11:10
*** jtomasek has joined #openstack-meeting11:11
*** markvoelker has joined #openstack-meeting11:11
*** markvoelker has quit IRC11:16
*** yamamoto has joined #openstack-meeting11:17
*** sacharya has joined #openstack-meeting11:20
*** Kiall has quit IRC11:24
*** sacharya has quit IRC11:24
*** prateek has quit IRC11:26
*** Kiall has joined #openstack-meeting11:27
*** bobmel has joined #openstack-meeting11:29
*** ntpttr has quit IRC11:30
*** bobh has joined #openstack-meeting11:31
*** guoshan has joined #openstack-meeting11:35
*** Kevin_Zheng has joined #openstack-meeting11:35
*** bobh has quit IRC11:36
*** sdague has joined #openstack-meeting11:38
*** ntpttr has joined #openstack-meeting11:39
*** gcb has quit IRC11:39
*** guoshan has quit IRC11:39
*** rfolco has joined #openstack-meeting11:40
*** yamamoto has quit IRC11:40
*** gcb has joined #openstack-meeting11:41
*** jchhatbar_ has joined #openstack-meeting11:58
*** david-lyle has joined #openstack-meeting11:59
*** sudipto has joined #openstack-meeting12:00
*** sudipto_ has joined #openstack-meeting12:00
*** jchhatbar has quit IRC12:00
*** yamamoto has joined #openstack-meeting12:01
*** mickeys has joined #openstack-meeting12:02
*** david-lyle has quit IRC12:04
*** nadya has joined #openstack-meeting12:04
*** mickeys has quit IRC12:06
*** zhiyuan has quit IRC12:06
*** rossella_s has joined #openstack-meeting12:06
*** yangyapeng has joined #openstack-meeting12:07
*** prateek has joined #openstack-meeting12:08
*** bobmel has quit IRC12:10
*** bobmel has joined #openstack-meeting12:11
*** cartik has quit IRC12:11
*** markvoelker has joined #openstack-meeting12:12
*** wanghao_ has quit IRC12:13
*** bkopilov has quit IRC12:13
*** rossella_s has quit IRC12:14
*** markvoelker has quit IRC12:16
*** zhiyuan has joined #openstack-meeting12:17
*** yamamoto has quit IRC12:19
*** gmann has quit IRC12:19
*** fdegir has quit IRC12:19
*** TheJulia has quit IRC12:19
*** samueldmq has quit IRC12:19
*** dpyzhov has quit IRC12:19
*** MarkAtwood has quit IRC12:19
*** arxcruz has quit IRC12:19
*** efried has quit IRC12:19
*** serverascode has quit IRC12:19
*** zz_dimtruck has quit IRC12:19
*** mkrai has quit IRC12:19
*** xgerman has quit IRC12:19
*** izaakk has quit IRC12:19
*** sweston has quit IRC12:19
*** dimtruckl has joined #openstack-meeting12:19
*** dimtruckl is now known as dimtruck12:19
*** arxcruz has joined #openstack-meeting12:19
*** efried has joined #openstack-meeting12:20
*** bvandenh has quit IRC12:20
*** mkrai has joined #openstack-meeting12:21
*** fdegir has joined #openstack-meeting12:21
*** izaakk has joined #openstack-meeting12:21
*** MarkAtwood has joined #openstack-meeting12:22
*** samueldmq has joined #openstack-meeting12:22
*** sweston has joined #openstack-meeting12:22
*** dpyzhov has joined #openstack-meeting12:23
*** xgerman has joined #openstack-meeting12:24
*** Julien-zte has quit IRC12:24
*** serverascode has joined #openstack-meeting12:24
*** TheJulia has joined #openstack-meeting12:25
*** gmann has joined #openstack-meeting12:25
*** zhiyuan has quit IRC12:29
*** bobh has joined #openstack-meeting12:32
*** salv-orl_ has quit IRC12:32
*** bobh has quit IRC12:36
*** matrohon has joined #openstack-meeting12:39
*** hwoarang_ is now known as hwoarang12:43
*** bobh has joined #openstack-meeting12:45
*** anilvenkata has quit IRC12:46
*** yamamoto has joined #openstack-meeting12:50
*** zhiyuan has joined #openstack-meeting12:50
*** yanyanhu has joined #openstack-meeting12:55
*** yamamoto has quit IRC12:56
*** wllabs has joined #openstack-meeting12:58
*** XueFeng has joined #openstack-meeting12:58
*** Ruijie_ has joined #openstack-meeting12:59
yanyanhu#startmeeting senlin13:00
openstackMeeting started Tue Jan  3 13:00:01 2017 UTC and is due to finish in 60 minutes.  The chair is yanyanhu. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: senlin)"13:00
openstackThe meeting name has been set to 'senlin'13:00
yanyanhuhello, everyone13:00
*** pradk has joined #openstack-meeting13:00
Ruijie_evening, yanyanhu :)13:01
yanyanhuhi, Ruijie_13:01
yanyanhulets wait for while for other attenders13:01
XueFenghi, yanyan,ruijie13:01
yanyanhuhi, XueFeng13:01
XueFenggood evneing13:02
Qiminghi13:02
*** prateek_ has joined #openstack-meeting13:02
yanyanhuhi, Qiming13:02
*** mickeys has joined #openstack-meeting13:02
yanyanhuhere is the agenda, please feel free to add topics https://wiki.openstack.org/wiki/Meetings/SenlinAgenda#Agenda_.282017-01-03_1300_UTC.2913:02
yanyanhuok, lets get started13:03
yanyanhu#topic ocata workitem13:03
*** openstack changes topic to "ocata workitem (Meeting topic: senlin)"13:03
yanyanhuhttps://etherpad.openstack.org/p/senlin-ocata-workitems13:03
yanyanhulets get through the list first13:03
yanyanhuenhance tempest API test13:03
*** lxinhui has joined #openstack-meeting13:04
yanyanhufor our versioned request support has been done, this item can be started13:04
yanyanhualthough with low priority maybe13:04
*** sdake has joined #openstack-meeting13:04
yanyanhuplease feel free to claim and work on it13:04
yanyanhunext one13:04
*** prateek has quit IRC13:04
yanyanhuhealth management13:05
yanyanhuhi, lxinhui13:05
lxinhuihi13:05
yanyanhuthere has been some dicussion on the spec13:05
lxinhuiYes13:05
yanyanhuabout mistral workflow for HA13:05
lxinhuihttps://review.openstack.org/41497913:05
*** elynn has joined #openstack-meeting13:06
lxinhuiIn the past week, there are many discussion there.13:06
lxinhuiI think finally the chained recover actions design are the best13:06
*** mickeys has quit IRC13:07
lxinhuiif my understanding is right, we need to implment do-worklfow in profile13:07
yanyanhuYes, and I think Qiming gave a great suggestion that we can use workflow to manage the entire recovery progress and also use it perform operation before/after node recovery13:07
lxinhuithen pre-op, post-op, and the action can call the workflow channel13:07
yanyanhujust I'm also not sure where is the best place to implement do_workflow logic13:08
yanyanhulxinhui, yes13:08
lxinhuiwhere do you suggest?13:08
lxinhuiyanyanhu13:08
yanyanhuwell, I thought health manager is the better place13:08
lxinhuihow?13:08
yanyanhubut after more thinking, I feel profile could be better now13:09
lxinhuidirectly call workflow?13:09
yanyanhulxinhui, if so, yes13:09
lxinhuias a parallel option of cluster recover?13:09
yanyanhujust I'm now feeling health manager should be a module to hold more generic logic13:09
yanyanhubut mistral workflow is openstack-specific conception13:09
yanyanhu(at least for mistral workflow)13:10
lxinhuithat is kind of hack for me13:10
Qimingthe current operation sequence is like this13:10
lxinhuiI look at the health manager like a extention of senlin engine service13:11
Qiming1. user request an explict cluster recover operaiton13:11
lxinhuibut the action and policy as plugin framework13:11
Qiming2. a cluster recover operation triggered by the detection logic13:11
Qimingin both cases, we are initiating a CLUSTER_RECOVER action, which is subject to check by the health poliy13:11
Qimingif there is no health policy attached, the default behavior would be recreate13:12
Qimingin health policy, we are trying to tune that action to be executed13:12
*** markvoelker has joined #openstack-meeting13:12
Qimingonce that action, e.g. REBUILD, REBOOT, "RUN A WORKFLOW" is determined by the policy13:13
yanyanhuQiming, yes. If the mistral workflow is operated before/after recovery action, obviously implementing it in health policy will be the choice13:13
yanyanhujust like what we are doing for lb policy I think13:13
Qimingthe CLUSTER_RECOVER action will call the base profile to do the job13:13
yanyanhubut if we use mistral workflow to drive the entire recovery progress, the situation becomes a little complicated...13:14
lxinhuiit is not only for aspect calling now13:14
Qimingmaybe we can trigger all recovery actions there13:14
lxinhuiyanyanhu, workflow is one option, even one step of whole recover process13:15
yanyanhuQiming, all recovery actions? you mean node rebuild/reboot and also workflow operations?13:15
lxinhuimistral is not the driver but senlin does13:16
yanyanhulxinhui, yes, just we need to consider where to implement the workflow exection logic13:16
Qimingyanyanhu, yes13:16
lxinhuithat is question I proposed :)13:17
yanyanhuI see. if so, profile should be the place to hold it?13:17
yanyanhulike do_recovery13:17
*** Wenzhi has joined #openstack-meeting13:17
Qimingonly the base profile13:17
*** Wenzhi has quit IRC13:17
Qimingit is dirty ...13:17
yanyanhuyes13:17
yanyanhuthat is13:17
*** markvoelker has quit IRC13:17
*** toscalix has quit IRC13:17
Qimingor another option is we parse the list of actions user specified in the policy spec13:18
yanyanhuI also feel only implementing it in base profile can help to avoid code duplication.13:18
Qimingif it is a workflow, we invoke it directly, as another action13:18
lxinhuiwhat code duplication?13:18
lxinhuisomething I mist here13:18
Qimingif it is a builtin action or profile operation, we return that in action.data13:18
*** dprince has joined #openstack-meeting13:18
lxinhuiduplicate with what?13:18
yanyanhuQiming, invoke it directly in health manager?13:18
*** nmagnezi has left #openstack-meeting13:18
Qiminghealth manager is only for the health detection side13:19
Qimingit is not a "manager"13:19
lxinhuiyes, yanyanhu13:19
*** jaypipes has joined #openstack-meeting13:19
lxinhuiit is not the right place13:19
yanyanhulxinhui, I mean if the workflow execution logic(do_workflow maybe) is not implemented in profile base, you may need to add do_workflow method for every profile type who needs this logic13:19
QimingThere are possibilities that users explicitly request a cluster to be recovered13:19
Qimingthus the action sequence is not triggered from the health manager13:20
yanyanhuQiming, I see13:20
*** toscalix has joined #openstack-meeting13:20
*** baoli has joined #openstack-meeting13:20
yanyanhuso that will be part of recovery action13:20
*** GordonTX has joined #openstack-meeting13:20
yanyanhuso workflow exection logic will be part of do_recovery action impelementation13:20
lxinhuii think so13:20
*** sacharya has joined #openstack-meeting13:20
Qimingyup, in current design, workflow is only used for recovery's purpose13:20
*** GordonTX has quit IRC13:20
*** baoli has quit IRC13:21
yanyanhuI see13:21
lxinhuiwe use use type to switch to workflow13:21
lxinhuis/use/can/g13:21
Qimingconsidering that we will have to support a list of actions (with and without workflow as action types), placing the iteration logic in base profile sounds fine to me13:22
*** baoli has joined #openstack-meeting13:22
*** bobh has quit IRC13:22
Qimingthe parameter passing logic is there, just ... we don't have the code to parse and execute more than one action13:23
Qiminghttp://git.openstack.org/cgit/openstack/senlin/tree/senlin/engine/actions/cluster_action.py#n65713:23
yanyanhuQiming, yes, action is the atomic operation for us13:23
*** lhx__ has quit IRC13:23
yanyanhuso combination of actions should be done at higher level, e.g. API or rpc13:24
Qimingline 658 is only extracting the first action for execution13:24
lxinhuiyes13:24
lxinhuiAnd no one review the SDK patch...13:24
lxinhuithe api twist patch of mistral has been merged13:25
*** sacharya has quit IRC13:25
yanyanhulxinhui, good news :)13:25
Qiminganother place is here: http://git.openstack.org/cgit/openstack/senlin/tree/senlin/engine/node.py#n36813:25
lxinhuihttps://review.openstack.org/#/c/414919/313:26
*** GordonTX has joined #openstack-meeting13:26
Qiminglxinhui, it is not done13:26
Qimingthat patch still has tons of problems13:26
lxinhuiplease review13:26
yanyanhujust I still free that workflow is not a generic conception...13:27
Qimingwill do13:27
yanyanhudoesn't like other logic we defined in cluster action module13:27
yanyanhuor in node module13:27
*** toscalix has quit IRC13:28
*** toscalix has joined #openstack-meeting13:28
*** toscalix has quit IRC13:28
*** toscalix_ has joined #openstack-meeting13:28
*** salv-orlando has joined #openstack-meeting13:28
Qiminglxinhui, you missed '_query_mapping' in those classes, the current code only support create, but allow_get is already there, 'include_output' is only a query parameter, ...13:28
lxinhuilet us finish it little by little13:29
Qimingokay13:29
Qimingyanyanhu, you can think of it as creating a ceilometer alarm13:29
lxinhuineed read more code of sdk13:29
*** thorst has joined #openstack-meeting13:30
yanyanhuQiming, yes13:30
yanyanhubut we usually support those service specific operations in plugins13:31
yanyanhuI feel13:31
*** lamt has joined #openstack-meeting13:31
yanyanhunot in generic modules, like node, cluster, or action modules13:31
Qimingyes, we will add drivers for workflow13:31
lxinhuiyanyanhu, seems you like AOP more than workflow13:31
yanyanhuQiming, yes, I mean maybe we need to wrap and abstract mistral workflow?13:32
Qimingwe can invoke workflow APIs from the health policy13:32
yanyanhulxinhui, AOP is?13:32
lxinhuijust joke13:32
yanyanhu:)13:32
lxinhuiQiming mentioned the concept in his mind last time :)13:32
yanyanhuQiming, yes, that makes more sense to me13:32
Qimingthe problem is that it will be difficult to build dependencies if some actions are triggered in policy, others are in profiles13:33
yanyanhuQiming, right, that is a headache13:33
yanyanhutill now, we either talk to backend service during action execution, or before/after action progress13:34
yanyanhubut not at the same time13:34
Qimingright13:34
Qimingso I'm thinking if this is the proper location to iterate all the action items and execute them one by one13:35
Qiminghttp://git.openstack.org/cgit/openstack/senlin/tree/senlin/engine/node.py#n36813:35
yanyanhuyou mean here? http://git.openstack.org/cgit/openstack/senlin/tree/senlin/engine/node.py#n38013:36
Qimingyes13:36
*** eharney has joined #openstack-meeting13:36
yanyanhuso it will fall into profile13:36
Qimingthat is only capable of doing some builtin operations13:36
Qimingnot workflows13:36
Ruijie_this feature also fit heat stacks?13:36
Qimingyes, Ruijie_13:36
yanyanhuQiming, yes13:36
*** Kevin_Zheng has quit IRC13:37
*** jchhatbar has joined #openstack-meeting13:37
*** salv-orlando has quit IRC13:37
yanyanhuRuijie_, yes, also dockers13:37
Qimingwe provide knives13:37
yanyanhuwe hope so :)13:37
Qimingyou decide how to use it13:37
lxinhuiyes, I think so depspite little mess is heat can call mistral too13:37
Qimingkill people or cook meal13:37
*** jchhatbar_ has quit IRC13:37
yanyanhuyep, that is the logic13:37
*** jchhatbar has quit IRC13:37
*** janki has joined #openstack-meeting13:38
yanyanhuso maybe we start from node.py13:38
lxinhuiagain, alike ceilometer...13:38
Qimingwe won't be responsible for debugging the workflows13:38
lxinhuisure13:38
Qiminguses decide how to write workflows to operate a specific nova server, heat stack, ... etc.13:39
lxinhuiprecondition is that users have their own trusted workflow13:39
yanyanhuyes, we just help to trigger it according to the rule user defines13:39
yanyanhuin the right place at the right time13:39
lxinhuimean people :)13:40
yanyanhu:P13:40
*** salv-orlando has joined #openstack-meeting13:40
Qimingthere are possibilities users trigger a workflow on a stack which was meant to be used on VM13:41
Qimingbut that possibility is small13:41
*** sdake has quit IRC13:41
Qimingyou won't use the same health policy on clusters of different types of entities13:41
Qimingat least I will call that stupid13:41
*** eharney has quit IRC13:41
yanyanhuyes13:41
yanyanhuso lxinhui, maybe you can finish the spec based on this discussion13:42
yanyanhuand we can talk more about the implementation detail later13:42
Qimingjust like you want to delete a cinder volume using 'nova delete', ... it won't work, for sure13:42
yanyanhu:)13:42
Qimingyes13:42
Qiminglet's move on13:42
yanyanhuok, lets move on13:43
yanyanhusenlinclient test13:43
yanyanhuhi, XueFeng, you're working on it now?13:43
*** janzian has joined #openstack-meeting13:43
Qimingdon't think so ... need a starting point I think13:43
yanyanhuI see13:44
Qimingone simple test, plust gate setup13:44
yanyanhuyes13:44
Qimingthen people can share the jobs adding test cases13:44
yanyanhuthat will be the basement13:44
yanyanhuok, will check this work later13:44
Qimingbasement is floor -113:44
yanyanhuhaha, yes13:44
Qiming:D13:44
yanyanhuok, next one13:45
yanyanhurenaming service calls13:45
yanyanhusaw lots of patches for it last week13:45
yanyanhuI think it hasn't been done yet?13:45
yanyanhudidn't check the code...13:45
yanyanhubut anyway, not very difficult work13:45
yanyanhuok, next one13:45
yanyanhucontainer profile13:46
yanyanhuhaiwei is not here I think?13:46
yanyanhuand those two patches have been merged13:46
yanyanhuwill remove them from the etherpad13:46
Qimingit's almost done I think13:46
QimingOMG, it is done13:46
yanyanhuyes, it is done13:46
Qimingcall2, reqquest_context2 all removed ...13:46
yanyanhuhave removed them :)13:46
Qimingamazing13:46
yanyanhucool13:47
*** ttx has quit IRC13:47
*** ataraday has quit IRC13:47
*** Swanson has quit IRC13:47
*** amrith has quit IRC13:47
*** dulek has quit IRC13:47
*** egon has quit IRC13:47
*** mestery has quit IRC13:47
yanyanhuyes, the configure option has also been removed13:47
yanyanhu:)13:47
*** X-dark_ has joined #openstack-meeting13:47
yanyanhuso we have finished the switching13:47
*** amrith has joined #openstack-meeting13:47
*** egon has joined #openstack-meeting13:47
*** X-dark has quit IRC13:47
*** X-dark_ is now known as X-dark13:47
*** scottda has quit IRC13:47
*** ildikov has quit IRC13:47
*** aimeeu has quit IRC13:47
*** ataraday has joined #openstack-meeting13:47
*** Swanson has joined #openstack-meeting13:47
XueFenghi, come back13:47
*** huanxuan has quit IRC13:47
yanyanhuso that's all in the list13:47
yanyanhuhi, XueFeng13:47
*** ttx has joined #openstack-meeting13:48
XueFengabout client test13:48
yanyanhuwe just talked about the test job for client13:48
*** irenab has quit IRC13:48
*** irenab has joined #openstack-meeting13:48
yanyanhumaybe a simple test case plus gate job setting up will be a good startpoint13:48
XueFengWill ping you tomorrow13:48
*** mestery has joined #openstack-meeting13:49
*** armax has joined #openstack-meeting13:49
yanyanhuthen more people can jump into it :)13:49
yanyanhuXueFeng, sure, thanks a lot :)13:49
*** dulek has joined #openstack-meeting13:49
yanyanhuok, next topic13:49
yanyanhu#topic Adopt existing VM for scaling13:49
*** openstack changes topic to "Adopt existing VM for scaling (Meeting topic: senlin)"13:49
yanyanhuhttps://etherpad.openstack.org/p/%E5%BC%B9%E6%80%A7%E4%BC%B8%E7%BC%A9%E7%BB%84%E6%94%AF%E6%8C%81%E6%B7%BB%E5%8A%A0%E4%BA%91%E4%B8%BB%E6%9C%BA13:49
yanyanhuWOW...13:49
*** elynn has quit IRC13:50
yanyanhuhere is a etherpad created by eldon from cmcc13:50
yanyanhuabout adopting exiting vm(s) for scaling13:50
*** ildikov has joined #openstack-meeting13:50
yanyanhuplease feel free to leave your comments if you're interest about this topic :)13:50
*** elynn has joined #openstack-meeting13:50
yanyanhumay need an english version for it...13:51
Ruijie_called "add an exiting node to cluster", I guess13:51
yanyanhuany question about it?13:51
Qimingjust adoption would be okay13:52
Ruijie_will this combined with another workflow13:52
Qimingit may and may not be related to scaling13:52
Ruijie_copy an vm's spec and use it to create VMs13:52
yanyanhuyes, adoption can be individual from scaling13:52
*** lhx__ has joined #openstack-meeting13:52
yanyanhus/can be/is13:52
yanyanhuorthogonal13:53
yanyanhuI learn this word from Qiming, haha13:53
yanyanhuso guys, please read it and share your ideas13:53
yanyanhuso lets move on?13:54
yanyanhu5 minutes left13:54
yanyanhu#topic meetup13:54
*** openstack changes topic to "meetup (Meeting topic: senlin)"13:54
*** scottda has joined #openstack-meeting13:54
*** tommylik_ has joined #openstack-meeting13:54
*** aimeeu has joined #openstack-meeting13:54
yanyanhuso here is the question. Who you guys can join it if we hold a meetup in Beijing :)13:54
* Ruijie_ :)13:55
elynnI can ;)13:55
yanyanhuor you will join it, you know the haze :P13:55
*** tommylik_ has quit IRC13:55
yanyanhuelynn, me too :)13:55
*** eharney has joined #openstack-meeting13:55
Qimingcool, someone volunteered to pay the bill, \o/13:55
*** tommylik_ has joined #openstack-meeting13:55
yanyanhuso just want to listen to your idea, especially who are now based on Beijing13:55
*** ajo has quit IRC13:55
yanyanhuQiming, haha13:55
*** liusheng has quit IRC13:55
*** tommylikehu_ has quit IRC13:56
*** tommylik_ has quit IRC13:56
*** liusheng has joined #openstack-meeting13:56
*** korzen has quit IRC13:56
*** tommylikehu_ has joined #openstack-meeting13:56
*** tonytan4ever has joined #openstack-meeting13:56
yanyanhuthat will decide the size of our meetup13:56
*** ajo has joined #openstack-meeting13:56
XueFengIn BeiJing?When?13:56
*** tommylikehu_ has left #openstack-meeting13:56
yanyanhuXueFeng, should before china spring festival13:57
elynnfree coffee serving :)13:57
yanyanhubut haven't decided yet13:57
XueFengOK.13:57
yanyanhuelynn, that's good enough :)13:57
yanyanhuXueFeng, where are you working at now?13:57
yanyanhunot in Beijing?13:57
*** trevormc has joined #openstack-meeting13:58
yanyanhusince if not, there will be travel fee need to cover :)13:58
XueFengNanJing,haha13:58
*** bkopilov has joined #openstack-meeting13:58
yanyanhunot far :)13:58
yanyanhuok, maybe we can talk about this offline before you guys make decision13:58
lxinhuiNanjing is a good place :)13:58
yanyanhujust want to remind we have the plan to hold it13:58
elynnlxinhui, agree13:58
elynn:D13:59
yanyanhuI will ask you guys tomorrow in senlin channel13:59
yanyanhuand lets decide it together13:59
lxinhui:)13:59
yanyanhugreat13:59
XueFengWill apply for this tommorrow13:59
XueFengMaybe it's ok.13:59
yanyanhumeetup and talk are always pleased13:59
yanyanhupleasing13:59
yanyanhuXueFeng, cool14:00
yanyanhuok, time is over14:00
yanyanhuthanks all you guys for joining14:00
yanyanhuhave a good night14:00
yanyanhuttyl14:00
yanyanhu#endmeeting14:00
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"14:00
openstackMeeting ended Tue Jan  3 14:00:25 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-01-03-13.00.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-01-03-13.00.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-01-03-13.00.log.html14:00
*** david-lyle has joined #openstack-meeting14:01
*** lxinhui has quit IRC14:01
*** zul has quit IRC14:01
*** weshay is now known as weshay_afk14:01
*** elynn has quit IRC14:02
*** yanyanhu has quit IRC14:02
*** XueFeng has quit IRC14:02
*** mickeys has joined #openstack-meeting14:03
*** julim has joined #openstack-meeting14:03
*** julim has quit IRC14:03
*** bzhao_ has joined #openstack-meeting14:03
*** haleyb has joined #openstack-meeting14:03
*** trevormc has left #openstack-meeting14:04
*** david-lyle has quit IRC14:05
*** zul has joined #openstack-meeting14:07
*** julim has joined #openstack-meeting14:08
*** huanxuan has joined #openstack-meeting14:08
*** mickeys has quit IRC14:08
*** cartik has joined #openstack-meeting14:08
*** Ruijie_ has quit IRC14:09
*** myoung has joined #openstack-meeting14:10
*** noslzzp has joined #openstack-meeting14:10
*** noslzzp has quit IRC14:10
*** noslzzp has joined #openstack-meeting14:11
*** wllabs_ has joined #openstack-meeting14:11
*** julim has quit IRC14:11
*** julim has joined #openstack-meeting14:12
*** wllabs_ has quit IRC14:12
*** markvoelker has joined #openstack-meeting14:13
*** wllabs_ has joined #openstack-meeting14:14
*** myoung has quit IRC14:14
*** myoung has joined #openstack-meeting14:15
*** wllabs has quit IRC14:15
*** wllabs_ is now known as wllabs14:15
*** bvandenh has joined #openstack-meeting14:16
*** fguillot has joined #openstack-meeting14:18
*** markvoelker has quit IRC14:18
*** kylek3h has joined #openstack-meeting14:18
*** trozet has joined #openstack-meeting14:20
*** lhx__ has quit IRC14:21
*** myoung has quit IRC14:22
*** myoung has joined #openstack-meeting14:22
*** janzian has left #openstack-meeting14:22
*** lblanchard has joined #openstack-meeting14:25
*** ayogi has quit IRC14:27
*** jgregor has joined #openstack-meeting14:27
*** cdelatte has joined #openstack-meeting14:28
*** jgregor_ has joined #openstack-meeting14:29
*** nadya has quit IRC14:32
*** jgregor has quit IRC14:32
*** VW has joined #openstack-meeting14:35
*** anilvenkata has joined #openstack-meeting14:36
*** VW has quit IRC14:37
*** markvoelker has joined #openstack-meeting14:38
*** claudiub has joined #openstack-meeting14:39
*** galstrom_zzz is now known as galstrom14:40
*** oomichi has quit IRC14:42
*** absubram has quit IRC14:43
*** oomichi has joined #openstack-meeting14:43
*** julian1 has quit IRC14:44
*** siva_krishnan has quit IRC14:44
*** jungleboyj has joined #openstack-meeting14:45
*** julian1 has joined #openstack-meeting14:45
*** salv-orlando has quit IRC14:45
*** jgregor_ has quit IRC14:45
*** masayukig has quit IRC14:48
*** masayukig_ has joined #openstack-meeting14:48
*** galstrom is now known as galstrom_zzz14:50
*** weshay_afk is now known as weshay14:50
*** lhx_ has joined #openstack-meeting14:51
*** mriedem has joined #openstack-meeting14:51
*** irenab has quit IRC14:52
*** irenab has joined #openstack-meeting14:52
*** jamesden_ has joined #openstack-meeting14:53
*** cleong has joined #openstack-meeting14:54
*** spzala has joined #openstack-meeting14:59
*** Julien-zte has joined #openstack-meeting14:59
*** cartik has quit IRC14:59
*** kevinz has joined #openstack-meeting15:00
*** bobh has joined #openstack-meeting15:01
*** david-lyle has joined #openstack-meeting15:01
*** hongbin has joined #openstack-meeting15:03
*** cdub has joined #openstack-meeting15:03
*** ociuhandu has quit IRC15:03
*** mickeys has joined #openstack-meeting15:04
*** yuval has quit IRC15:05
*** edtubill has joined #openstack-meeting15:06
*** david-lyle has quit IRC15:06
*** rbak has joined #openstack-meeting15:07
*** kevinz has quit IRC15:08
*** mickeys has quit IRC15:09
*** lhx_ has quit IRC15:13
*** spotz_zzz is now known as spotz15:14
*** cody-somerville has joined #openstack-meeting15:14
*** cody-somerville has quit IRC15:14
*** cody-somerville has joined #openstack-meeting15:14
*** sacharya has joined #openstack-meeting15:21
*** sudipto_ has quit IRC15:24
*** sudipto has quit IRC15:25
*** sudipto_ has joined #openstack-meeting15:25
*** sudipto has joined #openstack-meeting15:25
*** sacharya has quit IRC15:26
*** jaugustine has joined #openstack-meeting15:27
*** med_` is now known as medberry15:28
*** medberry is now known as med_15:28
*** med_ is now known as Guest4623215:29
*** Guest46232 is now known as medberry15:29
*** medberry has joined #openstack-meeting15:29
*** lhx_ has joined #openstack-meeting15:32
*** absubram has joined #openstack-meeting15:37
*** dtrainor has joined #openstack-meeting15:37
*** rbudden has joined #openstack-meeting15:39
*** rbowen has joined #openstack-meeting15:40
*** rbowen has left #openstack-meeting15:40
*** sdake has joined #openstack-meeting15:45
*** salv-orlando has joined #openstack-meeting15:46
*** TxGirlGeek has joined #openstack-meeting15:49
*** edtubill has quit IRC15:49
*** galstrom_zzz is now known as galstrom15:50
*** bvandenh has quit IRC15:50
*** prateek_ has quit IRC15:51
*** salv-orlando has quit IRC15:51
*** saisrikiran has joined #openstack-meeting15:51
*** bdperkin has quit IRC15:51
*** spotz_zzz has joined #openstack-meeting15:52
*** hieulq_ has joined #openstack-meeting15:54
*** edtubill has joined #openstack-meeting15:54
*** kristian__ has joined #openstack-meeting15:54
*** strigazi_ is now known as strigazi_AFK15:54
*** yangyapeng has quit IRC15:55
*** rbak has quit IRC15:55
*** yangyapeng has joined #openstack-meeting15:58
*** nklenke has joined #openstack-meeting15:59
*** Leom has joined #openstack-meeting15:59
*** jaugustine has quit IRC16:00
*** edtubill has quit IRC16:00
*** rbak has joined #openstack-meeting16:00
*** richm has joined #openstack-meeting16:01
*** richm has left #openstack-meeting16:01
*** lhx_ has quit IRC16:01
*** d0ugal has joined #openstack-meeting16:03
*** yangyapeng has quit IRC16:03
*** chenying_ has quit IRC16:03
*** bzhao has quit IRC16:04
*** sridharg has quit IRC16:04
*** caboucha has joined #openstack-meeting16:04
*** liusheng has quit IRC16:05
*** masayukig_ is now known as masayukig16:07
*** huanxuan has quit IRC16:07
*** masayukig is now known as masayukig_16:07
*** masayukig_ is now known as masayukig16:08
*** korzen has joined #openstack-meeting16:08
*** nadya has joined #openstack-meeting16:11
*** alex_xu has quit IRC16:11
*** chenying has joined #openstack-meeting16:11
*** janki has quit IRC16:17
*** janki has joined #openstack-meeting16:19
*** saisrikiran has quit IRC16:19
*** lamt has quit IRC16:20
*** jaugustine has joined #openstack-meeting16:20
*** lamt has joined #openstack-meeting16:21
*** alex_xu has joined #openstack-meeting16:22
*** edtubill has joined #openstack-meeting16:23
*** fnaval has joined #openstack-meeting16:24
*** rcernin has quit IRC16:25
*** ltomasbo has joined #openstack-meeting16:26
*** sudipto has quit IRC16:27
*** sudipto_ has quit IRC16:27
*** dmellado_ has joined #openstack-meeting16:28
*** janki has quit IRC16:30
*** baoli has quit IRC16:31
*** tesseract has quit IRC16:31
*** saisrikiran has joined #openstack-meeting16:39
*** geguileo has joined #openstack-meeting16:41
*** e0ne has quit IRC16:45
*** Julien-zte has quit IRC16:45
*** GordonTX has quit IRC16:46
*** GordonTX has joined #openstack-meeting16:46
*** Julien-zte has joined #openstack-meeting16:47
*** Julien-zte has quit IRC16:47
*** rbak has quit IRC16:47
*** Julien-zte has joined #openstack-meeting16:48
*** Julien-zte has quit IRC16:49
*** rbak has joined #openstack-meeting16:50
*** Julien-zte has joined #openstack-meeting16:50
*** Julien-zte has quit IRC16:50
*** GordonTX has quit IRC16:51
*** korzen has quit IRC16:53
*** dmellado has quit IRC16:53
*** zara_the_lemur__ has joined #openstack-meeting16:55
*** sdake has quit IRC16:57
*** yangyapeng has joined #openstack-meeting17:00
*** nkrinner is now known as nkrinner_afk17:00
*** lpetrut has quit IRC17:00
*** cartik has joined #openstack-meeting17:01
*** nadya has quit IRC17:02
*** david-lyle has joined #openstack-meeting17:03
*** kjorgensen has joined #openstack-meeting17:04
*** yangyapeng has quit IRC17:05
*** matrohon has quit IRC17:07
*** david-lyle has quit IRC17:08
*** medberry is now known as med_17:14
*** matrohon has joined #openstack-meeting17:15
*** rbak has quit IRC17:17
*** rbak has joined #openstack-meeting17:18
*** anilvenkata has quit IRC17:23
*** yamahata has joined #openstack-meeting17:24
*** lpetrut has joined #openstack-meeting17:26
*** yamahata has quit IRC17:27
*** yamahata has joined #openstack-meeting17:28
*** rwsu has joined #openstack-meeting17:30
*** baoli has joined #openstack-meeting17:31
*** jaugustine has quit IRC17:31
*** bobh has quit IRC17:32
*** yangyapeng has joined #openstack-meeting17:32
*** thorst is now known as thorst_afk17:35
*** yangyapeng has quit IRC17:37
*** masayukig is now known as masayukig_17:37
*** masayukig_ is now known as masayukig17:37
*** sshnaidm is now known as sshnaidm|afk17:37
*** masayukig is now known as masayukig_17:38
*** sambetts is now known as sambetts|afk17:38
*** masayukig_ is now known as masayukig17:38
*** toscalix_ is now known as toscalix17:39
*** csomerville has joined #openstack-meeting17:43
*** kristian__ has quit IRC17:43
*** cody-somerville has quit IRC17:46
*** saisrikiran has quit IRC17:46
*** egallen has quit IRC17:47
*** thorst_afk is now known as thorst17:51
*** kristian__ has joined #openstack-meeting17:55
*** pcaruana has quit IRC17:58
*** jaugustine has joined #openstack-meeting17:58
*** abalutoiu has joined #openstack-meeting17:59
*** kristian__ has quit IRC17:59
stevemarping agrebennikov, amakarov, annakoppad, ayoung, bknudson, breton, browne, chrisplo, crinkle, davechen, dolphm, dstanek, edmondsw, edtubill, gagehugo, gyee, henrynash, hrybacki, jamielennox, jaugustine, jgrassler, knikolla, lbragstad, kbaikov, ktychkova, morgan, nisha, nkinder, notmorgan, raildo, ravelar, rderose, rodrigods, roxanaghe, samueldmq, shaleh, spilla, srwilkers, StefanPaetowJisc, stevemar, topol18:00
*** gagehugo has joined #openstack-meeting18:00
rodrigodshi18:00
rodrigodsfirst 2017 meeting18:00
stevemaro/18:00
ayoungHeyo18:00
hrybackio/18:00
stevemar#startmeeting keystone18:00
openstackMeeting started Tue Jan  3 18:00:46 2017 UTC and is due to finish in 60 minutes.  The chair is stevemar. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: keystone)"18:00
gagehugoo/18:00
openstackThe meeting name has been set to 'keystone'18:00
jaugustineHappy 201718:00
lamto/18:00
lbragstado/18:00
dstaneko/18:00
gagehugoHappy New Year!18:01
stevemarhappy new year all :)18:01
*** rbak has quit IRC18:01
morgano/18:01
* morgan yawns and needs coffee18:01
samueldmqhi o/18:01
stevemarlooks like we have enough people to start :)18:02
morganstevemar: hah.18:02
stevemarhopefully everyone is well rested and fully recharged !18:02
morganrested? nope, i could use another 2-3 weeks off :P18:02
gagehugo^18:02
lbragstadmorgan :)18:02
bretonit is still holidays in russia18:03
bretonfor the next week18:03
dstanekmorgan: ++18:03
stevemarno one went overboard on doing things over the holidays, so thanks for that18:03
stevemarbreton: thanks for the heads up, enjoy the time off :)18:03
stevemar#topic announcements18:03
*** openstack changes topic to "announcements (Meeting topic: keystone)"18:03
stevemartime to Register for PTG !18:03
stevemar#link https://www.eventbrite.com/e/project-teams-gathering-tickets-2754929869418:03
bretonstevemar: meh, time off is for the weak :p18:03
*** david-lyle has joined #openstack-meeting18:03
ayoungthought that went up months ago?18:04
stevemarbreton: your tune will change eventually :)18:04
*** julim_ has joined #openstack-meeting18:04
stevemarayoung: hmm?18:04
*** bzhao_ has quit IRC18:04
samueldmq186 tickets lef18:04
samueldmqleft18:04
stevemarlooks like 186 left18:04
stevemarthis is essentially replacing the midcycle18:04
lbragstadfwiw - there is a refund process I believe18:04
bretonthat's a lot18:04
lbragstadso if you do register, and can't make it you can get your money back18:05
*** julim has quit IRC18:05
gagehugoyou can transfer tickets too I believe18:05
samueldmqlbragstad: refund process for the PTG ticktes ?18:05
samueldmqtickets*18:05
lbragstadsamueldmq yes18:05
bretonyes, PTG tickets are refundable18:05
stevemari put my travel request in for work, as soon as it's approved i'm buying18:05
samueldmqoh that's nice18:05
stevemarthere should be an operator or two there, mfisch i think18:06
*** AJaeger has joined #openstack-meeting18:06
*** cartik has quit IRC18:06
morgani already got my ticket.18:06
morgani need to do the hotel thing though18:06
stevemarthere are a few other hotels around, but try to book at the conference hotel18:06
gagehugomorgan: same18:07
gagehugonot sure what hotels are going to be18:07
morgangagehugo: annnnnd airfare.. but that can wait :P18:07
gagehugoyup18:07
stevemarhotel booking through foundation discounted price: https://www.starwoodmeeting.com/events/start.action?id=1609140999&key=381BF4AA18:07
morganoooh starwood.18:08
stevemaralright, next sub topic18:08
stevemar#topic What question should we ask our users in the next user survey18:08
*** openstack changes topic to "What question should we ask our users in the next user survey (Meeting topic: keystone)"18:08
stevemar#link http://lists.openstack.org/pipermail/openstack-dev/2016-December/109500.html18:08
*** david-lyle has quit IRC18:08
*** claudiub|2 has joined #openstack-meeting18:09
stevemarany ideas on this? I think last time i asked about what kind of user store is used, sql / ldap / federation / mix18:09
morgansomething something distributed18:09
morganmulti-az18:09
*** cartik has joined #openstack-meeting18:09
*** browne has joined #openstack-meeting18:09
morgantry and hammer down the story for that.18:09
ayoungWhat federation protocols do they need support for?18:09
lbragstadayoung ++18:09
stevemarwe only get 1 question unfortunately18:09
lbragstadthat might give us some direction on the work dstanek is doing with native saml support18:10
dstanekstevemar: 1 really/18:10
bretonhow much policy files are changed18:10
ayoungme, we know we need SAML and openidc18:10
ayoungwhat roles do people want18:10
lbragstadbreton yeah - that would be a good one, too18:10
*** ravelar has joined #openstack-meeting18:11
*** rbak has joined #openstack-meeting18:11
morganso 3 options imo18:11
lbragstadcan it be an essay question? ;)18:11
dstanekwhat is keystone lacking?18:11
bretonnobody knows what keystone is lacking.18:11
dstanekbreton: then it's done!18:11
lbragstad"In 500 words or less, what do we need to work on?18:11
bretoni tried asking a lot and everyone wants it to "just work"18:11
morgan1) policy, 2) something something multi-az how many etc needed, 3) native saml?18:11
*** claudiub has quit IRC18:12
lbragstadmorgan ++18:12
stevemarreply back to the ML if you can about your suggestion18:12
stevemarotherwise i'll pick one of the ones here18:13
lbragstadI think we could use some more feedback on policy - that kind of information is always hard to come by18:13
ayoungmorgan, what do you mean by multi az?18:13
morgan4) Write an Essay covering all aspects of keystone you are curtrently using and wish to have in the future. Use proper grammar, this essay will be graded on a 1-5 scale.18:13
morganmust be 1000 words or more, no more than 15 pages18:13
samueldmqI agree a great question would be something that will help us to set a long term goal starting/continuing in next cycle18:13
bretonnobody except us wants something in keystone18:13
bretonpeople want some concept18:13
bretonlike "policy"18:13
morganayoung: how many azs are folks really running single keystone in, how many are they trying to scale out to (single = single shared store), why single shared store/issues with it/latency/etc.18:14
stevemarbreton: yeah, i understand what you mean18:14
breton(it's the one i heard a lot btw)18:14
morganayoung: it's just a request we keep getting asked about.18:14
ayoungwhat is an az?18:14
samueldmqbut if the public is usign/testing, tehy know what keystone is abou18:14
samueldmqabout18:14
morganavailability zone, datacenter, discreet cloud install, pick your poison18:15
ayoungAhhhh18:15
ayoungI was reading it a authz....got it18:15
stevemarlet's go with the scaling question18:15
morganusing "aws" terms since it is pretty universal :)18:15
bretoni am afraid that with the multi-az question we are going to be asking 5-7 people18:15
bretonbecause 90% of deployments are single-region18:15
ayoungyou'd be surprised breton18:15
morgani think we can refine the question and get needs/desires18:16
ayoungmany are single region due to constraints, would like to have more18:16
morganayoung: ++18:16
stevemarwe could have it open ended and say "are you using multiple regions, and if not, what is stopping you"18:16
bretonayoung: yes. But we are basically asking them to architect for us.18:16
ayoungbreton, many people are willing to architect it, so long as they don't have to implement it18:17
ayoungwe can then pick and choose18:17
morganstevemar: lets make it 2 way open ened18:17
*** diablo_rojo has joined #openstack-meeting18:18
stevemarmorgan: want to work with me on this?18:18
morganstevemar: Are you using multiple regions backed by a single shared keystone (replicated or otherwise)? If so, what are the short comings you are running against and how far are you trying to scale. If not, are you looking to move to multiple regions in a shared keystone backend and/or what is stopping you (limitations)?18:18
morganstevemar: something like that as a starting place.18:18
morganstevemar: sure.18:18
stevemarrgr, lets move on18:18
stevemar#topic Office hours starting this Friday [lbragstad]18:18
*** openstack changes topic to "Office hours starting this Friday [lbragstad] (Meeting topic: keystone)"18:18
* morgan locks the door(s) to the office so we can watch lbragstad try and pick the lock.18:18
lbragstadalright - this is pretty self explanatory18:19
stevemarlbragstad: ^18:19
dstanekwoot!18:19
ayoungmorgan, suspect lbragstad would resort to chainsaw18:19
lbragstadlast year dstanek was running office hours every friday18:19
morganayoung: truth18:19
ayoungor explosives18:19
lbragstadayoung both are acceptable18:19
stevemari'm super pumped about it18:19
lbragstador mjolnir18:19
ayoungHA!18:19
lbragstadbut yet18:19
stevemarwe have a lot of little bugs to squash: https://docs.google.com/spreadsheets/d/156q820cXcEc8Y9YWQgoc_hyOm3AZ2jtMQM3zdDhwGFU/edit?usp=sharing18:20
lbragstadwe want to restore that meeting - and see if we can get it going again18:20
lbragstadanyone have questions about the format?18:20
stevemarlbragstad: we can adapt as we go, i think the way to make it succeed to do talk about it in the channel and communicate often18:20
lbragstadstevemar ++18:21
samueldmqjust in the case someone is not looking at the etherpad18:21
stevemaranyone else plan on attending? :)18:21
lbragstadI'm totally open to finding new ways to keep the initiative afloat18:21
samueldmqmailing list announcement18:21
*** kristia__ has joined #openstack-meeting18:21
samueldmq#link ttp://lists.openstack.org/pipermail/openstack-dev/2016-December/109319.html18:21
samueldmqetherpad18:21
samueldmq#link https://etherpad.openstack.org/p/keystone-office-hours18:21
lbragstadI forsure will be blocking off most of my day to it18:21
gagehugoI'm definitely interested in it18:21
dstanekI'll be around18:22
stevemar4 of us at least :)18:22
lbragstad16:00 - 23:00 UTC (9:00 - 17:00 CST)18:22
lbragstad^ that's my availablility18:22
stevemaralright, next topic ...18:22
stevemar#topic bumped a bunch of blueprints [stevemar]18:22
*** openstack changes topic to "bumped a bunch of blueprints [stevemar] (Meeting topic: keystone)"18:22
stevemari bumped the following to Pike:18:23
stevemarNative SAML in keystone18:23
stevemarExtend user API to support federated attributes18:23
stevemarVersioned federation mappings18:23
stevemarPer-User Auth Plugin Requirements18:23
stevemarFernet Key Store18:23
stevemarfeature proposal freeze deadline was dec 31/1618:23
*** spotz_zzz is now known as spotz_18:23
*** tonytan4ever has quit IRC18:23
morgan++18:23
stevemarnative saml / versioned mapping / per-user auth had no code18:23
stevemarfernet store had a -218:24
stevemarand federated attributes, it's going to be a 2 parters anyway, the work for Ocata can still go in18:24
*** tonytan4ever has joined #openstack-meeting18:24
morganper-user-auth will have some code up soon, just better to delay since this is a short cycle18:24
bretongood, i was a little struggling to get fernet key store stuff into proper shape.18:25
stevemarwell folks can always ask for an exception18:25
morganif some leading refactoring lands, great, but I don't expect the bulk of the funcational bits to land.18:25
samueldmqstevemar: that's nice. we have a few weeks for 3 features (in progress) and some bugs18:25
samueldmqsounds reasonable18:25
stevemarsamueldmq: right, this significantly reduces the amount of new stuff landing in o-318:25
*** kristia__ has quit IRC18:25
stevemarwith shadow mapping and role check being the big ones18:26
morganproposal: never make a freeze happen on new years again18:26
ayoungHeh18:26
lbragstadlol18:26
morganeither hit that freeze before the break or after18:26
morgannot on.18:26
bretonwhy?18:26
stevemarmorgan: it was agreed upon at the summit, to give folks who really wanted to code on the holiday a chance to do a PoC18:26
morganit's still silly18:26
ayoungheh18:27
morgani would have pushed for 1st day back18:27
stevemarwith the change in cycle dates i don't think it'll be an issue18:27
morgananyway18:27
morgannot a big deal18:27
stevemaryah18:27
stevemarnoted for next time (whoever runs the show after me :) )18:27
stevemarlooks like no questions there, will jump to next topic18:28
samueldmqfreeze on the 1st and you'll need 3 cycles to recover18:28
* samueldmq 's kidding18:28
stevemar#topic a single policy file18:28
*** openstack changes topic to "a single policy file (Meeting topic: keystone)"18:28
*** tonytan4ever has quit IRC18:28
*** acoles is now known as acoles_18:29
ayoungHa!18:29
stevemari was looking at using oslo.policy's in-code defaults, but then realized we have 2 policy files18:29
lbragstadstevemar mhmm18:29
ayoungstevemar, ah, you mean just for Keystone?18:29
ayoungcloudsample should die18:29
stevemarayoung: yes, just the sample keystone provides18:30
lbragstadfor historical context - how come we have two policy files?18:30
ayoungI thought you mean one policy for all OpenSrtack18:30
stevemarnah18:30
ayoungopensmack18:30
samueldmqI think we could transfer some checks from cloudsample to the main one if needed18:30
stevemarlbragstad: i lack the historical context :)18:30
samueldmqand then kill cloudsample18:30
ayoungOK, so, a lot of the issues that cloudsample exposed went into the rbac middleware design18:30
dstanekcloud sample is the one I use all the time18:30
stevemarcloud sample is more "domain-aware"18:31
lbragstad(this actually leads into a topic i have for the policy meeting tomorrow so I'm super curious about this history of this)18:31
samueldmqstevemar: ++ let's make the main one domain-aware too18:31
ayoungcan't change the default without breaking a lot of people18:31
samueldmqand kill the cloud sample18:31
stevemari assumed what samueldmq said, move some checks over to policy.json and delete cloud sample after18:31
ayounglets kills domains18:31
lbragstadayoung is that because v2.0 isn't domain aware?18:31
ayounglbragstad, its because people do domain operations with admin tokens scoped to projects18:32
lbragstadoh18:32
ayoungyou break workflow.  Horizon only recently grew domain awareness18:32
breton"domain operations" sounds weird18:32
ayounga lot of Henry's rule writing was way too complicated to follow in cloud sample, too.  Matching the scope....18:33
rodrigodsisn't the main policy file the one with the global admin issues?18:33
*** rbak has quit IRC18:33
samueldmqmigrate and deprecate the cloud sample18:33
ayoungbreton, "operations on domains" sound better?18:33
samueldmqput a notice on the top of it18:33
*** bobh has joined #openstack-meeting18:33
ayoungrodrigods, they both have that18:33
samueldmqpeople using it should at least open the file (and see the notice ) :)18:33
bretondomains sounds to me just like containers for projects and users18:33
ayoungit was easier to fix in cloudsample18:33
*** hieulq_ has quit IRC18:33
*** yangyapeng has joined #openstack-meeting18:33
rodrigodsbut the main one just checks "role:admin"18:33
bretonayoung: nah, i'm talking about the meaning of it18:33
rodrigodsthe cloudsample at least have the cloud_admin18:33
bretonwhat perpose do domains serve today?18:34
rodrigodsand the concept of domain_admins18:34
*** hieulq_ has joined #openstack-meeting18:34
ayoungrodrigods, someone needs to carry forward the 968696 work.  I've been pulled off it18:34
breton1. Source of users18:34
breton2. ???18:34
samueldmqso we saying we can't make the policy better because it'll break people ? :(18:34
*** hieulq_ has quit IRC18:34
stevemaryeah, i like the "cloud_admin" and "domain_admin" difference that is in cloud sample18:34
ayoungbreton, a namespace for projects18:34
rodrigodsbreton, think it is a clear separation in the cloud18:34
rodrigodsat least, the reseller idea was going to push that way18:34
*** rbak has joined #openstack-meeting18:34
bretonayoung: why do we need that?18:34
ayoungstevemar, we can't force roles on people either withoug breaking it18:34
ayoungbreton, without it, project names are global18:35
ayoungconsider the implications.18:35
bretonayoung: ok, so 2. namespace for projects18:35
stevemarlooks like we need more investigation here18:36
breton3?18:36
ayoungbreton, that is it18:36
ayoungjust the 218:36
stevemari thought it was just created to better show the domain operations available in v318:36
rodrigodsi always thought the cloudsample was going to be the main one18:36
ayoungrodrigods, that was one opinion18:36
rodrigodsthe only issue was the "domain_id" checking for the cloud_admin18:36
stevemarrodrigods: yep18:36
rodrigodsbut we have the admin project now, so...18:37
ayoungrope Henrynash in to any discussion on this, please18:37
ayoungits his bailywick18:37
stevemarayoung: i was just going to do that offline :)18:37
lbragstad^ that sounds like an action item18:37
samueldmqI also would like to hear henrynash's opinion, he's the one who originally wrote it iirc18:37
stevemari'll take that as an action item18:37
*** bobh has quit IRC18:37
ayoungIMNSHO the rule in cloudsample are way too hard to follow18:37
rodrigodsayoung, yeah... but that's our fault18:38
*** yangyapeng has quit IRC18:38
ayoungbut they are a better "scope" check than the base policy file18:38
rodrigodsif we want to be detailed in the rules, it needs to be written like that18:38
stevemarlooks like it went in here: https://github.com/openstack/keystone/commit/c7a5c6cf27a80ca50db9f1a1a74e8795eeefd9d118:38
stevemarback in havana :)18:38
ayoungthink in terms of rbac in middleware and you will see that they should be mostly scope checks18:39
ayoungadmin in there for the rare api18:39
*** zxiiro-away is now known as zxiiro18:39
ayoungotherwise, the domain ops rules should be allowed for anyone with the appropriate role on the domain18:40
stevemari'll talk with henry about it, it was just something i was mulling over18:40
stevemar#topic open discussion18:41
*** openstack changes topic to "open discussion (Meeting topic: keystone)"18:41
*** sdake has joined #openstack-meeting18:41
lbragstadstevemar if you get henry in -keystone, i'd be happy to hop in that discussion, too18:41
lbragstadstevemar i'd like to start thinking about proposing a project tag for rbac support and assess using keystone as an example for other projects to follow18:42
*** david-lyle has joined #openstack-meeting18:42
lbragstadand consolidating our policy files sounds like a good first step18:42
*** salv-orlando has joined #openstack-meeting18:42
samueldmqlbragstad: ++18:42
stevemaryeah, its going to be a whole thing18:43
stevemarif no one has anything else we can end it early18:43
*** nadya has joined #openstack-meeting18:44
*** nadya has quit IRC18:45
* stevemar is assuming quiet for 2 minutes means he can end the meeting18:45
stevemarthanks for coming all :)18:45
stevemarwelcome back18:45
bretonyey.18:45
stevemar#endmeeting18:45
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"18:45
openstackMeeting ended Tue Jan  3 18:45:16 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-01-03-18.00.html18:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-01-03-18.00.txt18:45
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-01-03-18.00.log.html18:45
*** asselin has joined #openstack-meeting18:45
*** browne has left #openstack-meeting18:46
*** gagehugo has left #openstack-meeting18:46
*** jaugustine has quit IRC18:46
*** annegentle has joined #openstack-meeting18:46
*** Swami has joined #openstack-meeting18:46
*** salv-orlando has quit IRC18:51
*** salv-orlando has joined #openstack-meeting18:51
*** bdperkin has joined #openstack-meeting18:53
*** bdperkin has quit IRC18:53
*** bdperkin has joined #openstack-meeting18:53
*** jaugustine has joined #openstack-meeting18:54
*** s3wong has joined #openstack-meeting18:56
*** annegentle has quit IRC18:58
*** annegentle has joined #openstack-meeting18:58
fungiwow, not much to talk about in keystone. fifteen minutes early?!?18:59
*** salv-orlando has quit IRC18:59
fungiinfra team, welcome to the exciting future of 2017!19:00
dstanekwe're just that good19:00
fungithis week we have futuristic topics proposed by AJaeger and fungi19:00
AJaegero/19:00
fungiafter winning a prolonged battle against 2016 we're starting the new year with a pretty clean slate on most of our usual meeting boilerplate, so this should go quickly19:00
*** ljxiash has quit IRC19:00
* zara_the_lemur__ is excited for the futuristic topics19:00
*** toscalix has quit IRC19:00
*** salv-orlando has joined #openstack-meeting19:01
clarkbhello19:01
fungithe future won't wait, so i guess we should get started19:02
fungi#startmeeting infra19:02
openstackMeeting started Tue Jan  3 19:02:05 2017 UTC and is due to finish in 60 minutes.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: infra)"19:02
openstackThe meeting name has been set to 'infra'19:02
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:02
fungi#topic Announcements19:02
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:02
fungilooks like i don't have any for this week19:02
fungias always, feel free to hit me up with announcements you want included in future meetings19:02
fungi#topic Actions from last meeting19:02
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:02
fungi#link http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-12-20-19.03.html19:02
*** Shrews has joined #openstack-meeting19:02
fungi"1. (none)"19:02
fungigood work!19:02
zaroO/19:03
fungii have to admit, i did a lot of that19:03
funginot ashamed19:03
*** caboucha has quit IRC19:03
fungi#topic Specs approval19:03
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:03
fungiwe don't seem to have anything new up this week19:03
fungi#topic Priority Efforts: Docs Publishing via AFS (AJaeger)19:03
*** openstack changes topic to "Priority Efforts: Docs Publishing via AFS (AJaeger) (Meeting topic: infra)"19:03
*** caboucha has joined #openstack-meeting19:03
fungi#link http://lists.openstack.org/pipermail/openstack-docs/2016-December/009430.html production docs.o.o cut-over plan19:03
*** sdake has quit IRC19:04
fungiwe were talking about this in irc yesterday, and it feels like we're ready to forge ahead here19:04
fungithe plan looks pretty solid19:04
jeblairi was just catching up on that this morning19:05
AJaegeryes, I think we're ready...19:05
*** ravelar has left #openstack-meeting19:05
jeblairi had one question -- why make docs-archive.o.o?  is files.o.o not sufficient for being able to retrieve a file in the (unlikely) event that we need it?19:05
AJaegerupdated plan at http://lists.openstack.org/pipermail/openstack-docs/2017-January/009436.html19:05
AJaegerjeblair: you cannot really follow links19:06
AJaegerall links to / will go to files.o.o instead of to the docs root19:06
jeblairokay, but i thought the archive was so that we can pull a file out and copy it over if we find it's missing19:06
fungiAJaeger: are they absolute, not relative?19:06
AJaegerit really depends - and some have docs.o.o hardcoded19:07
jeblaircreating a new vhost to serve obsolete content seems, at best, unecessary, and at worst, actually counter productive19:07
fungii guess the primary need is to have a copy of the files in case we forgot anything after we've told rackspace to tear down the cloudsites account. i'm less concerned about giving it a dedicated vhost and custom 404 forwarding but those also sound pretty cheap to add19:08
*** ociuhandu has joined #openstack-meeting19:08
fungiit does also seem like we should stop serving a dedicated site for the stale archive after some period of time, even if we do continue to keep copies of the files around19:09
fungimainly to avoid confusion like jeblair mentions19:09
jeblairokay.  it's a significant change to the plan.  i'd love it if we had a good reason for it, and a plan for retiring it, etc.  but i'm not going to veto it if someone wants to do that (extra) work.19:09
fungii'm mostly ambivalent, though curious to see arguments for why the files.o.o interface is really insufficient19:11
AJaegerwe can move forward without the extra vhost - and discuss the need of a vhost with the rest of the docs team.19:11
jlvillalo/19:11
jeblair(like, to me, the fact that links don't work is not a problem as i never envisioned the purpose of this to be that we would say "oh, you're looking for that doc?  it's hosted on docs-archive.openstack.org"19:11
jeblairi thought the purpose was to say "oh, crap, we're missing a doc, let me find it in the archive and manually copy it over")19:11
AJaegermy intention is indeed manually copying it over19:12
* AJaeger checks some old emails19:12
*** nadya has joined #openstack-meeting19:13
jeblairif you make docs-archive.o.o, make sure you make a fully-exclude robots.txt19:13
fungiright, we really really really don't want that appearing in search engines19:13
AJaegerindeed19:13
*** kristian__ has joined #openstack-meeting19:15
fungiokay, so are we at least agreed we can move forward with steps 1 and 2 for now, and discuss the necessity of step 3 with the docs team?19:15
AJaegeryes19:15
jeblairyes for 1...19:15
fungiwhat other blockers do we have for 2?19:16
jeblairfor 2 -- i pushed up a patch to do a vos release in cron so that we could serve docs from a readonly volume19:16
fungioh, that hasn't merged yet?19:16
jeblairi'm not sure if it landed19:16
fungipretty sure i reviewed it, but checking19:16
jeblairAJaeger: i think you were fixing it up?19:16
jeblair#link https://review.openstack.org/40088719:16
* AJaeger checks19:16
fungii seem to have new-year amnesia so i don't trust my pre-holiday memories at this point19:16
jeblairyeah, working through some fog myself :)19:17
AJaegerjeblair: yes, I fixed it19:17
jeblairwe may want to land that and create the replica volumes before doing #219:17
fungiokay, looks like i did review it19:17
* AJaeger updates plan and adds that change19:17
*** wllabs has quit IRC19:18
jeblair(we don't *have to* but we can be more relaxed about it if we're not in production during that)19:18
jeblairthat will let us serve docs from the readonly volumes which gives us HA on the backend storage19:18
fungionce #1 is done and 400887 merges and is checked out and confirmed working, should we schedule/announce a window to do #2 (the dns change) or just trust that it will be seamless enough we can announce it agter it's done?19:19
AJaegeranything else we want to do for that?19:19
jeblairthat gives me a warm fuzzy19:19
jeblair(we can also, later, add HA/load balancing on the frontend webserver if needed, but that's separate)19:19
fungis/agter/after/19:19
*** cartik has quit IRC19:19
*** kristian__ has quit IRC19:20
AJaegersince we can change back anytime if we notice problems, I'm fine with just doing it19:20
jeblairfungi: i vote seamless in the general case, but coordinate with docs team so they can watch for issues)19:20
fungisounds fine to me19:20
* annegentle catches up19:20
fungiwho from infra-root is taking point on the updated import from AJaeger's plan (item #1)?19:21
annegentleI was going to volunteer for 3 if I understand what's needed.19:21
AJaegerannegentle: nothing there that either of us can do19:21
clarkbianw had done the first pass.19:22
fungii think the feeling here is that none of us is entirely certain what's driving #3 in that plan19:22
annegentleAJaeger ah, ok19:22
fungiso want a better handle on the reasons and long-term maintenance of that archive19:22
annegentlefungi the scenario is what I keep mentioning but can't seem to get traction on - what if someone can't find something later and comes to me because I was docs PTL at the time?19:22
AJaegerannegentle: do we need docs-archived page or is it enough to have the archive?19:23
annegentleAJaeger what's the technical difference? As long as my scenario means I answer "go to this thing" I'm fine.19:23
AJaegerannegentle: http://files.openstack.org/docs-old/ has all the content, it's just not clickable19:23
fungiyeah, we don't dispute that we'll make a copy of the old content _files_ available, just disputing the driver for having it be completely rendered and usable as a documentation site on its own19:23
annegentleAJaeger that's probably fine19:23
AJaegerannegentle: and we already don't have that content anymore, we redirect /bexar /cactus etc and had removed that content ages ago19:23
annegentlefungi ok, then sounds like the retrieval use case is taken care of19:24
annegentleAJaeger right, because we thought we'd be able to build it.19:24
annegentleAJaeger from source19:24
annegentleAJaeger but that's not the case now19:24
annegentleAJaeger hence my concern19:24
AJaegerand that should still be the case.19:24
clarkbI can help out but don't want to take point as I am currently trying to make elasticsearch + logstash less failsauce after it went away for a week and a half over holidays19:24
AJaegerannegentle: old versions of our tools should be able to build old documents19:25
annegentleAJaeger oh, I thought you said on the ML that's not possible. Can't find the email on a quick look though.19:25
fungiyeah, not impossible, just tricky to put together a platform/environment contemporary with the old content suitable for rebuilding it19:25
fungiand not likely to be something we'd look at automating, so it would be a lot of manual effort for someone if it became necessary19:26
annegentlefungi oh lord, no need to automate19:26
annegentlefungi an outline that it's possible is fine to me19:26
AJaegerit's possible, yes19:27
AJaegermight be tricky as fungi said19:27
annegentleok, then my concerns are addressed. Yeah, I get the age-old problem of aging platforms. no biggie19:27
* AJaeger will followup on that email thread19:28
fungiyep, you'd probably need to get a old ubuntu lucid (or earlier?) vm booting, and install the necessary toolchain components from versions that were released around that same timeframe19:28
AJaegerHere's what I propose now: http://paste.openstack.org/show/593810/19:28
annegentleAJaeger with your 5) and doublechecking the rest I think it's good-to-go.19:29
AJaegerfungi: depends on what needs building. I expect java to run on newer distros as well - and that's the main part that we need19:29
AJaegerannegentle: let me add 6) Double check links on new docs.o.o19:29
fungiAJaeger: that paste lgtm19:29
annegentleAJaeger good point19:29
AJaegerannegentle: do you mean something else with double checking?19:30
annegentleAJaeger I meant me double-checking your paste :)19:30
annegentleAJaeger sorry, no additional checks necessary :)19:31
AJaegergreat!19:31
*** kristian__ has joined #openstack-meeting19:31
AJaegerok, so any infra-root volunteers to help with the steps, please?19:32
fungiianw doesn't seem to be around for the meeting but we can try to catch up with him later in #openstack-infra and see whether he's interested in updating the production content with the missing bits and refreshing the archive volume (since he did teh earlier stages of it)19:32
*** korzen has joined #openstack-meeting19:32
*** caboucha has quit IRC19:32
jeblairyeah, i'm not familiar with that part, so i'd love it if ianw or pabelanger could refresh it19:33
fungimy main goal for today was to get some consensus on the remaining steps and confirmation that we can move forward with them19:33
jeblairi'll make the read-only volumes, etc19:33
fungiso if we don't get volunteers in-meeting that shouldn't be a show stopper19:33
fungii'd imagine people are still catching up from their holiday breaks19:33
*** bobh has joined #openstack-meeting19:33
clarkbya thats my current situation19:34
fungiwe'll circle back around after the meeting today or tomorrow and try to work out who's doing what next19:34
* AJaeger will send a summary mail around to keep everybody updated19:34
fungiany other details we need to discuss for thus?19:34
clarkbelasticsearch/logstash went really sideways wtih us all afk so trying to correct that before moving on to other stuff19:34
fungis/thus/this?19:34
* AJaeger is happy, thanks19:34
*** salv-orlando has quit IRC19:35
fungiugh, i need to reconnect my irc client19:35
fungijust got a note from freenode they're about to reboot the server i'm connecting through19:35
fungibrb19:35
*** fungi has quit IRC19:35
*** TheJulia has quit IRC19:35
*** serverascode has quit IRC19:35
*** mkrai has quit IRC19:35
*** efried has quit IRC19:35
*** dimtruck has quit IRC19:35
*** Kiall has quit IRC19:35
*** ayoung has quit IRC19:35
*** JoseMello has quit IRC19:35
*** tinwood has quit IRC19:35
*** yinwei_computer has quit IRC19:35
*** gus has quit IRC19:35
*** sheel has quit IRC19:35
*** vdrok has quit IRC19:35
*** csatari has quit IRC19:35
*** tomhambleton has quit IRC19:35
*** numans has quit IRC19:35
*** igordcard has quit IRC19:35
*** jeblair has quit IRC19:35
*** mrhillsman has quit IRC19:35
*** peterstac has quit IRC19:35
*** laurelm has quit IRC19:35
*** markmcclain has quit IRC19:35
*** sam64 has quit IRC19:35
*** ktychkova_ has quit IRC19:35
*** nijaba has quit IRC19:35
*** SergeyLukjanov has quit IRC19:35
*** coreycb has quit IRC19:35
*** lennyb has quit IRC19:35
*** sdake has joined #openstack-meeting19:35
*** Kiall has joined #openstack-meeting19:35
*** igordcard has joined #openstack-meeting19:35
*** jeblair has joined #openstack-meeting19:35
*** SergeyLukjanov has joined #openstack-meeting19:36
*** ktychkova has joined #openstack-meeting19:36
*** numans has joined #openstack-meeting19:36
*** fungi has joined #openstack-meeting19:36
*** coreycb has joined #openstack-meeting19:36
*** laurelm has joined #openstack-meeting19:36
*** RY has joined #openstack-meeting19:36
*** ayoung has joined #openstack-meeting19:36
*** lennyb has joined #openstack-meeting19:36
*** dimtruck_ has joined #openstack-meeting19:36
*** tinwood has joined #openstack-meeting19:36
*** efried has joined #openstack-meeting19:36
RYhello19:36
*** mrhillsman has joined #openstack-meeting19:36
*** gus has joined #openstack-meeting19:36
*** markmcclain has joined #openstack-meeting19:36
*** peterstac has joined #openstack-meeting19:36
*** dimtruck_ is now known as dimtruck19:36
*** sam64 has joined #openstack-meeting19:36
*** nijaba has joined #openstack-meeting19:37
*** nijaba has quit IRC19:37
*** nijaba has joined #openstack-meeting19:37
fungiokay, i seem to be back successfully, so will continue chairing19:37
fungi#topic Upgrading Askbot on ask.openstack.org (fungi)19:37
*** openstack changes topic to "Upgrading Askbot on ask.openstack.org (fungi) (Meeting topic: infra)"19:37
*** JoseMello has joined #openstack-meeting19:38
fungii think we're ready to try upgrading askbot again19:38
fungithis is the change that will fire the upgrade process:19:38
fungi#link https://review.openstack.org/408657 Update ask.o.o to latest 0.7.x branch r219:38
fungii've marked it wip temporarily while we discuss granting mrmartin root access to the server19:38
fungi(askbot's upgrade process is fragile and we've already had to emergency revert it once, so i feel like having hands-on troubleshooting access for him would help matters)19:38
*** harlowja has joined #openstack-meeting19:38
fungi#link https://review.openstack.org/416072 Adding user 'mkiss' to ask.o.o19:38
*** mkrai has joined #openstack-meeting19:38
fungii'm primarily looking for infra-root consensus on that, but as always everyone is welcome to review19:38
*** bobh has quit IRC19:38
fungiwe've also got an issue, at least on the currently deployed version, with lots of false-positive rejections from its spam filtering19:38
fungiit has been suggested that the upgrade could solve it or at least make it easier to pin down:19:39
clarkboh good passes tests now19:39
fungi#link http://lists.openstack.org/pipermail/openstack-infra/2016-November/004812.html Logs for Ask.O.o - chasing false positive spam labeling19:39
fungithat's another thing which is hard to reproduce in staging and might benefit from mrmartin having more immediate access to troubleshoot19:39
*** sheel has joined #openstack-meeting19:39
*** vdrok has joined #openstack-meeting19:39
*** Cibo_ has quit IRC19:40
*** csatari has joined #openstack-meeting19:40
*** kristian__ has quit IRC19:40
*** kristia__ has joined #openstack-meeting19:40
*** guoshan has joined #openstack-meeting19:41
*** tomhambleton has joined #openstack-meeting19:41
*** jaugustine has quit IRC19:42
fungii didn't really have much else. i'm happy to drive/monitor the upgrade myself but wanted to try and get some consensus on mrmartin's shell access to it before proceeding19:42
clarkbworks for me, was waiting for tests to come back (I guess they did quickly and I just got distracted)19:43
jeblair++19:43
*** TheJulia has joined #openstack-meeting19:43
fungiokay, cool. thanks for reviewing19:44
fungi#topic Repo renaming (fungi)19:44
*** openstack changes topic to "Repo renaming (fungi) (Meeting topic: infra)"19:44
fungiwe have four repo renames proposed (in two project-config changes), so may want to consider whether it's time to schedule another rename maintenance19:45
*** prateek has joined #openstack-meeting19:45
fungii mostly added this to the agenda as filler in case we had time at the end (which we seem to)19:45
fungii know we just did a rename maintenance a few weeks ago, so if people think we should wait a little longer i'm fine with that19:45
*** rbudden has quit IRC19:46
*** guoshan has quit IRC19:46
fungithe last one seemed to go pretty smoothly though, what with ansible automation and gerrit's online reindexing19:46
clarkbits worth pointing out that newer gerrit has index consistency issues and online reindex problems according to gerrit ml19:46
fungiwe mainly need to be aware to give the release team a heads up, since they'd presumably want to avoid releasing anything while reindexing is underway, just to be safe19:47
clarkb(just throwing it out there as something we should test as part of our upgrade)19:47
fungioh, ouch19:47
fungiany news on whether they've pinned down the cause?19:47
zaroclarkb: i think a fixed was just merged for that19:48
zarohttps://gerrit-review.googlesource.com/#/c/93479/19:49
clarkboh good19:49
*** vishnoianil has joined #openstack-meeting19:49
fungiso hopefully nothing we need to worry about once we upgrade, other than maybe checking for a backport19:50
fungigiven that we're pretty much all just coming back from a wasteland of feasts and booze and lack of internets, i'm inclined to push the rename discussion out and revisit during next week's meeting19:51
fungiunless there's anyone who's eager to try and run one asap19:51
*** serverascode has joined #openstack-meeting19:51
clarkbsounds good19:52
fungi#topic Open discussion19:52
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:52
*** salv-orlando has joined #openstack-meeting19:53
fungianything else 2017 demands of us already?19:53
jlvillalMeetbot review request: https://review.openstack.org/413222   Gives better details when doing a #undo for some of the actions.19:53
jlvillalLow priority item...19:53
fungithanks jlvillal19:54
jlvillal:)19:54
zaroWas wondering if anybody knows where pabelanger is with the puppet fix to add zuul-launcher to openstack-ci repo?19:54
*** sdake has quit IRC19:54
fungizaro: i think there was a change proposed. i'll check the discussion from before the holidays19:54
fungioh, he said "just doing a few tests before pushing it up"19:56
fungi#link http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-12-20-19.03.log.html#l-1019:56
zarook. Thanks.19:57
fungii'm not seeing it for his open reviews, so maybe he still hasn't pushed it into review.o.o yet19:57
*** masayukig is now known as masayukig_19:57
*** masayukig_ is now known as masayukig19:57
*** gordc has joined #openstack-meeting19:57
fungianybody have anything else in these last two minutes?19:58
fungiokay, i'll give you back a minute of your time ;)19:59
fungithanks everyone!19:59
fungisee you all in #openstack-infra19:59
fungi#endmeeting19:59
*** cdent has joined #openstack-meeting19:59
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"19:59
openstackMeeting ended Tue Jan  3 19:59:17 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-01-03-19.02.html19:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-01-03-19.02.txt19:59
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-01-03-19.02.log.html19:59
*** AJaeger has left #openstack-meeting19:59
* ttx stays quiet until the clock turns19:59
* fungi stays tuned for the tc meeting, coming up next19:59
dhellmanno/19:59
johnthetubaguyo/20:00
thingeeo/20:00
ttxdims, dtroyer, EmilienM, mordred, mtreinish, sdague, stevemar: around ?20:00
EmilienMo/20:00
ttxflaper87 will miss this one IIRC20:00
dimso/20:00
stevemaro/20:00
mtreinisho/20:00
ttx#startmeeting tc20:00
openstackMeeting started Tue Jan  3 20:00:30 2017 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
dtroyero/20:00
*** openstack changes topic to " (Meeting topic: tc)"20:00
openstackThe meeting name has been set to 'tc'20:00
ttxHappy new year everyone!20:00
stevemarhappy new year!20:00
ttxOur agenda for today is at:20:00
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:00
ttx(2017 new year resolution: use #info #idea and #link liberally to make for a more readable summary)20:01
sdagueo/20:01
ttx#topic Driver teams: establish new "driver team" concept, or not20:01
*** openstack changes topic to "Driver teams: establish new "driver team" concept, or not (Meeting topic: tc)"20:01
ttxTwo weeks ago we discussed this and boiled it down to two options20:01
ttxConsider driver teams as being a piece of "OpenStack" (using the grey option as implementation):20:01
ttx#link https://review.openstack.org/40382920:01
ttxor not consider driver teams as being a piece of OpenStack unless they fill all the open collaboration requirements (soft black option):20:01
*** Shrews has left #openstack-meeting20:01
ttx#link https://review.openstack.org/40383620:02
sigmaviruso/20:02
ttxmtreinish in particular was still not comfortable living by the grey option, and several TC members still preferred soft black.20:02
ttxTaking a step back, for me the choice all depends on whether driver teams are looking for *recognition* or *discoverability*.20:02
johnthetubaguywhat would our users find useful here?20:02
ttxIf they are just looking for *discoverability*, then I think we can work out documentation / marketplace solutions that gives vendor drivers equivalent visibility to in-tree / in-team drivers20:02
ttxwithout having to permanently change governance or compromise on open collaboration requirements for "OpenStack" proper20:02
dhellmannright, I'm not that concerned with discoverability as a goal for this20:02
ttxso choosing "soft black" + getting our act together on driverlog/docs/marketplace is a valid answer20:03
ttx(and thingee volunteered to work on that, to give those teams what they need fast enough)20:03
ttxBut if they are /also/ looking for recognition, then grey is probably the most reasonable way to give it to them20:03
ttxSo... Do we have a clear view on what those teams are really after ?20:03
mtreinishttx: heh, that's a much more eloquent way to put what I was getting at during that last meeting :)20:03
*** TxGirlGeek has quit IRC20:03
ttxjohnthetubaguy: in both cases they get discoverability20:03
dhellmannI'm much more interested in having us consider drivers to be an important enough contribution that we include those contributors in our community.20:03
thingeeas noted in 403829 I'm not in favor of it because I believe based on the conversations I've had with sambetts|afk at the summit that it's discoverability20:03
gordcdhellmann: +1, that's what marketing/sales departments are for.20:03
stevemarmtreinish: ttx does that20:03
ttxstevemar: that is called preparation20:03
dims:)20:04
thingeeso approving this is not necessary of what was originally being asked20:04
dtroyerthingee: for the original case, maybe.  But we are considering a class of projects here...20:05
fungiwhile i second dhellmann's desire to include driver development as contributing to our community, i worry that the grey option removes some impetus to follow our real community development expectations by giving them a watered-down version they can follow instead20:05
* edleafe wanders in late20:05
dimsthingee ttx : is anyone else in the "drivers to be an important enough contribution that we include those contributors in our community" category?20:05
thingeeI understand sambetts|afk put up a review to created. I said originally, because at the summit, he was concerned about out of tree drivers in neutron not having documentation at docs.o.o20:05
ttxdhellmann: from your interactions with that crowd, what would you say the need/want ?20:05
ttxthey*20:05
thingeedtroyer exactly what dims asked, does anybody else want this, and give a good reason why20:05
mtreinishfungi: ++20:05
dhellmannttx: I took their original request to be official at face value. The subsequent discussions about discoverability may speak more to their motivation. *My* motivation hasn't changed.20:06
fungii still old that is _is_ possible to develop drivers in a completely open fashion, and am not entirely comfortable saying it's okay if you find that too much effort20:06
thingeeI think if we fix some legacy things that disallow out of trees to be discovered, this is not necessary20:06
fungis/old/hold/20:06
dhellmannthingee : discoverability and encouraging participation are orthogonal20:06
thingeeand if people are not in favor of making what a team's community of out of tree drivers more discoverable, then we should rediscuss if we want to allow out of tree drivers at all20:07
jrollfungi: do you think it's possible to develop drivers for proprietary things on a level playing field? (how does that work, simulator-y things?)20:07
thingeedhellmann can you explain how you see this encouraging participation?20:07
dhellmannI don't believe if we tell a large number of groups of people we're not interested in what they're producing, they'll be highly motivated to participate in the core of projects.20:07
dtroyerjroll: FWIW, I do not think it is _really_ possible, having tried that in more than one $DAY_JOB20:08
ttxjroll: I think it's hard. May involve sending free test rigs to everyone interested.20:08
bswartzyou can't not allow out of tree drivers -- it's open source20:08
*** jaugustine has joined #openstack-meeting20:08
fungias evidence, i look to the littany of linux and *bsd kernel drivers which were developed initially without vendor assistance, and used as leverage to convince manufacturers to start providing better specs and documentation for their products so that anyone could write drivers for them20:08
thingeedhellmann who is saying we're not interested?20:08
*** korzen has quit IRC20:08
dhellmannthingee : if we tell teams working on drivers that their contributions aren't allowed to be official, we are.20:08
thingeeagain official and discoverability.20:08
sdagueI think the level playing field statement is a quagmire of vagueness when it comes to drivers.20:08
jrollfungi: good example20:08
ttxdhellmann: arguably we are saying they are not "OpenStack", but something that can be used with "OpenStack"20:09
thingeeyou are official if we make it easy to discover your driver compatible with openstack20:09
thingeettx +120:09
*** e0ne has joined #openstack-meeting20:09
dhellmannthere's plenty of evidence that folks will write drivers anyway. I'm not worried about drivers going away. I'm worried about these companies with little experience being open having a bad experience when they're *trying* to be open.20:09
ttxdhellmann: I get your point though. We need drivers for openstack to be successful so why not consider them in20:09
dhellmannand deciding that a community built on the idea that we want lots of varied contributions doesn't want *their* contributions, of any sort20:10
johnthetubaguydhellmann: thats what I meant about what users want, they want their driver to be written in the open, following similar patterns to other drivers, ideally, but maybe I am overthinking it20:10
dhellmannnot all of them will choose to go through the trouble to become official, for various reasons20:10
thingeedhellmann I agree. and that's why I think the larger problem of them not being included in various things they would get without this patch should be considered first20:10
dhellmannjohnthetubaguy : I agree, we should encourage open development of drivers.20:10
ttxI'm on the fence, mostly because once official driver teams are created it will be hard to go back20:10
*** jaugustine has quit IRC20:10
thingeeI think we should fix the larger problem first. If that doesn't fix things, we should revisit doug's proposal20:11
dhellmannthingee : I don't think we want to start opening docs.openstack.org up to folks who have no relationship with us20:11
dtroyerttx: ++  and why it is clear to me we are not ready to go this route quite yet (if at all)20:11
sdaguethingee: and you think the larger issue is documentation discovery?20:11
ttxsdague: and proper marketplace listings20:11
thingeedhellmann we already do. cinder drivers which are in tree and are allowed to contribute their drivers in20:11
thingeesdague that is one example and the one given to me by sambetts|afk himself with cisco20:12
jrollthingee: being in cinder's tree is definitely some relationship20:12
johnthetubaguyor we could make it so only openly accessible teams are listed?20:12
dhellmannthingee : cinder drivers in-tree are part of a repo that belongs to a team that works with the tc, even if the specific contributors are not20:12
thingeejroll right, again larger problem is with out of tree drivers here20:12
dhellmannthingee : if all of the drivers were in tree, we wouldn't even be having this conversation20:12
thingeewe need to set what they can do that you get for being in tree. we have no business of saying what an individual team considers part of their project20:12
jrollthis would open it to *anything* in the openstack git namespace, which is open to any code20:12
jroll"it" being docs.o.o20:13
thingeedhellmann and again, I say revisit whether we should allow out of tree20:13
ttxthingee: I agree we could give the non-nuclear option a try, but how long do you expect it will take to get things fixed on the documentation / discovery front ?20:13
fungiit seems to me like docs.o.o is probably not the ideal venue to host driver-specific documentation anyway, and instead we should let official projects continue to document driver-related things in their own documentation while simultaneously improving the marketplace to allow driver authors to specify links to wherever they want to host their own driver-specific documentation20:13
thingeethis is just a bandaid fix imo20:13
*** zara_the_lemur__ has left #openstack-meeting20:13
dhellmannthingee: so you're after the red option?20:13
* thingee checks color code cliff notes20:13
dhellmannthingee : that's the one where the TC requires project teams to take in all drivers20:14
dhellmannthingee : we rejected that as too harsh20:14
dhellmannthis isn't a question of the motivation of the driver authors for being in tree20:14
ttxdhellmann: I think he is after one of the black options. Drivers can be made out of openstack20:14
dhellmannthey've been kicked out by their host project20:14
thingeedhellmann no, I'm saying that the discussion should be revisited if we're even beginning to question out of tree drivers.20:14
dhellmannttx: under that approach we can solve the discoverability problem, but not the community membership problem20:14
fungiyeah, i don't feel comfortable telling ptls what drivers they have to include in their project teams, much less in their source code trees for consuming services20:15
dhellmannthingee : I'm not sure we're on the same page at all.20:15
johnthetubaguynot all "drivers" are the same thing at this point either20:15
ttxdhellmann: agreed. It is the crux of the issue. Whether we want to consider those teams (and their slightly-less-open development methods) as a part of OpenStack20:16
thingeettx I guess if I begin proposing various ways to have to vendor products more included and the person who originally requested this sambetts|afk feels I'm meeting his requests reasonably, that we can consider that a win?20:16
dhellmannthingee : all of the alternatives you've proposed can be done independently of this change except allowing publishing to docs.openstack.org, afaict. Am I missing something?20:16
bswartzfungi: I disagree about the docs -- for some projects the most important part of configuring them is the driver configuration, and the config guide on docs.o.o is a good place for that information20:16
thingeedhellmann yes, I'm saying we can do maybe do without your proposals and just fix sambetts|afk's initial problems with even requesting to be an official team20:16
dhellmannttx: if you remember, I was in favor of *not* allowing special openness rules. I do see the argument in favor of loosening some, and could live with it, though.20:16
fungibswartz: and letting each individual driver vendor write that documentation inconsistently and outside your project's control and host that on docs.o.o is a good idea?20:16
dhellmannthingee : that doesn't solve *my* problem, though20:16
ttxdhellmann: well, the alternative was to relax rules for everyone...20:17
bswartzfungi: the project teams can and do review it, as do the docs team20:17
fungibswartz: even for repos maintained by unofficial teams?20:17
dhellmannthingee : the request from sambetts|afk highlighted a separate issue related to community membership that I'm trying to address in some way. I'm not really concerned with discoverability, except as a side-effect of being inclusive.20:17
dhellmannttx: true.20:18
ttxback to whether driver teams want recognition as a part of openstack or really don't care that much20:18
bswartzfungi:  talking about cinder/manila config guides20:18
dimsdhellmann : right, so i was asking if anyone is really is feeling left out20:19
ttxdhellmann: was there anything explicit, or do you consider them applying as sufficient proof ?20:19
fungibswartz: i'm not concerned about documentation vetted by and under teh control of manila, more worried about letting random manila driver teams not under manila or the docs team's oversight push up whatever documentation they want and serving it from an official-looking openstack website20:19
thingeewell if it's about community membership, there's the incentive some have brought up in your proposal review. Contribute to the core project to rather than just your individual out of tree driver repo.20:19
dhellmanndims : do we wait for someone to have that problem and not report it before we do something?20:19
thingeedhellmann ^20:19
dimsdhellmann : good point20:19
bswartzfungi: manila has all the drivers in tree -- I don't want them anywhere else20:19
*** caboucha has joined #openstack-meeting20:20
bswartzout of tree drivers are an abomination IMO20:20
*** askb has joined #openstack-meeting20:20
dhellmannthingee : telling people we don't care about their driver contributions isn't likely to have a positive effect on their contributions elsewhere. Offer them a carrot.20:20
ttxbswartz: but if someone does drivers somewhere on github, you'd prefer that we don't adopt them as a separate openstack project, right ?20:20
fungibswartz: and that's fine. i'm saying instead of encouraging random out-of-tree drivers not maintained by the teams responsible for the services with which they're integrated host their own individual documentation on docs.o.o themselves20:20
jrollfungi: reminder that the docs team does not oversee most of the big tent's docs, e.g. ironic just pushes whatever docs it wants20:21
bswartzttx: correct -- they should contribute directly to manila or stay on github20:21
ttxdhellmann: supposing that's a carrot to them20:21
thingeedhellmann are we having a shortage of drivers though in this being a problem. Last time I checked cinder drivers are still growing beyond 80 drivers now20:21
fungijroll: yep, which is why i said "or" here. i'm worried that a team which isn't the docs team nor ironic would be greenlit to publish ironic driver docs on docs.o.o20:21
dtroyerbswartz: does that approach result in any (or many?) thin in-tree wrapper drivers calling out to a propriteaty actual-driver somewhere?20:21
sdaguedo we have neutron community folks around? Because this really impacts neutron first.20:21
thingeeThe carrot is you're compatible with OpenStack because you follow the individual project team's guidelines of what is official20:21
dhellmannttx: yes, well, interpretation is up to the observer.20:21
ttxsdague: yes, wondering if we should not survey driver teams and see how much they care with the two solutions20:22
*** dimtruck is now known as zz_dimtruck20:22
sdagueAnd it would be good to have inputs there. I think we've mostly had cinder, nova, manilla voices, which are definitely more intree oriented20:22
*** zz_dimtruck is now known as dimtruck20:22
ttxs/with/about/20:22
mtreinishsdague: yeah, although do we think any other project will follow the neutron model?20:22
jrollfungi: idk, I don't have a problem with that, personally. some docs are better than none20:22
dhellmannthingee : and if the project team's guideline is "only this one driver, and we don't care about yours" then what option does someone have?20:22
bswartzdtroyer: that hasn't been a problem for us -- we make it hard to do that by frequently changing the driver interface (similar to how Linux makes out of tree drivers painful to maintain)20:22
mtreinishbecause it seems kinda unlikely to me that any of the other projects will20:22
dtroyermtreinish: neutron seems to be unique partially because of its histroy as a heavily vendor-driven project from the start20:23
mtreinishdtroyer: right20:23
sdaguejroll: would ironic end up in this model as well?20:23
smcginnismtreinish: I agree20:23
thingeedhellmann again, that's a problem of a particular project that I think we're trying to fix in the tempest related review I gave20:23
jrollironic has out of tree drivers as we require CI20:23
fungijroll: i mean as opposed to letting them host their documentation elsewhere. they're not going to automatically end up in an index on docs.o.o anyway, so if the driver marketplace is the index to driver documents, having some of them linking to documentation elsewhere seems fine to me20:23
dtroyerbswartz: thx20:23
jrollsdague: not pushing 100% out, but forcing some to stay out, yes20:23
ttxOK, so that we know where we stand today... I propose a quick indicative vote for TC members20:23
sdagueor, so ironic and neutron are going to be primary consumers20:23
sdagueand I feel like we haven't really had a ton of neutron feedback here20:24
fungisaying driver=specific documentation without collaboration from the consuming project doesn't automatically become more "discoverable" by getting served from docs.o.o20:24
jrollfungi: yeah, I suppose. I guess I lean toward 'why not' on the docs point, rather than 'why' :)20:24
ttx#startvote Where do you stand? allow-driver-teams, just-improve-discovery, on-the-fence20:24
openstackBegin voting on: Where do you stand? Valid vote options are allow-driver-teams, just-improve-discovery, on-the-fence.20:24
openstackVote using '#vote OPTION'. Only your last vote counts.20:24
ttx#vote on-the-fence20:24
thingeearmax has started the conversation in setting the precedent of how out of tree drivers could be tested. If we support that idea, we can begin using the neutron communities' guideline  of what  is official and highlight those like we do with other vendor products.20:24
fungi#vote just-improve-discovery20:24
dhellmann#vote allow-driver-teams20:25
mtreinish#vote just-improve-discovery20:25
sdague#vote on-the-fence20:25
EmilienM#vote allow-driver-teams20:25
dtroyer#vote allow-driver-teams20:25
thingeedhellmann contributors being paid by a company don't need to incentive from the community to contribute driver code.20:25
dims#vote on-the-fence20:25
*** tonytan4ever has joined #openstack-meeting20:25
johnthetubaguyvote one-the-fence20:25
sdaguejohnthetubaguy: you need a #20:25
ttxjohnthetubaguy: add #20:25
dhellmannthingee : the company needs an incentive to allow them to do anything other than that, though20:25
thingee#vote just-improve-discovery20:25
johnthetubaguy#vote on-the-fence20:25
thingeedhellmann can you give me examples of where that's a problem today though?20:25
fungithingee: i'd rather start from an even more loose position of giving projects a means of registering driver details into the driver marketplace using whatever criteria they feel is appropriate to determine "support"20:26
johnthetubaguysdague: ttx: sorry one handed badness20:26
ttxExplaining my on-the-fence: I'd like to reach out to driver teams and assess how much they want recognition vs. discoverability20:26
ttxbecause we seem to be assuming a lot (one way or another)20:26
dhellmannthingee : I don't think we need to wait for a problem to exist before we try to address it.20:26
stevemar#vote on-the-fence20:26
fungithingee: rather than requiring cinder and neutron to agree on what makes a driver supported20:26
ttxending vote in 20 sec20:26
ttx#endvote20:27
openstackVoted on "Where do you stand?" Results are20:27
openstackon-the-fence (5): dims, ttx, stevemar, sdague, johnthetubaguy20:27
openstackallow-driver-teams (3): EmilienM, dhellmann, dtroyer20:27
openstackjust-improve-discovery (3): thingee, mtreinish, fungi20:27
ttxPretty split20:27
thingeedhellmann I find that too bad that the TC wants to open this gate when there is no problem.20:27
dimsi'd like to understand if what can be done w.r.t just-improve-discovery without the need for TC intervention20:27
fungii'll note that i'm really in favor of "first-improve-discovery" (and then see if we still have a problem)20:27
johnthetubaguyfungi: I like that starting point idea, the projects know best20:27
thingeejohnthetubaguy +120:28
dimsfungi : true20:28
ttxAs an on-the-fence I propose to reach out to driver teams and try to get their feeling20:28
ttxstevemar: would you mid helping me in there ?20:28
ttxmind*20:28
jrollfwiw the TC is typically pretty reactive, I'd love to see some proactiveness here if we're confident the problem will happen eventually20:28
stevemarttx: sure20:28
dtroyerDoes anyone have a sense of what might change for the nova/cinder/manila teams if driver teams were introduced?20:28
jrollttx: stevemar: I can hook you up with some folks maintaining out of tree ironic drivers, if that's helpful20:28
ttxdims, stevemar, sdague, johnthetubaguy: anything else we should do this week to help you make a call ?20:28
dtroyerie, unintended consequences?20:28
smcginnisdtroyer: My only concern with all of this is having less incentive to contribute to core code.20:29
fungijroll: i'm happy to talk to the foundation site devs about dumping some more time into improving the driver marketplace (which is really just a sort of poc right now), but would need input from different teams on what would make it usable for them20:29
ttxdtroyer: not really, but yes introducing driver-teams is a more significant move than just sitting and fixing discoverability20:29
stevemarjroll: that would be helpful. ttx i just want to make sure what we're proposing actually helps the folks we're trying to help (so reaching out to driver teams sounds like a good place to start that)20:29
*** tonytan4ever has quit IRC20:29
johnthetubaguyttx: I would be tempted to approve driver teams, but I am attracted by the option of discoverability controlled by projects20:29
dtroyersmcginnis: you feel that you might see companies going in the opposite driection of what we are trying to achieve?20:29
dhellmannsmcginnis : I wouldn't expect a lot of impact on that to teams that welcome drivers into the parent projects.20:30
thingeesmcginnis I think this proposal in recognizing individual contributors in their vendor's team deliverables will not help with core contributions20:30
*** tonytan4ever has joined #openstack-meeting20:30
sdaguettx: mostly I want to know that whatever we're doing is actually going to solve the problem for neutron over the next year, with feedback from some of the neutron leadership on that20:30
ttxOK, I don't think we'll make more progress today. Feel free to discuss this (dhellmann and thingee in particular as you seem to lead both options)20:30
thingeerecognizing openstack contributors have to come from the projects themselves, not vendor python libraries, etc20:30
johnthetubaguyI guess I feel more worried about encouraging open collaboration on the vendor drivers20:31
dims++ sdague20:31
ttxsdague: ok, so making sure we cover neutron in our analysis20:31
thingeettx yes I will be happy to continue working this out with dhellmann20:31
ttxI propose we move on20:31
smcginnisdtroyer: Just a concern if we do anything that they are able to state they contribute to OpenStack by allowing them to work in isolation. Unfounded concerns probably.20:31
dhellmannyes, let's move on20:31
*** mickeys has joined #openstack-meeting20:31
johnthetubaguysdague: good point, the proposal currently excludes many neutron drivers due the the API clause20:31
*** dimtruck is now known as zz_dimtruck20:31
ttx#action ttx and stevemar to reach out to prospective driver teams and assess how much they care about recognition vs. just discoverability20:32
ttx#topic Disallow downtime of controlled resources during upgrades20:32
*** openstack changes topic to "Disallow downtime of controlled resources during upgrades (Meeting topic: tc)"20:32
ttx#link https://review.openstack.org/40436120:32
dolphmo/20:32
ttxdolphm: o/20:32
* ttx checks for refresh20:32
dolphmsince the last time this was on the agenda, i've incorporated some feedback into the latest review...20:32
*** AlanClark has joined #openstack-meeting20:33
dolphmspecifically, checkout L45-51 for some updated wording https://review.openstack.org/#/c/404361/6/reference/tags/assert_supports-accessible-upgrade.rst20:33
ttxlgtm20:33
ttxdhellmann: does the new wording fix your concerns ?20:33
dhellmannthe new wording addresses my only nit, thanks dolphm20:33
dolphmdhellmann: thanks for the feedback20:33
sdaguedolphm: ok, so basically if we do this the net is20:34
*** kristia__ has quit IRC20:34
stevemardolphm: lgtm, but i was OK with previous revs too20:34
*** bobh has joined #openstack-meeting20:34
*** kristian__ has joined #openstack-meeting20:34
sdaguenova, cinder get accessible upgrades, neutron / glance do not?20:34
sdaguejust to get this chunking in my head20:34
johnthetubaguyjust checking a phrase here: "continuously validated"20:35
EmilienMsdague: glance doesn't?20:35
dolphmno one would get it out of the gate, unless someone is already asserting the availability of resourcing during an upgrade?20:35
dolphmjohnthetubaguy: that's a slight change since the last revision as well20:35
mtreinishEmilienM: you can't get to the images during an upgrade20:35
sdagueEmilienM: when the glance services are offline, there is no access to their resources20:35
sdaguebecause their resources are only http accessable20:35
EmilienMindeed20:36
sdaguedolphm: ok, but conceptually, the services that can do this20:36
sdagueneutron can't because of ovs link resets and the like20:36
*** TxGirlGeek has joined #openstack-meeting20:37
dhellmannsdague : is that a fundamental problem with neutron, or could it be fixed?20:37
ttxare ovs link resets "abnormal", though ?20:37
EmilienMI thought the neutron thing changed in the last releases, I remember some parameters in Neutron to disable this thing20:37
sdaguedhellmann: it's a fundamental problem with some backends20:37
sdagueincluding the leading ones20:37
dhellmannok20:37
*** bobmel has quit IRC20:38
jrollmaybe this needs to reference a 'reasonable' amount of downtime? e.g. one packet dropping is probably fine, putting glance behind a load balancer and coordinating service restarts is probably fine20:38
dhellmannI'm not really sure what it buys us to have this flag at all if we have 2 fundamental services that can't achieve it, and therefore the cloud can't achieve it.20:38
johnthetubaguyits generally where projects sit in the dataplane, they have lots to do20:38
jrolllike, things ops would care about, not 0 downtime ever20:38
jrollif that makes sense20:38
fungii'm still a little fuzzy on how we expect to "continuously" test to prove that a service isn't unavailable at some random point during teh upgrade process20:38
dhellmannjroll : ++20:38
johnthetubaguyjroll: that feels like yet another tag, but thats a fair point20:38
fungibut maybe i'm getting too deep into imagining the implementation?20:38
johnthetubaguyfungi: "continuously" is the bit worrying me20:39
ttxjroll: yes, and that definition may vary20:39
*** bobh has quit IRC20:39
jrolljohnthetubaguy: if it's another tag, I guess I'm asserting this one isn't terribly useful20:39
johnthetubaguyjroll: this one would be one Nova could assert (if you turn off consoles, I guess...)20:39
jrolljohnthetubaguy: for something like glance, if an op wants zero downtime, a load balancer (and coordination) should be a requirement20:39
EmilienMsdague: I think the neutron thing was fixed by https://review.openstack.org/#/c/182920/20:40
dhellmannjroll, johnthetubaguy : right, if the point is to get to a state where it's possible to upgrade openstack with little disruption, and we're defining the way to do that as something some projects can't ever do, then how is it useful to say that even some projects can do it?20:40
mtreinishfungi: start a separate process to ping a server in a loop throughout a grenade job and fail if it drops? :p20:40
dolphmfor services that don't manage resources outside the control plane, i think the question is whether the tag should apply at all, or whether you get this tag for "free" by successfully asserting the rolling upgrade tag20:40
jrolldhellmann: ++20:40
johnthetubaguyjroll: yeah, I am OK with that, but they need to be able to run old and new services at the same time to do that20:40
mtreinishs/drops/drops any packets/20:40
jrolljohnthetubaguy: indeed20:40
fungimtreinish: that only proves it was up at the times those icmp echo requests arrived20:40
dimsmtreinish : ssh session instead? :)20:40
ttxsdague: would glance pass this with rolling updates (like you can always find an API server that works) ?20:40
fungimtreinish: but proves nothing about the (micro?)seconds between each ping20:41
mtreinishdims: yeah, ssh would be a better test :)20:41
*** dfflanders has joined #openstack-meeting20:41
johnthetubaguydhellmann: depends if you can make a very available cloud with a set of projects that all assert the "better" tag, until we can, its a bit useless I guess20:41
mtreinishfungi: fair point20:41
dhellmannfungi : I think "continuously" was added when someone pointed out that a test before and after an upgrade doesn't actually ensure that the resources was available *during* the upgrad20:41
sdaguedhellmann: well I think the fact that neutron can't right now should impact future evolution, because it's not really a neutron limitation but how some backends were done because this wasn't being thought of20:41
dolphmdhellmann: ++20:41
sdaguettx: maybe, we're starting to get pretty deep into HA architecture... which is fine, but up until this point the OpenStack upstream hasn't dictated that (it was left to distros / install tools)20:42
dhellmannfungi : so it's not the literal mathematical definition of continuously, but "during the upgrade with a reasonable sampling rate" or something else less word salady20:42
*** guoshan has joined #openstack-meeting20:42
johnthetubaguysdague: I think you reminded me I need to understand those neutron problems better20:42
dolphmi feel like asserting testing methodologies in tags is getting a little bit too much into the implementation details. if a project applies for a tag, i think it's up to the TC to determine whether the implementation of the tests satisfies the spirit of the tag20:42
ttxOK, I'm starting to wonder what user question this answers20:42
dhellmannsdague : is the problem in the driver, or in the thing the driver talks to?20:42
dhellmanndolphm : yeah, I was trying to clarify the wording for the discussion but I think it's fine as it is in the doc now20:43
EmilienMwhat are the neutron problems we are discussing of? is there any launchpad bug reference? I've seen https://bugs.launchpad.net/neutron/+bug/1383674 but it seems fixed for OVS backend. What else would cause this downtime?20:43
openstackLaunchpad bug 1383674 in neutron "Restarting neutron openvswitch agent causes network hiccup by throwing away all flows" [High,Fix released] - Assigned to Ann Taraday (akamyshnikova)20:43
sdagueso, EmilienM may be right that - https://review.openstack.org/#/c/182920/ fixed it20:43
ttxbasically WHY are we introducing this if it's not to drive behavior nor to answer a user question20:43
dhellmannyay, ok20:43
sdagueEmilienM: if the OVS backend flow rebuild is handled, that's fine20:43
johnthetubaguydolphm: yeah, I am largely agreed with that (does the testing spot the massive whoppers), I worry the wording in the proposed tag doesn't cover that20:43
dolphmttx: "my cloud provider advertises that they upgrade their cloud every day with the latest security updates, etc. will that affect my ability to consume cloud without interruption?"20:43
jrollsdague: reference HA architecture bits feels like a useful thing for upstream to dictate - e.g. "you should run two of these conductor things, you should put APIs behind LB"20:43
sdaguebut that can't survice an OVS upgrade itself20:43
fungidhellmann: my concern with "continuously" is more that i think there may be a misconception that there's anything _actually_ continuous in computing, and we need to design around the native discontinuity there instead (and word things accordingly)20:44
sdaguejroll: sure, I don't disagree, it's just new territory20:44
jrollas one of the first people to ever deploy ironic in production... I would have loved to have that20:44
jrollnod20:44
EmilienMrussellb: any thoughts on  ^^^^ ?20:44
dhellmannfungi : sure. I think I agree with dolphm that we don't want to put too much detail about the way to do it in the tag, but try to express the desired outcome.20:44
dolphmjohnthetubaguy: are you focusing on the word "continuously", or something else?20:44
sdaguejroll: and something that needs to be a bit more consistent across the projects. Because if one shows how to do it with haproxy, and another with something else, it's not super useful for a whole system :)20:45
jrollsdague: +1000000020:45
johnthetubaguydolphm: yeah, I am fixed on that word for reasons I don't understand20:45
ttxdolphm: feels a lot like "are those services working as the industry considers they should"20:45
johnthetubaguysdague: jroll: +120:45
sdagueI thought the basic question being answered was to Operators20:46
jrollI think of these as answers to ops questions, "how often (and how painful) is it reasonable to upgrade things"20:46
fungireally, we have a lot of different services used in different ways, and what sorts of outages are impactful for each of them varies accordingly20:46
johnthetubaguysdague: FWIW, I consider ovs a host/hypervisor upgrade, so its like a machine swap, if you don't want some packet loss20:46
ttxOK, feels like we'll need another round here20:46
* johnthetubaguy face palm20:46
johnthetubaguyignore that, thats more outage than ovs replace20:47
ttxdhellmann, sdague: please make sure to file your remarks/concerns on the review20:47
*** zz_dimtruck is now known as dimtruck20:47
sdaguejroll: right, and if I upgrade service X do I need to plan for customers seeing an outage20:47
johnthetubaguywe did some ovs upgrades, but you get packet loss20:47
*** guoshan has quit IRC20:47
jrollsdague: yep, meaning service X is going to get real old real fast :)20:47
fungiand brief packet loss for tcp-based protocols or thinbs which implement error correction/retransmission at the application layer may still be completely seamless20:48
ttxfeels like we'll have a hard time defining this as a tag, could be suggestions for improvements / goal instead20:48
dolphmjroll: if users are experiencing pain, then ops experiences the wrath of users... i don't see this as solving an ops pain point directly20:48
fungis/thinbs/things/20:48
jrolldolphm: not solving ops pain points, answering ops questions20:48
dolphmjroll: ah, i follow then20:48
ttxbecause defining "reasonable" and "normal" behavior will be hard overall20:48
johnthetubaguyI like sdague's suggestion of upgrade focused goals20:48
jrollideally users never notice an upgrade :)20:48
ttxanyway, i suggest we move on20:49
ttxand continue to discuss on the review20:49
johnthetubaguyjroll: +1, tricky to define20:49
ttxsince this is not ready20:49
*** nadya has quit IRC20:49
*** jaugustine has joined #openstack-meeting20:49
ttx#topic Pike goals20:50
*** openstack changes topic to "Pike goals (Meeting topic: tc)"20:50
ttxNot much time to discuss this20:50
EmilienMo/20:50
ttxEmilienM: looks like we have two goals proposed so far ?20:50
ttxanything else promising in the backlog ?20:50
ttx#link https://etherpad.openstack.org/p/community-goals20:50
EmilienMyes, python-3 and tempest plugin AFIK20:50
ttx* Add Pike goal split out tempest plugins (https://review.openstack.org/369749)20:50
ttx* add goal "support python 3.5" (https://review.openstack.org/349069)20:50
EmilienMwe had one goal for Ocata, having 2 goals for Pike would probably make sense20:50
dhellmannI saw some useful input from the product working group on the etherpad earlier today20:51
ttxah, missed it20:51
ttxHow are the proposed two doing in terms of community acceptance ?20:51
dhellmannthere were comments about their interest in some of the existing things, and one new one at the bottom20:51
EmilienMttx: for the python 3.5 goal, I haven't seen any pushback - https://review.openstack.org/#/c/349069/ (and ML)20:52
sdaguethose seem like reasonably scoped things, and have champions, so seems solid20:52
mtreinishttx: well I don't think anyone ever opposed the python 3 support. It was always more just a matter of feasibility in a timeframe and scope20:52
dhellmannthe only issue reported there was some concern about which python 3.5, since there's a bug swift needs fixed20:52
fungithough the infra team is using its own definition of compliance with the python 3.5 goal, which may not align with others' assumptions20:52
thingeeyes, I think we can move forward with py 3.520:52
EmilienMttx: for the tempest plugin goal - https://review.openstack.org/369749 - there are still some discussions in the proposal20:52
EmilienMsdague: ++ indeed20:52
jrollhas the tempest plugin goal been talked about on the ML? it has had some opposition in the patch20:53
ttxdhellmann: I guess that could be grounds for an exemption until 3.6 is done (or the bug is fixed) ?20:53
dimsmtreinish : dhellmann : i have only good things to say about teams i reached out to with issues for the dsvm up/down test20:53
dhellmannjroll: I haven't seen a thread, but I'm a few hours out of date20:53
stevemari like the advantages outlined in the tempest plugin patch20:53
jrolldhellmann: I'd expect a thread more than a few hours old by now :P20:53
ttxdone -> widely available20:54
dimsttx : there are other things that need to be fixed in swift well before that referenced bug is of concern20:54
dimsIMHO20:54
dhellmannttx: the fix is in a patch-level update to 3.5 (I don't remember which off the top of my head) but yes, I agree, that would make a delay OK in my mind20:54
ttxdims: right, so they could be working on that20:54
dhellmanndims : excellent, and thank you for picking that up20:54
mtreinishjroll: oops, i forgot to start a thread before the holidays when you asked me before20:54
*** gordc has left #openstack-meeting20:55
ttxEmilienM: when do you want to have the goals set in stone ?20:55
jrollmtreinish: heh, yeah, my question was "did I miss that during vacation" in disguise :)20:55
EmilienMttx: ocata-3 or rc1 if possible20:55
ttxAt least one month before PTG would be nice, so that people can plan to spend time in the Goal room20:55
EmilienMttx: it would gives us some window to prepare the communication and work in governance20:55
ttx(each goal will have a room for people wanting to quick-hack on them)20:55
dhellmanna month before ptg would be o-3, Jan 23-2720:55
EmilienMttx: eg: reach out teams so they can prepare their sessions at PTG if needed20:55
ttx(on Monday-Tuesday)20:56
ttxok, let's target o-320:56
mtreinishjroll: I'll push something out later today to start a ml discussion on it20:56
EmilienMttx: +120:56
ttxthat means refining the goals really quick20:56
*** absubram has quit IRC20:56
ttxand make sure people know they are coming20:56
dims++ ttx20:56
ttxalright, this seems to be on the right track20:56
jrollmtreinish: awesome20:57
EmilienMttx: I'll take actions on that, working closely with mtreinish and dhellmann20:57
ttxEmilienM: thanks again for coordinating20:57
ttx#topic Open discussion20:57
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:57
ttxFYI Piet Kruithof reached out to me saying he is stepping down from UX team PTLship20:57
ttxThere is a question of whether that team should continue as a standalone team20:57
ttx(or if UX efforts should rather be blended into every team)20:57
stevemarfor the future, can we have a set of goals for all projects to hit, not necessarily bound to a specific release/dev cycle?20:57
ttxstevemar: we would probably call that something else to avoid confusion20:58
EmilienMttx: how would we formalize #2 ?20:58
stevemarthen we don't have to worry about 'setting them in stone' by a specific milestone20:58
ttxI think the standalone UX team helped expose UX tools (personas, usability studies) to everyone20:58
thingeeI think a ux working group like we have api's etc would suffice20:58
ttxBut now that those tools are better-known, it's maybe time to encourage every team to use them directly20:58
thingeedon't think we need a team20:58
EmilienMthingee: agree20:58
thingeenot even sure what their deliverables were20:58
dhellmanndoes the existing ux team want to stay a team?20:58
dtroyerwhat we lose without Piet's team is the expertise in executing the studies20:58
ttxok, I propose to start a thread and check if there is a PTL candidate, or if that effort no longer needs a teazm or centralization.20:58
thingeettx +120:59
dhellmanndtroyer : ++, it's harder than it looks20:59
mtreinishttx: sounds like a plan20:59
EmilienMstevemar: how would you iterate?20:59
ttxWe'll see -- if nobody steps up the solution will find itself20:59
dtroyerdhellmann: I've done two of them and it really is...20:59
*** shamail has joined #openstack-meeting20:59
ttx#action ttx to start a UX thread20:59
thingeedtroyer +1 I guess what I meant was repo based deliverables.20:59
fungiwe also have a pholio instance in production now, requested by the ux team20:59
dhellmannthingee : they produced some ux reports that were distributed at the summit21:00
stevemarEmilienM: add them to a backlog once approved and when they are ready to target move the goal from backlog to cycle21:00
ttxdtroyer: agreed it's difficult to define personas or conduct studies without some centralization or guidance21:00
fungi(as a replacement for their use of the proprietary "invision" saas)21:00
ttxAlright we are out of time21:00
thingeedhellmann that is true. I guess those could be in a repo to recreate the pdfs21:00
EmilienMstevemar: I see, lgtm21:00
dhellmannstevemar : I like the idea of having a pipeline of goal definitions ready to go21:00
thingeebetter yet, put in a sphinx based doc on HIG, etc21:00
ttxThanks everyone! Don't despair, discussion is still progress :)21:00
dhellmannthingee : I think that's also part of what pholio was for21:00
stevemari would like to add support for say, microversions, in keystone, if it's approved. and once the cycle hits we're done.21:00
ttx#endmeeting21:00
*** openstack changes topic to "open discusion (Meeting topic: congressteammeeting)"21:01
openstackMeeting ended Tue Jan  3 21:00:59 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-01-03-20.00.html21:01
EmilienMttx: thx for chairing, as usual and happy new year folks :)21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-01-03-20.00.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-01-03-20.00.log.html21:01
*** ljxiash has joined #openstack-meeting21:01
johnthetubaguydhellmann: stevemar: +1 the pipeline21:01
dhellmannstevemar : nothing's stopping you from adding it now! ;-)21:01
jrollthanks ttx :)21:01
stevemardhellmann: it kinda does though, maybe not for that one, but for some of the more contentious ones21:01
dhellmannyeah, true21:02
stevemarjust a thought21:02
*** cdent has left #openstack-meeting21:03
*** shamail has quit IRC21:04
*** JoseMello has quit IRC21:05
*** ljxiash has quit IRC21:05
*** gagehugo has joined #openstack-meeting21:06
*** dbecker has quit IRC21:10
*** matrohon has quit IRC21:11
*** gagehugo has left #openstack-meeting21:11
*** rfolco_ has joined #openstack-meeting21:13
*** rfolco has quit IRC21:14
*** julim_ has quit IRC21:22
*** matrohon has joined #openstack-meeting21:24
*** ykatabam has joined #openstack-meeting21:25
*** sdake has joined #openstack-meeting21:25
*** nadeem has left #openstack-meeting21:26
*** iyamahat has joined #openstack-meeting21:27
*** e0ne has quit IRC21:29
*** rbudden has joined #openstack-meeting21:30
*** iyamahat has quit IRC21:33
*** tonytan4ever has quit IRC21:36
*** rfolco_ has quit IRC21:36
*** tonytan4ever has joined #openstack-meeting21:37
*** fzdarsky is now known as fzdarsky|afk21:38
*** fzdarsky|afk has quit IRC21:38
*** bobmel has joined #openstack-meeting21:38
*** jackie-truong has joined #openstack-meeting21:39
*** bobmel has quit IRC21:43
*** spzala has quit IRC21:44
*** cleong has quit IRC21:44
*** ijw has joined #openstack-meeting21:47
*** cdelatte has quit IRC21:48
*** sdake has quit IRC21:51
*** jrobinson has joined #openstack-meeting21:51
*** jrobinson has quit IRC21:53
*** sdake has joined #openstack-meeting21:53
*** jrobinson has joined #openstack-meeting21:54
*** RY has quit IRC21:56
*** dprince has quit IRC21:59
*** matrohon has quit IRC22:01
*** eharney has quit IRC22:01
*** Sukhdev has joined #openstack-meeting22:06
*** thorst has quit IRC22:07
*** thorst has joined #openstack-meeting22:08
*** ykatabam has quit IRC22:10
*** ijw has quit IRC22:11
*** jprovazn has quit IRC22:12
*** thorst has quit IRC22:13
*** ijw has joined #openstack-meeting22:13
*** lblanchard has quit IRC22:15
*** matrohon has joined #openstack-meeting22:15
*** abalutoiu has quit IRC22:16
*** VW has joined #openstack-meeting22:18
*** jaugustine has quit IRC22:19
*** fguillot has quit IRC22:22
*** VW has quit IRC22:23
*** Sukhdev has quit IRC22:24
*** fnaval_ has joined #openstack-meeting22:25
*** caboucha has quit IRC22:26
*** lpetrut has quit IRC22:27
*** salv-orlando has quit IRC22:28
*** edtubill has quit IRC22:28
*** VW has joined #openstack-meeting22:28
*** fnaval has quit IRC22:28
*** ykatabam has joined #openstack-meeting22:28
*** annegentle has quit IRC22:30
*** sdake has quit IRC22:30
*** salv-orlando has joined #openstack-meeting22:32
*** thorst has joined #openstack-meeting22:32
*** salv-orlando has quit IRC22:32
*** salv-orlando has joined #openstack-meeting22:33
*** baoli has quit IRC22:33
*** yangyapeng has joined #openstack-meeting22:35
*** jackie-truong has quit IRC22:35
*** thorst has quit IRC22:37
*** yangyapeng has quit IRC22:39
*** tonytan4ever has quit IRC22:41
*** galstrom is now known as galstrom_zzz22:41
*** tonytan4ever has joined #openstack-meeting22:42
*** tonytan4ever has quit IRC22:42
*** tonytan4ever has joined #openstack-meeting22:42
*** rbudden has quit IRC22:45
*** asselin has quit IRC22:49
*** tommylikehu_ has joined #openstack-meeting22:52
*** aeng has joined #openstack-meeting22:52
*** thorst has joined #openstack-meeting22:53
*** tonytan4ever has quit IRC22:53
*** jamesden_ has quit IRC22:57
*** thorst has quit IRC22:57
*** fnaval_ has quit IRC22:57
*** fnaval has joined #openstack-meeting22:58
*** sdake has joined #openstack-meeting22:59
*** jamesdenton has joined #openstack-meeting22:59
*** tommylikehu_ has quit IRC22:59
*** tommylikehu_ has joined #openstack-meeting22:59
*** spotz_ is now known as spotz_zzz23:01
*** jamesdenton has quit IRC23:01
*** matrohon has quit IRC23:09
*** kristian__ has quit IRC23:10
*** kristian__ has joined #openstack-meeting23:10
*** sdague has quit IRC23:11
*** openstack has joined #openstack-meeting23:13
*** ChanServ sets mode: +o openstack23:13
*** jaypipes has quit IRC23:14
*** tommylikehu_ has quit IRC23:14
*** kristian__ has quit IRC23:15
*** armax has quit IRC23:15
*** jaugustine has joined #openstack-meeting23:17
*** Julien-zte has joined #openstack-meeting23:21
*** ljxiash has joined #openstack-meeting23:23
*** VW_ has joined #openstack-meeting23:26
*** ljxiash has quit IRC23:27
*** lamt has quit IRC23:27
*** VW has quit IRC23:29
*** Julien-zte has quit IRC23:30
*** VW_ has quit IRC23:30
*** spzala has joined #openstack-meeting23:30
*** Fdaisuke has joined #openstack-meeting23:38
*** baoli has joined #openstack-meeting23:39
*** rbak has quit IRC23:41
*** guoshan has joined #openstack-meeting23:45
*** kjorgensen has quit IRC23:46
*** kjorgensen has joined #openstack-meeting23:48
*** Leom has quit IRC23:48
*** fnaval has quit IRC23:49
*** guoshan has quit IRC23:49
*** TxGirlGeek has quit IRC23:50
*** kjorgensen has quit IRC23:50
*** kjorgensen has joined #openstack-meeting23:50
*** kjorgensen has quit IRC23:51
*** VW has joined #openstack-meeting23:53
*** lixinhui has joined #openstack-meeting23:57
*** lixinhui has left #openstack-meeting23:57
*** VW has quit IRC23:58

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