Tuesday, 2017-03-07

*** VW has quit IRC00:00
*** asselin has quit IRC00:04
*** mriedem has quit IRC00:06
*** donghao has joined #openstack-meeting00:08
*** bzhao_ has quit IRC00:08
*** yangyapeng has quit IRC00:10
*** jrobinson has joined #openstack-meeting00:10
*** ianychoi has quit IRC00:10
*** ianychoi has joined #openstack-meeting00:11
*** bobmel has joined #openstack-meeting00:12
*** donghao has quit IRC00:12
*** delatte has quit IRC00:13
*** dmorita has joined #openstack-meeting00:13
*** felipemonteiro_ has quit IRC00:13
*** kylek3h has joined #openstack-meeting00:13
*** dmorita_ has joined #openstack-meeting00:14
*** dmorita has quit IRC00:14
*** dmorita has joined #openstack-meeting00:15
*** dmorita_ has quit IRC00:15
*** bobmel has quit IRC00:17
*** dmorita_ has joined #openstack-meeting00:18
*** dmorita has quit IRC00:19
*** dmorita has joined #openstack-meeting00:20
*** knangia has quit IRC00:21
*** dmorita has quit IRC00:21
*** dmorita has joined #openstack-meeting00:21
*** dmorita has quit IRC00:23
*** dmorita has joined #openstack-meeting00:23
*** dmorita_ has quit IRC00:23
*** Leo_ has quit IRC00:26
*** gcb has quit IRC00:26
*** claudiub has quit IRC00:27
*** shu-mutou has joined #openstack-meeting00:27
*** dmorita_ has joined #openstack-meeting00:27
*** dmorita has quit IRC00:28
*** dmorita_ has quit IRC00:32
*** dimtruck is now known as zz_dimtruck00:32
*** dmorita has joined #openstack-meeting00:32
*** hongbin has quit IRC00:34
*** zz_dimtruck is now known as dimtruck00:35
*** dmorita has quit IRC00:37
*** dmacpher has joined #openstack-meeting00:37
*** dmorita has joined #openstack-meeting00:37
*** amotoki has joined #openstack-meeting00:38
*** dmorita_ has joined #openstack-meeting00:40
*** dmorita_ has quit IRC00:42
*** dmorita_ has joined #openstack-meeting00:42
*** dmorita has quit IRC00:42
*** amotoki has quit IRC00:43
*** dmorita_ has quit IRC00:46
*** baoli has joined #openstack-meeting00:47
*** dmorita has joined #openstack-meeting00:48
*** mriedem has joined #openstack-meeting00:49
*** SerenaFeng has joined #openstack-meeting00:51
*** dmorita has quit IRC00:52
*** baoli has quit IRC00:53
*** salv-orlando has joined #openstack-meeting00:53
*** salv-orlando has quit IRC00:58
*** dane_leblanc has quit IRC01:00
*** sdague has quit IRC01:01
*** iceyao has joined #openstack-meeting01:03
*** diablo_rojo has quit IRC01:04
*** jkilpatr_ has quit IRC01:04
*** zhurong has joined #openstack-meeting01:05
*** jkilpatr_ has joined #openstack-meeting01:06
*** iceyao has quit IRC01:08
*** ihrachys has joined #openstack-meeting01:08
*** kongwei has joined #openstack-meeting01:08
*** ihrachys has quit IRC01:08
*** ihrachys has joined #openstack-meeting01:09
*** gongysh has joined #openstack-meeting01:09
*** ntpttr_ has quit IRC01:11
*** dimtruck is now known as zz_dimtruck01:11
*** knangia has joined #openstack-meeting01:12
*** zz_dimtruck is now known as dimtruck01:13
*** pvaneck has quit IRC01:13
*** yangyapeng has joined #openstack-meeting01:13
*** yangyapeng has quit IRC01:14
*** yangyapeng has joined #openstack-meeting01:14
*** dmorita has joined #openstack-meeting01:15
*** thorst has joined #openstack-meeting01:17
*** guoshan has joined #openstack-meeting01:17
*** kongwei has quit IRC01:18
*** thorst has quit IRC01:18
*** dmorita has quit IRC01:19
*** gongysh has quit IRC01:23
*** caowei has joined #openstack-meeting01:25
*** gongysh has joined #openstack-meeting01:26
*** Apoorva has quit IRC01:26
*** thorst has joined #openstack-meeting01:27
*** dmorita has joined #openstack-meeting01:31
*** dmorita_ has joined #openstack-meeting01:32
*** dmorita has quit IRC01:32
*** dmorita_ has quit IRC01:33
*** dmorita has joined #openstack-meeting01:33
*** trinaths has joined #openstack-meeting01:33
*** trinaths has quit IRC01:34
*** unicell has quit IRC01:34
*** gongysh has quit IRC01:34
*** trinaths has joined #openstack-meeting01:34
*** gongysh has joined #openstack-meeting01:35
*** trinaths1 has joined #openstack-meeting01:35
*** dmorita has quit IRC01:36
*** dmorita_ has joined #openstack-meeting01:36
*** xianghui has joined #openstack-meeting01:36
*** dmorita_ has quit IRC01:37
*** dmorita has joined #openstack-meeting01:37
*** kevinz has joined #openstack-meeting01:38
*** trinaths has quit IRC01:39
*** dmorita has quit IRC01:40
*** dmorita has joined #openstack-meeting01:40
*** dmorita_ has joined #openstack-meeting01:42
*** dmorita has quit IRC01:43
*** dmorita_ has quit IRC01:43
*** iceyao has joined #openstack-meeting01:43
*** dmorita has joined #openstack-meeting01:43
*** dmorita_ has joined #openstack-meeting01:45
*** dmorita has quit IRC01:45
*** dmorita has joined #openstack-meeting01:46
*** dmorita_ has quit IRC01:46
*** lhx__ has joined #openstack-meeting01:48
*** dmorita has quit IRC01:50
*** armax has quit IRC01:54
*** salv-orlando has joined #openstack-meeting01:55
*** salv-orlando has quit IRC01:59
*** Apoorva has joined #openstack-meeting02:00
*** dimtruck is now known as zz_dimtruck02:02
*** dmorita has joined #openstack-meeting02:03
*** awaugama has quit IRC02:05
*** dmorita_ has joined #openstack-meeting02:07
*** dmorita has quit IRC02:08
*** persia has quit IRC02:09
*** mtanino_ has quit IRC02:09
*** dmorita_ has quit IRC02:11
*** dschultz has joined #openstack-meeting02:12
*** persia has joined #openstack-meeting02:12
*** dmorita has joined #openstack-meeting02:13
*** jkilpatr_ has quit IRC02:14
*** xianghui_ has joined #openstack-meeting02:14
*** erlon has quit IRC02:15
*** markvoelker has quit IRC02:16
*** jkilpatr_ has joined #openstack-meeting02:16
*** dmorita_ has joined #openstack-meeting02:17
*** zz_dimtruck is now known as dimtruck02:17
*** xianghui has quit IRC02:17
*** dmorita has quit IRC02:18
*** dmorita_ has quit IRC02:21
*** dmorita has joined #openstack-meeting02:21
*** dmorita_ has joined #openstack-meeting02:23
*** dmorita__ has joined #openstack-meeting02:24
*** dmorita_ has quit IRC02:24
*** dmorita has quit IRC02:26
*** dmorita__ has quit IRC02:26
*** dmorita has joined #openstack-meeting02:26
*** dmorita has quit IRC02:28
*** dmorita has joined #openstack-meeting02:28
*** dmorita_ has joined #openstack-meeting02:30
*** dmorita has quit IRC02:30
*** galstrom_zzz is now known as galstrom02:32
*** fzdarsky_ has joined #openstack-meeting02:32
*** thorst has quit IRC02:33
*** thorst has joined #openstack-meeting02:33
*** dmorita has joined #openstack-meeting02:33
*** dmorita_ has quit IRC02:34
*** fzdarsky|afk has quit IRC02:35
*** mkrai_ has joined #openstack-meeting02:37
*** thorst has quit IRC02:38
*** dmorita has quit IRC02:38
*** dmorita has joined #openstack-meeting02:39
*** amotoki has joined #openstack-meeting02:39
*** dimtruck is now known as zz_dimtruck02:41
*** dmorita_ has joined #openstack-meeting02:42
*** guoshan has quit IRC02:42
*** dmorita has quit IRC02:43
*** amotoki has quit IRC02:44
*** dmorita_ has quit IRC02:46
*** yuanying_ has joined #openstack-meeting02:49
*** dmorita has joined #openstack-meeting02:49
*** yuanying has quit IRC02:49
*** oomichi has quit IRC02:50
*** Apoorva has quit IRC02:50
*** oomichi has joined #openstack-meeting02:50
*** dmorita has quit IRC02:54
*** diga has joined #openstack-meeting02:54
*** jkilpatr_ has quit IRC02:55
*** yatinkarel has joined #openstack-meeting02:55
*** hongbin has joined #openstack-meeting02:56
*** lhx__ has quit IRC02:57
*** lakerzhou has joined #openstack-meeting02:57
*** dmorita has joined #openstack-meeting02:57
*** lhx__ has joined #openstack-meeting02:58
*** shubhams has joined #openstack-meeting02:58
*** galstrom is now known as galstrom_zzz02:58
*** Namrata has joined #openstack-meeting02:58
*** dmorita_ has joined #openstack-meeting02:59
*** pksingh has joined #openstack-meeting02:59
*** VW has joined #openstack-meeting03:00
hongbin#startmeeting zun03:00
openstackMeeting started Tue Mar  7 03:00:49 2017 UTC and is due to finish in 60 minutes.  The chair is hongbin. Information about MeetBot at http://wiki.debian.org/MeetBot.03:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.03:00
*** openstack changes topic to " (Meeting topic: zun)"03:00
openstackThe meeting name has been set to 'zun'03:00
hongbin#link https://wiki.openstack.org/wiki/Zun#Agenda_for_2017-03-07_0300_UTC Today's agenda03:00
hongbin#topic Roll Call03:00
*** openstack changes topic to "Roll Call (Meeting topic: zun)"03:01
mkrai_Madhuri Kumari03:01
pksinghHello All03:01
yatinkarelYatin Karel03:01
hongbinthanks for joining the meting Namrata shubhams lakerzhou kevinz mkrai_ pksingh yatinkarel03:01
hongbin#topic Announcements03:01
*** openstack changes topic to "Announcements (Meeting topic: zun)"03:01
*** dmorita__ has joined #openstack-meeting03:01
hongbin1. Propose to switch to cycle-with-intermediary release model starting from Pike03:01
*** VW has quit IRC03:01
hongbin#link https://review.openstack.org/#/c/441524/03:02
*** dmorita has quit IRC03:02
*** VW has joined #openstack-meeting03:02
hongbinthis proposal means zun will aglin with openstack release sschedule starting from pike03:02
pksinghcool :)03:02
hongbinzun will make a release at the end of pike in particular03:02
mkrai_That's great!03:02
hongbinany comment about this announcement?03:03
shubhamsDo we need to create release docs then?03:03
pksinghwhen will be our firts release, any date?03:03
*** dmorita_ has quit IRC03:04
tonybpksingh: when you're ready03:04
hongbinshubhams: it is good to have but not mandatory03:04
tonybcycle-with-intermediary doesn't dictae that03:04
lakerzhouDo we need formal installation guides, and other stuff which are common to all the other projects.03:04
shubhamshongbin: tonyb : ok03:04
tonybshubhams: do you mean release notes?03:04
hongbinpksingh: i think it is good to have a first release right before the boston summit03:04
shubhamstonyb: yes03:04
pksinghhongbin: i think the same03:04
hongbinpksingh: then have the final release at the end of pike03:05
tonybshubhams: they get added with the change so you're always createing them03:05
shubhamstonyb: ok.03:05
hongbinlakerzhou: again, it is good to have, but not mandatory (if i understand correctly)03:05
*** dmorita has joined #openstack-meeting03:05
tonybhongbin: Yup that's right03:05
hongbintonyb: thanks for confirming03:06
*** dmorita__ has quit IRC03:06
hongbindiga: hey03:06
digahongbin: Hi03:06
hongbinok, it seems all the questions were addressed03:06
hongbin#topic Review Action Items03:06
*** openstack changes topic to "Review Action Items (Meeting topic: zun)"03:06
hongbin1. Wenzhi created a bp for migrate from 'id' to 'uuid' in the sql backend once the etcd backend is finishing migration (DONE)03:07
hongbin#link https://blueprints.launchpad.net/zun/+spec/replace-id-with-uuid03:07
*** galstrom_zzz is now known as galstrom03:07
hongbinthis bp means we will graudatly be moving from id to uuid03:07
*** ihrachys has quit IRC03:07
hongbinany comment ?03:07
hongbinseems no03:08
hongbin#topic Cinder integration (diga)03:08
*** openstack changes topic to "Cinder integration (diga) (Meeting topic: zun)"03:08
hongbin#link https://blueprints.launchpad.net/zun/+spec/cinder-zun-integration The BP03:08
hongbindiga: ^^03:08
digaHi, I have uploaded PS yesterday03:09
hongbin#link https://review.openstack.org/#/c/429943/03:09
digabut will add next patch today,03:09
digaI forgot to add some files & there are some code fixes remaining in the PS03:09
*** dmorita has quit IRC03:10
mkrai_Is it ready for review diga ?03:10
digaI have also uploaded CLI volume PS for client03:10
pksinghdiga: patch has some issues, would be better to make that in WIP03:10
digamkrai_: I am uploading latest PS then you can review03:10
mkrai_diga: Ok thanks03:10
*** bkopilov has quit IRC03:11
*** trinaths1 has quit IRC03:11
digapksingh: I forgot to add latest PS so by mistake it pushed older changes from another folder03:11
pksinghdiga: ok :)03:11
digapksingh: I have ready PS, will push in sometime03:11
*** epico has joined #openstack-meeting03:12
*** bobmel has joined #openstack-meeting03:12
hongbindiga: thanks for the huge effort of doing this patch03:12
digabut No test cases implemented yet, will cover test cases today/tomorrow03:12
hongbindiga: yes, just let us know when you are done03:12
digahongbin: Thanks you03:13
digahongbin: sure03:13
hongbindiga: i think it would be inefficient to give comments on this large patch, would you mind the reviewers directly update your patch for comments?03:13
*** vishnoianil has quit IRC03:13
hongbindiga: it is your call03:14
digahongbin: sure03:15
digahongbin: No Problem03:15
*** guoshan has joined #openstack-meeting03:15
hongbindiga: ok, then just let us know once you uploaded all the change03:15
*** sudipto has joined #openstack-meeting03:15
digahongbin: yep03:15
*** sudipto_ has joined #openstack-meeting03:15
hongbindiga: i will go though it once you are ready03:16
*** lhx__ has quit IRC03:16
digahongbin: yeah03:16
hongbinthanks diga03:16
digahongbin: welcome!03:16
hongbinok, next topic03:16
hongbin#topic Kuryr integration (hongbin)03:16
*** openstack changes topic to "Kuryr integration (hongbin) (Meeting topic: zun)"03:16
hongbin#link https://blueprints.launchpad.net/zun/+spec/kuryr-integration The BP03:16
hongbini was working on this bp last week03:17
*** bobmel has quit IRC03:17
hongbinsubmitted several patches to kuryr, mainly for fixing bugs and enable the existing network and ipv6 feature03:17
hongbini was playing with kuryr heavily last week, it seems we need to create an port in user's tenant, and pass the port to kuryr to bind03:18
hongbinbasically, all resources creation needs to be handled out of kuryr to statisfy the multi-tenancy model03:18
*** dmorita has joined #openstack-meeting03:18
*** mickeys has quit IRC03:19
hongbin#link https://review.openstack.org/#/q/project:openstack/kuryr-libnetwork+and+owner:%22Hongbin+Lu+%253Chongbin.lu%2540huawei.com%253E%2203:19
hongbinany question for this bp?03:19
digahongbin: do you mean creating port in neutron then pass it to kuryr ?03:19
*** ijw has quit IRC03:20
hongbindiga: yes03:20
digahongbin: okay03:20
pksinghhongbin: why do we need port?03:20
hongbinif we let kuryr to create the port, the port will belong to admin tenant03:20
hongbinassign floating ip to admin port will be impossible03:20
digapksingh: may be this is required for VIF binding03:20
hongbinpksingh: every container needs to have a neutron port03:20
*** dmorita has quit IRC03:21
*** dmorita has joined #openstack-meeting03:21
pksinghhongbin: ok03:21
hongbinany other question?03:22
mkraiZun will create this port itself?03:22
hongbinmkrai: yes03:22
digait should03:22
hongbinand we need to make sure the port is cleanup after the container is deleted03:22
*** dmorita has quit IRC03:22
hongbinbasically, more work for us03:22
*** dmorita has joined #openstack-meeting03:22
hongbinmore questions?03:23
digahongbin: in this case, once we delete the container, then this care should be taken by us03:23
hongbindiga: yes03:24
digahongbin: got it03:24
hongbinok, seems no more question03:25
hongbinnext topic03:25
hongbin#topic Introduce host capabilities and cpusets (sudipto)03:25
*** openstack changes topic to "Introduce host capabilities and cpusets (sudipto) (Meeting topic: zun)"03:25
hongbin#link https://review.openstack.org/#/c/427007/ The spec03:25
hongbinsudipto: there?03:25
sudipto_hongbin, hi yes.03:25
hongbinsudipto_: hey, thanks for joining03:25
sudipto_I willsend out a review of the spec with Eli's comments incorporated.03:25
*** bswartz has quit IRC03:25
*** dmorita_ has joined #openstack-meeting03:26
sudipto_Also i will be sending out the patchsets that hook up resource tracker with node init03:26
sudipto_Then once that is done, we will have to make the necessary changes in the scheduler in zun client.03:26
digasorry, I didn't get time to go through it, it will review it today03:26
sudipto_I would say - don't review the spec as yet, i will make some changes to it.03:26
sudipto_A good time to review would be post 12 hours from now :)03:26
diga:) ok03:27
*** dmorita has quit IRC03:27
sudipto_hongbin, things seem to progress, i just didn't have time last week, but i will resume this week. That's all i have.03:27
digasudipto_: are we trying to use nova schedular capabilities here ?03:27
sudipto_diga, no nova isn't involved.03:27
hongbinsudipto_: np for that, just let us know once you need workers :)03:27
*** eliqiao_ is now known as eliqiao03:28
sudipto_We would want to eventually move to the placement API - when it's ready.03:28
sudipto_But for now, it's our own tables.03:28
digasudipto_: ohh, you are introducing schedular in zun for resources ?03:28
digasudipto_: okay03:29
sudipto_there's already a scheduler in zun :)03:29
sudipto_not introducing one.03:29
hongbinyes, there is a foo scheduler in zun03:29
sudipto_enhancing it...03:29
pksinghfoo scheduler :)03:29
*** galstrom is now known as galstrom_zzz03:29
diga:) okay03:29
*** dmorita_ has quit IRC03:30
hongbinsudipto_: ok, thanks for the update03:30
hongbinany other comment on this bp?03:30
digaI am having less knowledge of zun :), my bad03:30
digawill dive into it to understand things03:30
hongbindiga: np for that03:31
*** armax has joined #openstack-meeting03:31
*** himani has joined #openstack-meeting03:31
digahongbin: :)03:31
hongbinok, if no more comment, let's advance topic03:31
hongbin#topic Discussion of the image API03:31
*** openstack changes topic to "Discussion of the image API (Meeting topic: zun)"03:31
hongbin#link https://etherpad.openstack.org/p/zun-image-api the etherpad03:31
hongbinthis is the topic tabled in the last meeting03:32
*** rderose has quit IRC03:32
*** Apoorva has joined #openstack-meeting03:32
hongbini would leave some time for everyone to go though the etherpad03:32
*** zz_dimtruck is now known as dimtruck03:32
hongbinmkrai: i might have a different opinions with you about storing image in db or not03:33
*** fnaval has joined #openstack-meeting03:34
*** thorst has joined #openstack-meeting03:34
hongbinpersonally, i don't think storing each image in each host in zun db will be scalable03:34
mkrai_hongbin: Sorry there is some issue with my IRC channe;03:34
hongbini lean to the image api to be stateless03:34
*** armax has quit IRC03:34
hongbinbut that is my personal taste03:35
mkrai_hongbin: which API are you talking about?03:35
hongbinmkrai_: image api03:35
mkrai_No I mean which specific API03:35
*** fnaval_ has joined #openstack-meeting03:35
*** links has joined #openstack-meeting03:35
hongbinmkrai_: i think i commented on all of them03:35
mkrai_hongbin: Ok I am reading it03:35
hongbinall, comments on this?03:36
shubhamshongbin:  so you mean, we should not store db info on each host03:37
hongbinshubhams: i think yes03:37
mkrai_hongbin: I think the image API can be made stateless but need to think more on the glance side also03:37
hongbinmkrai_: could you elaborate?03:38
mkrai_Yes sure03:38
shubhamshongbin: I agree to that but at the same time, I think that pulling image on all nodes should not be preferred or default behaviour atleast03:38
*** fnaval has quit IRC03:38
*** thorst has quit IRC03:38
pksinghi have on question, why we are going user->zun->image-repo why not user->image-repo?03:38
pksinghatleast for get calls?03:39
mkrai_For example, when using glance as image driver, the image-list should list only the container images not all images03:39
shubhamspksingh: sorry I didnt get your point03:39
hongbinshubhams: perhaps i agree with you for this comment03:39
mkrai_pksingh: Because we are going the same way for containers also03:39
hongbinshubhams: somehow, the default is to pick a host and pull it03:39
mkrai_shubhams: +103:40
pksinghmkrai_: containers and images are different, we are managing containers not images03:40
hongbinpksingh: i think user-> image-repo can be implemented in zunclient not server?03:40
*** yamahata_ has joined #openstack-meeting03:40
mkrai_pksingh: Agree, but Zun should also provide a way to manage images used for their containers03:40
*** knangia has quit IRC03:41
shubhamshongbin:  then if user specifies a host then image will be pulled on that host else it can be pulled on any random host ?03:41
pksinghhongbin: i think we dont need to implement at the client side, user has docker as well as glance cli,03:41
hongbinmkrai_: if in docker hub, zun image-list will list all the images in Docker Hub?03:41
pksinghmkrai_: i think no coe manages images, AMAIK03:41
*** yamahata has quit IRC03:41
*** iyamahat has quit IRC03:42
hongbinshubhams: yes and no, if specify a host, pull on that host, otherwise, pull on all hosts or a random host03:42
mkrai_hongbin: only the images which container are running similar to `docker images`03:42
hongbinmkrai_: i see03:43
hongbinmkrai_: but docker images is list all the image in localhost03:43
hongbinmkrai_: i am not sure how to do that in multi-host senario...03:44
hongbinpksingh: ack03:44
hongbinpksingh: perhaps we should split the discussion into two, client side and server side03:44
mkrai_hongbin: yes. That is where we need DB03:44
shubhamshongbin: perhaps in db, inside image table we have a column for "host"  that can have value "hostname", "all",?03:44
hongbinmkrai_: shubhams yes, that can be done, but i would worry the scalabillity03:45
hongbinif there is hundreds/thousands of hosts, the db will be too large03:45
hongbinand all the information there is duplicated, it is just the same images in different host03:45
hongbin(not all, some are duplicated)03:46
pksinghin future if we have something like replication then will be inserting the same image for every node in db?03:46
*** yamahata_ has quit IRC03:46
mkrai_host can be a list03:46
hongbinpksingh: interesting idea03:46
hongbinmkrai_: yes, that can be a solution03:47
mkrai_pksingh: the image API was implemented with regard to docker driver. I am not sure whether it can be scaled to COE at this time03:47
pksinghmkrai_: i think we are not just proxy to docker driver, atleast we have scheduler now and more intelligence03:48
digahongbin: mkrai_ : may be we can introduce some filters in image-api which will filter the images to the host03:48
*** dmorita has joined #openstack-meeting03:48
digato distribute images across the hosts03:49
digajust a thought03:49
hongbinif we follow the nova model, host is invisible to non-admin users03:49
hongbinok, it looks mkrai_ shubhams flavor for storing image in zun db03:50
hongbinpksingh: what is your view on this?03:50
*** dimtruck is now known as zz_dimtruck03:50
*** SerenaFeng has quit IRC03:50
pksinghhongbin: i am not sure, but after every pull during container creation we will add the image in db?03:51
mkrai_hongbin: We can take it like this, either we manage image API(for the we need DB) or drop it03:51
*** abhishek_k has joined #openstack-meeting03:52
hongbinmkrai_: yes, we need to decide on one over the other03:52
*** dmorita has quit IRC03:52
hongbinmkrai_: shubhams : perhaps you two could write the draft of the proposal in the etherpad, then we will revisit it in the next meeting03:53
shubhamshongbin: sure03:53
mkrai_hongbin: yes. Give me this week time to think over it and let's make a decision by next meeting03:53
mkrai_pksingh: Please write your thoughts too03:53
hongbinshubhams: mkrai_ : ok03:53
hongbin#topic Open Discussion03:54
*** openstack changes topic to "Open Discussion (Meeting topic: zun)"03:54
yatinkarelHi All, One query:03:54
yatinkarelI started looking for magnum-zun integration and this lead me to k8s-integration(pointed out by hogbin) but after going through the Etherpad(https://etherpad.openstack.org/p/zun-k8s-integration) and meeting discussions(pointed by shubhams) referenced in etherpad,03:54
yatinkarelGot some conflict between Zun's vision(After seeing zun wiki/Meeting Discusions) and multiple COE's support03:54
pksinghmkrai_: sure, may be we can sync up on some other channel03:54
mkrai_pksingh: sure03:54
yatinkarel- Provide Unified API to container Technologies(docker,lxc-docker,rkt)03:54
yatinkarel- COE's implementation in zun itself.(Competition with oter COE's)03:54
yatinkarel- COE's support eventually.(May be an extension, seperate from Zun core api's)03:54
hongbinyatinkarel: i think we agreed to introduce COE support in before03:55
*** gouthamr has quit IRC03:55
hongbinyatinkarel: we just set it to a relatively low priority since we wanted to focus on docker first03:55
*** salv-orlando has joined #openstack-meeting03:55
hongbinyatinkarel: if anyone want to start the work of k8s/coe integration, i think the team will take it03:56
*** thorst has joined #openstack-meeting03:56
*** thorst has quit IRC03:56
yatinkarelhongbin, but as i can see Unified API's vision(Introducing COE's may get distraction), is this OK for zun03:56
*** tpatil has joined #openstack-meeting03:56
*** mriedem has quit IRC03:56
hongbinyatinkarel: as long as the COE was introduced as a zun driver, it will implement the zun api03:57
yatinkarelor start for other container systems(rkt, lxc-docker)03:57
hongbinwe are currently focusing on docker as a starting point03:58
yatinkarelhongbin, Ok03:58
hongbinsupport of other container runtime might be in a low priority03:58
yatinkarelhongbin, Ok for now I would dig more into zun to get more idea03:58
hongbinyatinkarel: what is your point of view about zun's roadmap?03:59
*** samP has joined #openstack-meeting03:59
*** sagara has joined #openstack-meeting03:59
*** diga has quit IRC03:59
hongbinperhaps, we could take it offline03:59
yatinkarelyatinkarel, For me Unified would be the first(but this would lead to limited features(because we have to target common features))03:59
*** rkmrHonjo has joined #openstack-meeting03:59
yatinkarelhongbin, Ok03:59
hongbinall, time is up03:59
hongbinall, thanks for joining the meeting03:59
yatinkarelThanks hongbin04:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"04:00
openstackMeeting ended Tue Mar  7 04:00:07 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-03-07-03.00.html04:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-03-07-03.00.txt04:00
openstackLog:            http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-03-07-03.00.log.html04:00
*** noslzzp has quit IRC04:00
*** rbrady-afk has left #openstack-meeting04:00
*** salv-orlando has quit IRC04:00
*** lakerzhou has left #openstack-meeting04:00
samPhi..o/ > masakari-team04:01
*** Dinesh_Bhor has joined #openstack-meeting04:01
*** Apoorva_ has joined #openstack-meeting04:01
samP#startmeeting masakari04:01
openstackMeeting started Tue Mar  7 04:01:39 2017 UTC and is due to finish in 60 minutes.  The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot.04:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:01
*** openstack changes topic to " (Meeting topic: masakari)"04:01
openstackThe meeting name has been set to 'masakari'04:01
Dinesh_BhorHi all04:01
*** Apoorva has quit IRC04:01
samPHi all04:01
samPlet's start04:02
*** xianghui_ has quit IRC04:02
samP#topic bugs04:02
*** openstack changes topic to "bugs (Meeting topic: masakari)"04:02
*** guoshan has quit IRC04:02
*** takahara has joined #openstack-meeting04:02
samPany bugs to discuss?04:02
tpatil# link: https://bugs.launchpad.net/masakari/+bug/166351304:02
openstackLaunchpad bug 1663513 in masakari "Masakari failed to rescue PAUSED instances" [High,Confirmed] - Assigned to Dinesh Bhor (dinesh-bhor)04:02
samPtpatil: This was my action item from previous meeting.04:03
tpatilNeed your feedback on the proposed solution04:03
tpatilsamP: yes04:03
samPtpatil: sorry for the delay.. I will put my comments today04:04
tpatilsamP: thanks04:04
*** shubhams has left #openstack-meeting04:04
samPany other items?04:04
samPok then, if any other items, pls bring them in AOB04:05
samPlet's jump in to discussion for pike work items04:05
samP#topic Pike work items04:05
*** openstack changes topic to "Pike work items (Meeting topic: masakari)"04:05
samP#link https://etherpad.openstack.org/p/masakari-pike-workitems04:06
samPwe have long list of items.. :)04:06
sagarawe need to decide Pike priorities04:07
samPsagara: sure, and how we gonna do that, put your + on etherpad?04:07
sagarasamP: I agree add + to each items04:08
samPwell, lets take a look,04:08
samP1. Return request Id to caller04:09
samPthis is for add req-id to caller which is done in other projects..04:09
tpatilmasakariclient will be invoked from masakari-monitors, correct?04:10
*** emagana_ has joined #openstack-meeting04:10
*** Namrata has quit IRC04:10
tpatilsamP: Ok04:11
*** emagana has quit IRC04:11
samPI consider this is as a medium priority item, what do you think?04:12
samPmeans, nice to have04:12
tpatilsamP: correct04:12
rkmrHonjosamP:I agree.04:12
sagarasamP: I agree, too04:13
samPOK then let me mark as (M) for medium04:13
samP2. Notifying API progress04:13
tpatilas host failure is a long running task, we need this support04:14
samPI agree04:14
samPlets make it (H)04:14
samP3. Force Stonith04:15
tpatilwhat is needed in masakari to support this feature?04:15
samPThis feature is for, force down host when it cannot rescue04:15
sagaraI think it is important to kill host of semi-failure state04:16
*** markvoelker has joined #openstack-meeting04:16
tpatilyou mean, when masakari fails to process instance notification, then it should kill compute host, correct?04:17
samPfor an ex. some process are failing again and again, then we have to kill that host manually. With this feature, we can automate this04:17
samPor we can use this feature to make sure that failed host is down for sure, before we evacuate. This is important when you do not use pacemaker04:18
*** yonglihe has quit IRC04:19
samPtpatil: did not get what you said04:19
*** yamahata has joined #openstack-meeting04:20
*** mickeys has joined #openstack-meeting04:20
tpatilwho will initiate force down host notification?04:20
tpatilmasakari-engine itself?04:20
samPtpatil: masakari-engine04:21
*** markvoelker has quit IRC04:21
tpatilusing what information masakari-engine can shutdown compute host forcefully?04:22
*** noslzzp has joined #openstack-meeting04:22
samPtpatil: currently we dont have required info to do this. but we can use IPMI04:23
samPHowever, I think this feature is related to recovery method customization04:24
tpatilsamP: correct, masakari-engine is not aware of IPMI info as of now04:24
tpatilWho will write this spec?04:24
samPI can write the spec for this.04:24
*** mickeys has quit IRC04:25
tpatilsamP: Ok04:25
samPI am thinks priority for this as (M), because I think recovery method customization should come first04:26
sagaraI would like to up this items priority to (H)04:27
samPsagara: sure04:27
samPmarked as (H)04:27
sagaraIn HA, IPMI is used generally. Host could not accept any request like ssh in error state. so we need a way/tool to force power down.04:27
sagarasamP: thanks04:28
samPsagara: sure. agree04:28
samPlets move on04:28
samP4. Recovery method customization04:28
samPwe are discussing about this from last cycle..04:29
samPI think we are aware of what it is..04:29
samPshall we make it (H)?04:29
sagarasamP: agree04:30
tpatilAs of now, recovery action are implemented using taskflow04:30
tpatilto make recovery actions configurable similar to mistral, it's going to be a huge task04:30
*** lhx__ has joined #openstack-meeting04:30
samPtpatil: agree. we need to discuss how far we wants to make this configurable. Depend on the depth it might be not that huge04:31
tpatilcustomization can be done using config options quite easily04:31
*** sudipto has quit IRC04:32
*** sudipto_ has quit IRC04:32
samPtpatil: agree, that is one way to do it.04:32
tpatilsamP: ok, let's make this item as high priority04:33
*** sudipto has joined #openstack-meeting04:33
*** sudipto_ has joined #openstack-meeting04:33
samPtpatil: thanks. lets discuss the details later04:33
samP5. Masakari Act/Act04:33
*** bkopilov has joined #openstack-meeting04:34
samPbeside tooz, that else do we have to do to make this happen?04:34
tpatilneed act/act support for masakari-engine only, correct?04:34
*** Apoorva_ has quit IRC04:35
samPtpatil: yes, for api, we can use the same queue for act/act04:35
sagaraI think masakari-api isn't need to do additional work for act/act04:35
samPsagara: think same04:36
*** bswartz has joined #openstack-meeting04:36
samPwhat would it be? for me its (M) than (H)04:37
rkmrHonjosamP: I +1 to (M)04:38
tpatilsamP: +1 for M04:38
*** dmacpher is now known as dmacpher-afk04:38
samPok then, marked it as (M)04:38
*** ihrachys has joined #openstack-meeting04:39
samP6. Documentation04:39
samPIMHO, this is very important..04:39
Dinesh_BhorI think this should be H.04:39
*** armax has joined #openstack-meeting04:39
samPDinesh_Bhor: agree04:39
samPOK then lets mark this as (H)04:39
*** ihrachys has quit IRC04:40
samP7. Ironic Instance HA04:40
*** amotoki has joined #openstack-meeting04:40
*** unicell has joined #openstack-meeting04:40
samPI would like to mark this as (L), because spec and BP for this in ironic is under discussion.04:40
*** unicell has quit IRC04:40
*** unicell has joined #openstack-meeting04:40
samPI dont think we can make huge progress in masakari for this in Pike04:41
tpatilsamP: Ok04:41
rkmrHonjoNo objection.04:41
samP8. Use openstack resource agents for monitor compute nodes04:42
samPI will coordinate this with openstack-HA team, try to get some help from them04:42
*** unicell has quit IRC04:43
tpatilIt's an alternative to masakari-monitors project, correct?04:43
samPfrom my point of view, this is (M) item.04:43
samPtpatil: correct04:43
tpatilIs anyone from the community willing to take up this job04:43
*** sudipto_ has quit IRC04:43
*** sudipto has quit IRC04:43
*** amotoki has quit IRC04:44
samPtpatil: I have to discuss with aspiers about this.04:44
tpatilsamP: Ok04:45
*** donghao has joined #openstack-meeting04:45
*** xianghui_ has joined #openstack-meeting04:45
samPtpatil: I think we can get some help for implement this for HA team04:45
tpatilsamP: that will be great :)04:45
*** hongbin has quit IRC04:45
samPtpatil: I will try.04:46
samPshall we mark this as (M) or (H)?04:46
tpatil+1 for M04:46
*** unicell has joined #openstack-meeting04:47
samPok then, please say otherwise later..04:47
samPlets's go to next04:47
samP9. istral Integration04:47
samP9. Mistral Integration04:47
tpatilIt's nice to have thing, +1 for M04:47
sagarait's large feature, but it is not essentially, so I think it (M)04:48
samPOK then, marked it as (M)04:49
samP10. Functional test 04:49
sagaras/large feature/major feature/04:50
samPwe definitely need this..04:50
*** donghao has quit IRC04:50
sagaraFunctional is (H)04:50
tpatilAre we talking about writing functional tests in Tempest or masakari project?04:51
*** ykatabam has joined #openstack-meeting04:51
rkmrHonjotpatil: In my understanding, this is not tempest.04:51
tpatilrkmrHonjo: OK04:52
samPtpatil: its for masakari project..04:52
samPin masakari04:52
sagarasome of integration test in Masakari CI?04:52
samPsagara: currently we run same tests in masakari CI, but in future masakari CI is for destructive testing.04:53
rkmrHonjosamP: I thought that this item(Functional Test) means the tests like nova/tests/functional. Is this incorrect?04:54
samPIMHO, these functional and unit testing will use openstack infra as other projects04:54
samPrkmrHonjo: correct04:55
tpatilsamP: where can I find the code for tests written for masakari CI job?04:55
samPtpatil: I will share them. currently rkmrHonjo is working on them04:56
tpatilsamP: thanks04:56
samP#action samP share masakari CI test codes04:56
*** Apoorva has joined #openstack-meeting04:56
samPwe dont have much time left..04:56
sagaraso I would like to modify that 'Functional test' to 'destructive testing'04:57
*** thorst has joined #openstack-meeting04:57
*** trinaths has joined #openstack-meeting04:57
samPlets leave it there as functional testing, because we need them.04:57
sagarasamP: ok04:58
samPshall we add a new item call 'destructive testing'04:58
sagaraI will add it04:58
samPI add it04:58
samPOK, only 2 mins left04:59
rkmrHonjosamP: Sorry, destructive test is equal to functional test? I think that these are not equal.04:59
samPrkmrHonjo: no they are not equal04:59
rkmrHonjosamP: thanks.04:59
samPfor the rest of the list, please put your +1 for each topic04:59
*** trinaths1 has joined #openstack-meeting05:00
samPthen we can discuss the prority for those in our next meeting or in ML05:00
tpatilsamP: sounds good to me05:00
samPthank you all.. .let's end this meeting and move to opentack-masakari05:00
*** ayogi has joined #openstack-meeting05:00
*** trinaths1 has quit IRC05:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"05:01
openstackMeeting ended Tue Mar  7 05:01:00 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-03-07-04.01.html05:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-03-07-04.01.txt05:01
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-03-07-04.01.log.html05:01
samPthank you all05:01
sagarathank you05:01
*** trinaths has quit IRC05:02
*** thorst has quit IRC05:02
*** sagara has quit IRC05:03
*** guoshan has joined #openstack-meeting05:03
*** trinaths1 has joined #openstack-meeting05:04
*** trinaths has joined #openstack-meeting05:06
*** trinaths1 has quit IRC05:06
*** rkmrHonjo has quit IRC05:06
*** tpatil has quit IRC05:07
*** zhhuabj has quit IRC05:07
*** lhx__ has quit IRC05:08
*** guoshan has quit IRC05:08
*** trinaths has quit IRC05:08
*** trinaths has joined #openstack-meeting05:08
*** lhx__ has joined #openstack-meeting05:08
*** csomerville has joined #openstack-meeting05:09
*** cody-somerville has quit IRC05:09
*** trinaths1 has joined #openstack-meeting05:09
*** mickeys has joined #openstack-meeting05:11
*** trinaths has quit IRC05:12
*** trinaths has joined #openstack-meeting05:13
*** trinaths1 has quit IRC05:13
*** trinaths has quit IRC05:14
*** nadya has joined #openstack-meeting05:19
*** nadya has quit IRC05:20
*** takahara has quit IRC05:20
*** zhhuabj has joined #openstack-meeting05:20
*** claudiub has joined #openstack-meeting05:29
*** rbak has quit IRC05:31
*** jtomasek has quit IRC05:35
*** bobmel has joined #openstack-meeting05:39
*** salv-orlando has joined #openstack-meeting05:39
*** sudipto has joined #openstack-meeting05:39
*** sudipto_ has joined #openstack-meeting05:39
*** Alex_Staf has joined #openstack-meeting05:40
*** rcernin has joined #openstack-meeting05:40
*** salv-orlando has quit IRC05:43
*** bobmel has quit IRC05:44
*** ijw has joined #openstack-meeting05:46
*** markvoelker has joined #openstack-meeting05:46
*** ykatabam has quit IRC05:47
*** ykatabam has joined #openstack-meeting05:48
*** SerenaFeng has joined #openstack-meeting05:48
*** janki has joined #openstack-meeting05:49
*** markvoelker has quit IRC05:50
*** jrobinson is now known as jrobinson-afk05:57
*** thorst has joined #openstack-meeting05:58
*** youzp has joined #openstack-meeting05:59
*** yangyape_ has joined #openstack-meeting06:01
*** janki has quit IRC06:01
*** janki has joined #openstack-meeting06:01
*** thorst has quit IRC06:03
*** dmorita has joined #openstack-meeting06:03
*** youzp has left #openstack-meeting06:03
*** guoshan has joined #openstack-meeting06:03
*** yangyapeng has quit IRC06:03
*** guoshan has quit IRC06:08
*** dmacpher-afk is now known as dmacpher06:10
*** guoshan has joined #openstack-meeting06:10
*** dmorita has quit IRC06:10
*** sridharg has joined #openstack-meeting06:11
*** yangyapeng has joined #openstack-meeting06:12
*** Apoorva has quit IRC06:12
*** rcernin has quit IRC06:13
*** yangyape_ has quit IRC06:15
*** yangyape_ has joined #openstack-meeting06:16
*** ykatabam has quit IRC06:16
*** salv-orlando has joined #openstack-meeting06:16
*** Dinesh_Bhor has left #openstack-meeting06:16
*** jrobinson-afk has quit IRC06:17
*** adisky_ has joined #openstack-meeting06:19
*** yangyapeng has quit IRC06:20
*** yangyape_ has quit IRC06:21
*** jrobinson-afk has joined #openstack-meeting06:21
*** jrobinson-afk is now known as jrobinson06:21
*** yangyapeng has joined #openstack-meeting06:23
*** mickeys has quit IRC06:26
*** gyee has quit IRC06:26
*** samP has quit IRC06:27
*** gcb has joined #openstack-meeting06:28
*** samP has joined #openstack-meeting06:32
*** dmorita has joined #openstack-meeting06:34
*** e0ne has joined #openstack-meeting06:36
*** samP has quit IRC06:36
*** markvoelker has joined #openstack-meeting06:36
*** dmorita has quit IRC06:38
*** nkrinner_afk is now known as nkrinner06:40
*** e0ne has quit IRC06:40
*** amotoki has joined #openstack-meeting06:41
*** unicell1 has joined #openstack-meeting06:43
*** unicell has quit IRC06:44
*** dschultz has quit IRC06:44
*** samP has joined #openstack-meeting06:45
*** dschultz has joined #openstack-meeting06:45
*** amotoki has quit IRC06:46
*** ijw has quit IRC06:47
*** zhhuabj has quit IRC06:47
*** manikanta_tadi has joined #openstack-meeting06:47
*** markvoelker has quit IRC06:49
*** lamt has joined #openstack-meeting06:51
*** vishnoianil has joined #openstack-meeting06:56
*** e0ne has joined #openstack-meeting06:57
*** lpetrut has joined #openstack-meeting06:58
*** thorst has joined #openstack-meeting06:59
*** thorst has quit IRC07:04
*** abhishek_k has left #openstack-meeting07:04
*** lamt has quit IRC07:06
*** zhhuabj has joined #openstack-meeting07:06
*** jrist has quit IRC07:10
*** jrist has joined #openstack-meeting07:12
*** nijaba has quit IRC07:14
*** e0ne has quit IRC07:15
*** jrobinson has quit IRC07:16
*** andreas_s has joined #openstack-meeting07:17
*** nijaba has joined #openstack-meeting07:20
*** nijaba has quit IRC07:20
*** nijaba has joined #openstack-meeting07:20
*** salv-orl_ has joined #openstack-meeting07:23
*** salv-orlando has quit IRC07:26
*** mickeys has joined #openstack-meeting07:27
*** mickeys has quit IRC07:31
*** anilvenkata has joined #openstack-meeting07:32
*** SerenaFeng has quit IRC07:33
*** dmacpher has quit IRC07:33
*** salv-orl_ has quit IRC07:35
*** armax has quit IRC07:36
*** SerenaFeng has joined #openstack-meeting07:39
*** amotoki has joined #openstack-meeting07:42
*** Alex_Staf has quit IRC07:42
*** lpetrut has quit IRC07:43
*** gcb has quit IRC07:45
*** dschultz has joined #openstack-meeting07:46
*** amotoki has quit IRC07:46
*** yuval has joined #openstack-meeting07:46
*** tesseract has joined #openstack-meeting07:47
*** unicell1 has quit IRC07:48
*** pcaruana has joined #openstack-meeting07:50
*** dschultz has quit IRC07:51
*** SerenaFeng has quit IRC07:52
*** eranrom has joined #openstack-meeting07:52
*** SerenaFeng has joined #openstack-meeting07:53
*** salv-orlando has joined #openstack-meeting07:53
*** claudiub|2 has joined #openstack-meeting07:54
*** kota_ has joined #openstack-meeting07:54
*** rcernin has joined #openstack-meeting07:55
*** makowals_ has quit IRC07:55
*** claudiub has quit IRC07:57
*** askb has quit IRC07:57
*** aeng has quit IRC07:57
*** aeng has joined #openstack-meeting07:57
*** dosaboy has quit IRC07:58
*** lhx__ has quit IRC07:58
*** gcb has joined #openstack-meeting07:58
*** makowals has joined #openstack-meeting07:58
*** ykatabam has joined #openstack-meeting07:58
*** dosaboy has joined #openstack-meeting07:59
eranrom#startmeeting storlets07:59
openstackMeeting started Tue Mar  7 07:59:40 2017 UTC and is due to finish in 60 minutes.  The chair is eranrom. Information about MeetBot at http://wiki.debian.org/MeetBot.07:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.07:59
*** openstack changes topic to " (Meeting topic: storlets)"07:59
openstackThe meeting name has been set to 'storlets'07:59
*** thorst has joined #openstack-meeting08:00
eranromkota_: hey08:00
*** askb has joined #openstack-meeting08:00
*** akihito has joined #openstack-meeting08:00
eranromakihito: Hi08:00
eranromAgenda: https://wiki.openstack.org/wiki/Meetings/Storlets08:01
eranromOur first topic is:08:01
*** ralonsoh has joined #openstack-meeting08:01
eranrom#topic Release status08:01
*** openstack changes topic to "Release status (Meeting topic: storlets)"08:01
*** makowals has quit IRC08:01
*** iceyao has quit IRC08:02
* kota_ is looking at agenda08:02
*** sagara has joined #openstack-meeting08:02
eranromsagara: Hi. agenda: https://wiki.openstack.org/wiki/Meetings/Storlets08:03
eranromwe are at the first topic08:03
kota_sagara: o/08:03
sagaraeranrom: Hi08:03
eranromok, so release status update:08:03
eranromThere were several issues ranging from project templates to openstack ci permissions08:04
*** pksingh has quit IRC08:04
*** thorst has quit IRC08:04
eranromHopefully all is resolved now, and the final patch for the release passes Jenkins, and awaits the release team to approve.08:04
eranromOnce this is done, we should have a PiPy package and should appear in the openstack releases.08:05
*** ltomasbo|away is now known as ltomasbo08:05
kota_eranrom: sounds great that we can look at the release there :-D08:05
*** lhx__ has joined #openstack-meeting08:06
kota_eranrom: btw, do we have to make release note from something... reno?08:06
eranromThe release is still independent. I still need to look at the right model for us (milestones or intermediary)08:06
eranromkota_: I guess we are, but this would be part of doing more official releases. I still need to learn the process...08:07
*** pksingh has joined #openstack-meeting08:08
eranromquestions or next topic?08:08
*** mickeys has joined #openstack-meeting08:08
akihitoI have no question.08:09
sagaraI have no question, please next08:10
eranromakihito: pls go ahead.08:10
eranromakihito: sorry, read to fast :-)08:10
*** iceyao has joined #openstack-meeting08:10
eranrom#topic Pike community goals08:10
*** openstack changes topic to "Pike community goals (Meeting topic: storlets)"08:10
*** kota_ has quit IRC08:11
*** kota_ has joined #openstack-meeting08:11
kota_sorry, my network seems freaky connect/disconnect08:11
eranromAs I have mentioned in the wiki, since we are highly dependent on Swift which still has a lot of work towards py35, the best we can do is a unit test env08:12
eranromkota_: np08:12
eranromWe used to have a py35 test evn set up by Kota, but I think it is broken now...08:12
*** lpetrut has joined #openstack-meeting08:12
eranromOnce fixed we can add a gate job for it, and show progress08:12
kota_eranrom: ah, really? what's broken?08:12
eranromkota_: I was not able to run it. Could it be my env?08:13
*** hashar has joined #openstack-meeting08:14
kota_I'm surprised at we don't have py35 gate job :/08:14
eranromkota_: Any chance it is missing a "basepython = python3.5" in tox.ini?08:14
*** makowals has joined #openstack-meeting08:14
eranromOnce I get it to work, I will add the gate.08:15
eranromthat is add to the gate08:15
kota_eranrom: did it work? i mean basepython-ish08:15
eranromkota_: did not try yet...08:16
eranromkota_: are you running this?08:16
kota_ok, I also will try it. Definately it's a first step to support py308:16
*** amotoki has joined #openstack-meeting08:16
kota_creating the gate job08:16
kota_i mean08:16
*** makowals has quit IRC08:16
eranromkota_: sure.08:16
eranrom#topic Review prioritization08:18
*** openstack changes topic to "Review prioritization (Meeting topic: storlets)"08:18
eranromFirst, I suggest that you add your patches to the pad.08:19
*** yangyape_ has joined #openstack-meeting08:19
eranromkota_: I would LOVE to land your test concurrency patch08:19
akihitosorry. I have WIP patch only..08:20
kota_eranrom: sounds good08:20
eranromakihito: no problem.08:20
kota_eranrom: but as you know, it depends on unique container patch08:20
eranromkota_: right. But its also very close to completion - roght?08:21
eranromI will be happy to land them both :-)08:22
kota_lemme check08:22
*** donghao has joined #openstack-meeting08:22
*** yangyapeng has quit IRC08:22
*** sshnaidm|afk is now known as sshnaidm08:23
kota_it seems like, I was missing to push my patch, I found the diff in my local08:25
kota_let's push it08:25
eranromkota_: ok cool.08:26
kota_the git review calls nothing changed...08:26
kota_er, the new patch set already there, https://review.openstack.org/#/c/437976/408:27
kota_but the 2 concurrency patch just sitting on patch set 308:27
*** donghao has quit IRC08:27
eranromkota_: I see.08:28
kota_i think the patch set 4 is ready for reviews, which includes the unique container cleanup for you, eranrom08:28
eranromkota_: great! I ,ust have missed that, sorry. Let me review. If all is well, should we land?08:28
kota_eranrom: i hope :)08:28
eranromkota_: ok great.08:29
eranromkota_: btw - I have added PUT, COPY support to the ipython patch08:30
eranromanything else on the reviews topic?08:30
akihitoCan I raise the priority of 'Create base server listening on sbus' and 'Use argparse to parse command line options'?08:31
kota_eranrom: will look at the pach08:31
akihitobecause my WIP patch depend on these patches.08:31
eranromkota_: thanks08:32
kota_akihito: is it ready for review?08:32
eranromakihito: I have already +2 40662008:33
akihitoThank you Eran! :-)08:34
eranromakihito: will looked once at 419027, will review the updates.08:34
kota_me too (will do)08:35
kota_and set those into Priority: High08:35
kota_in the etherpad08:35
eranromakihito: I got confused... I have +2 027 in the past, will review the updates...08:35
akihitoThank you!! I confirm the etherpad.08:35
eranromOK, anything else on reviews?08:37
kota_akihito: is the difference from only rebased? for 027 eranrom reviewed08:37
*** phil_ has joined #openstack-meeting08:37
akihitoI confirm. just moment please.08:38
akihitosorry.. At that time, this patch was in charge by Kasinami.08:40
eranromakihito: right. I think that Takashi made some changes since I have reviewed this.08:41
kota_k, got it08:41
kota_akihito: thx for confirmation08:41
*** makowals has joined #openstack-meeting08:41
*** skraynev has quit IRC08:41
akihitoPlease review again one more time...08:42
*** cdub has quit IRC08:42
eranromakihito: sure, will do.08:42
eranromI think this covers all I had in mind.08:42
akihitoeranrom: Thank you!08:42
eranromAny other topics for today?08:42
eranromakihito: welcome08:42
*** cdub has joined #openstack-meeting08:43
sagaraNow I'm thinking resource limiting feature for storlets.08:44
akihitoI have no topic today.08:44
eranromsagara: If you have anything to share (thoughts, design, anything) I will be more then happy to review / help.08:45
*** dmorita has joined #openstack-meeting08:46
sagarasorry, no document, there is just only note08:47
*** dmorita has quit IRC08:47
sagaraI think storlets resource limiting has two point of view.08:47
*** dmorita has joined #openstack-meeting08:47
sagara1. account limiting08:47
sagara2. remains host stable from the high load of storlets applications08:47
*** mickeys has quit IRC08:48
sagaraItem 1, it's similar like swift rate limiting. limit number of storlet request per second for account.08:48
*** fzdarsky_ is now known as fzdarsky08:48
*** dewanee has quit IRC08:48
sagara#link: https://docs.openstack.org/developer/swift/ratelimit.html08:48
sagaraItem 2, now I'm thinking. I will limit CPU core, memory, Disk I/O which are used by container,08:48
sagaraI think it is difficult that how to limit Disk I/O,08:49
sagarait seems to have two design.08:49
sagara2-1, we use docker resource constraint08:49
*** pksingh has quit IRC08:50
sagara#link: https://docs.docker.com/engine/reference/run/#runtime-constraints-on-resources08:50
*** pksingh has joined #openstack-meeting08:50
sagarabut docker constraint I/O feature are like '--device-write-bps', it is cap, so storlets application cannot use host resource effectively.08:50
sagaraso I'm thinking another approach.08:51
sagara2-2, we use priority, like nice, ionice command with docker run.08:51
*** makowals has quit IRC08:51
*** priteau has joined #openstack-meeting08:51
*** dmorita has quit IRC08:51
*** dewanee has joined #openstack-meeting08:52
*** SerenaFeng has quit IRC08:53
eranromsagara: Thanks for sharing your thoughts. I guess I have one comment:08:53
sagaraIt's still on the way, so I need to address that requirement, problem, and design it.08:53
eranromsagara: sure.08:53
sagaraI glad to receive some comment.08:54
*** SerenaFeng has joined #openstack-meeting08:55
eranromthe comment is that we have a container per account, hence any resources being limited in #2 (be it 2-1 or 2-2) this can be employed per account08:55
eranromAlso, I am not sure there is a fundamental difference between limiting IO and limiting memory and CPU where you also cap the amount that can be used by storlet apps08:57
kota_perhaps, we could want to limit via application level08:57
eranromkota_: you mean different storlet apps get different resources?08:57
kota_to do that, perhaps, we could think of `ulimit`ing per storelt-daemon?08:57
kota_eranrom: might be08:57
eranromwe need to finish here. Do you want to continue in #openstack-storlets?08:58
eranromok, so I am ending the meeting and switching to #openstack-storlets08:58
sagaraok, sorry.08:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:58
openstackMeeting ended Tue Mar  7 08:58:58 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storlets/2017/storlets.2017-03-07-07.59.html08:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storlets/2017/storlets.2017-03-07-07.59.txt08:59
openstackLog:            http://eavesdrop.openstack.org/meetings/storlets/2017/storlets.2017-03-07-07.59.log.html08:59
*** kota_ has left #openstack-meeting08:59
*** jtomasek has joined #openstack-meeting08:59
*** mkrai_ has quit IRC09:00
*** dmorita has joined #openstack-meeting09:00
*** nadya has joined #openstack-meeting09:00
*** thorst has joined #openstack-meeting09:01
*** kota_ has joined #openstack-meeting09:03
*** makowals has joined #openstack-meeting09:04
*** pksingh has quit IRC09:04
*** phil_ has quit IRC09:04
*** dmorita has quit IRC09:05
*** toscalix has joined #openstack-meeting09:05
*** thorst has quit IRC09:05
*** pksingh has joined #openstack-meeting09:08
*** phil_ has joined #openstack-meeting09:09
*** dmorita has joined #openstack-meeting09:09
*** dmorita has quit IRC09:14
*** pksingh has quit IRC09:14
*** lpetrut has quit IRC09:15
*** pnavarro has joined #openstack-meeting09:17
*** lpetrut has joined #openstack-meeting09:17
*** yamahata has quit IRC09:19
*** Rocky_g has joined #openstack-meeting09:22
*** sigmavirus has quit IRC09:23
*** jcook has quit IRC09:23
*** sneti has quit IRC09:24
*** belmoreira has joined #openstack-meeting09:24
*** Rockyg has quit IRC09:24
*** martines has quit IRC09:25
*** vgadiraj has quit IRC09:25
*** karthikp_ has quit IRC09:25
*** bkopilov has quit IRC09:26
*** gongysh has quit IRC09:28
*** gongysh has joined #openstack-meeting09:28
*** bkopilov has joined #openstack-meeting09:29
*** sigmavirus has joined #openstack-meeting09:30
*** sigmavirus is now known as Guest8135009:30
*** gongysh has quit IRC09:30
*** ralonsoh_ has joined #openstack-meeting09:31
*** karthikp_ has joined #openstack-meeting09:31
*** fzdarsky has quit IRC09:31
*** jcook has joined #openstack-meeting09:32
*** d0ugal has quit IRC09:32
*** iyamahat has joined #openstack-meeting09:34
*** ralonsoh has quit IRC09:34
*** sneti has joined #openstack-meeting09:35
*** zhhuabj has quit IRC09:35
*** d0ugal has joined #openstack-meeting09:36
*** vgadiraj has joined #openstack-meeting09:36
*** dmorita has joined #openstack-meeting09:36
*** martines has joined #openstack-meeting09:38
*** pksingh has joined #openstack-meeting09:40
*** dmorita has quit IRC09:40
*** Alex_Staf has joined #openstack-meeting09:42
*** fzdarsky has joined #openstack-meeting09:44
*** kevinz has quit IRC09:46
*** aarefiev_afk is now known as aarefiev09:47
*** d0ugal has quit IRC09:48
*** zhhuabj has joined #openstack-meeting09:48
*** mickeys has joined #openstack-meeting09:48
*** shu-mutou is now known as shu-mutou-AWAY09:49
*** d0ugal has joined #openstack-meeting09:50
*** mickeys has quit IRC09:53
*** electrofelix has joined #openstack-meeting09:53
*** bkopilov has quit IRC09:56
*** nadya has quit IRC09:58
*** iyamahat has quit IRC10:01
*** thorst has joined #openstack-meeting10:02
*** ralonsoh_ is now known as ralonsoh10:02
*** e0ne has joined #openstack-meeting10:03
*** dbecker has joined #openstack-meeting10:04
*** xianghui_ has quit IRC10:04
*** guoshan has quit IRC10:05
*** links has quit IRC10:05
*** thorst has quit IRC10:06
*** SerenaFeng has quit IRC10:08
*** bkopilov has joined #openstack-meeting10:09
*** markvoelker has joined #openstack-meeting10:10
*** ociuhandu has joined #openstack-meeting10:10
*** SerenaFeng has joined #openstack-meeting10:10
*** e0ne has quit IRC10:12
*** SerenaFeng has quit IRC10:13
*** SerenaFeng has joined #openstack-meeting10:14
*** yangyape_ has quit IRC10:14
*** links has joined #openstack-meeting10:19
*** salv-orl_ has joined #openstack-meeting10:23
*** e0ne has joined #openstack-meeting10:24
*** iceyao has quit IRC10:25
*** sambetts|afk is now known as sambetts10:25
*** gcb has quit IRC10:26
*** X-dark has quit IRC10:26
*** salv-orlando has quit IRC10:27
*** X-dark has joined #openstack-meeting10:27
*** salv-orl_ has quit IRC10:27
*** caowei has quit IRC10:33
*** iceyao has joined #openstack-meeting10:34
*** alexchadin has joined #openstack-meeting10:34
*** epico has quit IRC10:34
*** iceyao has quit IRC10:38
*** links has quit IRC10:39
*** zhhuabj has quit IRC10:39
*** nadya has joined #openstack-meeting10:40
*** Guest6667 is now known as Guest666610:43
*** dschultz has joined #openstack-meeting10:48
*** mickeys has joined #openstack-meeting10:49
*** emagana has joined #openstack-meeting10:50
*** claudiub|2 has quit IRC10:51
*** emagana_ has quit IRC10:51
*** dschultz has quit IRC10:53
*** mickeys has quit IRC10:54
*** links has joined #openstack-meeting10:55
*** zhhuabj has joined #openstack-meeting10:58
*** pksingh has quit IRC11:00
*** thorst has joined #openstack-meeting11:02
*** bvandenh has quit IRC11:06
*** thorst has quit IRC11:07
*** pksingh has joined #openstack-meeting11:07
*** ltomasbo is now known as ltomasbo|away11:09
*** Vivek has joined #openstack-meeting11:14
*** pksingh has quit IRC11:15
*** bvandenh has joined #openstack-meeting11:16
*** sdague has joined #openstack-meeting11:27
*** donghao has joined #openstack-meeting11:27
*** caowei has joined #openstack-meeting11:27
*** DFFlanders has quit IRC11:32
*** donghao has quit IRC11:33
*** sudipto has quit IRC11:36
*** sudipto_ has quit IRC11:36
*** kevinz has joined #openstack-meeting11:39
*** iceyao has joined #openstack-meeting11:39
*** yangyapeng has joined #openstack-meeting11:39
*** yangyapeng has quit IRC11:40
*** yangyapeng has joined #openstack-meeting11:40
*** jchhatbar has joined #openstack-meeting11:43
*** janki has quit IRC11:46
*** mickeys has joined #openstack-meeting11:50
*** markvoelker has quit IRC11:50
*** mickeys has quit IRC11:54
*** rfolco has joined #openstack-meeting12:00
*** bobmel has joined #openstack-meeting12:01
*** thorst has joined #openstack-meeting12:03
*** aysyd has joined #openstack-meeting12:04
*** thorst has quit IRC12:08
*** neiljerram has joined #openstack-meeting12:08
*** salv-orlando has joined #openstack-meeting12:09
*** bkopilov has quit IRC12:13
*** pnavarro has quit IRC12:14
*** rbowen has joined #openstack-meeting12:15
*** askb has quit IRC12:19
*** GK___1wm____SU has joined #openstack-meeting12:20
*** dgonzalez has quit IRC12:22
*** GK___1wm____SU has quit IRC12:23
*** markvoelker has joined #openstack-meeting12:23
*** salv-orlando has quit IRC12:29
*** SerenaFeng has quit IRC12:31
*** thorst has joined #openstack-meeting12:34
*** ayoung has quit IRC12:35
*** claudiub|2 has joined #openstack-meeting12:42
*** erlon has joined #openstack-meeting12:43
*** zhurong has quit IRC12:45
*** ayogi has quit IRC12:50
*** rbowen has quit IRC12:55
*** rbowen has joined #openstack-meeting12:57
*** jaypipes has joined #openstack-meeting12:59
*** XueFengLiu has joined #openstack-meeting13:00
*** elynn has joined #openstack-meeting13:00
Qiming#startmeeting senlin13:00
openstackMeeting started Tue Mar  7 13:00:21 2017 UTC and is due to finish in 60 minutes.  The chair is Qiming. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: senlin)"13:00
openstackThe meeting name has been set to 'senlin'13:00
Qimingevening, morning13:00
*** ruijie_ has joined #openstack-meeting13:01
Qiminglet's see who else is joining13:01
QimingI know yanyan is on biz trip13:01
Qimingproposed meeting agenda is here: https://wiki.openstack.org/wiki/Meetings/SenlinAgenda#Weekly_Senlin_.28Clustering.29_meeting13:02
XueFengLiuoh, so happy13:02
Qimingpls feel free to add items13:02
*** kevinz has quit IRC13:02
*** kevinz has joined #openstack-meeting13:03
Qimingokay, maybe we can get started13:03
Qiming#topic pike workitems13:03
*** openstack changes topic to "pike workitems (Meeting topic: senlin)"13:03
Qiming#link https://etherpad.openstack.org/p/senlin-pike-workitems13:03
Qimingprofile-only support13:04
Qimingthe sdk side and client side patchs are merged13:04
Qiminghowever, we are still missing the api layer patch13:04
Qimingthat is ... weird13:04
XueFengLiuneed check13:05
*** ijw has joined #openstack-meeting13:05
Qimingoh, request objects have been changed13:05
*** dprince has joined #openstack-meeting13:06
*** elynn_ has joined #openstack-meeting13:06
*** ijw has quit IRC13:06
Qimingjust the history.rst needs a change and we need to bump microversion to 1.6 to enable this13:06
*** lxinhui has joined #openstack-meeting13:06
XueFengLiuYes , tow hongbing and guoshan cooperate to do this bp13:07
Qimingalright, changed the work item to reflect the reality13:08
Qimingnext item13:08
Qimingfeature rich nova server13:08
XueFengLiumaybe we can notice them to add history13:08
elynn_Saw your comments13:08
elynn_Sorry I haven't got time to update it.13:09
Qiminglast time we discussed working on nova server and vdu profile in parallel, maybe elynn_ still wants to fix vdu first13:09
Qimingi'm fine with that13:09
*** sudipto has joined #openstack-meeting13:09
*** sudipto_ has joined #openstack-meeting13:09
Qimingjust want to let you know, I'm starting to look at server adoption13:09
elynn_Yes, I would like to let vdu stable first13:09
elynn_Then back port to nova profile13:10
Qimingwhich means I'm gonna propose changes to nova server profile13:10
*** lhx__ has quit IRC13:10
Qimingso ... it may make your future back port a little difficult13:10
elynn_When you do that, add me as reviewer13:10
Qiminghopefully I'm not changing a lot of existing code13:10
*** ltomasbo|away is now known as ltomasbo13:10
Qimingpls keep working on the vdu profile13:11
elynn_I will update them this week13:11
Qimingrumors said we have got the talk on this accepted13:11
Qimingit means ... at least we have a preview version for people to try out13:11
elynn_Haven't got any emails about the results yet.13:11
lxinhuiOn my side, still test VDU with vims13:11
Qiminghi, xiao xin13:12
lxinhuisome problems jum out13:12
lxinhuihi Qiming13:12
*** ijw_ has joined #openstack-meeting13:12
*** sagara has quit IRC13:12
*** eharney has quit IRC13:12
lxinhuinot sure if it is caused by template or wrong attributes13:12
*** jchhatbar has quit IRC13:12
lxinhuithe ims service can not serve normally as heat template did13:12
lxinhuiwill dig more to root cause the error13:12
Qiminggreat we are making progress on this, ...13:13
*** akihito has quit IRC13:13
elynn_Maybe I should not swallow the jinja2 errors...13:13
Qimingright, that 'pass' is masking out a lot of error conditions13:14
elynn_The design now is when encounter attributes error raised by jinja2 , it will silently pass and use the un-replaced user_data instead.13:14
Qimingem, that deserves a -113:14
elynn_I did that because if someone just want to use {{}} in their user_data, then senile won't raise errors...13:16
*** ijw_ has quit IRC13:16
elynn_I guest I worry too much...13:16
Qimingfailing silently is not good anyway13:16
elynn_Will modify that13:17
Qimingleft a comment with a -1 as reminder, :)13:18
*** kevinz has quit IRC13:18
Qimingmore on this topic?13:18
Qimingmoving on13:18
Qimingengine improvement13:18
*** pchavva has joined #openstack-meeting13:19
*** kevinz has joined #openstack-meeting13:19
Qimingcracking NODE_CHECK actions13:19
XueFengLiuyes, Qiming13:19
XueFengLiunot update13:19
XueFengLiuneed review13:19
QimingI'm thinking if we should make this a little bit self managed13:19
*** elynn_ has quit IRC13:20
Qimingfor NODE_CHECK, CLUSTER_CHECK actions originated/derived from health manager13:20
Qimingwe can label them as self destroyable13:21
*** Drankis has joined #openstack-meeting13:21
Qimingwhen we do action_mark_complete in database, the action delete itself13:21
*** dmorita has joined #openstack-meeting13:21
*** VW has quit IRC13:21
XueFengLiuI thought this before13:22
Qimingfor end users, actions not originated from client requests are strange13:22
Qimingi was even thinking of other alternatives instead of forking actions13:22
Qiminga little bit difficult ...13:22
Qimingnext thing is about server adoption, and maybe stack adoption13:23
*** elynn_ has joined #openstack-meeting13:23
Qimingcurrent thought is to add a node-adopt api13:23
Qimingimplemented as a do_adopt() method in each profile type13:23
Qimingthe method carries a 'confirm=False' parameter and a 'snapshot=False' parameter13:24
*** bkopilov has joined #openstack-meeting13:24
XueFengLiuyes ,this is the base for adopt13:24
Qimingwhich means by default, do_adopt will extract relevant properties from an exising server, filling a new profile spec using the property values13:24
Qimingbut ... since confirm is False, we don't create a new profile yet13:25
Qimingsince snapshot=False, we don't create a server snapshot yet13:25
*** caowei has quit IRC13:25
XueFengLiuI got the idea13:25
Qimingfrom client side, user must explicit specify confirm=True13:26
*** dmorita has quit IRC13:26
*** Alex_Staf has quit IRC13:26
Qimingthen a new node will be created, with a new profile created13:26
Qiminguser can provide a dict to override the properties extracted from an existing server/stack13:26
Qimingwith confirm=False, user will always get a chance to "preview" what kind of a new profile senlin will create for him/her13:27
Qiminga skeleton is ready, need some test cases to be added before submit for review13:28
*** salv-orlando has joined #openstack-meeting13:28
Qimingone thing I met is about networks13:28
*** elynn has quit IRC13:28
*** elynn__ has joined #openstack-meeting13:28
XueFengLiuwhich problem13:28
Qimingfrom server properties extracted, it is really hard to determine whether the server should be created using network name, port id or fixed ip ...13:29
Qimingthe input and the output are different for network properties13:29
*** rossella_s has joined #openstack-meeting13:29
Qimingthat could be something we really need user's intervention13:29
*** bkopilov has quit IRC13:29
Qiminganother problem is that I haven't find an api to get the admin password for a nova server13:29
*** elynn_ has quit IRC13:30
Qimingalthough we can specify it when creating one13:30
*** nadya has quit IRC13:30
Qimingjust an update on the current progress, pls let me know if you have suggestions, on #senlin channel13:30
Qimingmoving on to next topic13:31
QimingRDO shipment13:31
*** hoangcx has joined #openstack-meeting13:32
XueFengLiuAdd requirements in sepc and debug in centos 713:32
XueFengLiuNot difficult13:32
Qiminghave you consulted RDO guys?13:32
XueFengLiuhave not13:32
XueFengLiuWill ping them in #rdo13:33
Qimingokay, feel free to ask questions, there is not many cannibals on earth today13:33
Qimingthanks for driving this13:33
XueFengLiuMy pleasure:)13:33
Qimingalright, meeup in Nanjing13:34
Qimingyour input, XueFengLiu ?13:34
Qimingthanks for drafting the tutorial, I'll spend some time reading it13:34
XueFengLiuThere is a meetup in NanJing 2017,3,1813:34
Qimingplease also check my paper, it is a more comprehensive introduction from developer's perspective13:35
XueFengLiuOn the meetup the first topic is about senlin:)13:35
*** zhangshuai has quit IRC13:35
*** zhurong has joined #openstack-meeting13:36
*** salv-orl_ has joined #openstack-meeting13:36
QimingI'll try my best to join you, but ... cannot promise a thing yet13:36
*** zhangshuai has joined #openstack-meeting13:36
QimingI'm overcommitted ...13:36
Qimingnext topic13:37
QimingI'm not aware of progress in this thread13:37
*** tommylikehu_ has joined #openstack-meeting13:37
XueFengLiuIf you can come, it will be more professional13:37
Qimingnext is about senlinclient functional test13:38
QimingI think the gate is ready, we can start adding test cases now13:38
*** claudiub|2 is now known as claudiub13:38
*** ayoung has joined #openstack-meeting13:39
XueFengLiuThat's good13:39
XueFengLiuWe can distribute ti to team to help do this13:39
*** salv-orlando has quit IRC13:39
Qimingpolicy improvement13:39
Qimingruijie has been improving lb policy for CLUSTER_RECOVER action13:40
XueFengLiuyes, two patches for this13:40
ruijie_yes, but still need improvement13:40
*** mickeys has joined #openstack-meeting13:40
ruijie_for parsing action data13:41
Qimingso far... for actions, we are not fully utilizing its "outputs" property13:41
*** bkopilov has joined #openstack-meeting13:41
Qimingwe have been heavily using its 'inputs' and 'data' property for input parameters and policy decisions respectively13:42
ruijie_It is used outer Senlin .. e.g. MQ message13:42
QimingI cannot recall whether LB policy is alreadying using action.outputs13:42
Qimingwe may want to make sure all actions record there results into 'outputs'13:43
Qimingthough we don't have a strong use case for it yet13:43
*** rossella_s has quit IRC13:43
*** gouthamr has joined #openstack-meeting13:43
Qimingit's just an option, ruijie_, you can still use action.data for LB improvement13:43
Qimingit is not the only valid solution13:44
ruijie_Qiming, you mean dump the data to action.data but not action.outputs?13:44
Qimingit depends13:44
ruijie_I mean for the LB policy13:44
Qimingif the data you are dumping are more suitable to be treated as 'outputs', you can do it13:44
XueFengLiuWhat is the different about action.data and action.outputs13:45
Qimingthen in LB policy you will check it13:45
*** mickeys has quit IRC13:45
Qimingaction.data is designed for internal use, policies use action.data to pass information from one to another13:45
ruijie_Currently, we dump the data to outputs only if node_recover succeeded13:46
Qimingaction.outputs is about the final result from an action's execution13:46
Qimingthat is fine13:46
*** cleong has joined #openstack-meeting13:46
QimingI was not saying it has to be done this way or that way13:46
*** salv-orl_ has quit IRC13:46
ruijie_yes Qiming13:47
Qimingokay, take your time on this, sir13:47
Qimingguess that's all about pike work items,13:47
XueFengLiuOK ,I see,  if action finished, all policies also finished, then we can use "outputs" which is designed for final result13:48
ruijie_not really Xuefeng13:48
*** youzp has joined #openstack-meeting13:48
Qiminglooking ahead ... we are about to prioritize things we want to get done duing Pike13:48
ruijie_there is still an post_op be executed after the action13:48
QimingI've checked the blueprints13:48
Qimingsome are already approved, some need more clarifications13:49
Qiming#topic pike goals13:49
*** openstack changes topic to "pike goals (Meeting topic: senlin)"13:49
*** rossella_s has joined #openstack-meeting13:49
XueFengLiuYes, ruijie_13:49
*** lpetrut has quit IRC13:49
Qimingmy personal opinion on pike goals13:50
*** bbbzhao has quit IRC13:50
Qimingcontainer support, complete health support, usable VNF support13:50
Qimingothers may include node adoption13:51
*** links has quit IRC13:51
Qimingwhich has already started13:51
*** esberglu has joined #openstack-meeting13:51
*** VW has joined #openstack-meeting13:51
Qiminga more dirty work is to rebase profile and policy schema onto versioned objects13:51
*** julim has joined #openstack-meeting13:51
Qimingthen we have a better versioning support all profile/policy versions13:52
*** raildo has joined #openstack-meeting13:52
XueFengLiuQiming, this is you personal things want to do or personal option?13:52
Qimingmy personal view13:52
Qimingpls don't view them as all in my plate13:52
QimingI cannot eat that much13:52
XueFengLiuGot it13:53
*** youzp has quit IRC13:53
QimingI'm asking your suggestions13:53
Qimingwhat do you think should we give a higher priority13:53
*** pnavarro has joined #openstack-meeting13:53
Qimingif you don't have an answer right now, pls think about it and share with team later13:53
*** sudipto_ has quit IRC13:54
*** sudipto has quit IRC13:54
XueFengLiuadoption is high13:54
XueFengLiuothers I will share later13:54
XueFengLiuIn next weekly meeting13:55
Qimingcheck TODO.rst and FEATURES.rst13:55
*** lhx__ has joined #openstack-meeting13:55
Qimingneed some tuning to those lists13:55
*** rossella_s has quit IRC13:55
XueFengLiuAnd about https://blueprints.launchpad.net/senlin/+spec/cluster-lock-cluster-unlock13:55
Qimingfor example, api wg conformance is not a big issue now13:55
Qimingwe have been closely following their guidelines13:55
XueFengLiuneed discuss wiht ruijie_ and Qiming13:56
XueFengLiuWhich is senlin want for cluster-lokc-unlock13:56
Qimingright, that blueprint needs some details13:56
Qiming#topic open discussions13:57
*** openstack changes topic to "open discussions (Meeting topic: senlin)"13:57
Qimingstill a few minutes13:57
ruijie_My thought is mark it as ERROR or something before.13:57
QimingERROR is a state you can recover from13:58
QimingI was thinking that a cluster is frozen13:58
*** reedip_1 has joined #openstack-meeting13:58
Qimingno more actions are accepted before an 'unfreeze' ... :)13:58
ruijie_Right Qiming, only recover action could make it alive again13:58
*** kota_ has left #openstack-meeting13:59
Qiminghow about adding your comment to the etherpad13:59
ruijie_sure Qiming13:59
Qimingtime's up, guys, thx for joining13:59
XueFengLiuOK, will add more in that13:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:59
openstackMeeting ended Tue Mar  7 13:59:41 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-03-07-13.00.html13:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-03-07-13.00.txt13:59
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-03-07-13.00.log.html13:59
*** gouthamr has quit IRC13:59
*** donghao has joined #openstack-meeting14:01
*** tonytan4ever has joined #openstack-meeting14:01
*** alexchadin has quit IRC14:02
*** lxinhui has quit IRC14:02
*** gouthamr has joined #openstack-meeting14:02
*** neiljerram has quit IRC14:04
*** fguillot has joined #openstack-meeting14:04
*** sagara has joined #openstack-meeting14:05
*** donghao has quit IRC14:06
*** neiljerram has joined #openstack-meeting14:07
*** Guest81350 is now known as sigmavirus14:08
*** sigmavirus has quit IRC14:09
*** sigmavirus has joined #openstack-meeting14:09
*** sagara has quit IRC14:09
*** lpetrut has joined #openstack-meeting14:09
*** lamt has joined #openstack-meeting14:14
*** xyang1 has joined #openstack-meeting14:15
*** zhurong has quit IRC14:16
*** youzp has joined #openstack-meeting14:17
*** ociuhandu has quit IRC14:18
*** noslzzp has quit IRC14:20
*** noslzzp has joined #openstack-meeting14:21
*** youzp has left #openstack-meeting14:21
*** nadya has joined #openstack-meeting14:23
*** mriedem has joined #openstack-meeting14:24
*** nadya has quit IRC14:26
*** ihrachys has joined #openstack-meeting14:26
*** sshnaidm is now known as sshnaidm|afk14:28
*** ociuhandu has joined #openstack-meeting14:29
*** alexchadin has joined #openstack-meeting14:30
*** alexchadin has quit IRC14:30
*** lamt has quit IRC14:32
*** nadya has joined #openstack-meeting14:33
*** rderose has joined #openstack-meeting14:36
*** tbh has joined #openstack-meeting14:41
*** nadya has quit IRC14:44
*** mickeys has joined #openstack-meeting14:44
*** jmckind has joined #openstack-meeting14:45
*** toure|afk is now known as toure14:46
*** sshnaidm|afk is now known as sshnaidm14:49
*** mtanino has joined #openstack-meeting14:49
*** mickeys has quit IRC14:49
*** kevinz has quit IRC14:49
*** jmckind has quit IRC14:50
*** jmckind has joined #openstack-meeting14:54
*** ruijie__ has joined #openstack-meeting14:55
*** dschultz has joined #openstack-meeting14:56
*** rbak has joined #openstack-meeting14:56
*** ruijie_ has quit IRC14:58
*** zz_dimtruck is now known as dimtruck14:58
*** sandanar has joined #openstack-meeting14:59
*** mlavalle has joined #openstack-meeting15:00
*** donghao has joined #openstack-meeting15:01
*** dschultz has quit IRC15:01
yuval#startmeeting karbor15:01
openstackMeeting started Tue Mar  7 15:01:37 2017 UTC and is due to finish in 60 minutes.  The chair is yuval. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: karbor)"15:01
openstackThe meeting name has been set to 'karbor'15:01
yuvalHello and welcome to Karbor meeting15:01
*** hoangcx has quit IRC15:02
*** kjw3 has joined #openstack-meeting15:03
*** lamt has joined #openstack-meeting15:03
yuvalgiving it 5 minutes to see if people arrive, it's late in China15:03
*** Julien-zte has joined #openstack-meeting15:04
*** fnaval_ has quit IRC15:05
*** mcunietti has joined #openstack-meeting15:06
*** pnavarro has quit IRC15:06
*** youzp has joined #openstack-meeting15:07
*** hongbin has joined #openstack-meeting15:07
*** emagana has quit IRC15:08
*** pcaruana has quit IRC15:09
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:10
openstackMeeting ended Tue Mar  7 15:10:31 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:10
openstackMinutes:        http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-03-07-15.01.html15:10
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-03-07-15.01.txt15:10
openstackLog:            http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-03-07-15.01.log.html15:10
*** yuval has quit IRC15:10
*** youzp has quit IRC15:11
*** baoli has joined #openstack-meeting15:12
*** baoli_ has joined #openstack-meeting15:13
*** TxGirlGeek has joined #openstack-meeting15:14
*** iyamahat has joined #openstack-meeting15:15
*** baoli has quit IRC15:17
*** aerwin3 has quit IRC15:18
*** saggi has quit IRC15:18
*** saggi has joined #openstack-meeting15:20
*** andreas_s has quit IRC15:21
*** matrohon has joined #openstack-meeting15:21
*** fnaval has joined #openstack-meeting15:22
*** ruijie_ has joined #openstack-meeting15:22
*** pcaruana has joined #openstack-meeting15:23
*** armax has joined #openstack-meeting15:23
*** ijw has joined #openstack-meeting15:24
*** dgonzalez has joined #openstack-meeting15:24
*** salv-orlando has joined #openstack-meeting15:24
*** tonytan_brb has joined #openstack-meeting15:25
*** tonytan4ever has quit IRC15:25
*** ruijie__ has quit IRC15:26
*** donghao has quit IRC15:27
*** alexpilotti has joined #openstack-meeting15:28
*** donghao has joined #openstack-meeting15:29
*** dmorita has joined #openstack-meeting15:30
*** emagana has joined #openstack-meeting15:31
*** emagana has quit IRC15:33
*** annegentle has joined #openstack-meeting15:33
*** sandanar has quit IRC15:33
*** tommylikehu_ has quit IRC15:33
*** dmorita has quit IRC15:34
*** dmorita has joined #openstack-meeting15:34
*** Leo_ has joined #openstack-meeting15:34
*** emagana has joined #openstack-meeting15:35
*** spn has joined #openstack-meeting15:37
*** emagana has quit IRC15:38
*** emagana has joined #openstack-meeting15:39
*** dmorita has quit IRC15:39
*** emagana has quit IRC15:39
*** emagana has joined #openstack-meeting15:40
*** GK___1wm____SU has joined #openstack-meeting15:40
*** claudiub has quit IRC15:40
*** spn has quit IRC15:43
*** awaugama has joined #openstack-meeting15:45
*** iceyao has quit IRC15:45
*** eharney has joined #openstack-meeting15:45
*** GK___1wm____SU has quit IRC15:46
*** kjw3 has quit IRC15:49
*** jlibosva has joined #openstack-meeting15:50
*** lamt has quit IRC15:50
*** awaugama has quit IRC15:52
*** nkrinner is now known as nkrinner_afk15:53
*** knangia has joined #openstack-meeting15:53
*** diablo_rojo has joined #openstack-meeting15:54
*** dschultz has joined #openstack-meeting15:55
*** baoli has joined #openstack-meeting15:56
*** baoli_ has quit IRC15:59
*** lamt has joined #openstack-meeting16:00
*** hieulq_ has joined #openstack-meeting16:01
ihrachys#startmeeting neutron_ci16:01
openstackMeeting started Tue Mar  7 16:01:21 2017 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
ihrachyshi everyone16:01
*** openstack changes topic to " (Meeting topic: neutron_ci)"16:01
openstackThe meeting name has been set to 'neutron_ci'16:01
*** kjw3 has joined #openstack-meeting16:01
ihrachysjlibosva: kevinbenton: manjeets:16:02
* jlibosva already waved16:02
* ihrachys waves back at mlavalle 16:02
ihrachysjlibosva: I long for people attention, it's never enough16:02
*** mcunietti has quit IRC16:02
*** trevormc has joined #openstack-meeting16:03
ihrachysok let's start with reviewing action items from the previous meeting16:03
ihrachys#topic Action items from previous meeting16:03
*** openstack changes topic to "Action items from previous meeting (Meeting topic: neutron_ci)"16:03
*** elynn__ has quit IRC16:03
ihrachys"ihrachys to monitor e-r irc bot reporting in the channel"16:03
ihrachysso, I haven't seen a single report in the channel from the bot16:03
*** lpetrut has quit IRC16:03
*** janki has joined #openstack-meeting16:03
ihrachysso I guess now I have another action item to track, which is to fix it :)16:03
ihrachys#action ihrachys fix e-r bot not reporting in irc channel16:04
ihrachysnext is: "manjeets to repropose the CI dashboard script for reviewday"16:04
ihrachysI see this proposed: https://review.openstack.org/#/c/439114/16:04
*** awaugama has joined #openstack-meeting16:05
ihrachysI guess we can't check the result before landing16:05
*** boden has joined #openstack-meeting16:06
*** donghao has quit IRC16:06
*** electrocucaracha has joined #openstack-meeting16:07
ihrachysok it seems like a good start, I will review after the meeting16:07
mlavalleihrachys: do you have a pointer?16:07
ihrachysmlavalle: pointer to?16:07
mlavallemanjeets patchset16:07
ihrachysI thought I pasted it16:08
mlavalleihrachys: you did. my bad16:08
ihrachysok np16:08
ihrachysit's basically doing a simple gerrit board with bug/* filters for each gate-failure tagged bug16:08
ihrachysso it seems the right thing16:08
ihrachysI wonder if there is place to reuse code between dashboard, but otherwise it seems solid16:09
ihrachysok next item is: "ihrachys to follow up with armax on why trunk connectivity test fails for lb scenario job"16:09
ihrachysso kevinbenton looked at the failures and realized that's because the scenario job for ovs was not using ovsfw16:09
ihrachysand hybrid firewall does not support trunks16:10
*** ijw has quit IRC16:10
*** hashar has quit IRC16:10
ihrachysfor that matter there are a bunch of patches: https://review.openstack.org/#/q/topic:fix-trunk-scenario16:10
ihrachystwo neutron patches in gate, and we will need project-config change in to make it all good16:10
ihrachysthere is still cleanup to do for gate-hook that I will follow up16:10
manjeetssorry for being late16:11
ihrachys#action ihrachys to clean up dsvm-scenario flavor handling from gate-hook16:11
* mlavalle waves at manjeets16:11
ihrachysmanjeets: hi. you have a link to an example dashboard handy?16:11
ihrachys(use url shortener if you paste it directly)16:11
ihrachyseveryone did it at least once in their lifetime!16:12
manjeetsihrachys, I can generate one continue on meeting i'll paste in few mins16:12
ihrachysmanjeets: ok thanks16:12
*** e0ne has quit IRC16:12
mlavalleI certainly did more than once :-)16:12
ihrachysnext item was "ihrachys to follow up on PTG working items related to CI and present next week"16:12
ihrachysI did check the list, and i have some items to discuss, but will dedicate a separate section16:13
ihrachysok next was on me and not really covered so I will repeat it for public shame and the next meeting check16:13
ihrachys#topic ihrachys to walk thru list of open gate failure bugs and give them love16:13
*** openstack changes topic to "ihrachys to walk thru list of open gate failure bugs and give them love (Meeting topic: neutron_ci)"16:13
ihrachysnext was "armax to assess impact of d-g change on stadium gate hooks"16:13
ihrachys(that was the breakage due to local.conf loading changes)16:14
ihrachysI suspect armax is not online just yet16:14
ihrachysand I haven't seen a complete assessment from him just yet. I gotta chase him down. :)16:14
ihrachys#action ihrachys to chase down armax on d-g local.conf breakage assessment for stadium16:14
ihrachysspeaking of which, the next item was for me to land and backport the fix for neutron repo, and we did16:15
ihrachyshere: https://review.openstack.org/#/q/Ibd0f67f9131e7f67f3a4a62cb6ad28bf80e11bbf,n,z16:15
ihrachysso neutron repo should be safe16:15
jlibosvagood job!16:15
ihrachysas for others, we gotta have a dedicated time to look16:15
ihrachysok let's now have a look at our current state of gate16:16
*** annegent_ has joined #openstack-meeting16:16
ihrachys#topic Gate state16:16
*** openstack changes topic to "Gate state (Meeting topic: neutron_ci)"16:16
ihrachysthe neutron grafana is at: http://grafana.openstack.org/dashboard/db/neutron-failure-rate16:17
ihrachysone thing that stands out is api job showing 50% failure rate in sliding window16:17
ihrachysgood news is that it should be fixed now16:17
*** XueFengLiu has quit IRC16:18
ihrachysthere was a breakage caused by devstack-gate patch that was fixed by a revert: https://review.openstack.org/#/c/442123/16:18
*** GK___1wm____SU has joined #openstack-meeting16:18
ihrachyssince it's not the first time we are borked by d-g changes, I proposed to add a non voting neutron-api job for devstack-gate here: https://review.openstack.org/#/c/442156/16:18
*** GK___1wm____SU has quit IRC16:19
*** annegentle has quit IRC16:19
ihrachysnext job of concern is gate-tempest-dsvm-neutron-dsvm-ubuntu-xenial16:20
ihrachyscurrently at 25%16:20
ihrachysin gate16:20
ihrachysofc some of it may be due to OOM killers and libvirtd crashing16:20
ihrachysbut since it stands out16:20
*** julim has quit IRC16:20
ihrachysit's probably more than just that16:20
ihrachysand 25% in gate is not good16:21
ihrachysany ideas about what lingers the job?16:21
*** kristian__ has joined #openstack-meeting16:21
ihrachysthere was a nasty metadata issue the prev week that kevinbenton tracked down to conntrack killing connections for other tenants16:21
mlavalleihrachys: you meant gate-tempest-dsvm-neutron-dvr-ubuntu-xenial, right?16:21
ihrachysthat should be fixed by https://review.openstack.org/#/c/441346/16:21
ihrachysmlavalle: hm yeah, dvr, sorry16:22
*** belmoreira has quit IRC16:22
* haleyb hears dvr and listens up16:23
*** pradk has joined #openstack-meeting16:23
*** cody-somerville has joined #openstack-meeting16:23
*** cody-somerville has quit IRC16:23
*** cody-somerville has joined #openstack-meeting16:23
ihrachyshaleyb: any ideas what makes dvr look worse than others? ;016:23
manjeetsihrachys, is there any patch in progress for gate issues16:24
manjeetscurrentlt i don't see any which have either bug id in message or in topic16:24
ihrachysmanjeets: not that I know of for dvr job, hence I wonder16:24
haleybihrachys: it's probably the one lingering bug we have, https://bugs.launchpad.net/neutron/+bug/150900416:24
openstackLaunchpad bug 1509004 in neutron ""test_dualnet_dhcp6_stateless_from_os" failures seen in the gate" [High,Confirmed]16:24
ihrachysoh you mean generally16:24
*** Julien-zte has quit IRC16:25
*** csomerville has quit IRC16:25
manjeetsit used to show some patches, logic i added was either bug id in commit message or topic of patches16:25
*** Julien-zte has joined #openstack-meeting16:25
haleybalthough that bug is more general l3, but happens more with dvr16:25
*** Julien-zte has quit IRC16:25
ihrachysmanjeets: makes sense. let's have a look at specific cases after the meeting.16:25
mlavallehaleyb: +16:25
*** anilvenkata is now known as anilvenkata_afk16:26
*** hieulq_ has quit IRC16:26
ihrachyshaleyb: and do we have any lead on it?16:26
*** pcaruana has quit IRC16:26
*** Julien-zte has joined #openstack-meeting16:27
*** Julien-zte has quit IRC16:27
haleybihrachys: no it has been elusive for a long time, but not 25%, in the single digits16:27
ihrachysok I feel there is some investigation to do16:27
ihrachyspreferrably for l3 folks16:28
ihrachysare you up for the job?16:28
*** Julien-zte has joined #openstack-meeting16:28
*** Julien-zte has quit IRC16:28
*** phil_ has quit IRC16:28
mlavalleihrachys: if this is a priority, I can devote some bandwidth to it16:28
mlavallehaleyb: ^^^ let me know if you want me to do this16:28
ihrachysmlavalle: CI stability especially for jobs that are in gate is of priority for the whole project16:29
ihrachysthe failures slow down merge velocit16:29
haleybthanks mlavalle, yes, sometimes a new set of eyes will find something16:29
ihrachys#action haleyb and mlavalle to investigate what makes dvr gate job failing with 25% rate16:29
haleybihrachys: but above you said there was a 25% failure?  that wasn't the dvr job16:29
ihrachysthat was dvr, I made a mistake16:29
haleyboh, now i see it in grafana16:30
ihrachyshaleyb: see here http://grafana.openstack.org/dashboard/db/neutron-failure-rate?panelId=5&fullscreen16:30
*** rcernin has quit IRC16:30
ihrachysfinally, we have fullstack job and whopping ~100% failure rate16:30
*** nadya has joined #openstack-meeting16:30
ihrachysjlibosva: what's happening with it? caught a flu?16:31
jlibosvaI haven't checked, just see it's really busted16:31
jlibosvaI saw couple of failures related to qos16:31
*** lhx__ has quit IRC16:31
ihrachysexample: http://logs.openstack.org/10/422210/10/check/gate-neutron-dsvm-fullstack-ubuntu-xenial/3aad0fa/testr_results.html.gz16:31
ihrachysyeah qos, I saw it a lot before16:31
jlibosvabut didn't get to it yet, you can add me an AI to have a peak16:31
*** Drankis has quit IRC16:32
ihrachysI assume it's on ajo ;)16:32
haleybihrachys: sometimes dvr is just the victim, has more moving parts, we make no changes and failures rise and fall16:32
* haleyb realizes that's a bad excuse16:32
ihrachyshaleyb: bingo ;)16:32
ihrachysjlibosva: I will try to have qos folks have a look, and if not we'll revisit16:32
ihrachysit's not too pressing since it's non-voting16:33
ihrachys#action ajo to chase down fullstack 100% failure rate due to test_dscp_qos_policy_rule_lifecycle failures16:33
jlibosvabut it's almost up to 100% :-/16:33
jlibosvaI'll have a look anyways :-P16:33
ihrachysyou are a free agent of your destiny16:33
ihrachys#action jlibosva to help ajo understand why fullstack fails16:34
*** dprince has quit IRC16:34
ihrachysok seems like we have grasp of current issues, or have folks on hooks for remaining unknowns ;)16:34
ihrachyslet's move on16:34
haleybihrachys: for example, in the tempest gate, the dvr failure graph mimics the api failure one, just lower16:34
*** ijw has joined #openstack-meeting16:35
ihrachyshaleyb: I think dvr job was not broken by gate-hook, but maybe just monitor for a day before jumping on it16:35
haleybwill do16:35
*** GK___1wm____SU has joined #openstack-meeting16:35
ihrachysif it doesn't resolve itself, then start panicking16:35
ihrachysok moving on16:35
ihrachys#topic PTG followup16:35
*** openstack changes topic to "PTG followup (Meeting topic: neutron_ci)"16:35
*** eharney_ has joined #openstack-meeting16:36
ihrachysso I went through the -final etherpad at: https://etherpad.openstack.org/p/neutron-ptg-pike-final and tried to list actionable CI items16:36
ihrachyslet's review those and find owners16:36
ihrachysfirst block is functional job stability matters16:36
ihrachysseveral things here to track, though some were already covered16:37
ihrachysfor one thing, the ovsdb-native timeout issue16:37
*** markvoelker has quit IRC16:37
ihrachysthere were suggestion that we should try to eliminate some of broken parts from the run16:38
*** tesseract has quit IRC16:38
ihrachys1. raise timeout for ovsdb operations. I think there was some agreement that it may help to reduce the rate16:38
*** eharney has quit IRC16:38
ihrachysnot sure if otherwiseguy still feels ok-ish about it, considering his late fixes up for review16:38
*** eharney_ is now known as eharney16:39
ihrachysI am specifically talking about https://review.openstack.org/441208 and https://review.openstack.org/44125816:39
*** JoseMello has joined #openstack-meeting16:39
otherwiseguyihrachys, I'm ok with raising timeout.16:39
*** tonytan_brb has quit IRC16:39
otherwiseguyI think it'll help. but we need to raise the probe_interval as well.16:40
*** tonytan4ever has joined #openstack-meeting16:40
ihrachysotherwiseguy: would you mind linking your patches to the correct bug in LP?16:40
*** sridharg has quit IRC16:40
otherwiseguyihrachys, will do16:40
ihrachysthat will help them to show up at the gerrit CI board manjeets is working on16:40
ihrachysok then I guess it's on ajo to revive the timeout patch16:41
ihrachys#action ajo to restore and merge patch raising ovsdb native timeout: https://review.openstack.org/#/c/425623/16:41
*** jamesdenton has joined #openstack-meeting16:42
ihrachysanother thing that should reduce the number of tests for the job and hence the chance of hitting the issue is otherwiseguy's work to spin off ovsdb layer into a separate repo16:42
*** julim has joined #openstack-meeting16:42
ihrachysstarting from https://review.openstack.org/#/c/442206/ and https://review.openstack.org/#/c/438087/16:42
ihrachysit's wip16:42
*** julim has quit IRC16:43
ihrachysI believe it won't fix the issue for the neutron gate because we still have tests that do not target the layer but use it (like dhcp agent)16:43
otherwiseguyihrachys, theoretically it could move out of WIP as soon as soon as added to openstack/requirements16:43
ihrachysotherwiseguy: oh it's passing everything? you're quick16:43
*** janki has quit IRC16:44
ihrachysotherwiseguy: you could as well Depends-On the patch to pass the remaining job16:44
otherwiseguyI'll have to merge in any changes we've made since posting it, but git subtree handles that.16:44
ihrachysand then just remove WIP16:44
manjeetsotherwiseguy, would there be any version for initial ovsdb ?16:44
otherwiseguyI guess I need to add to global-requirements.txt as well? wasn't sure if there was something automated if added to projects.txt in requirements.16:45
ihrachysotherwiseguy: projects.txt only makes requirements bot to propose syncs for your repo16:45
ihrachysit doesn't change a thing beyond that16:45
ihrachys(unless I am completely delusional)16:45
otherwiseguymanjeets, there are some dev versions posted to pypi. I'll probably make a real release 0.1 release soonish.16:45
*** baoli has quit IRC16:46
*** baoli has joined #openstack-meeting16:46
ihrachysotherwiseguy: so, you need to add ovsdbapp into global-reqs.txt and upper-constraints.txt16:46
otherwiseguyTHere is some refactoring I'd like to do before an actual 1.0 release. But once everything is completely up, I can do Depends-On changes for projects to handle my refactoring.16:46
*** GK___1wm____SU has quit IRC16:46
otherwiseguyihrachys, Ok. I'll do that as well.16:46
ihrachysand depends-on that, not the patch that modifies projects.txt16:46
manjeetsotherwiseguy, then don't we need upper-constraint as well (I may be wrong) ?16:47
*** tbh has quit IRC16:47
ihrachyswe do16:47
ihrachysotherwiseguy: so you are not going to adopt it in neutron before 1.0?16:47
otherwiseguyI'll go through the instructions on project creation doc page.16:47
otherwiseguyihrachys, we can (and should) adopt immediately. Just going to change some, but I can keep things in sync. Especially after adding some more cores soon. :p16:48
ihrachysotherwiseguy: as long as it does not go too far to make adoption more complicated16:48
ihrachysconsider what happened to oslo.messaging :)16:48
ihrachysbetter stick to what we have and refactor once we have projects tied16:49
otherwiseguyihrachys, It'll be easier just having to make the ovsdb changes in one place as opposed to making them in neutron, then merging to ovsdbapp, then moving things, etc.16:49
*** denismakogon has joined #openstack-meeting16:49
*** felipemonteiro_ has joined #openstack-meeting16:49
ihrachysunless you see a huge architectural issue that requires drastic changes16:49
otherwiseguyRight, I'm planning on moving everything to using ovsdbapp as is, then gradually making changes later.16:49
*** julim has joined #openstack-meeting16:50
ihrachysack, good16:50
ihrachysok that seems to progress and I am sure otherwiseguy will complete it till next meeting ;)16:50
otherwiseguyI will be pretty obsessed with it for a bit.16:50
ihrachysanother item from PTG was driving switch to ha+dvr jobs for most gate jobs16:50
ihrachysfor that matter, anilvenkata_afk has the following patch in devstack-gate that doesn't move too far lately: https://review.openstack.org/#/c/383827/16:51
*** kjw3 has quit IRC16:51
ihrachysAnil just rebased it16:51
ihrachysI will leave an action item on anilvenkata_afk to track that16:51
ihrachys#action anilvenkata_afk to track inclusion of HA+DVR patch for devstack-gate16:52
ihrachysthere were also talks about reducing the number of jobs in gate, like removing non-dvr, non-multinode flavours wherever possible16:52
ihrachysanyone willing to take the initial analysis of what we can do and report the next week with suggestions on what we can remove?16:53
*** strigazi is now known as strigazi_AFK16:53
haleybihrachys: and i had just proposed to make the dvr-multinode job voting, but dvr+ha+multinode is just as good16:53
ihrachysbtw not just in gate but in check queue too, we have some jobs that are not going anywhere, or that are worthless for what I wonder (ironic?)16:54
*** julim has quit IRC16:54
ihrachyshaleyb: I would imagine that instead of piling new jobs on top we would remove non-dvr and replace them with dvr flavours16:54
haleybthey have to be voting in check to be voting in gate from what i learned16:54
ihrachyshaleyb: link to the patch would be handy16:54
haleybi had started that in newton16:55
ihrachysok. considering that we currently have 25% failure rate for the job, it may be challenging to sell its voting status ;)16:55
ihrachyslet's discuss on gerrit16:55
ihrachysso, anyone to do the general analysis for all jobs we have?16:56
ihrachysok let's leave it for the next meeting to think about, we are running out of time16:56
*** yamahata has joined #openstack-meeting16:57
ihrachyswe will follow up on more ptg items the next week16:57
ihrachys(dude the number is huge)16:57
ihrachys#topic Open discussion16:57
*** openstack changes topic to "Open discussion (Meeting topic: neutron_ci)"16:57
manjeetsihrachys, one more missing bit py35 demonstration via tempest or functional job16:57
ihrachysmanjeets: yeah it's in my list for next week16:58
ihrachysthere are more :)16:58
ihrachysI would like to raise attention to jlibosva docs patch on gerrit rechecks: https://review.openstack.org/#/c/426829/16:58
ihrachysI think it's ready to go though I see some comments from manjeets that may need addressing16:58
ihrachysI don't believe that the policy should apply to 'gate deputies' only16:59
ihrachys(btw we don't have such a role)16:59
jlibosvaI'll look at the comments16:59
manjeetsihrachys, It is for upgrades but still ci gate-grenade-dsvm-neutron-linuxbridge-multinode-ubuntu-xenial-nv16:59
ihrachysto make it work, everyone should be on the same page and behave responsibly16:59
jlibosvaI think he meant bug deputies?16:59
manjeetsi need to follow up on that just a reminder will do that after meeting16:59
ihrachyswell I would not expect bug deputies to be on the hook to read logs now16:59
ihrachysit's enough work to triage bugs already17:00
ihrachysmanjeets: ok17:00
ihrachysjlibosva: let's follow up on manjeets's comments in gerrit17:00
ihrachyswe are out of time17:00
manjeetsor there can be separate gate deputies not sure if that would make more sense17:00
ihrachyswe haven't covered everything we should have, but that's ok, it means we have work to do ;)17:00
ihrachysthanks all17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Tue Mar  7 17:00:46 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-03-07-16.01.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-03-07-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-03-07-16.01.log.html17:00
*** aarefiev is now known as aarefiev_afk17:00
dschultz#startmeeting functions17:01
openstackMeeting started Tue Mar  7 17:01:22 2017 UTC and is due to finish in 60 minutes.  The chair is dschultz. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: functions)"17:01
openstackThe meeting name has been set to 'functions'17:01
dschultzHello all! Welcome to the first project meeting for project Picasso - Functions as a Service for OpenStack17:02
*** mlavalle has left #openstack-meeting17:02
denismakogonwhat's up?17:02
dschultzcan we do a quick roll call to see who's with us? then we'll get started17:02
dschultzperhaps they fell silent or will join us later. let's resume17:03
dschultz#topic Discuss time slot for future meetings17:04
*** openstack changes topic to "Discuss time slot for future meetings (Meeting topic: functions)"17:04
*** sshnaidm is now known as sshnaidm|off17:04
dschultzCurrent cadence is biweekly (even weeks) on Tuesdays at 1700 UTC.17:04
denismakogoni'm in UTC+2 (east europe)17:04
*** robputt has joined #openstack-meeting17:04
*** GK___1wm____SU has joined #openstack-meeting17:04
robputthi everyone17:05
dschultz1700 is about the earliest i can do while still being caffeinated, but open to later times if that works best for the majority17:05
dschultzhi rob!17:05
*** tonytan4ever has quit IRC17:05
dschultzdo you have any preference on meeting time?17:05
robputtright now is cool for me :-)17:06
dschultzi'm UTC-7 (Colorado)17:06
dschultzok, cool17:06
*** dprince has joined #openstack-meeting17:06
robputtI am in UTC time zone at the moment, but in summer months I am in BST (aka UTC+1)17:06
denismakogonso i think we're fine with having meeting in CT timezone, should be fine for all of us17:06
dschultzSo let's keep current schedule for now17:07
dschultz#topic New project name to replace Picasso17:07
*** openstack changes topic to "New project name to replace Picasso (Meeting topic: functions)"17:07
*** jlibosva has left #openstack-meeting17:07
robputtbtw I moved all the stuff in the dev mailing list into the etherpad17:07
denismakogonyeah, pretty hot question, Picasso is registered trademark https://trademarks.justia.com/854/80/picasso-85480361.html17:08
dschultzSo, it's come to our attention that we'll need to change the project name from Picasso due to legality of the name, as Denis mentioned.17:08
robputtthe name itself?17:08
*** GK___1wm____SU has quit IRC17:08
robputtor just the shape and style?17:08
*** yamahata has quit IRC17:08
dschultzJust the project name17:08
robputtwow, Picasso dental wax17:08
robputtdon't wanna annoy these guys :-P17:08
*** iyamahat has quit IRC17:08
robputtthey might have an army of dentists come after us :-P17:09
denismakogonwe need to ask folks from Foundation for help i think17:09
robputtI'll be honest the reason why I became interested in this project17:09
dschultzSo, I'd like us to come up with some alternatives and vote on it at the next meeting. Sound good? I'd like community input here, but I was thinking we could maybe just call it Functions?17:09
robputtwas because we already have our own internal Function as a Service built on an OpenStack ecosystem17:09
robputtmaybe we could just steal the name from my project if Rackspace is happy with it?17:09
robputtit's short hand latin for "to execute"17:10
denismakogoni think we need couple options that we can present to Foundation17:11
dschultzha, i like it. want to make note of that? Current options: Functions, Exequor (pending approval)17:11
robputtwho is making notes?17:11
*** kjw3 has joined #openstack-meeting17:11
robputtwant me to add them to the etherpad?17:11
denismakogonchat bot, no?17:11
*** tonytan4ever has joined #openstack-meeting17:12
dschultzchat bot will do some notes, but best to keep it in etherpad.17:12
denismakogonmakes sense17:12
dschultzthank you robputt17:12
*** markvoelker has joined #openstack-meeting17:12
dschultzanything else on the project name topic?17:13
robputterrr, nothing else from me at the moment17:14
robputtbut maybe I can think of some other options17:14
*** dandruta has joined #openstack-meeting17:14
robputtbtw is the intention to keep appending successive meetings to the etherpad?17:14
*** jamesdenton has quit IRC17:14
robputtif so we can just copy this topic to the next meeting and let people add their thoughts in the ehterpad17:14
*** designbybeck has joined #openstack-meeting17:14
*** rtrox has joined #openstack-meeting17:15
denismakogonmakes sense, dschultz what you think?17:15
robputthey rtrox :-)17:16
dschultzi think it would be best to have a new etherpad for each meeting, using the date timestamp of the meeting. but at first, since this project is in the early stages i don't see any issue with doing as suggested17:16
*** GK___1wm____SU has joined #openstack-meeting17:16
denismakogonSo, project name is still quite open, we don't have deadline for now since we're a bit far away from becoming a BigTent project17:16
*** ntpttr_ has joined #openstack-meeting17:16
robputtwow, you guys are very ambitious :-D17:17
robputtI think BigTent status takes alot17:17
dschultzright, it's not urgent but something we need to consider moving forward.17:17
dschultzok, moving on17:18
dschultz#topic Roadmap and blueprints17:18
*** openstack changes topic to "Roadmap and blueprints (Meeting topic: functions)"17:18
denismakogondschultz: may i step in?17:18
denismakogonSo, the main thing on our roadmap is to build Picasso V2 that wouldn't be a thin API layer in front of IronFunctions, but would be a set of extensions and middleware for IronFn17:20
denismakogonNext thing - bring more container techmologies17:20
denismakogonlike K8t, roket.io17:20
*** donghao has joined #openstack-meeting17:20
robputtare these container functionality under IronFunctions or directly under Picasso / whatever we call it?17:21
denismakogonthird thing - support building functions from source code17:21
robputtBy this do you mean providing it with a Python package etc... rather than a prebaked Docker image?17:21
*** baoli has quit IRC17:21
denismakogonfunctionality is inside of IronFunctions lib called runner that is an abstraction above Docker (for now)17:21
dschultzrobputt: IronFunctions has a backend container driver (default: Docker), which is pluggable to support drivers for K8s, rkt, etc. #link https://github.com/iron-io/runner17:22
denismakogonrobputt: yes, some sort of, but such feature will involve couple OpenStack services like Glance, Glare and Swift17:23
*** ltomasbo is now known as ltomasbo|away17:24
denismakogonSo, the main thing we'd do is to switch from Python code to Go code because IronFunctions is pure Go.17:24
robputtHow does the community feel about this?17:24
robputthaving two projects in different languages doesn't prevent them co-existing or interacting with eachother17:25
denismakogonaccording to the latest info if there's a tech reason to use Go there's no objections17:25
robputtI know in the past there was alot of push back when Swift team wanted to use some GoLang components for performance reasons as Go was (and to my knowledge still isn't) an official OpenStack unless you have extenuating circumstances17:25
denismakogonit was said by TC members17:25
*** Apoorva has joined #openstack-meeting17:26
*** GK___1wm____SU has quit IRC17:26
*** donghao has quit IRC17:26
*** iyamahat has joined #openstack-meeting17:27
dschultzyes, Go is a hot topic as far as community support. let's make sure we approach this the right way...17:27
*** jamesdenton has joined #openstack-meeting17:27
dschultzdenismakogon: we do not yet have a blueprint on what you proposed, right? should that be an action item? maybe highlight the pros/cons17:27
denismakogonGo language was decided to be accepted as second valid language for backend development in OpenStack, there are somethings that are requiring to be done in infra to support Go, but Swift already has feature branches that are including Go code17:27
denismakogondschultz: right17:27
*** ravelar has joined #openstack-meeting17:28
denismakogoni'll make spec by the next meeting17:28
dschultz#action denismakogon to create blueprint for moving from Python to Go17:28
dschultzawesome, added action item17:28
notmynamegood luck17:28
robputtI personally object unless there is a real reason to use GoLang17:28
robputta good example is alot of OpenStack stuff hasn't been ported to GoLang17:29
*** matrohon has quit IRC17:29
robputte.g. Keystone-AuthMiddleware, Oslo Packages and so on...17:29
denismakogonSo, the thing is Picasso is fully mimics IronFunctions API plus two features - keystone auth and public/private functions17:29
*** trevormc has left #openstack-meeting17:29
robputtI think a GoLang based service would be very alien to OpenStack deployers17:30
robputtTrue, in it's current form Picasso is a proxy layer with auth for IronFunctions17:30
*** mickeys has joined #openstack-meeting17:31
robputthowever proxy layers don't really need to be the same language as the underlying technology17:31
denismakogonrobputt: you are right, that's why we'll invest time into helping infra and oslo teams to build the same set of libs in Go17:31
*** GK___1wm____SU has joined #openstack-meeting17:31
robputtWell, if we are willing to put in the work to bring OpenStack standard set of libs into GoLang17:31
robputtand are happy to maintain them accross future releases then I guess its more of an interesting proposition17:31
rtroxdenismakogon what is the big selling point for a port to GoLang?17:31
robputtbut if we cannot commit to that, I think we are doing a disservice to the community by leaving them between a rock and a hard place with some Go stuff which gets out of date17:32
denismakogonyes, in any case we'll align with all requirements to join big tent someday17:32
*** GK___1wm____SU has quit IRC17:32
robputtThe reality is there are ALOT of oslo libs, and stuff like keystone-authmiddleware which ideally would need to be ported to Go and maintained for this to be a positive move17:33
rtroxbecause so far, the "pro" that I've seen is just that ironfunctions is written in go, is there some functionality or use-case that is leading you to want a go rewrite?17:33
denismakogonrobputt: all of this will be done as complete Go integration17:33
robputtI have to say Go worries me as a direction for the project17:34
robputtits alot of overhead for not alot of gain17:34
robputtand simply because IronFunctions is Go doesn't really mean Picasso should be Go too17:34
denismakogonrtrox: we'd reduce amount of code, we'd reduce number of services to 1 service with pre-built load balancer17:34
*** mickeys has quit IRC17:35
robputtIs there anyone from the community we can refer to to decide under which extenuating circumstances we should use an alternative language to Python?17:35
robputtdenismakogon: by moving this to Go, would is literally be absorbed into IronFunctions with 100% vendor lock in?17:35
denismakogonIronFunctions is not vendor-locked17:36
robputtno but Picasso is17:36
*** gagehugo has joined #openstack-meeting17:36
robputtIt's like saying "libvirt is not vendor locked so Nova should only have a libvirt driver and nothing else"17:36
robputtthe reality is what if someone wanted to use Fission behind Picasso?17:37
robputtor dare we say it even a lambda driver if they so choose todo so?17:37
dschultzwell keep in mind IronFunctions is open-source, and the idea behind it is to get away from vendor lock-in like AWS17:37
dschultzIronFunctions actually supports importing Lambda functions17:38
robputtTrue I get this, but for me the vendor lock in should be at the Picasso level not at IronFunctions level17:38
robputtas a precedent no other big tent API has lock in to a particular backend driver17:38
denismakogoneven with Fission, you can build a driver to IronFunctions17:38
robputtI think you are missing the point here,17:39
*** ntpttr_ has quit IRC17:39
robputtin it's current form with Picasso you MUST use IronFunctions17:39
*** dmorita has joined #openstack-meeting17:39
robputtthere is no freedom to choose and alternative17:39
*** fzdarsky is now known as fzdarsky|afk17:39
robputtI understand IronFunctions is opensource and so on, but the real thing behind FOSS software is freedom17:39
robputtas well as being opensource17:40
dschultzI think I follow robputt: but from an architecture view, it seems like a tall order to be able to support multiple platforms/frameworks, when the common denominator is the container execution engine, which should be pluggable17:40
robputtto be honest, if we are simply adding keystone auth to IronFunctions17:40
dschultzdon't get me wrong, i agree with your comments and concern. just not sure how we can approach it17:40
robputtI don't really think there is a project here, it may as well just be part of IronFunctions with the ability to turn on or off keysotne auth in the config file17:41
robputtWell, we should look to Nova, Neutron, Cinder, Swift and so on17:41
robputtto understand how they implemented multiple backend drivers17:41
rtroxunless you're discussing the entire ironfunctions code base become part of not-picasso?17:42
robputtCinder is probably a good one to consider as there are lots of multiple vendor backends for Cinder17:42
*** rossella_s has joined #openstack-meeting17:42
*** mickeys has joined #openstack-meeting17:42
robputtfrom simply having the block device on a disk on a Linux box, to different SANs and NAS configurations17:42
robputtI am confident if they can get multiple pluggable back end drivers for such an array of vendors, it can be done in Picasso too17:43
*** dmorita has quit IRC17:43
robputtinitially yes there may only be 1 backend driver, for IronFunctions17:43
*** dmorita has joined #openstack-meeting17:43
robputtbut it should be a pluggable choice for the deployer to make in my opinion... and then maybe as a contributor I may add drivers for my preferred backend function running thingy...17:43
robputtfor sure atleast I'd like to see Fission and IronFunction backend drivers17:44
denismakogonok, so, the question is still open.17:45
*** spilla has joined #openstack-meeting17:45
dschultzworth exploring this idea more. thanks for the input. i wanted to touch on 1 or 2 blueprint topics before going to open discussion (if time permits)17:45
robputtI think we need a bigger input of opinion to resolve this one...17:45
robputtthe other option17:46
robputtis to make IronFunctions as a thing17:46
robputtOpenStack Functions17:46
rtroxyea, that's what I asked above17:46
robputtthis way, they have a pluggable back end17:46
denismakogonLet's assume that we'll have Picasso as is, we'd need to support oslo libs stack, i'd say that those libs are designed to work through evenlets17:46
*** kristian__ has quit IRC17:46
*** yamahata has joined #openstack-meeting17:47
robputtdenismakogon: I am not 100% sure what you are getting at here17:48
*** toscalix has quit IRC17:48
robputtsome stuff in Oslo is eventlet driven, such as some stuff in Oslo.Db project and Oslo.AsyncIO17:48
*** bobmel_ has joined #openstack-meeting17:48
rtroxme either, when we were talking about oslolibs we were talking about things like oslo.config, oslo.log, oslo.db, etc17:48
*** sudipto has joined #openstack-meeting17:48
*** sudipto_ has joined #openstack-meeting17:48
robputtbut no all of oslo is eventlet based17:49
robputtit depends if eventlet suits that particular libs use case17:49
denismakogonPicasso doesn't use eventlets and it wouldn't use at all17:50
robputtis there something in particular against eventlet?17:50
denismakogonso, i see value in supporting oslo.log and oslo.config only17:50
robputtthere is a call for oslo.db not to use eventlet17:50
denismakogonrobputt: yes, why do we need eventlet if we have native event loop with uvloop policy?17:50
robputtwell, does everything want to wait for the loop?17:51
robputtthats the question, it is really down to usecase17:51
*** reedip_1 has quit IRC17:51
dschultz##info discussing Oslo libs17:51
dschultz#link https://blueprints.launchpad.net/picasso/+spec/oslo-config17:51
dschultz#link https://blueprints.launchpad.net/picasso/+spec/oslo-logging17:51
rtroxand actually eventlet is optional in oslo.db https://github.com/openstack/oslo.db/blob/master/oslo_db/concurrency.py#L60-L6617:51
*** bobmel has quit IRC17:51
*** david-lyle_ has joined #openstack-meeting17:52
denismakogonif oslo.db would support fully async operations through async/await we'll come back to it, before that it's suitable17:52
denismakogonoslo.db does not support asyncio API and it's blocker17:53
robputtI think we are missing the point here17:53
robputtOslo.Db is designed to be deployed accross many diverse environments17:53
robputtwith varying Python versions etc...17:53
rtroxand varying backend drivers17:53
robputtI beleive async and await is only really around since either Python 3.4 or 3.5?17:53
rtroxto various backend DBs17:53
denismakogonPicasso is Python 3.5+17:54
robputtThere are alot of OpenStack deployers out there who deploy old versions of Python, old OpenStack versions17:54
robputtin the operators space I don't know anyone who is firmly using Mitaka yet17:54
*** david-lyle has quit IRC17:54
denismakogonso, before oslo.db will support asyncio API, we'd build an abstraction to support more than one DB if needed17:54
robputtlots are still on Kilo and Liberty and running Python 2.7.2 across their environment17:54
robputtso, I would like to understand here17:55
*** david-lyle_ is now known as david-lyle17:55
*** abalutoiu has joined #openstack-meeting17:55
robputtis the async stuff in > Python 3.5 and absolute requirement for Picasso (and if so why?) or is it just more convenient?17:55
denismakogonPicasso was designed to work over asyncio API to provide pretty fast layer in from of IronFunction to get function execution proxying fast as possible.17:56
*** ayogi has joined #openstack-meeting17:56
*** galstrom_zzz is now known as galstrom17:56
denismakogonrobputt: absolute requirement17:57
denismakogonlet's move this discussion to Slack or IRC, we're running out of time17:58
denismakogondschultz: let's move to next topic17:58
robputtyep lets move on17:58
*** ayogi has quit IRC17:58
dschultzThe last blueprint update I'd like to cover is async  tracking: #link https://blueprints.launchpad.net/picasso/+spec/async-tracking17:59
dschultzwe are tracking that here #link https://github.com/iron-io/functions/issues/41517:59
robputtthis i think is already covered in IronFunctions17:59
*** tonytan4ever has quit IRC17:59
robputtif I send a non blocking execution17:59
robputtit returns some ID which I can poll against for the result of the function17:59
robputtbut that ID does not appear to be proxied back to Picasso17:59
denismakogonrobputt: not really, tracking is available while function runs, its status is not available when async execution is finished18:00
robputtand there is no way to poll a result in Picasso18:00
*** sudipto has quit IRC18:00
*** sudipto_ has quit IRC18:00
*** tonytan4ever has joined #openstack-meeting18:00
*** mdong has joined #openstack-meeting18:00
*** mdong has left #openstack-meeting18:00
denismakogonrobputt: IronFunctions doesn't have an API to track specific execution rather than querying all statuses18:00
robputtso how do you get results from a function run which is non returning?18:00
*** ralonsoh has quit IRC18:01
*** unrahul has joined #openstack-meeting18:01
robputtunless you implement some call back yourself in the function?18:01
denismakogonrobputt: for now, there's no such capability18:01
dschultzsee the PR linked above. IronFunctions team is working on a solution for this.18:01
dschultzsorry guys, running out of time here. we can continue in our channel18:01
*** links has joined #openstack-meeting18:01
denismakogondschultz: right18:01
robputtlets move to openstack-functions18:01
dschultzthank you all for attending! sincerely appreciate your input!18:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:01
openstackMeeting ended Tue Mar  7 18:01:47 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/functions/2017/functions.2017-03-07-17.01.html18:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/functions/2017/functions.2017-03-07-17.01.txt18:01
openstackLog:            http://eavesdrop.openstack.org/meetings/functions/2017/functions.2017-03-07-17.01.log.html18:01
lbragstad#startmeeting keystone18:01
openstackMeeting started Tue Mar  7 18:01:56 2017 UTC and is due to finish in 60 minutes.  The chair is lbragstad. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: keystone)"18:01
openstackThe meeting name has been set to 'keystone'18:02
lbragstadping agrebennikov, amakarov, annakoppad, antwash, ayoung, bknudson, breton, browne, chrisplo, cmurphy, davechen, dolphm, dstanek, edmondsw, edtubill, gagehugo, henrynash, hrybacki, jamielennox, jaugustine, jgrassler, knikolla, lamt, lbragstad, kbaikov, ktychkova, morgan, nishaYadav, nkinder, notmorgan, portdirect raildo, ravelar, rderose, rodrigods, roxanaghe, samueldmq, SamYaple, shaleh, spilla, srwilkers,18:02
lbragstad StefanPaetowJisc, stevemar, topol, shardy, ricolin18:02
lbragstadagenda #link https://etherpad.openstack.org/p/keystone-weekly-meeting18:02
*** mdong has joined #openstack-meeting18:02
lbragstadwe have a lot on the agenda today - so i'll get started wth announcements as folks trickle in18:02
lbragstad#topic Announcement: Pike deadlines18:02
*** openstack changes topic to "Announcement: Pike deadlines (Meeting topic: keystone)"18:02
lbragstad#link https://review.openstack.org/#/c/44199918:03
*** vinaypotluri has joined #openstack-meeting18:03
lbragstadI proposed our deadlines for Pike and I'm going to double check those today18:03
lbragstadand resolve the merge conflict18:03
lbragstadbut I'd expect to have those cleaned up and merged sometime this week18:03
*** david-lyle has quit IRC18:04
lbragstadjust giving everyone a heads up so that they know what we have for a schedule in Pike as far as deadlines go18:04
lbragstad#topic Announcement: New release of keystoneauth today after the following merge18:04
*** openstack changes topic to "Announcement: New release of keystoneauth today after the following merge (Meeting topic: keystone)"18:04
lbragstad#link https://review.openstack.org/#/c/442516/18:04
lbragstad#link https://review.openstack.org/#/c/442536/18:04
lbragstadjust for awareness18:04
lbragstadif there is anything folks want in the next release of ksa - let me know18:04
lbragstadotherwise we'll be cutting the first version for pike sometime today or tomorrow18:05
*** david-lyle has joined #openstack-meeting18:05
lbragstadalright - on to the fun stuff18:05
lbragstad#topic VMT follow up from PTG18:05
*** openstack changes topic to "VMT follow up from PTG (Meeting topic: keystone)"18:05
lbragstadFollowed up with a few folks from OpenStack Security that have some good information we can use to forward with VMT for identity related projects18:05
notmorganthose are test fixture changes btw ^ the ksa bits18:05
lbragstadping michaelxin, knangia, xin9972, unrahul18:05
lbragstadknangia unrahul o/18:05
lbragstad#link https://openstack-security.github.io/collaboration/2016/04/26/threat-analysis-process.html18:06
lbragstad#link https://openstack-security.github.io/collaboration/2016/01/16/threat-analysis.html18:06
unrahulhey lbragstad18:06
knangiahey lbragstad18:06
unrahulso  michealxin won't be available today18:06
lbragstadunrahul knangia thanks for dropping by!18:06
unrahulsure lbragstad , let us know how we may help out18:06
lbragstadunrahul knangia would you mind giving us a brief introduction to what you both do?18:06
unrahulyup so we are both from OSIC security team, mainly working on the openstack security testing project syntribos18:07
unrahulwe are members of the openstack security project18:07
*** denismakogon has quit IRC18:08
*** sambetts is now known as sambetts|afk18:08
lbragstadunrahul it sounds like you are both familiar with the VMT security analysis process as well?18:08
unrahulWe have participated in the initial discussions on security analysis of barbican, it was mostly driven by Rob clark and Doug chivers from the security team18:09
lbragstadawesome - we poked around at that document during the PTG18:09
unrahulAnd if you guys are initiating a security analysis for keystone, I would recommend involving either of them18:09
lbragstadand used it as a reference18:09
*** aasthad has joined #openstack-meeting18:10
lbragstadunrahul do they have irc nicks?18:10
*** baoli has joined #openstack-meeting18:10
knangiaexactly, participated in barbican threat analysis, but mostly i guess, michael xin can guide us18:10
notmorganyes, the goal is to get Keystoneauth, KeystoneMiddleware, and Keystone reviewed18:10
lbragstadyeah - we were planning on starting with keystonemiddleware (at least according to our etherpad) #link https://etherpad.openstack.org/p/pike-ptg-keystone-vmt-coverage18:10
unrahulyes, hyakuhei and capnoday18:10
notmorganthe VMT only covers keystone server at the omment and an updated analysis is definitely in order sinc e keystone has changed a TON since it split from Nova18:11
notmorganas has ksm.18:11
unrahulso keystone middleware is the one that you are going to start with?18:11
lbragstadunrahul i think that was the initial plan18:11
lbragstadright notmorgan?18:12
notmorganwhatever was agreed to is what we are doing. :P18:12
notmorgani am going to say sure ;)18:12
gagehugoyeah the three listed in the etherpad were the first goals I believe from the PTG18:12
* notmorgan can only do so much being split in all the ways I am, so, defering to the notes taken from the meetings18:12
lbragstadi believe that was the action item18:13
lbragstadthe goal was to see if we could get ksm done first18:13
lbragstadand since it is a smaller code base, i think that would be a good start?18:13
notmorgani'm just glad folks are taking interest in this and helping to make those of us working on the VMT lives easier.18:13
unrahulIn any case, we need to have a well defined architectural diagram to identify background information and data flow paths, trust boundaries etc.18:13
lbragstadi was super relieved to hear that unrahul and knangia were working on this, too18:14
lbragstadunrahul so it coming up with that diagram the first step?18:14
unrahulSo we need to have a latest architectural diagram first18:14
unrahulyes lbragstad18:14
lbragstadunrahul cool18:14
knangiayes, the architecture diagram should be the start18:14
lbragstadok - so that'd be something we as the keystone team would be on the hook for18:15
knikollawe might also improve our developer docs in the process of this18:15
lbragstadthen i assume we work on it together?18:15
*** ayogi has joined #openstack-meeting18:15
*** julim has joined #openstack-meeting18:15
lbragstadknikolla ++ i was just thinking about that super old keystonemiddleware arch document we have18:15
unrahulAnd we are not actively working on the threat analysis, but yes have participated in the initial draft of barbican during our mid-cycle. We are willing to help in anyway we can, especially with michaelxin having extensive experience in the field.18:16
lbragstadunrahul ok - do you need the diagram in any particular format?18:16
knangiafor reference ^^18:16
unrahulHere is a sample diagram of barbican https://github.com/openstack/security-analysis/blob/master/doc/source/artifacts/barbican/newton/architecture-page.rst18:17
unrahulit was mostly done on draw.io18:17
notmorganah i was wondering what tool was used18:18
unrahulnotmorgan:  draw.io18:18
* notmorgan has been using ascii-flow, but draw.io is way way cooler18:18
*** rossella_s has quit IRC18:18
knangiacool tool18:18
unrahulA diagram such as this would enable us to identify data assets, its impact and how the system talks with the outside world18:19
unrahulnotmorgan:  ascii-flow is indeed cool :)18:19
knangiayes, so should know the assets, its impacts, trust boundaries with th help of diagram18:20
lbragstadis anyone from the keystone team interested in taking a stab at updating our ksm architecture doc and doing the diagram?18:20
*** vishnoianil has quit IRC18:20
lbragstadfwiw - this would only be fore ksm initially18:20
gagehugoI'd be willing to help18:20
lbragstadgagehugo awesome - anyone else feel like tag-teaming it?18:21
gagehugoI'm not a great artist though :(18:21
lbragstadgagehugo that's what draw.io is for ;)18:21
lbragstadknikolla yeah?18:21
lbragstadknikolla gagehugo i'll put you both down for it then?18:21
gagehugosounds good18:21
knikollasounds good18:21
knangiacool !18:22
lbragstad#action gagehugo and knikolla to start updating keystonemiddleware architecture doc and provide knikolla and unrahul with an updated keystonemiddleware architecture diagram18:22
openstackRemoving item from minutes: #action gagehugo and knikolla to start updating keystonemiddleware architecture doc and provide knikolla and unrahul with an updated keystonemiddleware architecture diagram18:22
lbragstad#action gagehugo and knikolla to start updating keystonemiddleware architecture doc and provide knangia and unrahul with an updated keystonemiddleware architecture diagram18:22
*** david-lyle has quit IRC18:23
lbragstadknangia unrahul i assume once those things are done, we can start the next steps in the process18:23
knikollaknangia: unrahul: which irc channel can we usually find you?18:24
*** adiantum has joined #openstack-meeting18:25
*** david-lyle has joined #openstack-meeting18:25
*** bobmel has joined #openstack-meeting18:25
unrahullbragstad: knikolla  we hang out mostly in #openstack-security18:25
knangia+1 unrahul18:25
unrahulyou guys are welcome to join and ping us or anyone of us there for help18:25
knikollaalright, added.18:25
lbragstadnice - i just joined18:26
lbragstadawesome - well it sounds like we have a path forward18:26
lbragstadgagehugo knikolla thanks for being awesome and helping with this18:26
unrahulAs this process is going on, it is a good idea to initiate discussions with the security team, by pining hyakuhei , who is the security PTL18:26
lbragstadgagehugo knikolla do either of you have specific questions?18:26
knikollaat the moment no18:27
gagehugolbragstad: not yet18:27
*** claudiub has joined #openstack-meeting18:27
gagehugoprobably will later though18:27
lbragstadgagehugo knikolla ack18:27
lbragstadunrahul knangia do either of you have specific questions for us?18:27
knangiahyakuhei can be a great assistance18:27
gagehugoknangia: noted18:28
unrahulnop, nothing as of now, may be talking with someone in barbican can give more advice on how to do the new process as well as they just finished theirs18:28
knangianot for now...probably later18:29
unrahulI think redrobot is the barbican point of contact18:29
lbragstadunrahul that makes sense, i assume we can hash that out in #openstack-security, too?18:29
*** bobmel_ has quit IRC18:29
*** raildo has quit IRC18:29
*** david-lyle has quit IRC18:29
lbragstadI'll put a note on next weeks agenda to keep this in the fore front18:30
lbragstadbut I assume we'll come knocking when we have the diagram and everything ready to go18:30
*** nadya has quit IRC18:30
lbragstadunrahul knangia thanks for the time, answering questions, and being willing to help out18:31
unrahullbragstad: anytime, ping us if you guys need any further help, or anything.18:31
knangiayou're welcome :) glad to help18:31
lbragstadunrahul will do18:31
gagehugowill do!18:31
lbragstadalright - moving on18:32
lbragstad#topic PTG Topics18:32
*** openstack changes topic to "PTG Topics (Meeting topic: keystone)"18:32
lbragstadlast meeting we parsed a bunch of back logged specs and PTG items18:32
lbragstadi've proposed some patches to update the keystone-specs repository accordingly18:33
lbragstadwe only have a couple topics left18:33
lbragstad#topic PTG Topics: Decouple auth from API version18:33
*** openstack changes topic to "PTG Topics: Decouple auth from API version (Meeting topic: keystone)"18:33
lbragstad#link http://specs.openstack.org/openstack/keystone-specs/specs/keystone/backlog/decouple-auth-from-api-version.html18:33
lbragstadnotmorgan i know we had a pretty detailed discussion about this at the PTG18:33
lbragstadnotmorgan but since you have a better idea of how all that works, do you think the backlogged spec needs to be updated?18:34
lbragstadgiven the current state of keystone?18:34
dstaneki remember talking about this, but i don't remember if we were going to get it done this cycle18:34
*** edmondsw has joined #openstack-meeting18:34
notmorganbasically what needs to happen is we need to implement the new auth route for keysotne at  /auth18:35
lbragstaddstanek i'm not sure either - but I for sure want to capture notmorgan's PoV on it18:35
notmorganwhich takes an auth "version" or whatever we want to call it as part of the body/header/something18:35
notmorganthen we need to wire up /v3/auth and /v2.0/auth into the mechanism18:35
lbragstadthe reasons for doing it seemed to make sense at the PTG and I think we should add them to the spec if we can, that way we don't lose the information18:35
*** raildo has joined #openstack-meeting18:35
notmorganso when those routes are hit, it converts to the expected form and passes across internally18:36
*** david-lyle has joined #openstack-meeting18:36
notmorganonce that is done, we need to ensure ksa can talk to the new auth endpoint and know it's the new auth endpoint18:36
notmorganso GET /auth would need to produce something interesting18:36
notmorganit's not crazy nor super complex18:36
edmondswwhat are the reasons?18:37
notmorganit's just giving us flexability in auth without mucking with the crud interfaces18:37
notmorganbecause iterating on /v3/auth is going to _require_ microversions and microversions for auth on the v3 interface is a terrible idea18:37
notmorganit also allows us to maintain auth data if it doesn't need to change if we want to say do v4 api instead of microversions18:37
lbragstadbecause.... ?18:37
edmondswthis would require microversions as well, per the api guidelines18:37
notmorganedmondsw: no.18:38
knikollathe new guidelines are pretty strict18:38
edmondswnotmorgan go read https://review.openstack.org/#/c/42184618:38
notmorganthe guidelines are terrible if we have to put microversions on an endpoint like auth18:38
*** jtomasek has quit IRC18:39
knikollathey basically want to microversion any change, for interop reasons18:39
notmorganmicroversions for CRUD interfaces is lazy and terrible.18:39
notmorganbut is fine because we already lost that argument18:39
*** salv-orlando has quit IRC18:39
*** ijw has quit IRC18:39
*** kjw3 has quit IRC18:40
notmorganknikolla: then i think i need to just stop talking.18:40
notmorganscuttle the spec. just microversion things18:40
*** vinaypotluri has left #openstack-meeting18:41
lbragstadi thought there was discussion at the  PTG that made microversions questionable18:41
lbragstadi mean - we already removed the microversion spec from our backlog18:41
edmondswlbragstad within the keystone room... but outside of keystone microversions are winning the day18:41
*** abalutoiu has quit IRC18:41
notmorganif we don't do microversions in keystone, moving auth is super important18:41
*** eharney has quit IRC18:41
notmorganbecause the headache of v2->v3 was auth18:42
notmorgannot the crud interface18:42
notmorganthe fact we tied auth to the api crud api was a big mistake in v2.018:42
notmorganand carried into v318:42
notmorgan(predates everyone here except maybe dolphm)18:42
notmorganif we do microversions in keystone and auth endpoint would need it too, i wont fight too hard for this18:43
*** nadya has joined #openstack-meeting18:43
notmorgani'll just let the folks doing microversions handle these cases. since it'll cover it18:43
* notmorgan still thinks microversions are simply a terrible idea18:43
notmorganit comes down to keystone direction18:43
lbragstadnotmorgan would you be interested in documenting the reasons for decoupling auth from versions in the spec?18:44
*** salv-orlando has joined #openstack-meeting18:44
lbragstadnotmorgan even if it's just a simple list?18:44
edmondswright... I don't disagree about microversions being awful. If keystone wants to hold out on not doing them, I'm fine with that. But we won't get that silly tag18:44
notmorganedmondsw: i'd rather keystone didn't have that tag18:45
dstanekedmondsw: ++ for aiming for *not* having the tag18:45
*** eharney has joined #openstack-meeting18:45
knikollawe're special18:45
notmorganlbragstad: the reasons are in the problem statement18:45
lbragstadwe're just a bunch of rebels18:45
*** nadya has quit IRC18:45
lbragstadnotmorgan ok - so the spec is accurate, even with all the changes in keystone since it was proposed?18:46
lbragstads/proposed/merged to backlog/18:46
notmorganbecause auth hasn't really changed18:46
lbragstadok - cool18:46
notmorganthe only things we might modify is make /catalog a top level bit as well18:46
notmorganor similar18:46
lbragstadsounds like we can just leave it as is then for now18:46
lbragstad#topic PTG Topics: Materialized Path for HMT18:47
*** openstack changes topic to "PTG Topics: Materialized Path for HMT (Meeting topic: keystone)"18:47
notmorganbut like i said, if we're doing microversions, i just wont push hard for this and would just say might as well scuttle the spec18:47
lbragstadnotmorgan sounds like we haven't gotten a definitive answer on that yet - but when we do i'll be sure to update accordingly18:47
lbragstad#link http://specs.openstack.org/openstack/keystone-specs/specs/keystone/backlog/materialize-project-hierarchy.html18:47
lbragstadthis has been in backlog for a long time18:47
notmorgani think we killed this a while ago18:48
notmorganlike all the code for it18:48
lbragstadyeah - i remember seeing an implementation for it somewhere,18:48
notmorganit was -2'd and abandoned because of some reason? also no one is championing it anymore18:49
lbragstadit was in review for a long time/18:49
notmorganit's not a bad idea.18:49
lbragstadno - it does sound useful18:49
dstaneki think we may need to revisit the problem again because of limits18:49
notmorgani don't remember why it was killed18:49
dstaneknot sure about the implementation though18:49
knikolladstanek: let's derive a new problem statement once we figure out limits18:49
dstanekknikolla: there is no different in the fundamental issue18:50
*** s3wong has joined #openstack-meeting18:51
lbragstadfrom a performance perspective, we'll need this at some point if we do HMT I assume18:51
dstanekwe simply need a more efficient way to grab hierachy info... the limits work will just dictate what we do with it18:51
knikolladstanek: understood18:51
dstanekthis probably isn't needed this cycle though18:51
lbragstadso it sounds like we need to follow up on this once we come to a more definitive conclusion of limits18:51
dstaneki'd even go further to say we can follow up after we have a working poc for limits18:52
dstanekthen this would be an optimization18:52
knikolladstanek: ++18:52
lbragstad#action keystone group to follow up on materialized path for HMT once we come to a conclusion on limits18:53
lbragstadworks for me18:53
*** kjw3 has joined #openstack-meeting18:53
lbragstadi don't expect that to happen before Queens18:53
lbragstadmoving on18:53
lbragstad#topic PTG Topics: Default Policy File18:53
*** openstack changes topic to "PTG Topics: Default Policy File (Meeting topic: keystone)"18:53
lbragstad#link http://specs.openstack.org/openstack/keystone-specs/specs/keystone/backlog/policy-default.html18:53
lbragstadwith all the work antwash and ravelar have been doing, I don't think this is need anymore18:54
knikollathis is obsolete by policy in code right?18:54
lbragstadyeah - i think so18:54
ayoungThis grew out of the diesre to merge the curent ahd cloud sample approachs IIRC18:54
ayoungAh...no...that one can die18:55
lbragstad#action lbragstad to remove policy default spec18:55
ayoungI didn;t realize it was still around.  That was a vestige of the Dynamic policy effort18:55
lbragstadnice - that was easy18:55
lbragstadthanks for confirming18:55
lbragstadmoving on18:55
lbragstad#topic Reviews18:55
*** openstack changes topic to "Reviews (Meeting topic: keystone)"18:55
ayoungpretty sure I wrote it18:55
lbragstadso we have some reviews to get around to - posted them here so that folks are aware18:56
lbragstadpassword hashing in keystone: #link https://review.openstack.org/#/c/438808/ (bug: #link https://bugs.launchpad.net/keystone/+bug/1668503 )18:56
openstackLaunchpad bug 1668503 in OpenStack Identity (keystone) pike "sha512_crypt is insufficient, use pbkdf2_sha512 for password hashing" [High,In progress] - Assigned to Morgan Fainberg (mdrnstm)18:56
lbragstadWill need to be backported to all supported releases18:56
notmorgannot being backported18:56
notmorgantoo difficult to do w/o disruption18:56
lbragstadnotmorgan isn't that what your note said?18:56
lbragstadnotmorgan aha - maybe i misunderstood then18:56
notmorganthat is a master and forward change now18:56
notmorganthe note was originally that18:56
notmorganit has changed post discussion in -keystone18:56
lbragstadok - cool18:57
lbragstadeither way, we'll need to get some eyes on it18:57
notmorganbecause it requires new config options etc18:57
notmorganreally is not backportable.18:57
ayoungmake sure it does not break LDAP18:57
notmorganthe ci failure it was seeing was unrelated18:57
notmorganayoung: only affects password storage18:57
notmorgansince ldap is non-write18:57
ayounggot it18:57
*** pvaneck has joined #openstack-meeting18:57
notmorgandoesn't matter18:57
*** baoli has quit IRC18:58
lbragstadcouple more18:58
lbragstadpolicy in code: #link https://review.openstack.org/#/q/topic:bp/policy-in-code+status:open+project:openstack/keystone18:58
lbragstadoslo.policy descriptions: #link https://review.openstack.org/#/c/439070/18:58
notmorganthe ci failure was testr binary/script in a non-expected location ftr18:58
notmorganso, please review.18:58
lbragstadand finally - spec reviews18:58
lbragstadwe have a bunch of things proposed to specs, but it looks like most either need to be abandon or updated to reflect discussions had at the PTG18:58
lbragstadspec proposal freeze will be in about 6 - 7 weeks18:59
*** adisky_ has quit IRC18:59
lbragstadbut that's all I have18:59
lbragstadthanks for coming everyone!18:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:59
openstackMeeting ended Tue Mar  7 18:59:49 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-03-07-18.01.html18:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-03-07-18.01.txt18:59
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-03-07-18.01.log.html18:59
*** asselin has joined #openstack-meeting18:59
*** gagehugo has left #openstack-meeting19:00
*** mdong has left #openstack-meeting19:00
pabelangerhello infra people19:00
*** edmondsw has left #openstack-meeting19:00
pabelangerfungi is absent today, and I've offered up to chair the meeting.19:00
*** spilla has left #openstack-meeting19:00
*** Shrews has joined #openstack-meeting19:00
pabelangerOur schedule is pretty light today19:00
jeblairpabelanger: hello19:00
*** electrofelix has quit IRC19:01
pabelangerwe currently only a a single topic, so lets get to it19:01
pabelanger#startmeeting infra19:01
openstackMeeting started Tue Mar  7 19:01:42 2017 UTC and is due to finish in 60 minutes.  The chair is pabelanger. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
pabelanger#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:01
pabelanger#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
pabelangerI believe clarkb was successful in upgrading translate.o.o to xenial.19:02
* mordred waves19:02
*** sdague has quit IRC19:02
pabelangerI don't think we had any outages either, so good work19:02
pabelangerthat was the only thing I had, moving on19:03
pabelanger#topic Actions from last meeting19:03
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:03
pabelanger#link http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-02-28-19.03.html Minutes from last meeting19:03
pabelangerianw launch a "beta" nodepool builder on xenial19:03
*** jamesdenton has quit IRC19:03
ianwso i tried brining up a host on vexxhost as well19:03
ianwjust for something different19:04
ianwhit some shade issues in the launch script https://review.openstack.org/44091419:04
*** david-lyle has quit IRC19:04
pabelanger#link https://review.openstack.org/#/c/440914/19:04
ianwi also did a little hacking on the launch script19:04
ianw#link https://review.openstack.org/44092819:04
ianwwhich might be helpful19:04
ianwbut, there is no builder yet :)  will keep at it as time permits however19:05
*** david-lyle has joined #openstack-meeting19:06
*** jamesdenton has joined #openstack-meeting19:06
pabelangerianw: did you want me to recycle the action from this week for the next meeting?19:06
ianwpabelanger: i think just leave it with me, as it's not super high priority19:06
pabelangerianw: great19:07
pabelangerif nothing else, we can move onto the next topic19:07
pabelanger#topic Specs approval19:07
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:07
pabelanger#link https://review.openstack.org/434951 Stackalytics Persistent Cache19:07
pabelangerStill looking for some reviews on our stackalytics spec for mrmartin.19:08
pabelangerAlso, does anybody know if we reached out to the stackalytics-core team for feedback?19:08
pabelangermrmartin: do you mind doing that?19:08
*** baoli has joined #openstack-meeting19:09
mrmartinnot yet, but I'll ping them19:09
pabelangergreat, I think fungi just wanted to give them a heads up, see what they thought19:09
pabelanger#topic Priority Efforts19:10
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:10
pabelangerI didn't have anything specific here. Not sure if jeblair wanted to add anything on the topic of zuulv3?19:11
*** dmorita has quit IRC19:12
jeblairpabelanger: i wanted to discuss your tox changes, but you're the chair so i'll let you decide when to do that :)19:12
pabelangerjeblair: sure, that's our next topic. So we can move into that.19:12
pabelanger#topic Zuulv3 sample jobs (jeblair)19:12
*** openstack changes topic to "Zuulv3 sample jobs (jeblair) (Meeting topic: infra)"19:12
pabelangerjeblair: after you sir19:13
*** matrohon has joined #openstack-meeting19:13
jeblairpabelanger wrote some some basic jobs for zuulv319:13
jeblairhttps://review.openstack.org/#/c/438281/ and https://review.openstack.org/#/c/442180/19:13
jeblair#link https://review.openstack.org/#/c/438281/19:13
jeblair#link https://review.openstack.org/#/c/442180/19:13
*** Rocky_g has quit IRC19:14
jeblairthose are competing approaches to defining some basic tox jobs19:14
*** Rocky_g has joined #openstack-meeting19:14
jeblairi'd like folks who have an interest to take a look at both of them and weigh in on it19:14
pabelangeryes, reviews welcome please.19:14
jeblairparticularly, whether one or the other is easier to follow or might be more mantainable if we use it as the base of our most common jobs in project-config19:14
ShrewsIs there a tl;dr summarizing the different approaches?19:16
ShrewsMaybe describe them in the commits?19:16
jeblairthat would probably be helpful :)19:16
pabelangeryes, I can update them after meeting to describe the differences19:16
pabelangerfor the most part, the differences are in the .zuul.yaml file19:17
jeblair(but to summarize here, i'd say the main question is how far we should parameterize our playbooks19:17
jeblairroles, obviously yes, but playbooks?  i think it's a legitimate question as to which is more easily understandable to casual users)19:18
ianwhttps://review.openstack.org/#/c/438281/24/.zuul.yaml so the run_tox_env arg has disappared?19:19
*** markstur has joined #openstack-meeting19:19
ianwdisappeared even19:19
*** dmorita has joined #openstack-meeting19:19
jeblairianw: yes, and been replaced by more playbooks19:19
pabelangerianw: right, it is not needed because we provide 3 different playbooks, which setup there own specific job vars19:19
ianwahh yes ok19:20
*** dandruta has quit IRC19:20
mordredfwiw, 438281 reads nicer to me - but both are readable and understandable19:20
pabelangerso far, I like 438281 more, only because you don't need to mental map things from .zuul.yaml, at the cost of more playbooks in tree19:21
pabelangerbut interest in others feedback19:21
*** kjw3 has quit IRC19:22
*** salv-orl_ has joined #openstack-meeting19:22
jeblairpabelanger: maybe a ml post would be good too to collect more feedback.19:23
*** ayogi has quit IRC19:23
pabelangersure, I can propose something on etherpad first, then send it along19:23
mordredpabelanger: also, it may feel better once the run-tox role fully replaces the run-tox.sh jenkins script and isn't just a passthrough19:23
jeblairgood point19:24
pabelangermordred: agree, for now I've been doing easy mode for our JJB to ansible conversion.19:24
mordredpabelanger: TOTALLY - and I think the exact right call19:24
mordredmostly just pointing out that some of the parameterization might feel artificial to folks when the role is just a shell call to a script19:24
*** GK___1wm____SU has joined #openstack-meeting19:25
mordredso to sort of imagine that run-tox actually has the run-tox.sh logic in it when looking at these19:25
*** salv-orlando has quit IRC19:25
pabelanger#action pabelanger to send ML post to get more feedback on our current run-tox playbooks / role19:26
*** GK___1wm____SU has quit IRC19:27
pabelangerThis was our only topic for todays meeting, so if nothing else, we can move to open discussions19:28
pabelanger#topic Open discussion19:28
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:28
*** vishnoianil has joined #openstack-meeting19:29
pabelangerSeen a tweet about ubuntu 12.04 EOL next month (Apr-2017), since we still have a few servers running 12.04 we should think about a virtual sprint to fix that19:30
mordredpabelanger: speaking of ...19:30
mordredwe have a server still running 10.0419:30
mordredmaybe it's time to turn off old-wiki?19:30
mordredor maybe we should keep it to see how long it'll run ...19:31
pabelanger10.04 really?19:31
mordred(for those who don't know, old-wiki is the very first vm that was ever spun up for openstack)19:31
mordredpabelanger: 10.04 was very modern when that vm was created19:31
mordredalso - please don't let anyone tell you that cloud vms are not stable19:31
mordredsince that vm was created, I believe I've had 6 different laptops :)19:32
bkeroSnarf it down through wget --recursive, host that content somewhere static?19:32
pabelangerindeed, I didn't know old-wiki.o.o was a thing19:32
mordredoh - the content is not useful - it's all been migrated elsewhere to my knowledge19:33
pabelangerI was planning on talking with clarkb once he is back online, maybe for next meeting has a few options for a virtual sprint to do upgrades. I don't think we have many servers that are 12.04 right now19:33
mordredbkero: although I suppose we could also snapshot the machine image, then download it :)19:33
ianwwe could just check it's in archive.org (for posterity) and zap it?19:33
mordredpabelanger: ++19:34
bkeromordred: I have nothing I want on there, although if fears still exist about losing data, ianw or my option should alleviate those.19:34
pabelangersounds like we might be able to end early today19:35
mordredoh wow - this is in my homedir: nova_0.9.0-0ubuntu0ppa1~lucid1bzr200.debian.tar.gz19:36
pabelangerianw: what is needed for that?19:36
Rocky_gCapture it in the wayback machine, then kill it19:37
ianwrobots.txt seems like it allows it19:37
pabelangerlets check with fungi when he is back online. But, I tend to agree with mordred, all the data has already been migrated. But, it would be good to understand, why it was still running19:39
pabelangerand with that, I'm going to end our meeting.19:39
mordredalso - jbryce still has a shell account on the machine :)19:39
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:40
openstackMeeting ended Tue Mar  7 19:40:10 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-03-07-19.01.html19:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-03-07-19.01.txt19:40
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-03-07-19.01.log.html19:40
*** Shrews has left #openstack-meeting19:40
*** nadya has joined #openstack-meeting19:40
*** kjw3 has joined #openstack-meeting19:41
*** bobmel has quit IRC19:45
*** tobberydberg has joined #openstack-meeting19:45
*** dmorita has quit IRC19:51
*** dmorita has joined #openstack-meeting19:51
*** e0ne has joined #openstack-meeting19:57
jrollwow, the infra meeting is super short when fungi isn't running it :P19:59
*** dmorita has quit IRC19:59
*** dmorita has joined #openstack-meeting19:59
lbragstadjroll :)20:01
*** gouthamr has quit IRC20:01
jrollalso I just realized no TC meeting this week20:01
jrollhave fun in boston, whoever is there20:02
lbragstadaha - i forgot about that, too20:02
Rocky_gme three20:03
*** cdent has joined #openstack-meeting20:03
*** salv-orl_ has quit IRC20:03
*** gordc has joined #openstack-meeting20:06
*** links has quit IRC20:09
*** ayoung has quit IRC20:16
*** askb has joined #openstack-meeting20:22
*** priteau has quit IRC20:23
*** nadya has quit IRC20:24
*** priteau has joined #openstack-meeting20:24
*** priteau has quit IRC20:29
*** gouthamr has joined #openstack-meeting20:29
*** armstrong has joined #openstack-meeting20:33
*** JoseMello has quit IRC20:35
*** kjw3 has quit IRC20:37
*** pnavarro has joined #openstack-meeting20:38
*** oneswig has joined #openstack-meeting20:38
*** priteau has joined #openstack-meeting20:39
*** rhe00 has quit IRC20:41
*** raildo has quit IRC20:45
*** bobmel has joined #openstack-meeting20:46
*** awaugama has quit IRC20:47
*** flanders_ has joined #openstack-meeting20:49
*** claudiub|2 has joined #openstack-meeting20:50
*** bobmel has quit IRC20:51
*** tobberydberg has quit IRC20:52
*** stream10 has joined #openstack-meeting20:53
flanders_Morning/afternoon/evening to one and all, esp this hear for scientific-wg  😃20:53
*** claudiub has quit IRC20:53
*** julim has quit IRC20:55
* flanders_ pours another cup of coffee in hopes of typing better...20:56
armstrongis my typing too bad?20:56
flanders_Apologies no armstrong20:57
armstrongok hahaha20:57
*** baoli has quit IRC20:57
flanders_Was referring to my previous message20:57
flanders_Early in the morning here in Australia, so I'm still waking up :)20:58
*** baoli has joined #openstack-meeting20:58
armstrongOh I see20:58
*** jaugustine has joined #openstack-meeting20:58
oneswig... wait for it ...20:59
*** cdent has left #openstack-meeting20:59
armstrongyou are far away ... hopefully I will be in Australia on the 18th20:59
flanders_Come say hi armstrong I'm in Melbourne :)21:00
*** gordc has left #openstack-meeting21:00
oneswig#startmeeting scientific-wg21:00
openstackMeeting started Tue Mar  7 21:00:13 2017 UTC and is due to finish in 60 minutes.  The chair is oneswig. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: scientific-wg)"21:00
openstackThe meeting name has been set to 'scientific_wg'21:00
armstrongok cool21:00
*** ykatabam has quit IRC21:00
oneswigGreetings all21:00
*** electrocucaracha has left #openstack-meeting21:00
oneswig#link Agenda for today https://wiki.openstack.org/wiki/Scientific_working_group#IRC_Meeting_March_7th_201721:00
oneswigBut really it's mainly about the Forum this session21:01
oneswigHi hogepodge, flanders_, armstrong and all21:01
*** tobberydberg has joined #openstack-meeting21:01
oneswigmartial will be a few minutes late (other meetings to attend to)21:02
oneswigHi priteau21:02
*** jmlowe has joined #openstack-meeting21:02
armstrongHello oneswig21:02
oneswigLast week, the EMEA cohort got started on an etherpad...21:02
hogepodgeI had one item to add to the agenda if we can squeeze it in.21:02
*** sdague has joined #openstack-meeting21:03
*** ravelar has left #openstack-meeting21:03
*** powerd has joined #openstack-meeting21:03
oneswighogepodge: sure, up front or any other business?21:03
*** trandles has joined #openstack-meeting21:03
oneswig#link Forum ideas brainstorming https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg21:03
hogepodgeit was reprinting the openstack in science books. someone from the wg had asked for them to be reprinted for docker con, but given the expense we were hoping to defer that to sc 17 with a possible content refresh21:04
oneswighogepodge: I think a refresh is hoped for anyway, we started gathering data for a chapter on federation but hit a stumbling block (seems like there may be backwards compatibility issues wrt Ocata and domains - jmlowe did you find out more?)21:05
jmloweI did not21:06
hogepodgesorry to bring this up out of turn on the agenda :-/21:06
oneswigAlas, me neither21:06
oneswighogepodge: I wouldn't call most of our meetings strictly linear :-)21:06
*** martial has joined #openstack-meeting21:06
martial(sorry, another meeting that would not end)21:07
*** lpetrut has joined #openstack-meeting21:07
oneswighogepodge: what date were you thinking of as a publish deadline?21:07
oneswigHi martial21:07
oneswig#chair martial21:07
openstackCurrent chairs: martial oneswig21:07
oneswigmartial: people are perusing https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg and we are discussing a second print run on the book21:08
*** dimtruck is now known as zz_dimtruck21:08
*** armax has quit IRC21:09
hogepodgewe don't have a firm deadline, we would have to order books now for dockercon, and printing up old books means less budget for printing revised books21:09
martialhogepodge: yes, I was the one who was wondering about the book for DockerCon21:09
oneswighogepodge: sounds like they are 6 months apart.21:09
martialHow many people stopped by the booth last year?21:10
armstrongAt Barcelona ?21:10
jmlowehey, here we go, re: federation https://bugs.launchpad.net/keystone/+bug/164268721:10
openstackLaunchpad bug 1642687 in OpenStack Identity (keystone) "Missing domain for federated users" [Medium,Fix released] - Assigned to Ron De Rose (ronald-de-rose)21:10
martialarmstrong: sorry DockerCon 1621:10
martialstig, we might want to also invite a couple people from the cyborg project to see us and discuss how they can help21:11
jmloweusers no longer go in a FEDERATED domain but now have a per IdP domain21:12
martialzhipheng is already getting in touch with blair on that21:12
*** julim has joined #openstack-meeting21:12
*** aysyd has quit IRC21:12
oneswigmartial: you mean Cyborg team at a WG IRC meeting?21:13
*** eharney has quit IRC21:13
martialoneswig: I am going to see if I can come up with a small presentation on our Data Science model with benchmarking aggregation21:13
hogepodgemartial: if we want to print them up, can you circle up with me offline for number, and also justification I can take back to the marketing team?21:13
*** b1airo has joined #openstack-meeting21:13
oneswigjmlowe: what are the consequences -does this prevent federated users from being co-tenants on a common project?21:13
*** matrohon has quit IRC21:14
b1airoMorning and apologies - wheels have come off at home this morning21:14
oneswigb1airo: good morning21:14
oneswig#chair b1airo21:14
openstackCurrent chairs: b1airo martial oneswig21:14
martialhogepodge: I can get in touch with you, yes. I will be at DockerCon too21:14
martialb1airo: welcome / hopefully nothing too bad21:14
jmloweafaik you just need to layout your mapping a little differently21:15
oneswigjmlowe: is this a major issue?  Something worth articulating ... in a Forum etherpad for example?21:16
*** fguillot has quit IRC21:16
martialoneswig: no, I meant for the cyborg team to stop by for a quick BoF maybe and introduce their work to us; they are looking for input/user stories on how they can help21:16
oneswigjmlowe: isn't federated user mapping something to keep as simple as possible, does it cause issues here?21:16
jmloweI think it still needs a bit more research, docs still stay you have to map to groups but I was under the impression having spoken with the keystone devs that was actually a bug fixed in Newton21:16
*** DFFlanders has joined #openstack-meeting21:17
*** rfolco has quit IRC21:17
oneswigjmlowe: but it's keeping you from federating - was it digital globe?21:17
martialoneswig: zhipeng contacted me and I tried to put him in touch with b1airo, as our GPU / GPGPU expert21:17
oneswigmartial: do you have a feel for how Cyborg differs from what's being talked about with the Nova placement scheduler?  I'd be interested to see that clarified21:18
b1airomartial: yes I got the email, haven't looked yet though21:19
martialoneswig: not the best understanding, no, I agree; which is why I wanted to start this conversation with them21:19
martialDFFlanders: welcome21:19
*** e0ne has quit IRC21:20
*** Lizhong has joined #openstack-meeting21:20
oneswigmartial: think you can clarify this with Jim G?  He's on the project isn't he?21:20
jmloweI'm getting my group problem fixed, read only ldap groups that were not fully populated, I need to have a fairly sophisticated mapping as all of the usage accounting depends on tenant per activity with users having roles on multiple tenants21:20
*** ijw has joined #openstack-meeting21:20
martialoneswig: I will talk to Jim21:20
flanders_@martial: o/21:20
jmloweI share a lot of my ldap backend with Chameleon21:21
oneswigIU has fingers in many pies - is it a Chameleon site?21:21
jmloweIt's Kate Keahey's cloud research project at UT Austin and U Chicago21:22
*** kjw3 has joined #openstack-meeting21:22
martialoneswig: Jim said he will find out :)21:22
jmloweI believe priteau is part of that project21:23
priteaujmlowe: Jetstream uses TACC's LDAP?21:23
martialjmlowe: I beieve you are correct re priteau21:24
priteauyes I am21:24
jmloweyes, it's insane21:25
jmloweI create all kinds of problems for Akhil21:26
priteaujmlowe: we have moved away from an LDAP-backed Keystone. We now have a sync script to Keystone's MySQL DB21:26
priteauat least in our bare-metal clouds. KVM is still using LDAP directly21:26
jmlowepriteau: just identity, assignment is in sql21:26
priteauWe use SQL for both21:28
priteauI can get you in touch with our admin if you want to perform the same kind of migration21:29
*** eharney has joined #openstack-meeting21:29
jmloweMy federation goal is to do openid connect federation via globus auth and get xsede portal users mapped correctly to the tenants that their corresponding TACC users have roles on, if I can make it work I'd be happy to write it up for v2 of the book21:29
martialjmlowe: sounds great :)21:30
oneswigjmlowe: that is EXACTLY the kind of case study that would really add value21:30
*** pchavva has quit IRC21:32
*** ayoung has joined #openstack-meeting21:32
martialwhat is the next item on the agenda?21:33
*** zz_dimtruck is now known as dimtruck21:33
oneswigsome folks are working through the etherpad -21:34
*** ayoung has quit IRC21:34
b1airoHasn't been much Forum ML chatter that I've noticed yet...21:34
oneswigFrom what I've seen it's us and the Telco WG, plus Nova, Neutron who have made etherpads for brainstorming21:36
*** gouthamr has quit IRC21:37
*** ayoung has joined #openstack-meeting21:37
*** jrobinson has joined #openstack-meeting21:38
*** salv-orlando has joined #openstack-meeting21:38
oneswigAre there any thoughts on items that are missing from the Etherpad?21:38
*** rfolco has joined #openstack-meeting21:39
*** rfolco has quit IRC21:39
DFFlandersmore to come, lots of discussions ongoing re forum as a new event.  iterations will be needed.21:39
martialDFFlanders: yes it seems very different I must say21:39
oneswigDFFlanders: any issues that could be laid out here that would be relevant to the Boston Cloud Declaration?21:40
*** stream10 has quit IRC21:41
trandlesI'm interested in knowing if discussions of federation & Boston Cloud Declaration are taking into consideration FedRAMP.  https://www.fedramp.gov/  It's a US gov't thing but for labs like LANL and (I presume) organizations like NIST it's an important consideration.21:44
* trandles pokes martial 21:44
martialtrandles: am here, but unfortunately not something I can comment on21:44
*** tobberydberg has quit IRC21:45
*** kjw3 has quit IRC21:46
oneswigCame up on the mailing list yesterday - http://lists.openstack.org/pipermail/openstack-operators/2017-March/012859.html21:46
oneswigmentioned in passing21:46
trandlesgah, I missed that...thx for the link21:47
*** asselin has quit IRC21:47
martialtrandles: I will obviously see what we can do here, but it is not something I am involved with21:47
*** gyee has joined #openstack-meeting21:47
martialI will see who here is involved and see if they can join the converstaion21:48
trandlesmartial: It's fairly new to me too.  Someone sprung it on me in a meeting yesterday.21:48
flanders_oneswig: if we can all stay meta and observe how this forum goes (and resulting PTG), then I think we will iterate in feedback for Sydney.21:49
martialtrandles: I am aware of it, we have to use cloud systems (not on premise) that are fedramp certified, so it is on our mind, trust me :)21:49
martialthat said, it is not decided here either21:49
martialbut I will see who at NIST is the right person to get this conversation started21:50
*** abalutoiu has joined #openstack-meeting21:51
oneswigflanders_: ok thanks, makes sense to find a working modus operandi before driving it too hard21:51
flanders_trandles: ping the chairs of the Boston Declaration: Khalil and Wilfred.  It is a higher level policy thing trying to get the funding agencies to agree some priority areas of which federation will be one.  I doubt they will talk technical implementation.21:51
trandlesflanders_: thx, will do21:52
martialflanders_: agreed21:53
martialtrandles: cc me if you can, I just started reaching out here on this matter21:53
oneswigI think the etherpad has arrived at a steady state... any more contributions?21:54
flanders_oneswig: +1 let's use Boston to experiment and iterate the forum from there.21:54
*** dprince has quit IRC21:54
oneswigflanders_: point of order here, what happens next?  Is it that we fold the brainstorming sessions together and find common cause?21:55
*** cleong has quit IRC21:55
*** youzp has joined #openstack-meeting21:55
b1airoStill need to figure out if it is feasible to present at GTC in the middle of the Forum...21:56
b1airoWrong coast21:56
oneswigThey'll do a live video linkup for you, right? :-)21:57
flanders_oneswig: the UC will make announcements on the ML21:57
*** rbowen has quit IRC21:57
oneswigah ok, will keep an eye out for that21:57
flanders_In short, I'm not sure and will bring this up to UC chairs21:57
martialflanders_: ok, thanks21:57
flanders_Keep the questions coming!21:58
oneswigTime's running low however21:58
armstrongwhen is launchpad switching to storyboard?21:58
flanders_I'd like the scientific-wg to be the first to know it's features are being delivered (via the PTG) for its users.21:58
b1airoThat would be nice!21:59
*** gouthamr has joined #openstack-meeting21:59
oneswigA highly satisfying result indeed21:59
flanders_Once list of forum activities are set let's think about which PTLs to invite to our sessions <-- future agenda item plz21:59
b1airoIn other news we finished our DC move!21:59
*** donghao has joined #openstack-meeting21:59
martialb1airo: congratulations :)22:00
oneswigarmstrong: not sure - saw something about it happening but no dates nor further details...22:00
armstrongoneswig ok thanks22:00
*** youzp has quit IRC22:00
oneswigb1airo: good job.  Can't wait to hear how you're going to top that one22:00
flanders_b1airo: bonza! ;)22:00
flanders_Are you available for squash now b1airo ?22:01
oneswigPerhaps b1airo you can help Melbourne Uni with their move now?22:01
*** Rocky_g has quit IRC22:01
b1airoUsually the way it goes oneswig22:01
flanders_+1 tru dat22:01
oneswigOK we are out of time.  Thanks all, it's a wrap22:01
*** jmlowe has left #openstack-meeting22:01
oneswig #endmeeting22:01
flanders_L8er :)22:01
priteauBye everyone22:02
oneswigoh.  The meeting hasn't ended.  Does that mean we can't leave?22:02
martialthanks all, see you soon :)22:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:02
openstackMeeting ended Tue Mar  7 22:02:37 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:02
priteauhave we lost the bot?22:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scientific_wg/2017/scientific_wg.2017-03-07-21.00.html22:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scientific_wg/2017/scientific_wg.2017-03-07-21.00.txt22:02
openstackLog:            http://eavesdrop.openstack.org/meetings/scientific_wg/2017/scientific_wg.2017-03-07-21.00.log.html22:02
martialextra space :)22:02
*** oneswig has quit IRC22:03
b1airoSo slow this AI stuff22:04
*** donghao has quit IRC22:04
martialb1airo: using DIGIT on your GPU cluster?22:04
b1airoHas been played with yeah22:05
martialnvidia just released their v5 I believe22:05
*** martial has quit IRC22:07
b1airoYeah we need to do a driver upgrade and now we need different versions for Kepler versus GRID22:07
*** tonytan4ever has quit IRC22:07
*** baoli has quit IRC22:08
*** armstrong has quit IRC22:10
*** trandles has quit IRC22:11
*** pnavarro has quit IRC22:11
*** armax has joined #openstack-meeting22:12
*** thorst has quit IRC22:12
*** ihrachys has quit IRC22:14
*** baoli has joined #openstack-meeting22:21
*** rossella_s has joined #openstack-meeting22:21
*** jmckind has quit IRC22:22
*** ykatabam has joined #openstack-meeting22:23
*** nadya has joined #openstack-meeting22:24
*** lpetrut has quit IRC22:26
*** nadya has quit IRC22:29
*** tdasilva has quit IRC22:32
*** baoli has quit IRC22:38
*** ihrachys has joined #openstack-meeting22:40
*** ihrachys has quit IRC22:41
*** julim has quit IRC22:41
*** tdasilva has joined #openstack-meeting22:44
*** bobmel has joined #openstack-meeting22:47
*** esberglu has quit IRC22:49
*** esberglu has joined #openstack-meeting22:49
*** priteau has quit IRC22:51
*** bobmel has quit IRC22:51
*** emagana has quit IRC22:52
*** esberglu_ has joined #openstack-meeting22:53
*** designbybeck has quit IRC22:53
*** rossella_s has quit IRC22:53
*** esberglu has quit IRC22:54
*** tdasilva has quit IRC22:54
*** sdague has quit IRC22:57
*** esberglu_ has quit IRC22:57
*** baoli has joined #openstack-meeting22:58
*** baoli has quit IRC22:59
*** jamesdenton has quit IRC23:02
*** TxGirlGeek has quit IRC23:03
*** iceyao has joined #openstack-meeting23:03
*** baoli has joined #openstack-meeting23:04
*** erlon has quit IRC23:05
*** tdasilva has joined #openstack-meeting23:07
*** reedip_1 has joined #openstack-meeting23:07
*** iceyao has quit IRC23:07
*** felipemonteiro_ has quit IRC23:10
*** dimtruck is now known as zz_dimtruck23:13
*** tdasilva has quit IRC23:15
*** eharney has quit IRC23:16
*** ociuhandu has quit IRC23:17
*** grumpycatt has quit IRC23:18
*** grumpycatt has joined #openstack-meeting23:18
*** anilvenkata_afk has quit IRC23:19
*** annegent_ has quit IRC23:20
*** anilvenkata_afk has joined #openstack-meeting23:21
*** lamt has quit IRC23:23
*** grumpycatt has quit IRC23:25
*** grumpycatt has joined #openstack-meeting23:25
*** bcafarel has quit IRC23:25
*** bcafarel has joined #openstack-meeting23:26
*** xyang1 has quit IRC23:27
*** fnaval has quit IRC23:28
*** powerd has quit IRC23:30
*** jaugustine has quit IRC23:31
*** claudiub|2 has quit IRC23:33
*** tdasilva has joined #openstack-meeting23:34
*** mriedem has quit IRC23:36
*** VW has quit IRC23:37
*** powerd has joined #openstack-meeting23:38
*** rbak has quit IRC23:38
*** ociuhandu has joined #openstack-meeting23:40
*** boden has quit IRC23:42
*** galstrom is now known as galstrom_zzz23:43
*** thorst has joined #openstack-meeting23:45
*** thorst has quit IRC23:45
*** tobberydberg has joined #openstack-meeting23:45
*** Leo_ has quit IRC23:46
*** baoli has quit IRC23:47
*** tobberydberg has quit IRC23:50
*** thorst has joined #openstack-meeting23:55
*** fnaval has joined #openstack-meeting23:56
*** fnaval has quit IRC23:56
*** esberglu has joined #openstack-meeting23:58

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