Tuesday, 2016-08-30

*** _nadya_ has quit IRC00:03
*** dmorita has quit IRC00:05
*** dmorita has joined #openstack-meeting00:05
*** esberglu has joined #openstack-meeting00:06
*** zhurong has quit IRC00:07
*** shaohe_feng has quit IRC00:09
*** woodster_ has quit IRC00:09
*** shaohe_feng has joined #openstack-meeting00:10
*** onovy has quit IRC00:11
*** onovy has joined #openstack-meeting00:13
*** jungleboyj has quit IRC00:13
*** sdake has joined #openstack-meeting00:14
*** leeantho has quit IRC00:14
*** Patifa has quit IRC00:14
*** mtanino has quit IRC00:16
*** sarob has quit IRC00:16
*** Suyi_ has quit IRC00:16
*** shaohe_feng has quit IRC00:19
*** sindhu has joined #openstack-meeting00:19
*** Swami has quit IRC00:20
*** shaohe_feng has joined #openstack-meeting00:20
*** thorst has quit IRC00:23
*** thorst has joined #openstack-meeting00:24
*** spzala has quit IRC00:25
*** spzala has joined #openstack-meeting00:25
*** Wenzhi has joined #openstack-meeting00:27
*** pvaneck has quit IRC00:27
*** Apoorva has quit IRC00:27
*** iyamahat_ has joined #openstack-meeting00:29
*** shaohe_feng has quit IRC00:29
*** EdMc-ss has quit IRC00:30
*** EdMc-ss has joined #openstack-meeting00:30
*** iyamahat has quit IRC00:30
*** spzala has quit IRC00:30
*** shaohe_feng has joined #openstack-meeting00:31
*** cody-somerville has quit IRC00:31
*** cody-somerville has joined #openstack-meeting00:31
*** thorst has quit IRC00:32
*** saju_m has quit IRC00:32
*** sindhu has quit IRC00:37
*** shaohe_feng has quit IRC00:40
*** shaohe_feng has joined #openstack-meeting00:40
*** shashank_hegde has quit IRC00:44
*** ijw has joined #openstack-meeting00:46
*** ijw has quit IRC00:46
*** ijw has joined #openstack-meeting00:46
*** su_zhang has quit IRC00:48
*** su_zhang has joined #openstack-meeting00:48
*** su_zhang has quit IRC00:49
*** shaohe_feng has quit IRC00:50
*** shaohe_feng has joined #openstack-meeting00:53
*** su_zhang has joined #openstack-meeting00:53
*** sindhu has joined #openstack-meeting00:54
*** edtubill has joined #openstack-meeting00:57
*** su_zhang has quit IRC00:57
*** shaohe_feng has quit IRC01:00
*** zzxwill_ has joined #openstack-meeting01:00
*** vishwanathj has quit IRC01:02
*** shaohe_feng has joined #openstack-meeting01:02
*** xiaohhui has quit IRC01:02
*** vishwanathj has joined #openstack-meeting01:02
*** shaohe_feng has quit IRC01:10
*** shaohe_feng has joined #openstack-meeting01:11
*** zhurong has joined #openstack-meeting01:12
*** gyee has quit IRC01:14
*** sdake has quit IRC01:14
*** yamamoto has quit IRC01:15
*** thorst has joined #openstack-meeting01:17
*** thorst has quit IRC01:17
*** cody-somerville has quit IRC01:17
*** ivar-lazzaro has quit IRC01:17
*** ivar-lazzaro has joined #openstack-meeting01:17
*** edtubill has quit IRC01:17
*** thorst has joined #openstack-meeting01:17
*** ivar-lazzaro has quit IRC01:18
*** shaohe_feng has quit IRC01:21
*** sdake has joined #openstack-meeting01:21
*** yamamoto has joined #openstack-meeting01:21
*** shaohe_feng has joined #openstack-meeting01:22
*** hua has joined #openstack-meeting01:23
*** gongysh has joined #openstack-meeting01:23
*** donghao has joined #openstack-meeting01:25
*** hongbin has joined #openstack-meeting01:26
*** thorst has quit IRC01:26
*** mriedem_afk has quit IRC01:29
*** shaohe_feng has quit IRC01:31
*** shaohe_feng has joined #openstack-meeting01:31
*** ociuhandu has joined #openstack-meeting01:32
*** salv-orlando has joined #openstack-meeting01:32
*** ljxiash has joined #openstack-meeting01:34
*** ociuhandu has quit IRC01:34
*** Leo_ has joined #openstack-meeting01:34
*** banix has joined #openstack-meeting01:34
*** ivc_ has quit IRC01:35
*** Leo_ has quit IRC01:37
*** ivc_ has joined #openstack-meeting01:37
*** ivc_ has quit IRC01:37
*** ljxiash has quit IRC01:39
*** shashank_hegde has joined #openstack-meeting01:40
*** shaohe_feng has quit IRC01:41
*** shaohe_feng has joined #openstack-meeting01:41
*** amotoki has joined #openstack-meeting01:42
*** salv-orlando has quit IRC01:43
*** parora has joined #openstack-meeting01:43
*** prateek_ has quit IRC01:45
*** amotoki has quit IRC01:46
*** hua has quit IRC01:47
*** rfolco has quit IRC01:47
*** Sukhdev has joined #openstack-meeting01:48
*** cody-somerville has joined #openstack-meeting01:48
*** dslevin has left #openstack-meeting01:50
*** shaohe_feng has quit IRC01:51
*** s3wong has quit IRC01:52
*** ljxiash has joined #openstack-meeting01:52
*** ljxiash has quit IRC01:54
*** ljxiash has joined #openstack-meeting01:54
*** unicell has quit IRC01:55
*** shaohe_feng has joined #openstack-meeting01:56
*** hua has joined #openstack-meeting02:00
*** spzala has joined #openstack-meeting02:01
*** shaohe_feng has quit IRC02:02
*** shaohe_feng has joined #openstack-meeting02:02
*** vishwanathj has quit IRC02:03
*** vishwanathj has joined #openstack-meeting02:03
*** yamamoto has quit IRC02:05
*** zzxwill_ has quit IRC02:09
*** zzxwill_ has joined #openstack-meeting02:09
*** gongysh has quit IRC02:11
*** sindhu has quit IRC02:12
*** spzala has quit IRC02:12
*** shaohe_feng has quit IRC02:12
*** shaohe_feng has joined #openstack-meeting02:13
*** ijw has quit IRC02:14
*** ijw has joined #openstack-meeting02:14
*** ijw has quit IRC02:16
*** dtrainor has quit IRC02:18
*** shaohe_feng has quit IRC02:22
*** kbyrne has quit IRC02:22
*** thorst has joined #openstack-meeting02:24
*** kbyrne has joined #openstack-meeting02:24
*** shaohe_feng has joined #openstack-meeting02:25
*** Benj_ has joined #openstack-meeting02:30
*** thorst has quit IRC02:31
*** amotoki has joined #openstack-meeting02:31
*** Sukhdev has quit IRC02:32
*** shaohe_feng has quit IRC02:32
*** ljxiash has quit IRC02:32
*** shaohe_feng has joined #openstack-meeting02:33
*** ljxiash has joined #openstack-meeting02:35
*** ljxiash has quit IRC02:36
*** shu-mutou has joined #openstack-meeting02:36
*** ljxiash has joined #openstack-meeting02:36
*** Benj_ has quit IRC02:36
*** Sukhdev has joined #openstack-meeting02:37
*** epico has joined #openstack-meeting02:41
*** Sukhdev has quit IRC02:42
*** shaohe_feng has quit IRC02:43
*** shaohe_feng has joined #openstack-meeting02:43
*** draynium has quit IRC02:45
*** armax has quit IRC02:46
*** banix has quit IRC02:46
*** hongbin has quit IRC02:48
*** hongbin has joined #openstack-meeting02:48
*** draynium has joined #openstack-meeting02:48
*** banix has joined #openstack-meeting02:48
*** fnaval has quit IRC02:51
*** shaohe_feng has quit IRC02:53
*** ociuhandu has joined #openstack-meeting02:53
*** shaohe_feng has joined #openstack-meeting02:54
*** vishwanathj has quit IRC02:55
*** vishwanathj has joined #openstack-meeting02:55
*** ub has joined #openstack-meeting02:55
*** banix has quit IRC02:55
*** ub2 has quit IRC02:57
*** amotoki has quit IRC02:58
hongbin#startmeeting zun03:00
openstackMeeting started Tue Aug 30 03:00:10 2016 UTC and is due to finish in 60 minutes.  The chair is hongbin. Information about MeetBot at http://wiki.debian.org/MeetBot.03:00
*** jckasper has quit IRC03:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.03:00
*** openstack changes topic to " (Meeting topic: zun)"03:00
hongbin#link https://wiki.openstack.org/wiki/Zun#Agenda_for_2016-08-30_0300_UTC Today's agenda03:00
openstackThe meeting name has been set to 'zun'03:00
hongbin#topic Roll Call03:00
*** openstack changes topic to "Roll Call (Meeting topic: zun)"03:00
*** ub has quit IRC03:00
WenzhiWenzhi Yu03:00
*** amotoki has joined #openstack-meeting03:00
*** jckasper has joined #openstack-meeting03:00
hongbinhi Wenzhi03:00
Wenzhihi hongbin03:01
hongbinWenzhi: I know Madhuri cannot make this meeting03:01
hongbinOther folks are busy with the release possibly03:01
Wenzhiyes probably03:02
hongbinLe't wait a few more seconds to see if anyone else is joining03:02
Wenzhiso just you and me today? :)03:02
Wenzhiok03:02
hongbinhopefully not :)03:02
eliqiaohi03:02
hongbineliqiao: hey03:03
*** Kevin_Zheng has quit IRC03:03
*** shaohe_feng has quit IRC03:03
*** yanyanhu has joined #openstack-meeting03:03
yanyanhuhi, sorry, I'm late03:04
*** vishwanathj has quit IRC03:04
hongbinyanyanhu: hi03:04
*** shaohe_feng has joined #openstack-meeting03:04
*** vishwanathj has joined #openstack-meeting03:04
hongbinOK. Let's start. It looks folks are busy today. Maybe have a short meeting03:04
*** jckasper has quit IRC03:04
hongbin#topic Announcements03:04
*** openstack changes topic to "Announcements (Meeting topic: zun)"03:04
hongbin1. We have an accepted talk at Barcelona summit03:05
hongbin#link https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=zun03:05
hongbinplease come to the talk if you are available03:05
*** yamamoto has joined #openstack-meeting03:05
hongbin#topic Review Action Items03:05
*** openstack changes topic to "Review Action Items (Meeting topic: zun)"03:05
hongbin1. hongbin create a bug for enhancing the quickstart guide (DONE)03:05
hongbin#link https://review.openstack.org/#/c/359574/ Submit a patch instead03:06
yanyanhuhongbin, sure will definitely join it if have the chance to travel to barcelona03:06
hongbinyanyanhu: ok03:06
*** jamespage has quit IRC03:06
hongbinyanyanhu: hope to see you there03:06
Wenzhiyes ^^03:06
yanyanhuyes :)03:07
*** ociuhandu has quit IRC03:07
hongbin#topic Nova integration (Namrata)03:07
*** openstack changes topic to "Nova integration (Namrata) (Meeting topic: zun)"03:07
hongbinnarmrata is not here today03:07
hongbinlet's skip this one03:07
hongbin#topic Container image store03:07
*** openstack changes topic to "Container image store (Meeting topic: zun)"03:07
hongbin#link https://blueprints.launchpad.net/zun/+spec/glance-integration03:07
hongbin#link https://etherpad.openstack.org/p/zun-container-image03:07
*** vishwanathj has quit IRC03:08
hongbinthere is an initial decision about the image store at previous meeting03:08
*** vishwanathj has joined #openstack-meeting03:08
hongbinbasically, we will support both Glance and Docker Hub. If Glance is used, export docker image as a tar file before uploading to glance03:09
hongbin1. Glance:03:09
hongbin$ zun pull glance/busybox03:09
*** amotoki has quit IRC03:09
hongbin2. Public Docker Hub:03:09
hongbin$ zun pull busybox03:09
*** roxanagh_ has joined #openstack-meeting03:09
hongbin3. Private Docker registry:03:09
hongbin$ zun pull $REGISTRY_IP/busybox03:09
*** yamamoto has quit IRC03:10
hongbinLater, if there is more storage backend (i.e. glare) we can do this03:10
hongbin$ zun pull XXX/busybox03:10
hongbinbasically, it leverages the prefix to locate the image store03:10
yanyanhuhongbin, zun pull will pull specific image from e.g. glare to local host?03:11
*** ijw has joined #openstack-meeting03:11
hongbinyanyanhu: yes03:11
yanyanhulocal host where zun cmd is executed03:11
yanyanhuI see03:11
yanyanhulooks like kind of image management operations03:11
eliqiaoit seems we need to do a abstract layer to cover all image back-end.03:11
eliqiaoIf so, this may be out of zun's scope?03:12
hongbinyanyanhu: yes like docker pull/push03:12
hongbineliqiao: yes there needs to be a abstracted layer03:12
eliqiaoor, we are working out a unify image API for all containers images?03:12
hongbineliqiao: maybe like nova, it has a layer to talk to glance03:12
*** zzxwill_ has quit IRC03:12
*** zzxwill has joined #openstack-meeting03:13
hongbineliqiao: yes, but hopefully it is no more than push and pull03:13
*** yamahata has quit IRC03:13
eliqiaohongbin: it's glace client.03:13
*** fnaval has joined #openstack-meeting03:13
hongbineliqiao: yes, consider zun implements a glance client as well03:13
*** ub has joined #openstack-meeting03:13
*** shaohe_feng has quit IRC03:13
*** shaohe_feng has joined #openstack-meeting03:14
hongbinyanyanhu: what do you think?03:14
*** itzdilip has joined #openstack-meeting03:14
Wenzhihow if user what to modify the images, like docker commit?03:14
yanyanhuhong, I agree with eliqiao03:14
eliqiaowho will really keep the iamge actually?03:14
yanyanhuthat maybe it is helpful feature03:15
eliqiaoglance or docker registry/03:15
hongbineliqiao: both03:15
WenzhiIf we use glance as image back-end, how do we modify the image?03:15
hongbindocker push to overwrite the image03:15
*** ijw has quit IRC03:15
hongbinsorry zun push03:15
hongbinbasically, we implement a docker pull/push equivalent03:16
yanyanhuhongbin, if it is purely about image management, maybe it is not in zun's scope03:16
eliqiaowho will do the pusing? zun-??03:16
hongbinyanyanhu: agree, zun should not manage the iamge by itself03:16
yanyanhusince IMHO, the images may be prepared before they are consumed by Zun03:16
hongbineliqiao: users03:16
eliqiaoif we do a zun push, that is to say we have a image locally, zun will help to push the image to glance?03:17
hongbinyanyanhu: I see03:17
eliqiaobut we don't have zun-conductor for now.03:17
hongbineliqiao: the workflow is like docker CLI03:17
hongbin1. zun pull busybox03:17
hongbin2. modify the image locally03:18
hongbin3. zun push glance/busybox03:18
hongbin4. zun run -it glance/busybox03:18
*** sudipto has joined #openstack-meeting03:18
*** sudipto_ has joined #openstack-meeting03:18
hongbinthis is similiar to a typical docker behaviour03:18
hongbinand glance is served as a private registry03:19
*** baoli_ has quit IRC03:19
*** vishwanathj is now known as vishwanathj_zzz03:19
Wenzhisounds reasonable03:19
*** baoli has joined #openstack-meeting03:19
hongbinyanyanhu: however, I am open to discuss if it fits into the scope03:20
yanyanhuhongbin, yes. Actually I think Zun push which push image to glance/glare sounds more reasonable for me. But Zun pull doesn't look that necessary I feel03:21
*** sindhu has joined #openstack-meeting03:21
hongbinyanyanhu: I see03:21
eliqiaoyanyanhu: +103:21
*** tonytan_brb has quit IRC03:21
eliqiaozun-driver will do the pull03:21
hongbinyanyanhu: let's me record your comment at the etherpad03:21
yanyanhusince users do have the requirement to generate a glance/glare image based on running container03:21
yanyanhuhongbin, thanks :)03:21
yanyanhubut for pulling image from docker hub to local glance/glare storage, user can rely on glance/glare client to do it (if this operation is supported by glance/glare of course :))03:22
*** _nadya_ has joined #openstack-meeting03:23
hongbinyes, the the flow is like03:23
hongbindocker pull xxx / glance download xxx03:23
*** ub2 has joined #openstack-meeting03:23
hongbinthen, zun push xxxx03:24
*** shaohe_feng has quit IRC03:24
*** ub has quit IRC03:24
*** klkumar has joined #openstack-meeting03:24
hongbinwhich is also fine03:24
yanyanhuyes, so zun is kind of bridge between docker hub and glance03:24
yanyanhufor image operations03:25
hongbinagree03:25
*** shaohe_feng has joined #openstack-meeting03:25
hongbinthen, another question is how to do a commit03:25
hongbinand upload it to glance/docker hub03:25
*** tochi has quit IRC03:26
hongbinmaybe need to implement another operation? like $ zun commit CONTAINER03:26
yanyanhuhongbin, it is possible I think03:26
hongbinok03:26
yanyanhumay also depends on how glance/glare support it I feel03:27
hongbinthen zun commit will download the container to local file system?03:27
eliqiaozun-compute will do the push right?03:27
hongbineliqiao: users do the push03:27
eliqiaoalso does zun commit03:27
hongbineliqiao: zun-compute do the pull03:27
*** _nadya_ has quit IRC03:27
*** iyamahat_ has quit IRC03:27
*** ub has joined #openstack-meeting03:28
eliqiaoI don't get that, if you want to do a commit, then you first need to run that contianer on zun-compute03:28
*** mickeys has quit IRC03:28
hongbineliqiao: for zun commit, I am not sure it should commit to glance or to somewhere else03:28
hongbineliqiao: yes03:28
eliqiaothen user do a commit, zun-compute will commit it, then user do zun push, zun-compute will do the push03:28
*** ub2 has quit IRC03:28
*** vishwanathj_zzz has quit IRC03:29
hongbineliqiao: but push is user's local -> glance03:29
*** vishwanathj_zzz has joined #openstack-meeting03:29
hongbineliqiao: not zun-compute -> glance03:30
hongbineliqiao: maybe zun commit can do it like zun-compute -> glance03:30
*** thorst has joined #openstack-meeting03:30
hongbineliqiao: or do it like zun-compute -> user's local03:31
eliqiaohongbin: think about that a user only have install zun-client ..03:31
hongbinyes03:32
eliqiaozun-client will in charge of pushing image?03:32
hongbinyes03:32
eliqiaok03:32
hongbinhave zun-client depends on dockerpy03:32
hongbinthen it should be able to push03:32
*** esberglu has quit IRC03:33
yanyanhueliqiao, I think hongbin means 'zun push' is a functionality that zun provides for user to 'convert' a 'remote' docker image to 'local' 'glance/glare' image03:33
yanyanhuhongbin, plz correct me if I misunderstand it03:33
yanyanhuthis operation can be provided by zunclient03:33
hongbinyes03:33
hongbinbecause the convertion is not trival03:33
hongbinso do it for users is good03:34
*** shaohe_feng has quit IRC03:34
*** sankarshan has joined #openstack-meeting03:34
yanyanhuhongbin, agree this is very helpful for user. Just ideally, glance/glare can provide it :)03:34
*** ub has quit IRC03:34
*** shaohe_feng has joined #openstack-meeting03:35
*** sindhu has quit IRC03:35
hongbinyanyanhu: agree03:35
*** sindhu has joined #openstack-meeting03:35
hongbinok, will raise this discussion in the ML03:36
hongbinespecially for the pull and commit03:36
eliqiao+103:36
*** thorst has quit IRC03:36
hongbin#action hongbin raise a ML to discuss container image03:36
yanyanhuhongbin, of course, that strongly depends on glance/glare's support03:36
hongbinyanyanhu: but I don't think they will support it in a near future03:37
yanyanhuhongbin, if so, it's good zun can provide this functionality03:37
hongbinyanyanhu: k03:38
yanyanhuwe should provide user at least one option :)03:38
hongbinok, next topic03:38
hongbin#topic Multi-tenancy (Wenzhi Yu)03:38
*** openstack changes topic to "Multi-tenancy (Wenzhi Yu) (Meeting topic: zun)"03:38
hongbin#link https://blueprints.launchpad.net/zun/+spec/support-multi-tenancy03:38
hongbin#link https://etherpad.openstack.org/p/zun-multi-tenancy03:39
hongbinWenzhi: ^^03:39
*** yamamoto has joined #openstack-meeting03:39
Wenzhiyes03:39
Wenzhihttps://review.openstack.org/#/c/357615/03:39
Wenzhiwith this patch now we can scope the containers by tenants03:39
WenzhiIMO that's the whole work we need so far?03:39
*** ub has joined #openstack-meeting03:40
hongbinWenzhi: I saw the patch03:41
*** xinwu has joined #openstack-meeting03:41
hongbinWenzhi: it seems to enable the paste.ini03:41
hongbinWenzhi: but not sure how it relates to multi-tenancy03:41
Wenzhithe container related code in Zun is basically copied from Magnum I think03:41
Wenzhithat means the code has already implemented multi-tenancy03:42
hongbinWenzhi: ok, let's me double check that03:42
Wenzhithe reason containers are not scoped by tenants in Zun is because we did not capture the 'porject_id' or 'user_id' from user requests03:43
hongbinoh, I see03:43
*** vishwanathj_zzz has quit IRC03:44
hongbinthen I guess it is fine now after your patch03:44
*** zzxwill has quit IRC03:44
Wenzhiyes, I already tested manually, now the containers are scoped by tenants in Zun03:44
hongbinawesome03:44
*** shaohe_feng has quit IRC03:44
*** vishwanathj_zzz has joined #openstack-meeting03:44
hongbinWenzhi: then let's close the bp03:44
yanyanhumaye also need multi-tanant support in db layer? not sure whether it has been there in existing db interfaces03:44
*** shaohe_feng has joined #openstack-meeting03:44
Wenzhiyanyanhu: what do you mean by 'multi-tanant support in db layer'?03:45
hongbinyanyanhu: Wenzhi : I think it is already there: https://github.com/openstack/higgins/blob/master/zun/db/sqlalchemy/api.py#L11203:45
yanyanhuhongbin, great03:45
*** yamamoto has quit IRC03:45
*** salv-orlando has joined #openstack-meeting03:45
hongbinsince the code are copied from Magnum, so Magnum alreadys implements in in db layer03:45
*** vishnoianil has quit IRC03:46
Wenzhiyes03:46
yanyanhuWenzhi, if it has been there, we don't need further work here :)03:46
hongbinWenzhi: great job03:46
yanyanhucool03:46
Wenzhithanks :)03:46
*** vishnoianil has joined #openstack-meeting03:46
hongbinok, then this one finish, let's move to the next topic03:47
hongbin#topic Container network03:47
*** openstack changes topic to "Container network (Meeting topic: zun)"03:47
hongbin#link https://blueprints.launchpad.net/zun/+spec/neutron-integration03:47
hongbinI took this one because I have looked into Kuryr and nova-docker in before03:47
*** baoli has quit IRC03:48
*** ljxiash has quit IRC03:48
hongbinHere is what I think, we don't need kury-libnetwork03:48
hongbinmaybe we needs kuryr-lib03:48
hongbinhowever, I suggest to decouple from kuryr for now, and re-visit the dependency after kuryr is mature03:49
*** fnaval has quit IRC03:49
hongbinI plan to port nova-docker implementation to zun as a start03:49
Wenzhisounds like a plan03:50
*** fnaval has joined #openstack-meeting03:50
hongbinthen, switch to kuryr-lib later03:50
hongbinany comment?03:50
hongbinor anything needs to clarify?03:50
*** links has joined #openstack-meeting03:51
hongbinyanyanhu: eliqiao ^^03:51
yanyanhuhi, sorry, just trapped by some other stuff03:52
*** ub has quit IRC03:52
yanyanhusounds good for me03:52
hongbinok03:53
*** vishwanathj_zzz has quit IRC03:53
*** zz_dimtruck is now known as dimtruck03:53
hongbin#topic Open Discussion03:53
*** openstack changes topic to "Open Discussion (Meeting topic: zun)"03:53
*** vishnoianil has quit IRC03:53
*** vishwanathj_zzz has joined #openstack-meeting03:53
*** salv-orlando has quit IRC03:53
hongbinany other topic to discuss?03:54
*** ub has joined #openstack-meeting03:54
hongbinsounds not, then let's wrap up a little earlier03:54
*** shaohe_feng has quit IRC03:54
hongbin#endmeeting03:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"03:55
openstackMeeting ended Tue Aug 30 03:54:59 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)03:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zun/2016/zun.2016-08-30-03.00.html03:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zun/2016/zun.2016-08-30-03.00.txt03:55
openstackLog:            http://eavesdrop.openstack.org/meetings/zun/2016/zun.2016-08-30-03.00.log.html03:55
*** vishwanathj_zzz has quit IRC03:55
*** armax has joined #openstack-meeting03:55
*** vishwanathj_zzz has joined #openstack-meeting03:55
*** xinwu has quit IRC03:55
*** shaohe_feng has joined #openstack-meeting03:57
*** ljxiash has joined #openstack-meeting03:57
*** prateek_ has joined #openstack-meeting03:58
*** ub has quit IRC03:59
*** xinwu has joined #openstack-meeting04:00
*** tochi has joined #openstack-meeting04:01
*** hongbin has quit IRC04:01
*** parora has quit IRC04:01
*** ljxiash has quit IRC04:02
*** numans has joined #openstack-meeting04:03
*** numans has quit IRC04:04
*** numans has joined #openstack-meeting04:04
*** yamamoto has joined #openstack-meeting04:04
*** shaohe_feng has quit IRC04:05
*** shaohe_feng has joined #openstack-meeting04:05
*** ub has joined #openstack-meeting04:06
*** roxanag__ has joined #openstack-meeting04:08
*** jamemcc has quit IRC04:08
*** uxdanielle has joined #openstack-meeting04:08
*** roxanagh_ has quit IRC04:09
*** zzxwill has joined #openstack-meeting04:09
*** amotoki has joined #openstack-meeting04:12
*** xinwu has quit IRC04:13
*** JRobinson__ has quit IRC04:14
*** shaohe_feng has quit IRC04:15
*** shaohe_feng has joined #openstack-meeting04:16
*** liuhanxi has joined #openstack-meeting04:16
*** yamamoto has quit IRC04:18
*** xinwu has joined #openstack-meeting04:22
*** tonytan4ever has joined #openstack-meeting04:22
*** shaohe_feng has quit IRC04:25
*** tochi has quit IRC04:25
*** sindhu has quit IRC04:26
*** shaohe_feng has joined #openstack-meeting04:26
*** sindhu has joined #openstack-meeting04:26
*** tonytan4ever has quit IRC04:26
*** prateek_ has quit IRC04:26
*** yanyanhu has left #openstack-meeting04:31
*** xinwu has quit IRC04:31
*** jrist has quit IRC04:33
*** prateek has joined #openstack-meeting04:34
*** jrist has joined #openstack-meeting04:34
*** sindhu has quit IRC04:34
*** sudipto_ has quit IRC04:34
*** thorst has joined #openstack-meeting04:35
*** sudipto has quit IRC04:35
*** shaohe_feng has quit IRC04:35
*** tochi has joined #openstack-meeting04:36
*** ntpttr- has quit IRC04:36
*** shaohe_feng has joined #openstack-meeting04:37
*** vishwanathj_zzz has quit IRC04:38
*** ozstacker has joined #openstack-meeting04:38
*** vishwanathj_zzz has joined #openstack-meeting04:38
*** iyamahat has joined #openstack-meeting04:40
*** yamamoto has joined #openstack-meeting04:40
*** ntpttr- has joined #openstack-meeting04:40
*** donghao has quit IRC04:40
*** ntpttr- is now known as ntpttr04:41
*** thorst has quit IRC04:41
*** salv-orlando has joined #openstack-meeting04:41
*** shaohe_feng has quit IRC04:43
*** cdub has quit IRC04:43
*** shaohe_feng has joined #openstack-meeting04:44
*** ntpttr has quit IRC04:44
*** ntpttr has joined #openstack-meeting04:45
*** shaohe_feng has quit IRC04:46
*** vishwanathj_zzz has quit IRC04:47
*** shaohe_feng has joined #openstack-meeting04:47
*** vishwanathj_zzz has joined #openstack-meeting04:47
*** shaohe_feng has quit IRC04:49
*** shaohe_feng has joined #openstack-meeting04:49
*** vishwanathj_zzz has quit IRC04:50
*** vishwanathj_zzz has joined #openstack-meeting04:50
*** dimtruck is now known as zz_dimtruck04:53
*** zhurong has quit IRC04:54
*** shaohe_feng has quit IRC04:56
*** shaohe_feng has joined #openstack-meeting04:57
*** ayoung has quit IRC04:58
*** yamamoto has quit IRC05:00
*** anilvenkata has joined #openstack-meeting05:03
*** jdurgin has quit IRC05:03
*** jdurgin has joined #openstack-meeting05:04
*** zzxwill has quit IRC05:05
*** vishwanathj_zzz has quit IRC05:06
*** Sukhdev has joined #openstack-meeting05:06
*** vishwanathj_zzz has joined #openstack-meeting05:07
*** sudipto_ has joined #openstack-meeting05:07
*** sudipto has joined #openstack-meeting05:07
*** zzxwill has joined #openstack-meeting05:08
*** uxdanielle has quit IRC05:09
*** vishwanathj_zzz has quit IRC05:11
*** vishwanathj_zzz has joined #openstack-meeting05:11
*** Sukhdev has quit IRC05:12
*** liamji has joined #openstack-meeting05:13
*** ljxiash has joined #openstack-meeting05:15
*** vishwanathj_zzz has quit IRC05:15
*** vishwanathj_zzz has joined #openstack-meeting05:15
*** lifeless_ is now known as lifeless05:15
*** vishwanathj_zzz has quit IRC05:17
*** vishwanathj_zzz has joined #openstack-meeting05:17
*** unicell has joined #openstack-meeting05:18
*** unicell has quit IRC05:19
*** janki has joined #openstack-meeting05:21
*** itzdilip has quit IRC05:22
*** armax has quit IRC05:22
*** blogan_ is now known as blogan05:24
*** unicell has joined #openstack-meeting05:24
*** fnaval_ has joined #openstack-meeting05:25
*** vishwanathj_zzz has quit IRC05:26
*** vishwanathj_zzz has joined #openstack-meeting05:26
*** ilyashakhat has joined #openstack-meeting05:27
*** fnaval has quit IRC05:29
*** zhurong has joined #openstack-meeting05:30
*** xinwu has joined #openstack-meeting05:31
*** sudswas__ has joined #openstack-meeting05:33
*** Poornima has joined #openstack-meeting05:34
*** sudipto has quit IRC05:35
*** sudipto has joined #openstack-meeting05:35
*** sudipto_ has quit IRC05:35
*** vishwanathj_zzz has quit IRC05:38
*** vishwanathj_zzz has joined #openstack-meeting05:38
*** thorst has joined #openstack-meeting05:39
*** vishwanathj_zzz has quit IRC05:40
*** sridharg has joined #openstack-meeting05:40
*** vishwanathj_zzz has joined #openstack-meeting05:40
*** yamamoto has joined #openstack-meeting05:41
*** bvandenh has quit IRC05:45
*** armax has joined #openstack-meeting05:46
*** thorst has quit IRC05:46
*** sdake has quit IRC05:47
*** sandanar has joined #openstack-meeting05:47
*** xinwu has quit IRC05:48
*** nkrinner_afk is now known as nkrinner05:48
*** fnaval has joined #openstack-meeting05:49
*** sdake has joined #openstack-meeting05:50
*** xinwu has joined #openstack-meeting05:50
*** fnaval_ has quit IRC05:53
*** su_zhang has joined #openstack-meeting05:56
*** yuval has joined #openstack-meeting05:56
loquacitiesalright, who's here for the install guide meeting?06:00
*** ebalduf has quit IRC06:00
strigazio/06:02
loquacitiesstrigazi: hi :)06:03
loquacitiesi was thinking no one was here ;)06:03
strigazilet's wait a little more06:04
loquacitiesok06:05
*** manikanta_tadi has joined #openstack-meeting06:05
*** Sukhdev has joined #openstack-meeting06:06
loquacitiesok, i think this party ended before it began :(06:07
loquacitiesstrigazi: thanks for coming, anyway06:07
strigaziJust a question06:07
strigaziabout testing06:07
*** andreas_s has joined #openstack-meeting06:07
loquacitiessure06:07
*** dguitarbite has joined #openstack-meeting06:08
strigaziWhat environment do you use? Two vm with two fake nics?06:08
*** salv-orl_ has joined #openstack-meeting06:08
loquacitiesthere's a couple of scenarios in the install guide06:08
strigaziThe install guide assumes two nods06:08
dguitarbiteHello06:08
loquacitiesoh, dguitarbite hi :)06:08
loquacitiesshould we start the recording?06:08
dguitarbite:)06:08
strigaziok06:09
loquacitiesi don't have anything formal to go through, really, but people might want to read the scrollback06:09
loquacities#startmeeting docinstallteam06:09
openstackMeeting started Tue Aug 30 06:09:26 2016 UTC and is due to finish in 60 minutes.  The chair is loquacities. Information about MeetBot at http://wiki.debian.org/MeetBot.06:09
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.06:09
*** openstack changes topic to " (Meeting topic: docinstallteam)"06:09
openstackThe meeting name has been set to 'docinstallteam'06:09
loquacities#topic Testing: https://wiki.openstack.org/wiki/Documentation/NewtonDocTesting06:09
*** openstack changes topic to "Testing: https://wiki.openstack.org/wiki/Documentation/NewtonDocTesting (Meeting topic: docinstallteam)"06:09
loquacities#link Debian: http://lists.openstack.org/pipermail/openstack-docs/2016-August/009006.html06:09
loquacities#link Ubuntu: http://lists.openstack.org/pipermail/openstack-docs/2016-August/009008.html06:09
loquacitiesthere we go06:10
*** salv-orlando has quit IRC06:11
loquacitiesstrigazi: so, to answer the question: just step through the install guide here: http://docs.openstack.org/project-install-guide/draft/06:11
loquacitiesso yes, two nodes06:11
strigaziyes, but in practice you fake them right?06:11
loquacitiesyeah, absolutely06:11
*** salv-orlando has joined #openstack-meeting06:12
strigaziAny other  advice on that?06:12
loquacitiesi'm not an expert, i'm sure i'll get better at this as we go on ;)06:13
*** su_zhang has quit IRC06:13
*** JRobinson__ has joined #openstack-meeting06:13
*** bmoss has joined #openstack-meeting06:13
bmosshowdy06:13
*** etoews has quit IRC06:13
loquacitiesi've just asked brian to join, he's had more hands on experience than me :)06:13
*** su_zhang has joined #openstack-meeting06:14
strigaziSo far I was testing magnum against devstack06:14
loquacitiesbmoss: strigazi was just looking for advice on testing06:14
strigazihi bmoss06:14
bmosshi :)06:14
*** ilyashakhat has quit IRC06:14
*** dguitarbite has quit IRC06:15
*** etoews has joined #openstack-meeting06:15
strigaziTo have the environment rewuired by the install guide you fake two nodes and fake two nics. Do you have any advice before starting?06:15
*** moizarif has joined #openstack-meeting06:16
bmosswell, if you're installing your nodes on vms, it is probably a good idea to have a network services layer to firewall your nodes06:17
*** salv-orl_ has quit IRC06:17
*** moizarif_ has quit IRC06:17
*** dguitarbite has joined #openstack-meeting06:17
*** moizarif_ has joined #openstack-meeting06:17
*** zzxwill has quit IRC06:17
dguitarbiteloquacities: ping06:17
*** salv-orlando has quit IRC06:17
loquacitiesyep?06:18
*** su_zhang has quit IRC06:18
dguitarbiteOhh, I just did not see any activity.06:18
loquacitiesyeah, i was letting strigazi and bmoss discuss :)06:18
dguitarbite:)06:18
*** rcernin has joined #openstack-meeting06:19
bmossstrigazi, so a network services layer is a good idea. Also, type very carefully. ;) There is a lot of config and small mistakes cause big headaches.06:19
*** _nadya_ has joined #openstack-meeting06:19
strigazibmoss, I'll give it a go if I have any specific issue I'll ping on irc06:20
loquacitiescool, ok, dguitarbite did you have an update on the parser?06:20
bmossto be honest, there probably isn't much more to say. The Install Guides are pretty good at taking the reader through the steps. And if something isn't clear, then it is probably a bug with the guide. Well, unless it has missed something new from openstack.06:20
*** ijw has joined #openstack-meeting06:20
*** zzxwill has joined #openstack-meeting06:21
dguitarbiteYes, I do have an update :D. It is a couple of hours more work away from being ready to be used by us.06:21
bmossstrigazi, good luck, and thanks for testing! Fresh eyes are the best for catching problems.06:21
loquacitieswoohoo!06:21
loquacities#topic install guide testing parser06:21
*** openstack changes topic to "install guide testing parser (Meeting topic: docinstallteam)"06:21
*** moizarif has quit IRC06:21
dguitarbiteI have a meeting with Andreas this Thrusday where I would present him the running version of the parser and discuss how to move ahead.06:21
*** ilyashakhat has joined #openstack-meeting06:21
loquacitiescool06:21
loquacitiesi'm looking forward to seeing it in action!06:21
strigaziwe'll update in this release?06:22
dguitarbiteloquacities: There are some changes to the install guides from my side though.06:22
loquacitiessuch as?06:22
*** amotoki has quit IRC06:22
*** xinwu has quit IRC06:22
dguitarbite#link https://github.com/dguitarbite/openstack-manuals/commit/dd14956679969856a02201fe44098c3a2ef6eebf06:22
dguitarbiteloquacities: These small syntax changes should not impact install guides generated HTML pages. They just are for reducing the complexity otherwise writing this parser would be a full time job for a team.06:23
loquacitiesright, so they're non-printing?06:23
loquacitiesah, yep, i see06:24
dguitarbiteloquacities: Nope, but they are critical for the parser to function.06:24
dguitarbiteThere should be few more minor changes to the syntax, I have 1-2 minor challenges to match.06:24
loquacitiesok06:25
dguitarbite*challenges to face.06:25
loquacitiesso how does the parser show that it's passed/failed?06:25
*** ijw has quit IRC06:25
dguitarbiteSo, I will be writing custom exception class which invokes/throws exceptions at different points. This should allow us to add some strings to give failure indications.06:26
loquacitiesright06:26
*** pcaruana has joined #openstack-meeting06:26
dguitarbitehttps://github.com/dguitarbite/rst2bash/blob/master/parser.py#L27106:26
dguitarbiteSomething on a similar line.06:27
loquacitiesright, makes sense06:27
loquacitiescool! i'm really excited about this :)06:27
dguitarbiteThere is another change that I would like to introduce. To create a variables file at the start of the install guides.06:27
dguitarbiteMe too :).06:27
*** AJaeger has joined #openstack-meeting06:28
*** armax has quit IRC06:28
AJaegersorry for coming late to the party06:28
dguitarbiteThis variables file should allow us to keep things flexible and use the variables like $keystone_user_password etc.06:28
dguitarbiteAJaeger: hi06:28
dguitarbiteloquacities: Something like this but more user friendly: http://git.openstack.org/cgit/openstack/training-labs/tree/labs/osbash/config/credentials06:30
loquacitiesoh, that's clever06:30
dguitarbiteSo for the users, they can copy paste this at the start of the install guides or just use their values when they see $nova_admin_password.06:30
loquacitiesyeah, like a kickstart06:31
dguitarbiteloquacities: Yes.06:31
loquacitiesvery cool :)06:31
dguitarbiteI want to finish it soon :).06:31
AJaegeragreed06:31
AJaegerplease do ;)06:31
loquacities+1 :)06:31
dguitarbiteAJaeger: Haha, yes.06:31
loquacitiesok, any other business?06:32
loquacities#topic other business06:32
*** openstack changes topic to "other business (Meeting topic: docinstallteam)"06:32
*** bvandenh has joined #openstack-meeting06:32
dguitarbiteloquacities: I cannot find the wiki page we use to track the progress of install-guides.06:32
loquacitieshttps://wiki.openstack.org/wiki/Documentation/NewtonDocTesting06:32
dguitarbiteloquacities: And also for working on SLE/openSUSE, I would like to start fixing it from next week.06:33
loquacitiesthat'd be great :)06:33
loquacitiesi'm hoping to have everything (well, as much as possible) tested by the end of september06:33
dguitarbiteBut I am not yet sure if the packages for any of these distros are already shipping Newton.06:33
loquacitiesthat's a week before release day06:33
loquacitiesi haven't got an update on suse packages, yet06:33
dguitarbiteUpdate as in reply to your email on docs ML?06:34
AJaegerdguitarbite: our SUSE packages are ready, aren't they?06:34
loquacitiesyeah06:34
dguitarbite AJaeger Yes, we have it as master branch for sure.06:34
loquacitiesAJaeger: if that's true, can you post something to the ML?06:35
dguitarbiteNot sure about the other distros though.06:35
loquacitiesi have b2 repos for debian and ubuntu06:35
AJaegerdguitarbite: can you send the email with details, please? You're closer to that06:35
loquacitiesnothing for rhel yet06:35
dguitarbiteAJaeger: Yes, for sure. Shall I send it over the Docs ML itself?06:35
*** Na3iL has joined #openstack-meeting06:35
loquacitiesyou can reply to my email, subject "Install Guide Testing in 3 ... 2 ..."06:36
loquacitiesthat way it's all together06:36
*** lpetrut has joined #openstack-meeting06:36
dguitarbiteloquacities: Done.06:36
loquacitiesyay!06:36
loquacitiesthanks :)06:36
loquacitiesok, thanks for a great meeting everyone (despite the slow start!)06:36
strigazibye06:37
dguitarbitebye06:37
loquacitiescya o/06:37
loquacities#endmeeting06:37
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"06:37
AJaegerbye06:37
openstackMeeting ended Tue Aug 30 06:37:40 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)06:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docinstallteam/2016/docinstallteam.2016-08-30-06.09.html06:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docinstallteam/2016/docinstallteam.2016-08-30-06.09.txt06:37
openstackLog:            http://eavesdrop.openstack.org/meetings/docinstallteam/2016/docinstallteam.2016-08-30-06.09.log.html06:37
*** ilyashakhat has quit IRC06:38
*** AJaeger has left #openstack-meeting06:39
*** dguitarbite has left #openstack-meeting06:39
*** vishnoianil has joined #openstack-meeting06:44
*** sdake has quit IRC06:44
*** _nadya_ has quit IRC06:44
*** thorst has joined #openstack-meeting06:44
*** xinwu has joined #openstack-meeting06:46
*** amotoki has joined #openstack-meeting06:46
*** zaneb has quit IRC06:48
*** ilyashakhat has joined #openstack-meeting06:48
*** sudipto has quit IRC06:48
*** sudswas__ has quit IRC06:48
*** zaneb has joined #openstack-meeting06:48
*** roxanag__ has quit IRC06:50
*** rasca has joined #openstack-meeting06:50
*** ilyashakhat has quit IRC06:51
*** Sukhdev has quit IRC06:51
*** thorst has quit IRC06:51
*** roxanagh_ has joined #openstack-meeting06:51
*** hua has quit IRC06:52
*** JRobinson__ has quit IRC06:56
*** amotoki has quit IRC06:56
*** roxanagh_ has quit IRC06:56
*** hua has joined #openstack-meeting06:58
*** sudswas__ has joined #openstack-meeting07:00
*** sudipto has joined #openstack-meeting07:00
*** jckasper has joined #openstack-meeting07:02
*** hua has quit IRC07:03
*** amotoki has joined #openstack-meeting07:04
*** ozstacker has quit IRC07:04
*** jckasper has quit IRC07:06
*** tesseract- has joined #openstack-meeting07:07
*** hua has joined #openstack-meeting07:07
*** hua has quit IRC07:07
*** hua has joined #openstack-meeting07:08
*** amotoki_ has joined #openstack-meeting07:08
*** sheel has joined #openstack-meeting07:08
*** amotoki has quit IRC07:09
*** hua has quit IRC07:10
*** hua has joined #openstack-meeting07:10
*** hua has quit IRC07:11
*** Poornima has quit IRC07:11
*** hua has joined #openstack-meeting07:12
*** jlanoux has joined #openstack-meeting07:13
*** fredrik has joined #openstack-meeting07:13
*** Akis_ has joined #openstack-meeting07:15
*** toscalix has joined #openstack-meeting07:17
*** jlanoux has quit IRC07:18
*** Akis__ has quit IRC07:18
*** jlanoux has joined #openstack-meeting07:19
*** kaminohana has quit IRC07:20
*** lpetrut has quit IRC07:21
*** hua has quit IRC07:21
*** adiantum has joined #openstack-meeting07:25
*** zhhuabj_ has joined #openstack-meeting07:26
*** jamespage has joined #openstack-meeting07:27
*** xinwu has quit IRC07:28
*** matrohon has joined #openstack-meeting07:33
*** anilvenkata has quit IRC07:33
*** reed has quit IRC07:33
*** reed_ is now known as reed07:33
*** hashar has joined #openstack-meeting07:36
*** akuznetsov has joined #openstack-meeting07:37
*** bvandenh has quit IRC07:38
*** bvandenh has joined #openstack-meeting07:38
*** fzdarsky|afk has joined #openstack-meeting07:41
*** nmagnezi has joined #openstack-meeting07:42
*** fzdarsky|afk is now known as fzdarsky07:44
*** amotoki_ has quit IRC07:47
*** amotoki has joined #openstack-meeting07:47
*** thorst has joined #openstack-meeting07:49
*** kaisers1 has quit IRC07:50
*** matthewbodkin has joined #openstack-meeting07:51
*** kaisers has quit IRC07:52
*** roxanagh_ has joined #openstack-meeting07:52
*** zzxwill has quit IRC07:52
*** kaisers has joined #openstack-meeting07:53
*** kaisers1 has joined #openstack-meeting07:53
*** bmoss has quit IRC07:54
*** zzxwill has joined #openstack-meeting07:55
*** roxanagh_ has quit IRC07:56
*** thorst has quit IRC07:57
*** mickeys has joined #openstack-meeting07:59
*** dmorita has quit IRC08:00
*** shashank_hegde has quit IRC08:01
*** toscalix has quit IRC08:02
*** shashank_hegde has joined #openstack-meeting08:02
*** r-mibu has quit IRC08:02
*** r-mibu has joined #openstack-meeting08:03
*** dmorita has joined #openstack-meeting08:03
*** toscalix has joined #openstack-meeting08:03
*** mickeys has quit IRC08:04
*** yassine has joined #openstack-meeting08:05
*** yassine is now known as Guest1760908:06
*** Guest17609 is now known as yassou08:06
*** cdub has joined #openstack-meeting08:08
*** dmorita has quit IRC08:08
*** rossella_s has joined #openstack-meeting08:09
*** bvandenh has quit IRC08:12
*** shashank_hegde has quit IRC08:14
*** toscalix_ has joined #openstack-meeting08:14
*** shashank_hegde has joined #openstack-meeting08:14
*** toscalix has quit IRC08:14
*** toscalix_ has quit IRC08:18
*** shashank_hegde has quit IRC08:19
*** toscalix_ has joined #openstack-meeting08:19
*** tonytan4ever has joined #openstack-meeting08:23
*** tonytan4ever has quit IRC08:28
*** mgershen has left #openstack-meeting08:30
*** zhhuabj_ has quit IRC08:32
*** tricircle has joined #openstack-meeting08:33
*** cdub has quit IRC08:35
*** electrofelix has joined #openstack-meeting08:35
*** RuiChen has joined #openstack-meeting08:38
*** hichihara has joined #openstack-meeting08:39
*** markd_ has joined #openstack-meeting08:40
*** mikelk has joined #openstack-meeting08:41
*** lennyb has quit IRC08:42
*** cdub has joined #openstack-meeting08:42
*** zhhuabj_ has joined #openstack-meeting08:44
*** asettle has joined #openstack-meeting08:46
*** ricolin has joined #openstack-meeting08:47
*** manikanta_tadi has quit IRC08:48
*** zhonghua has joined #openstack-meeting08:49
*** bvandenh has joined #openstack-meeting08:55
*** thorst has joined #openstack-meeting08:56
*** xiangxinyong456 has joined #openstack-meeting08:57
*** saggi has joined #openstack-meeting08:57
*** Leon_Wang has joined #openstack-meeting08:58
saggiKarbor team! Rise from your grave!09:00
saggi#startmeeting karbor09:00
openstackMeeting started Tue Aug 30 09:00:20 2016 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
xiangxinyong456hello09:00
*** links has quit IRC09:00
yuvalhey09:00
Leon_Wanghello09:00
*** zhonghua-lee has joined #openstack-meeting09:01
saggiAre we waiting for anyone?09:01
zhonghua-leehi09:01
saggiI haven't seen yinwei in meetings for a while09:01
*** zhangshuai has joined #openstack-meeting09:01
*** thorst has quit IRC09:02
*** manikanta_tadi has joined #openstack-meeting09:02
saggiOK09:02
saggi#topic Delete 'crontab' time format for time trigger, and support RFC2445 (zengchen)09:03
*** openstack changes topic to "Delete 'crontab' time format for time trigger, and support RFC2445 (zengchen) (Meeting topic: karbor)"09:03
saggizengchen is not here.09:03
yuvalpinged him in channel09:03
*** zengchen has joined #openstack-meeting09:03
*** zzxwill has quit IRC09:03
zengchensorry i am late09:03
saggiWhat about $topic?09:04
*** jlanoux has quit IRC09:05
zengchendelete crontab time format and support rfc2445 only.09:05
*** dmorita has joined #openstack-meeting09:05
saggiwhy remove the existing one. Why not have both?09:05
saggizengchen ?09:05
zengchenfrom the point of user, he don't care use which format to describe the time.09:05
*** chenying__ has joined #openstack-meeting09:06
*** lpetrut has joined #openstack-meeting09:06
zengchenand from the point of horizon, it use only one time format.09:06
chenying__hi09:06
*** ccstorage2016 has joined #openstack-meeting09:06
zhonghua-leezengchen: can I say crontabl is part of RFC2445?09:06
*** zhhuabj_ has quit IRC09:06
*** zhangshuai_ has joined #openstack-meeting09:07
zengchenzhonghua-lee:RFC2445 is enough, and more appropriate than crontab.09:07
zhonghua-leezengchen: so, could you please simplly explain the difference "crontab" and RFC 2445, I think some guys confuse this09:08
zengchenzhuanghua-lee:ok09:08
zhonghua-leezengchen: thanks09:09
*** zhangshuai___ has joined #openstack-meeting09:09
chenying__delete crontab. I think it is ok.09:10
zengchenIMO, crontab can be used in simple use cases, and can not describe more complex time than rfc2445.09:10
*** dmorita has quit IRC09:10
*** zhangshuai has quit IRC09:10
saggixiangxinyong456: What about UI for this ?\09:10
xiangxinyong456if crontab is deleted,I guess we need to do some work in horizon09:11
zengchenxiangxinyong456:whatever use rfc2445 or crontab or others, horizon should choose one from them.09:12
*** zhangshuai_ has quit IRC09:12
xiangxinyong456yeah we have already use crontab.09:12
xiangxinyong456why not keep the crontab?09:13
zengchenxiangxinyong456:if so, we would better choose an appropriate one.09:13
zhonghua-leexiangxinyong456: can UI support both of them?09:13
xiangxinyong456zhonghua-lee: it is not neccerray09:13
saggiIt's just a metter of having a format combo box09:13
*** sankarshan is now known as sankarshan_away09:13
yuvalIMO we should keep support for crontab for now. Later we can decide to change the UI for iCal and maybe remove crontab09:14
chenying__chenzeng  think crontab format  is  port of rfc2245 time  format.09:14
chenying__part09:14
xiangxinyong456but the user does not care whether we use crontab or rfc09:14
saggixiangxinyong456: They have different features09:15
xiangxinyong456yeah09:15
zhonghua-leexiangxinyong456: if users do not care, why to change the UI?09:15
zengchenchenying__:I don't know whether crontab is part of rfc, I think if we want to support more complex time format, it better to use rfc.09:15
saggiSo they need different UIs for the different limitations\features09:15
*** shashank_hegde has joined #openstack-meeting09:15
*** cdub has quit IRC09:16
xiangxinyong456but we should users evevy day,every week, like this09:16
*** links has joined #openstack-meeting09:16
xiangxinyong456the ui is the same09:16
saggizengchen: We are not arguing with that. But since we have the option to specify time format we can have both for now. We just need to make sure we have a proper UI for both.09:16
xiangxinyong456but we need to do some transform between ui and time format09:16
xiangxinyong456the ui is same09:17
zengchensaggi:but i think we don't need to add a box for user to choose time format, they don't care.09:17
xiangxinyong456zengchen: +109:17
saggizengchen: I understand09:17
saggiOK, than just make sure the UI moves to the new format as well.09:18
xiangxinyong456yeah09:18
zengchensaggi:at present, zhangshuai has submitted a patch to support rfc2445, so the last work is about UI.09:19
saggigreat09:19
*** jlanoux has joined #openstack-meeting09:20
zhangshuai___https://review.openstack.org/#/c/35971109:20
zengchensaggi:so we change to rfc some time later?09:20
xiangxinyong456<yuval> IMO we should keep support for crontab for now. Later we can decide to change the UI for iCal and maybe remove crontab09:20
saggizengchen: When the UI changes09:20
xiangxinyong456i agree yuval09:20
zengchensaggi & xiangxinyong456:ok09:20
zhangshuai___+109:21
*** ccstorage2016 has quit IRC09:21
xiangxinyong456if the rfc is stable, we could move into it in the ui09:21
saggiOK, than we have both for now and try and migrate the default to be rfc224509:21
xiangxinyong456no problem09:22
zengchensaggi:great.09:22
saggi#topic Rename window September 2nd (yuvalbr)09:22
*** openstack changes topic to "Rename window September 2nd (yuvalbr) (Meeting topic: karbor)"09:22
*** ivc_ has joined #openstack-meeting09:22
yuvalWell, infra team has designated September 2nd for the rename window09:22
yuvalit means a downtime for gerrit09:22
yuvalafter that, smaug repositories will be renamed to karbor09:23
*** _nadya_ has joined #openstack-meeting09:23
saggiWe need to be ready with patches to commit so that after the switch we can immediately fix all the paths and make sure everything still works.09:23
xiangxinyong456good news09:23
yuvalthe rename window happens on Friday09:24
yuvalalso, all our communications move to #openstack-karbor09:25
xiangxinyong456ok09:25
zhangshuai___ok09:25
yuvalthat's it09:26
zengchenyuval:all patches should be merged before that.09:26
yuvalzengchen: which patches?09:27
zengchennot merge now09:27
yuvalzengchen: what?09:27
*** _nadya_ has quit IRC09:28
*** jlanoux_ has joined #openstack-meeting09:28
*** vishnoianil has quit IRC09:29
*** ccstorage2016 has joined #openstack-meeting09:29
zengchenyuval:for example, the patches are reviewing now should be merged before that time.09:29
*** nkrinner has quit IRC09:29
*** _nadya_ has joined #openstack-meeting09:30
yuvalzengchen: the rename shouldn't affect patches pending review09:30
saggi They will move to the new repo09:30
zengchenyuval:ok09:30
*** ccstorage2016 has quit IRC09:30
saggiThat whole point of the downtime is to migrate all of the information09:31
*** jlanoux has quit IRC09:31
zengchensaggi:so we should spend more time to review patches, right?09:31
saggizengchen: You should always do that :)09:32
zengchensaggi:ok, understand.09:32
yuvalzengchen: anything specific?09:32
zengchenyuval:i have several patches pending review, so i have a little worry.09:32
yuvalzengchen: I see most of them had a new version in the latest day. are they stable now?09:33
*** lpetrut1 has joined #openstack-meeting09:34
*** lpetrut has quit IRC09:34
*** lpetrut1 is now known as lpetrut09:34
zengchenyuval: most of them is stable, i am trying to submit a patch about updating scheduled operation.09:35
yuvalzengchen: if something is not stable, mark with workflow -1, so we'll know to wait with the review09:35
*** nkrinner has joined #openstack-meeting09:36
zengchenyuval:understand, i will do it. thank you.09:36
*** ljxiash has quit IRC09:36
*** ljxiash has joined #openstack-meeting09:37
saggiOK09:37
saggi#topic open discussion09:37
*** openstack changes topic to "open discussion (Meeting topic: karbor)"09:37
saggiAnything else?09:37
saggiJust be ready to be on call on Friday in case something goes wrong and the infra guys needs us09:39
*** apetrich has joined #openstack-meeting09:39
Leon_Wanghi,i''m a new guy and want to be a contributor,can anyone give some tips on it?09:40
saggiLeon_Wang: Sure09:40
yuvalLeon_Wang: welcome! :)09:40
Leon_Wangsaggi:thanks09:40
saggiWhat area do you want to contribute to09:40
zengchenLeon_Wang:welcome.09:40
xiangxinyong456welcome leon09:40
*** roxanagh_ has joined #openstack-meeting09:40
chenying__welcome09:40
Leon_Wangsaggi:karbor,of course:)09:41
Leon_Wangeveryone thank09:41
*** ljxiash has quit IRC09:41
zengchenLeon_Wang:maybe you can see the wiki first. if you have any problem. you can ask in our chanel.09:42
Leon_Wangnow i'm learning to know something about code review09:42
Leon_Wangzengchen:yeah,working on it09:43
*** cdub has joined #openstack-meeting09:43
*** lennyb has joined #openstack-meeting09:43
zengchenLeon_Wang:good. then you can read our codes. karbor have 3 componets, you can choose one to see.09:44
Leon_Wangis it nessary for me to get familiar with the concrete code?09:45
saggiLeon_Wang: What do you want to do? Is there any feature you need or bug you want to fix?09:45
*** roxanagh_ has quit IRC09:45
Leon_Wangsaggi:right now i think i only can do code review09:46
*** e0ne has joined #openstack-meeting09:47
saggiLeon_Wang: Go for it!09:47
Leon_Wangsaggi:but i want to fix bugs or even some feature later09:47
saggiSure09:47
saggiWe are all in #openstack-smaug or #openstack-karbor if you have any questions09:47
saggiThanks everyone09:47
saggi#endmeeting09:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:47
openstackMeeting ended Tue Aug 30 09:47:58 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/karbor/2016/karbor.2016-08-30-09.00.html09:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/karbor/2016/karbor.2016-08-30-09.00.txt09:48
openstackLog:            http://eavesdrop.openstack.org/meetings/karbor/2016/karbor.2016-08-30-09.00.log.html09:48
Leon_Wangsaggi:ok,thanks alot09:48
*** yamamoto has quit IRC09:48
*** xiangxinyong456 has quit IRC09:49
*** RuiChen has quit IRC09:49
*** Leon_Wang has left #openstack-meeting09:50
*** tricircle has quit IRC09:51
*** ronghui has quit IRC09:52
*** hichihara has quit IRC09:53
*** adiantum has quit IRC09:55
*** ub has quit IRC09:55
*** adiantum has joined #openstack-meeting09:56
*** zhonghua has quit IRC09:58
*** zhangshuai___ has quit IRC09:58
*** thorst has joined #openstack-meeting09:58
*** ihrachys has joined #openstack-meeting10:00
*** liuyulong is now known as yulong|away10:00
*** jlanoux has joined #openstack-meeting10:00
*** ub has joined #openstack-meeting10:01
*** zzxwill has joined #openstack-meeting10:03
*** zhurong has quit IRC10:03
*** jlanoux_ has quit IRC10:03
*** amotoki_ has joined #openstack-meeting10:03
*** shu-mutou is now known as shu-mutou-AFK10:04
*** ronghui has joined #openstack-meeting10:04
*** thorst has quit IRC10:05
*** dmorita has joined #openstack-meeting10:06
*** ricolin has quit IRC10:07
*** amotoki has quit IRC10:07
*** chenying__ has quit IRC10:08
*** zhhuabj_ has joined #openstack-meeting10:10
*** dmorita has quit IRC10:11
*** sambetts|afk is now known as sambeets10:11
*** sambeets is now known as sambetts10:11
*** ub2 has joined #openstack-meeting10:16
*** ub has quit IRC10:17
*** iyamahat has quit IRC10:21
*** sridharg has quit IRC10:22
*** amotoki has joined #openstack-meeting10:23
*** tonytan4ever has joined #openstack-meeting10:24
*** amotoki_ has quit IRC10:25
*** hichihara has joined #openstack-meeting10:26
*** salv-orlando has joined #openstack-meeting10:27
*** apetrich has quit IRC10:28
*** tonytan4ever has quit IRC10:28
*** dfflanders has quit IRC10:30
*** ntpttr has quit IRC10:30
*** amotoki_ has joined #openstack-meeting10:33
*** ntpttr has joined #openstack-meeting10:35
*** amotoki has quit IRC10:36
*** apetrich has joined #openstack-meeting10:37
*** lbrune has joined #openstack-meeting10:38
*** lbrune has left #openstack-meeting10:42
*** yamamoto has joined #openstack-meeting10:42
*** ub2 has quit IRC10:43
*** rossella_s has quit IRC10:44
*** sridharg has joined #openstack-meeting10:48
*** salv-orl_ has joined #openstack-meeting10:52
*** tochi has quit IRC10:52
*** sdague has joined #openstack-meeting10:53
*** salv-orl_ has quit IRC10:54
*** salv-orlando has quit IRC10:56
*** sridharg has quit IRC10:56
*** sshnaidm|afk is now known as sshnaidm10:56
*** sridharg has joined #openstack-meeting10:57
*** dkehn_ has quit IRC10:57
*** yamamoto_ has joined #openstack-meeting10:59
*** yamamoto has quit IRC11:02
*** fzdarsky is now known as fzdarsky|lunch11:03
*** jckasper has joined #openstack-meeting11:03
*** thorst has joined #openstack-meeting11:03
*** amakarov_away is now known as amakarov11:05
*** epico has quit IRC11:06
*** hparekh_ has joined #openstack-meeting11:08
*** jckasper has quit IRC11:08
*** hparekh_ has quit IRC11:08
*** yamamoto_ has quit IRC11:08
*** dkehn_ has joined #openstack-meeting11:10
*** wznoinsk has quit IRC11:10
*** adisky has joined #openstack-meeting11:10
*** thorst has quit IRC11:11
*** hoangcx has joined #openstack-meeting11:11
*** apetrich has quit IRC11:11
*** rtheis has joined #openstack-meeting11:12
*** hoangcx2 has joined #openstack-meeting11:15
*** yamamoto has joined #openstack-meeting11:16
*** yamamoto has quit IRC11:17
*** ub has joined #openstack-meeting11:17
*** hoangcx has quit IRC11:17
*** dmorita has joined #openstack-meeting11:22
*** ub2 has joined #openstack-meeting11:23
*** ub has quit IRC11:25
*** apetrich has joined #openstack-meeting11:25
*** banix has joined #openstack-meeting11:26
*** dmorita has quit IRC11:27
*** wznoinsk has joined #openstack-meeting11:28
*** roxanagh_ has joined #openstack-meeting11:29
*** yamamoto has joined #openstack-meeting11:29
*** banix has quit IRC11:29
*** banix has joined #openstack-meeting11:30
*** sudipto has quit IRC11:32
*** sudswas__ has quit IRC11:32
*** yamamoto has quit IRC11:33
*** roxanagh_ has quit IRC11:33
*** amotoki_ has quit IRC11:33
*** asettle has quit IRC11:35
*** asettle has joined #openstack-meeting11:36
*** amotoki has joined #openstack-meeting11:36
*** vishnoianil has joined #openstack-meeting11:37
*** thorst has joined #openstack-meeting11:38
*** thorst_ has joined #openstack-meeting11:39
*** banix has quit IRC11:39
*** maeca1 has joined #openstack-meeting11:40
*** Wenzhi has quit IRC11:41
*** liamji has quit IRC11:42
*** thorst has quit IRC11:42
*** tpsilva has joined #openstack-meeting11:48
*** zzxwill has quit IRC11:50
*** asettle has quit IRC11:51
*** cdub has quit IRC11:54
*** rfolco has joined #openstack-meeting11:57
*** efried has joined #openstack-meeting11:58
*** pradk has joined #openstack-meeting12:02
*** sindhu has joined #openstack-meeting12:04
*** sandanar has quit IRC12:04
*** fredrik has quit IRC12:08
*** sindhu has quit IRC12:08
*** vladikr has joined #openstack-meeting12:09
*** esumerfd has joined #openstack-meeting12:10
*** akuznetsov has quit IRC12:11
*** akuznetsov has joined #openstack-meeting12:11
*** tonytan4ever has joined #openstack-meeting12:13
*** zhurong has joined #openstack-meeting12:15
*** clenimar has quit IRC12:15
*** bobh has joined #openstack-meeting12:15
*** akuznetsov has quit IRC12:16
*** banix has joined #openstack-meeting12:17
*** sarob has joined #openstack-meeting12:17
*** ub2 has quit IRC12:18
*** fredrik has joined #openstack-meeting12:18
*** rossella_s has joined #openstack-meeting12:20
*** fredrik has quit IRC12:21
*** fredrik has joined #openstack-meeting12:21
*** sarob has quit IRC12:22
*** yamamoto has joined #openstack-meeting12:22
*** dprince has joined #openstack-meeting12:26
*** banix has quit IRC12:27
*** fredrik has quit IRC12:28
*** fredrik has joined #openstack-meeting12:29
*** liuyulong has joined #openstack-meeting12:29
*** su_zhang has joined #openstack-meeting12:31
*** dmorita has joined #openstack-meeting12:34
*** bobh has quit IRC12:35
*** dmorita has quit IRC12:39
*** rooneym has joined #openstack-meeting12:41
*** sudipto has joined #openstack-meeting12:42
*** sudswas__ has joined #openstack-meeting12:42
*** baoli has joined #openstack-meeting12:44
*** annegentle has joined #openstack-meeting12:48
*** fzdarsky|lunch is now known as fzdarsky|afk12:48
*** cdelatte has joined #openstack-meeting12:49
*** vhoward has joined #openstack-meeting12:49
*** rbak has joined #openstack-meeting12:51
*** fzdarsky|afk is now known as fzdarsky12:52
*** manikanta_tadi has quit IRC12:52
*** markvoelker has joined #openstack-meeting12:52
*** rbak has quit IRC12:53
*** esberglu has joined #openstack-meeting12:53
*** claudiub has joined #openstack-meeting12:54
*** dtrainor has joined #openstack-meeting12:55
*** yanyanhu has joined #openstack-meeting12:58
*** asselin_ has quit IRC12:59
Qiming#startmeeting senlin12:59
openstackMeeting started Tue Aug 30 12:59:57 2016 UTC and is due to finish in 60 minutes.  The chair is Qiming. Information about MeetBot at http://wiki.debian.org/MeetBot.12:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:59
*** openstack changes topic to " (Meeting topic: senlin)"13:00
openstackThe meeting name has been set to 'senlin'13:00
*** clenimar has joined #openstack-meeting13:00
Qimingevening13:00
yanyanhuhi13:01
*** elynn has joined #openstack-meeting13:01
Qiminghi, wait a few minutes and see if anyone else is joining13:01
yanyanhuok13:01
*** guoshan has joined #openstack-meeting13:02
*** qwebirc78218 has joined #openstack-meeting13:02
*** guoshan has quit IRC13:02
*** xyang1 has joined #openstack-meeting13:02
*** gabriel-bezerra has quit IRC13:02
elynno/13:03
yanyanhuhi, elynn13:03
Qiminghi, elynn and guoshan13:03
Qimingnot sure if others are joining13:03
Qiminglet's get started13:03
Qiming#topic newton work items13:03
qwebirc78218hello13:03
*** openstack changes topic to "newton work items (Meeting topic: senlin)"13:03
*** guoshan has joined #openstack-meeting13:03
*** guoshan has quit IRC13:03
Qiminghi, qwebirc7821813:03
yanyanhuhi, qwebirc7821813:03
Qiming#link https://etherpad.openstack.org/p/senlin-newton-workitems13:03
Qimingperformance testing, any progress?13:04
*** gcb has quit IRC13:04
yanyanhuyes13:04
*** guoshan has joined #openstack-meeting13:04
yanyanhuroman has put +2 on the profile context patch13:04
yanyanhuneed another +2 and workflow13:04
Qimingneed to ping rally core?13:04
yanyanhuonce this patch is merged, will add context for cluster as well13:04
yanyanhuQiming, yes, maybe wait for another one or two days13:05
Qimingokay13:05
Qimingintegration test side, https://review.openstack.org/#/c/354566/13:05
yanyanhugood news is it works now13:05
Qimingstill waiting for another core to approve13:05
yanyanhuQiming, yes, for adding zaqar support13:05
yanyanhubut at least we can rely on it to make some basic verifications13:05
Qimingokay, that is not urgent13:05
yanyanhuyes13:06
Qimingbasic verification passed, that is great13:06
yanyanhuyep13:06
Qiminghealth policy side13:06
QimingLB based health detection is still not there13:06
Qimingnot sure if xinhui is still pushing it13:06
Qimingshe has been working on fencing nova compute host13:07
*** su_zhang has quit IRC13:07
*** asettle has joined #openstack-meeting13:07
Qimingexperimenting with IPMI drivers13:07
*** su_zhang has joined #openstack-meeting13:07
Qimingthe only problem in that direction is nova is not emitting a notification if nova-compute is down13:07
*** lixinhui_ has joined #openstack-meeting13:08
Qimingthere are notifications if the compute service is shut down by operators, but if the compute host is down, there is no notification13:08
Qimingthat is too bad13:08
Qimingso the only workaround, as of today, would be a poller13:08
lixinhui_you have confirmed that13:09
yanyanhupoller sounds reasonable for this scenario13:09
Qimingso ... I'm not sure if we should (in Ocata release) make health manager a separate service13:09
*** rodrigods has quit IRC13:09
*** jckasper has joined #openstack-meeting13:09
Qimingyes, lixinhui_, confirmed13:09
Qimingthanks for joining13:09
*** rodrigods has joined #openstack-meeting13:09
lixinhui_sorry for late13:09
Qimingthat is a stupid design, hopefully we can help improve it if we get cycles13:09
*** david-lyle has quit IRC13:10
Qimingother improvements to health policy is about the recover/check workflow revision13:10
Qimingmostly are done now13:10
Qimingthe policy can now suspend itself if node deletion was initiated from a RPC request instead of a failure detected13:11
Qimingthat part is also done13:11
QimingI was thinking of make the policy a little bit smarter13:11
yanyanhugreat13:11
*** adisky has quit IRC13:11
*** su_zhang has quit IRC13:11
Qimingif you look at this: http://git.openstack.org/cgit/openstack/senlin/tree/senlin/engine/health_manager.py#n6113:12
Qimingwhen a node is down and get detected13:12
*** sfilatov has joined #openstack-meeting13:12
Qimingwe actually are sending this info as params when invoking the node_recover API13:12
*** vladikr has left #openstack-meeting13:12
Qimingthe policy can be improved to handle different 'event' and/or 'state' a little bit smarter13:13
lixinhui_good point13:13
Qimingsay if a node is in SHUTDOWN state, the policy can try just 'reboot' it13:13
Qimingor 'start' it13:13
Qimingthis is still an imagination, have to wait for the nova server operations patch merged into sdk13:13
Qimingprofile/policy version13:14
Qimingyanyan has been working on a 'workaround'13:14
*** roxanagh_ has joined #openstack-meeting13:14
yanyanhuyes, basic versioning support for schema and spec has been there13:14
QimingI'm calling it a 'workaround' because ... versioning is pretty big a problem to solve13:14
Qimingwe'll get back to that later13:15
yanyanhubut I think we have a lot more detail to figure out before deciding how to support policy/profile version control13:15
Qimingcontainer support13:15
yanyanhuyes13:15
Qimingcorrect13:15
Qiminghaiwei's patch is finally in13:15
yanyanhuyes, long run...13:15
*** gabriel-bezerra has joined #openstack-meeting13:15
Qiminghe is now experimenting specifying a host_cluster when creating container clusters13:16
Qiminggood luck ...13:16
Qimingwith that work as a starting point, we may want to discuss how to proceed as next step13:16
*** sheel has quit IRC13:16
Qiminghaven't got time to review his new spec proposal though13:16
yanyanhubetter have a session in summit to discuss this topic13:17
Qimingbut I'd like to call a cross project discussion with magnum/zun on this13:17
Qimingright13:17
*** markvoelker has quit IRC13:17
yanyanhuQiming, sure, that will be the best13:17
Qimingreceiver side, yanyan has been working on zaqar support13:17
Qimingplease delete the items that are done13:18
yanyanhuQiming, yes13:18
yanyanhusure13:18
*** david-lyle has joined #openstack-meeting13:18
yanyanhuthe initial part has been merged today13:18
Qiminghopefully, zaqar can bring in a more secure, more flexible channel for users/services to send signals to senlin13:18
yanyanhuyes13:18
*** roxanagh_ has quit IRC13:19
Qimingthat was another marathon13:19
Qimingokay, anything else on the etherpad page?13:19
yanyanhulooks so. hopefully we can have a basic version that works before cut our release13:19
Qimingthis week is the week to cut newton-3 release13:19
QimingI don't want to do it on Friday, too risky, when the gate is so jammed13:19
yanyanhuah, hope to catch rc113:20
*** jamesdenton has joined #openstack-meeting13:20
Qimingwe have the flexibility to merge more stable features in next few weeks13:20
Qimingbecause we don't have a huge pipeline for review/debate13:20
*** sfilatov has quit IRC13:20
yanyanhugood news13:21
Qimingokay, moving on to next topic13:21
Qiming#topic health checking update13:21
*** openstack changes topic to "health checking update (Meeting topic: senlin)"13:21
Qimingem ... I have basically covered that13:21
yanyanhuyep13:21
Qimingmostly about the check/recover workflow and the handling of different actions in the policy13:21
*** xuhaiwei_ has joined #openstack-meeting13:21
Qimingthere is still a feature not implemented13:21
Qimingwe were hoping that the recover action can be a list of operations for the profile to try13:22
Qimingcurrently, the profile (nova in particular) only understand REBUILD, and the generic profile only handles RECREATE13:22
Qimingthat would be an interesting work for future13:23
Qimingevening, xuhaiwei_13:23
Qiming#topic cluster status update13:23
*** openstack changes topic to "cluster status update (Meeting topic: senlin)"13:23
xuhaiwei_hi, Qiming13:23
*** cardeois has joined #openstack-meeting13:23
Qimingif you are watching the gerrit notifications, you will notice that I have been working on cluster status update fix these two days13:23
xuhaiwei_kept silent to not disturb you:)13:24
Qimingthe basic idea is this: we will update cluster status, based on the status of the member nodes13:24
QimingNOT based on the last operation performed on it13:24
*** liuhanxi has quit IRC13:24
Qiminge.g. a CLUSTER_UPDATE operation may fail, but the cluster may still remain ACTIVE13:24
Qimingwe have to differentiate this two things13:25
*** lblanchard has joined #openstack-meeting13:25
*** esberglu has quit IRC13:25
*** bobh has joined #openstack-meeting13:25
QimingA CLUSTER_SCALE_OUT may fail, but that failure is an action failure, it doesn't mean the cluster is not operable13:25
QimingI think this series of patches is near an end13:26
*** donghao has joined #openstack-meeting13:26
*** esberglu has joined #openstack-meeting13:26
Qimingwhen making these changes, I also changed the modifcation of 'desired_capacity'13:26
Qimingwe were changing the 'desired_capacity' after an action is completed, but that is WRONG13:27
Qimingit has been reported several times13:27
yanyanhuyes, saw that patch, that is reasonable13:27
yanyanhuespecially from ha perspective13:27
Qimingso I was also making that happen before the action is executed13:27
Qimingwhen a request arrives, the user's expectation is the desired_capacity13:27
Qimingif the engine failes to perform the action, it should not change user's expectation13:28
Qimingthat was a simple logic, but we unfortunately learned it in a hard way13:28
Qimingquestions/comments on this?13:28
Qimingseems a no13:29
qwebirc78218sorry to break13:29
qwebirc78218can i ask a question13:29
Qimingsure13:29
qwebirc78218last time, i create a node but failed13:29
qwebirc78218so i recovered it13:29
*** mriedem has joined #openstack-meeting13:30
qwebirc78218but the desire capacity is still 013:30
*** mmedvede_ has joined #openstack-meeting13:30
*** mmedvede has quit IRC13:30
*** mmedvede_ has quit IRC13:30
Qimingyep, that is exactly one of the problems we are fixing13:30
qwebirc78218is that should be 113:30
*** rossella_s has quit IRC13:30
Qimingwhen you are creating a node, the desired capacity should be incremented by 113:31
qwebirc78218okey, thanks for answering13:31
Qimingeven if the node creation was a failure13:31
Qiming'increment the cluster size by one', that is the user's (your) desire13:31
Qimingwe should handle it differently13:31
*** su_zhang has joined #openstack-meeting13:31
Qimingthanks for brining this up13:31
*** bobh has quit IRC13:32
Qimingmoving on13:32
Qiming#topic ocata design summit sessions13:32
*** openstack changes topic to "ocata design summit sessions (Meeting topic: senlin)"13:32
Qiming#link https://etherpad.openstack.org/p/ocata-senlin-sessions13:32
yanyanhuhave put my name on profile/policy versioning13:33
QimingI was just dumping some topics above my head13:33
Qimingpolicy/profile versioning definitely needs some discussion13:33
Qimingeven before/after that session13:33
yanyanhuyes13:33
Qimingmaybe combined with Topic 413:33
Qiming"versioned everything"13:34
yanyanhuQiming, yes, topic 4 can be a extentional discussion13:34
Qimingyep, we cannot finish that in one session13:34
Qimingmaybe we need two slots13:34
yanyanhuyes, if we have enough time slot13:34
Qimingtopic 2 is about health13:34
Qimingwe have some preliminary support now, next step is to make it work in production environments13:35
*** bobh has joined #openstack-meeting13:35
Qimingit is a huge problem space13:35
Qimingwe have to brainstorm the working items and prioritize them13:35
Qimingmaybe involve a congress extension or mistral workflow13:36
Qimingi just don't now13:36
Qimings/now/know13:36
Qimingthe 3rd topic I can think of is about container clustering13:36
Qiminghaiwei has set a stage for us, where are we heading next?13:37
*** esberglu has quit IRC13:37
xuhaiwei_Maybe I can be the driver13:37
Qimingthat would be excellent13:37
*** xiaohhui has joined #openstack-meeting13:37
xuhaiwei_I didn't spend enough time on it up to now, will try  to do more things before the summit13:37
*** uxdanielle has joined #openstack-meeting13:37
*** asselin_ has joined #openstack-meeting13:38
*** nmagnezi has quit IRC13:38
Qimingso ...13:38
Qimingany more ideas you can think of?13:38
xuhaiwei_first should let the container going13:38
Qimingor we can just let ttx know that we need 4 working sessions?13:39
yanyanhuI guess another topic may worth to discuss is cluster do operation?13:39
Qimingokay13:39
yanyanhualtough we already have some basic idea for it. but may need to figure out the detail13:39
yanyanhuand also use case13:39
Qimingopenstack cluster do reboot13:40
xuhaiwei_I updated the spec a few days ago, hope you can review it https://review.openstack.org/#/c/281102/13:40
*** markvoelker has joined #openstack-meeting13:40
Qimingwe already support 'openstack cluster run --script <script> --network private --address-type private --identity-file <file> --user fedora <cluster_name>13:41
*** mmedvede has joined #openstack-meeting13:41
Qimingterribly sorry, haiwei, will jump onto it tomorrow13:41
xuhaiwei_ok13:41
Qimingcluster do is more about actions supported by a profile type13:41
*** esberglu has joined #openstack-meeting13:41
yanyanhuyes, maybe we can support cluster run with a template as input :)13:42
*** ub has joined #openstack-meeting13:42
yanyanhuto improve the convenience13:42
Qimingyou will create several apis to manage the scripts13:43
yanyanhuQiming, or maybe just a client side support13:43
yanyanhuto avoid enforcing user define too many parameters in command line13:43
Qimingit is the same13:43
*** ivc_ has quit IRC13:43
Qimingjust ... where you are putting your parameters13:44
yanyanhuyes13:44
yanyanhuseems so13:44
Qimingif you tried 'glance image-create', you know what I mean13:44
yanyanhuyea13:44
Qimingso, please feel free to add items to the agenda13:45
yanyanhusure13:45
*** markvoelker has quit IRC13:45
QimingI'll review the etherpad tomorrow and conclude with a number to feedback ttx13:45
yanyanhuwill think about it13:45
Qimingthanks13:45
Qiming#topic open discussion13:45
*** openstack changes topic to "open discussion (Meeting topic: senlin)"13:45
*** baojg has joined #openstack-meeting13:46
*** dmorita has joined #openstack-meeting13:46
*** annegentle has quit IRC13:46
*** e0ne has quit IRC13:46
Qimingwe are freezing senlinclient this week13:46
Qimingany topics/patches you want to merge before we cut a release?13:47
yanyanhuQiming, the message receiver support has been there, no more item from my side13:47
*** janki has quit IRC13:47
*** hoangcx2 has quit IRC13:47
Qimingone thing I can think of is about dumping out the action ID for all requests that return a pointer to the action13:47
*** e0ne has joined #openstack-meeting13:48
Qimingwe were not so consistent on this before, there have been some complaints on this13:48
*** hoangcx has joined #openstack-meeting13:48
*** zz_dimtruck is now known as dimtruck13:48
*** ub2 has joined #openstack-meeting13:48
Qimingsometimes we say "request accepted", sometimes we say "request accepted by actoin <action id>"13:48
*** ub has quit IRC13:48
*** thorst_ is now known as thorst13:48
Qimingthat is something we can improve13:49
Qimingalso the 'deprecation warning' is a little bit confusing13:49
Qimingwe can explicitly say WHEN it will deprecate13:49
Qimingit should be April 201713:49
Qimingtwo cycles13:49
Qimingand we will get back the '--profile' option from openstackclient13:50
Qimingby then13:50
*** Julien-zte has joined #openstack-meeting13:50
Qiminganything else?13:50
*** dmorita has quit IRC13:51
Qimingseems we are done?13:51
yanyanhunope13:51
xuhaiwei_no13:51
Qimingthanks for joining, everyone13:51
yanyanhuthanks, have a good night13:51
Qimingwish you all a sweet dream and a wet bed13:51
xuhaiwei_thanks13:51
*** jlibosva has joined #openstack-meeting13:51
Qimingbye13:52
yanyanhu:)13:52
Qiming#endmeeting13:52
xuhaiwei_bye13:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:52
openstackMeeting ended Tue Aug 30 13:52:08 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-08-30-12.59.html13:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-08-30-12.59.txt13:52
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-08-30-12.59.log.html13:52
*** yanyanhu has quit IRC13:52
*** ayoung has joined #openstack-meeting13:52
*** janki has joined #openstack-meeting13:54
*** rbak has joined #openstack-meeting13:56
*** _nadya_ has quit IRC13:57
*** janki has quit IRC13:57
*** electrocucaracha has joined #openstack-meeting13:57
*** hynekm has joined #openstack-meeting13:57
*** mlavalle has joined #openstack-meeting13:57
*** yamahata has joined #openstack-meeting13:58
*** john-davidge has joined #openstack-meeting13:58
*** akamyshnikova has joined #openstack-meeting13:58
*** SridarK has joined #openstack-meeting13:59
*** janzian has joined #openstack-meeting13:59
*** qwebirc78218 has quit IRC13:59
ihrachys#startmeeting networking14:00
openstackMeeting started Tue Aug 30 14:00:18 2016 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
ihrachyshi all14:00
njohnstono/14:00
mlavalleo/14:00
*** myoung|afk is now known as myoung14:00
amotokio/14:00
jlibosva\o14:00
jschwarz\o/14:00
* ihrachys letting the dust to settle14:00
hoangcxhi14:00
haleybhi14:00
hichiharahi14:00
HenryGo/14:00
* john-davidge stirs the dust14:00
ihrachys#link https://wiki.openstack.org/wiki/Network/Meetings Agenda14:01
electrocucaracha0/14:01
akamyshnikovahi14:01
*** iyamahat has joined #openstack-meeting14:01
ihrachys#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:01
andreas_so/14:01
ihrachysI have a lot of announcements for everyone14:01
* ihrachys looks where to start14:02
ihrachysfirst order of business, we are approaching milestone3 cut-off14:02
ihrachysit should happen till Sep 114:02
ihrachys= this week14:02
*** eharney has joined #openstack-meeting14:02
ihrachysrelease gods are to prepare release request in due course14:02
*** annegentle has joined #openstack-meeting14:03
*** liuyulong has quit IRC14:03
*** pc_m has joined #openstack-meeting14:03
ihrachyssame goes for the client, same deadline14:03
ihrachysamotoki already pushed a release request: https://review.openstack.org/#/c/362880/14:03
jschwarz:Qa!14:03
jschwarzoops :P14:03
*** su_zhang has quit IRC14:03
*** hockeynut has joined #openstack-meeting14:03
ihrachysafter the milestone3 cut-off, the branch will be strictly monitored not to allow any breakage in14:04
*** su_zhang has joined #openstack-meeting14:04
*** dimtruck is now known as zz_dimtruck14:04
ihrachysthe only things to be allowed after it happens are bug fixes, doc cleanups, plus things that happen to get an FFE (feature freeze exception) approved14:04
ihrachys#link http://lists.openstack.org/pipermail/openstack-dev/2016-August/102321.html Armando email on the matter and the process14:04
ihrachysthe process to apply for FFE is by updating the post mortem document Armando spun up: https://review.openstack.org/#/c/360207/14:05
ihrachyseven if you don't have an exception to request (huge thanks for that!), you should still follow the link and update it with comments on features you led or helped with or just happen to know details about14:06
ihrachysit will be of enormous help for PTL and other folks involved in release process if the review is updated with latest state for all tracked bits14:06
ihrachysthe next events ahead are, RC1 and stable/newton branches' creation14:07
*** dmorita has joined #openstack-meeting14:07
ihrachysthat will happen some time 2 weeks+ from now14:07
ihrachysmore details at: https://releases.openstack.org/newton/schedule.html14:07
ihrachysonce stable/newton is cut-off, master is open for Ocata development and everyone can proceed merging featureful patches.14:07
*** esberglu has quit IRC14:07
*** sdake has joined #openstack-meeting14:08
ihrachysso, we have 2 weeks of master being kinda locked for anything but release critical14:08
*** su_zhang has quit IRC14:08
HenryGAre any outstanding DB migrations still hoping to get into Newton?14:08
ihrachyscores, make sure you ain't land crap14:08
ihrachysHenryG: are you intending to tag the latest migrations with Newton?14:08
*** esberglu has joined #openstack-meeting14:09
jschwarzHenryG, yes14:09
ihrachysHenryG: I think there are patches in flight that should land in Newton that happen to touch schema, I suggest we wait a week or so14:09
jschwarzHenryG, https://review.openstack.org/#/c/357965/1014:09
*** cleong has joined #openstack-meeting14:09
HenryGI usually do the tagging quite late.14:09
amotokiHenryG: what repos do you plan to cover? neutron, lbaas, fwaas, vpnaas and dynamic-routing?14:09
ihrachysgood news we have a pre-release check list now: http://docs.openstack.org/developer/neutron/policies/release-checklist.html14:10
ihrachyswe will follow the list during the upcoming weeks to make sure nothing is left behind14:10
HenryGamotoki: Good question. It may also be a good point to stop this tagging that no one uses as far as I know.14:10
*** dmorita has quit IRC14:11
amotokiI am not sure no one uses it. do we hear it from operators?14:11
ihrachysHenryG: The question is more about the contract we happened to define and whether we can break it.14:11
*** ljxiash has joined #openstack-meeting14:11
*** sdake_ has joined #openstack-meeting14:12
*** ivc_ has joined #openstack-meeting14:12
ihrachysHenryG: a good start to stop doing it would be reaching out ops and deployment tools teams14:12
ihrachysfor N, it will need to happen anyhow14:12
HenryGihrachys: ack14:12
*** sdake has quit IRC14:13
ihrachysthe last thing to note, we had a midcycle, and Armando with the help of his minions prepared a report14:13
ihrachys#link http://lists.openstack.org/pipermail/openstack-dev/2016-August/102366.html14:13
*** elynn has left #openstack-meeting14:13
ihrachyseveryone is encouraged to comment on the thread14:13
ihrachysI think it captures most prominent discussions that happened during the event rather neatly, so please make use of it14:13
*** ebalduf has joined #openstack-meeting14:14
ihrachysok, announcements are done!14:14
* ihrachys wipes off sweat from his head14:14
ihrachys#topic Blueprints14:14
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:14
*** lixinhui_ has quit IRC14:14
*** sbelous__ has joined #openstack-meeting14:15
ihrachysnot much to cover here, just a note that feature owners and approvers should update the dashboards for targeted features14:15
ihrachys#link https://launchpad.net/neutron/+milestone/newton-314:15
ihrachysalso it's probably a good time to make more use of the dashboard to target and track bugs that we believe are release critical.14:15
*** amotoki__ has joined #openstack-meeting14:15
*** baojg has quit IRC14:16
ihrachysreviewers, now that we cut off milestonel, please focus on bugs and FFEs in your reviews; other stuff should anyway be delayed to when the branch is open14:16
ihrachys#topic Bugs and Gate failures14:17
*** openstack changes topic to "Bugs and Gate failures (Meeting topic: networking)"14:17
ihrachyswe had armax covering the bug deputy role for the last 2 weeks14:17
ihrachyswell, actually 1.5 weeks. he told me he did not pay attention the last half of the last week :-|14:17
njohnstonYay armax!14:17
*** prateek has quit IRC14:17
ihrachysso we could have some bits falling thru cracks14:17
*** Liuqing has joined #openstack-meeting14:18
ihrachyswe really need a volunteer to cover for this week, atm we have no one14:18
ihrachysactually, we also need a volunteer for the next one too14:18
ihrachysdon't be shy, raise your hands!14:18
jschwarzihrachys, I'd like to volunteer for the next week14:18
*** baojg has joined #openstack-meeting14:18
ihrachysjschwarz: Sep 5+ is yours!14:18
jschwarzihrachys, yay!14:18
ihrachyswho has capacity for this week?14:18
*** sindhu has joined #openstack-meeting14:19
*** anilvenkata has joined #openstack-meeting14:19
*** spotz_zzz is now known as spotz14:19
*** skraynev_ has joined #openstack-meeting14:19
* ihrachys taps the desktop with his fingers14:20
* HenryG watches the tumbleweeds rolling by14:20
haleybi can do the rest of this week, but monday is a holiday around here14:20
ihrachysit's very important to have someone covering during pre-release weeks14:20
ihrachyshaleyb: next Monday?14:20
haleybyes14:21
jschwarzhaleyb, Monday is mine! ^_^14:21
ihrachyshaleyb: that's ok, jschwarz starts on Sun :)14:21
*** jungleboyj has joined #openstack-meeting14:21
haleybgood, i figured i had until the meeting14:21
ihrachysjschwarz: haleyb: thanks folks, you rock. please one of you, update the agenda page with the set dates.14:21
jschwarzon it14:21
ihrachyshaleyb: if possible, you may look at what happened the last Thu-Fri since those may be without coverage.14:22
ihrachysthanks again for all the volunteers.14:22
*** cardeois has quit IRC14:23
*** banix has joined #openstack-meeting14:23
ihrachysnow that we approach release, we should also keep an eye on deprecation bugs:14:23
ihrachys#link https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.tag=deprecation14:23
*** zz_dimtruck is now known as dimtruck14:23
*** galstrom_zzz is now known as galstrom14:23
ihrachysif something should be deprecated in N, it's the time to do it, otherwise a thing prolonges till O14:23
*** cardeois has joined #openstack-meeting14:24
ihrachysalso, we should really start cleaning up all the automatically created doc bugs we have on our plate:14:24
ihrachys#link https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.tag=doc14:24
ihrachysplease folks, walk thru the list and assign yourself to relevant bits, and make them happen before N final. We should have the best docs. :)14:25
ihrachysI believe best candidates for those doc bugs are authors of patches that triggered their creation in the first place14:25
ihrachysyou may need to update openstack-manuals or neutron-lib (api-ref) or devref, depending on the kind of the bug.14:25
*** trevormc has joined #openstack-meeting14:26
john-davidgeihrachys: Is there a way to modify the script to auto-assign them it that way? Could a a useful future improvement14:26
*** amuller has joined #openstack-meeting14:26
ihrachysjohn-davidge: I guess it's a matter of some patch in infra repos14:26
ihrachysjohn-davidge: you are obviously welcome to start it, or discussion on openstack-dev@14:26
*** liamji has joined #openstack-meeting14:26
* john-davidge will do some digging14:26
*** mriedem has quit IRC14:27
ihrachysI suspect that it may be a lot easier to do for someone already involved in the repos14:27
ihrachysjohn-davidge: thanks!14:27
ihrachysthe last bugs list to keep an eye on is gate failures:14:27
ihrachys#link https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.tag=gate-failure14:27
*** mriedem has joined #openstack-meeting14:28
*** baojg has quit IRC14:28
ihrachyslooks like we don't have anyone working on first two14:28
*** boden has joined #openstack-meeting14:28
*** amotoki__ has quit IRC14:29
ihrachyswould be great to have someone digging those so that we proactively keep our gate in order during next weeks.14:29
ihrachysspeaking of gate... we may have some work to do to clean up our logs before release14:29
*** nmagnezi has joined #openstack-meeting14:29
ihrachyswe looked at current service logs from full job yesterday, and those look quite bad.14:29
ihrachystracebacks, deadlocks, irrelevant warnings14:30
* ihrachys digs for a link14:30
ihrachysexample: http://logs.openstack.org/30/271830/10/check/gate-tempest-dsvm-neutron-full-ubuntu-xenial/52ca52d/logs/screen-q-svc.txt.gz?level=TRACE14:30
ihrachysI'd like to remind that openstack logging guidelines require that no tracebacks are shown in logs14:30
*** fnaval_ has joined #openstack-meeting14:30
*** mikelk has quit IRC14:31
ihrachysfor one, that deadlock/InternalError red thing, it seems relevant to provision blocks and standardattributes.14:31
ihrachyskevinbenton: did you happen to look at those?14:31
ihrachysI also see ipam mentioned in deadlock failures.14:32
*** esberglu_ has joined #openstack-meeting14:32
ihrachysso carl_baldwin may also be interested14:32
*** e0ne has quit IRC14:32
ihrachysanother case to look at is this traceback: http://logs.openstack.org/30/271830/10/check/gate-tempest-dsvm-neutron-full-ubuntu-xenial/52ca52d/logs/screen-q-svc.txt.gz?level=TRACE#_2016-08-29_11_27_28_09514:32
haleybihrachys: there were a couple patches last night to deal with dhcp traces14:32
ihrachysis it a negative test triggering the traceback? we may have some work to do to sanitize the exception14:33
ihrachyshaleyb: cool. links?14:33
haleybtwo were merged, let me find links14:33
*** esberglu has quit IRC14:33
*** ociuhandu has joined #openstack-meeting14:33
*** fnaval has quit IRC14:33
amotokii think https://bugs.launchpad.net/bugs/1618216 and https://bugs.launchpad.net/bugs/161818714:34
openstackLaunchpad bug 1618216 in neutron "dhcp agent RPC handler doesn't retry DBError" [High,Fix released] - Assigned to Kevin Benton (kevinbenton)14:34
*** fnaval_ has quit IRC14:34
openstackLaunchpad bug 1618187 in neutron "InvalidInput exceptions from DHCP RPC handler" [High,Fix released] - Assigned to Kevin Benton (kevinbenton)14:34
*** su_zhang has joined #openstack-meeting14:34
haleyb https://review.openstack.org/36245814:34
haleyband https://review.openstack.org/36234314:34
*** fnaval has joined #openstack-meeting14:34
*** e0ne has joined #openstack-meeting14:34
*** woodster_ has joined #openstack-meeting14:34
ihrachysok, cool. I have a more recent one here: http://logs.openstack.org/74/362774/1/check/gate-tempest-dsvm-neutron-full-ubuntu-xenial/c4a8799/logs/screen-q-svc.txt.gz?level=TRACE14:34
haleybyes, those two, but i think the underlyng bug is still there, can't tell yet14:35
* ihrachys notes that he should look at 'Failed to determine MTU for segment None:None; network 694e0047-c236-4fb4-9070-4e33d12c6c2b MTU calculation may be not accurate' thingy. haven't seen it before.14:35
*** sudswas__ has quit IRC14:35
*** sudipto has quit IRC14:35
ihrachysalso still seeing pymysql.err.IntegrityError in ipam code at: http://logs.openstack.org/74/362774/1/check/gate-tempest-dsvm-neutron-full-ubuntu-xenial/c4a8799/logs/screen-q-svc.txt.gz?level=TRACE#_2016-08-30_11_03_10_70314:35
*** esberglu_ has quit IRC14:36
*** su_zhang has quit IRC14:36
*** nkrinner has quit IRC14:36
ihrachysok, I just wanted everyone to be aware that's part of release process that logs should be clean14:36
*** su_zhang has joined #openstack-meeting14:37
ihrachysthere are some gate news that may be worth mentioning too14:37
*** tonytan_brb has joined #openstack-meeting14:37
ihrachysjlibosva has a controversial patch adding scenarios job to the gate (or reusing existing one to run those tests): https://review.openstack.org/35534414:38
jlibosvacontroversial? :)14:38
ihrachyslooks like people have OPINIONS! :)14:38
ihrachysalso of note, we now gate neutronclient on stable branches of neutron: https://review.openstack.org/#/c/361603/14:39
ihrachysthere are also Xenial based jobs baking for functional/fullstack: https://review.openstack.org/#/c/359843/14:39
*** nkrinner has joined #openstack-meeting14:39
ihrachysthe latter should give us ovs 2.5 from apt repos, not through compilation14:39
*** esberglu has joined #openstack-meeting14:39
ihrachysok, let's move thru specific topics14:40
ihrachys#topic Transition to OSC14:40
*** openstack changes topic to "Transition to OSC (Meeting topic: networking)"14:40
ihrachysrtheis: your stage?14:40
*** tonytan4ever has quit IRC14:40
rtheisstatus update from midcycle is available via armax's email14:40
ihrachysrtheis: where do we stand Newton release wise?14:41
*** su_zhang has quit IRC14:41
ihrachysrtheis: f.e. we have some qos patches in OSC. would they land if ready?14:41
rtheisOSC is working on 3.x release stability so new function merges are on hold until that is complete14:41
ihrachysI see. so we proceed with neutronclient and maybe in Ocata we land OSC bits.14:42
rtheisthe qos patches can proceed and land in the next osc release14:42
*** prateek has joined #openstack-meeting14:42
*** tonytan_brb has quit IRC14:42
ihrachysrtheis: thanks for the update14:42
ihrachys#topic Keystone v314:42
*** openstack changes topic to "Keystone v3 (Meeting topic: networking)"14:42
ihrachysdasm: you're up14:42
*** tonytan4ever has joined #openstack-meeting14:42
*** david-lyle has quit IRC14:43
ihrachysanyone except dasm aware of the state of affairs? how close are we? any remaining bits to land?14:43
ihrachysI see this WIP https://review.openstack.org/#/c/357977/14:44
ihrachysit does not seem really ready. I wonder whether it means it slips into O14:44
ihrachysok, moving on14:44
ihrachys#topic Neutron-lib14:44
*** openstack changes topic to "Neutron-lib (Meeting topic: networking)"14:44
*** esberglu has quit IRC14:44
ihrachysboden: care to update? :)14:45
bodenneutron-lib 0.4.0 was recently released to pypi14:45
*** esberglu has joined #openstack-meeting14:45
amotokiand stable/newton branch has been created.14:46
HenryGYes, 0.4.0 will most likely be the "Newton version" of the lib14:46
HenryGWe haven't spotted any issues yet.14:46
bodenI would encourage folks to take a spin through the neutron-lib reviews if they get time14:46
*** nkrinner has quit IRC14:46
*** sdake_ has quit IRC14:47
bodenHenryG: anything else noteworthy?14:47
*** guoshan has quit IRC14:47
amotokiI am looking thru api-ref cleanup patches but it is not so fast.. let me give some more time.14:47
ihrachysamotoki: that work is not blocked by release times, right?14:48
ihrachysit's docs only, so should be always ok to land14:48
*** cartik has joined #openstack-meeting14:48
amotokiihrachys: yes. it is not a release blocker14:48
ihrachysgreat.14:48
ihrachys#topic Open Floor14:48
*** openstack changes topic to "Open Floor (Meeting topic: networking)"14:48
*** david-lyle has joined #openstack-meeting14:48
amotokiit is what we want to have before release though14:48
ihrachysI am looking thru on demand agenda, nothing new pops out14:48
ihrachysanyone has a topic interesting to the team to raise?14:49
*** enriquetaso has joined #openstack-meeting14:49
bodennext monday is holidy in US14:49
bodens/holidy/holiday/g14:50
*** piet has joined #openstack-meeting14:50
njohnstonso the next of these meetings will be lightly attended14:50
dasanind_ihrachys: there are some patches related to centralize config options with +2s do you think they will make it in N release14:50
ihrachysdasanind_: that's a question to ask the approver. I don't personally think it's release critical, probably best effort.14:50
ihrachysdoes it mean we should cancel the next meeting?14:51
ihrachysI will leave it up to armax to decide though.14:51
*** Liuqing has quit IRC14:51
ihrachysok, I guess we'll call it a day. stay tuned, be aware of release implications, and behave.14:51
ihrachys#endmeeting14:51
*** _nadya_ has joined #openstack-meeting14:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:51
openstackMeeting ended Tue Aug 30 14:51:37 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-08-30-14.00.html14:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-08-30-14.00.txt14:51
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-08-30-14.00.log.html14:51
jlibosvabye14:51
* njohnston considers behaving a "stretch goal"14:52
hichiharabye14:52
*** pc_m has left #openstack-meeting14:52
hoangcxbye14:52
*** amuller has left #openstack-meeting14:53
*** electrocucaracha has left #openstack-meeting14:53
*** jlanoux has quit IRC14:53
*** ilyashakhat has joined #openstack-meeting14:53
*** hoangcx has quit IRC14:53
*** esberglu has quit IRC14:53
*** esberglu has joined #openstack-meeting14:54
*** anilvenkata is now known as anilvenkata_afk14:55
*** saju_m has joined #openstack-meeting14:55
*** jlanoux has joined #openstack-meeting14:56
*** asettle has quit IRC14:56
*** boden has left #openstack-meeting14:56
*** fnaval has quit IRC14:56
*** egallen has joined #openstack-meeting14:57
*** asettle has joined #openstack-meeting14:57
*** iyamahat has quit IRC14:57
*** hashar is now known as hasharAway14:57
*** rajinir has joined #openstack-meeting14:58
*** yuval has quit IRC14:59
*** jdandrea_ has joined #openstack-meeting14:59
*** nkrinner has joined #openstack-meeting14:59
*** jlibosva has left #openstack-meeting15:00
*** amotoki has quit IRC15:01
carl_baldwino/15:01
mlavalleo/15:01
carl_baldwinmlavalle: Is it just us?15:01
xiaohhuihi15:01
john-davidgeo/15:01
carl_baldwinxiaohhui: john-davidge: hi15:01
haleybhi15:02
mlavalleno, the usual band of fans are here :-)15:02
john-davidgecarl_baldwin: hey15:02
john-davidgemlavalle: :)15:02
carl_baldwin#startmeeting neutron_routed_networks15:02
*** ilyashakhat has quit IRC15:02
openstackMeeting started Tue Aug 30 15:02:21 2016 UTC and is due to finish in 60 minutes.  The chair is carl_baldwin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** openstack changes topic to " (Meeting topic: neutron_routed_networks)"15:02
openstackThe meeting name has been set to 'neutron_routed_networks'15:02
*** iyamahat has joined #openstack-meeting15:02
*** hichihara has quit IRC15:02
carl_baldwinThis could be short, I think.15:02
*** david-lyle has quit IRC15:02
*** jdandrea_ has left #openstack-meeting15:02
carl_baldwin#topic Announcements15:03
*** openstack changes topic to "Announcements (Meeting topic: neutron_routed_networks)"15:03
carl_baldwinNewton-3 is imminent.15:03
carl_baldwinI have to say that it has been a very good cycle all things considered.15:03
*** roxanagh_ has joined #openstack-meeting15:04
*** skraynev_ has quit IRC15:04
carl_baldwinThe patch to enable creation and deletion of segments merged!15:04
carl_baldwin#link https://review.openstack.org/#/c/31735815:04
carl_baldwinAny other announcements?15:04
mlavalleWe have a routed networks talk confirmed for Barcelona:15:04
mlavalle#link https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/15149/scaling-up-openstack-networking-with-routed-networks15:05
carl_baldwinmlavalle: Yes, good thinking.15:05
carl_baldwinWouldn't it be cool if generic resource pool scheduling was available by then?15:05
john-davidgemlavalle: carl_baldwin: Excellent! The service subnets talk wasn't approved unfortunately15:05
mlavalleyeah, I am doing all on my part to have that ready15:05
carl_baldwinI keep meaning to check that thread on the ML about the next steps for it.15:05
carl_baldwinmlavalle: I know you are. Just wondering about the other work in Nova.15:06
mlavalleyeap15:06
mlavallethat's the challenge15:06
mlavallebut they are merging code15:06
mlavalleI have to say that15:06
*** pc_m has joined #openstack-meeting15:06
carl_baldwinThat's good.15:07
carl_baldwin#link http://lists.openstack.org/pipermail/openstack-dev/2016-August/102477.html15:07
carl_baldwinI saw Matt sent this ^15:07
*** coolsvap is now known as coolsvap_15:07
carl_baldwin#topic patches15:07
carl_baldwin#link https://review.openstack.org/#/q/status:open+(topic:bp/routed-networks+OR+topic:bp/neutron-routed-networks+OR+topic:bp/service-subnets)15:07
*** openstack changes topic to "patches (Meeting topic: neutron_routed_networks)"15:07
carl_baldwinLet's have a quick run through on this. ^15:07
*** tonytan_brb has joined #openstack-meeting15:07
*** sbelous__ has quit IRC15:07
carl_baldwinOh, also the service subnets should be operational now.15:08
carl_baldwinThanks john-davidge15:08
mlavalleyaay!15:08
carl_baldwin... and haleyb15:08
*** iyamahat has quit IRC15:08
john-davidge\o/15:08
haleybcarl_baldwin: yes, just waiting for OSC change still.  And thanks to you too15:08
carl_baldwinI did post a refactor that I think improves the code readability but doesn't change the operation really15:08
carl_baldwin#link https://review.openstack.org/#/c/36085815:09
*** roxanagh_ has quit IRC15:09
carl_baldwinI'll rebase this as soon as possible. I wanted it to implement the unaddressed ports blueprint.15:09
john-davidgecarl_baldwin: It's a much needed refactor, thanks for going back to that15:09
*** sdake has joined #openstack-meeting15:09
*** armax has joined #openstack-meeting15:09
john-davidgeI have a WIP patch for the docs https://review.openstack.org/#/c/360526/15:10
carl_baldwinjohn-davidge: I did it with optimizing the error generation path in a future path. I think we can cut down those queries now that it is easier to see what all they're doing.15:10
*** cartik has quit IRC15:10
john-davidgehaleyb: Included you as a co-author as it's based heavily on the spec15:10
carl_baldwinjohn-davidge: Great! I hadn't seen that yet.15:10
john-davidgeNot finished yet, but I'll continue working on it this week15:11
haleybjohn-davidge: thanks, will review15:11
*** tonytan4ever has quit IRC15:11
*** nkrinner is now known as nkrinner_afk15:11
carl_baldwinI'll keep an eye on it.15:11
john-davidgehaleyb: carl_baldwin: thanks15:12
carl_baldwinThere is one more patch I'd like to get in to Newton.15:12
carl_baldwin#link https://review.openstack.org/#/c/293305/15:12
carl_baldwinMostly because if we don't, we'll have to create a new extension for it. :(15:12
*** numans has quit IRC15:12
carl_baldwinIt is getting pretty close.15:12
john-davidgeAh, this one. I'll take another look15:13
carl_baldwinI found a strange issue yesterday that was causing many of the UTs to fail. Now, it just has one failure and I think I can fix it up.15:13
carl_baldwinThanks reedip for getting it in better shape last night.15:13
rtheiscarl_baldwin: I was hoping to have that patch merge first before removing WIP from OSC network create and delete patch sets since it changes the interface15:14
carl_baldwinI think that's the last one we'll have the chance to get in before feature freeze15:14
carl_baldwinrtheis: ack, that makes sense.15:14
carl_baldwinI hope to get it merged today.15:14
rtheisawesome15:14
carl_baldwinWe might be able to sneak a few more in as bug fixes.15:15
carl_baldwin... and new tests15:16
*** iyamahat has joined #openstack-meeting15:16
carl_baldwinmlavalle: How is the testing effort going?15:16
mlavallecarl_baldwin: it is going well.... we now have a connectivity test15:16
*** hynekm has quit IRC15:17
mlavalleBin is having some trouble with his dev environment. So I will test it today and tomorow in my environment15:17
*** toscalix has joined #openstack-meeting15:17
carl_baldwinmlavalle: Let us know when / if you think they are ready for review.15:17
mlavallecarl_baldwin: will do15:17
*** sudswas__ has joined #openstack-meeting15:18
*** sudipto has joined #openstack-meeting15:18
carl_baldwinxiaohhui: ping15:18
mlavallein Ocata we are going to add more test cases around the interaction with gneric resource pools15:18
xiaohhuiack15:18
*** cartik has joined #openstack-meeting15:18
carl_baldwin#link https://review.openstack.org/#/c/337956/15:18
carl_baldwinmlavalle: That is a good plan15:18
carl_baldwinxiaohhui: This patch has been sitting for a while. Do you think we need it?15:19
*** toscalix_ has quit IRC15:19
xiaohhuiI might need more work on that patch, but I don't think thing will break without that patch.15:19
xiaohhuiI can continue working on that patch as bug fix.15:20
carl_baldwinxiaohhui: ack15:20
rtheisregarding testing... is segment extension enabled by default or will it be?15:20
xiaohhuiThat is what I want to discuss about, too15:20
xiaohhuihttps://review.openstack.org/#/c/317358/25/neutron/services/segments/db.py@30715:20
xiaohhuikevinbeton brought this out too,15:21
carl_baldwinrtheis: xiaohhui: That is a good question. Right now, it is not enabled by default.15:21
*** toscalix has quit IRC15:21
*** toscalix has joined #openstack-meeting15:21
carl_baldwinWill one of you post a patch to make it on by default? We can discuss on the patch.15:22
xiaohhuiShould we enable it by default? because ml2 will always use segment, I think it is reasonable to make it as default.15:22
xiaohhuiI can do that15:22
*** david-lyle has joined #openstack-meeting15:22
carl_baldwinxiaohhui: Thanks. Let us know when you have it up and I can get some attention on it.15:22
xiaohhuisure,15:22
*** sandanar has joined #openstack-meeting15:23
mlavallexiaohhui: are you still planning to unify the 2 paths?15:23
carl_baldwinxiaohhui: Maybe a post to the ML with a link to the patch will be good too.15:23
xiaohhuiI will do that.  unifying the 2 path can eliminate a TODO in https://review.openstack.org/#/c/31735815:24
*** sridharg has quit IRC15:24
carl_baldwinxiaohhui: Thanks.15:25
*** xuhaiwei_ has quit IRC15:25
carl_baldwinWhat else do we have to discuss today?15:25
*** dkehn_ has quit IRC15:26
mlavalleAssuming our focus this meeting is N-3, nothing as far as I know15:26
john-davidgecarl_baldwin: At what point would you like to start discussing plans for Ocata?15:27
*** fnaval has joined #openstack-meeting15:27
carl_baldwinjohn-davidge: We should start doing that pretty soon. But, N-3 is currently taking a lot of cognitive energy for me.15:27
*** links has quit IRC15:28
john-davidgecarl_baldwin: Sure, it's still too early for now. Perhaps 1-2 weeks from now15:28
carl_baldwinjohn-davidge: agree15:28
*** nibalizer has quit IRC15:29
carl_baldwinSounds like that's about it for today.15:29
carl_baldwinGreat work, everyone. We got a lot done in Newton and I think the quality is pretty good.15:30
carl_baldwinI'll give you 30 minutes back.15:30
*** Ravikiran_K has joined #openstack-meeting15:30
carl_baldwin#endmeeting15:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:30
xiaohhuibye~15:30
openstackMeeting ended Tue Aug 30 15:30:41 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_routed_networks/2016/neutron_routed_networks.2016-08-30-15.02.html15:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_routed_networks/2016/neutron_routed_networks.2016-08-30-15.02.txt15:30
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_routed_networks/2016/neutron_routed_networks.2016-08-30-15.02.log.html15:30
*** sdake has quit IRC15:31
*** banix has quit IRC15:31
*** banix has joined #openstack-meeting15:31
*** mickeys has joined #openstack-meeting15:32
*** ub2 has quit IRC15:32
*** andreas_s has quit IRC15:33
*** mlavalle has left #openstack-meeting15:33
*** xinwu has joined #openstack-meeting15:34
*** tung_doan has joined #openstack-meeting15:34
*** esberglu has quit IRC15:35
*** xinwu has quit IRC15:36
*** esberglu has joined #openstack-meeting15:36
*** salv-orlando has joined #openstack-meeting15:40
*** david-lyle has quit IRC15:40
*** sindhu has quit IRC15:41
*** gyee has joined #openstack-meeting15:42
*** unicell has quit IRC15:42
*** Leo_ has joined #openstack-meeting15:43
*** esberglu_ has joined #openstack-meeting15:43
*** manikanta_tadi has joined #openstack-meeting15:44
*** neel has joined #openstack-meeting15:44
*** klkumar has quit IRC15:44
*** esberglu has quit IRC15:44
*** fredrik has quit IRC15:45
*** donghao has quit IRC15:45
*** dkehn_ has joined #openstack-meeting15:46
*** esberglu has joined #openstack-meeting15:46
*** dmorita has joined #openstack-meeting15:46
*** esumerfd has quit IRC15:46
*** Patifa has joined #openstack-meeting15:47
*** esumerfd has joined #openstack-meeting15:48
*** lpetrut has quit IRC15:48
*** esberglu_ has quit IRC15:48
*** zhurong has quit IRC15:49
*** unicell has joined #openstack-meeting15:50
*** david-lyle has joined #openstack-meeting15:50
*** banix has quit IRC15:50
*** janki has joined #openstack-meeting15:51
*** jlanoux has quit IRC15:52
*** janzian has quit IRC15:52
*** ihrachys has quit IRC15:54
*** esberglu has quit IRC15:55
*** esberglu has joined #openstack-meeting15:55
*** vishwanathj_zzz is now known as vishwanathj15:56
*** rbak has quit IRC15:57
*** dkushwaha has joined #openstack-meeting15:57
*** Sukhdev has joined #openstack-meeting15:58
*** rbak has joined #openstack-meeting15:58
*** dprince has quit IRC15:59
*** esberglu has quit IRC16:00
*** dprince has joined #openstack-meeting16:00
*** sindhu has joined #openstack-meeting16:00
*** sripriya has joined #openstack-meeting16:00
*** diga has joined #openstack-meeting16:01
sridhar_ram#startmeeting tacker16:01
openstackMeeting started Tue Aug 30 16:01:26 2016 UTC and is due to finish in 60 minutes.  The chair is sridhar_ram. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: tacker)"16:01
openstackThe meeting name has been set to 'tacker'16:01
*** egallen has quit IRC16:01
sridhar_ram#topic Roll Call16:01
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"16:01
jankio/16:01
manikanta_tadio/16:01
digao/16:01
dkushwahao/16:01
vishwanathjo/16:01
tung_doano/16:01
neelo/16:01
bobho/16:02
sripriyao/16:02
*** kebray has joined #openstack-meeting16:02
mike_mo/16:02
*** leeantho has joined #openstack-meeting16:02
sridhar_ramhello everyone!16:02
sridhar_ramlet's start..16:02
sridhar_ram#chair bobh sripriya16:02
openstackCurrent chairs: bobh sridhar_ram sripriya16:02
sridhar_ram#topic Announcements16:02
*** openstack changes topic to "Announcements (Meeting topic: tacker)"16:02
*** s3wong has joined #openstack-meeting16:02
sridhar_ramFew quick ones..16:02
*** esberglu has joined #openstack-meeting16:03
s3wonghello16:03
sridhar_ram#link https://releases.openstack.org/newton/schedule.html16:03
sridhar_ramWe are in newton-3 / feature freeze territory !16:04
*** devananda is now known as devananda|MOVING16:04
*** egallen has joined #openstack-meeting16:04
*** mriedem1 has joined #openstack-meeting16:04
sridhar_ramWe need to be extra careful what we land until Sept 15th (newton release deadline)16:04
sridhar_ramnext..16:04
*** natarajk has joined #openstack-meeting16:04
sridhar_ramPlease join me to welcome Yong Sheng to the core team!16:05
sridhar_ram#link http://lists.openstack.org/pipermail/openstack-dev/2016-August/102356.html16:05
sridhar_ramOur geo diversity is quite amazing!16:05
sridhar_ramnext..16:05
sridhar_ramFinal Tacker client for Newton 0.7.0 is released16:05
sridhar_ram#link http://lists.openstack.org/pipermail/openstack-announce/2016-August/001496.html16:05
sridhar_ramthanks for all those who pushed patchsets and reviews to make this happen..!16:06
*** mriedem has quit IRC16:06
sridhar_ramany other quick general shout outs ?16:06
*** mriedem1 is now known as mriedem16:07
*** kebray has quit IRC16:07
*** esberglu has quit IRC16:07
sridhar_rammoving on..16:07
*** natarajk has quit IRC16:07
sridhar_ram#topic Newton Release Status16:07
*** openstack changes topic to "Newton Release Status (Meeting topic: tacker)"16:07
*** kebray has joined #openstack-meeting16:07
sridhar_ramlet's go around and to see any sticking issues in the features expected to land in next couple of weeks...16:07
*** natarajk has joined #openstack-meeting16:08
sridhar_ramtung_doan: how is your alarm monitoring coming along ?16:08
sridhar_ramtung_doan: any major issues blocking you ?16:08
tung_doansridhar: alarm monitor is almost done. https://review.openstack.org/#/q/status:open+project:openstack/tacker+branch:master+topic:tacker-alarming16:08
tung_doansridhar: i will need reviews latter16:09
sridhar_ramtung_doan: does this include ceilometer alarm driver ?16:09
tung_doansridhar: yes, sure16:09
*** eezhova has quit IRC16:10
*** klkumar has joined #openstack-meeting16:10
sridhar_ramtung_doan: sorry, i haven't looked closely.. which specific patchset has ceilometer related things ?16:10
tung_doansridhar: alarm framework is already lauched. But it still need to review16:10
tung_doansridhar: np. https://review.openstack.org/#/c/362975/16:10
*** dmorita has quit IRC16:11
*** dmorita has joined #openstack-meeting16:11
sridhar_ramtung_doan: i was looking for requirements.txt changes to pull in ceilometer client..16:11
sridhar_ramtung_doan: anyways, will review...16:12
*** trevormc has left #openstack-meeting16:12
sridhar_ramteam - need your help in the review of alarm mon..16:12
tung_doansridhar:  thanks16:12
sridhar_ramit is coming in late, so..16:12
sridhar_ramcan someone volunteer to work with tung_doan to go beyond code review to pull the patchset and verify the functinality .. while the patchsets are still out16:13
*** hasharAway is now known as hashar16:13
*** ljxiash has quit IRC16:13
jankisridhar_ram, I can help16:13
tung_doansridhar: thanks you guys.. I will try to modify if possible in the rest time16:13
*** diablo_rojo has joined #openstack-meeting16:14
sridhar_ramjanki: great, thanks..16:14
jankisridhar_ram, mention not :)16:14
tung_doansridhar: thanks janki16:14
sridhar_ramtung_doan: please watchout for issues reported by janki !!16:15
sridhar_rammoving on to...vnffg16:15
tung_doansridhar: sure.. it is important time for me16:15
tung_doansridhar: janki thank :)16:15
*** yamamoto has quit IRC16:15
sridhar_ramtrozet: s3wong: hi, can you give an update where we stand on this feature16:15
jankitung_doan, welcome :)16:15
*** ociuhandu has quit IRC16:15
*** adiantum has quit IRC16:15
*** armax has quit IRC16:16
trozetsridhar_ram: hello16:16
sridhar_ramtrozet: sorry, for the abrupt pull into the meeting  :)16:16
*** sudswas__ has quit IRC16:16
*** sudipto has quit IRC16:16
sridhar_ramtrozet: s3wong: trying to get a sense of what is remaining for this whole feature ..16:16
digasridhar_ram: it seems, we have very large patchset. it will be good if we can reduce patch size in the future16:16
trozetsridhar_ram: the plugin/ext side is almost done.  Need to get the abstract driver and janki's patch through (if not already done).  I then need to test the plugin with the client that was merged16:16
s3wongsridhar_ram: I am doing integration of driver with trozet's plugin16:17
trozetdiga: this was the preferred method16:17
sridhar_ramdiga: the blame is on me, to consolidate at slightly coarse grain level16:17
s3wongsridhar_ram: found some bugs (on my side), will post new patch sometime this week16:17
sridhar_ram*to ask them16:17
digatrozet: okay16:17
*** tonytan_brb has quit IRC16:17
jankitrozet, I have uploaded PS addressing the comments16:17
trozetsridhar_ram, s3wong: can we get the abstract driver taken care of? and janki's patch?16:17
s3wongtrozet: what's to take care of? merge?16:18
sridhar_ramtrozet: yes, those two are definitely close to land16:18
jankisridhar_ram, a separate error_response will be droppped by API layer. Also error_response column is not present in the client16:18
trozets3wong: for abstract driver need your review s3wong16:18
sridhar_ramjanki: understood, i was about to response.. let's skip error_reason for now16:18
sridhar_ram*respond16:19
jankisridhar_ram, yes. I do have an idea though. we can discuss that after meeting16:19
s3wongsridhar_ram, trozet: I am still the author of abstract driver, should I even +2 it :-)16:19
*** banix has joined #openstack-meeting16:19
sridhar_ramtrozet: in fact, even the plugin / db / extn side seems to have gotten enough eyeballs.. that patchset would be next (in this series)16:19
*** matrohon has quit IRC16:19
trozets3wong: haha i don't mean you have to +2...just feedback on what I posted16:19
trozets3wong: like is it ok or not16:20
*** lpetrut has joined #openstack-meeting16:20
*** natarajk has quit IRC16:20
sridhar_ramtrozet: beyond the plugin / ext, abstract driver, n-sfc implementation .. what is remaining to be posted ?16:21
*** david-lyle has quit IRC16:21
*** natarajk has joined #openstack-meeting16:21
*** natarajk has quit IRC16:21
s3wongsridhar_ram: that should be it --- it is end to end already with these16:21
trozetsridhar_ram: i need to do the real TOSCA validation of the VNFFGD16:22
trozetsridhar_ram: there are a few places where i have TODO (like validating all the VNFs are on the same VIM)16:22
sridhar_rams3wong: trozet: yes, the TOSCA portion is critical...16:22
*** natarajk has joined #openstack-meeting16:22
trozetsridhar_ram: but not too much other than testing everything together and seeing what doesnt work16:22
sridhar_ramtrozet: do you need substitution_mapping support for your TOSCA needs ?16:22
sridhar_rambobh: ^^16:22
trozetsridhar_ram: I think we decided on ignoring that for the first pass16:23
trozetsridhar_ram: to make things less complicated16:23
*** david-lyle has joined #openstack-meeting16:23
bobhtrozet: probably a good idea16:23
sridhar_ramtrozet: sure, thats a fine approach for this first iteration16:23
digatrozet: any help you need ? I hv some interest in VNFFG16:24
sridhar_rami believe we need that more for NSD and NSD + VNFFGD16:24
trozetdiga: I could use help testing the whole thing16:24
trozetdiga: once it's ready16:25
sridhar_rams3wong: any blockers for your n-sfc implementation ?16:25
digatrozet: sure16:25
s3wongsridhar_ram: no, other than day job :-)16:25
trozets3wong: heh16:25
sridhar_rams3wong: :)16:25
sridhar_ramdiga: similar to what janki is doing for alarm-mon, it will be great if can team up w/ these folks to give this a spin end-to-end with all the patchsets out .. that would be awesome16:26
digasridhar_ram: Sure. I will16:26
sridhar_ramtrozet: janki: haiwei: s3wong: sripriya: amazing tag teaming so far in executing this feature ..!16:26
jankisridhar_ram, thanks :)16:27
sridhar_ramBTW, a talk submission on this feature is accepted for barcelona summit..16:27
sridhar_ram#link https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/15335/orchestrating-vnf-forwarding-graphs-and-sfc-using-opendaylight-neutron-and-tacker16:27
digasridhar_ram: Absolutely, will like to work with trozet & s3wong for every help they need from my side reviewing, testing etc16:28
*** dmacpher has quit IRC16:28
sridhar_rameven more reason to finish this and show a kickass demo!16:28
*** esberglu has joined #openstack-meeting16:28
trozetyeah diga, if you also want to review 2k lines that would be helpful ;)16:28
sridhar_ramdiga: great, thanks!16:28
digatrozet: :)16:28
trozetsridhar_ram: i'll plan on picking up and pushing new changes thursday16:29
sridhar_rammoving on..16:29
*** Swami has joined #openstack-meeting16:29
trozetsridhar_ram: so if we can get abstract driver and vnf resources done by then, i twill reduce hte number of moving parts under me16:29
s3wongtrozet: Thursday sounds good16:29
sridhar_ramtrozet: absolutely.. we can take care of them in a day16:29
*** matthewbodkin has quit IRC16:30
s3wong(someone else needs to give a +2 on abstract-driver)16:30
sridhar_rams3wong: if you can review trozet's updates to your abstract driver .. we are good to go16:30
trozetthanks16:30
s3wongsridhar_ram: sure --- still not appropriate to give a +2 :-)16:30
*** e0ne has quit IRC16:31
sripriyas3wong: will review the patch16:31
*** rbak has quit IRC16:31
*** unicell has quit IRC16:31
s3wongsripriya; Thanks!16:31
sridhar_rams3wong: understood.. just leave a note to us in the irc channel16:31
sridhar_ramnext, ... VNFC16:31
sridhar_ram#link https://review.openstack.org/#/c/339798/16:32
*** rbak has joined #openstack-meeting16:32
manikanta_tadiFor VNFC BP, We have pushed a WIP patch already  https://review.openstack.org/#/c/358321/16:32
*** Leo_ has quit IRC16:32
manikanta_tadireview of spec is ongoing,16:32
*** hockeynut has quit IRC16:33
sridhar_rammanikanta_tadi: we need more folks to review this...16:33
sridhar_rammike_m: your comments are quite helpful ..16:33
manikanta_tadithe tasks still left are sample templates,devref, functional tests which myself and tbh are taking up16:33
sridhar_rambobh: did you had a chance to look at this spec ?16:33
bobhsridhar_ram: briefly - I'll take another look16:34
manikanta_tadibobh, Thanks ..16:34
sridhar_ramI'm looking for bit more consensus on where we are heading .. even if we implement just a portion of the whole thing16:34
*** natarajk has quit IRC16:34
*** ivar-lazzaro has joined #openstack-meeting16:35
*** anilvenkata_afk has quit IRC16:35
mike_mI have a concern with the VNF requirement of needing the heat api agent.16:35
sridhar_ramI do realize this is a "new" feature that seems to slide in .. we can bring this in as an "experimental" feature in newton16:35
sridhar_rammike_m: can you elaborate pls?16:35
*** david-lyle_ has joined #openstack-meeting16:36
mike_mi was wondering of a more agnostic approach for the VNF.  This makes the feature very OpenStack VNF specific.16:36
sridhar_rammike_m: couldn't agree more..16:37
bobhsridhar_ram: mike_m me too16:37
mike_mI see the cloud-init as the only viable approach in this short period of time.  Couldn't that satisify the initial startup requirements?16:37
sridhar_rammike_m: we absolutely want Tacker be a TOSCA Orchestrator engine .. for multiple VIM types (openstack, vmware, aws, etc) and for NFV and beyond (like enterprisey use-cases)16:38
*** iyamahat has quit IRC16:38
sridhar_rammike_m: we already support cloud-init in Tacker's TOSCA in the form of user-data..16:38
*** Nayana_ has joined #openstack-meeting16:39
*** uxdanielle has quit IRC16:39
*** Sukhdev has quit IRC16:39
*** electrofelix has quit IRC16:39
*** yamahata has quit IRC16:39
*** david-lyle has quit IRC16:39
bobhsridhar_ram: but user_data could easily be mapped to a different VIM without requiring specific changes to the image16:39
mike_mLooking at this at a different angle, do you think the config of a VNF/VNFC might be more related to the EM interface?16:40
bobhsridhar_ram: if a VNF relies on specific Heat functionality for creation, it is pretty much tying itself to OpenStack anyway16:40
sridhar_rambobh: you make use of the fact cloud-init is supported in different VIMs, agree but it can't support mid-life vnfc install / uninstall16:40
*** roxanaghe has quit IRC16:40
bobhsridhar_ram: agree, do we know of similar capabilities in other VIMs?16:41
*** roxanaghe has joined #openstack-meeting16:41
mike_mIn some respects, mid-life management might be more related to em.16:41
sridhar_rambobh: cloud-init is supported in many VIMs - definitely vmware and aws16:41
bobhsridhar_ram: was thinking about the heat-specific config resources - SoftwareDeployment/SoftwareCOnfig/etc16:42
sridhar_rambobh: back to your question on making this heat specific, that is why i want to see this spec talk more about the VNFC changes in TOSCA and plugin and *most importantly* describe an abstract interface from plugin to infra_driver..16:42
sridhar_rambobh: .. it is upto the infra_driver to use any available mechanism -- cloud-init, ssh, SoftwareDeployment, etc16:43
*** haruma has joined #openstack-meeting16:43
sridhar_rammike_m: my understanding is EM aspects comes once the VNFC s/w is in place in the target VDU..16:43
bobhsridhar_ram: right, which I was uncomfortable with specifying the heat driver in the VNFC config16:43
*** egallen has quit IRC16:43
*** egallen has joined #openstack-meeting16:43
sridhar_rammike_m: but we need to get the bits in place first and that is what we need some clarity16:44
*** roxanaghe_ has joined #openstack-meeting16:44
*** vishwanathj_ has joined #openstack-meeting16:44
sridhar_rambobh: agree, that part doesn't gel for me as well..16:44
mike_magree16:44
*** shashank_hegde has quit IRC16:45
sridhar_ramif we scope this work to describe TOSCA VNFC dom will be given to infra_driver and infra_driver will take care of honoring it (or erroring out as un-supported) would that be okay for this initial attempt?16:46
sridhar_ramplugin and TOSCA part doesn't (and shouldn't) know about SoftwareDeployement happening underneath16:47
mike_mthat sounds like the right approach to me16:47
*** roxanaghe has quit IRC16:47
*** roxanaghe__ has joined #openstack-meeting16:47
bobhsridhar_ram: agree - and the TOSCA shouldn't tell the orchestrator which infra to use16:47
manikanta_tadisridhar_ram, agree, this sounds good to me too16:47
sridhar_rambobh: mike_m: fair enough..!16:48
sridhar_rammanikanta_tadi: please incorporate these in the spec and let's see how far we can push :)16:48
*** comay has quit IRC16:48
manikanta_tadisridhar_ram: Sure, will make the changes accordingly16:48
sridhar_rammanikanta_tadi: continue to iterate these in your WIP patchsets16:48
sridhar_ramalright.. moving on..16:49
*** egallen has quit IRC16:49
sridhar_ram#topic Ocata Feature Grooming16:49
*** openstack changes topic to "Ocata Feature Grooming (Meeting topic: tacker)"16:49
*** Ravikiran_K has quit IRC16:49
*** haruma has left #openstack-meeting16:49
sridhar_ramI'd like to kick start Ocata feature planning in the background as we wrap up Newton16:49
*** raildo has joined #openstack-meeting16:50
sridhar_ramas usual there is going to be a etherpad ..16:50
*** egallen has joined #openstack-meeting16:50
sridhar_ram.. no surprise there, but i've left it empty this time :)16:50
sridhar_ram#link https://etherpad.openstack.org/p/tacker-ocata-grooming16:51
*** roxanaghe_ has quit IRC16:51
sridhar_rambased on the midcycle and other recent discussions ..16:51
*** bobh has quit IRC16:52
sridhar_ramI'd like to propose a decomposed vim-infra driver framework as one of the top items for next cycle16:52
digasridhar_ram: I am writting one spec for new API framework implementation like we discussed last time, will submit it to ocata repo. I have done enough study on that16:52
mike_mhas there been more discussions regarding this one: https://blueprints.launchpad.net/tacker/+spec/em-module? Could this be added as a potential for Ocata?16:52
sridhar_ramplease capture the items you think that is important for Ocata16:52
*** gyee has quit IRC16:53
*** hashar is now known as hasharAway16:53
sridhar_ramdiga: sure, that's great16:53
*** galstrom is now known as galstrom_zzz16:53
*** _nadya_ has quit IRC16:53
sridhar_rammike_m: yes, that be taken up as well..16:53
*** pradk has quit IRC16:53
*** pradk- has joined #openstack-meeting16:53
digasridhar_ram: yep16:53
sridhar_ramit will be also nice to come up w/ a relative priority among different items16:54
*** reed has quit IRC16:54
*** reed has joined #openstack-meeting16:54
sridhar_ramcapturing in the blueprint is definitely a better option16:54
sridhar_ramwe can use the etherpad to socialize the idea16:54
digasridhar_ram: +116:55
sridhar_ramwe will obviously have few carry overs from newton.. like NSD16:55
*** gyee has joined #openstack-meeting16:55
mike_mno bp yet, but vmware vim.16:55
mike_mlikely a long shot for now, but certainly can be discussed.16:56
*** anilvenkata has joined #openstack-meeting16:56
sridhar_rammike_m: sure, in fact i noticed there is a oslo.vmware ..16:56
sridhar_ram#link https://github.com/openstack/oslo.vmware16:56
manikanta_tadisridhar_ram, OSC support ?16:56
sridhar_ramsomething we can leverage16:56
mike_mI saw that, was wondering the same.16:56
sridhar_rammanikanta_tadi: yes, but relative priority will be low IMO16:57
*** erlon has quit IRC16:57
digamike_m: sridhar_ram : I think lets have seperate etherpad for vmware vim, we can list out all in detail there16:57
dkushwahasridhar_ram, so, can we start for ocata now?16:57
mike_mok16:57
*** unicell has joined #openstack-meeting16:57
sridhar_ramdiga: yes, vmware vim will be biggee..16:57
*** sripriya has quit IRC16:57
*** iyamahat has joined #openstack-meeting16:58
digasridhar_ram: yeah16:58
sridhar_ramdkushwaha: yes, the spec work can start.. the patchsets can merge only after stable/newton is pulled.. roughly after Sept 15th16:58
sridhar_ramdkushwaha: can you please update ur NSD patchset to ocata dir ?16:58
*** hynekm has joined #openstack-meeting16:58
dkushwahasridhar_ram, yes sure16:59
*** hynekm has left #openstack-meeting16:59
sridhar_ramalright, let's continue to groom this Ocata list over next few meetings..16:59
sridhar_ramtime's almost up16:59
sridhar_ramuse the etherpad to capture any ideas to be entertained for Ocata.. it could be features or code clean17:00
sridhar_ramthats it17:00
sridhar_rambye folks17:00
sridhar_ram#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Tue Aug 30 17:00:13 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
digabye17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-08-30-16.01.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-08-30-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-08-30-16.01.log.html17:00
*** dkushwaha has left #openstack-meeting17:00
*** rasca has quit IRC17:00
*** sdague has quit IRC17:00
*** s3wong has quit IRC17:01
*** sdague has joined #openstack-meeting17:01
*** Leo_ has joined #openstack-meeting17:01
*** raj_singh_ has joined #openstack-meeting17:01
*** raj_singh_ has left #openstack-meeting17:01
*** su_zhang has joined #openstack-meeting17:01
*** egallen has quit IRC17:02
*** hieulq_ has joined #openstack-meeting17:02
*** _nadya_ has joined #openstack-meeting17:03
*** pradk- is now known as pradk17:03
*** su_zhang has quit IRC17:03
*** Apoorva has joined #openstack-meeting17:03
*** su_zhang has joined #openstack-meeting17:04
*** anilvenkata_ has joined #openstack-meeting17:04
*** ilyashakhat has joined #openstack-meeting17:04
*** su_zhang has quit IRC17:04
*** esberglu has quit IRC17:04
*** su_zhang has joined #openstack-meeting17:05
*** _nadya_ has quit IRC17:05
*** manikanta_tadi has quit IRC17:05
*** anilvenkata has quit IRC17:06
*** unicell has quit IRC17:06
*** sindhu has quit IRC17:09
*** su_zhang has quit IRC17:11
*** SridarK has quit IRC17:11
*** ijw has joined #openstack-meeting17:11
*** su_zhang has joined #openstack-meeting17:11
*** rcernin has quit IRC17:12
*** amakarov is now known as amakarov_away17:12
*** klkumar has quit IRC17:12
*** tesseract- has quit IRC17:14
*** Suyi_ has joined #openstack-meeting17:14
*** esberglu has joined #openstack-meeting17:15
*** su_zhang has quit IRC17:16
*** yamamoto has joined #openstack-meeting17:16
*** asettle has quit IRC17:16
*** asettle has joined #openstack-meeting17:17
*** tonytan4ever has joined #openstack-meeting17:18
*** Nayana_ has quit IRC17:19
*** sarob has joined #openstack-meeting17:19
*** hieulq_ has quit IRC17:19
*** sandanar_ has joined #openstack-meeting17:21
*** natarajk has joined #openstack-meeting17:21
*** yamamoto has quit IRC17:22
*** tung_doan has quit IRC17:22
*** tonytan4ever has quit IRC17:23
*** ijw has quit IRC17:24
*** cartik has quit IRC17:24
*** tesseract- has joined #openstack-meeting17:24
*** sandanar has quit IRC17:24
*** neel has quit IRC17:24
*** pcaruana has quit IRC17:25
*** ijw has joined #openstack-meeting17:25
*** diga has quit IRC17:25
*** bobh has joined #openstack-meeting17:26
*** _nadya_ has joined #openstack-meeting17:26
*** sdake has joined #openstack-meeting17:27
*** tesseract- has quit IRC17:28
*** tonytan4ever has joined #openstack-meeting17:29
*** bobh_ has joined #openstack-meeting17:32
*** s3wong has joined #openstack-meeting17:32
*** liamji has quit IRC17:32
*** xiaohhui has quit IRC17:32
*** su_zhang has joined #openstack-meeting17:32
*** galstrom_zzz is now known as galstrom17:34
*** ivar-laz_ has joined #openstack-meeting17:34
*** bobh has quit IRC17:35
*** egallen has joined #openstack-meeting17:35
*** su_zhang has quit IRC17:35
*** csomerville has joined #openstack-meeting17:35
*** vhoward has quit IRC17:36
*** su_zhang has joined #openstack-meeting17:36
*** Patifa has quit IRC17:36
*** ivar-lazzaro has quit IRC17:37
*** asettle has quit IRC17:37
*** cody-somerville has quit IRC17:38
*** Patifa has joined #openstack-meeting17:38
*** NishaYadav has joined #openstack-meeting17:39
*** cody-somerville has joined #openstack-meeting17:40
*** dmorita has quit IRC17:40
*** csomerville has quit IRC17:42
*** hockeynut has joined #openstack-meeting17:42
*** unicell has joined #openstack-meeting17:42
*** prateek_ has joined #openstack-meeting17:42
*** ivar-laz_ has quit IRC17:43
*** dmorita has joined #openstack-meeting17:43
*** ivar-lazzaro has joined #openstack-meeting17:43
*** jaugustine_ has joined #openstack-meeting17:43
*** _nadya_ has quit IRC17:43
*** shashank_hegde has joined #openstack-meeting17:44
*** jaugustine has quit IRC17:44
*** jaugustine_ is now known as jaugustine17:44
*** sripriya has joined #openstack-meeting17:44
*** jamemcc has joined #openstack-meeting17:44
*** prateek has quit IRC17:46
*** lpetrut has quit IRC17:46
*** sripriya has left #openstack-meeting17:48
*** sarob has quit IRC17:49
*** sarob has joined #openstack-meeting17:51
*** eezhova has joined #openstack-meeting17:53
*** markvoelker has joined #openstack-meeting17:54
*** adiantum has joined #openstack-meeting17:54
*** natarajk has left #openstack-meeting17:54
*** sarob has quit IRC17:55
*** browne has joined #openstack-meeting17:56
*** roxanaghe_ has joined #openstack-meeting17:59
*** baoli has quit IRC17:59
*** asettle has joined #openstack-meeting17:59
*** dmorita has quit IRC17:59
bretono/17:59
*** baoli has joined #openstack-meeting18:00
stevemaro/18:00
*** su_zhang has quit IRC18:00
stevemar#startmeeting keystone18:00
openstackMeeting started Tue Aug 30 18:00:32 2016 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
openstackThe meeting name has been set to 'keystone'18:00
jaugustineheyo18:00
stevemarbreton: it's 16 weeks18:00
browneo/18:00
dstaneko/18:00
rodrigodso/18:01
rderoseo\18:01
bknudsonhi18:01
*** Sukhdev has joined #openstack-meeting18:01
*** roxanaghe has joined #openstack-meeting18:01
*** e0ne has joined #openstack-meeting18:01
lbragstado/18:01
*** esberglu has quit IRC18:01
stevemarshort agenda again!18:02
stevemarhttps://etherpad.openstack.org/p/keystone-weekly-meeting18:02
bretonstevemar: thanks, sounds good18:02
NishaYadavo/18:02
*** roxanaghe__ has quit IRC18:02
stevemarif anyone has anything to add to the agenda, do so now18:03
stevemaror wait til open discussion18:03
*** sandanar_ has quit IRC18:03
ayoungping list?18:03
*** anilvenkata_ has quit IRC18:03
stevemarayoung: yes sir!18:03
stevemarping ajayaa, amakarov, ayoung, breton, browne, crinkle, claudiub, davechen, david8hu, dolphm, dstanek, edmondsw, gagehugo, gyee, henrynash, hogepodge, htruta, jamielennox, jaugustine, joesavak, jorge_munoz, knikolla, lbragstad, MaxPC, morgan, nkinder, notmorgan, raildo, rodrigods, rderose, roxanaghe, samleon, samueldmq, shaleh, stevemar, tsymanczyk, topol, vivekd, wanghong, xek, nishaYadav18:03
raildoo/18:04
*** roxanaghe_ has quit IRC18:04
xeko/18:04
samueldmqhi all18:04
knikollao/18:04
*** Sukhdev has quit IRC18:04
topolo/18:04
stevemar#topic milestone-3 status18:05
NishaYadav\o18:05
*** openstack changes topic to "milestone-3 status (Meeting topic: keystone)"18:05
*** amakarov has joined #openstack-meeting18:05
*** dmorita has joined #openstack-meeting18:05
*** tesseract- has joined #openstack-meeting18:05
*** banix has quit IRC18:05
stevemardstanek's fix for caching merged, that was a huge win18:05
*** tesseract- has quit IRC18:05
*** tesseract- has joined #openstack-meeting18:06
stevemardoes anyone know if it also fixes https://bugs.launchpad.net/bugs/1600393 and https://bugs.launchpad.net/bugs/1600394 ?18:06
openstackLaunchpad bug 1600393 in OpenStack Identity (keystone) "v2.0 catalog seen in v3 token" [Critical,Confirmed] - Assigned to David Stanek (dstanek)18:06
amakarovdstanek: now how about backport it? ))18:06
dstanekstevemar: you mean caching works now :-P18:06
openstackLaunchpad bug 1600394 in OpenStack Identity (keystone) "memcache raising "too many values to unpack"" [Critical,Confirmed] - Assigned to David Stanek (dstanek)18:06
stevemarhehe18:06
dstanekamakarov: sure, i can do that after this last pass at lbragstad's review18:06
*** john-davidge has quit IRC18:06
*** banix has joined #openstack-meeting18:06
stevemarbreton: i think you mentioned it also solved one of those bugs?18:06
*** nisha_ has joined #openstack-meeting18:07
*** NishaYadav has quit IRC18:07
stevemari suppose we could mark them as incomplete and ask the originator to check with the master branch if it's still an issue18:07
bknudsonI don't see how this would fix either of those bugs.18:07
*** nisha_ is now known as nishaYadav18:07
*** shaleh has joined #openstack-meeting18:07
*** spzala has joined #openstack-meeting18:07
shaleh\o18:07
bknudsonthe problems there aren't because the cache wasn't flushed correctly18:08
*** salv-orl_ has joined #openstack-meeting18:08
*** tesseract- has quit IRC18:08
stevemarbknudson: for both bugs or are you referring to one in particular?18:09
samueldmqbknudson: ++, those do not seem to be related to me either18:09
amakarovstevemar: is my oslo.cache solution still required? Does somebody else use memcache besides keystone?18:09
*** uxdanielle has joined #openstack-meeting18:09
samueldmqstevemar: dstanek: has anybody else got to reproduce those bugs ?18:10
bknudson stevemar: both of those bugs.18:10
* notmorgan is lurking at best18:10
bknudsonalthough I've never seen the v2.0 catalog seen in v3 token issue18:10
*** Apoorva has quit IRC18:10
*** yamahata has joined #openstack-meeting18:10
bknudsonamakarov: apparently there other users of oslo.cache besides keystone.18:10
*** comay has joined #openstack-meeting18:10
amakarovnotmorgan: do you know what projects use oslo.cahe too?18:10
*** Apoorva has joined #openstack-meeting18:10
*** tesseract- has joined #openstack-meeting18:10
stevemarbknudson: if flushing the cache solves the issue, then it sounds like we don't need a keystone fix?18:10
*** jamielennox has joined #openstack-meeting18:11
notmorganamakarov: none in the way we do. most use the in-mem old compat memcache dict thing18:11
*** salv-orlando has quit IRC18:11
dstaneki don't think my fix could possibly fix some of the weird bugs we are seeing18:11
bknudsonstevemar: flushing the cache won't fix the "too many values to unpack" bug.18:12
notmorganbknudson: that is the wierdest bug18:12
*** diablo_rojo has quit IRC18:12
*** jungleboyj has quit IRC18:12
notmorganbecause the error comes from the memcache lib18:12
notmorganso weird.18:12
bknudsonnotmorgan: still looking at it. I'm going to add some tracing to python-memcached18:12
amakarovdstanek: you'd become a silver bullet author in that case ))18:12
notmorganbknudson: ++18:12
bknudsonnotmorgan: should be able to see exactly what it's reading from memcache socket18:13
dstanekamakarov: one could only wish18:13
*** _nadya_ has joined #openstack-meeting18:13
stevemarwell at any rate, it sounds like neither will be solved for milestone 318:13
dstaneki couldn't replicate the others in my local environment to debug18:13
stevemarconsidering it will be tagged tomorrow...18:13
*** tonytan4ever has quit IRC18:13
samueldmqstevemar: we can tag and work in a fix -> backport18:14
*** parora has joined #openstack-meeting18:14
stevemaryep18:14
*** tonytan4ever has joined #openstack-meeting18:14
stevemarokay, i'll bump those 218:14
stevemarnotmorgan: bknudson what about https://bugs.launchpad.net/bugs/1609566 and https://review.openstack.org/#/c/358872/ ?18:15
openstackLaunchpad bug 1609566 in OpenStack Identity (keystone) "500 error from revocation event deserialize" [Medium,In progress] - Assigned to Morgan Fainberg (mdrnstm)18:15
bknudsonI think those are all the same bug18:15
notmorganbknudson: nope.18:15
bknudsonsame cause18:15
notmorganbknudson: not the deserialie one18:15
bretonyep, 1609566 is unrelated18:15
stevemarright18:15
notmorganthat one is actually a different issue, looks like it's getting non-strings back out18:16
*** jamielennox has left #openstack-meeting18:16
stevemardstanek: you had a -1 on it18:16
notmorganstevemar: a rebase should be all that patch needed, since it;'s partial-bug18:16
notmorganthere is longer term stuff to be done there but it will squash the issue more directly and give us feedback18:16
dstanekstevemar: which one?18:16
stevemardstanek: https://review.openstack.org/#/c/358872/18:17
*** prateek_ has quit IRC18:17
notmorgani don't think we can only serialize rthe keys we want atm, no guarantee that is correct. if anything we also need the filter on the deserialie+logging18:17
dstanekah, yeah. i don't see why we store it in memcache if we can serialize it. i'd rather fix on the flip side18:17
*** anilvenkata_ has joined #openstack-meeting18:18
dstanekwe're serializing __dict__ which is bad18:18
notmorgandstanek: what worries me is that this suddenly started being an issue, I don't know what refactor broke it.18:18
stevemarrebased it18:19
dstaneknotmorgan: is it reproducible?18:19
*** Na3iL has quit IRC18:19
amakarovSpeaking of 1609566, we've run into issue when revocation tree grows larger 1M and gets declined by memcache. It doesn't prodice an error though - just returns NO_VALUE on the next GET operation18:19
notmorgandstanek: it has been in isolated environemnts.18:19
notmorgandstanek: it's just another weird edge cases18:19
bknudsonI can probably recreate https://bugs.launchpad.net/bugs/160956618:19
openstackLaunchpad bug 1609566 in OpenStack Identity (keystone) "500 error from revocation event deserialize" [Medium,In progress] - Assigned to Steve Martinelli (stevemar)18:19
notmorganamakarov: welcome to memcache18:19
bknudsonbut I get other errors too when I try to recreate anything18:19
notmorganamakarov: that has been a long running issue with using memcache and lists of objects18:20
dstanekamakarov: yep, that's the expected behavior :-(18:20
notmorganamakarov: if you're hitting that, restart memcache with a larger slab size =/18:20
amakarovnotmorgan: yes, we had to do that18:20
bknudsonis someone working on the issue with querying revocation events?18:20
*** toscalix has quit IRC18:20
lbragstadbknudson ravelar is working on that a bit18:21
bknudsonI think there's a review in progress but it's a POC18:21
dstaneknotmorgan: amakarov: but first do some performance analysis to make sure the change does negatively impact what you can cache18:21
lbragstadspecifically on optimizing the sql query18:21
bknudsonI think it would help everyone if that was completed18:21
amakarovalso I think we're doing smth wrong if we end up tossing cicterns of data here and there18:21
*** ravelar1 has joined #openstack-meeting18:21
notmorgandstanek: larger than 1M slab size is a horrible thing to do to memcache and will absolutely make for bad performance (relative)18:21
amakarovs/cicterns/cisterns/18:21
lbragstadspeaking of ravelar118:22
lbragstadthere he is18:22
*** markvoelker has quit IRC18:22
samueldmqlbragstad: has ravelar posted anything already?18:22
notmorganamakarov: this is really a known issue.18:22
dstaneksamueldmq: i believe there is a wip18:22
lbragstadravelar1 I believe you have a review up for your work on the revocation event sql query, right?18:22
*** janki has quit IRC18:22
bknudsonon my system I see huge slowdowns with only a few revocation events.18:22
notmorganamakarov: and one of the only places we are storing a list of elements in cache.18:22
stevemardstanek: so you'll still be -1 on this? rather fix it than ignore the errors? (mind you it's just a partial fix)18:22
notmorganamakarov: there is a reason we don't cache other "list" methods18:22
amakarovsamueldmq: btw my token pre-cache patch is really useful in the case ^^18:22
bknudsonand in our staging envs we're getting a lot of complaints about the revocation event slowdown.18:23
lbragstadbknudson same here... i notice performance degradation after just a few tempest runs (~1500 events)18:23
dstanekstevemar: i'd have to go over it again at +1 as a temp fix. my concern is that we could throw out an importatnt key18:23
notmorgani hate to admit it, but the horrible tree code at least wasn't broken all over the place18:23
dstaneki'd have to look to see if that is possible18:23
bknudsoneven to build the tree you need to fetch every row18:23
notmorgandstanek: we could, it is better to fail securely and reject more tokens than to pass invalid tokens (if we maintain revocations as a thing)18:24
amakarovbknudson: what's the story with in-database revocation check?18:24
notmorganbknudson: yes. i mean the associated bugs.18:24
bknudsonseems like we should be able to take advantage of the "since" part of the query (if we kept the list in mem)18:24
amakarovayoung: ^18:24
ravelar1There are a few issues I have been running into with trying to change the current is_revoked and matches to query but they mainly stem from tox tests that solely test based on premade event dictionaries18:24
dstaneki don't understand how we get a non-string key to begin with18:24
*** sarob has joined #openstack-meeting18:24
ayoungKill it.18:24
notmorgandstanek: something in one of the refactors to revocations and serialization broke it.18:24
notmorgandstanek: and i can't point a finger at why/where.18:25
*** su_zhang has joined #openstack-meeting18:25
bknudsonhere's the review: https://review.openstack.org/#/c/359371/18:25
notmorgandstanek: i've now spent days working through the code. so in short, i just opted for somerthng that breaks less but makes a lot of noise so we get feedback18:25
bknudsonfor making the revocation check an sql query18:26
notmorganbknudson: ++ i would like to see that if we keep revocations.18:26
*** su_zhang has quit IRC18:26
bknudsonClint Byrum was interested. Wanted to see indexes on the columns.18:26
notmorganand he is correct18:26
*** rrecio has joined #openstack-meeting18:26
notmorganwe should index the columns18:26
ayoungwe should drop the whole damn thing18:26
notmorgani think i said the same thing early on in these discussions18:26
bknudsony, otherwise you do a table scan anyways18:26
stevemarsounds like this bug can make the cut, at least the partial fix can18:27
*** egallen has quit IRC18:27
*** pvaneck has joined #openstack-meeting18:27
rodrigodsis there an evidence that the issue is the python code?18:27
lbragstadis SpamapS around?18:27
ayoungNewton Release Note:  Tokens can no longer be revoked.18:27
ayoungDOne.18:27
notmorganayoung: convince stevemar, i'm fine with it but convince stevemar18:27
notmorganayoung: since he's PTL18:27
notmorgani think the ops community will be in an uproar18:27
*** asettle has quit IRC18:27
stevemarnot the right time, i just want to get newton-3 done18:28
notmorganbecause there is no way to lock out tokens without timeout in cases .18:28
amakarovyes! 5 minutes tokens ftw!18:28
dstaneknotmorgan: the only thing i can think of as being a possible scenario is somehow __dict__ is getting directly manipulated18:28
notmorgandstanek: possibly, i am actually thinking of making the reveent not an object anymore18:28
notmorgandstanek: and make it a primitive if we keep it18:28
SpamapSlbragstad: I'm around. what's up?18:28
notmorgandstanek: then we drop the custom msgpack serializer18:28
notmorgandstanek: trivial18:28
ayoungnotmorgan, ?18:28
lbragstadSpamapS you were looking to have a discussion around indexes here - https://review.openstack.org/#/c/359371/ ?18:29
bknudsonif you want to set up a dev environment where you can reproduce these problems I can provide instructiona.18:29
SpamapSlbragstad: I'll look right now.18:29
ayoungrevocation as a primitive...?18:29
lbragstadSpamapS we have ravelar1 here, too18:29
notmorganayoung: make it a dict (eeeeuuwwW) and it'll be less janky serializing [if we don't drop it]18:29
SpamapSOh cool18:29
ayoungnotmorgan, ++18:29
SpamapSok I already looked at that yesterday, yay. :)18:29
*** sarob has quit IRC18:29
notmorganSpamapS: yeah we were saying we agree, indexes18:29
ayoungnotmorgan, lets make it a dict.  Nothing wrong with that.18:29
notmorganSpamapS: :)18:29
SpamapSI just want to see an assertion of which existing index, or new index, will service the query.18:29
*** sarob has joined #openstack-meeting18:30
notmorganayoung: ok i'll roll that today then. but it'll be a backport for RC18:30
ayoungit is just a Data transfer object.  If we say "any fields but these are ignored" we should be OK18:30
notmorganor wait18:30
notmorganuh18:30
notmorganwhatever18:30
*** tesseract- has quit IRC18:30
notmorganit'll be the post n-318:30
SpamapSI trust mysql's optimizer to sometimes pick better ones than we _think_ will be used.18:30
ayoungand "all fields must be serializable"18:30
stevemarnotmorgan: yes, thats the one ;)18:30
*** tongli has joined #openstack-meeting18:30
*** tesseract- has joined #openstack-meeting18:30
SpamapSBut we should at least think about which ones we think should make it go fast.18:30
dstanekbknudson: yes, please18:30
notmorganSpamapS: oh i 100% agree here.18:30
*** tesseract- has quit IRC18:30
stevemarcan i move on to the blueprints?18:31
notmorganayoung: we wont be able to drop msgpack because datetime doesn't serialize the way we need it in json18:31
bknudsondstanek: here's the instructions: https://review.portbleu.com/gitweb?p=pyrrrat-ci.git;a=blob;f=docs/deploy-vagrant.rst;h=0cbe2a128c17b57753b168cc5990512712e834f9;hb=HEAD18:31
notmorganayoung: but we can just make rev event a dict and call it a day18:31
*** tesseract- has joined #openstack-meeting18:31
ayoungnotmorgan, if that works, I am fine with it18:31
stevemarravelar1 + bknudson to fix revocation :)18:32
stevemartempted to #action that one18:32
*** flwang1 has quit IRC18:32
*** mickeys has quit IRC18:32
stevemar#topic blueprints still tagged for newton-318:33
*** openstack changes topic to "blueprints still tagged for newton-3 (Meeting topic: keystone)"18:33
dstanekbknudson: thx18:33
stevemarwe've got https://blueprints.launchpad.net/keystone/+spec/credential-encryption and https://blueprints.launchpad.net/keystone/+spec/pre-cache-tokens still tagged for newton318:33
*** ivar-lazzaro has quit IRC18:33
stevemarprecache tokens first for amakarov18:33
*** _sarob has joined #openstack-meeting18:34
*** ilyashakhat has quit IRC18:34
stevemarthe spec was approved, the code is up https://review.openstack.org/#/c/309146/18:34
*** flwang1 has joined #openstack-meeting18:34
stevemardstanek: you're -1 on it, and so is haneef18:34
dstanekafter talking to amakarov i think i'll take the -1 away18:35
stevemarnotmorgan opinion on this one? your views are always appreciated18:35
ravelar1notmorgan: which column is consistent enough to index?18:35
amakarovsamueldmq, dstanek, haneef: In the discussion above was the point that validation gets slow if revocation tree grows large18:35
amakarovthat's the value of the patch18:35
henrynash(sneaks in the back door)18:35
dstaneki wasn't completely sure on the overall value since i reuse tokens. this would only really help those that never reuse tokens18:35
* dstanek welcomes henrynash to the party18:36
bknudsonback from bank holiday18:36
stevemarhenrynash: you carried an entire door with you?18:36
*** anilvenkata_ has quit IRC18:36
ayoungstevemar, it was a doggy door.18:36
*** piet has quit IRC18:36
henrynasha man's gotta do what a man's gotta do18:36
dstanekamakarov: my biggest concern is the extra invalidations. not sure what the impact would be for those18:36
*** yamahata has quit IRC18:37
amakarovdstanek: we cache tokens in KMW anyway18:37
*** sarob has quit IRC18:37
*** tesseract- has quit IRC18:37
amakarovdstanek: oh, didn't get your point: you are about chenges that cause cache region to die18:38
dstanekamakarov: but your pre-caching in keystone so i'm wondering how often one of those operations happen that invalidate *all* the tokens18:38
bknudsonwhat if there was a config option to enable pre-caching of tokens?18:38
stevemarbknudson: would that make you sleep better at night?18:39
bknudsonthen if you think it'll help you then go ahead and enable it18:39
amakarovbknudson: 'caching=true' ))18:39
dstanekbknudson: options are usually a good thing18:39
stevemaramakarov: i don't think bknudson's ask is too much18:39
stevemaramakarov: think you can whip it up?18:39
amakarovstevemar: I have no problem with making that configurable18:40
dstanekamakarov: is there any way to say what the negative impact might be from real production cloud data?18:40
amakarovstevemar: iiuc the question is the value of the whole thing18:40
*** sindhu has joined #openstack-meeting18:40
bknudsonyou can propose removing the config option next release18:41
amakarovdstanek: our scale team agreed this won't do any harm18:41
*** mtanino has joined #openstack-meeting18:41
dstanekamakarov: so not many of those action actually happen?18:41
bknudsonI suspect it will be fine to do and we'll enable it but I'd want to see the performance results first.18:41
stevemar#action amakarov to make precaching configurable18:42
amakarovbknudson: shall we discuss a test case you'd like to see?18:42
amakarovout of the meeting probably18:42
*** tonytan_brb has joined #openstack-meeting18:42
*** Apoorva has quit IRC18:43
*** myoung is now known as myoung|bbl18:43
dstanekamakarov: what happens when a trust is deleted for instance18:43
amakarovdstanek: approximately as many as those causing token revocations18:43
*** su_zhang has joined #openstack-meeting18:43
amakarovdstanek: ..it happens :) regions gets invalidated18:43
bknudsonI'm not going to have the time to try it myself until I get through a bunch of other issues.18:43
bknudsonnobody here is complaining about this since we're hitting the issue with revocation events18:44
stevemaron to credential encryption...18:44
lbragstad#link https://review.openstack.org/#/c/355618/18:44
stevemarlbragstad: https://blueprints.launchpad.net/keystone/+spec/credential-encryption18:44
ayoungUSE TLS18:44
ayoungAnd X509 auth18:44
lbragstad^ that change is dependent on a couple devstack changes18:45
*** dmorita has quit IRC18:45
lbragstad(which are linked in the commit message)18:45
*** lpetrut has joined #openstack-meeting18:45
stevemarayoung: it's more so admins can't do a database dump and look at all your stufff18:45
*** su_zhang has quit IRC18:45
lbragstadbut it's passing - and I'm working on a migration guide now18:45
lbragstadI'm about half done and expect to have it completed by the end of the day18:45
*** tonytan4ever has quit IRC18:45
*** Apoorva has joined #openstack-meeting18:45
dstanekamakarov: with my patch merged we'll actualy start invalidating regions for real, which is part of my concern18:45
lbragstadnothing formal, just a gist showing what the upgrade looks like, along with the new upgrade process18:45
ayoungstevemar, Huh?  I thought it was for config files.18:45
stevemarayoung: nope18:45
*** Leo_ has quit IRC18:45
lbragstadbut - with that, I think the biggest hangup is now on triggers...18:46
stevemarayoung: it's for the credentials backend18:46
amakarovdstanek: your patch will save a lot of headache!18:46
ayoungah18:46
*** _nadya_ has quit IRC18:46
ayoungok...18:46
* ayoung goes back to LDAP land18:46
stevemarhehe18:46
lbragstadI'm working on the guide here - https://gist.github.com/lbragstad/ddfb10f9f9048414d1f781ba006e95d118:47
*** dmorita has joined #openstack-meeting18:47
lbragstad#link https://gist.github.com/lbragstad/ddfb10f9f9048414d1f781ba006e95d118:47
*** tonytan4ever has joined #openstack-meeting18:47
lbragstadwhich right now is pretty basic, I'm adding the credential specific stuff in a bit18:47
lbragstadI'll be sure to drop it into -keystone when its finished, and link it in the implementation review18:48
*** yamahata has joined #openstack-meeting18:48
*** delattec has joined #openstack-meeting18:48
stevemarlbragstad: still seems a lot of moving parts to land before tomorrow EOD18:49
stevemarlbragstad: must it land in newton?18:49
*** salv-orl_ has quit IRC18:49
*** iyamahat has quit IRC18:50
lbragstadstevemar well - it was a requirement for the mfa stuff18:50
*** liangy_ has joined #openstack-meeting18:50
*** Suyi_1 has joined #openstack-meeting18:50
*** NikitaKonovalov has quit IRC18:50
*** topol has quit IRC18:50
*** iyamahat has joined #openstack-meeting18:50
stevemartrue18:50
*** anilvenkata_ has joined #openstack-meeting18:50
*** tonytan_brb has quit IRC18:50
*** comay_ has joined #openstack-meeting18:50
*** aignatov has quit IRC18:50
*** cdelatte has quit IRC18:51
*** jtomasek has quit IRC18:51
*** bknudson has quit IRC18:51
*** ianw has quit IRC18:51
*** comay has quit IRC18:52
*** Suyi_ has quit IRC18:52
*** apetrich has quit IRC18:52
*** lennyb has quit IRC18:52
*** jrist has quit IRC18:52
*** liangy has quit IRC18:52
*** duvarenkov_ has quit IRC18:52
*** hughhalf has quit IRC18:52
*** ivyyy has quit IRC18:52
*** mestery has quit IRC18:52
stevemarwe could make the MFA work dependant on credential encryption (in O)18:52
stevemarlbragstad: i won't bump it for now, but i won't cry if it doesn't make the cut :)18:52
lbragstadstevemar i think we need to have the trigger discussion18:52
stevemar#topic sql triggers18:52
*** openstack changes topic to "sql triggers (Meeting topic: keystone)"18:52
lbragstadbecause that is going to be a big factor in if this lands.18:52
*** dlahn has joined #openstack-meeting18:53
lbragstadstevemar I doubt I'll have the time to rework the implementation to not use triggers by tomorrow18:53
stevemarmailing list for the record: http://lists.openstack.org/pipermail/openstack-dev/2016-August/102293.html18:53
stevemarlbragstad: i thought bayer said triggers was OK to use in this instance18:53
lbragstadstevemar agree - he did18:54
stevemarlbragstad: so what's the issue?18:54
*** dimtruck is now known as zz_dimtruck18:54
lbragstadstevemar it sounds like others still have issues with it though18:54
stevemari say we use them18:54
lbragstadok18:54
rderoseme too :) ++18:54
henrynashstevemar: ++ (even though we hopefully don't need them for the created_at fix)18:54
lbragstadstevemar in that case - i think the current implementation works well18:55
*** banix has quit IRC18:55
lbragstadwe test the triggers against MySQL and postresql18:55
*** Shrews has joined #openstack-meeting18:55
*** prateek_ has joined #openstack-meeting18:55
*** bethwhite_ has joined #openstack-meeting18:55
henrynashlbragstad: ...and I think we are saying....we don't support sqlite for upgrades...18:56
stevemarhenrynash: yes18:56
lbragstadhenrynash yeah - zzzeek was on board with that too18:56
stevemari doubt we've ever supported that18:56
*** hughhalf has joined #openstack-meeting18:56
*** bknudson has joined #openstack-meeting18:56
*** aignatov has joined #openstack-meeting18:56
henrynashstevemar: well, we have to be a bit carefull....you do an offline "upgrade" just to stand up a new version of openstack18:57
*** piet has joined #openstack-meeting18:57
*** AJaeger has joined #openstack-meeting18:57
*** mestery has joined #openstack-meeting18:57
bknudsonI think I got disconnected18:57
*** NikitaKonovalov has joined #openstack-meeting18:57
henrynashstevemar: i.e. we do a db_sync and run through all the migrations18:57
*** annegentle has quit IRC18:57
samueldmqlbragstad: henrynash are there special cases for sqlite too ?18:57
stevemarlbragstad: bumping credential encryption also means bumping the triggers decision to O :)18:58
stevemarsince we won't have any18:58
*** intr1nsic has quit IRC18:58
lbragstadstevemar that is ultimately bumping R/W upgrades as well18:58
henrynashstevemar: that's gotta work...or nobody can use sqlite at all (which we would secretly like, but not sure we can legistlate against immeditaly)18:58
*** annegentle has joined #openstack-meeting18:58
samueldmqstevemar: seems a sane decision18:58
*** dmorita has quit IRC18:58
samueldmqany reason we should rush with that ?18:58
henrynashlbragstad: I really object to that....I would rather have RW upgrades than mfa18:59
*** topol_ has joined #openstack-meeting18:59
*** parora has quit IRC18:59
lbragstadstevemar we also currently support TOTP18:59
*** salv-orlando has joined #openstack-meeting18:59
lbragstadwhich leverages the credential backend18:59
stevemarlbragstad: and those aren't encrypted either18:59
*** hasharAway is now known as hashar18:59
lbragstadfrom a security perspective - they aren't encrypted18:59
lbragstadright18:59
*** erlon has joined #openstack-meeting18:59
*** banix has joined #openstack-meeting19:00
henrynashlbragstad: the need for keystone no downtime upgrades must, imho, come before mfa (if the mfa solution isn'r ready for RW upgrades)19:00
stevemarlets jump to -keystone19:00
stevemar#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Aug 30 19:00:14 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-08-30-18.00.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-08-30-18.00.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-08-30-18.00.log.html19:00
fungiinfra team, assemble!19:00
pleia2o/19:00
fungitoday's exciting topics provided by jeblair, fungi, zaro and pleia219:00
Zarao/19:00
SotKo/19:00
clarkbhello19:00
AJaegero/19:01
*** intr1nsic has joined #openstack-meeting19:01
zaroo/19:01
jeblairhowdy19:01
mordredo/19:01
fungi#startmeeting infra19:02
openstackMeeting started Tue Aug 30 19:02:16 2016 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
bkeroo/19:02
fungi#info Track chairs have confirmed there will be a Zuul v3 presentation at the Ocata Summit19:02
*** ekcs has joined #openstack-meeting19:02
fungijeblair: did you have any additional details on that?19:02
Shrewso/19:02
rcarrillocruzo/19:03
jeblairfungi: no, that's about it.  i mean, i may make a sign-up table for ansi artists.... ;)19:03
* mordred thinks someone should storm the room dressed as the staypufft marshmellow man19:03
fungiheh19:03
*** jtomasek has joined #openstack-meeting19:03
*** shaleh has left #openstack-meeting19:03
*** duvarenkov_ has joined #openstack-meeting19:04
pleia2#link https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/16615/zuul-v3-openstack-and-ansible-native-cicd19:04
fungiperfect--thanks pleia2!19:04
jeblairmordred: do we have anyone with experience dressing up in ridiculous costumes at summits?19:04
fungii was just trying to hunt that down19:04
*** lennyb has joined #openstack-meeting19:04
pleia2I can make stick puppets19:04
*** apetrich has joined #openstack-meeting19:04
*** browne has left #openstack-meeting19:04
*** ivyyy has joined #openstack-meeting19:04
fungi#info Gerrit downtime on Friday 2016-09-02 at 18:00 UTC19:04
fungi#link http://lists.openstack.org/pipermail/openstack-dev/2016-August/102281.html19:04
*** Patifa has quit IRC19:04
fungi#info Reminder: late-cycle joint Infra/QA get together to be held September 19-21 (CW38) in at SAP offices in Walldorf, DE19:05
fungi#link https://wiki.openstack.org/wiki/Sprints/QAInfraNewtonSprint19:05
fungithere are still 5 slots remaining, but if you're going you should put your name in the registration table on that wiki page soon lest you end up on the standby waiting list19:05
*** david-lyle_ is now known as david-lyle19:05
*** kebray has quit IRC19:05
fungias always, get me announcements before next week's meeting and i'll include them19:05
fungi#topic Actions from last meeting19:05
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:05
*** ravelar1 has left #openstack-meeting19:05
fungi#link http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-08-23-19.01.html19:06
fungiAJaeger start a docs ml thread to refresh constraints around retention of old/unmaintained documents19:06
fungi#link http://lists.openstack.org/pipermail/openstack-docs/2016-August/009003.html19:06
fungithat happened19:06
fungithanks!19:06
fungipleia2 send maintenance announcement for upcoming gerrit project renames19:06
fungi(already linked in the announcements earlier)19:06
*** zz_dimtruck is now known as dimtruck19:06
*** ianw has joined #openstack-meeting19:07
fungii may add an ad-hoc topic later if there's time to discuss project rename logistics for friday19:07
fungi#topic Specs approval: PROPOSED "Update doc publishing spec for AFS"19:07
*** openstack changes topic to "Specs approval: PROPOSED "Update doc publishing spec for AFS" (Meeting topic: infra)"19:07
fungi#link https://review.openstack.org/276482 Update doc publishing spec for AFS19:07
ianwo/19:07
*** jrist has joined #openstack-meeting19:07
jeblairme puts down sandwich19:07
fungilooks like we're set to finish voting on this one!19:07
jeblairyeah, i think we have what we need19:08
*** ilyashakhat has joined #openstack-meeting19:08
jeblairi updated it yesterday based on feedback from loquacities that came out of the docs ml thread19:08
fungigood with approving it at/after 19:00 utc thursday if no objections are voiced?19:08
*** pabelanger has joined #openstack-meeting19:08
pabelangero/19:08
jeblairthe good news is that not needing to do the migration makes things simpler, and gets rid of a significant work item19:08
*** sshnaidm is now known as sshnaidm|afk19:08
jeblairfungi: yes19:08
fungi#info Council voting will remain open on the "Update doc publishing spec for AFS" change until 19:00 UTC on Thursday, September 119:09
jeblairthis could use some volunteers19:09
jeblairmordred: has volunteered19:09
mordredyah. I will help19:09
jeblairwe could probably use another infra person, and probably a docs team member as well19:09
fungiadditional volunteers for some of the tasks would be good19:09
jeblairit will be highly parallelizable19:09
*** vhoward has joined #openstack-meeting19:09
jeblairin fact, almost all of the work items are paralellizable19:10
pabelangersure, I can help19:10
jeblairso if people wanted to pile on this, we could probably get it done very quickly19:10
*** baoli has quit IRC19:10
*** lpetrut has quit IRC19:10
fungiAJaeger was already starting to dig through the existing content and trying to mirror a copy to see what's involved. i don't know if he has any new insights yet19:10
AJaegerfungi: not yet - still mirroring content ;(19:10
jeblair(and there is some urgency around this since cloud sites is being spun out, and apparently we use too many inodes)19:10
fungioh, wow19:10
mordredwe are big inode consumers19:11
pleia2hehe19:11
pleia2we break a lot of clouds19:11
fungiAJaeger: still downloading after how long? how much do you have so far?19:11
AJaegerFastest way to safe inodes: Don't push up sources - and don't separate trees for each tags19:11
*** coolsvap_ has quit IRC19:12
AJaegerfungi, still downloading after 36 hours. I had to break after 24 hours ;( and restarted. Luckly lftp can mirror, so it's not starting from zero...19:12
pleia2oy19:12
AJaegerat 594184 files and 9.8 GB now...19:12
*** gyee has quit IRC19:12
jeblairi wonder if doing that inside of rax would be any faster?19:13
fungiyeah, thankfully with the current version of the plan just needing an "old docs site" published somewhere after we get site generation going to the new location, having that take a few days to pull is tractable19:13
AJaegershouldn't be much longer....19:13
jeblairfungi: yep19:13
fungianything else we need to cover on that spec right now?19:13
persiaSadly, for many-small-files, there is limited speedup for low-latency.19:13
clarkbjust 2ish more GB19:13
AJaegerregarding the inode usage: I have indentifed some really unused content (we even have redirects away from it)19:14
AJaegerAnd biggest offender is _source:19:14
AJaeger705 MB; 156k inodes19:14
jeblairfungi: nope.  we have some volunteers, and i will requisition others as needed.  :)19:14
AJaegermore in the next days...19:14
jeblairfungi: oh, you had an idea of making that a priority effort...19:15
fungijeblair: ahh, yep. maybe we can propose that next week19:15
*** armax has joined #openstack-meeting19:15
jeblairoh, also, i'll be away next week19:15
fungi(or the week after!)19:15
fungi#topic Priority Efforts: Zuul v3 (jeblair)19:16
*** openstack changes topic to "Priority Efforts: Zuul v3 (jeblair) (Meeting topic: infra)"19:16
fungi#link https://review.openstack.org/360817 Zuul v3: update branches job keyword19:16
fungi#link https://review.openstack.org/360819 Zuulv3: drop variable interpolation and add nodesets19:16
*** vishwanathj_ has quit IRC19:16
jeblairme puts sandwich down again19:16
*** eranrom has joined #openstack-meeting19:16
*** ijw has quit IRC19:16
jeblairthe first change is trivial19:16
jeblairso go bikeshed that if you want.  :)19:16
jeblairi just didn't want to be committing code that didn't match the spec19:16
jeblairthe second is interesting19:17
jeblairit's a substantive change19:17
jeblairoh i thought i updated the agenda19:17
jeblairthe link should be to https://review.openstack.org/36146319:17
jeblair#link https://review.openstack.org/361463 Zuulv3: drop variable interpolation and add nodesets19:17
jeblairi think the commit msg explains the rationale19:18
fungiaha, yep you had 360819 linked in the agenda, and i didn't double-check it19:18
fungisorry about that19:18
jeblairwell, i left a forwarding address in gerrit, so if anyone looked at the agenda before now, they will have ended up in the right place anyway :)19:19
fungiheh19:19
*** ilyashakhat has quit IRC19:20
jeblairso i don't know if we want to open formal voting on this, or what.19:20
fungimaybe. good that it has a clear example19:20
fungithough your editor seems to enjoy injecting hard tabs19:20
pabelangerI like the change19:20
*** armax has quit IRC19:20
jeblairyeah, tabs are awesome, but i can remove them in a followup if we want to formally vote on the non-tab content.19:21
clarkbreading the commit message makes sense to me19:21
fungii can add 361463 to the list for formal voting. 360817 i think i'll just approve as administrivia19:22
jeblairsounds good19:22
fungi#info Council voting will remain open on the "Zuulv3: drop variable interpolation and add nodesets" change until 19:00 UTC on Thursday, September 119:22
* mordred steals jeblair's sandwich before he can pick it up again19:23
jeblairtoo late19:23
Shrewslgtm19:23
Shrewsthe review, not the sandwich19:23
fungihurry and take a bite19:23
fungi#topic Priority Efforts: Nodepool: Use Zookeeper for Workers (jeblair)19:23
*** openstack changes topic to "Priority Efforts: Nodepool: Use Zookeeper for Workers (jeblair) (Meeting topic: infra)"19:23
fungi#link https://review.openstack.org/360821 Update nodepool zookeeper spec with branch19:24
jeblairme puts down sandwich for the last time19:24
jeblairthis one is probably administrivia too19:24
jeblairi think we discussed this a week or 2 ago, and started using the branch since then19:24
fungiyep, just looked, i'm cool with approving now19:24
jeblairso thought we ought to update the spec for it19:24
*** annegentle has quit IRC19:24
fungithanks19:25
fungi#topic Design summit session planning (fungi)19:25
*** openstack changes topic to "Design summit session planning (fungi) (Meeting topic: infra)"19:25
fungi#link https://etherpad.openstack.org/p/infra-ocata-summit-planning Infra Ocata summit planning pad19:25
fungijust following up quickly... i put in a preliminary request for one fishbowl and five workrooms plus the half-day collaboration space on friday19:26
Zara\o/19:26
fungiif anyone disagrees, i still have until tomorrow to amend our allocation request19:26
fungialso, are most people sticking around for friday? if so, it might make sense to request some of our workrooms be on friday morning so we can treat it like additional general collaboration time19:27
*** ianw_ has joined #openstack-meeting19:28
*** Sukhdev has joined #openstack-meeting19:28
*** baoli has joined #openstack-meeting19:28
rcarrillocruzi do plan to fly back on Saturday, so yeah19:28
bkerome too19:28
mordredI will be flying on saturday19:28
pleia2same19:28
clarkbsaturday too19:28
pabelangerI too19:28
fungicool, that was the hope19:28
jeblairme too19:29
fungii'll let you all know what we end up with, but in the meantime keep adding session ideas to the etherpad19:29
mordredfungi: not related to that - I will only be in germany monday and tuesday, flying to stockholm from frankfurt at noon on wednesday, in case anyone cares about such information19:29
*** Leo_ has joined #openstack-meeting19:29
*** parora has joined #openstack-meeting19:30
fungimordred: good to know. as previously discussed, i won't be in germany but i have hopes someone will feed me highlights19:30
* pleia2 takes all the notes19:30
fungipleia2 rocks19:30
fungi#topic Sprint to test Gerrit online indexing (zaro)19:30
*** openstack changes topic to "Sprint to test Gerrit online indexing (zaro) (Meeting topic: infra)"19:30
zaroi'm looking for help to test gerrit's online reindex.19:31
zarousing review-dev.o.o19:31
fungizaro: my current plan is to try it in production during our project rename maintenance in a few days, but any testing you get done before then would be awesome19:31
zarofungi: ok.  if you want to skip then cool with me19:31
zaroworst case is you'll just need to do offline reindex19:32
pleia2yeah, we scheduled a 4 hour window just in case19:32
fungiwell, if you had anything you were going to try on review-dev in the next few days, feedback from that would be awesome19:32
*** dmorita has joined #openstack-meeting19:32
fungijust so we have a better idea of what to anticipate19:32
zarowell, i'm suggesting that i run online reindex and need volunteers to use gerrit while it's reindexing19:33
zarothat's basically the test19:33
*** dmorita has quit IRC19:33
*** prateek_ has quit IRC19:33
zarothe reindex takes about 1.5 hrs without any activity on gerrit19:33
*** mickeys has joined #openstack-meeting19:33
fungiyep. anyone have time to poke at uploading changes to and reviewing them on review-dev while there's an online reindex of a large repo happening there?19:33
*** rtheis_ has joined #openstack-meeting19:33
pleia2sure19:34
fungizaro: when do you expect to be around to kick off the reindexing and keep an eye on it?19:34
pleia2I'm around all week, so whenever works19:34
*** ivar-lazzaro has joined #openstack-meeting19:35
*** dprince has quit IRC19:35
zarohow about tomorrow morning?19:35
pleia2wfm19:35
*** armax has joined #openstack-meeting19:35
*** dmorita has joined #openstack-meeting19:35
*** dmorita has quit IRC19:35
fungialso, does gerrit show-caches or show-queues or something display the reindexing progress?19:35
*** rtheis has quit IRC19:35
fungicurious how best to keep tabs on it during our maintenance window on friday19:35
zaroyes19:35
fungiokay, cool19:36
zaroshow-queues19:36
*** ilyashakhat has joined #openstack-meeting19:36
fungithanks!19:36
zarohow about start at 1700 utc?19:36
*** e0ne has quit IRC19:36
pleia2sounds good19:37
*** dmorita has joined #openstack-meeting19:37
fungii'll get to pleia2's topic on the agenda first, and then i'll inject mine about the gerrit rename maintenance logistics and we can talk a little more about reindexing as part of that19:37
zarocool, was going to suggest a sprint, but probably not needed.19:37
fungi#info Gerrit online reindex testing will be run on review-dev Wednesday, August 31 starting at 17:00 UTC19:37
pleia2zaro: maybe we can recruit some folks as we go ;)19:38
fungisounds good19:38
*** _nadya_ has joined #openstack-meeting19:38
fungi#topic Another bug day? (pleia2)19:38
*** openstack changes topic to "Another bug day? (pleia2) (Meeting topic: infra)"19:38
pleia2so, the last time we did one of these was back in April19:38
fungii agree, seems like we're overdue19:38
*** _nadya_ has quit IRC19:38
pleia2bugs are piling up again19:38
pleia2I think it would be nice to get this out of the way before our sprint in germany19:38
pleia2next week is bad for me because there's a Jury Summons on my desk, my schedule is unpredicable19:39
pleia2but any time the week after19:39
*** rcernin has joined #openstack-meeting19:39
clarkbwhat about monday of thr week after?19:39
*** ivar-lazzaro has quit IRC19:39
clarkbnext monday is a us holiday19:39
pleia2wfm19:39
*** mickeys has quit IRC19:39
pleia2september 12th19:40
fungiyeah, that seems fine for me19:40
fungii have nothing on my calendar except a weekly vmt thing19:41
pabelangerI think that works for me too19:41
pleia2ok, I'll get that organized w/ etherpad and add to the sprint channel schedule19:41
fungi#info Infra bug sprint tentatively scheduled for Monday, September 1219:42
fungiaction pleia2 set up sprint booking for infra bug day19:42
fungithanks!19:42
fungi#action pleia2 set up sprint booking for infra bug day19:42
fungihelps if i # those19:42
*** yuval has joined #openstack-meeting19:42
fungianything else we should cover now for bug day planning?19:43
pleia2I don't think so19:43
*** su_zhang has joined #openstack-meeting19:43
fungi#topic Gerrit rename maintenance logistics (fungi)19:44
*** openstack changes topic to "Gerrit rename maintenance logistics (fungi) (Meeting topic: infra)"19:44
*** dmorita has quit IRC19:44
fungii got to going back over the change that added teh rename playbook19:44
fungi#link https://review.openstack.org/175147 Add an ansible playbook for project renames19:44
fungiunfortunately i hadn't gotten around to reviewing that before it merged last year19:45
fungiit seems we took out the steps for renaming/transferring repos in github but i don't see what in the playbook takes care of that19:45
fungii'm assuming i should add that back into the manual part of the process19:45
fungialso it's doing a graceful stop of zuul via kill -URS1 which i fear will take faaaaar too long for us19:46
fungier, kill -USR119:46
yuval(yuval from smaug => karbor here, arriving late :)19:46
jeblairyeah, that'd take 24 hours19:46
*** dmorita has joined #openstack-meeting19:46
fungiand it'll need updating to remove the offline reindexing step now that we can do online19:47
fungijust trying to pick everyone's brain that's done prior renames to see if there's any other gotchas that jump out at you19:47
*** su_zhang has quit IRC19:48
*** jamesdenton has quit IRC19:48
fungiand i'm fuzzy on how any of this actually works19:49
jeblairhas it ever been used?19:49
*** hockeynut has quit IRC19:49
funginot in our gerrit at least19:49
fungifor example, the shell items that echo db queries through |mysql reviewdb19:50
jeblairyolanda is not here, though she decided it was ready to be merged...19:50
pleia2and not in prod afaik19:50
jeblairmordred: do you have thoughts?19:50
*** dprince has joined #openstack-meeting19:50
mordredjeblair: not useful ones19:51
*** Carolbarrett has joined #openstack-meeting19:51
*** fzdarsky is now known as fzdarsky|afk19:52
fungiit looks like `echo ... |mysql reviewdb` is relying on ~root/.my.cnf being set up correctly, so that's probably fine19:52
fungias i too rely on that going to our trove instance correctly19:52
*** _nadya_ has joined #openstack-meeting19:52
fungii'll doublecheck that storyboard.o.o has a similarly correct ~root/.my.cnf19:52
*** _nadya_ has quit IRC19:52
fungianyway, i'm still game for giving this a shot, but would appreciate people getting up with me with any concerns over it before friday so i can revert to our old mostly-manual process if necessary19:53
jeblairwell, i certainly wouldn't stop zuul that way19:54
*** dmorita has quit IRC19:54
clarkbits looking likr I may be sitting with at least one foundation staff member to go over using gerrit during the renames so I will defer to others19:54
fungiright. things i already know need to be changed there: zuul stop/start/reenqueue, offline reindex. also adding teh github steps back into the manual steps19:54
clarkb(we can use review dev while review is down)19:54
pleia2I'll have a look through too to see if anything jumps out at me19:55
fungiappreciated19:55
*** takashi has joined #openstack-meeting19:55
*** dmorita has joined #openstack-meeting19:55
*** jungleboyj has joined #openstack-meeting19:56
zaroclarkb: hopefully it will only be down for a little bit19:56
fungi#topic Open discussion19:57
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:57
yuvalhey, yuval from smaug/karbor - is anything required on our part during/after the rename?19:57
*** harlowja has quit IRC19:58
fungiyuval: we'll generate a change you'll want to approve that updates your .gitreview file19:58
*** annegentle has joined #openstack-meeting19:58
fungiyuval: but also you may find that some of your jobs are broken by the new repo name and, if so, you'll probably want to be around to patch those as needed19:58
*** diablo_rojo has joined #openstack-meeting19:58
*** su_zhang has joined #openstack-meeting19:58
AJaegerfungi, the changes look complete - but there're always surprises ;)19:59
fungithat's one of the reasons we usually do these right before the weekend, so you have a little time to get tests updated before they'll impact a large number of new changes in review19:59
fungiAJaeger: yeah, it's often going to be things like repo urls hard-coded in devstack plugins or something19:59
fungiokay, we're out of time19:59
fungithanks everyone!20:00
*** Apoorva has quit IRC20:00
fungi#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Aug 30 20:00:06 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-08-30-19.02.html20:00
yuvalfungi: thanks20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-08-30-19.02.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-08-30-19.02.log.html20:00
ttxo/20:00
*** Sukhdev has quit IRC20:00
*** kota_ has joined #openstack-meeting20:00
dimso/20:00
ttxAnyone around for the TC meeting ?20:00
dtroyero/20:01
CarolbarrettHi20:01
tonybo/20:01
claudiubo/20:01
annegentlehere20:01
* edleafe scurries to the side of the room20:01
ttxdhellmann, flaper87, johnthetubaguy, mestery, mtreinish, mordred, russellb, sdague: around ?20:01
mordredo/20:01
dhellmanno/20:01
*** bethwhite_ has left #openstack-meeting20:01
sdagueo/20:01
flaper87o/20:01
ttx#startmeeting tc20:01
openstackMeeting started Tue Aug 30 20:01:33 2016 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: tc)"20:01
openstackThe meeting name has been set to 'tc'20:01
ttxWelcome back everyone... Our agenda for today:20:01
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:01
johnthetubaguyo/20:01
ttx(remember to use #info #idea and #link liberally to make for a more readable summary)20:01
ttx#topic Extra ATCs20:02
*** openstack changes topic to "Extra ATCs (Meeting topic: tc)"20:02
*** Patifa has joined #openstack-meeting20:02
ttxWe have two late requests for addition of extra-ATCs20:02
*** Patifa has quit IRC20:02
ttxI'm saying late because we are now past the deadline described at20:02
ttx#link https://releases.openstack.org/newton/schedule.html#n-extra-atcs20:02
*** su_zhang has quit IRC20:02
ttxThe first one was submitted in time, we just didn't process it last week since there was a meeting skip20:02
* amrith sneaks into the back rows20:02
annegentleseems reasonable to allow20:02
ttxThat is "Adds winstackers extra ATCs list" (https://review.openstack.org/355872)20:02
ttxThe second one was submitted a bit late but we could give it an exception I guess, since it's our first time doing this20:03
*** adiantum has quit IRC20:03
ttxThe too late one being "Add Bryan Sullivan as extra-ATC for Congress" (https://review.openstack.org/358762)20:03
* flaper87 is good with giving it an exception20:03
mordredwfm20:03
ttxI'm approving the first one20:03
claudiub\o/20:03
dtroyer++ on the second20:03
dhellmanndoes approving these mean they would apply to the upcoming elections?20:03
dhellmannI'm OK with it either way, I'm just asking to clarify20:04
ttxI'm +1 on the Congress exception too, just we close the bar now20:04
ttxdhellmann: yes20:04
dhellmannok20:04
annegentlecool20:04
sdagueyeh, I think it's fine.20:04
ttxWe haven't tagged the repo for elections yet20:04
dhellmannand yes, I agree with saying we're closing this for this cycle20:04
mtreinisho/20:04
annegentleoh yeah should we ask the election officials if they're ok with this addition?20:04
ttx#agreed Those were the last extra-ATC requests for this cycle20:04
tonyb+1 from me20:05
ttxannegentle: they close the list much later usually so they should be ok20:05
dhellmanntonyb : thanks20:05
annegentletonyb thanks for taht20:05
fungithey'll also get summit registration discount codes when i send the final batch next week (assuming they're not already contributors to another official project team)20:05
annegentlethat even20:05
dims+1 to close the door with these20:05
*** Patifa has joined #openstack-meeting20:05
annegentlefungi ok, good to know20:05
ttxok, Bryan approved too20:05
dhellmannfungi : ah, ok, good20:05
dimsfungi : thanks20:05
ttxok, moving on20:05
ttx#topic Update Glance mission statement20:06
*** openstack changes topic to "Update Glance mission statement (Meeting topic: tc)"20:06
ttx#link https://review.openstack.org/35405320:06
ttxThis update is to reflect the long-term focus of Glance in light of the upcoming Glare split20:06
ttxWhich should happen during Ocata20:06
ttxLooks like the current proposed version is consensual amongst Glance devs20:06
flaper87++20:06
flaper87Sounds reasonable and it reflects the direction the team is going20:06
*** dmorita has quit IRC20:07
ttxyep, I'm fine adjusting it even if Glare is not separated out yet20:07
amrithvery good sign that there are no -1's20:07
ttxapproving now unless there is a last-minute objection20:07
dimslet's do it20:07
ttxdone20:07
annegentlesounds good20:07
ttxnext topic!20:07
ttx#topic Add the newly-created Requirements team to projects.yaml20:07
*** openstack changes topic to "Add the newly-created Requirements team to projects.yaml (Meeting topic: tc)"20:07
ttx#link https://review.openstack.org/35838020:08
ttxThis is the last split from the original release management team (after VMT and stable branch maintenance)20:08
*** galstrom is now known as galstrom_zzz20:08
dhellmann\o/20:08
ttxMy only gripe would be that the mission is not mentioning dependency convergence, but that's not enough to block it.20:08
ttxreading mtreinish recent comments though20:08
tonybttx: Yeah the mission statement is weak but I'm happy to fix that20:08
mtreinishttx: oh, annegentle and I were just talking about adding a check job to run the validate tox job20:09
dhellmannyeah, I'd like to fix that in a separate patch if we can20:09
mtreinishttx: https://review.openstack.org/#/c/363165/220:09
mtreinishunrelated to the review really20:09
ttxtonyb: ok, I'll propose the adjustment in a subsequent patch20:09
annegentleyeah more of a process / expectation question but thanks20:09
ttx#action ttx to suggest dependency convergence as part of requirements mission as a separate patch20:10
ttxOK, let's approve this one then20:10
*** nishaYadav has quit IRC20:10
*** su_zhang has joined #openstack-meeting20:10
tonybThank!20:10
ttxThe important bit is to get the team up there20:10
ttxapproved20:11
mtreinishtonyb: I wonder how many ptl hats you can collect for barcelona20:11
ttxOK, now for more interesting discussions20:11
ttx#topic New Storlets project team20:11
tonybmtreinish: ;P20:11
*** openstack changes topic to "New Storlets project team (Meeting topic: tc)"20:11
dimsyay welcome to requirements team!20:11
dhellmannttx: tonyb and I may need to talk with you about summit space if you haven't already allotted some for the new team20:11
*** sdake has quit IRC20:11
ttxI'd like to timebox that one to the next 25 min (up until :35)20:11
*** pradk has quit IRC20:11
ttxdhellmann: I think I included Tony in the list20:12
dhellmannttx: ok, cool20:12
*** sdake has joined #openstack-meeting20:12
tonybdhellmann: sure.20:12
ttxLet's say I'm "forward-looking" rather than "cheating"'20:12
tonybdhellmann: I've sumitted for stable and requirements20:12
ttxSo.. Storlets20:12
ttx#link https://review.openstack.org/35369320:12
dhellmanntonyb : ok, good, I wanted to make sure you got some for requirements20:12
ttxOK, round 2 of discussion on this one, since last meeting we could only spend 10 minutes on it20:12
*** anilvenkata_ has quit IRC20:12
ttxLet me try to summarize the objections/comments so far, and then we can have a discussion about the specifics20:13
dhellmannI'd like to hear from some of the folks who had time to look at the storlets code since I didn't and there were comments on the review about organization and such20:13
ttx1. Use of Java and C code20:13
flaper87o/20:13
ttxUsage of Java seems limited to glue code to make user-side containerized Java payloads work20:13
* flaper87 stfu and lets ttx talk20:13
ttxI'm fine with that especially since there are plans to add support for user-side Python/XXX payloads20:13
flaper87ttx: that was not my understanding20:13
ttxUsage of C code seems to be limited to ~800sloc to work around limitations to pass FDs to Java in the container -- long-term would be great to find a way around that20:13
ttxThere is also a simple tool to run within the container, which could be using shell instead (restart_docker_container.c)20:14
ttxflaper87: what was your understanding ?20:14
flaper87my understanding was that storelets are currently written in Java and that's what is executed20:14
johnthetubaguyin a python sense that C code sounds a bit like privsep?20:14
ttxflaper87: well, a "storlet" is the user-side code20:14
johnthetubaguyright, it runs java code, I think20:14
flaper87I think I asked this in the review. I wonder if there will be storelets written in some other language20:14
flaper87ttx: oh you said glue code and I thought about something else20:14
ttxIt is a Python pipeline creating a container that runs code. Currently Java code20:15
eranromWe are currently working on Pytrhob20:15
flaper87it's the actual code that users will write20:15
johnthetubaguythe data processing world is very java/scala centric, so it doesn't surprise me they started there20:15
ttxjohnthetubaguy: ++20:15
ttxLet me finish the writeup20:15
eranromjohnthetubaguy: you got us :-)20:15
ttx2. Java as a dependency20:15
ttxThe main issue with Java as a dependency is that in some cases that means effectively depending on non-free Oracle SDK, since OpenJDK is, let's say... less tested and people are encouraged to run Oracle JDK to avoid corner oddities20:15
flaper87johnthetubaguy: not saying it's bad20:15
flaper87fwiw20:15
ttxIn this precise scenario though I feel like it's only used for user-side payloads, so it's slightly less of a problem20:16
*** pradk has joined #openstack-meeting20:16
ttxBut still, to avoid questions and legal redistribution troubles I think we need to clearly depend on OpenJDK rather than "a Java runtime"20:16
mordred++20:16
ttx3. Unlogged meetings, single-core approvals20:16
dims++ ttx20:16
ttxThose are pretty common in not-yet-official projects, and could be fixed post-approval20:16
ttx4. Java-centric code organization and build system20:16
ttxI posted this one on the review today -- browsing the source code for storlets feels like walking on an alien planet.20:17
annegentleCan users only run Java? Or is this a "serverless" solution where compute processes could run as if SSHing in?20:17
dhellmannttx: in the past we've asked to see some period of time with logged meetings before approving20:17
ttxIt really feels like Python code bolted on a Java project rather than the other way around20:17
dtroyerdhellmann: ++20:17
fungifwiw, we already leverage openjsk in some infra jobs (and for some infra services) so it should be straightforward from a ci perspective20:17
flaper87dhellmann: yeah20:17
fungier, openjdk20:17
ttxdhellmann: yeah, which is why I raised it as an objection20:17
dhellmannok, you said it could be fixed after20:17
ttxGiven that the project should be open to other type of user-side workloads (including Python) I think the project should rather be Python with Java code bolted on top20:17
ttxdhellmann: my personal view on it, but yes, it adds up20:18
ttxThat would make it more familiar for existing OpenStack developers and make it more like other OpenStack projects20:18
ttxWhich brings us to the last objection20:18
ttx5. Timing of the proposal20:18
ttxOverall it feels a bit early for this to be included as an OpenStack project. There seems to be a bit of code organization refactoring, documentation to do (like the README still containing boilerplate), also QA integration...20:18
flaper87++20:18
ttxSo it feels more like Ocata material than Newton, and I would rather delay this inclusion while we iron out those details, rather than fast-track it.20:18
ttxAlso adding new projects at this stage of the cycle is slightly suboptimal (too late for release inclusion, bit late for ATC codes, too late to be included in Design Summit...)20:19
flaper87right20:19
ttxAny other objection that I failed to capture ? Any comment on those objections ?20:19
mordredttx: I think that's a good summary, and a good plan of action20:19
mordredI don't think any of the issues are insurmountable20:19
dtroyerHave they talked about the general security issue of running user code on servers?20:19
flaper87Not sure if you mentioned the coding style but I did bring it up in the review20:19
flaper87I like the plan of actions20:19
mordredand given the release timing, given them some time to deal with it and then return after the summit sounds perfectly reasonable20:19
mtreinishdtroyer: meh, it's containers all the security you need :)20:20
ttxIdeally we would have someone from the TC signing up to help them in the coming month(s) so that they can apply again at the start of Ocata20:20
dimsmtreinish : LOL20:20
ttxbut I'll admit my dance pad is full20:20
annegentlegood outline thanks ttx anyone here from storelets?20:20
ttxannegentle: eranrom is here20:20
flaper87ttx: I can help20:20
flaper87eranrom: ^20:20
*** esberglu has joined #openstack-meeting20:21
eranromflaper87: ttx: Thanks!20:21
ttxflaper87: nice20:21
ttx#agreed flaper87 can mentor the storlets team for early addition in Ocata20:21
dimsflaper87 : nice of you!20:21
eranromQuick question: Could we still hold a (mini) design summit in Barcelona?20:21
ttxeranrom: none of those objections are insurmontable like mordred says. Just a bit of cleanup and process to follow and reapply when it's better time to do so20:21
* flaper87 agrees with what's been agreed20:22
eranromttx: Sure, thanks for the summary. We are on it20:22
ttxeranrom: we usually reach out to teams that have proposed recntlky to offer some space when there is space left (there usually is)20:22
* flaper87 adds insurmontable to his dictionary20:22
eranromttx: alright, thanks20:23
ttxeranrom: I'll be in touch in the coming weeks20:23
flaper87eranrom: ditto20:23
ttxeranrom: do the objections all make sense ?20:23
edleafeflaper87: you should probably add "insurmountable" too :)20:23
eranromttx: Absolutley20:23
ttx(I bet flaper87 will help further explaining anyway20:23
flaper87edleafe: jeeez, I knew I should have trusted the red line under insurmontable20:24
annegentleeranrom so is the idea to enable more end-user language options?20:24
eranromyes, we are very actively working on Python now20:24
ttxIt feels like it could support Go with minimal effort, and Python20:24
annegentleeranrom great, thanks20:25
eranromttx: correct20:25
*** gyee has joined #openstack-meeting20:25
johnthetubaguyI added something about privsep vs that C code20:25
ttxOK, if no more questions, we can move to next topic20:26
johnthetubaguyits not a blocker, I am just curious what the difference is20:26
*** rtheis_ is now known as rtheis20:26
johnthetubaguybut we can move on, we can talk about that in the review20:26
ttxjohnthetubaguy: I think it's passing logging FDs around and expose them within the jvm, but I read quickly20:26
*** pabelanger has left #openstack-meeting20:26
eranromjohnthetubaguy: pardon my ignorance privsep? we can discuss offline though20:26
dhellmanneranrom : http://docs.openstack.org/developer/oslo.privsep/20:27
*** esberglu_ has joined #openstack-meeting20:27
johnthetubaguywhat dhellmann said^20:27
dhellmanneranrom : also http://docs.openstack.org/developer/oslo.rootwrap/ which is the older lib, but may fit your use case better20:27
johnthetubaguyit might do what you need for those docker operations (it might not, but I was just curious really)20:27
eranromsure, will have a look thanks!20:28
*** esberglu has quit IRC20:28
*** esberglu_ is now known as esberglu20:28
ttxyeah, let's discuss that offline20:28
johnthetubaguy+120:28
ttxMOving on20:28
dhellmann++20:28
*** sindhu has quit IRC20:28
ttx#topic Goals20:28
*** openstack changes topic to "Goals (Meeting topic: tc)"20:28
ttxWe have a number of reviews that iterate on the stuff we merged last meeting20:28
ttxFirst one expands the goal template with a section to reflect current state:20:28
ttx#link https://review.openstack.org/35667420:28
*** AJaeger has left #openstack-meeting20:28
ttxLooks like a good idea that we can merge now20:28
dhellmannthis was sdague's idea, for the record20:28
flaper87sounds good to me20:29
ttxObjections ?20:29
ttx(change also applies said extra section to the already-approved copypaste-removal goal)20:30
annegentlewe're not gonna make extra whitespace removal a requirement? I kid.20:30
ttxAlright, approving now20:30
ttxSecond one is a bit of clean up following last meeting, adding reference to goals/ and the house rule to fast-track PTL responses to the goals20:31
ttx#link https://review.openstack.org/35669920:31
* ttx reads most recent patchset20:31
*** hrybacki is now known as hrybacki|afk20:31
dhellmannthanks to annegentle for pointing out some clumsy wording there20:31
ttxThanks annegentle -- when I don't parse a sentence I assume it's because I'm bad at English20:32
dtroyeryes, much clearer, thanks20:32
*** esberglu has quit IRC20:32
ttxpiling up +1s20:32
annegentleI'm bad at parsing usually20:32
*** esberglu has joined #openstack-meeting20:33
*** esberglu has left #openstack-meeting20:33
ttx5 and counting20:33
* dhellmann has a bad tendency toward complex sentence structure20:33
*** rcernin has quit IRC20:33
mordreddhellmann: I don't not have similar issues20:33
*** banix has quit IRC20:33
*** rcernin has joined #openstack-meeting20:33
annegentlehey, at least you're using genderless pronouns :)20:33
dhellmannmordred : don't be so negative ;-)20:34
*** Apoorva has joined #openstack-meeting20:34
*** rstarmer has joined #openstack-meeting20:34
ttxAlright, another winner20:34
mordreddhellmann: negative is the new positive20:34
ttxThird one is an incremental improvement on the goals document wording:20:34
ttx#link https://review.openstack.org/35615620:34
ttxThere was an objection (from dhellmann and me) on the analyze part20:35
ttx+ a minor wording suggestion20:35
ttxIf those are the only objections, maybe do a quick new patchset ?20:35
flaper87++20:35
dtroyer++20:35
* flaper87 is ready to vote as soon as the new ps is up20:36
ttxIn the mean time we can discuss the last part20:36
dimsagree on new ps20:36
*** mickeys has joined #openstack-meeting20:36
ttxannegentle: are you on a ps-regeneration-friendly setting ?20:36
ttxin*20:36
ttxa.k.a. not on your phone20:36
annegentleyeah20:36
ttxDo you agree with the proposed tweaks ?20:37
* annegentle is never on a phone for irc20:37
ttxnever say never20:37
annegentleoh yes. I can change20:37
ttxOK, let's discuss py35 again in the mean time20:37
ttxSo... last is the Python 3.5 support goal, which we left over last meeting to have more discussion on it:20:38
ttx#link https://review.openstack.org/34906920:38
ttxI commented earlier today that as it stood the goal was slightly suboptimal, since it was a bit too asymmetric20:38
ttxwith two teams already expected to miss it20:39
dtroyerI think this will not be the last time we come across a goal like that, which would otherwise be an easy decision20:39
dimsor folks would have already done it :)20:39
ttxI still would very much like some py35 progress as a goal in Ocata though20:39
*** ianw has quit IRC20:39
*** ianw_ is now known as ianw20:39
*** amakarov has quit IRC20:39
ttxdhellmann suggested making unit tests optional in the goal20:40
dhellmannI think we can take 3 approaches here.20:40
* flaper87 reads carefully20:40
dhellmann1. we can say up front that some projects aren't likely to finish their unit tests, and leave those as exceptions20:40
*** ijw has joined #openstack-meeting20:40
sdagueyeh, honestly, I think that from a global perspective, if you want a real move forward on python 3 support, we should only talk about full stack testing20:40
dhellmann2. we can make unit tests entirely optional, which would maybe mean fewer projects actually update them than could20:40
dhellmann3. we can remove all mention of unit tests for now20:40
ttxor 4. we can pick an completely-different goal entirely20:41
dhellmannsure, or 420:41
sdagueI think that if the goals are layed out as are in that document, what you will actually get is folks focussing on unit / functional side20:41
ttxI'm 2 3 4 120:41
sdagueand skipping the full stack, because it's harder20:41
sdaguebut if it's just full stack, you'll get more real progress in 3.5 support20:41
fungiyeah, even for a project as limited in scope as bindep, it took me enlisting someone to spend a fair amount of time to migrate from mox to mock so we could get py3k unit testing out of teh way20:41
*** mickeys has quit IRC20:41
*** ilyashakhat has quit IRC20:41
dhellmannsdague : I suppose that depends on the test coverage from any given layer of tests, which is why I included all 3 to start20:42
sdagueit's not just about coverage20:42
annegentleI'm pro-4, but I couldn't come up with a solid new goal.20:42
sdagueit's about what things look like when they are actually running, multi process20:42
annegentleYou know I was thinking of an API reference consistency goal, but it doesn't compare/replace py3.520:42
annegentleso, yeah, didn't propose20:42
ttxsdague: do you think we could build a goal that would be "complete-able" and would advance full stack testing in for Ocata20:42
flaper87Let's also keep in mind Ocata is a shorter cycle20:43
ttx?20:43
sdaguettx: probably, though until we're in freeze it's hard to think about20:43
flaper87I'm pro 2 3 4 1 too20:43
annegentleyour brain froze too sdague ? :)20:43
sdaguewell, my brain is focussed on ensuring the placement api is ready to go20:43
ttxShall we defer picking the second goal to post-FF ?20:43
annegentlettx hm...20:44
fungiworth noting, that's really only applicable to stuff that's integration tested under devstack or has functional testing, right? there are a lot of "outside the stack" projects maintained by various teams20:44
annegentleis there a list of candidate 2nd goals anyone else has?20:44
johnthetubaguysdague: +1 all your comments here, it feels like more focus on full stack would be better, but I am unsure how possible that is right now20:44
dhellmannannegentle : https://etherpad.openstack.org/p/ocata-tc-goals20:45
annegentledhellmann perfect thanks20:45
flaper87I would still like to see progress on the py3.5 work for ocata, tbh. If having it as a goal, even with optional bits, helps then I'm good with that20:45
sdaguejohnthetubaguy: right, honestly that ends up being something where what you really need is a couple of people to try the world, see what works, fall back, start filing bugs20:45
*** myoung|bbl is now known as myoung20:45
*** nmagnezi has quit IRC20:45
johnthetubaguysdague: yeah +120:45
mtreinishjohnthetubaguy: I actually think that it would be easier than doing mox->mock in nova20:45
dhellmannannegentle : that said, I am strongly opposed to delaying work on the python 3 port any further.20:46
johnthetubaguymtreinish: yeah, I totally think it is20:46
clarkbdhellmann: ++20:46
annegentledhellmann yeah20:46
dhellmanneven if we reduce the scope of this goal, I think it's extremely important for us to start pushing20:46
*** jungleboyj has quit IRC20:46
flaper87dhellmann: exactly20:46
*** sindhu has joined #openstack-meeting20:46
amriththis isn't going to be the last time that we have a goal that some projects can't finish in one cycle. requiring that all projects finish the goal in 1 cycle limits the number of projects that would be candidate for these kinds of goals. Doesn't it make sense to stick with the goal with the known set of exceptions going in, with the understanding that those projects have one more cycle (and the goals from that cycle?)20:46
sdaguedhellmann: right, I agree with you. I'm suggesting an approach that I think will move us further along20:46
dhellmannafaik, there are no other goals for which we have an external deadline20:46
flaper87I would still like to see progress on the py3.5 work for ocata, tbh. If having it as a goal, even with optional bits, helps then I'm good with that20:46
dimsdhellmann : keep unit/functional and drop integration for ocata?20:46
*** mickeys has joined #openstack-meeting20:46
sdaguedims: no20:46
dhellmannsdague : yeah, I would rather focus on that than changing to a different goal20:47
ttx(FTR annegentle's new patchset is up at https://review.openstack.org/#/c/356156, please vote)20:47
fungihow about disabling all mock-using nova unit tests (and any others that spontaneously break) when tested under python 3.5? curious how involved that would be20:47
sdaguedims: that's actually pretty much pointless I think20:47
sdaguereally, we're at this tipping point20:47
sdague2 people and 4 weeks would probably get 1/2 the iaas projects over to a python 3 gate20:47
sdaguefor devstack20:48
*** dmorita has joined #openstack-meeting20:48
fungiwhich would then allow readding tests under the 3.5 job as they're updated to work there20:48
dims(provided sufficient core reviewers...yes)20:48
sdagueand have a work list that shows the path forward20:48
sdaguebut, this isn't going to be a thing we can push out just to all the teams and assume that scatter gather works I don't think20:48
sdagueI expect this only works with 1 or 2 drivers that are handling this globally as well20:48
mtreinishfungi: that's what the jobs do now iirc (they use a blacklist on py3)20:48
johnthetubaguyits more a central team that will create a bunch of work folks need to jump on, I guess?20:49
*** asettle has joined #openstack-meeting20:49
*** dmorita has quit IRC20:49
*** raildo has quit IRC20:49
*** dmorita has joined #openstack-meeting20:49
dhellmannjohnthetubaguy : no, I don't want anyone to assume that there is a team of folks standing by to submit these patches20:49
sdaguejohnthetubaguy: and shake out all the gate / devstack / tempest issues that I'm sure are there20:49
johnthetubaguydhellmann: agreed we can't assume they are there, its just where the work will flow from (I need a better word than flow...)20:50
ttxOK, so it feels like we need to continue the discussion on this one and we won't solve it in the coming 5 minutes20:50
dimsso we pick say a test (devstack+tempest) and say we should be able to run various things with a blacklist if needed20:50
ttxShould we have at thread ? Just wait post-FF so that people have more bandwidth ?20:50
*** sindhu has quit IRC20:50
ttxa*20:51
annegentlewe sorta need to just try out goals and learn from them.20:51
sdaguettx: sure. Though in my mind, I think we still need to understand if there will be global drivers for an activity like this20:51
dims++ttx (post-FF)20:51
sdaguebecause I actually don't think we'll make progress without that20:51
annegentleso maybe sticking with py35, documenting expectations, then having a post-mortem discussion helps the most20:51
sdagueand it's not super clear that's part of this process20:51
dimssdague : i agree20:51
sdaguethat's where I'm having difficulty reconciling20:51
annegentlesdague you're likely correct (and steeped in experience)20:52
*** Mortir has joined #openstack-meeting20:52
dimskudos to haypo and others who brought us this far in python320:52
sdaguebecause I think the folks pushing python3 thus far, are actually quite disconnected from full stack testing20:52
*** Mortir has quit IRC20:52
johnthetubaguyfeels like the full stack bit is the most important bit, and there is a big natural bottleneck in the middle20:52
ttxok, let's discuss it again next week. Please vote on  https://review.openstack.org/#/c/356156/ so that we can at least improve that one20:52
sdaguedims: yes, definitely20:52
ttxs/improve/approve20:52
* dims peeks at the clock20:53
ttxAnd let's move to open discussion20:53
ttx#topic Open discussion20:53
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:53
ttxI had a quick question for that20:53
ttxregarding the proposed Ocata release schedule20:53
ttx#link https://review.openstack.org/#/c/357214/20:53
ttxIt's based on placing the release week the week of the PTG end of February20:53
*** ilyashakhat has joined #openstack-meeting20:53
ttxAs predicted that makes for a short cycle (13 weeks between DS and FF, including the end-of-year holiday period)20:53
ttx(to compare with recent history, Newton was 18, Mitaka was 18, Liberty was 15, Juno was 16)20:54
ttxA lot of projects already said they would take advantage of that to do some technical debt reduction (a.k.a. a stabilization cycle)20:54
*** lblanchard has quit IRC20:54
*** lpetrut has joined #openstack-meeting20:54
mtreinishdoes anyone have any objection to running the validation tox job nonvoting on projects.yaml changes? (I have that patch up)20:54
ttxSome have been wondering if the TC should not more aggressively encourage that line of thought20:54
fungimake it the "py3k cycle"? ;)20:54
ttxThoughts on that ?20:54
dimsfungi : ++ :)20:54
*** sindhu has joined #openstack-meeting20:55
ttxPersonally I'd rather let project teams take it to their own conclusions20:55
dtroyerWe've kicked that idea around for a long time, this is the natural time to do it20:55
ttxand focus on the goals soft-guidance instead20:55
dimsttx : +1 to soft-guidance20:55
fungi"themes" seem like a friendly way to encourage that20:55
mtreinishttx: yeah, I think the soft approach makes sense here20:55
ttxWe just need to make sure everyone realizes how short it is20:55
ttxbut that's relmgt team work, not tc20:55
ttxmtreinish: go for it (non-voting job)20:56
sdagueso, I almost feel like we should just call out R-8 as dead week20:56
sdaguebecause, I can't imagine you'll have many reviewers working that week20:56
ttxsdague: right20:56
*** ilyashakhat has quit IRC20:56
*** JRobinson__ has joined #openstack-meeting20:57
dimsrelmgt can send out a email with the proposed dates and callout the # of weeks and R-8 etc20:57
mtreinishttx: well it's mostly does anyone have a reason we shouldn't do:  https://review.openstack.org/36316520:57
*** Patifa has quit IRC20:57
dhellmannI'm also considering proposing that we freeze all libraries the week before o-3 instead of splitting client and non-client -- the split has introduced some confusion in teams with libs that seem on the fence between client or not20:57
mtreinishI think it would be useful to get the metric tag info on proposed changes so we can easily refer to it in review20:57
*** e0ne has joined #openstack-meeting20:58
mtreinishthe tradeoff is querying stackalytics is slow (it took ~15min locally to finish)20:58
dhellmannmtreinish : as long as it's non-voting, I don't have an issue. I just don't want the repo blocked when data outside our control changes the definition of "valid"20:58
dimsdhellmann : the problem there is the requirements need to be updated..20:58
fungiin the past it was because non-client library releases needed to get updated in caps in client library requirement files during the intervening week20:58
funginow we're hopefully relying a lot more on constraints and less on requirements cap bumps though20:58
ttxstill short of one vote on Anne's https://review.openstack.org/#/c/356156/20:58
mtreinishdhellmann: yeah definitely, I made sure to leave it nonvoting20:58
dhellmanndims : what fungi  said20:58
dtroyershould we just limit the client bits to that then?20:59
dimsack dhellmann fungi20:59
ttxthx sdague20:59
yuvalSorry to pop in, yuval from smaug/karbor. Would like to update that smaug repo will be renamed karbor this weekend by the infra team. Just want to make sure it's ok to do so when the governance patch ( https://review.openstack.org/#/c/353278/ ) vote is still running20:59
dhellmanndtroyer : ?20:59
*** xarses has joined #openstack-meeting20:59
dhellmannyuval : yes20:59
ttxyuval: i'll approve that one as soon as the rename is done20:59
dtroyerlimit the clients to settling the requirements in the following week after lib freeze20:59
yuvaldhellmann: ttx: thanks20:59
ttxAlright, one min left20:59
ttxAnything else, anyone ?21:00
*** baoli has quit IRC21:00
*** sindhu has quit IRC21:00
ttxTaking that as no21:00
ttx#endmeeting21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Tue Aug 30 21:00:48 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
ttxThanks everyone21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-08-30-20.01.html21:00
amriththx ttx21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-08-30-20.01.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-08-30-20.01.log.html21:00
dimsthanks ttx, bye everyone21:01
*** yuval has quit IRC21:01
*** julian1 has joined #openstack-meeting21:03
*** e0ne has quit IRC21:03
*** _alastor1 is now known as _alastor-21:03
*** _alastor- is now known as _alastor__21:04
*** Carolbarrett has quit IRC21:05
*** e0ne has joined #openstack-meeting21:06
*** jmckind has joined #openstack-meeting21:06
*** azbiswas has joined #openstack-meeting21:06
*** radeks has joined #openstack-meeting21:07
*** dprince has quit IRC21:08
*** esberglu has joined #openstack-meeting21:09
*** enriquetaso has quit IRC21:11
*** radeks has quit IRC21:11
*** spzala has quit IRC21:12
*** thorst has quit IRC21:13
*** harlowja has joined #openstack-meeting21:17
*** hockeynut has joined #openstack-meeting21:17
*** rstarmer has quit IRC21:18
*** ayoung has quit IRC21:19
*** rtheis has quit IRC21:20
*** maeca1 has quit IRC21:22
*** e0ne has quit IRC21:23
*** pfallenop has quit IRC21:24
*** sdake has quit IRC21:26
*** salv-orlando has quit IRC21:26
*** annegentle has quit IRC21:29
*** dbecker has quit IRC21:29
*** cody-somerville has quit IRC21:29
*** rfolco has quit IRC21:29
*** tiantian has joined #openstack-meeting21:29
*** egallen has joined #openstack-meeting21:29
*** cody-somerville has joined #openstack-meeting21:30
*** hockeynut has quit IRC21:31
*** pfallenop has joined #openstack-meeting21:31
*** sdake has joined #openstack-meeting21:32
*** armax has quit IRC21:32
*** huangtianhua has quit IRC21:32
*** shashank_hegde has quit IRC21:33
*** claudiub has quit IRC21:35
*** cleong has quit IRC21:35
*** rfolco has joined #openstack-meeting21:37
*** sindhu has joined #openstack-meeting21:37
*** rfolco has quit IRC21:39
*** spzala has joined #openstack-meeting21:40
*** eezhova has quit IRC21:40
*** Swami has quit IRC21:44
*** spzala has quit IRC21:44
*** annegentle has joined #openstack-meeting21:46
*** shashank_hegde has joined #openstack-meeting21:47
*** eharney has quit IRC21:48
*** Shrews has left #openstack-meeting21:49
*** shashank_hegde has quit IRC21:49
*** salv-orlando has joined #openstack-meeting21:49
*** esberglu_ has joined #openstack-meeting21:50
*** xarses has left #openstack-meeting21:50
*** asettle has quit IRC21:51
*** shashank_hegde has joined #openstack-meeting21:51
*** asettle has joined #openstack-meeting21:51
*** esberglu has quit IRC21:52
*** banix has joined #openstack-meeting21:53
*** tonytan4ever has quit IRC21:54
*** esberglu_ has quit IRC21:54
*** esberglu has joined #openstack-meeting21:55
*** asettle has quit IRC21:56
*** bobh_ has quit IRC21:57
*** spotz is now known as spotz_zzz21:59
*** esberglu has quit IRC21:59
*** diablo_rojo has quit IRC22:01
*** mriedem has quit IRC22:01
*** jmckind has quit IRC22:03
*** rajinir has quit IRC22:05
*** sindhu has quit IRC22:05
*** rstarmer has joined #openstack-meeting22:07
*** topol_ is now known as topol22:09
*** hashar has quit IRC22:10
*** lpetrut has quit IRC22:12
*** akuznetsov has joined #openstack-meeting22:13
*** su_zhang has quit IRC22:22
*** spzala has joined #openstack-meeting22:24
*** ianw has quit IRC22:26
*** apetrich has quit IRC22:28
*** esumerfd has quit IRC22:30
*** apetrich has joined #openstack-meeting22:30
*** jrist has quit IRC22:32
*** akuznetsov has quit IRC22:33
*** su_zhang has joined #openstack-meeting22:34
*** jamesdenton has joined #openstack-meeting22:36
*** sdake has quit IRC22:36
*** spzala has quit IRC22:38
*** spzala has joined #openstack-meeting22:38
*** jrist has joined #openstack-meeting22:39
*** sindhu has joined #openstack-meeting22:39
*** hemna is now known as hemnafk22:39
*** piet has quit IRC22:40
*** amitgandhinz has quit IRC22:41
*** amitgandhinz has joined #openstack-meeting22:42
*** annegent_ has joined #openstack-meeting22:42
*** spzala has quit IRC22:43
*** annegentle has quit IRC22:43
*** esumerfd has joined #openstack-meeting22:45
*** Swami has joined #openstack-meeting22:47
*** Swami_ has joined #openstack-meeting22:47
*** jamesdenton has quit IRC22:48
*** ivar-lazzaro has joined #openstack-meeting22:49
*** esumerfd has quit IRC22:50
*** azbiswas has quit IRC22:51
*** uxdanielle has quit IRC22:55
*** rbak has quit IRC22:56
*** ianw has joined #openstack-meeting22:57
*** vhoward has quit IRC22:58
*** takashi has quit IRC22:58
*** ayoung has joined #openstack-meeting22:59
*** armax has joined #openstack-meeting23:00
*** roxanaghe has quit IRC23:00
*** pradk has quit IRC23:00
*** cardeois has quit IRC23:04
*** Leo_ has quit IRC23:05
*** saju_m has quit IRC23:06
*** takashi has joined #openstack-meeting23:07
*** egallen has quit IRC23:07
*** Apoorva has quit IRC23:09
*** hrybacki|afk is now known as hrybacki23:10
*** Apoorva has joined #openstack-meeting23:14
*** sindhu has quit IRC23:16
*** jamesdenton has joined #openstack-meeting23:16
*** _sarob has quit IRC23:18
*** salv-orlando has quit IRC23:21
*** takashi has quit IRC23:23
*** kaminohana has joined #openstack-meeting23:23
*** su_zhang has quit IRC23:23
*** ekcs has quit IRC23:25
*** sindhu has joined #openstack-meeting23:29
*** tochi has joined #openstack-meeting23:29
*** sdague has quit IRC23:31
*** jamesdenton has quit IRC23:34
*** annegent_ has quit IRC23:34
*** jaugustine has quit IRC23:34
*** rcernin has quit IRC23:35
*** esumerfd has joined #openstack-meeting23:42
*** zhurong has joined #openstack-meeting23:44
*** tpsilva has quit IRC23:44
*** Julien-zte has quit IRC23:44
*** esumerfd has quit IRC23:46
*** banix has quit IRC23:47
*** rooneym has quit IRC23:49
*** mriedem has joined #openstack-meeting23:57
*** tonytan4ever has joined #openstack-meeting23:58
*** shu-mutou-AFK is now known as shu-mutou23:59

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