*** dmorita has joined #openstack-meeting | 00:01 | |
*** salv-orlando has quit IRC | 00:09 | |
*** dmacpher has joined #openstack-meeting | 00:09 | |
*** mickeys has joined #openstack-meeting | 00:10 | |
*** aeng has joined #openstack-meeting | 00:12 | |
*** mickeys has quit IRC | 00:14 | |
*** jrobinson has joined #openstack-meeting | 00:15 | |
*** fnaval has quit IRC | 00:18 | |
*** armax has quit IRC | 00:20 | |
*** dmacpher has quit IRC | 00:22 | |
*** reedip has quit IRC | 00:23 | |
*** Julien-zte has joined #openstack-meeting | 00:38 | |
*** gcb has quit IRC | 00:42 | |
*** rderose has quit IRC | 00:46 | |
*** esberglu has joined #openstack-meeting | 00:54 | |
*** sdague has quit IRC | 00:57 | |
*** esberglu has quit IRC | 00:58 | |
*** iceyao has joined #openstack-meeting | 01:01 | |
*** diablo_rojo has joined #openstack-meeting | 01:01 | |
*** tobberydberg has joined #openstack-meeting | 01:03 | |
*** tobberydberg has quit IRC | 01:08 | |
*** cody-somerville has quit IRC | 01:09 | |
*** cody-somerville has joined #openstack-meeting | 01:09 | |
*** cody-somerville has quit IRC | 01:09 | |
*** cody-somerville has joined #openstack-meeting | 01:09 | |
*** kevinz has joined #openstack-meeting | 01:11 | |
*** mickeys has joined #openstack-meeting | 01:11 | |
*** kevinz has quit IRC | 01:11 | |
*** mickeys has quit IRC | 01:15 | |
*** kevinz has joined #openstack-meeting | 01:17 | |
*** Apoorva has quit IRC | 01:19 | |
*** longxiongqiu has joined #openstack-meeting | 01:20 | |
*** cody-somerville has quit IRC | 01:23 | |
*** Sukhdev has quit IRC | 01:26 | |
*** zhhuabj has quit IRC | 01:26 | |
*** diablo_rojo has quit IRC | 01:27 | |
*** guoshan has joined #openstack-meeting | 01:28 | |
*** zhurong has joined #openstack-meeting | 01:30 | |
*** huanxuan has joined #openstack-meeting | 01:37 | |
*** zhhuabj has joined #openstack-meeting | 01:39 | |
*** yamamoto has joined #openstack-meeting | 01:43 | |
*** diablo_rojo has joined #openstack-meeting | 01:47 | |
*** ykatabam1 has joined #openstack-meeting | 01:50 | |
*** knangia has quit IRC | 01:51 | |
*** ykatabam has quit IRC | 01:51 | |
*** VW has joined #openstack-meeting | 01:51 | |
*** julim_ has joined #openstack-meeting | 01:54 | |
*** julim has quit IRC | 01:54 | |
*** zhhuabj has quit IRC | 01:54 | |
*** dmorita has quit IRC | 01:55 | |
*** sshnaidm is now known as sshnaidm|off | 01:56 | |
*** zz_dimtruck is now known as dimtruck | 01:57 | |
*** VW has quit IRC | 01:59 | |
*** hongbin has joined #openstack-meeting | 02:00 | |
*** lakerzhou has joined #openstack-meeting | 02:00 | |
*** vishnoianil has quit IRC | 02:02 | |
*** lhx__ has joined #openstack-meeting | 02:02 | |
*** lhx__ has quit IRC | 02:06 | |
*** lhx__ has joined #openstack-meeting | 02:07 | |
*** esberglu has joined #openstack-meeting | 02:09 | |
*** VW has joined #openstack-meeting | 02:10 | |
*** unicell has quit IRC | 02:11 | |
*** mickeys has joined #openstack-meeting | 02:12 | |
*** bobh has quit IRC | 02:12 | |
*** dmorita has joined #openstack-meeting | 02:13 | |
*** esberglu has quit IRC | 02:14 | |
*** zhhuabj has joined #openstack-meeting | 02:14 | |
*** reedip has joined #openstack-meeting | 02:14 | |
*** mickeys has quit IRC | 02:16 | |
*** ykatabam1 has quit IRC | 02:16 | |
*** dmorita has quit IRC | 02:17 | |
*** VW has quit IRC | 02:19 | |
*** bobh has joined #openstack-meeting | 02:20 | |
*** VW has joined #openstack-meeting | 02:30 | |
*** FengShengqin has joined #openstack-meeting | 02:32 | |
*** ykatabam has joined #openstack-meeting | 02:32 | |
*** VW has quit IRC | 02:33 | |
*** gouthamr has quit IRC | 02:33 | |
*** bobh has quit IRC | 02:36 | |
*** fzdarsky_ has joined #openstack-meeting | 02:39 | |
*** gongysh has joined #openstack-meeting | 02:40 | |
*** bobh has joined #openstack-meeting | 02:41 | |
*** yamahata has quit IRC | 02:42 | |
*** baoli has joined #openstack-meeting | 02:43 | |
*** fnaval has joined #openstack-meeting | 02:43 | |
*** fzdarsky has quit IRC | 02:43 | |
*** epico has joined #openstack-meeting | 02:43 | |
*** fnaval has quit IRC | 02:43 | |
*** VW has joined #openstack-meeting | 02:45 | |
*** hongbin has quit IRC | 02:46 | |
*** iyamahat has quit IRC | 02:47 | |
*** VW_ has joined #openstack-meeting | 02:47 | |
*** VW has quit IRC | 02:47 | |
*** hongbin has joined #openstack-meeting | 02:48 | |
*** shubhams has joined #openstack-meeting | 02:48 | |
*** FengShengqin has quit IRC | 02:49 | |
*** mkrai_ has joined #openstack-meeting | 02:49 | |
*** FengShengqin has joined #openstack-meeting | 02:51 | |
*** cody-somerville has joined #openstack-meeting | 02:52 | |
*** sudipto has joined #openstack-meeting | 02:54 | |
*** sudipto has quit IRC | 02:56 | |
*** pksingh has joined #openstack-meeting | 02:58 | |
hongbin | #startmeeting zun | 03:00 |
---|---|---|
openstack | Meeting started Tue Mar 14 03:00:03 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 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 03:00 |
*** openstack changes topic to " (Meeting topic: zun)" | 03:00 | |
openstack | The meeting name has been set to 'zun' | 03:00 |
hongbin | #link https://wiki.openstack.org/wiki/Zun#Agenda_for_2017-03-14_0300_UTC Today's agenda | 03:00 |
hongbin | #topic Roll Call | 03:00 |
*** openstack changes topic to "Roll Call (Meeting topic: zun)" | 03:00 | |
mkrai_ | Madhuri Kumari | 03:00 |
shubhams | shubham | 03:00 |
pksingh | pradeep | 03:00 |
*** zhangjl has joined #openstack-meeting | 03:00 | |
kevinz | kevinz | 03:00 |
hongbin | thanks for joining the meeting mkrai_ shubhams pksingh kevinz | 03:01 |
hongbin | let's get started | 03:01 |
FengShengqin | hi | 03:01 |
hongbin | oh, hey FengShengqin | 03:01 |
hongbin | FengShengqin: thanks for joining | 03:01 |
hongbin | #topic Announcements | 03:01 |
*** openstack changes topic to "Announcements (Meeting topic: zun)" | 03:01 | |
hongbin | 1. Zun will have two presentations in Boston Summit | 03:02 |
hongbin | #link https://www.openstack.org/summit/boston-2017/summit-schedule/events/18591/project-update-zun Project Update - Zun | 03:02 |
hongbin | #link https://www.openstack.org/summit/boston-2017/summit-schedule/events/17988/future-of-containers-in-openstack Future of Containers in OpenStack | 03:02 |
mkrai_ | Yayy !! | 03:02 |
pksingh | FengShengqin: You had some problem with IRC in your organization? Good to see you here :) | 03:02 |
hongbin | There are a few other talks that will related to zun | 03:02 |
pksingh | :( | 03:02 |
pksingh | i can't be part of the talk | 03:02 |
FengShengqin | yes,I'm glad too | 03:02 |
hongbin | #topic Review Action Items | 03:03 |
*** openstack changes topic to "Review Action Items (Meeting topic: zun)" | 03:03 | |
hongbin | #topic Cinder integration (diga) | 03:03 |
*** openstack changes topic to "Cinder integration (diga) (Meeting topic: zun)" | 03:03 | |
hongbin | #link https://blueprints.launchpad.net/zun/+spec/cinder-zun-integration The BP | 03:03 |
hongbin | it looks diga is not here, perhaps we could skip this topic for now | 03:03 |
hongbin | we could revisit it if diga showed up later in the meeting | 03:04 |
hongbin | fyi, it seems he was working on this patch last week | 03:04 |
hongbin | #link https://review.openstack.org/#/c/429943/ | 03:04 |
hongbin | #topic Kuryr integration (hongbin) | 03:04 |
*** openstack changes topic to "Kuryr integration (hongbin) (Meeting topic: zun)" | 03:05 | |
hongbin | #link https://blueprints.launchpad.net/zun/+spec/kuryr-integration The BP | 03:05 |
hongbin | i submitted several patches to kuryr-libnetwork, but still waiting for them to be merged | 03:05 |
*** VW_ has quit IRC | 03:06 | |
*** diga has joined #openstack-meeting | 03:06 | |
hongbin | i wanted to get them all merged first before starting to work on the zun side because the implemenation depends on how the patches will be accepted in kuryr side | 03:06 |
*** VW has joined #openstack-meeting | 03:06 | |
pksingh | hongbin: is there any problem in acceptence of those patches in kuryr? | 03:06 |
hongbin | fyi, here are the patches | 03:06 |
hongbin | #link https://review.openstack.org/#/q/project:openstack/kuryr-libnetwork+and+owner:%22Hongbin+Lu+%253Chongbin.lu%2540huawei.com%253E%22 | 03:06 |
pksingh | most of them got +2 :) | 03:07 |
hongbin | pksingh: reviewers might have some advices on revising the patches | 03:07 |
kevinz | cool | 03:07 |
hongbin | pksingh: the design might change to address comments from their reviewers | 03:07 |
hongbin | yes, it looks most of them are close to merge | 03:08 |
pksingh | hongbin: ok | 03:08 |
mkrai_ | It seems only few are left to be merged | 03:08 |
hongbin | hopefully, i can get them all merged by this week | 03:08 |
pksingh | great !! | 03:08 |
hongbin | ok, any other comment on this topic? | 03:08 |
diga | o/ | 03:08 |
diga | sorry got late | 03:09 |
hongbin | diga: hi diga, thanks for joining | 03:09 |
*** kaisers_ has joined #openstack-meeting | 03:09 | |
*** tpatil has joined #openstack-meeting | 03:09 | |
hongbin | #topic Cinder integration (diga) | 03:09 |
*** openstack changes topic to "Cinder integration (diga) (Meeting topic: zun)" | 03:09 | |
hongbin | #link https://blueprints.launchpad.net/zun/+spec/cinder-zun-integration The BP | 03:09 |
diga | hongbin: yeah | 03:09 |
hongbin | diga: ^^ | 03:09 |
diga | hongbin: Most of the work is completed, I am facing some problem with Fuxi, | 03:10 |
*** salv-orlando has joined #openstack-meeting | 03:10 | |
diga | hongbin: if you have time tomorrow your day time, can you help on it ? | 03:10 |
hongbin | diga: yes, i will try | 03:10 |
mkrai_ | diga: What kind of issue? | 03:10 |
*** VW has quit IRC | 03:10 | |
*** Shunli has joined #openstack-meeting | 03:11 | |
*** priteau has joined #openstack-meeting | 03:11 | |
diga | hongbin: Fuxi installation & some integration issues are there | 03:11 |
diga | hongbin: will mail you seperately on this, | 03:11 |
pksingh | Shunli: Welcome :) | 03:12 |
Shunli | :) | 03:12 |
diga | hongbin: mostly on integration level, something is messing up in docker volume call to fuxi | 03:12 |
hongbin | Shunli: hey, thanks for joining ! | 03:12 |
hongbin | diga: i see | 03:12 |
Shunli | my pleasure | 03:12 |
*** mickeys has joined #openstack-meeting | 03:12 | |
*** ihrachys has joined #openstack-meeting | 03:12 | |
diga | hongbin: I will send you details on this, I am not able to trace the issue at docker level | 03:12 |
hongbin | diga: sure, i will try my best to help | 03:13 |
diga | hongbin: thank you | 03:13 |
hongbin | thanks diga | 03:13 |
diga | hongbin: wc! | 03:13 |
hongbin | #topic Introduce host capabilities and cpusets (sudipto) | 03:14 |
*** openstack changes topic to "Introduce host capabilities and cpusets (sudipto) (Meeting topic: zun)" | 03:14 | |
hongbin | #link https://review.openstack.org/#/c/427007/ The spec | 03:14 |
hongbin | it looks sudipto is not here right now | 03:14 |
diga | hongbin: I have to join another office meeting at 9, need to leave now | 03:14 |
*** dmorita has joined #openstack-meeting | 03:14 | |
hongbin | diga: ok, ttyl, thanks again for joining the meeting | 03:14 |
diga | hongbin: np | 03:15 |
*** diga has quit IRC | 03:15 | |
*** salv-orlando has quit IRC | 03:15 | |
*** priteau has quit IRC | 03:15 | |
*** cody-somerville has quit IRC | 03:15 | |
hongbin | ok, let's table this topic to next week | 03:15 |
hongbin | next one | 03:15 |
hongbin | #topic Discussion of the image API | 03:15 |
*** openstack changes topic to "Discussion of the image API (Meeting topic: zun)" | 03:16 | |
hongbin | #link https://etherpad.openstack.org/p/zun-image-api the etherpad | 03:16 |
hongbin | mkrai_: shubhams : want to drive this topic? | 03:16 |
mkrai_ | Ok so I will try to give an update on this | 03:16 |
mkrai_ | hongbin: Yes | 03:16 |
mkrai_ | We (shubham, pksingh and I) had meeting on this and decided on few things | 03:16 |
mkrai_ | pksingh: Please feel free to chime in | 03:16 |
*** bobh has quit IRC | 03:16 | |
pksingh | mkrai_: go ahead :) | 03:17 |
*** ihrachys has quit IRC | 03:17 | |
mkrai_ | We decided to have some of the image APIs(POST, GET, DELETE) and all restricted to admin | 03:17 |
mkrai_ | For multiple hosts, pulling images should be possible for single host, all hosts or list of hosts separated by comma. This can be done in parallel if optimization is needed | 03:17 |
*** mickeys has quit IRC | 03:18 | |
mkrai_ | And we will have the 'host' field in image DB to store the hosts information | 03:18 |
FengShengqin | can anyone help how to use mulit zun-computes? | 03:18 |
*** youzp has joined #openstack-meeting | 03:18 | |
mkrai_ | And some of the APIs like search can be removed | 03:18 |
*** dmorita has quit IRC | 03:19 | |
mkrai_ | That's is all from our discussion | 03:19 |
hongbin | FengShengqin: your questions is about the image api? | 03:19 |
mkrai_ | What are teams' opinion on it? | 03:19 |
FengShengqin | no | 03:19 |
hongbin | FengShengqin: we can revisit your question later in the meeting agenda | 03:20 |
FengShengqin | thanks | 03:20 |
*** esberglu has joined #openstack-meeting | 03:20 | |
hongbin | mkrai_: if the search api is removed, users won't be able to search in dockerhub/glance? | 03:20 |
mkrai_ | hongbin: Yes | 03:21 |
hongbin | mkrai_: then they are expacted to use docker/glance cli to do that | 03:21 |
hongbin | mkrai_: which seems to be fine | 03:21 |
mkrai_ | hongbin: Yes | 03:21 |
hongbin | mkrai_: the only concern i have is scalability of storing all images X hosts db entries | 03:22 |
hongbin | mkrai_: however, i think it would be fine to get started in this way as proposed | 03:22 |
*** ihrachys has joined #openstack-meeting | 03:23 | |
hongbin | mkrai_: we can revisit it if the scalability is proven to be a problem later | 03:23 |
mkrai_ | I think having a single entry with 'host' field a list to store the images should do | 03:23 |
mkrai_ | sorry store the host info | 03:23 |
hongbin | perhaps it is better to start with a simpler implementation (host per image) | 03:24 |
hongbin | the optimization like storing list of hosts could be done at the second iteration | 03:24 |
mkrai_ | Ok sounds good | 03:24 |
mkrai_ | yes | 03:25 |
pksingh | hongbin: +1, it sounds good as of now | 03:25 |
*** esberglu has quit IRC | 03:25 | |
mkrai_ | Cool. Thanks pksingh and shubhams for the same :) | 03:25 |
hongbin | mkrai_: pksingh : i have no problem of this approach, it sounds good to me | 03:25 |
hongbin | others, any comment? | 03:25 |
mkrai_ | Thanks hongbin | 03:25 |
pksingh | :) | 03:26 |
mkrai_ | I will go ahead with the implementation | 03:26 |
hongbin | mkrai_: thanks | 03:26 |
*** unicell has joined #openstack-meeting | 03:27 | |
hongbin | mkrai_: shubhams pksingh thanks for all of you to work out the proposal | 03:27 |
*** huanxuan has quit IRC | 03:27 | |
hongbin | any other comment before advancing topic? | 03:27 |
hongbin | ok, move on | 03:28 |
hongbin | #topic Introduce container composition | 03:28 |
*** openstack changes topic to "Introduce container composition (Meeting topic: zun)" | 03:28 | |
hongbin | kevinz: want to drive this topic? | 03:28 |
hongbin | #link https://review.openstack.org/#/c/437759/ | 03:28 |
kevinz | Yeah ~ Wenzhi and me will work on this topic | 03:28 |
kevinz | And I've uploaded new version of the spec now | 03:28 |
hongbin | the spec looks quite close to remove the wip | 03:30 |
kevinz | In the new spec, we plan to implement capsule as K8S pod and incompatible with docker compose yml file(by setting the kind filed) | 03:30 |
kevinz | field | 03:30 |
hongbin | kind field? | 03:31 |
kevinz | Yeah "kind" field in yaml file. | 03:31 |
hongbin | what this field is going to represent? | 03:31 |
hongbin | docker or pod? | 03:32 |
kevinz | The "kind" can be set to "compose", if we want to praser the docker-compose file | 03:32 |
hongbin | i see | 03:32 |
hongbin | not sure how much this field would help | 03:33 |
hongbin | but that is just my feeling | 03:34 |
mkrai_ | Me too. What are the other valid option for field? | 03:34 |
pksingh | may be having different APIs would help more, but not sure | 03:34 |
kevinz | Now just "pod" and "compose", may be add more in the future | 03:35 |
kevinz | Differet "kind" field will call different praser for the yaml | 03:36 |
mkrai_ | Ok. I will try to visit the spec today and get more detail. | 03:36 |
yuanying | Does latest docker swarm support docker-compose? | 03:36 |
kevinz | pksingh: Yeah that is another way to implement | 03:36 |
hongbin | yuanying: hey, good to see you here :) | 03:37 |
*** janonymous has joined #openstack-meeting | 03:37 | |
yuanying | hongbin: hi, me too | 03:37 |
kevinz | yuanying: Not sure, I will check. So IMO, if docker-compose is not important, we will remove its support ? | 03:37 |
*** wxy has quit IRC | 03:38 | |
yuanying | I guess, docker-compose and pod are different | 03:38 |
yuanying | docker-compose is just a template, right?? | 03:38 |
kevinz | Yeah, just a template for multiple dockers. Don't have much functions | 03:39 |
yuanying | yes, but pod has other meaning | 03:39 |
yuanying | it has tightly related conatiners | 03:40 |
yuanying | So, I think we should avoid to think | 03:40 |
hongbin | kevinz: i think yuanying bring up a great point here | 03:41 |
yuanying | to regard the same between pod and docker-compose | 03:41 |
hongbin | compose and pod are very different in implementation and meaning | 03:41 |
kevinz | Yeah, compatible with docker compose file may introduce more problem. | 03:41 |
hongbin | i would rather to pick one instead of picking both | 03:41 |
yuanying | maybe | 03:41 |
kevinz | Right, so I think pod is good to implement now | 03:42 |
hongbin | ok, wfm | 03:42 |
mkrai_ | +1 for pod | 03:42 |
yuanying | +1 | 03:42 |
pksingh | +1 | 03:42 |
kevinz | May be table docker-compose compatible in the future | 03:42 |
hongbin | great | 03:43 |
kevinz | OK Thanks~ I will update the spec for review | 03:43 |
hongbin | it looks we agreed on a direction | 03:43 |
hongbin | kevinz: thanks | 03:43 |
kevinz | :-) | 03:43 |
kevinz | My pleasure ~ Thanks all for the valuable advice | 03:43 |
hongbin | any other comment on this topic? | 03:43 |
*** takahara has joined #openstack-meeting | 03:44 | |
hongbin | #topic Manage resource constraints per sandbox | 03:44 |
*** openstack changes topic to "Manage resource constraints per sandbox (Meeting topic: zun)" | 03:44 | |
*** ihrachys has quit IRC | 03:44 | |
hongbin | #link https://blueprints.launchpad.net/zun/+spec/resource-management | 03:44 |
hongbin | i wanted to bring this up to see if everyone agree on this proposal | 03:45 |
hongbin | or feel free to bring up any opposing point of view | 03:45 |
*** shubhams has quit IRC | 03:45 | |
hongbin | the idea is very simple: adding --cgroup-parent option to poin to the sandbox (infra container) when lauching the real container | 03:46 |
hongbin | e.g. docker run ... -cgroup-parent <sandbox> ... | 03:46 |
mkrai_ | hongbin: Currently there is one container per sandbox. Right? | 03:46 |
hongbin | mkrai_: yes | 03:47 |
mkrai_ | And does this mean we can have multiple container inside one sandbox? | 03:47 |
yuanying | Is this related to Pod implementation? | 03:47 |
hongbin | yes | 03:47 |
mkrai_ | so it means we are exposing the sandbox containers as well | 03:47 |
*** Julien-zte has quit IRC | 03:48 | |
hongbin | yuanying: yes, i guess it will be used by kevinz 's proposal | 03:48 |
yuanying | ok | 03:48 |
*** Julien-zte has joined #openstack-meeting | 03:48 | |
mkrai_ | hongbin: ^ | 03:48 |
hongbin | mkrai_: not really, pod doesn't expose infra container either | 03:48 |
mkrai_ | Yes so that is what I was thinking | 03:49 |
*** tpatil has quit IRC | 03:49 | |
hongbin | mkrai_: i mean you know there is a pod, but you don't know the infra container, although you can see the resource constraints of the pods | 03:49 |
mkrai_ | I can't realise the design now, are you planning to submit any spec for this feature? | 03:50 |
hongbin | mkrai_: you have any specific concern? | 03:50 |
*** rabel_b1 has joined #openstack-meeting | 03:50 | |
hongbin | mkrai_: i can if i am the one who will take this bp :) | 03:51 |
mkrai_ | That will be great :) | 03:51 |
hongbin | if nobody want to take it, i can be the default, then i can work out a spec, that is fine. | 03:51 |
mkrai_ | As per my knowledge it is not possible to add containers to pod after it is launched. Right ? | 03:52 |
hongbin | mkrai_: although i am not sure, i think it can | 03:52 |
*** huanxuan has joined #openstack-meeting | 03:52 | |
hongbin | mkrai_: the cgroup should be able to change at runtime | 03:52 |
mkrai_ | hongbin: Ok I need to check in k8s | 03:53 |
hongbin | mkrai_: i don't think k8s allow it, but i mean it is technically possible | 03:54 |
mkrai_ | yes | 03:54 |
hongbin | ok, let's move to open discussion | 03:54 |
hongbin | #topic Open Discussion | 03:54 |
*** openstack changes topic to "Open Discussion (Meeting topic: zun)" | 03:54 | |
hongbin | mkrai_: any other concern you have? | 03:55 |
mkrai_ | No but I would prefer to have a spec for this, if everyone is ok | 03:55 |
hongbin | mkrai_: ack | 03:55 |
mkrai_ | Thanks hongbin | 03:55 |
hongbin | np | 03:55 |
*** dmorita has joined #openstack-meeting | 03:56 | |
hongbin | FengShengqin: i think you had a question in before, now it is the right time to ask :) | 03:56 |
*** Sukhdev has joined #openstack-meeting | 03:56 | |
*** zsli_ has joined #openstack-meeting | 03:57 | |
hongbin | others, any topic to bring up? | 03:57 |
hongbin | seems no, we can end the meeting a little earlier today | 03:58 |
hongbin | all, thanks for joining the meeting, see you next time | 03:58 |
mkrai_ | Thank you everyone | 03:58 |
*** tpatil has joined #openstack-meeting | 03:58 | |
hongbin | #endmeeting | 03:58 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 03:58 | |
openstack | Meeting ended Tue Mar 14 03:58:42 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 03:58 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-03-14-03.00.html | 03:58 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-03-14-03.00.txt | 03:58 |
openstack | Log: http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-03-14-03.00.log.html | 03:58 |
*** Shunli has quit IRC | 03:59 | |
*** rkmrHonjo has joined #openstack-meeting | 03:59 | |
*** hongbin has quit IRC | 03:59 | |
*** mkrai_ has quit IRC | 04:00 | |
*** sagara has joined #openstack-meeting | 04:00 | |
*** dmorita has quit IRC | 04:00 | |
rkmrHonjo | Hi | 04:01 |
sagara | hi | 04:01 |
tpatil | Hi | 04:01 |
sagara | today, sampath maybe cannot join this meeting | 04:02 |
*** Dinesh_Bhor has joined #openstack-meeting | 04:02 | |
tpatil | Ok | 04:02 |
tpatil | who would like to drive this meeting? | 04:03 |
rkmrHonjo | OK, I try to drive. | 04:03 |
tpatil | Ok | 04:03 |
sagara | rkmrHonjo: thanks | 04:03 |
rkmrHonjo | #startmeeting masakari | 04:03 |
openstack | Meeting started Tue Mar 14 04:03:57 2017 UTC and is due to finish in 60 minutes. The chair is rkmrHonjo. Information about MeetBot at http://wiki.debian.org/MeetBot. | 04:03 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 04:03 |
*** openstack changes topic to " (Meeting topic: masakari)" | 04:04 | |
openstack | The meeting name has been set to 'masakari' | 04:04 |
*** pksingh has quit IRC | 04:04 | |
rkmrHonjo | #topic bugs | 04:04 |
*** openstack changes topic to "bugs (Meeting topic: masakari)" | 04:04 | |
rkmrHonjo | Do you have any bugs to discuss? | 04:04 |
*** baoli has quit IRC | 04:04 | |
*** guoshan has quit IRC | 04:05 | |
rkmrHonjo | nothing? | 04:05 |
tpatil | # link : https://bugs.launchpad.net/masakari/+bug/1670940 | 04:05 |
openstack | Launchpad bug 1670940 in masakari "If failure host is the reserved host, the compute service of the failure host finally beccomes the enable status" [Undecided,In progress] - Assigned to takahara.kengo (takahara.kengo) | 04:05 |
sagara | do we need to talk https://bugs.launchpad.net/masakari/+bug/1670940 ? | 04:05 |
*** pksingh has joined #openstack-meeting | 04:06 | |
tpatil | There is already a patch up to fix this issue | 04:06 |
tpatil | I will review this patch soon | 04:06 |
rkmrHonjo | tpatil: Thank you. I'll review it, too. | 04:06 |
sagara | me too | 04:06 |
*** ykatabam has quit IRC | 04:06 | |
rkmrHonjo | any other items? | 04:07 |
sagara | no | 04:07 |
*** asselin has quit IRC | 04:08 | |
rkmrHonjo | ok. Let's go to next topic. | 04:08 |
rkmrHonjo | #topic Pike work items | 04:08 |
*** openstack changes topic to "Pike work items (Meeting topic: masakari)" | 04:08 | |
sagara | #link: https://etherpad.openstack.org/p/masakari-pike-workitems | 04:08 |
rkmrHonjo | Do you have objections about priorities written in etherpad? | 04:09 |
rkmrHonjo | s/objections/opinions/g | 04:09 |
sagara | I have read all items, I agree those priorities. | 04:10 |
tpatil | me too | 04:10 |
Dinesh_Bhor | yes, me too | 04:11 |
rkmrHonjo | me too. | 04:11 |
Dinesh_Bhor | About this: Python 3.x support | 04:12 |
tpatil | It will be nice to see specs for high priority items | 04:12 |
*** iceyao has quit IRC | 04:12 | |
Dinesh_Bhor | I think most of the masakari code is already PY3 compatible | 04:12 |
*** youzp has quit IRC | 04:13 | |
tpatil | Dinesh_Bhor: Do we have any gate jobs that run on PY3? | 04:14 |
Dinesh_Bhor | tpatil: No, not yet | 04:14 |
*** zsli__ has joined #openstack-meeting | 04:15 | |
*** mickeys has joined #openstack-meeting | 04:15 | |
tpatil | It's better to add this support before declaring it's py3 compatible | 04:15 |
*** ihrachys has joined #openstack-meeting | 04:15 | |
Dinesh_Bhor | tpatil: Agree | 04:15 |
*** iceyao has joined #openstack-meeting | 04:15 | |
*** rabel__b1 has joined #openstack-meeting | 04:16 | |
*** ykatabam has joined #openstack-meeting | 04:16 | |
*** abhishekk has joined #openstack-meeting | 04:16 | |
sagara | tpatil, Dinesh_Bhor: Do we need to change py3 priority? | 04:16 |
*** zsli__ has quit IRC | 04:18 | |
tpatil | Anyone want to run masakari on Py3? | 04:18 |
*** zsli_ has quit IRC | 04:18 | |
tpatil | If yes, we can make it high priority | 04:18 |
*** zsli__ has joined #openstack-meeting | 04:18 | |
*** mickeys has quit IRC | 04:19 | |
sagara | I haven't heard run masakari on Py3. | 04:19 |
*** rabel_b1 has quit IRC | 04:19 | |
sagara | So, I think we don't need to change that priority (remains Low) | 04:20 |
rkmrHonjo | I think that there are a few people running openstack on Py3. | 04:20 |
*** iceyao has quit IRC | 04:20 | |
rkmrHonjo | sagara: I agree to your opinion. | 04:22 |
Dinesh_Bhor | sagara: I am ok with L | 04:23 |
tpatil | rkmrHonjo: Let's these people comment on the Py3 item on etherpad and we can change it's priority to high. What do you guys think? | 04:23 |
sagara | tpatil: I agree | 04:24 |
tpatil | Dinesh has added a new BP | 04:24 |
tpatil | # link: https://blueprints.launchpad.net/masakari/+spec/enable-openstack-proposal-bot | 04:24 |
rkmrHonjo | tpatil: I agree. | 04:24 |
tpatil | sagara, rkmrHonjo: Thanks | 04:25 |
*** ihrachys has quit IRC | 04:25 | |
tpatil | Add devstack plugin for masakari-monitors | 04:25 |
tpatil | For above item , I don't think there is a need for specs | 04:26 |
tpatil | presently, masakari doesn't install masakari-monitors on single node | 04:26 |
tpatil | we should add this support in masakari devstack plugin itself | 04:27 |
sagara | tpatil: I agree, I think it also need for destructive testing for masakari | 04:28 |
*** Sukhdev has quit IRC | 04:28 | |
tpatil | sagara: correct | 04:29 |
tpatil | Recoverable libvirt events customization | 04:29 |
tpatil | Who will write specs for this item? | 04:29 |
rkmrHonjo | tpatil: me. | 04:29 |
rkmrHonjo | soryy, | 04:30 |
rkmrHonjo | sorry, not me. | 04:30 |
sagara | Is it sampath idea? | 04:30 |
*** iceyao has joined #openstack-meeting | 04:31 | |
tpatil | We need to understand which libvirt events to support and what action to take for each of them | 04:31 |
rkmrHonjo | sagara: the idea is written by me. but the person who writes specs is not decided. | 04:31 |
rkmrHonjo | tpatil: yes. | 04:31 |
*** kaisers_ has quit IRC | 04:32 | |
rkmrHonjo | sagara, tpatil: OK, I try to write specs. | 04:32 |
tpatil | Add ssl support to Masakari API | 04:32 |
tpatil | We have worked on this item before. Will upload patch soon | 04:33 |
rkmrHonjo | #action rkrmHonjo write Recoverable libvirt events customization spec | 04:33 |
abhishekk | tpatil: for this no changes needed in masakari | 04:33 |
tpatil | abhishekk: need to confirm it again | 04:34 |
abhishekk | tpatil: we need to get this patch merged in devstack https://review.openstack.org/#/c/416009/ | 04:34 |
sagara | "Add ssl support to Masakari API" have already implemented (but not merged)? | 04:34 |
*** zsli_ has joined #openstack-meeting | 04:34 | |
sagara | I confirmed it. ok so I will review it. | 04:35 |
*** links has joined #openstack-meeting | 04:35 | |
*** ihrachys has joined #openstack-meeting | 04:36 | |
rkmrHonjo | abhishekk: Can we use HTTPS endpoint if we install current masakari by manual(not devstack)? | 04:36 |
*** zsli__ has quit IRC | 04:36 | |
sagara | sorry, I misunderstood about https://review.openstack.org/#/c/416009/ | 04:37 |
*** youzp has joined #openstack-meeting | 04:37 | |
abhishekk | rkmrHonjo: I have not tried mannualy, but IMO it will work | 04:37 |
rkmrHonjo | abhishekk: ok, thanks. | 04:38 |
abhishekk | you just need to create https endpoints | 04:38 |
*** gongysh has quit IRC | 04:40 | |
rkmrHonjo | abhishekk: Really? Is specifying key files in masakari.conf unnecessary? | 04:40 |
abhishekk | rkmrHonjo: you need to specify ssl_key_file = /opt/stack/data/CA/int-ca/private/devstack-cert.key and | 04:42 |
abhishekk | ssl_cert_file = /opt/stack/data/CA/int-ca/devstack-cert.crt | 04:42 |
abhishekk | under wsgi section in masakari.conf | 04:42 |
rkmrHonjo | abhishekk: thanks! | 04:42 |
abhishekk | these key files you can found in devstack repo | 04:43 |
abhishekk | s/found/find | 04:43 |
sagara | Let's talk next item | 04:46 |
rkmrHonjo | OK. After all, should we need to change the priority? I think that it is not needed. | 04:46 |
rkmrHonjo | sagara: sorry, ok. let's go to next item. | 04:47 |
*** cody-somerville has joined #openstack-meeting | 04:47 | |
sagara | rkmrHonjo: don't need to change "add ssl support"'s priority. and it maybe already works well. | 04:48 |
rkmrHonjo | sagara: ok. | 04:49 |
sagara | Is there any comment for items below? | 04:50 |
rkmrHonjo | sagara: no. | 04:50 |
tpatil | can we proceed to the next topic? | 04:52 |
rkmrHonjo | tpati: Yeah. Next topic is AOB. | 04:52 |
sagara | tpatil: yes. I already agree | 04:52 |
rkmrHonjo | #topic AOB | 04:52 |
*** openstack changes topic to "AOB (Meeting topic: masakari)" | 04:52 | |
*** markstur_ has quit IRC | 04:52 | |
rkmrHonjo | Do you have any other topics? | 04:53 |
*** dmacpher has joined #openstack-meeting | 04:53 | |
*** gongysh has joined #openstack-meeting | 04:53 | |
*** tobberydberg has joined #openstack-meeting | 04:54 | |
tpatil | No | 04:54 |
rkmrHonjo | OK, thank you all. this meeting is over. | 04:54 |
*** markstur has joined #openstack-meeting | 04:54 | |
rkmrHonjo | (I'll write "endmeeting" after that.) | 04:55 |
rkmrHonjo | #endmeeting | 04:55 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 04:55 | |
openstack | Meeting ended Tue Mar 14 04:55:20 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 04:55 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-03-14-04.03.html | 04:55 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-03-14-04.03.txt | 04:55 |
openstack | Log: http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-03-14-04.03.log.html | 04:55 |
sagara | thanks | 04:55 |
*** youzp has quit IRC | 04:55 | |
*** zsli_ has quit IRC | 04:55 | |
*** sagara has quit IRC | 04:56 | |
rkmrHonjo | thank you all. bye. | 04:56 |
*** gongysh has quit IRC | 04:56 | |
*** rkmrHonjo has quit IRC | 04:56 | |
*** tobberydberg has quit IRC | 04:58 | |
*** markstur has quit IRC | 04:58 | |
*** knangia has joined #openstack-meeting | 04:59 | |
*** takahara has quit IRC | 04:59 | |
*** zsli_ has joined #openstack-meeting | 05:00 | |
*** zsli_ has quit IRC | 05:00 | |
*** janki has joined #openstack-meeting | 05:01 | |
*** kaisers_ has joined #openstack-meeting | 05:02 | |
*** tpatil has quit IRC | 05:03 | |
*** yatin_away is now known as yatin | 05:06 | |
*** yatin is now known as yatinkarel | 05:07 | |
*** ayogi has joined #openstack-meeting | 05:07 | |
*** esberglu has joined #openstack-meeting | 05:08 | |
*** salv-orlando has joined #openstack-meeting | 05:11 | |
*** youzp has joined #openstack-meeting | 05:11 | |
*** dimtruck is now known as zz_dimtruck | 05:12 | |
*** esberglu has quit IRC | 05:13 | |
*** salv-orlando has quit IRC | 05:15 | |
*** dmorita has joined #openstack-meeting | 05:16 | |
*** jrobinson has quit IRC | 05:17 | |
*** gcb has joined #openstack-meeting | 05:17 | |
*** dmorita has quit IRC | 05:20 | |
*** trinaths has joined #openstack-meeting | 05:21 | |
*** Julien-zte has quit IRC | 05:24 | |
*** Julien-zte has joined #openstack-meeting | 05:25 | |
*** epico has quit IRC | 05:25 | |
*** youzp has quit IRC | 05:25 | |
*** epico has joined #openstack-meeting | 05:27 | |
*** jrobinson has joined #openstack-meeting | 05:27 | |
*** rabel__b1 has quit IRC | 05:27 | |
*** zhangjl has left #openstack-meeting | 05:27 | |
*** prateek has joined #openstack-meeting | 05:33 | |
*** markstur has joined #openstack-meeting | 05:35 | |
*** markstur has quit IRC | 05:39 | |
*** swapnil-nilangek has joined #openstack-meeting | 05:40 | |
*** janonymous has quit IRC | 05:44 | |
*** DFFlanders has joined #openstack-meeting | 05:46 | |
*** sridharg has joined #openstack-meeting | 05:46 | |
*** adisky_ has joined #openstack-meeting | 05:48 | |
*** csomerville has joined #openstack-meeting | 05:49 | |
*** gongysh has joined #openstack-meeting | 05:51 | |
*** claudiub has joined #openstack-meeting | 05:51 | |
*** cody-somerville has quit IRC | 05:52 | |
*** ihrachys has quit IRC | 05:56 | |
*** reedip has quit IRC | 06:00 | |
*** tobberydberg has joined #openstack-meeting | 06:01 | |
*** tobberydberg has quit IRC | 06:03 | |
*** tobberydberg has joined #openstack-meeting | 06:03 | |
*** kaisers_ has quit IRC | 06:06 | |
*** nkrinner_afk is now known as nkrinner | 06:06 | |
*** tobberydberg has quit IRC | 06:08 | |
*** Dinesh_Bhor has left #openstack-meeting | 06:10 | |
*** ykatabam has quit IRC | 06:11 | |
*** salv-orlando has joined #openstack-meeting | 06:12 | |
*** bkopilov has joined #openstack-meeting | 06:14 | |
*** yamahata has joined #openstack-meeting | 06:15 | |
*** prateek has quit IRC | 06:15 | |
*** prateek has joined #openstack-meeting | 06:16 | |
*** markstur has joined #openstack-meeting | 06:16 | |
*** salv-orlando has quit IRC | 06:17 | |
*** nadya has joined #openstack-meeting | 06:17 | |
*** markstur has quit IRC | 06:21 | |
*** mickeys has joined #openstack-meeting | 06:25 | |
*** salv-orlando has joined #openstack-meeting | 06:26 | |
*** epico has quit IRC | 06:26 | |
*** david-lyle has quit IRC | 06:27 | |
*** mickeys has quit IRC | 06:28 | |
*** belmoreira has joined #openstack-meeting | 06:29 | |
*** anilvenkata has joined #openstack-meeting | 06:30 | |
*** epico has joined #openstack-meeting | 06:39 | |
*** nadya has quit IRC | 06:40 | |
*** yangyapeng has joined #openstack-meeting | 06:40 | |
*** unicell has quit IRC | 06:42 | |
*** yangyapeng has quit IRC | 06:44 | |
*** kaisers_ has joined #openstack-meeting | 06:44 | |
*** gyee has joined #openstack-meeting | 06:45 | |
*** gyee has quit IRC | 06:46 | |
*** vishnoianil has joined #openstack-meeting | 06:47 | |
*** andreas_s has joined #openstack-meeting | 06:47 | |
*** gyee has joined #openstack-meeting | 06:49 | |
*** kaisers_ has quit IRC | 06:49 | |
*** lpetrut has joined #openstack-meeting | 06:49 | |
*** gyee has quit IRC | 06:50 | |
*** kaisers_ has joined #openstack-meeting | 06:51 | |
*** e0ne has joined #openstack-meeting | 06:51 | |
*** kaisers_ has quit IRC | 06:56 | |
*** esberglu has joined #openstack-meeting | 06:57 | |
*** markstur has joined #openstack-meeting | 06:58 | |
*** esberglu has quit IRC | 07:01 | |
*** markstur has quit IRC | 07:02 | |
*** dmacpher has quit IRC | 07:09 | |
*** nkrinner has quit IRC | 07:09 | |
*** alexchadin has joined #openstack-meeting | 07:10 | |
*** nkrinner has joined #openstack-meeting | 07:14 | |
*** mriedem has quit IRC | 07:17 | |
*** rbak has quit IRC | 07:19 | |
*** tesseract has joined #openstack-meeting | 07:20 | |
*** rbak has joined #openstack-meeting | 07:20 | |
*** knangia has quit IRC | 07:21 | |
*** salv-orl_ has joined #openstack-meeting | 07:23 | |
*** youzp has joined #openstack-meeting | 07:23 | |
*** youzp has quit IRC | 07:23 | |
*** mickeys has joined #openstack-meeting | 07:25 | |
*** salv-orlando has quit IRC | 07:26 | |
*** yuval has joined #openstack-meeting | 07:27 | |
*** e0ne has quit IRC | 07:28 | |
*** youzp has joined #openstack-meeting | 07:28 | |
*** mickeys has quit IRC | 07:29 | |
*** jrobinson has quit IRC | 07:31 | |
*** youzp has quit IRC | 07:36 | |
*** markstur has joined #openstack-meeting | 07:40 | |
*** iyamahat has joined #openstack-meeting | 07:40 | |
*** adiantum has joined #openstack-meeting | 07:41 | |
*** markstur has quit IRC | 07:44 | |
*** iyamahat has quit IRC | 07:45 | |
*** tobberydberg has joined #openstack-meeting | 07:47 | |
*** pcaruana has joined #openstack-meeting | 07:50 | |
*** priteau has joined #openstack-meeting | 07:51 | |
*** kaisers_ has joined #openstack-meeting | 07:52 | |
*** matrohon has joined #openstack-meeting | 07:52 | |
*** swapnil-nilangek has quit IRC | 07:52 | |
*** lpetrut has quit IRC | 07:55 | |
*** claudiub has quit IRC | 07:55 | |
*** mickeys has joined #openstack-meeting | 07:56 | |
*** kota_ has joined #openstack-meeting | 07:59 | |
*** sagara has joined #openstack-meeting | 08:00 | |
*** eranrom has joined #openstack-meeting | 08:00 | |
eranrom | #startmeeting storlets | 08:00 |
openstack | Meeting started Tue Mar 14 08:00:28 2017 UTC and is due to finish in 60 minutes. The chair is eranrom. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:00 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:00 |
*** openstack changes topic to " (Meeting topic: storlets)" | 08:00 | |
openstack | The meeting name has been set to 'storlets' | 08:00 |
kota_ | hey-yo | 08:00 |
sagara | hi | 08:00 |
eranrom | Hi | 08:00 |
*** akihito has joined #openstack-meeting | 08:01 | |
eranrom | Let's start. | 08:01 |
akihito | Hi | 08:01 |
*** takashi has joined #openstack-meeting | 08:01 | |
eranrom | akihito: Hi | 08:02 |
eranrom | I did not add anything to the agenda | 08:02 |
*** rbartal has joined #openstack-meeting | 08:02 | |
eranrom | There is something on stopping unused containers | 08:02 |
eranrom | which I am looking at | 08:02 |
takashi | hi | 08:03 |
kota_ | takashi: !!!! | 08:03 |
akihito | takashi: Hi! | 08:03 |
*** alexpilo_ has joined #openstack-meeting | 08:03 | |
*** alexpilotti has quit IRC | 08:03 | |
kota_ | we missed you takashi at the PTG | 08:03 |
*** nadya has joined #openstack-meeting | 08:03 | |
takashi | all: hi | 08:03 |
takashi | kota_: sorry about that :-( I'll check your great discussion result... | 08:04 |
eranrom | takashi: Hi! | 08:04 |
takashi | There are no big topics from my side today. I think I should review some of the patches about agent refactoring | 08:05 |
takashi | eranrom: o/ | 08:05 |
eranrom | takashi: great to see you here! | 08:05 |
takashi | eranrom: me too :-) | 08:05 |
takashi | it would be great if I can ask some review about https://review.openstack.org/#/c/426586/ | 08:05 |
takashi | especially from kota_ :-P | 08:05 |
kota_ | what's that? | 08:06 |
takashi | about range handling | 08:06 |
eranrom | #topic: Patches priority reviews | 08:06 |
*** openstack changes topic to ": Patches priority reviews (Meeting topic: storlets)" | 08:06 | |
kota_ | oic | 08:06 |
takashi | eranrom: thx | 08:06 |
eranrom | :-) | 08:07 |
takashi | I'm afraid this is very affective bug, so I'll backport it to stable later. | 08:07 |
takashi | after we land the fix | 08:07 |
takashi | I think we also need to backport the patch to fix breaking unit test to stable | 08:07 |
eranrom | takashi: yep, good point. | 08:07 |
eranrom | takashi: I think I did that. | 08:08 |
takashi | which is submitted by kota_ and already merged to master | 08:08 |
takashi | eranrom: I'm afraid that I overlooked that. thx! | 08:08 |
kota_ | if no big topic here, can we look at the patch together? | 08:08 |
kota_ | what's the difference after the version i reviewed | 08:08 |
kota_ | ? | 08:08 |
kota_ | sorry, I have to re-install the change in my head :/ | 08:09 |
akihito | I have 'stopping unused containers' topic. | 08:09 |
takashi | kota_: added some unit tests to assert my change | 08:09 |
sagara | I have resource limiting topic, but now I am writing that to etherpad. | 08:09 |
sagara | #link: https://etherpad.openstack.org/p/storlets-rate-resource-limiting-design | 08:09 |
takashi | kota_: in tests/unit/swift_middleware/handlers/test_obj.py and tests/unit/swift_middleware/handlers/test_proxy.py | 08:10 |
eranrom | ok lets spend few minutes on the patch, and then proceed with Sagara's and Akihito's topics | 08:10 |
takashi | eranrom: +1 | 08:10 |
*** salv-orl_ has quit IRC | 08:10 | |
sagara | thanks | 08:10 |
akihito | Thank you! I wrote my topic in etherpad. | 08:10 |
akihito | <<https://etherpad.openstack.org/p/storlets-pike-design-summit>> | 08:10 |
akihito | No. 10 - 12 | 08:10 |
eranrom | kota_: takashi: we want to go over this one https://review.openstack.org/#/c/426586/ right? | 08:11 |
kota_ | takashi: quick question, current *file* object range shouldbe [start, end] but http range [start, end), right? | 08:11 |
eranrom | akihito: yes, I saw good topic! | 08:11 |
kota_ | eranrom: yes | 08:11 |
takashi | kota_: yes | 08:11 |
kota_ | k and the middleware (which in http layer) resolves (translates) to file | 08:11 |
kota_ | make sense. | 08:11 |
*** esberglu has joined #openstack-meeting | 08:12 | |
*** swapnil-nilangek has joined #openstack-meeting | 08:12 | |
*** hashar has joined #openstack-meeting | 08:13 | |
kota_ | takashi: can you make sure https://review.openstack.org/#/c/426586/2..4/tests/unit/swift_middleware/handlers/test_obj.py@258 | 08:13 |
kota_ | ? | 08:13 |
*** imcsk8 has quit IRC | 08:14 | |
kota_ | the http range calls 1-6 there | 08:14 |
takashi | kota_: oh, sorry | 08:14 |
*** imcsk8 has joined #openstack-meeting | 08:14 | |
kota_ | and http range should be [1, 6) so that 1, 2, 3, 4, 5 | 08:14 |
takashi | In http rfc, range should include end | 08:14 |
*** ltomasbo|away is now known as ltomasbo | 08:14 | |
takashi | so http deals range as [start, end] | 08:14 |
kota_ | that means, opposite? | 08:14 |
takashi | kota_: yes | 08:14 |
takashi | current file object deals range as [start, end) | 08:15 |
takashi | so we need some translation between them | 08:15 |
takashi | more precisely, current python file object | 08:15 |
*** markstur has joined #openstack-meeting | 08:15 | |
kota_ | ah, ok, the docs in middleware says, general range as (include start, and exclude end) | 08:15 |
*** esberglu has quit IRC | 08:16 | |
takashi | kota_: I believe that is general range diffinition :-P | 08:16 |
takashi | definition | 08:16 |
kota_ | done | 08:19 |
eranrom | kota_: Thanks! | 08:20 |
takashi | kota_: thx! | 08:20 |
eranrom | anything else on reviews? | 08:20 |
kota_ | I still like clear cleanup for convert http range <-> general range (class or functions) | 08:20 |
kota_ | though | 08:20 |
*** markstur has quit IRC | 08:20 | |
eranrom | kota_: My understanding is that the translation between http and files requires adding +1 to the end. | 08:21 |
kota_ | eranrom: correct | 08:21 |
eranrom | previously that +1 was in the SBus layer, and Takashi changes that to happen in the middleware level | 08:21 |
takashi | eranrom: previously that +1 was done in Java SDaemon | 08:22 |
takashi | and not done in Python SDaemon (storlet-daemon) | 08:22 |
eranrom | oh, even worse... | 08:22 |
eranrom | takashi: right! | 08:22 |
takashi | with my patch, +1 is done in gateway side | 08:22 |
kota_ | takashi: that means, Java SDaemon is now +2 for the range? | 08:22 |
takashi | kota_: I removed that +1 in my patch | 08:22 |
kota_ | ok | 08:23 |
takashi | all range execution case python/java proxy/object is now tested in functional tests | 08:23 |
*** kaisers_ has quit IRC | 08:24 | |
eranrom | anything else on ramges? | 08:24 |
eranrom | ranges? | 08:24 |
takashi | nothing more from me | 08:25 |
takashi | I'll submit backport patch to stable/ocata later, and ping you after that | 08:25 |
*** martinkopec has joined #openstack-meeting | 08:25 | |
eranrom | takashi: sure. thanks! | 08:26 |
eranrom | anything else on patches before we continue? | 08:26 |
*** tobberydberg_ has joined #openstack-meeting | 08:28 | |
*** dmorita has joined #openstack-meeting | 08:28 | |
kota_ | please go ahead eranrom | 08:29 |
takashi | let's move to the next topic | 08:29 |
eranrom | Since I have already read, lets continue with Akihito's topic. | 08:29 |
eranrom | #topic: Stopping unused containers / storlet demons | 08:30 |
*** openstack changes topic to ": Stopping unused containers / storlet demons (Meeting topic: storlets)" | 08:30 | |
akihito | Thank you! | 08:30 |
eranrom | I like the suggestion, I have two comments so far: | 08:30 |
eranrom | 1. We need to add a configurable timeouts for all 3 (I think you mention a timeout only for the third, which is the storlet app) | 08:31 |
eranrom | 2. I would like to understand how you plan to enforce the storlet app timeout. for the factory and storlet daemon it seems pretty streight forward | 08:32 |
*** aarefiev_afk is now known as aarefiev | 08:32 | |
*** tobberydberg_ has quit IRC | 08:32 | |
*** dmorita has quit IRC | 08:33 | |
eranrom | sorry one more comment: | 08:33 |
eranrom | Regarding file deletions. Have we agreed on having a storlet create a file? | 08:33 |
*** markstur has joined #openstack-meeting | 08:33 | |
*** sandanar has joined #openstack-meeting | 08:34 | |
kota_ | sorry, I'm missing the etherpad which we reffers right now | 08:35 |
akihito | eranrom: Thank you comments. first. Why we need to set Timeout for daemon_factory and agent process? | 08:35 |
eranrom | https://etherpad.openstack.org/p/storlets-pike-design-summit | 08:35 |
akihito | No. 10-12 :-) | 08:35 |
kota_ | akihito: ah, you added to that one, ok thx | 08:36 |
kota_ | please continue | 08:36 |
eranrom | akihito: because when we, e.g. start the container, and hence the daemon_factory there may be some time passing before any storlet_daemon is started | 08:36 |
akihito | Oh. I understand! OK. fix it. | 08:37 |
eranrom | similarly, there may pass some time after we start a storlet_daemon and before we get a storlet request | 08:37 |
*** markstur has quit IRC | 08:38 | |
akihito | for No2 comments. I want to add timeout for storlet app in agent_process. | 08:39 |
akihito | https:/In /github.com/openstack/storlets/blob/master/storlets/agent/daemon/manager.py#L223-L224 | 08:39 |
akihito | sorry <<https://github.com/openstack/storlets/blob/master/storlets/agent/daemon/manager.py#L223-L224>> | 08:39 |
akihito | refer to <<https://review.openstack.org/#/c/410296/5/storlets/agent/common/server.py>> | 08:40 |
*** guoshan has joined #openstack-meeting | 08:40 | |
akihito | oh. sorry.. | 08:40 |
akihito | https://review.openstack.org/#/c/410296/5/storlets/agent/common/server.py | 08:40 |
*** rabel__b1 has joined #openstack-meeting | 08:42 | |
eranrom | Making a suggestion: | 08:43 |
eranrom | sorry.. | 08:43 |
kota_ | np | 08:44 |
eranrom | How about writing comments on the etherpads, and use the time now for questions. | 08:44 |
kota_ | i support that idea | 08:45 |
eranrom | akihito: I will comment on the Etherpad regarding your answer to comment 2. | 08:45 |
*** gongysh has quit IRC | 08:45 | |
*** ralonsoh has joined #openstack-meeting | 08:46 | |
akihito | eranrom: I see. Thank you. | 08:46 |
kota_ | eranrom: on the question for you | 08:49 |
eranrom | kota_: yep | 08:49 |
kota_ | eranrom: meaning "should we support that storlet app can write some files into the local in the container" | 08:49 |
kota_ | eranrom: I strongly recommend to support that option | 08:49 |
eranrom | kota_: right, we started this discussion. and I think takashi also wanted to ask on this. | 08:50 |
kota_ | eranrom: I know, we *don't* want such in-effective use case for our storlet streaming apps | 08:50 |
*** manikanta_tadi has quit IRC | 08:50 | |
*** e0ne has joined #openstack-meeting | 08:50 | |
kota_ | eranrom: however, from my experience with my custormers, absolutely we will have a clif (might be wall) when translating leagcy app to the storlet one. | 08:51 |
kota_ | i'm calling *legacy* app is something like which can run on file system | 08:51 |
*** toscalix has joined #openstack-meeting | 08:51 | |
*** sshnaidm|off is now known as sshnaidm | 08:52 | |
eranrom | kota_: I see. | 08:52 |
*** guoshan has quit IRC | 08:52 | |
kota_ | eranrom: i can manage the translation with my custormer but almost case for our poc starts with just running legacy app in the storlet container | 08:52 |
kota_ | that is enabled to write the files to read | 08:53 |
eranrom | ffmpeg? | 08:53 |
kota_ | no? | 08:53 |
kota_ | i have certain cases for now, | 08:53 |
kota_ | not only oss | 08:54 |
eranrom | kota_: I was asking because I had the same problem with ffmpeg for which I found a solution | 08:54 |
eranrom | kota_: got it | 08:54 |
*** salv-orlando has joined #openstack-meeting | 08:54 | |
eranrom | ok, note that cleaning up those files is as simple as restarting the container (and deleting the older instance) | 08:54 |
kota_ | eranrom: maybe it's one of them. espically, a kind of hard-coded 'path-forced' input format. | 08:55 |
*** Cibo_ has joined #openstack-meeting | 08:55 | |
eranrom | kota_: yep | 08:55 |
kota_ | like "progam -i file_to_path" | 08:55 |
eranrom | right | 08:55 |
*** phil_ has joined #openstack-meeting | 08:55 | |
eranrom | Will you be interested to setup another time this week to discuss the comments for Sagara's and Akihito's suggestions? | 08:56 |
*** janonymous has joined #openstack-meeting | 08:56 | |
*** shu-mutou-AWAY is now known as shu-mutou | 08:56 | |
eranrom | we can read it all and comment by then | 08:56 |
eranrom | we can meet in #openstack-storlets | 08:56 |
kota_ | +1 | 08:56 |
sagara | yes, I would like you to review resource limiting design. | 08:56 |
akihito | OK. | 08:57 |
eranrom | Tomorrow same time? | 08:57 |
kota_ | i could have | 08:58 |
takashi | I'll join if possible | 08:58 |
takashi | I had some local discussions about the topics with sagara-san and akihito, so I think you can have the discussion without me. | 08:59 |
sagara | just a wait | 08:59 |
*** chenying_ has joined #openstack-meeting | 08:59 | |
eranrom | takashi: ok, sure! | 08:59 |
sagara | I can join tomorrow meeting at same time. | 09:00 |
eranrom | sagara: greate thanks | 09:00 |
eranrom | I must end here. | 09:00 |
sagara | eranrom: thanks | 09:00 |
eranrom | Lets go to #openstack-storlets | 09:00 |
eranrom | #endmeeting | 09:00 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 09:00 | |
openstack | Meeting ended Tue Mar 14 09:00:37 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:00 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/storlets/2017/storlets.2017-03-14-08.00.html | 09:00 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/storlets/2017/storlets.2017-03-14-08.00.txt | 09:00 |
openstack | Log: http://eavesdrop.openstack.org/meetings/storlets/2017/storlets.2017-03-14-08.00.log.html | 09:00 |
yuval | #startmeeting karbor | 09:00 |
openstack | Meeting started Tue Mar 14 09:00:48 2017 UTC and is due to finish in 60 minutes. The chair is yuval. Information about MeetBot at http://wiki.debian.org/MeetBot. | 09:00 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 09:00 |
*** openstack changes topic to " (Meeting topic: karbor)" | 09:00 | |
openstack | The meeting name has been set to 'karbor' | 09:00 |
chenying_ | hi | 09:00 |
yuval | Hello, and welcome to Karbor's weekly meeting! | 09:00 |
*** abhishekk has left #openstack-meeting | 09:01 | |
zhangshuai | hi, all | 09:01 |
*** takashi has quit IRC | 09:01 | |
yuval | On the agenda today: finalizing the list of goals for Pike, including schedule | 09:01 |
*** r-mibu has joined #openstack-meeting | 09:01 | |
*** sagara has quit IRC | 09:01 | |
*** akihito has quit IRC | 09:02 | |
yuval | Let's wait 2 more minutes for people to arrive | 09:02 |
*** r-mibu has left #openstack-meeting | 09:02 | |
*** iceyao has quit IRC | 09:02 | |
yuval | chenying_: zhonghua, xiangxinyong, chenzeng, wu, chenhuayi are coming? | 09:05 |
chenying_ | yuval: waiting I will make a call. | 09:06 |
chenying_ | I am not at the office. | 09:06 |
*** zengchen has joined #openstack-meeting | 09:08 | |
zengchen | sorry, i'm late | 09:08 |
*** zhonghua has joined #openstack-meeting | 09:09 | |
*** mickeys has quit IRC | 09:09 | |
*** xiang123456 has joined #openstack-meeting | 09:09 | |
xiang123456 | hello | 09:09 |
zhonghua | hi | 09:09 |
yuval | what about chenhuayi? wu? | 09:10 |
zhonghua | he is sick | 09:10 |
zhonghua | AFAIK | 09:10 |
yuval | let's start | 09:10 |
*** markstur has joined #openstack-meeting | 09:10 | |
yuval | #topic Pike | 09:10 |
*** openstack changes topic to "Pike (Meeting topic: karbor)" | 09:10 | |
yuval | See the agenda and the link to the purposed final goals in https://wiki.openstack.org/wiki/Meetings/Karbor | 09:11 |
yuval | The Google document in the agenda includes a list of goals and schedule | 09:12 |
*** gongysh has joined #openstack-meeting | 09:12 | |
yuval | Besides specs and features, we should put heavy emphasize on deployment documentation | 09:13 |
yuval | Specifically plugin developer guides and API reference | 09:13 |
yuval | Does anyone has a suggestion about a missing feature, or priority for a listed goal? | 09:14 |
*** Cibo_ has quit IRC | 09:14 | |
*** phil_ has quit IRC | 09:15 | |
*** iceyao has joined #openstack-meeting | 09:15 | |
yuval | *have | 09:15 |
*** markstur has quit IRC | 09:15 | |
*** phil_ has joined #openstack-meeting | 09:15 | |
yuval | If you have, please burst in to say, I'll go over the high priority goals | 09:15 |
zhonghua | yuval, should we discuss the list one by one? | 09:15 |
yuval | I'll go over the important ones only | 09:15 |
chenying_ | Hi yuval suggest that write the agenda to openstack etherpad. Most of time the Google document is unavailable for us. | 09:16 |
*** manikanta_tadi has joined #openstack-meeting | 09:16 | |
yuval | Copied it here: https://etherpad.openstack.org/p/karbor-Pike-planning | 09:17 |
chenying_ | Ok Thanks. | 09:17 |
yuval | 1. release-with-intermediary | 09:18 |
*** guoshan has joined #openstack-meeting | 09:18 | |
yuval | We have adopted release-with-intermediary release model | 09:18 |
yuval | see https://releases.openstack.org/reference/release_models.html | 09:18 |
*** lhx__ has quit IRC | 09:19 | |
*** kaisers_ has joined #openstack-meeting | 09:19 | |
*** lhx__ has joined #openstack-meeting | 09:19 | |
yuval | this basically means that we have to release python-karborclient on time (over a month before the actual release) | 09:19 |
yuval | and we will have a feature freeze in karbor, about a month before the actual release | 09:20 |
yuval | so remembering new features in the last minute will not get inside Karbor. Plan accordingly | 09:20 |
yuval | questions? | 09:21 |
zhonghua | does that mean we should make a milestone plan | 09:21 |
zhonghua | ? | 09:21 |
yuval | We are not bound to milestones, but we should try to follow them as best we can. We must comply to the feature-freeze deadlines | 09:22 |
zhonghua | only FF? | 09:22 |
*** xiang123456 has quit IRC | 09:22 | |
yuval | This means that we should put very high effort on specs in the following 1-2 months, then high effort on features, then high effort on bugs in the last 1-2 months | 09:23 |
yuval | zhonghua: see here https://releases.openstack.org/pike/schedule.html | 09:23 |
zhonghua | ok | 09:24 |
zhonghua | thanks | 09:24 |
chenying_ | Bank indexing: about this goal, do we need intreoduce a new indexing component to karor in pike? | 09:24 |
yuval | chenying_: we will get to that in a minute | 09:24 |
yuval | I opened a milestone for pike in launchpad: https://launchpad.net/karbor/+milestone/pike-ms | 09:25 |
yuval | Please bookmark it. Specs and bugs for pike should be attached to it | 09:25 |
yuval | Important specs for Pike: | 09:25 |
yuval | We have the Tiramisu spec and implementation in Cinder, which is relevant to Karbor: | 09:26 |
*** lhx__ has quit IRC | 09:26 | |
yuval | https://review.openstack.org/229722 | 09:26 |
yuval | https://review.openstack.org/352228 | 09:26 |
yuval | https://review.openstack.org/352229 | 09:26 |
*** lhx__ has joined #openstack-meeting | 09:27 | |
*** lhx__ has quit IRC | 09:27 | |
*** lhx__ has joined #openstack-meeting | 09:28 | |
yuval | 2. Bank indexing spec - important spec about interface for indexing and querying checkpoints. The interface should provide a solution for single-site and multi-site scenarios | 09:28 |
yuval | chenying_: to your question: add the interface and reference implementation | 09:28 |
chenying_ | yuval single-site usecase, we can database bank. The Bank indexing may is not needed. | 09:29 |
yuval | chenying_: database can be used for the bank backend, but karbor currently doesn't have a index/query interface | 09:30 |
zhonghua | chenying_, +1 | 09:30 |
*** diablo_rojo has quit IRC | 09:30 | |
*** kota_ has left #openstack-meeting | 09:30 | |
*** Julien-zte has quit IRC | 09:30 | |
yuval | chenying_: by adding the index/query interface, we can use the database inherent indexing in single-site scenario | 09:30 |
chenying_ | yuval: IMO introduce a new project or component to karbor , it is too heavy and make it more complex for bank module. | 09:31 |
*** Julien-zte has joined #openstack-meeting | 09:31 | |
chenying_ | yuval IMO introduce a new project or component about indexing to karbor | 09:31 |
yuval | chenying_: there must be misunderstanding, as this is not about introducing a new project | 09:31 |
chenying_ | yuval a new project or component like searchlight | 09:32 |
zhonghua | yuval, Iam not sure is it neccessary to add this interface as a standard interface | 09:32 |
yuval | chenying_: as said, there is a misunderstanding, nobody said anything about adding a new project or component | 09:33 |
*** gongysh has quit IRC | 09:33 | |
*** zhhuabj has quit IRC | 09:33 | |
yuval | chenying_: we are speaking about karbor requirement to query checkpoints: by date, by plan, by metadata, etc | 09:33 |
yuval | this can be used by using database indexing, in single-site scenarios where database is used as a bank | 09:34 |
yuval | by indexing into a sqlite database in the bank itself | 09:34 |
yuval | or an external component | 09:34 |
*** abalutoiu_ has quit IRC | 09:34 | |
yuval | index/query will be part of the bank interface. we will provide a reference implmentation for sqlite indexing in the bank, and database indexing for database bank plugin | 09:35 |
*** manikanta_tadi has quit IRC | 09:35 | |
*** alexpilotti has joined #openstack-meeting | 09:36 | |
chenying_ | yuval I know, an external component will be intrduced about swift bank. Do we really add extra interface about indexing. In the usecase of database, the default query interface also support indexing by date, by plan, by metadata, etc | 09:37 |
*** alexpilo_ has quit IRC | 09:37 | |
yuval | chenying_: no, in the case of a object storage bank (e.g swift) we will provide an sqlite index which will reside in the bank itself. Anyone who will want to index the bank in an external component will have to write that for his bank plugin | 09:38 |
yuval | we are short on time, let's continue this specific discussion in karbor channel after meeting | 09:38 |
yuval | moving on to the next item | 09:38 |
chenying_ | OK | 09:38 |
yuval | Multi-Tenant Isolation spec | 09:39 |
*** alexchadin has quit IRC | 09:39 | |
yuval | very important spec about how to expose checkpoints to users without exposing them to unauthorized users | 09:39 |
yuval | this is relevant to single and multi site scenarios | 09:39 |
zhonghua | yuval, +1 | 09:40 |
yuval | this spec is very high priority | 09:40 |
*** esberglu has joined #openstack-meeting | 09:41 | |
yuval | last critical spec - removing heat | 09:42 |
yuval | Regarding documentation - zhonghua is working on getting us a technical writer to assist with documentation | 09:42 |
yuval | this is a critical part of the Pike release | 09:43 |
*** dbecker has joined #openstack-meeting | 09:43 | |
zhonghua | yuval, od you know is there any community team can help us | 09:43 |
zhonghua | do | 09:43 |
yuval | zhonghua: yes, I spoke with docs team in PTG. They will be able to assist in reviewing, but they will obviously not write the docs for us | 09:44 |
zhonghua | got it | 09:44 |
yuval | Questions? Suggestions? | 09:45 |
zhonghua | I will try to find the right guys | 09:45 |
*** esberglu has quit IRC | 09:45 | |
*** zhhuabj has joined #openstack-meeting | 09:45 | |
yuval | zhonghua: great | 09:46 |
yuval | #topic Open Discussion | 09:47 |
*** openstack changes topic to "Open Discussion (Meeting topic: karbor)" | 09:47 | |
yuval | zengchen: xiang12345: chenying_: zhangshuai: ? | 09:47 |
*** markstur has joined #openstack-meeting | 09:47 | |
*** diablo_rojo has joined #openstack-meeting | 09:48 | |
chenying_ | About the goal :Deployment | 09:48 |
yuval | ? | 09:48 |
yuval | anything specific? | 09:48 |
chenying_ | Do you have any suggestion about the tools or project which karbor should support. | 09:49 |
yuval | chenying_: we currently have Kolla, I think we should extend to OpenStack Ansible | 09:49 |
chenying_ | You know, There are many project or tools about openstack deployment. | 09:50 |
yuval | chenying_: RPM/DEB packages are a low hanging fruit IMO | 09:50 |
*** Julien-zte has quit IRC | 09:50 | |
chenying_ | yuval: Of course. | 09:51 |
*** Julien-zte has joined #openstack-meeting | 09:51 | |
*** kei_yama has joined #openstack-meeting | 09:51 | |
yuval | anything else? | 09:52 |
*** markstur has quit IRC | 09:52 | |
*** manikanta_tadi has joined #openstack-meeting | 09:54 | |
yuval | Thanks for attending, everybody! | 09:54 |
yuval | #endmeeting | 09:54 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 09:54 | |
openstack | Meeting ended Tue Mar 14 09:54:27 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:54 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-03-14-09.00.html | 09:54 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-03-14-09.00.txt | 09:54 |
openstack | Log: http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-03-14-09.00.log.html | 09:54 |
*** zhurong has quit IRC | 09:54 | |
*** lhx__ has quit IRC | 09:58 | |
*** kaisers_ has quit IRC | 09:59 | |
*** lhx__ has joined #openstack-meeting | 09:59 | |
*** zhonghua has quit IRC | 09:59 | |
*** phil_ has quit IRC | 09:59 | |
*** zhangshuai has left #openstack-meeting | 10:01 | |
*** nadya has quit IRC | 10:01 | |
*** Julien-zte has quit IRC | 10:03 | |
*** Julien-zte has joined #openstack-meeting | 10:04 | |
*** phil_ has joined #openstack-meeting | 10:05 | |
*** lennyb has quit IRC | 10:06 | |
*** Julien-zte has quit IRC | 10:07 | |
*** Julien-zte has joined #openstack-meeting | 10:07 | |
*** Julien-zte has quit IRC | 10:08 | |
*** Julien-zte has joined #openstack-meeting | 10:09 | |
*** Julien-zte has quit IRC | 10:10 | |
*** Julien-zte has joined #openstack-meeting | 10:11 | |
*** Julien-zte has quit IRC | 10:11 | |
*** gcb has quit IRC | 10:11 | |
*** lennyb has joined #openstack-meeting | 10:11 | |
*** dmorita has joined #openstack-meeting | 10:16 | |
*** kevinz has quit IRC | 10:17 | |
*** salv-orlando has quit IRC | 10:18 | |
*** Julien-zte has joined #openstack-meeting | 10:20 | |
*** dmorita has quit IRC | 10:21 | |
*** youzp has joined #openstack-meeting | 10:23 | |
*** kaisers_ has joined #openstack-meeting | 10:24 | |
*** markstur has joined #openstack-meeting | 10:24 | |
*** martinkopec has quit IRC | 10:26 | |
*** youzp has quit IRC | 10:28 | |
*** markstur has quit IRC | 10:29 | |
*** rabel__b1 has quit IRC | 10:31 | |
*** Raildo has joined #openstack-meeting | 10:31 | |
*** rabel__b1 has joined #openstack-meeting | 10:32 | |
*** chenying_ has quit IRC | 10:32 | |
*** chenying_ has joined #openstack-meeting | 10:32 | |
*** rabel_b1 has joined #openstack-meeting | 10:36 | |
*** rabel__b1 has quit IRC | 10:38 | |
*** jkilpatr has quit IRC | 10:39 | |
*** alexchadin has joined #openstack-meeting | 10:40 | |
*** dmorita has joined #openstack-meeting | 10:40 | |
*** trinaths has left #openstack-meeting | 10:42 | |
*** rbak_ has joined #openstack-meeting | 10:44 | |
*** abalutoiu has joined #openstack-meeting | 10:44 | |
*** dmorita has quit IRC | 10:45 | |
*** nadya has joined #openstack-meeting | 10:45 | |
*** salv-orlando has joined #openstack-meeting | 10:45 | |
*** salv-orl_ has joined #openstack-meeting | 10:46 | |
*** lpetrut has joined #openstack-meeting | 10:46 | |
*** rbak has quit IRC | 10:46 | |
*** askb has quit IRC | 10:46 | |
*** sdague has joined #openstack-meeting | 10:47 | |
*** askb has joined #openstack-meeting | 10:48 | |
*** shu-mutou is now known as shu-mutou-AWAY | 10:49 | |
*** salv-orlando has quit IRC | 10:49 | |
*** fzdarsky_ has quit IRC | 10:50 | |
*** salv-orl_ has quit IRC | 10:51 | |
*** pksingh has quit IRC | 10:51 | |
*** fzdarsky has joined #openstack-meeting | 10:51 | |
*** fzdarsky has quit IRC | 10:52 | |
*** fzdarsky has joined #openstack-meeting | 10:52 | |
*** fzdarsky has quit IRC | 10:53 | |
*** youzp has joined #openstack-meeting | 10:53 | |
*** fzdarsky has joined #openstack-meeting | 10:53 | |
*** swapnil-nilangek has quit IRC | 10:55 | |
*** kaisers_ has quit IRC | 10:56 | |
*** youzp has quit IRC | 10:58 | |
*** manikanta_tadi has quit IRC | 11:01 | |
*** markstur has joined #openstack-meeting | 11:01 | |
*** rabel_b1 has quit IRC | 11:03 | |
*** rabel has joined #openstack-meeting | 11:05 | |
*** markstur has quit IRC | 11:06 | |
*** Raildo is now known as raildo | 11:13 | |
*** abalutoiu has quit IRC | 11:15 | |
*** FengShengqin has quit IRC | 11:18 | |
*** jkilpatr has joined #openstack-meeting | 11:19 | |
*** guoshan has quit IRC | 11:21 | |
*** jkilpatr has quit IRC | 11:27 | |
*** yuval has quit IRC | 11:27 | |
*** youzp has joined #openstack-meeting | 11:28 | |
*** manikanta_tadi has joined #openstack-meeting | 11:28 | |
*** esberglu has joined #openstack-meeting | 11:29 | |
*** epico has quit IRC | 11:31 | |
*** aasthad has quit IRC | 11:32 | |
*** esberglu has quit IRC | 11:34 | |
*** links has quit IRC | 11:36 | |
*** IgorYozhikov has quit IRC | 11:36 | |
*** lhx__ has quit IRC | 11:37 | |
*** IgorYozhikov has joined #openstack-meeting | 11:37 | |
*** markstur has joined #openstack-meeting | 11:38 | |
*** fzdarsky is now known as fzdarsky|lunch | 11:38 | |
*** makowals_ has joined #openstack-meeting | 11:39 | |
*** jkilpatr has joined #openstack-meeting | 11:40 | |
*** makowals has quit IRC | 11:43 | |
*** markstur has quit IRC | 11:43 | |
*** makowals_ has quit IRC | 11:44 | |
*** links has joined #openstack-meeting | 11:48 | |
*** DFFlanders has quit IRC | 11:51 | |
*** kaisers_ has joined #openstack-meeting | 11:52 | |
*** dmorita has joined #openstack-meeting | 11:52 | |
*** Julien-zte has quit IRC | 11:55 | |
*** dmorita has quit IRC | 11:57 | |
*** askb has quit IRC | 12:01 | |
*** kevinz has joined #openstack-meeting | 12:03 | |
*** yuval has joined #openstack-meeting | 12:05 | |
*** nadya has quit IRC | 12:05 | |
*** yuval has quit IRC | 12:06 | |
*** kevinz has quit IRC | 12:07 | |
*** yuval has joined #openstack-meeting | 12:07 | |
*** aysyd has joined #openstack-meeting | 12:07 | |
*** nadya has joined #openstack-meeting | 12:10 | |
*** hashar is now known as hasharLunch | 12:12 | |
*** lhx__ has joined #openstack-meeting | 12:13 | |
*** janonymous has quit IRC | 12:14 | |
*** markstur has joined #openstack-meeting | 12:15 | |
*** markstur has quit IRC | 12:20 | |
*** yangyapeng has joined #openstack-meeting | 12:22 | |
*** ociuhandu has quit IRC | 12:22 | |
*** kevinz has joined #openstack-meeting | 12:22 | |
*** abalutoiu has joined #openstack-meeting | 12:26 | |
*** manikanta_tadi has quit IRC | 12:28 | |
*** rfolco has joined #openstack-meeting | 12:29 | |
*** yuval has quit IRC | 12:31 | |
*** yuval has joined #openstack-meeting | 12:31 | |
*** kaisers_ has quit IRC | 12:32 | |
*** nadya has quit IRC | 12:32 | |
*** makowals has joined #openstack-meeting | 12:32 | |
*** nadya has joined #openstack-meeting | 12:32 | |
*** gongysh has joined #openstack-meeting | 12:37 | |
*** efried has joined #openstack-meeting | 12:37 | |
*** lhx__ has quit IRC | 12:37 | |
*** csomerville has quit IRC | 12:41 | |
*** kei_yama has quit IRC | 12:43 | |
*** makowals_ has joined #openstack-meeting | 12:48 | |
*** rbak_ has quit IRC | 12:48 | |
*** rbak_ has joined #openstack-meeting | 12:48 | |
*** dprince has joined #openstack-meeting | 12:49 | |
*** makowals has quit IRC | 12:50 | |
*** gouthamr has joined #openstack-meeting | 12:51 | |
*** links has quit IRC | 12:52 | |
*** baoli has joined #openstack-meeting | 12:52 | |
*** markstur has joined #openstack-meeting | 12:52 | |
*** links has joined #openstack-meeting | 12:53 | |
*** amotoki has joined #openstack-meeting | 12:54 | |
*** baoli has quit IRC | 12:55 | |
*** baoli has joined #openstack-meeting | 12:56 | |
*** fzdarsky|lunch is now known as fzdarsky | 12:57 | |
*** markstur has quit IRC | 12:57 | |
*** abalutoiu has quit IRC | 12:57 | |
*** lamt has joined #openstack-meeting | 12:58 | |
*** elynn has joined #openstack-meeting | 12:58 | |
*** XueFeng has joined #openstack-meeting | 13:00 | |
*** yanyanhu_ has joined #openstack-meeting | 13:00 | |
*** baoli has quit IRC | 13:00 | |
yanyanhu_ | #startmeeting senlin | 13:00 |
openstack | Meeting started Tue Mar 14 13:00:42 2017 UTC and is due to finish in 60 minutes. The chair is yanyanhu_. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:00 |
Qiming | #startmeeting senlin | 13:00 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:00 |
*** openstack changes topic to " (Meeting topic: senlin)" | 13:00 | |
openstack | The meeting name has been set to 'senlin' | 13:00 |
openstack | Qiming: Error: Can't start another meeting, one is in progress. Use #endmeeting first. | 13:00 |
yanyanhu_ | oops | 13:00 |
elynn | oops | 13:01 |
*** Nagaraj has joined #openstack-meeting | 13:01 | |
XueFeng | :) | 13:01 |
Qiming | thanks yanyan | 13:01 |
yanyanhu_ | hi, Qiming, sorry a little bit later. the network is unstable, have to use vpn to connect | 13:01 |
yanyanhu_ | Qiming, please go ahead : ) | 13:01 |
Qiming | alright | 13:01 |
yanyanhu_ | my pleasure :) | 13:01 |
Qiming | meeting agenda posted | 13:01 |
Qiming | #link https://wiki.openstack.org/wiki/Meetings/SenlinAgenda#Weekly_Senlin_.28Clustering.29_meeting | 13:02 |
*** baoli has joined #openstack-meeting | 13:02 | |
Qiming | basically the things on the list is about work items update, pike goal tunings, summit pre | 13:02 |
Qiming | pls add items if any | 13:02 |
*** lamt has joined #openstack-meeting | 13:03 | |
*** Julien-zte has joined #openstack-meeting | 13:03 | |
Qiming | let's get started | 13:03 |
*** esberglu has joined #openstack-meeting | 13:03 | |
*** hoangcx has joined #openstack-meeting | 13:03 | |
Qiming | #topic pike work items | 13:03 |
Qiming | #link https://etherpad.openstack.org/p/senlin-pike-workitems | 13:03 |
*** gongysh has quit IRC | 13:03 | |
*** anilvenkata is now known as anilvenkata_afk | 13:04 | |
Qiming | api - profile_only | 13:04 |
*** Nagaraj has quit IRC | 13:04 | |
Qiming | 444100 is in now | 13:04 |
*** dmorita has joined #openstack-meeting | 13:04 | |
Qiming | API test just added: https://review.openstack.org/#/c/445298/ | 13:05 |
Qiming | found a serious bug in version negotiation | 13:05 |
Qiming | need more eyes on it | 13:05 |
Qiming | there could be similar bugs in other request objects | 13:06 |
XueFeng | which problme? | 13:06 |
XueFeng | problem | 13:06 |
Qiming | see the about patch: https://review.openstack.org/#/c/445298/ | 13:06 |
*** ociuhandu has joined #openstack-meeting | 13:06 | |
*** yanyanhu_ has quit IRC | 13:06 | |
XueFeng | ok | 13:06 |
*** yanyanhu_ has joined #openstack-meeting | 13:07 | |
Qiming | the obj_make_compatible is not deleting the primitive keys properly | 13:07 |
XueFeng | if 'profile_only' in primitive['senlin_object.data']: | 13:08 |
XueFeng | del primitive['senlin_object.data']['profile_only'] | 13:08 |
Qiming | right | 13:08 |
Qiming | moving on to next topic? | 13:08 |
XueFeng | move | 13:08 |
Qiming | feature rich nova server | 13:08 |
*** lakerzhou has quit IRC | 13:08 | |
elynn | I guess current patches are in now | 13:08 |
Qiming | both 438891 and 432587 are in | 13:09 |
yanyanhu_ | got merged this afternoon | 13:09 |
Qiming | let's see if there are more patches coming in | 13:09 |
elynn | Need some tuning and address Qiming's -1 :) | 13:09 |
elynn | I think it's done for now | 13:09 |
Qiming | you can leave those to your backport work | 13:09 |
*** dmorita has quit IRC | 13:09 | |
elynn | And I plan to move it to nova.server | 13:09 |
*** tobberyd_ has joined #openstack-meeting | 13:10 | |
elynn | piece by piece | 13:10 |
Qiming | I believe the top priority is to make it work | 13:10 |
yanyanhu_ | +1 | 13:10 |
elynn | Actually xinhui did a demo internal | 13:10 |
Qiming | and make sure the summit sessions are well prepared | 13:10 |
elynn | successfully | 13:10 |
elynn | Use this vdu profile together with monitor from vmware, to create a NFV scenario . | 13:11 |
*** nadya has quit IRC | 13:11 | |
*** markvoelker has quit IRC | 13:11 | |
Qiming | nice! | 13:11 |
Qiming | moving on | 13:11 |
Qiming | engine improvement -- cluster check | 13:12 |
XueFeng | no update this week | 13:12 |
Qiming | are we working on self-destroyable actions? | 13:12 |
Qiming | okay | 13:12 |
Qiming | node adopt | 13:12 |
*** lamt has quit IRC | 13:12 | |
XueFeng | prepare for the meetup 2017.3.18 | 13:12 |
*** tobberyd_ has quit IRC | 13:12 | |
Qiming | proposed a patch: | 13:12 |
Qiming | https://review.openstack.org/444817 | 13:13 |
*** tobberyd_ has joined #openstack-meeting | 13:13 | |
yanyanhu_ | great | 13:13 |
yanyanhu_ | this is what we are expecting | 13:13 |
Qiming | there are things very tricky | 13:13 |
*** tobberydberg has quit IRC | 13:13 | |
Qiming | personality | 13:13 |
Qiming | is an attribute you cannot get back from a server | 13:13 |
Qiming | networks, we cannot get the original request if it was created from port ids | 13:14 |
Qiming | and, port id, even extracted, doesn't seem that useful | 13:14 |
Qiming | with elynn's suggestion, I'm only extracting network name | 13:14 |
XueFeng | Yes | 13:15 |
Qiming | the worst thing is about user_data | 13:15 |
Qiming | we really need them back | 13:15 |
elynn | I always thought we can not get user_data... | 13:15 |
Qiming | nova api microversion 2.3 added this support | 13:15 |
elynn | Since I didn't find a rest API for it... | 13:15 |
Qiming | however, the attribute is renamed to OS-EXT-SRV-ATTR:user_data ... | 13:16 |
elynn | okay, good to know | 13:16 |
*** ayogi has quit IRC | 13:16 | |
yanyanhu_ | yes, user_data is important for further scaling operation | 13:16 |
Qiming | and it is limited to admin users, as of now | 13:16 |
*** markvoelker has joined #openstack-meeting | 13:16 | |
Qiming | talked to nova-api group, they are onto it. | 13:16 |
Qiming | they won't fix the name issue in near future, but they will fix the privilege restriction | 13:17 |
XueFeng | sounds good | 13:17 |
Qiming | from sdk side, brian came up with a hack: https://review.openstack.org/#/c/444933/ | 13:17 |
Qiming | it is not an easy choice to make | 13:17 |
Qiming | things are always complicated when we are talking about nova | 13:18 |
Qiming | until that is released, we cannot get user_data back | 13:18 |
*** claudiub has joined #openstack-meeting | 13:18 | |
Qiming | another todo is about creating snapshot when adopting a server node | 13:19 |
Qiming | this is made optional | 13:19 |
*** Ruijie has joined #openstack-meeting | 13:19 | |
Qiming | will need to work on profile level and then engine -> api -> sdk -> client path | 13:19 |
*** krtaylor has joined #openstack-meeting | 13:19 | |
Qiming | moving on | 13:19 |
Qiming | RDO | 13:19 |
XueFeng | ok | 13:20 |
XueFeng | sorry, this week rdo is also no update | 13:20 |
Qiming | okay, pls keep pushing | 13:20 |
Qiming | next, health management | 13:20 |
XueFeng | Will | 13:21 |
*** abalutoiu has joined #openstack-meeting | 13:21 | |
Qiming | xinhui is not in? | 13:21 |
yanyanhu_ | seems so | 13:21 |
yanyanhu_ | she has been back in last week | 13:21 |
*** kevinz has quit IRC | 13:21 | |
Qiming | alright, we have got a talk about enterprise monitoring + senlin + mistral | 13:21 |
Qiming | that story has to be made ready | 13:22 |
yanyanhu_ | yes, there is a presentation on it | 13:22 |
Qiming | maybe we should move fencing support back to TODO list? | 13:22 |
Qiming | it is not a trivial job | 13:22 |
yanyanhu_ | maybe another meet in vmware :P | 13:22 |
yanyanhu_ | for the summit preparation | 13:22 |
*** lakerzhou has joined #openstack-meeting | 13:23 | |
Qiming | em, xinhui called me the other day | 13:23 |
Qiming | talking about having senlin make placement decisions | 13:23 |
Qiming | because we are already there, with quite a few policies | 13:23 |
yanyanhu_ | agree | 13:24 |
yanyanhu_ | placement policy? | 13:24 |
Qiming | her question was about how to make it work with the new placement api from nova | 13:24 |
Qiming | I don't have a vision on that either | 13:24 |
elynn | Xinhui is busy recent days and she is sick.. | 13:24 |
Qiming | I'm not sure how the placement API is positioned, where it is heading | 13:24 |
*** prateek has quit IRC | 13:25 | |
yanyanhu_ | so nova has new api for advanced placement operations? | 13:25 |
yanyanhu_ | if so, that could be helpful | 13:25 |
Qiming | is it very ambitious to cover all aspects of placement decision? including network and storage factors? | 13:25 |
yanyanhu_ | sure | 13:25 |
yanyanhu_ | that is ambitious | 13:25 |
Qiming | or is it only about host resources and many also other multi-az, multi-region scheduling? | 13:26 |
yanyanhu_ | especially for network | 13:26 |
elynn | yanyanhu_, yes, nova has a placement API in nova codes now. | 13:26 |
Qiming | it is mandatory if an devstack installation now | 13:26 |
Qiming | anyway, let's see what will happen | 13:26 |
elynn | I guess recent days she will get more details of this requirement, and later we could figure out how we fit in this requirement. | 13:26 |
Qiming | at the same time, I really don't want to waste time duplicating features from another project | 13:27 |
*** kaisers_ has joined #openstack-meeting | 13:27 | |
Qiming | okay, so we can stick to our own agenda | 13:28 |
elynn | yes, we won't reinvent the wheels. | 13:28 |
Qiming | we have less than one month to release p-1 | 13:28 |
*** felipemonteiro has joined #openstack-meeting | 13:29 | |
yanyanhu_ | ... | 13:29 |
Qiming | +1 | 13:29 |
*** lakerzhou has quit IRC | 13:29 | |
XueFeng | Yes | 13:29 |
elynn | Just need to fill the gap. | 13:29 |
Qiming | we hope we can may operators life easier, not more painful | 13:29 |
*** rabel has quit IRC | 13:29 | |
Qiming | #link https://releases.openstack.org/pike/schedule.html | 13:29 |
*** markstur has joined #openstack-meeting | 13:30 | |
Qiming | moving on? | 13:30 |
yanyanhu_ | ok | 13:30 |
elynn | okay | 13:30 |
Qiming | I guess no progress on client functional tests? | 13:30 |
Qiming | though the gate job (non-voting) is ready | 13:30 |
XueFeng | Yes:) | 13:30 |
Qiming | okay | 13:30 |
Qiming | policy improvement, wrt LB policy and CLUSTER_RECOVER | 13:31 |
Ruijie | em, this can be removed .. | 13:31 |
Qiming | done? | 13:31 |
Qiming | or ... still some minor improvements needed? | 13:31 |
Ruijie | may need to improve the data | 13:32 |
*** artom has quit IRC | 13:32 | |
XueFeng | After meetup will do all things hard | 13:32 |
XueFeng | :) | 13:32 |
Qiming | okay, thx | 13:32 |
Ruijie | yes Qiming, still some improvements needed, will look forword to it | 13:32 |
Qiming | leaving that item there for a while | 13:33 |
Ruijie | okay | 13:33 |
*** kaisers_ has quit IRC | 13:33 | |
Qiming | NFV support is on the wishlist | 13:33 |
Qiming | got no news from Haiwei, although we have a talk on that | 13:33 |
Qiming | Xinhui's live demo is for that session, elynn ? | 13:33 |
elynn | For haiwei's session? | 13:34 |
*** markstur has quit IRC | 13:34 | |
elynn | No, xinhui's demo is for internal review. | 13:34 |
XueFeng | haiwei is busy, and he said he will do the patch in tacker | 13:34 |
elynn | But could do some modify and be prepare to other presentation. | 13:35 |
Qiming | okay | 13:35 |
Qiming | no matter what we are talking about | 13:35 |
XueFeng | And then we prepare for the session | 13:35 |
*** mriedem has joined #openstack-meeting | 13:35 | |
Qiming | it has to be in the master, for users to try out | 13:35 |
elynn | Cause it's not purely openstack, including some vmware software. But definitely for NFV. | 13:36 |
Qiming | okay, then the openstack part has to be ready | 13:36 |
Qiming | and possibly an alternative to vmware software as a generic solution would be great | 13:36 |
Qiming | there is nothing wrong to present vendor specific solution | 13:37 |
XueFeng | Yes, that will be great | 13:37 |
elynn | :) | 13:37 |
Qiming | but a generic one would be more useful to most audience | 13:37 |
elynn | We can find a day to let her show us again. | 13:37 |
Qiming | cool. | 13:37 |
elynn | Until she is not busy and recover from cough . | 13:38 |
Qiming | anything else on pike work items, the etherpad? | 13:38 |
yanyanhu_ | write a article for senlin[XueFeng Finished | 13:38 |
Qiming | I'm suffering too from coughing lately | 13:38 |
yanyanhu_ | great job from xuefeng | 13:38 |
Ruijie | +1 | 13:38 |
Qiming | would be nice if we have an English version, :) | 13:38 |
yanyanhu_ | Qiming, take a good rest | 13:39 |
Qiming | cannot reset, man | 13:39 |
yanyanhu_ | understand... | 13:39 |
yanyanhu_ | really busy recently | 13:39 |
XueFeng | So we need a English version? | 13:39 |
*** cdub has joined #openstack-meeting | 13:39 | |
Qiming | got some instructions to share your workload, just this afternoon | 13:39 |
yanyanhu_ | Qiming, yes, I also got the call... | 13:40 |
yanyanhu_ | need more discussion on it tomorrow | 13:40 |
Qiming | ok | 13:40 |
yanyanhu_ | you know, about the handover | 13:40 |
Qiming | okay | 13:40 |
yanyanhu_ | which will come soon | 13:40 |
Qiming | moving on | 13:40 |
elynn | handover what? | 13:40 |
Qiming | #topic pike goals | 13:40 |
XueFeng | QiMing | 13:40 |
yanyanhu_ | elynn, you will get it soon :P | 13:40 |
elynn | senlin? | 13:41 |
Qiming | we talked about this very briefly last week | 13:41 |
XueFeng | ironic container adoption health improve ;do some use cases | 13:41 |
elynn | okay...bless it's a good news | 13:41 |
XueFeng | My option in pike | 13:41 |
*** matrohon has quit IRC | 13:42 | |
Qiming | great. | 13:42 |
Qiming | more thoughts? | 13:42 |
XueFeng | container is hot now maybe | 13:42 |
Qiming | ironic has a bp, container is there for improvement, adoption is already started, health improvement needs update from xinhui | 13:43 |
XueFeng | Yes | 13:44 |
Qiming | XueFeng, when ironic support work has started, please help ensure it is tracked in the workitems etherpad | 13:44 |
*** matrohon has joined #openstack-meeting | 13:44 | |
yanyanhu_ | in my mind, both ha and container are very important. For HA, we need a practical use case, for container, we need deployment and orchestration support | 13:44 |
XueFeng | And maybe some stories container in baremetel | 13:44 |
yanyanhu_ | I mean something like k8s deployment(or at least something like compose) | 13:44 |
*** kevinz has joined #openstack-meeting | 13:44 | |
Qiming | container on baremetal would be next step when both components are stable | 13:44 |
*** knangia has joined #openstack-meeting | 13:44 | |
Qiming | right | 13:45 |
Qiming | I'm thinking of a cluster config property | 13:45 |
XueFeng | Ok | 13:45 |
Qiming | introducing yet another abstraction is gonna make things difficult to understand | 13:45 |
XueFeng | Recently, some guys put into zun, and I talk with them | 13:45 |
elynn | Agree with you, Qiming | 13:46 |
Qiming | zun is good if it can really make the container runtime easy to use/manage | 13:46 |
Qiming | still a lot of things to do in the HA space | 13:47 |
Qiming | more thoughts? | 13:47 |
XueFeng | And we need to let them know senlin and zun | 13:47 |
yanyanhu_ | yes, if it is reliable for managing container, will be really helpful | 13:47 |
XueFeng | Which is different | 13:47 |
Qiming | I think that team is aware of both projects' mission | 13:48 |
Qiming | I'd like to see closer integration happen earlier than later | 13:48 |
*** eharney has joined #openstack-meeting | 13:48 | |
XueFeng | So we can integrate zun+senlin | 13:48 |
XueFeng | Right? | 13:48 |
Qiming | why not? | 13:49 |
XueFeng | Yes | 13:49 |
Qiming | #topic boston summit prep | 13:49 |
*** electrofelix has joined #openstack-meeting | 13:49 | |
Qiming | I'm only included in one of the talks accepted, the senlin + mistral one | 13:50 |
Qiming | so that will be my top priority | 13:50 |
*** jlibosva has joined #openstack-meeting | 13:50 | |
Qiming | I believe xinhui is involved in all three talks? | 13:50 |
XueFeng | Yes | 13:50 |
Qiming | maybe she will be the best driver for this | 13:51 |
*** ataraday_ has joined #openstack-meeting | 13:51 | |
Qiming | will sync with her offline | 13:51 |
elynn | :) you add a lot work to her. | 13:51 |
Qiming | or better yet, online, when she stops by the #senlin channel | 13:51 |
XueFeng | congratulate senlin:accepted three sessions in bostion summit. | 13:51 |
Qiming | elynn, I think she enjoys driving things | 13:52 |
*** yanyanhu has joined #openstack-meeting | 13:52 | |
yanyanhu | sorry just dropped | 13:52 |
Qiming | or, she may want to offload that to you, elynn | 13:52 |
*** lakerzhou has joined #openstack-meeting | 13:52 | |
XueFeng | /s/bostion/boston | 13:52 |
elynn | Qiming, I believe what you say. | 13:52 |
Qiming | :D | 13:53 |
XueFeng | HaHa | 13:53 |
elynn | I will handle all trivial things :) | 13:53 |
*** iyamahat has joined #openstack-meeting | 13:53 | |
Qiming | alright, people need some believes, no matter what he/she is working on | 13:53 |
*** yanyanhu_ has quit IRC | 13:53 | |
Qiming | #topic open discussions | 13:53 |
*** matrohon has quit IRC | 13:54 | |
*** yanyanhu_ has joined #openstack-meeting | 13:54 | |
Qiming | since we cannot talk about talks without xinhui joining us | 13:54 |
*** john-davidge has joined #openstack-meeting | 13:54 | |
Qiming | moving on to open discussions | 13:54 |
elynn | Will you go to boston summit Qiming ? | 13:54 |
*** anilvenkata_afk is now known as anilvenkata | 13:55 | |
yanyanhu_ | what is the exact date of summit | 13:55 |
elynn | May 5-11 | 13:55 |
yanyanhu_ | May 08 - May 12 | 13:55 |
elynn | May 8-11 | 13:55 |
Qiming | https://review.openstack.org/#/c/445298/ | 13:55 |
*** matrohon has joined #openstack-meeting | 13:55 | |
Qiming | \o/ | 13:55 |
Qiming | I love pep8 errors | 13:55 |
yanyanhu_ | LoL | 13:56 |
elynn | :D | 13:56 |
*** trevormc has joined #openstack-meeting | 13:56 | |
XueFeng | :) | 13:56 |
Qiming | it took me almost 3 hours to narrow this down to a pep8 error, :) | 13:56 |
Qiming | anything else, gentlemen? | 13:57 |
yanyanhu_ | nope from me | 13:57 |
*** links has quit IRC | 13:57 | |
*** zhhuabj has quit IRC | 13:57 | |
elynn | no~ | 13:58 |
*** yanyanhu_ has quit IRC | 13:58 | |
*** mlavalle has joined #openstack-meeting | 13:58 | |
XueFeng | Hi all, I think container is important in pike cycle:) | 13:58 |
Qiming | thanks for joining, I have saved one minute for you, remember it | 13:58 |
Qiming | #endmeeting | 13:58 |
*** yanyanhu has quit IRC | 13:58 | |
*** XueFeng has quit IRC | 13:58 | |
*** Ruijie has quit IRC | 13:58 | |
Qiming | yanhan has to end the meeting | 13:58 |
*** janzian has joined #openstack-meeting | 13:59 | |
*** yanyanhu has joined #openstack-meeting | 13:59 | |
yanyanhu | network connection is terrible... | 13:59 |
yanyanhu | hi, Qiming, has the meeting finished? | 14:00 |
yanyanhu | if so, I will end the meeting | 14:00 |
yanyanhu | ok, seems so | 14:00 |
yanyanhu | #endmeeting | 14:00 |
*** annp has joined #openstack-meeting | 14:00 | |
*** jaugustine has joined #openstack-meeting | 14:01 | |
jlibosva | yanyanhu: maybe you need to rename to yanyanhu_ ? | 14:01 |
yanyanhu | #endmeeting | 14:01 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 14:01 | |
openstack | Meeting ended Tue Mar 14 14:01:39 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:01 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-03-14-13.00.html | 14:01 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-03-14-13.00.txt | 14:01 |
openstack | Log: http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-03-14-13.00.log.html | 14:01 |
yanyanhu | jlibosva, it's ok now :) | 14:01 |
jlibosva | ah :) thanks | 14:01 |
jlibosva | #startmeeting networking | 14:01 |
openstack | Meeting started Tue Mar 14 14:01:54 2017 UTC and is due to finish in 60 minutes. The chair is jlibosva. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:01 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:01 |
yanyanhu | looks like my network is poor :( | 14:01 |
*** openstack changes topic to " (Meeting topic: networking)" | 14:01 | |
openstack | The meeting name has been set to 'networking' | 14:01 |
yanyanhu | sorry for this | 14:02 |
mlavalle | o/ | 14:02 |
jlibosva | Hello friends! | 14:02 |
ataraday_ | hi | 14:02 |
*** huanxuan has quit IRC | 14:02 | |
amotoki | o/ | 14:02 |
bcafarel | hi | 14:02 |
john-davidge | o/ | 14:02 |
trevormc | o/ | 14:02 |
yamahata | hello | 14:02 |
dalvarez | o/ | 14:02 |
annp | Hi | 14:02 |
*** yanyanhu has quit IRC | 14:02 | |
jlibosva | #topic Announcements | 14:02 |
*** openstack changes topic to "Announcements (Meeting topic: networking)" | 14:02 | |
dasanind | hi | 14:02 |
dasm | o/ | 14:02 |
jlibosva | Seems like there are no new announcements on the wiki | 14:02 |
ajo | late o/ | 14:02 |
jlibosva | ttx sent out an email with information about Forum at the next OS summit, might be worth reading for those who plan to attend | 14:03 |
jlibosva | #link http://lists.openstack.org/pipermail/openstack-dev/2017-March/113459.html | 14:03 |
jlibosva | Also Emilien sent one to collect ideas about the format | 14:03 |
jlibosva | #link http://lists.openstack.org/pipermail/openstack-dev/2017-March/113115.html | 14:03 |
*** awaugama has joined #openstack-meeting | 14:03 | |
jlibosva | So that was about upcoming summit | 14:03 |
jlibosva | Regarding stadium | 14:04 |
jlibosva | ofagent is about to be retired | 14:04 |
*** dmacpher has joined #openstack-meeting | 14:04 | |
EmilienM | (let me know any question) | 14:04 |
jlibosva | :) | 14:04 |
jlibosva | #link https://review.openstack.org/#/c/441488/ | 14:04 |
jlibosva | That's all announcements from me, anybody has anything to announce? | 14:05 |
*** ihrachys has joined #openstack-meeting | 14:05 | |
jlibosva | Let's move on then | 14:05 |
jlibosva | #topic Blueprints | 14:05 |
*** openstack changes topic to "Blueprints (Meeting topic: networking)" | 14:05 | |
jlibosva | https://launchpad.net/neutron/+milestone/pike-1 | 14:06 |
*** mickeys has joined #openstack-meeting | 14:06 | |
jlibosva | We have 14 BP - Does anybody want to raise anything here? Is anybody blocked with his work? | 14:06 |
*** markstur has joined #openstack-meeting | 14:06 | |
jlibosva | Seems like we can jump to bugs then | 14:07 |
jlibosva | #topic Bugs and gate failures | 14:07 |
*** openstack changes topic to "Bugs and gate failures (Meeting topic: networking)" | 14:07 | |
jlibosva | There has been one critical bug around for a while | 14:08 |
jlibosva | this one https://bugs.launchpad.net/neutron/+bug/1627106 | 14:08 |
openstack | Launchpad bug 1627106 in neutron "TimeoutException while executing tests adding bridge using OVSDB native" [Critical,In progress] - Assigned to Terry Wilson (otherwiseguy) | 14:08 |
ihrachys | it's gone right? | 14:08 |
jlibosva | It looks like it would worth to get https://review.openstack.org/#/c/425623/ in | 14:08 |
ihrachys | I see functional is stable lately | 14:08 |
*** tonytan4ever has joined #openstack-meeting | 14:08 | |
jlibosva | yes, I was about to say that | 14:08 |
ihrachys | see http://grafana.openstack.org/dashboard/db/neutron-failure-rate?panelId=7&fullscreen | 14:08 |
ihrachys | ok | 14:08 |
jlibosva | but it seems the failure rate got down even before we merged terry's patch :) | 14:09 |
jlibosva | and there is still the patch ajo has ^^ | 14:09 |
ihrachys | did it? there were several fixes by otherwiseguy | 14:09 |
ajo | About the patch | 14:09 |
ajo | I'd like to talk with terry about it | 14:09 |
ajo | It was my understanding that that wasn't the timeout to tweak | 14:09 |
ajo | this tweaks the timeout of a request to ovsdb | 14:09 |
ajo | but | 14:09 |
*** tonytan4ever has quit IRC | 14:10 | |
ajo | it was some sort of low level heartbeat protocol timeout what I understood was timing out | 14:10 |
ajo | and dropping the connections | 14:10 |
ajo | abut I could have got it wrong | 14:10 |
ajo | ping otherwiseguy | 14:10 |
ajo | :) | 14:10 |
jlibosva | ajo: did you see his last comments on the patch? | 14:10 |
ajo | jlibosva in fact I didn't: reading | 14:10 |
*** tonytan4ever has joined #openstack-meeting | 14:10 | |
*** mickeys has quit IRC | 14:10 | |
ajo | ah | 14:10 |
ajo | :D | 14:10 |
*** ayogi has joined #openstack-meeting | 14:11 | |
ajo | so let's move forward | 14:11 |
jlibosva | so we should decide whether we want to get that in and eventually close the LP bug | 14:11 |
jlibosva | we can discuss on review or LP :) | 14:11 |
*** markstur has quit IRC | 14:11 | |
ajo | Is anything missing on my current patch? | 14:11 |
ajo | commit message ok | 14:11 |
jlibosva | ajo: ihrachys has -1 due to closing the bug | 14:12 |
ajo | jlibosva just published an edit, thanks :) | 14:12 |
jlibosva | ok, moving on | 14:12 |
jlibosva | thanks ajo :) | 14:12 |
jlibosva | Other than that, I don't see any critical bugs | 14:12 |
jlibosva | Bug deputy for last week was dasanind - he sent a report to ML, good job | 14:13 |
dasanind | jlibosva: thank you | 14:13 |
jlibosva | dasanind: oh, you're around, good :) Do you want to update here? | 14:13 |
dasanind | sure | 14:13 |
dasanind | there were approximately 25 bugs last week | 14:13 |
dasanind | I was unable to triage 2 of them :( | 14:14 |
dasanind | https://bugs.launchpad.net/neutron/+bug/1672345 | 14:14 |
openstack | Launchpad bug 1672345 in neutron "Loadbalancer V2 ports are not serviced by DVR" [Undecided,New] | 14:14 |
dasanind | https://bugs.launchpad.net/neutron/+bug/1672433 | 14:14 |
openstack | Launchpad bug 1672433 in neutron "dhcp-agent should send a grace ARP after assigning IP address in dhcp namespace" [Undecided,New] | 14:14 |
*** tmorin has joined #openstack-meeting | 14:14 | |
dasanind | In addition to these there were couple of RFEs | 14:14 |
ihrachys | the last one is quite interesting. seems like we may want to send garps for dhcp ports too. the use case is a bit blurry and debatable, but ping should work anyhow. | 14:15 |
dasanind | also there was an old bug https://bugs.launchpad.net/neutron/+bug/1629097 | 14:16 |
openstack | Launchpad bug 1629097 in neutron "neutron-rootwrap processes not getting cleaned up" [Undecided,Confirmed] | 14:16 |
*** boden has joined #openstack-meeting | 14:17 | |
dasanind | That's all I had for the bug deputy report :) | 14:17 |
jlibosva | dasanind: thanks for good work :) | 14:18 |
*** zz_dimtruck is now known as dimtruck | 14:18 | |
dasanind | jlibosva: thank you | 14:18 |
jlibosva | seems like the first one might be a duplicate, would be worth to get feedback from assignee of https://bugs.launchpad.net/neutron/+bug/1583694 to confirm | 14:18 |
openstack | Launchpad bug 1583694 in neutron "[RFE] DVR support for Allowed_address_pair port that are bound to multiple ACTIVE VM ports" [Wishlist,In progress] - Assigned to Swaminathan Vasudevan (swaminathan-vasudevan) | 14:18 |
jlibosva | anybody else has any other bug worth highlighting here? | 14:19 |
jlibosva | ok, moving on | 14:20 |
jlibosva | sindhu is bug deputy for this week | 14:20 |
jlibosva | and we need a volunteer for next week :) | 14:20 |
sindhu | jlibosva: yes :) | 14:21 |
ihrachys | I can do next | 14:21 |
jlibosva | ihrachys: thanks | 14:21 |
*** annp has quit IRC | 14:21 | |
jlibosva | #info ihrachys bug deputy for week Mar 20th | 14:21 |
jlibosva | #topic Docs | 14:22 |
*** openstack changes topic to "Docs (Meeting topic: networking)" | 14:22 | |
*** bzhao_ has joined #openstack-meeting | 14:22 | |
jlibosva | I saw john-davidge waving at the beginning of the meeting :) | 14:22 |
*** annp has joined #openstack-meeting | 14:22 | |
*** fnaval has joined #openstack-meeting | 14:22 | |
jlibosva | john-davidge: do you want to give any updates? | 14:22 |
*** jmckind has joined #openstack-meeting | 14:23 | |
jlibosva | ok, looks like he's not behind keyboard | 14:24 |
*** iceyao_ has joined #openstack-meeting | 14:24 | |
jlibosva | we can get back the topic after OSC if amotoki wants to give any updates? :) | 14:25 |
*** iceyao has quit IRC | 14:25 | |
amotoki | are we changing the topic? | 14:25 |
jlibosva | #topic Transition to OSC | 14:25 |
*** openstack changes topic to "Transition to OSC (Meeting topic: networking)" | 14:25 | |
jlibosva | yes :) | 14:25 |
amotoki | :) | 14:25 |
amotoki | no new patch landed last week related to neutron in OSC, but several patches are near to merge. | 14:26 |
*** hongbin has joined #openstack-meeting | 14:26 | |
*** reedip has joined #openstack-meeting | 14:26 | |
amotoki | it is a good news. | 14:26 |
amotoki | I have one thing to note. | 14:26 |
reedip | o/ | 14:27 |
amotoki | Filtering of OSC networking "list" commands does not work correctly due to the lack of openstacksdk support. | 14:27 |
*** alexchadin has quit IRC | 14:27 | |
amotoki | I will track the progress of the filtering feature later this week. | 14:27 |
amotoki | in addition to that, some patches to neutron OSC plugins are proposed reagridng stadium inclusion. | 14:28 |
amotoki | if you have some, add me to a reviewer. | 14:28 |
amotoki | that's all from me. | 14:28 |
ihrachys | re filtering, you mean users can't scope requests? | 14:29 |
*** kaisers_ has joined #openstack-meeting | 14:29 | |
amotoki | what i mean is like 'neutron port-list --network-id <net-id>' or something. | 14:29 |
jlibosva | amotoki: is there a LP bug for sdk? | 14:29 |
ihrachys | yeah. so everything always returned? | 14:29 |
amotoki | jlibosva: I am searching it..... | 14:29 |
amotoki | ihrachys: yeah, all are returned :( | 14:30 |
ihrachys | meh | 14:30 |
amotoki | openstack network list --external returns all :( | 14:30 |
hoangcx | "neutron OSC plugins are proposed reagridng stadium inclusion" => https://review.openstack.org/#/c/439978/ | 14:30 |
amotoki | hoangcx: VPNaaS is one of them | 14:30 |
*** Leo_ has joined #openstack-meeting | 14:31 | |
hoangcx | amotoki, yes. Thank you for your review | 14:31 |
reedip | amotoki : added :) | 14:31 |
*** eharney_ has joined #openstack-meeting | 14:32 | |
*** longxiongqiu has quit IRC | 14:32 | |
amotoki | does anyone know octavia folks are implementing their OSC plugin? If not I will ask them | 14:32 |
dasm | amotoki: i think some work is going on, thanks to sindhu and ankur-gupta-f1 | 14:32 |
*** eharney has quit IRC | 14:33 | |
amotoki | dasm: thanks. I was not aware of it. | 14:33 |
*** bobh has joined #openstack-meeting | 14:34 | |
amotoki | if nothing, let's move on | 14:34 |
jlibosva | amotoki: ok, thanks for updates | 14:35 |
dasm | amotoki: i've double checked. sindhu didn't start her work, but ankur-gupta-f1 has something,. they still waiting for v2 for octavia | 14:35 |
bzhao | amotoki, no, I found nothing. And last meeting of ocavia, there is nothing about osc.. | 14:35 |
*** eharney_ is now known as eharney | 14:35 | |
reedip | amotoki : ankur posted a patch for octavia | 14:36 |
reedip | oh , just saw the other messages, thanks dasm | 14:36 |
amotoki | okay, it looks better to sync their plan on CLI on the progress with octavia. thanks for the input. | 14:36 |
amotoki | plan and progress. | 14:36 |
dasm | amotoki: https://review.openstack.org/#/c/428414/ | 14:37 |
jlibosva | #link https://review.openstack.org/#/c/439978/ | 14:37 |
jlibosva | #link https://review.openstack.org/#/c/428414/ | 14:37 |
*** lamt has joined #openstack-meeting | 14:37 | |
jlibosva | amotoki: re openstacksdk bug - is network the only resource that can't be filtered? | 14:38 |
*** markstur has joined #openstack-meeting | 14:38 | |
amotoki | jlibosva: I think no. I haven't checked all, but the comment says it does not support query.... | 14:39 |
youzp | #topic specs | 14:39 |
jlibosva | so it sounds to me that not only Neutron might be affected | 14:40 |
*** swapnil-nilangek has joined #openstack-meeting | 14:40 | |
jlibosva | ok, thanks all for osc updates | 14:40 |
ankur-gupta-f4 | Sorry im late :( | 14:40 |
amotoki | you're welcome. | 14:40 |
jlibosva | let's move to neutron-lib unless there is still something related to osc to discuss | 14:40 |
boden | hi, I can provide a quick neutron-lib summary if we’re done with OSC | 14:41 |
jlibosva | #topic Neutron-lib and planned neutron refactoring | 14:41 |
*** openstack changes topic to "Neutron-lib and planned neutron refactoring (Meeting topic: networking)" | 14:41 | |
john-davidge | jlibosva: Sorry about that, had to step away from keyboard for a few minutes | 14:41 |
jlibosva | boden: thanks:) go ahead | 14:41 |
jlibosva | john-davidge: no problem, we can get back Docs after neutron-lib, if that's fine | 14:42 |
john-davidge | jlibosva: Sure :) | 14:42 |
*** youzp has quit IRC | 14:42 | |
boden | last week we discussed a new lib release.. we have a release patch proposed https://review.openstack.org/#/c/445483/ | 14:42 |
boden | as noted; there are 2 other patches I was hoping we could pick up for the release; so hopefully we can close on those in the next day or few | 14:42 |
ihrachys | boden: no links to patches | 14:43 |
ihrachys | oh there is one | 14:43 |
ihrachys | not another though | 14:43 |
*** markstur has quit IRC | 14:43 | |
*** lakerzhou has left #openstack-meeting | 14:43 | |
boden | ihrachys: yes the other is still under dev in my workspace | 14:43 |
boden | if we need a release of lib today; we can go ahead without them, but if no rush it would be helpful to wait | 14:44 |
jlibosva | #link https://review.openstack.org/#/c/442763/ | 14:44 |
jlibosva | #link https://review.openstack.org/#/c/445483 | 14:44 |
ihrachys | boden: is it something user visible? | 14:45 |
ihrachys | because e.g. doc update does not merit a release blocker | 14:45 |
*** davidsha has joined #openstack-meeting | 14:45 | |
boden | ihrachys: true, but it clarifies our pep8/hacking check process which will now be “live” for all consumers | 14:45 |
boden | is there a rush to release lib, are people waiting on something in the release? | 14:46 |
amotoki | i think docs.o.o/developer/neutron-lib is published from the released version. | 14:46 |
amotoki | woops... i am wrong.. | 14:46 |
dasm | amotoki: nope. it's published with every change | 14:47 |
ihrachys | not me, I don't wait on it, but would be nice to get e.g. callbacks earlier | 14:47 |
boden | ihrachys: the patch I’m working on and would like to get in makes neutron-lib api-def consumption work… but again it could wait for the next release if needed | 14:49 |
boden | in any case; we can move forward with the release with or without my patches… last time checked the periodic gate was green | 14:49 |
dasm | ditto. both neutron-lib and neutron periodics are green | 14:50 |
jlibosva | Maybe we can discuss on the docs update in 445483 change? | 14:50 |
boden | sure | 14:50 |
ihrachys | + | 14:50 |
boden | that’s all I have for lib | 14:50 |
jlibosva | boden: alright, thanks for update and bringing up the discussion | 14:50 |
jlibosva | #topic Docs | 14:50 |
*** openstack changes topic to "Docs (Meeting topic: networking)" | 14:50 | |
jlibosva | john-davidge: hi :) | 14:50 |
john-davidge | jlibosva: Hi | 14:50 |
*** makowals_ has quit IRC | 14:51 | |
john-davidge | We had a large number of patches merge for the RFC 5737 fix this week. Thanks especially to caoyuan for the chnages | 14:51 |
*** iyamahat has quit IRC | 14:52 | |
john-davidge | There is also a lot of activity on moving documented neutron client commands to OSC. I'd like to remind contributors to make sure the output is being updated as well as the input where neccessary. | 14:52 |
*** electrocucaracha has joined #openstack-meeting | 14:53 | |
john-davidge | Those are the only major points from me this week, thanks | 14:53 |
jlibosva | john-davidge: thanks! | 14:53 |
*** galstrom_zzz is now known as galstrom | 14:53 | |
jlibosva | any comments anybody for docs? | 14:53 |
*** longxiongqiu has joined #openstack-meeting | 14:54 | |
jlibosva | ok, moving to open discussion, we have 5 mins | 14:54 |
jlibosva | #topic Open discussion | 14:54 |
*** openstack changes topic to "Open discussion (Meeting topic: networking)" | 14:54 | |
annp | Hi jlibosva and everyone | 14:54 |
jlibosva | There are no new topics in On Demand Agenda | 14:54 |
jlibosva | annp: hi :) | 14:55 |
annp | We have updated logging api spec (#link https://review.openstack.org/#/c/203509) and also uploaded our implementation for OVS firewall driver logging (#link https://review.openstack.org/#/c/396104/). | 14:55 |
annp | Could you please take a look on this and leave your comments? | 14:55 |
annp | Thank you :) | 14:55 |
*** artom has joined #openstack-meeting | 14:55 | |
ihrachys | the prev drivers meeting, we discussed that a tad, and I think the only thing to decide is whether we want to wait for ml2 framework for binding validation before allowing that in | 14:55 |
jlibosva | I promised at PTG that I'm gonna have a look :) | 14:56 |
ihrachys | kevinbenton was for not waiting, but wanted to check with rkukura first | 14:56 |
annp | jlibosva: Thanks :) | 14:56 |
ihrachys | I think we should have some go-decision this week | 14:56 |
jlibosva | ihrachys: the drivers meeting is on Thu? | 14:57 |
ihrachys | yes | 14:57 |
ihrachys | log: http://eavesdrop.openstack.org/meetings/neutron_drivers/2017/neutron_drivers.2017-03-09-22.00.log.html | 14:57 |
ihrachys | 22:09:53+ | 14:57 |
*** elynn has left #openstack-meeting | 14:57 | |
ihrachys | in unrelated news, would be nice to see progress on https://review.openstack.org/#/q/topic:new-neutron-devstack-in-gate | 14:58 |
ihrachys | some bits are devstack controlled so not much we can do, but there are some small bits on neutron side | 14:58 |
ihrachys | so reviews welcome | 14:58 |
*** kevinz has quit IRC | 14:58 | |
jlibosva | annp: thanks for bringing up the SG logging API - seems like it's on radar | 14:59 |
annp | ihrachys: I got it. thanks for your information. | 14:59 |
john-davidge | ihrachys: Any movement on approval of https://bugs.launchpad.net/neutron/+bug/1667329 in drivers meeting? | 14:59 |
openstack | Launchpad bug 1667329 in neutron "[RFE] Floating IP Subnets on Routed Provider Networks" [Undecided,Triaged] | 14:59 |
jlibosva | ihrachys: thanks for the link - I'll try to go through the open changes | 14:59 |
ihrachys | john-davidge: it was not discussed | 14:59 |
*** kaisers_ has quit IRC | 14:59 | |
john-davidge | ihrachys: Ok, thanks | 15:00 |
jlibosva | we're out of time | 15:00 |
jlibosva | thanks everybody for showing up :) | 15:00 |
dasanind | thanks | 15:00 |
*** iyamahat has joined #openstack-meeting | 15:00 | |
*** prateek has joined #openstack-meeting | 15:00 | |
jlibosva | #endmeeting | 15:00 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 15:00 | |
openstack | Meeting ended Tue Mar 14 15:00:19 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:00 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/networking/2017/networking.2017-03-14-14.01.html | 15:00 |
*** slaweq has joined #openstack-meeting | 15:00 | |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/networking/2017/networking.2017-03-14-14.01.txt | 15:00 |
openstack | Log: http://eavesdrop.openstack.org/meetings/networking/2017/networking.2017-03-14-14.01.log.html | 15:00 |
mlavalle | Thanks | 15:00 |
annp | thanks | 15:00 |
ralonsoh | ... and hello to QoS | 15:00 |
ralonsoh | #startmeeting neutron_qos | 15:00 |
openstack | Meeting started Tue Mar 14 15:00:54 2017 UTC and is due to finish in 60 minutes. The chair is ralonsoh. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:00 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
*** openstack changes topic to " (Meeting topic: neutron_qos)" | 15:00 | |
openstack | The meeting name has been set to 'neutron_qos' | 15:00 |
ralonsoh | Hi | 15:01 |
slaweq | hello | 15:01 |
*** electrocucaracha has left #openstack-meeting | 15:01 | |
davidsha | Hi | 15:01 |
*** ayogi has quit IRC | 15:01 | |
*** tobberyd_ has quit IRC | 15:01 | |
*** janzian has left #openstack-meeting | 15:01 | |
ralonsoh | let's wait 30 secs | 15:01 |
*** tobberydberg has joined #openstack-meeting | 15:01 | |
slaweq | ok, 1..2..3.. :P | 15:01 |
ralonsoh | #topic RFEs | 15:01 |
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)" | 15:01 | |
ralonsoh | let's go | 15:01 |
*** jlibosva has left #openstack-meeting | 15:02 | |
ralonsoh | the first one | 15:02 |
ralonsoh | #link https://bugs.launchpad.net/neutron/+bug/1657089 | 15:02 |
openstack | Launchpad bug 1657089 in neutron "[RFE]Add bandwidth_limit to vip" [Undecided,New] | 15:02 |
ralonsoh | a new one | 15:02 |
*** markstur has joined #openstack-meeting | 15:02 | |
reedip | nice transition | 15:02 |
betherly | o/ | 15:02 |
*** tobberydberg has quit IRC | 15:02 | |
ralonsoh | not assigned, but should be in the whislist | 15:02 |
ralonsoh | I mean, there are other features to be implemented in QoS | 15:03 |
ralonsoh | for example, QoS on FIP | 15:03 |
*** tobberydberg has joined #openstack-meeting | 15:03 | |
ralonsoh | I'll ping ajo to set this to low priority | 15:03 |
*** cody-somerville has joined #openstack-meeting | 15:03 | |
ralonsoh | next one | 15:03 |
ralonsoh | #link https://bugs.launchpad.net/neutron/+bug/1505627 | 15:03 |
openstack | Launchpad bug 1505627 in neutron "[RFE] QoS Explicit Congestion Notification (ECN) Support" [Wishlist,Incomplete] - Assigned to Reedip (reedip-banerjee) | 15:03 |
ralonsoh | reedip? | 15:03 |
*** m1dev has joined #openstack-meeting | 15:03 | |
*** tobberydberg has quit IRC | 15:04 | |
ajo | hi ralonsoh , betherly , slaweq , reedip :) o/ (sorry to be late) | 15:04 |
*** tobberydberg has joined #openstack-meeting | 15:04 | |
ralonsoh | ajo: np! | 15:04 |
davidsha | np | 15:04 |
ralonsoh | reedip: any update on this one? | 15:04 |
slaweq | hello ajo | 15:04 |
reedip | ralonsoh : awaiting review on the etherpad from you guys. I have created the environment, would be testing for qrouter and update you with the results soon | 15:04 |
ralonsoh | perfect! | 15:04 |
*** armax has joined #openstack-meeting | 15:04 | |
ralonsoh | as soon as you have patches, ping us to review them | 15:05 |
davidsha | reedip: this is the etherpad right? https://etherpad.openstack.org/p/QoS_ECN | 15:05 |
reedip | ralonsoh : ok, I will draft the spec now, I guess it would be better to get it in for now... else it would always be in the nascent stage | 15:05 |
reedip | davidsha yeah | 15:05 |
ralonsoh | reedip: ok, yes | 15:06 |
davidsha | reedip: cool. | 15:06 |
ralonsoh | reedip: I need to take a second look and make some comments | 15:06 |
ralonsoh | next one | 15:06 |
ralonsoh | #link https://bugs.launchpad.net/neutron/+bug/1596611 | 15:06 |
openstack | Launchpad bug 1596611 in neutron "[RFE] Create L3 IPs with qos (rate limit)" [Wishlist,In progress] - Assigned to LIU Yulong (dragon889) | 15:06 |
*** aasthad has joined #openstack-meeting | 15:06 | |
ralonsoh | my main concern with this one: to make it compatible with current qos implementation | 15:07 |
*** tobberydberg has quit IRC | 15:07 | |
ralonsoh | the spec in under review | 15:07 |
*** tobberydberg has joined #openstack-meeting | 15:07 | |
ralonsoh | one sec | 15:07 |
ralonsoh | I don't find the spec now | 15:08 |
davidsha | https://review.openstack.org/#/c/374506/ | 15:08 |
ralonsoh | #link https://review.openstack.org/#/c/374506/ | 15:08 |
ralonsoh | Yes, thanks | 15:09 |
ralonsoh | is LIU here? | 15:09 |
*** matrohon has quit IRC | 15:09 | |
davidsha | Is dragon889 his irc? | 15:09 |
ralonsoh | I don't know.... | 15:09 |
ralonsoh | OK, please continue with the reviews. I'll try to ping him | 15:10 |
ralonsoh | next one | 15:10 |
ralonsoh | https://bugs.launchpad.net/neutron/+bug/1639220 | 15:10 |
openstack | Launchpad bug 1639220 in neutron "[RFE] Introduce Network QoS policy "is_default" behaviour" [Low,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez) | 15:10 |
ralonsoh | ajo: I need you to answer to Ihar and me | 15:11 |
ralonsoh | in launchpad | 15:11 |
ajo | oh, let me check | 15:11 |
ralonsoh | thanks | 15:11 |
ralonsoh | ok, let's move to bugs | 15:12 |
ralonsoh | #topic Bugs | 15:12 |
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)" | 15:12 | |
ralonsoh | #link https://bugs.launchpad.net/neutron/+bug/1669430 | 15:12 |
openstack | Launchpad bug 1669430 in neutron "Deprecation warning in Neutron QoSDSCPMarkingRule functional tests" [Low,In progress] | 15:12 |
ajo | I'll answer on LP I need to think :D | 15:12 |
*** john-davidge has quit IRC | 15:12 | |
ralonsoh | ajo: np, and thanks! | 15:12 |
*** matrohon has joined #openstack-meeting | 15:12 | |
*** jaugustine has quit IRC | 15:13 | |
ralonsoh | this bug should be closed because is addressed by https://review.openstack.org/#/c/438148 | 15:13 |
ralonsoh | as soon as the patch is merged | 15:13 |
ralonsoh | actually, I don't think this is a QoS problem | 15:13 |
reedip | ralonsoh : -1 Add related bug or partially closes :) | 15:14 |
ralonsoh | ok, but we should remove qos tag | 15:14 |
*** tobberydberg has quit IRC | 15:14 | |
ralonsoh | is not related | 15:14 |
*** tobberydberg has joined #openstack-meeting | 15:14 | |
davidsha | ralonsoh: Sorry, saw it in a functional test for a patch I was reviewing! | 15:14 |
reedip | ralonsoh : if this bug is being closed by the above patch, some sort of indication needs to be given, isnt it | 15:15 |
*** jaugustine has joined #openstack-meeting | 15:15 | |
ralonsoh | reedip: you are right | 15:15 |
*** iceyao has joined #openstack-meeting | 15:15 | |
ralonsoh | davidsha: can you take this one? | 15:15 |
*** tobberydberg has quit IRC | 15:15 | |
davidsha | ralonsoh: Sure. | 15:16 |
ralonsoh | davidsha: just follow it properly | 15:16 |
ralonsoh | perfect | 15:16 |
*** tobberydberg has joined #openstack-meeting | 15:16 | |
ralonsoh | next one | 15:16 |
ralonsoh | #link https://bugs.launchpad.net/neutron/+bug/1667138 | 15:16 |
openstack | Launchpad bug 1667138 in neutron "Minumum bandwidth can be higher than maximum bandwidth limit in same QoS policy" [Medium,In progress] - Assigned to Reedip (reedip-banerjee) | 15:16 |
ralonsoh | reedip: how is going? | 15:16 |
reedip | aah , I will push this patch in another hour.... | 15:16 |
reedip | test cases pending | 15:17 |
slaweq | for me it looks fine now | 15:17 |
slaweq | but needs tests still | 15:17 |
reedip | yeah slaweq :) | 15:17 |
ralonsoh | https://review.openstack.org/#/c/442375/: we will follow the patch | 15:17 |
ralonsoh | reedip: thank you for taking care of it | 15:17 |
ralonsoh | next one | 15:18 |
ralonsoh | #link https://bugs.launchpad.net/neutron/+bug/1663908 | 15:18 |
openstack | Launchpad bug 1663908 in neutron "Qos rules not cleaned by L2 agent" [Undecided,New] - Assigned to David Shaughnessy (david-shaughnessy) | 15:18 |
reedip | ralonsoh : naah , just doing my job | 15:18 |
ralonsoh | davidsha: how is going? | 15:18 |
*** rbartal has quit IRC | 15:18 | |
davidsha | ralonsoh: I was looking into it, wanted to ask slaweq a few question. I'll follow up after the meeting | 15:19 |
*** iceyao_ has quit IRC | 15:19 | |
slaweq | davidsha: ok, no problem :) | 15:19 |
ralonsoh | perfect, and thanks | 15:19 |
ralonsoh | next one | 15:19 |
ralonsoh | #link https://bugs.launchpad.net/neutron/+bug/1662109 | 15:19 |
openstack | Launchpad bug 1662109 in neutron "tempest scenario test_qos fails intermittently" [High,Confirmed] - Assigned to Miguel Angel Ajo (mangelajo) | 15:19 |
*** andreas_s has quit IRC | 15:20 | |
ralonsoh | this one is problematic... | 15:20 |
ajo | yup it is | 15:20 |
ajo | the test is disabled | 15:20 |
ralonsoh | yes... and there is no solution or clue about the problem? | 15:20 |
ajo | as far as I could understand, the issue we have is that somehow, the agent doesn't realize that a port has been updated to have a policy | 15:20 |
ajo | either because the notification about port update doesn't arrive under some condition | 15:20 |
*** hoangcx has quit IRC | 15:21 | |
ajo | or because it talks back to neutron, and the policy isn't there? | 15:21 |
ajo | I couldn't identify the exact root cause | 15:21 |
ajo | but | 15:21 |
ajo | I could see how the policy was created, and attached to port | 15:21 |
ajo | and agent never sees the port being updated with the policy | 15:21 |
ajo | hance, the rule is not applied | 15:21 |
ralonsoh | a rpc problem? | 15:22 |
ajo | I should probably unassign the bug from myself if anybody else has bw to look at it | 15:22 |
ajo | there were changes recently on the ML2 plugin | 15:22 |
ajo | for port_updates | 15:22 |
ajo | and notifications | 15:22 |
ajo | may be it's related to that | 15:22 |
ajo | basically, we check wether the policy_id changed, and hence trigger the update | 15:22 |
ajo | let me grab a link | 15:22 |
ralonsoh | ok | 15:22 |
ajo | https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/plugin.py#L1207 | 15:23 |
*** xyang1 has joined #openstack-meeting | 15:23 | |
ajo | just look for qos_policy_id in that file, same thing for network policies | 15:23 |
*** hasharLunch is now known as hashar | 15:24 | |
ralonsoh | now I don't have time to take a look at this bug | 15:24 |
ralonsoh | bt | 15:24 |
ralonsoh | but | 15:24 |
ralonsoh | in two weeks I'll have more time | 15:25 |
ralonsoh | ajo: so if you need help, ping me | 15:25 |
ralonsoh | ok, next one | 15:25 |
ralonsoh | #link https://bugs.launchpad.net/neutron/+bug/1659265 | 15:25 |
openstack | Launchpad bug 1659265 in neutron "Network level QoS policies should apply to network:router_gateway" [Wishlist,In progress] - Assigned to Maxime (maxime-guyot-p) | 15:25 |
ralonsoh | this one is under review | 15:26 |
ralonsoh | IMO, the logic implemented is not correct | 15:26 |
*** raj_singh_ has quit IRC | 15:26 | |
ralonsoh | one sec | 15:26 |
ralonsoh | https://review.openstack.org/#/c/425218/11/neutron/tests/unit/objects/qos/test_rule.py | 15:26 |
ralonsoh | This logic allows a net qos policy to override a port qos policy | 15:27 |
ralonsoh | reviews to this patch are welcome | 15:27 |
slaweq | ralonsoh: I will check it today | 15:27 |
ralonsoh | thanks | 15:27 |
ralonsoh | next one | 15:27 |
ralonsoh | #link https://bugs.launchpad.net/neutron/+bug/1657381 | 15:27 |
openstack | Launchpad bug 1657381 in neutron "QoS drivers need to implement a precommit for the actions" [Medium,In progress] - Assigned to Miguel Angel Ajo (mangelajo) | 15:27 |
ralonsoh | ajo restarted this one | 15:28 |
ajo | right | 15:28 |
ajo | I had a talk on summit with the ODL people | 15:28 |
ajo | and they explained me that they had some synchronization constraints in the way the implement things | 15:28 |
ajo | and they don't need to stop a transaction | 15:28 |
ajo | but need a log entry in their journal before DB change is commited | 15:28 |
ajo | I can't remember all the details now, but it made sense at that time :] | 15:29 |
ajo | manjeets could probably explain it again if necessary | 15:29 |
ralonsoh | perfect: now all extensions will have the qos service extended with this new events | 15:29 |
*** ociuhandu has quit IRC | 15:29 | |
ajo | btw, I need to leave, I'll read the log later | 15:29 |
reedip | ajo : its basically how the newtorking-odl's v2 driver is created | 15:29 |
ralonsoh | see you! | 15:29 |
*** mtanino has quit IRC | 15:29 | |
ajo | thank you folks | 15:30 |
reedip | it needs both pre-commit and post-commit behavior | 15:30 |
davidsha | thanks, see ya | 15:30 |
ralonsoh | now ajo needs to write the tests in this patch | 15:30 |
ralonsoh | ok, last one | 15:30 |
ralonsoh | #link https://bugs.launchpad.net/neutron/+bug/1649503 | 15:30 |
openstack | Launchpad bug 1649503 in neutron "Mechanism driver can't be notified with updated network" [High,In progress] - Assigned to Hong Hui Xiao (xiaohhui) | 15:30 |
ralonsoh | it has high importance | 15:31 |
ralonsoh | and it's stopped | 15:31 |
ralonsoh | today i'll ping the author. If there is no answer, I'll take this one | 15:31 |
ralonsoh | or anyone here, of course | 15:31 |
slaweq | it's waiting for kevinbenton opinion AFAIR | 15:31 |
ralonsoh | no no | 15:31 |
ralonsoh | look at this: https://review.openstack.org/#/c/410101/ | 15:32 |
slaweq | ralonsoh: yes, and there is comment from armax | 15:32 |
ralonsoh | and there is no activity in launchpad | 15:32 |
slaweq | that maybe kevinbenton has a better suggestion | 15:32 |
slaweq | :) | 15:32 |
ralonsoh | I'll try to re-activate this patch and, eventually, I'll take care of it | 15:33 |
slaweq | k | 15:33 |
ralonsoh | if you don't mind, of course | 15:33 |
slaweq | me, no :) | 15:33 |
ralonsoh | hehehe | 15:33 |
ralonsoh | ok, next topic | 15:33 |
ralonsoh | sorry | 15:33 |
ralonsoh | any other hidden bug? | 15:34 |
slaweq | bugs no | 15:34 |
slaweq | but I think You forgot earlier about https://bugs.launchpad.net/neutron/+bug/1586056 | 15:34 |
openstack | Launchpad bug 1586056 in neutron "[RFE] Improved validation mechanism for QoS rules with port types" [Wishlist,In progress] - Assigned to Slawek Kaplonski (slaweq) | 15:34 |
slaweq | :) | 15:34 |
slaweq | or I missed it | 15:34 |
ralonsoh | yes!! | 15:34 |
ralonsoh | no no | 15:34 |
ralonsoh | you are right | 15:34 |
slaweq | so patch is there https://review.openstack.org/#/c/426946/ and waiting for review | 15:34 |
slaweq | I will address ralonsoh comments today | 15:34 |
ralonsoh | perfect! | 15:34 |
ralonsoh | I think this patch is going fast and very well | 15:35 |
slaweq | there is one strange thing with fullstack tests | 15:35 |
ralonsoh | buy reviews are always welcome | 15:35 |
ralonsoh | s/buy/but/ | 15:35 |
slaweq | yes :) | 15:35 |
slaweq | some of tests are failing but I'm not sure how it can be related to this patch | 15:35 |
ralonsoh | slaweq: ping ajo to review it | 15:36 |
slaweq | also, ralonsoh, please double check if supported rules and attributes are properly set | 15:36 |
ralonsoh | slaweq: ? | 15:36 |
slaweq | because e.g for linuxbridge driver https://review.openstack.org/#/c/426946/13/neutron/services/qos/drivers/linuxbridge/driver.py there was MINIMUM BANDWIDT LIMIT RULE | 15:36 |
slaweq | but I'm not sure if it's really supported currently | 15:37 |
ralonsoh | no, it's not | 15:37 |
slaweq | that's what I thougt but I wasn't sure | 15:37 |
slaweq | thx | 15:37 |
ralonsoh | sriov: max, min | 15:37 |
*** Julien-zte has quit IRC | 15:37 | |
ralonsoh | ovs: max, dscp | 15:37 |
ralonsoh | lb: max, dscp | 15:37 |
*** Julien-zte has joined #openstack-meeting | 15:37 | |
slaweq | ok, so I have it like that | 15:37 |
slaweq | thx ralonsoh | 15:37 |
ralonsoh | ok, next topic! | 15:38 |
ralonsoh | #topic Other Changes | 15:38 |
*** openstack changes topic to "Other Changes (Meeting topic: neutron_qos)" | 15:38 | |
ralonsoh | There is no agenda... | 15:38 |
*** Julien-zte has quit IRC | 15:38 | |
ralonsoh | any suggestion? | 15:38 |
betherly | im in process of developing qos panel in horizon | 15:38 |
*** Julien-zte has joined #openstack-meeting | 15:38 | |
*** anilvenkata has quit IRC | 15:38 | |
*** jesusaur has quit IRC | 15:38 | |
betherly | ajo has been awesome at helping me know what information you will want in the panel and so far i have a basic view available | 15:38 |
*** Julien-zte has quit IRC | 15:39 | |
ralonsoh | betherly: yes, I put this in open discussion | 15:39 |
betherly | ralonsoh: ah sorry! | 15:39 |
ralonsoh | betherly: no! | 15:39 |
davidsha | betherly: Have you a link to the patch? | 15:39 |
ralonsoh | doesn't matter | 15:39 |
betherly | https://review.openstack.org/#/c/418828/ | 15:39 |
ralonsoh | perfect! | 15:39 |
davidsha | Thanks! | 15:39 |
*** Julien-zte has joined #openstack-meeting | 15:39 | |
*** Julien-zte has quit IRC | 15:39 | |
betherly | no actions currently available but its getting there bit by bit | 15:39 |
ralonsoh | I'm not an expert in horizon, but I'll take a look at it | 15:40 |
betherly | ralonsoh: awesome thanks :) | 15:40 |
*** Julien-zte has joined #openstack-meeting | 15:40 | |
ralonsoh | I'll add this patch to our meetings | 15:40 |
*** rderose has joined #openstack-meeting | 15:40 | |
*** Julien-zte has quit IRC | 15:40 | |
slaweq | I will look at it also | 15:40 |
ralonsoh | and if you have any problem, ping us | 15:40 |
*** Julien-zte has joined #openstack-meeting | 15:41 | |
ralonsoh | ok, last topic | 15:41 |
ralonsoh | #topic Open Discussion | 15:41 |
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)" | 15:41 | |
*** Julien-zte has quit IRC | 15:41 | |
ralonsoh | Any other announcement?? | 15:41 |
*** ociuhandu has joined #openstack-meeting | 15:41 | |
slaweq | FYI: I will have talk about QoS in Neutron on Openstack day in Poland | 15:41 |
davidsha | I should have a PoC for the common classifier up within the next hour or 2 | 15:41 |
slaweq | it's next wednesday :) | 15:41 |
*** Julien-zte has joined #openstack-meeting | 15:41 | |
davidsha | slaweq: congrats and good luck! | 15:42 |
ralonsoh | slaweq: send the link!! | 15:42 |
*** jesusaur has joined #openstack-meeting | 15:42 | |
slaweq | davidsha: thx | 15:42 |
*** Julien-zte has quit IRC | 15:42 | |
slaweq | ralonsoh: link to what? slides? | 15:42 |
ralonsoh | slaweq: the youtube video hehehe | 15:42 |
slaweq | http://www.openstackday.pl/agenda/ | 15:42 |
slaweq | ralonsoh: if it will be on Youtube I will send on next meeting :) | 15:43 |
ralonsoh | perfect!!! | 15:43 |
slaweq | but it will be probably in polish so You will not understand it :P | 15:43 |
reedip | good luck slaweq :) | 15:43 |
davidsha | slaweq: Half the fun is seeing what google translate will say you said :P | 15:43 |
ralonsoh | youtbe translator hehehe | 15:43 |
ralonsoh | good luck | 15:43 |
slaweq | thx reedip | 15:43 |
slaweq | :D | 15:44 |
ralonsoh | ok, guys, thank you very much!! | 15:44 |
reedip | davidsha : LOL | 15:44 |
ralonsoh | let's finish | 15:44 |
slaweq | ok | 15:44 |
slaweq | thx | 15:44 |
ralonsoh | #endmeeting | 15:44 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 15:44 | |
openstack | Meeting ended Tue Mar 14 15:44:47 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:44 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/neutron_qos/2017/neutron_qos.2017-03-14-15.00.html | 15:44 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2017/neutron_qos.2017-03-14-15.00.txt | 15:44 |
openstack | Log: http://eavesdrop.openstack.org/meetings/neutron_qos/2017/neutron_qos.2017-03-14-15.00.log.html | 15:44 |
ralonsoh | bye! | 15:44 |
davidsha | Thanks! | 15:44 |
*** ociuhandu has quit IRC | 15:45 | |
*** mlavalle has left #openstack-meeting | 15:48 | |
*** boden has left #openstack-meeting | 15:48 | |
betherly | thanks!! | 15:49 |
*** longxiongqiu has quit IRC | 15:49 | |
*** lpetrut has quit IRC | 15:51 | |
*** unicell has joined #openstack-meeting | 15:53 | |
*** nadya has joined #openstack-meeting | 15:53 | |
*** janki has quit IRC | 15:54 | |
*** tobberyd_ has joined #openstack-meeting | 15:55 | |
*** kaisers_ has joined #openstack-meeting | 15:55 | |
*** markvoelker has quit IRC | 15:56 | |
*** jlibosva has joined #openstack-meeting | 15:56 | |
*** iceyao has quit IRC | 15:56 | |
*** markvoelker has joined #openstack-meeting | 15:58 | |
*** tobberydberg has quit IRC | 15:59 | |
*** tobberyd_ has quit IRC | 15:59 | |
ihrachys | #startmeeting neutron_ci | 16:00 |
openstack | Meeting started Tue Mar 14 16:00:55 2017 UTC and is due to finish in 60 minutes. The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:00 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:00 |
manjeets | hi | 16:00 |
*** openstack changes topic to " (Meeting topic: neutron_ci)" | 16:00 | |
openstack | The meeting name has been set to 'neutron_ci' | 16:01 |
ihrachys | hi everyone | 16:01 |
jlibosva | hi | 16:01 |
dasanind | hi | 16:01 |
* ihrachys waves back at manjeets, jlibosva, and dasanind | 16:02 | |
ihrachys | #topic Action items from previous meeting | 16:02 |
*** openstack changes topic to "Action items from previous meeting (Meeting topic: neutron_ci)" | 16:02 | |
ihrachys | first was: "ihrachys fix e-r bot not reporting in irc channel" | 16:02 |
ihrachys | I haven't got to that one just yet, need to talk to mtreinish I guess on why it's not reporting, I suspect wrong configuration that is too limiting. lemme repeat the action for the next week. | 16:03 |
*** sridharg has quit IRC | 16:03 | |
ihrachys | #action ihrachys fix e-r bot not reporting in irc channel | 16:03 |
*** jaugustine has quit IRC | 16:03 | |
ihrachys | next was "ihrachys to clean up dsvm-scenario flavor handling from gate-hook" | 16:03 |
ihrachys | that happened | 16:03 |
*** salv-orlando has joined #openstack-meeting | 16:03 | |
ihrachys | we landed https://review.openstack.org/#/c/442758/ | 16:03 |
ihrachys | beyond cleanup, there is some failure in ovs scenario job that started showing up after latest hook rework | 16:05 |
ihrachys | we will discuss later | 16:05 |
ihrachys | next was "ihrachys to walk thru list of open gate failure bugs and give them love" | 16:05 |
*** salv-orlando has quit IRC | 16:05 | |
ihrachys | I did, closed some bugs that didn't seem relevant | 16:05 |
*** felipemonteiro has quit IRC | 16:05 | |
ihrachys | ok next was "ihrachys to chase down armax on d-g local.conf breakage assessment for stadium" | 16:05 |
*** salv-orlando has joined #openstack-meeting | 16:05 | |
*** swapnil-nilangek has quit IRC | 16:06 | |
ihrachys | armax posted some patches since then: https://review.openstack.org/442884 for client, https://review.openstack.org/442890 for fwaas | 16:06 |
*** hashar has quit IRC | 16:06 | |
ihrachys | both were backported into stable branches | 16:06 |
ihrachys | there is also ongoing work for sfc gate: https://review.openstack.org/#/c/445037/ and https://review.openstack.org/#/c/442882/ | 16:07 |
ihrachys | I assume that's all there is | 16:07 |
*** felipemonteiro has joined #openstack-meeting | 16:07 | |
ihrachys | ok next was "haleyb and mlavalle to investigate what makes dvr gate job failing with 25% rate" | 16:08 |
clarkb | ihrachys: e-r reports that dhcp lease failures are causing problems | 16:08 |
clarkb | not sure if that is on your radar or not | 16:08 |
ihrachys | clarkb: it wasn't. is there a bug? | 16:08 |
*** mlavalle has joined #openstack-meeting | 16:09 | |
mlavalle | hi | 16:09 |
clarkb | ihrachys: yes its top of e-r list http://status.openstack.org/elastic-recheck/index.html | 16:09 |
ihrachys | mlavalle: hey. we were looking for update on dvr job failure rate that was 25% prev week | 16:09 |
clarkb | ihrachys: the bug is over a year old and "fixed" in nova net, I think we must be rematching errors from syslog? against neutron jobs | 16:09 |
clarkb | ihrachys: so the bug there may not be the most up to date | 16:09 |
mlavalle | ihrachys: I couldn't make progress on that last week :-( | 16:10 |
*** jkilpatr has quit IRC | 16:10 | |
ihrachys | clarkb: yeah, seems like catching generic message | 16:10 |
ihrachys | mlavalle: ok then I leave the action on you | 16:10 |
ihrachys | #action haleyb and mlavalle to investigate what makes dvr gate job failing with 25% rate | 16:10 |
mlavalle | ihrachys: thanks. I was sick a few days last week | 16:10 |
ihrachys | clarkb: thanks for bringing up, we will have a look | 16:11 |
ihrachys | mlavalle: np, get well | 16:11 |
clarkb | thanks | 16:11 |
ihrachys | #action ihrachys explore why bug 1532809 bubbled into top in e-r | 16:11 |
openstack | bug 1532809 in OpenStack Compute (nova) liberty "Gate failures when DHCP lease cannot be acquired" [High,In progress] https://launchpad.net/bugs/1532809 - Assigned to Sean Dague (sdague) | 16:11 |
ihrachys | next was "ajo to chase down fullstack 100% failure rate due to test_dscp_qos_policy_rule_lifecycle failures" | 16:11 |
ihrachys | also jlibosva was going to help ajo | 16:12 |
ihrachys | jlibosva: any progress? | 16:12 |
jlibosva | ihrachys: yes | 16:12 |
manjeets | I may sound dumb asking that question can some explain a bit what is e-r ? | 16:12 |
jlibosva | I started looking at it like hour-ish ago :) | 16:12 |
jlibosva | It got broken by https://review.openstack.org/#/c/380329 | 16:12 |
jlibosva | I suspect that delete_dscp doesn't work with native driver | 16:12 |
ihrachys | manjeets: elastic-recheck, it's a tool that captures failure patterns in logs and reports in gerrit, on elastic recheck webui, and in irc | 16:12 |
jlibosva | I'm just trying a local run and I'm about to send a simple patch to verify the fullstack fix | 16:13 |
jlibosva | https://review.openstack.org/445560 | 16:13 |
manjeets | ohk thanks ihrachys | 16:13 |
*** salv-orlando has quit IRC | 16:13 | |
ihrachys | jlibosva: niiice | 16:13 |
jlibosva | I need to make sure that's really it, I didn't give it much love yet | 16:14 |
ihrachys | jlibosva: I wonder why we have different API for drivers | 16:14 |
jlibosva | yeah ... | 16:14 |
*** aarefiev is now known as aarefiev_afk | 16:14 | |
ihrachys | still this is a nice step to check if that fixes the issue | 16:14 |
*** ataraday_ has quit IRC | 16:14 | |
*** trevormc has left #openstack-meeting | 16:14 | |
ihrachys | if so, we can look at making them consistent | 16:14 |
*** swapnil-nilangek has joined #openstack-meeting | 16:15 | |
jlibosva | there is also a constant failure in securitygroups for linuxbridge | 16:15 |
jlibosva | I didn't get a chance to look at that yet | 16:15 |
ihrachys | gotcha | 16:15 |
*** toscalix has quit IRC | 16:16 | |
*** sandanar has quit IRC | 16:16 | |
jlibosva | can be an AI to me till the next meeting ;) | 16:16 |
ihrachys | #action jlibosva fix delete_dscp for native driver: https://review.openstack.org/445560 | 16:17 |
ihrachys | #action jlibosva to fix remaining fullstack failures in securitygroups for linuxbridge | 16:17 |
ihrachys | we are getting closer to stable functional job (it shows normal failure rate now), let's do the same for fullstack | 16:18 |
ihrachys | next AI was "ajo to restore and merge patch raising ovsdb native timeout: https://review.openstack.org/#/c/425623/" | 16:18 |
*** treiz has quit IRC | 16:18 | |
ihrachys | we restored, but now I am not sure | 16:18 |
ihrachys | as seen on http://grafana.openstack.org/dashboard/db/neutron-failure-rate?panelId=7&fullscreen functional is back to normal | 16:18 |
ihrachys | and not the old normal, but actual normal | 16:18 |
ihrachys | its failure rate is less than -api job that is considered rather stable and is voting | 16:19 |
ihrachys | so I am not sure we should land the timeout bump | 16:19 |
ihrachys | thoughts? | 16:19 |
jlibosva | I would go for it | 16:20 |
jlibosva | as the worst that can happen is that some actions might take longer before failing | 16:20 |
jlibosva | if transaction is successful, it won't be longer | 16:20 |
ihrachys | but doesn't it open door wider for performance regressions | 16:22 |
*** annp has quit IRC | 16:22 | |
*** jkilpatr has joined #openstack-meeting | 16:23 | |
jlibosva | you mean that if we make a change that would create a longer transaction it would fail for us in gate while with higher timeout it would get pass? | 16:24 |
ihrachys | yeah. we will catch it a lot later when we pile up more regressions on top | 16:24 |
ihrachys | at the point when it may be harder to unravel things | 16:25 |
*** phil_ has quit IRC | 16:25 | |
*** ayogi has joined #openstack-meeting | 16:25 | |
jlibosva | maybe we can close the bug and discuss this on the review with pros and cons | 16:26 |
ihrachys | yeah | 16:26 |
ihrachys | I also want to get back to the question of voting for the job in several weeks | 16:26 |
ihrachys | assuming we prove it's stable | 16:26 |
ihrachys | ok let's discuss further in gerrit | 16:27 |
ihrachys | next AI was "anilvenkata_afk to track inclusion of HA+DVR patch for devstack-gate" | 16:27 |
*** annegentle has joined #openstack-meeting | 16:27 | |
jlibosva | ihrachys: you mean putting functional to gate queue? | 16:27 |
*** alexpilo_ has joined #openstack-meeting | 16:27 | |
ihrachys | jlibosva: yes | 16:28 |
jlibosva | or talking about fullstack | 16:28 |
jlibosva | ok | 16:28 |
ihrachys | we told we want it stable and voting? | 16:28 |
ihrachys | maybe just check, we'll see | 16:28 |
ihrachys | but voting | 16:28 |
*** alexpilotti has quit IRC | 16:28 | |
ihrachys | ehm, sorry, I mix things :) | 16:28 |
ihrachys | yes, gate queue | 16:28 |
jlibosva | got it :) | 16:28 |
ihrachys | for fullstack, it will be first check voting | 16:28 |
ihrachys | for that we need to show weeks of steady stability | 16:29 |
ihrachys | only time will tell if we can do that | 16:29 |
ihrachys | ok back to HA+DVR job | 16:29 |
ihrachys | the patch is still sitting there: https://review.openstack.org/#/c/383827/ | 16:29 |
ihrachys | we may want clarkb and other infra gurus to chime in | 16:30 |
*** nkrinner is now known as nkrinner_afk | 16:30 | |
ihrachys | I see clarkb +2d it in the past | 16:30 |
clarkb | I can rereview | 16:30 |
ihrachys | thanks! | 16:31 |
*** iyamahat has quit IRC | 16:31 | |
ihrachys | #action anilvenkata to follow up on HA+DVR job patches | 16:31 |
*** e0ne has quit IRC | 16:31 | |
*** yamahata has quit IRC | 16:32 | |
ihrachys | there was a test failure in the new ha-dvr job, probably because of the new topology used | 16:32 |
*** annegentle has quit IRC | 16:32 | |
ihrachys | I assume Anil will look at it once we have infra side done | 16:32 |
*** Patifa has joined #openstack-meeting | 16:33 | |
*** Apoorva has joined #openstack-meeting | 16:33 | |
*** dmorita has joined #openstack-meeting | 16:33 | |
*** Apoorva has quit IRC | 16:33 | |
ihrachys | though actually, since devstack-gate is part of the same queue, we don't need to wait, we can start fixing the test runs with depends-on patches | 16:33 |
ihrachys | gotta check with Anil on his plans | 16:34 |
ihrachys | and, that was it for action items from the previous week | 16:34 |
ihrachys | let's move on | 16:34 |
ihrachys | #topic Action items from PTG | 16:34 |
*** openstack changes topic to "Action items from PTG (Meeting topic: neutron_ci)" | 16:34 | |
*** cdub has quit IRC | 16:34 | |
ihrachys | the prev meeting, we covered most of them | 16:34 |
ihrachys | the only thing that was left behind is python3 strategy | 16:35 |
ihrachys | during ptg, we decided there should be a bunch of jobs that should transfer to py3 | 16:35 |
*** tonytan_brb has joined #openstack-meeting | 16:35 | |
ihrachys | I believe functional and fullstack were in short list | 16:35 |
*** tonytan_brb has quit IRC | 16:35 | |
*** prateek has quit IRC | 16:35 | |
ihrachys | also we need some tempest job switched to py3 | 16:36 |
ihrachys | jlibosva: what's the plan? | 16:36 |
*** tonytan4ever has quit IRC | 16:36 | |
*** tonytan_brb has joined #openstack-meeting | 16:36 | |
jlibosva | yes, I believe functional, fullstack and full-tempest makes most sense. I don't think we have any blueprint or bug where we can track the effort | 16:37 |
jlibosva | so I'm gonna create some | 16:37 |
jlibosva | and same for tempest split | 16:37 |
ihrachys | jlibosva: which full-tempest? | 16:37 |
ihrachys | I think we have several | 16:37 |
*** tobberydberg has joined #openstack-meeting | 16:38 | |
ihrachys | there is one all-in-one, and two multinodes | 16:38 |
ihrachys | (which are 2nodes really) | 16:38 |
*** prateek has joined #openstack-meeting | 16:39 | |
jlibosva | but none of multinode are voting, are they? | 16:39 |
*** dmacpher is now known as dmacpher-afk | 16:39 | |
*** belmoreira has quit IRC | 16:39 | |
ihrachys | yeah | 16:40 |
ihrachys | and that's a shame | 16:40 |
ihrachys | but consider that the single node one is part of integrated gate | 16:40 |
ihrachys | so it wouldn't be a neutron only decision to switch it | 16:40 |
*** claudiub has quit IRC | 16:40 | |
ihrachys | and I suspect it wouldn't go smooth | 16:40 |
jlibosva | hmm, I need to update myself on that, I see we already have some py35 tempest: http://logs.openstack.org/29/380329/24/check/gate-tempest-dsvm-py35-ubuntu-xenial/4ed1870/logs/testr_results.html.gz | 16:41 |
ihrachys | jlibosva: it's not working | 16:41 |
ihrachys | because swift is not really compatible | 16:41 |
ihrachys | and devstack attempts to execute it as py3 | 16:41 |
ihrachys | I think that's going to be tackled with https://review.openstack.org/#/c/439108/ | 16:42 |
*** david-lyle has joined #openstack-meeting | 16:42 | |
ihrachys | but so far it doesn't move anywhere | 16:42 |
*** tobberydberg has quit IRC | 16:42 | |
*** 21WAAS6DN has joined #openstack-meeting | 16:42 | |
jlibosva | so what does the job run? | 16:43 |
ihrachys | it runs everything that devstack determines as py3 compat in py3 | 16:44 |
ihrachys | and there was a hack in devstack that enforced py3 for swift | 16:44 |
ihrachys | that was honestly totally wrong | 16:44 |
ihrachys | because they have py3 SyntaxErrors in their code, not to mention it was never tried | 16:45 |
*** ltomasbo is now known as ltomasbo|away | 16:45 | |
ihrachys | anyhoo, let's leave AI on you and move on | 16:46 |
ihrachys | #action jlibosva to figure out the plan for py3 gate transition and report back | 16:46 |
ihrachys | there will also be some CI related work once we get to switch to lib/neutron: https://review.openstack.org/#/q/topic:new-neutron-devstack-in-gate and mod_wsgi | 16:47 |
jlibosva | yep | 16:47 |
ihrachys | one other thing than I wanted to raise is https://review.openstack.org/#/c/439114/ | 16:47 |
ihrachys | manjeets: what's the status of the dashboard patch? are you going to respin it? | 16:47 |
*** fzdarsky is now known as fzdarsky|afk | 16:48 | |
manjeets | ihrachys, yes | 16:48 |
ihrachys | I was thinking, maybe we should squash that with existing neutron review dashboard | 16:48 |
ihrachys | having a single tool may make more sense | 16:48 |
manjeets | yes that make sense since some of existing method can be used as well | 16:48 |
ihrachys | thoughts? | 16:48 |
*** bzhao_ has quit IRC | 16:48 | |
manjeets | just creating a new section for all gate patches in existing dashboard | 16:49 |
manjeets | ?? | 16:49 |
ihrachys | yea | 16:49 |
manjeets | ++ | 16:49 |
*** unicell has quit IRC | 16:49 | |
ihrachys | #action manjeets respin https://review.openstack.org/#/c/439114/ to include gate-failure reviews into existing dashboard | 16:49 |
ihrachys | another thing I wanted to note is that we made some progress on the path to index functional and fullstack logs in logstash | 16:50 |
ihrachys | https://review.openstack.org/#/q/topic:index-func-logs | 16:50 |
ihrachys | we now generate a -index.txt file with all INFO+ messages in each gate run | 16:51 |
jlibosva | ihrachys: good job :) | 16:51 |
ihrachys | the only missing bit is actually updating logstash config to index it | 16:51 |
ihrachys | I hope to get infra review it today | 16:51 |
ihrachys | clarkb: maybe you have +2 there too? system-config ^ | 16:51 |
*** hashar has joined #openstack-meeting | 16:51 | |
ihrachys | speaking of more logs collected, another stalled work is collecting info on mlock-consuming processes: https://review.openstack.org/#/q/topic:collect-mlock-stats-in-gate | 16:52 |
ihrachys | I haven't seen oom-killers lately. is it just my perception? | 16:53 |
* jlibosva hasn't checked the status | 16:53 | |
clarkb | ihrachys: ya I can look a tthat too | 16:53 |
*** iyamahat has joined #openstack-meeting | 16:53 | |
*** bobh has quit IRC | 16:53 | |
ihrachys | thanks | 16:54 |
*** d0ugal has quit IRC | 16:55 | |
ihrachys | ok any more topics to raise this time? | 16:56 |
jlibosva | not from me | 16:57 |
manjeets | not from me either atm | 16:58 |
ihrachys | ok let's call it a day | 16:58 |
ihrachys | thanks everyone | 16:58 |
manjeets | thanks | 16:58 |
jlibosva | thanks! | 16:58 |
ihrachys | #endmeeting | 16:58 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 16:58 | |
openstack | Meeting ended Tue Mar 14 16:58:16 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:58 |
jlibosva | bye | 16:58 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-03-14-16.00.html | 16:58 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-03-14-16.00.txt | 16:58 |
openstack | Log: http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-03-14-16.00.log.html | 16:58 |
*** jlibosva has left #openstack-meeting | 16:58 | |
davidsha | Hi | 17:01 |
*** fzdarsky|afk is now known as fzdarsky | 17:01 | |
*** ltomasbo|away is now known as ltomasbo | 17:05 | |
*** reedip has quit IRC | 17:06 | |
*** swapnil-nilangek has quit IRC | 17:07 | |
*** arxcruz has quit IRC | 17:09 | |
*** markstur has quit IRC | 17:09 | |
*** arxcruz has joined #openstack-meeting | 17:12 | |
*** eharney has quit IRC | 17:12 | |
*** david-lyle_ has joined #openstack-meeting | 17:13 | |
*** david-lyle has quit IRC | 17:13 | |
*** nadya has quit IRC | 17:14 | |
*** yamahata has joined #openstack-meeting | 17:14 | |
*** fzdarsky has quit IRC | 17:14 | |
*** matrohon has quit IRC | 17:16 | |
*** chris_morrell has joined #openstack-meeting | 17:17 | |
*** tmorin has quit IRC | 17:18 | |
*** ltomasbo is now known as ltomasbo|away | 17:19 | |
*** fzdarsky has joined #openstack-meeting | 17:22 | |
*** hashar has quit IRC | 17:23 | |
*** eharney has joined #openstack-meeting | 17:26 | |
*** unicell has joined #openstack-meeting | 17:27 | |
*** Patifa has quit IRC | 17:27 | |
*** bkopilov has quit IRC | 17:27 | |
*** Patifa has joined #openstack-meeting | 17:31 | |
*** Cibo_ has joined #openstack-meeting | 17:31 | |
*** mickeys has joined #openstack-meeting | 17:31 | |
*** kaisers_ has quit IRC | 17:32 | |
*** davidsha has quit IRC | 17:33 | |
*** thingee has joined #openstack-meeting | 17:35 | |
*** bkopilov has joined #openstack-meeting | 17:38 | |
*** dbecker has quit IRC | 17:43 | |
*** gagehugo has joined #openstack-meeting | 17:43 | |
*** spilla has joined #openstack-meeting | 17:45 | |
*** cody-somerville has quit IRC | 17:48 | |
*** csomerville has joined #openstack-meeting | 17:48 | |
*** tesseract has quit IRC | 17:49 | |
*** cody-somerville has joined #openstack-meeting | 17:50 | |
*** csomerville has quit IRC | 17:53 | |
*** bobh has joined #openstack-meeting | 17:54 | |
*** browne has joined #openstack-meeting | 17:55 | |
*** nadya has joined #openstack-meeting | 17:57 | |
*** d0ugal has joined #openstack-meeting | 17:58 | |
*** bobh has quit IRC | 17:58 | |
*** s3wong has joined #openstack-meeting | 17:59 | |
*** henrynash has joined #openstack-meeting | 18:00 | |
lbragstad | #startmeeting keystone | 18:00 |
openstack | Meeting started Tue Mar 14 18:00:28 2017 UTC and is due to finish in 60 minutes. The chair is lbragstad. Information about MeetBot at http://wiki.debian.org/MeetBot. | 18:00 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 18:00 |
*** openstack changes topic to " (Meeting topic: keystone)" | 18:00 | |
openstack | The meeting name has been set to 'keystone' | 18:00 |
lbragstad | ping 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:00 |
lbragstad | StefanPaetowJisc, stevemar, topol, shardy, ricolin | 18:00 |
browne | o/ | 18:00 |
spilla | o/ | 18:00 |
lbragstad | agenda #link https://etherpad.openstack.org/p/keystone-weekly-meeting | 18:00 |
henrynash | howdy y’all | 18:00 |
topol | 0/ | 18:00 |
topol | o/ | 18:00 |
gagehugo | o/ | 18:00 |
lamt | o/ | 18:00 |
rderose | o/ | 18:00 |
knikolla | o/ | 18:01 |
cmurphy | o/ | 18:01 |
*** pvaneck has joined #openstack-meeting | 18:01 | |
ayoung | Hey Ho, Lets Go! | 18:01 |
*** ralonsoh has quit IRC | 18:02 | |
*** nadya has quit IRC | 18:02 | |
ildikov | o/ | 18:02 |
lbragstad | alright - we have a lot on the agenda today so let's get started | 18:03 |
lbragstad | #topic Mascot | 18:03 |
*** openstack changes topic to "Mascot (Meeting topic: keystone)" | 18:03 | |
lbragstad | i got an email last week from the foundation asking if we liked our mascot | 18:03 |
*** ociuhandu has joined #openstack-meeting | 18:03 | |
lbragstad | we have the opportunity to make changes if we want them | 18:03 |
*** pcaruana has quit IRC | 18:03 | |
rodrigods | o/ | 18:04 |
*** d0ugal has quit IRC | 18:04 | |
gagehugo | I like the design | 18:04 |
lbragstad | Heidi, from the foundation, mentioned that someone thought about incorporating a key into the shell of the turtle | 18:04 |
lbragstad | right now - it's in the shape of a shield | 18:04 |
ayoung | I thought a keyhole would be more appropriate | 18:04 |
* ayoung looks for early prototypes | 18:05 | |
knikolla | ayoung: ooo i remember those prototypes | 18:05 |
*** mgagne_ is now known as mgagne | 18:05 | |
ayoung | https://admiyo.fedorapeople.org/openstack/stoney-turtle.svg | 18:05 |
* notmorgan doesn't wanna. | 18:05 | |
*** henrynash has quit IRC | 18:05 | |
*** bobh has joined #openstack-meeting | 18:05 | |
notmorgan | i kinda still like the Keystone Lite logo we had. | 18:06 |
notmorgan | ftr. | 18:06 |
notmorgan | that said, i don't feel strongly the turtle needs to change | 18:06 |
*** portdirect has joined #openstack-meeting | 18:06 | |
ayoung | notmorgan, will live forever on our jackets | 18:06 |
lbragstad | does anyone else have things they'd like to incorporated into the logo? | 18:06 |
notmorgan | the only mascot that i could see on a laptop of mine is the new Ironic one, fwiw. | 18:06 |
*** henrynash has joined #openstack-meeting | 18:07 | |
lbragstad | s/to/to see/ | 18:07 |
*** qwebirc35726 has joined #openstack-meeting | 18:07 | |
*** qwebirc35726 has quit IRC | 18:07 | |
lbragstad | alright - i'll give ayoung's feedback to Heidi and if they roll a new version we can vote on it | 18:08 |
lbragstad | #action lbragstad to give feedback to the foundation and keep team posted on outcomes | 18:08 |
lbragstad | #topic Upstream training liaison | 18:08 |
*** openstack changes topic to "Upstream training liaison (Meeting topic: keystone)" | 18:08 | |
lbragstad | ildikov o/ | 18:08 |
ildikov | lbragstad: tnx | 18:09 |
ildikov | Hi All :) | 18:09 |
lbragstad | ildikov and i talked about various upstream training efforts at the PTG | 18:09 |
gagehugo | ildikov o/ | 18:09 |
ildikov | the plan is to have liaisons from every team | 18:09 |
lbragstad | ildikov but i'll let her give an intro | 18:09 |
ildikov | both for the training and to on board new contributors in general | 18:10 |
ildikov | the training itself is one and a half days long, interactive and hands-on and that aims to show the first steps to the contributors | 18:10 |
ildikov | we are running it before every Summit, the next one will be in Boston, Saturday afternoon and Sunday | 18:11 |
*** Sukhdev has joined #openstack-meeting | 18:11 | |
ildikov | we are running a short survey, so students can voice their interest in contribution areas and projects | 18:11 |
ildikov | we would like to have coverage for the areas they are interested in on site | 18:12 |
*** jkilpatr has quit IRC | 18:12 | |
ildikov | as for the liaisons, the expectation is that if they can help us with the training material and/or attending the training and help the students that would be great | 18:13 |
*** jkilpatr has joined #openstack-meeting | 18:13 | |
*** henrynash has quit IRC | 18:13 | |
lbragstad | ildikov i know dstanek expressed interest in helping | 18:13 |
ildikov | lbragstad: sounds great! :) | 18:13 |
lbragstad | ildikov but i assume you wouldn't be opposed to others helping out if they are interested? | 18:14 |
ildikov | not at all! | 18:14 |
lbragstad | awesome | 18:14 |
lbragstad | ildikov you all planning on having a weekly meeting, right? | 18:14 |
ildikov | the current volunteers are all enthusiastic people, but we can always use more ideas and help | 18:14 |
ildikov | we will soon start the preparation to the Boston Summit and we will look into run weekly meetings | 18:15 |
ildikov | we have anew IRC channel: #openstack-university | 18:15 |
lbragstad | ildikov are liaisons expected to be at the Boston forum? | 18:15 |
ildikov | this is for mentors, trainers, coaches and anyone who's interested in this activity | 18:16 |
ildikov | we are flexible in terms of travel, we will ask the liaisons first especially if there's much interest in the area they cover | 18:16 |
*** annegentle has joined #openstack-meeting | 18:17 | |
lbragstad | that makes sense | 18:17 |
ildikov | so someone can still be a liaison even if he/she is not able to travel to some of the trainings | 18:17 |
rodrigods | i'm already mentor for other internship programs | 18:17 |
rodrigods | i can help here as well | 18:17 |
lbragstad | rodrigods ++ | 18:18 |
rodrigods | mostly with material | 18:18 |
ildikov | we are also in discussion with a few OpenStack Days event organizers who would like to run a one day long version of the training | 18:18 |
ildikov | rodrigods: sounds great, thanks! | 18:18 |
knikolla | i'm based in boston, if the liason won't be able to attend for keystone i can fill in | 18:18 |
ildikov | so we will also ask help from the liaisons/teams to find local people for these smaller events | 18:18 |
*** mlavalle has left #openstack-meeting | 18:19 | |
*** antwash has joined #openstack-meeting | 18:19 | |
ildikov | knikolla: great, thank you! | 18:19 |
ildikov | #link https://docs.openstack.org/upstream-training/ - this is the training website, we will start to update it soon: | 18:19 |
*** abalutoiu has quit IRC | 18:19 | |
*** annegentle has quit IRC | 18:20 | |
ildikov | #link ttps://etherpad.openstack.org/p/upstream-training-team - this is the list of volunteers and so far identified liaisons | 18:20 |
lbragstad | #link https://etherpad.openstack.org/p/upstream-training-team | 18:20 |
*** annegentle has joined #openstack-meeting | 18:20 | |
ildikov | we will use [os-university] as ML tag | 18:20 |
ildikov | so if any of you would be interested in helping out just add yourself to the etherpad and look for the tag on the ML for news and also jump on the IRC channel I posted above | 18:21 |
ildikov | also feel free to ping me anytime if you have questions | 18:21 |
lbragstad | ildikov awesome - thanks for all the information | 18:21 |
ildikov | I can give more updates, but I don't want to hijack the whole meeting now :) | 18:22 |
ildikov | lbragstad: thanks for the opportunity and support! | 18:22 |
lbragstad | ildikov anytime, i'm happy to see the involvement here (thanks rodrigods knikolla) | 18:22 |
rodrigods | ++ | 18:23 |
ildikov | thank you all! | 18:23 |
lbragstad | ildikov thanks! | 18:23 |
lbragstad | #topic VMT Update: keystonemiddleware diagram and docs | 18:23 |
*** openstack changes topic to "VMT Update: keystonemiddleware diagram and docs (Meeting topic: keystone)" | 18:23 | |
lbragstad | knikolla gagehugo | 18:23 |
gagehugo | o/ | 18:23 |
lbragstad | you both started working on this as a result of last weeks meeting - how are things going? | 18:23 |
gagehugo | knikolla and I made a first draft for an architecture diagram for keystonemiddleware: http://i.imgur.com/1KIUsRh.png | 18:24 |
ayoung | what is a VMT? I thought that was the state I passed through to get to Canada? | 18:24 |
lbragstad | #link http://i.imgur.com/1KIUsRh.png | 18:24 |
lbragstad | ayoung vulnerability management team | 18:24 |
ayoung | Ah | 18:24 |
*** Cibo_ has quit IRC | 18:24 | |
*** ayogi has quit IRC | 18:25 | |
lbragstad | we need to initiate a security analysis of all identity projects to get coverage | 18:25 |
gagehugo | https://etherpad.openstack.org/p/pike-ptg-keystone-vmt-coverage | 18:25 |
*** annegentle has quit IRC | 18:25 | |
ayoung | OK, makes sense now | 18:25 |
lbragstad | gagehugo knikolla have either of you been able to get through to the security folks? | 18:25 |
lbragstad | cc unrahul ^ | 18:25 |
gagehugo | lbragstad: wanted to double check with keystone people first about the accuracy of the diagram | 18:26 |
unrahul | lbragstad: | 18:26 |
lbragstad | gagehugo and just do double check - this is only targeting keystonemiddleware initially | 18:26 |
gagehugo | yes | 18:26 |
unrahul | gagehugo: may be you can initiate the review by starting a gerrit review against security-analysis repo | 18:26 |
bknudson_ | do we have the ability to encrypt the memcache data? | 18:27 |
gagehugo | unrahul sure | 18:27 |
unrahul | So that security community may also coment | 18:27 |
unrahul | thanks gagehugo | 18:27 |
ayoung | bknudson_, I swore we had that at some point | 18:27 |
gagehugo | bknudson_ that would be something we should note then if that's the case | 18:27 |
lbragstad | i know the ksm caching implementation is different than that of oslo.cache | 18:27 |
ayoung | http://git.openstack.org/cgit/openstack/keystonemiddleware/tree/keystonemiddleware/auth_token/_cache.py | 18:29 |
*** lpetrut has joined #openstack-meeting | 18:29 | |
ayoung | http://git.openstack.org/cgit/openstack/keystonemiddleware/tree/keystonemiddleware/auth_token/_cache.py#n242 | 18:29 |
lbragstad | #link http://git.openstack.org/cgit/openstack/keystonemiddleware/tree/keystonemiddleware/auth_token/_cache.py#n243 | 18:29 |
ayoung | lass SecureTokenCache(TokenCache): | 18:29 |
notmorgan | also, a service can pass a cache handle to ksm | 18:30 |
ayoung | make that class SecureTokenCache(TokenCache): | 18:30 |
notmorgan | (like swift) | 18:30 |
gagehugo | ah ok | 18:30 |
knikolla | looks like the answer is yes | 18:30 |
notmorgan | and ksm will use that cache handle/connection to do the lifting as well | 18:30 |
bknudson_ | ok, might be useful to put cache encryption into the diagram (the key is in the config file) | 18:31 |
*** henrynash has joined #openstack-meeting | 18:31 | |
lbragstad | ++ | 18:31 |
gagehugo | will do! | 18:31 |
lbragstad | sounds like also need to open a review to the security repo | 18:32 |
*** claudiub has joined #openstack-meeting | 18:32 | |
*** spotz is now known as spotz_zzz | 18:32 | |
gagehugo | yup | 18:32 |
lbragstad | one other thing about the diagram is that it might be easier to read if we numbered the steps | 18:33 |
*** spotz_zzz is now known as spotz | 18:33 | |
gagehugo | ah, yeah the process tutorial does that | 18:33 |
gagehugo | basically provide a walkthrough then I assume | 18:34 |
*** cody-somerville has quit IRC | 18:34 | |
*** cody-somerville has joined #openstack-meeting | 18:34 | |
lbragstad | the diagram has arrows in it the denote some sort of flow | 18:34 |
*** longxiongqiu has joined #openstack-meeting | 18:35 | |
knikolla | the arrows denote the initiator of the communication | 18:36 |
lbragstad | looks like there are arrows here #link https://openstack-security.github.io/collaboration/2016/01/16/threat-analysis.html | 18:36 |
*** cdub has joined #openstack-meeting | 18:36 | |
knikolla | and numbers also. cool, we'll update the diagram. | 18:37 |
lbragstad | awesome - thanks again | 18:37 |
lbragstad | we can keep reviewing offline | 18:37 |
gagehugo | sure | 18:37 |
knikolla | ++ | 18:37 |
lbragstad | gagehugo knikolla did either of you have anything else on VMT? | 18:37 |
*** mkoderer has quit IRC | 18:37 | |
gagehugo | I think that is it for now? We can open a review and see what to do from there (after we update the diagram) | 18:38 |
lbragstad | do you want me to keep the topic on the agenda for next week? | 18:38 |
knikolla | if it's a light agenda | 18:38 |
gagehugo | lbragstad: sure | 18:38 |
*** dprince has quit IRC | 18:38 | |
lbragstad | knikolla gagehugo sounds good | 18:38 |
lbragstad | thanks guys, let's move on | 18:38 |
lbragstad | #topic Pike specs | 18:38 |
*** openstack changes topic to "Pike specs (Meeting topic: keystone)" | 18:38 | |
lbragstad | we have several specs in the works | 18:38 |
lbragstad | figured we could use a little time during today's meeting to work through them | 18:39 |
lbragstad | a couple of them are close | 18:39 |
lbragstad | #topic Pike specs: API keys | 18:39 |
*** openstack changes topic to "Pike specs: API keys (Meeting topic: keystone)" | 18:39 | |
*** electrofelix has quit IRC | 18:39 | |
lbragstad | rderose o/ | 18:39 |
lbragstad | #link https://review.openstack.org/#/c/438761/ | 18:39 |
rderose | We discussed this at the PTG, the problem: users storing their username/password in configuration files for their scripts / 3rd party tools. | 18:39 |
rderose | Instead allow users to create access key credentials with limited scope (subset of their roles). | 18:39 |
rderose | The key would be used like a password credential; thus, used to request a scoped token. | 18:39 |
rderose | The questions we've been discussing is, should we instead, treat the keys more like bearer tokens where you could use the key to make an API call and not have to request a scoped token. | 18:40 |
*** longxiongqiu has quit IRC | 18:40 | |
breton | will it replace service users' username/password | 18:40 |
breton | ? | 18:40 |
lbragstad | dstanek has an alternate spec proposed - https://review.openstack.org/#/c/440593/1 | 18:40 |
rderose | breton: yes | 18:40 |
lbragstad | breton yes - that would be the intent | 18:40 |
gagehugo | rderose: the key would be scoped then I assume? | 18:40 |
breton | oh well. | 18:40 |
rderose | gagehugo: yes | 18:40 |
breton | i wonder how many people it is going to break | 18:40 |
rderose | breton: shouldn't break anyone | 18:41 |
rderose | username/password will still work | 18:41 |
lbragstad | breton i assume we will gracefully switch | 18:41 |
lbragstad | i don't expect it to break anyone | 18:41 |
breton | because it broke people when we moved to plugins | 18:41 |
*** aysyd has quit IRC | 18:41 | |
lbragstad | we should just encourage people to deploy service users more securely | 18:41 |
bknudson_ | not having to request a scoped token is follow-on work. | 18:41 |
rderose | bknudson_: ++ | 18:42 |
lbragstad | the big different between rderose's approach and dstanek's approach that I see is that one treats api keys like credentials and one treats it like a token | 18:42 |
*** kaisers_ has joined #openstack-meeting | 18:43 | |
lbragstad | in one you use the api key to *get* a token and in the other you use the api key *as* the token | 18:43 |
breton | maybe we should continue the x509 stuff that gyee started some time ago | 18:43 |
breton | it has code ready on the server side | 18:43 |
lbragstad | breton what's left to do there? | 18:43 |
breton | and the only thing that was missing is auth plugins | 18:43 |
lbragstad | ah | 18:43 |
breton | i remember i could validate a token with it | 18:44 |
lbragstad | breton does x509 allow you to delegate subsets of roles? | 18:44 |
breton | lbragstad: i don't remember, probably no. | 18:44 |
breton | but... we have trusts to delegate subset of roles | 18:44 |
lbragstad | we'd have to find a way to get that in there in order for it to be on par with the direction of API keys | 18:45 |
bknudson_ | we could have a header for the roles to include in the token | 18:45 |
bknudson_ | (then we'd have to store the roles in the fernet token) | 18:45 |
lbragstad | rderose the other difference between dstanek's approach and yours is that he requires the roles in the API key to be a subset | 18:46 |
rderose | lbragstad: I see, but I'm not sure why that has to be a hard requirement | 18:46 |
*** pvaneck has quit IRC | 18:46 | |
lbragstad | i think dstanek is out today :( | 18:47 |
lbragstad | it would be nice to have him here for this discussion | 18:47 |
*** pvaneck has joined #openstack-meeting | 18:47 | |
rderose | and I like the approach of request a scope token for now (far less complicated) | 18:47 |
rderose | and not request a scoped token as future work | 18:47 |
rderose | the approach will solve the use case in the spec | 18:47 |
lbragstad | yeah - i guess it depends on what we want this to look like eventually | 18:48 |
lbragstad | we could implement it with using api key as an authentication method/auth plugin | 18:49 |
notmorgan | honestly, i prefer the model where you don't exchange the API key for a token | 18:49 |
lbragstad | notmorgan so a traditional api key | 18:49 |
notmorgan | because that mirrors more accurately what an API-Key in other areas of the industry ends up being | 18:49 |
notmorgan | it is a lot more work to make happen | 18:49 |
lbragstad | true | 18:49 |
notmorgan | changes to KSA, to KSM, and Keystone | 18:49 |
notmorgan | vs just changes to Keystone | 18:49 |
notmorgan | and an auth-plugin for KSA | 18:50 |
notmorgan | you will likely still need to support API-Key for Token | 18:50 |
rderose | notmorgan: I think we can get there, but yeah, to start API-key for token | 18:50 |
lbragstad | if we use api access as an auth plugin, then i'd say we need to name it something different than API key (we can call it whatever we want) | 18:50 |
lbragstad | i just don't want to accidentally advertise API keys when that's not what they are | 18:51 |
notmorgan | i would really prefer to never implement api-key for tokne that is | 18:51 |
rderose | notmorgan: ah | 18:51 |
notmorgan | and yes do not name it "api-key" as the auth method | 18:51 |
rderose | :) | 18:51 |
*** 21WAAS6DN has quit IRC | 18:51 | |
rderose | currently, I've named it 'access-key' | 18:51 |
notmorgan | can we call it something totally not related... | 18:51 |
notmorgan | make up a word | 18:51 |
lbragstad | unicorn-key | 18:51 |
notmorgan | "foobaz-auth-key" | 18:52 |
*** dmorita has quit IRC | 18:52 | |
rderose | haha | 18:52 |
knikolla | not-a-key | 18:52 |
notmorgan | knikolla: veto ;) | 18:52 |
lbragstad | this-is-not-an-api-key-key | 18:52 |
gagehugo | don-key | 18:52 |
notmorgan | anyway | 18:52 |
notmorgan | if we can avoid api-key-for-token it would be much better. however...... | 18:53 |
notmorgan | discovery/catalog would still be needed. | 18:53 |
bknudson_ | could we pass the api key in the password? | 18:53 |
notmorgan | bknudson_: in theory | 18:53 |
notmorgan | but that is something i don't wnat | 18:53 |
henrynash | what’s the rush that means we can’t do the work for a real api key? | 18:53 |
notmorgan | if we can avoid it | 18:53 |
lbragstad | we tried to do something like that with TOTP | 18:54 |
notmorgan | now... let me say this clearly | 18:54 |
notmorgan | Since i am not going to implement this, my view is pretty much just a "what makes sense and mirrors the industry" | 18:54 |
lbragstad | notmorgan so - take the long road and do real api keys? | 18:55 |
bknudson_ | I'm going to need to talk to keystone to get the service catalog. | 18:55 |
notmorgan | API-Key should be used directly in lieu of the keystone-tokne, it should be a subset of roles, and should require an expiration on creation (where 0, or -1 is "never"). it should be revokable by the user. | 18:55 |
rderose | notmorgan: I hear you, but... this would solve the use case and it doesn't prevent us from extending this in the future | 18:55 |
notmorgan | rderose: if we don't ever want real api-keys. do it as an exchange for token | 18:56 |
*** dmorita has joined #openstack-meeting | 18:56 | |
notmorgan | rderose: don't do a short-cut because "it solves the case but is easier" unless that is the mechanism you really want people to use | 18:56 |
*** amotoki has quit IRC | 18:56 | |
lbragstad | then it would be an application specific password - right? | 18:56 |
notmorgan | remember, once it is implemented, it is in keystone *forever* effectively | 18:56 |
notmorgan | lbragstad: pretty much | 18:57 |
notmorgan | i'm fine with application-specific passwords | 18:57 |
notmorgan | its a very different UX than api-keys | 18:57 |
notmorgan | what are we aiming to solve? application-specific-passwords, API-Keys, a specific use-case that is agnostic to that, etc | 18:57 |
lbragstad | another question - for the development cost, what's going to give users and operators more bang for their buck? | 18:58 |
rderose | notmorgan: we're aiming to solve having users put there usernames/passwords in config files which has access to all of the user's roles | 18:59 |
notmorgan | application-specific password would then use trusts *as well* for subsets of roles | 18:59 |
rderose | notmorgan: there isn't really an industry standard around access/api keys | 18:59 |
* breton whispers about time | 19:00 | |
notmorgan | do not lump in a new special password-thing that works totally different from current passwords, if it works like passwords | 19:00 |
notmorgan | use "trusts" in that case. | 19:00 |
lbragstad | breton thanks | 19:00 |
*** zara_the_lemur__ has joined #openstack-meeting | 19:00 | |
lbragstad | and we're out of time, let's take this to -keystone | 19:00 |
lbragstad | #endmeeting | 19:00 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 19:00 | |
openstack | Meeting ended Tue Mar 14 19:00:32 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 19:00 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-03-14-18.00.html | 19:00 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-03-14-18.00.txt | 19:00 |
openstack | Log: http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-03-14-18.00.log.html | 19:00 |
*** gagehugo has left #openstack-meeting | 19:00 | |
clarkb | fungi: is it time? | 19:01 |
fungi | infra team, i summon you | 19:01 |
fungi | so it seems | 19:01 |
zara_the_lemur__ | o/ | 19:01 |
* jeblair arrives with sandwich | 19:02 | |
cmurphy | hi o/ | 19:02 |
ianw | hello | 19:02 |
zaro | O/ | 19:02 |
fungi | behold, this week we have action items assigned to and topics proposed by pabelanger, jeblair, clarkb | 19:02 |
fungi | #startmeeting infra | 19:03 |
openstack | Meeting started Tue Mar 14 19:03:39 2017 UTC and is due to finish in 60 minutes. The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot. | 19:03 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 19:03 |
*** openstack changes topic to " (Meeting topic: infra)" | 19:03 | |
openstack | The meeting name has been set to 'infra' | 19:03 |
fungi | #link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting | 19:03 |
fungi | #topic Announcements | 19:04 |
*** openstack changes topic to "Announcements (Meeting topic: infra)" | 19:04 | |
*** olaph has joined #openstack-meeting | 19:04 | |
fungi | i don't have any this week | 19:04 |
fungi | as always, feel free to hit me up with announcements you want included in future meetings | 19:04 |
*** dmorita has quit IRC | 19:04 | |
fungi | #topic Actions from last meeting | 19:04 |
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)" | 19:04 | |
fungi | #link http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-03-07-19.01.htm | 19:05 |
fungi | pabelanger to send ML post to get more feedback on our current run-tox playbooks / role | 19:05 |
fungi | i want to say i read it cover to cover | 19:05 |
jeblair | fungi: then say it! | 19:06 |
fungi | #link http://lists.openstack.org/pipermail/openstack-infra/2017-March/005230.html Feedback requested for tox job definition | 19:06 |
fungi | looks done to me | 19:06 |
jhesketh | o/ | 19:06 |
*** Shrews has joined #openstack-meeting | 19:07 | |
fungi | pabelanger: per yesterday's zuul meeting, you're no longer blocked on that, right? | 19:07 |
*** csomerville has joined #openstack-meeting | 19:07 | |
pabelanger | fungi: right, we are merged | 19:07 |
fungi | #link http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-03-13-22.02.log.html#l-120 Status updates: Zuul sample jobs | 19:08 |
fungi | cool | 19:08 |
fungi | #topic Specs approval: PROPOSED Zuul v3: remove references to swift (jeblair) | 19:08 |
*** openstack changes topic to "Specs approval: PROPOSED Zuul v3: remove references to swift (jeblair) (Meeting topic: infra)" | 19:08 | |
*** ociuhandu has quit IRC | 19:09 | |
*** henrynash has quit IRC | 19:09 | |
fungi | #link https://review.openstack.org/443984 Zuul v3: remove references to swift | 19:09 |
jeblair | oh thanks | 19:09 |
jeblair | i was looking for that link under my sandwich | 19:09 |
jeblair | this is pretty short. we talked about it at the ptg, and a little in irc since then | 19:10 |
*** cody-somerville has quit IRC | 19:10 | |
jeblair | the gist is that we think sending logs to swift is a thing people will still probably want to do, but we don't need built-in support in zuul for it | 19:10 |
fungi | any feel for whether there are downstreams relying on that feature? | 19:10 |
jeblair | so we can drop that from the spec, and later add it back to what we're calling the 'standard library' | 19:10 |
fungi | ahh, right, can just be in a role/playbook | 19:10 |
fungi | seems entirely non-contentious to me | 19:11 |
fungi | anyone object to opening council voting on this until 19:00 utc thursday? | 19:11 |
jeblair | i think based on informal conversations, it's ready for vote | 19:11 |
fungi | #info Council voting is open on "Zuul v3: remove references to swift" until 19:00 UTC Thursday, March 16 | 19:12 |
fungi | looks like it also depends on some silly whitespace fixes | 19:12 |
jeblair | they are absolutely critical. | 19:12 |
fungi | which are now approved | 19:13 |
*** henrynash has joined #openstack-meeting | 19:13 | |
fungi | #topic Specs approval: PROPOSED Zuul v3: update job trees to graphs (jeblair) | 19:13 |
*** henrynash has quit IRC | 19:13 | |
*** openstack changes topic to "Specs approval: PROPOSED Zuul v3: update job trees to graphs (jeblair) (Meeting topic: infra)" | 19:13 | |
fungi | #link https://review.openstack.org/443985 Zuul v3: update job trees to graphs | 19:14 |
*** henrynash has joined #openstack-meeting | 19:14 | |
jeblair | this also has a follup clarification which i don't think needs its own vote, but it may be helpful to look at it since it makes the example more clear | 19:14 |
jeblair | #link https://review.openstack.org/445022 Zuulv3: clarify job dependencies example | 19:14 |
*** kaisers_ has quit IRC | 19:15 | |
jeblair | this one is substantial -- it changes the job and project-pipeline definition syntax | 19:15 |
*** henrynash has quit IRC | 19:15 | |
jeblair | it also has an implementation based on a patch which was proposed to the master branch some time ago | 19:15 |
jeblair | so you can see it in action | 19:15 |
fungi | while a small part of me feels like this is scope creep, it was apparently stated that this would be a part of zuul v3 and as it's basically already written, i don't see any reason to object | 19:15 |
*** henrynash has joined #openstack-meeting | 19:16 | |
jeblair | yeah, we probably should have put at least a placeholder in the spec earlier to say "we're going to do this but we don't know what the syntax will look like yet". sorry about that. | 19:16 |
jeblair | before v3.0 is definitely the time to do this though, since it's a major configuration syntax change. we won't have any users left if we put them through two of those. | 19:17 |
fungi | right, that's the best argument in favor for me. much harder to do after the big bang syntax change | 19:17 |
fungi | anyone object to opening council voting on this until 19:00 utc thursday? | 19:17 |
jeblair | (the main thing to note in the spec update is that we lose the ability to structure jobs in a yaml tree. so you don't *visually* see the dependencies in the config file. but you are able to express them fairly easily, and of course it allows more topologies than before.) | 19:18 |
clarkb | no objection here. I think i have already voted positively on this one | 19:18 |
fungi | #info Council voting is open on "Zuul v3: update job trees to graphs" until 19:00 UTC Thursday, March 16 | 19:19 |
fungi | seemed pretty consensual in the zuul subteam meeting yesterday anyway | 19:19 |
fungi | #topic Priority Efforts | 19:19 |
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)" | 19:19 | |
fungi | i don't see any specific updates/blockers for these called out in the agenda | 19:20 |
*** henrynash has quit IRC | 19:20 | |
*** antwash has left #openstack-meeting | 19:20 | |
fungi | i know that the task tracker and zuul v3 work are proceeding, and zaro was inquiting about some of the testing prerequisites for the gerrit upgrade just before the meeting | 19:20 |
fungi | at some point we likely need to revisit the ansible puppet apply spec and see whether whatever's remaining on it is still a priority | 19:21 |
*** nadya has joined #openstack-meeting | 19:21 | |
*** artom has quit IRC | 19:22 | |
fungi | #topic Zuulv3 sample jobs (pabelanger) | 19:22 |
*** openstack changes topic to "Zuulv3 sample jobs (pabelanger) (Meeting topic: infra)" | 19:22 | |
fungi | is this a holdover from last week? | 19:22 |
fungi | looks like the thing which spawned the action item | 19:23 |
pabelanger | it is, sorry for not deleting it from the wiki | 19:23 |
fungi | no problem, sorry for not cleaning up the agenda )or paying close enough attention to last week's meeting minutes) | 19:23 |
*** raildo_ has joined #openstack-meeting | 19:23 | |
fungi | #topic Plan sprint for getting off precise. Should happen within the next month or so. (clarkb) | 19:23 |
*** openstack changes topic to "Plan sprint for getting off precise. Should happen within the next month or so. (clarkb) (Meeting topic: infra)" | 19:23 | |
clarkb | ohai | 19:23 |
fungi | this looks fresh, or at least worth rediscussing | 19:23 |
clarkb | one of the things we siad pre ptg was that we should have a sprint to finish up the precise cleanup (and possibly work on xenialification) | 19:24 |
*** aysyd has joined #openstack-meeting | 19:24 | |
clarkb | precise EOL is a month away or so so we should work on that | 19:24 |
pabelanger | yes, we talked a little about this last week in open discussions | 19:24 |
pabelanger | thanks for bringing it up again | 19:24 |
*** henrynash has joined #openstack-meeting | 19:25 | |
clarkb | ah ok, I missed last week (I guess i hsould've checked logs) | 19:25 |
clarkb | was a time frame selected? I think we likely need at least several days | 19:25 |
*** leanderthal|afk has quit IRC | 19:25 | |
pabelanger | no, we didn't select a date | 19:25 |
clarkb | I'm basically wide open between now and summit (no planned travel) | 19:26 |
fungi | i won't be able to pitch in a week from tomorrow (wednesday the 22nd) as i have a prior obligation which will occupy most of my day | 19:26 |
fungi | aside from that i don't have any more travel until april 10th | 19:26 |
pabelanger | I should be good anytime between now and summit | 19:26 |
*** raildo has quit IRC | 19:27 | |
pabelanger | no travel on the books | 19:27 |
clarkb | maybe we can target next week and just deal with fungi being out :) | 19:27 |
clarkb | I think sooner we start working on this the better | 19:27 |
fungi | almost a month with no travel for me--quite thrilled | 19:27 |
*** raildo_ has quit IRC | 19:27 | |
zara_the_lemur__ | nice | 19:27 |
jeblair | do we have a list handy? | 19:27 |
fungi | well, i'm only out one day. i'll happily work on it the rest of the week if that's the plan | 19:27 |
*** raildo has joined #openstack-meeting | 19:28 | |
ianw | i'm around (in au time) and happy to help on this too | 19:28 |
clarkb | I don't have a list handy, but shouldn't be had to get one from ansible/puppet? | 19:28 |
jeblair | might be helpful to estimate how many days | 19:29 |
clarkb | good point | 19:29 |
* fungi remembers the days when he could just pull that up in puppetboard | 19:29 | |
clarkb | fungi: me too :( | 19:29 |
fungi | speaking of servers still running on precise... | 19:29 |
fungi | (for some definitions of "running in this case) | 19:29 |
*** raildo has quit IRC | 19:29 | |
clarkb | https://etherpad.openstack.org/p/newton-infra-distro-upgrade-plans found our old etherpad | 19:30 |
fungi | perfect. if anybody's deployed anything at all on precise since then, they're clearly not paying attention | 19:30 |
fungi | wiki can come off that list | 19:30 |
clarkb | lists, static, planet, puppetd, wiki, zuul. And pretty sure soe of those are done | 19:31 |
fungi | zuul is now trusty, just checked | 19:31 |
clarkb | static is done too | 19:31 |
fungi | so that brings us to lists, planet and puppetdb (puppetboard) | 19:32 |
clarkb | yup | 19:32 |
clarkb | and I checked those all are precise | 19:32 |
jeblair | is puppetdb still useful? | 19:32 |
fungi | it's so very, very broken | 19:32 |
clarkb | planet wants an upgrade to xenial iirc | 19:32 |
fungi | yeah | 19:32 |
clarkb | jeblair: I think if the service could be made to work yes | 19:32 |
pabelanger | ci-backup according to site.pp | 19:32 |
pabelanger | jeblair: not to me | 19:32 |
fungi | pabelanger: oh, i think there is an upgraded one for that which hasn't been switched into production yet? | 19:33 |
clarkb | jeblair: the use case we need from something like it is reporting to humans that are not roots so they cansee when their changes happen | 19:33 |
pabelanger | fungi: not sure, site.pp just lists precise | 19:33 |
jeblair | clarkb: but only if they look quickly, before the next 10 runs | 19:33 |
clarkb | jeblair: yes. Not sure puppetboard is the best way to solve that problem. But its the problem we'd like to have solved | 19:34 |
fungi | well, in this case i say it's "not useful" because it's completely and thoroughly offline for a year or more now | 19:34 |
jeblair | i vote we drop it. i'd love the use case to be handled, but we should stop pretending it is. :| | 19:34 |
fungi | perpetual "internal server error" | 19:34 |
fungi | yeah, i won't object to someone redeploying it and getting it working, we can keep the config management around for it | 19:34 |
*** raildo has joined #openstack-meeting | 19:35 | |
*** ociuhandu has joined #openstack-meeting | 19:35 | |
fungi | but it's not like deleting the current precise host it's un-running on will be a regression | 19:35 |
clarkb | right | 19:35 |
clarkb | so mostly lists and planet then | 19:35 |
fungi | yup. lists is tricksy because we'll need to defer inbound messages on a secondary mx (ideally) while we test out the replacement with copied (migrated?) data | 19:36 |
pabelanger | interwebs not great for me currently | 19:36 |
fungi | planet should be a relative non-event since there's no persistent data. just need to get it working (on xenial i guess?) and then switch dns | 19:37 |
clarkb | fungi: jeblair (email noob here) couldn't we set up a second MX record for ne whost with higher priority which would cause senders to fall back on existing host until ne whost existed? | 19:37 |
clarkb | is problem in syncing the data in mailmain? | 19:38 |
jeblair | fungi: well, we don't really need a secondary mx if the downtime is small (say < 30m). | 19:38 |
*** X-dark_ has joined #openstack-meeting | 19:38 | |
fungi | i'm not sure the term "sprint" is really applicable here, but we do need one or (preferably) more people carefully planning the lists switch and then pre-testing the replacement | 19:38 |
jeblair | sending servers don't usually generate bounces for connection errors until they persist a while | 19:38 |
*** henrynash has quit IRC | 19:38 | |
fungi | right, holding the inbound queue on a secondary mx would really only be necessary if we can't make the switch (including dns propagation) happen in a reasonably short timeframe | 19:39 |
jeblair | but if we did want no interruption in mx service, we could probably just have the existing one queue and then deliver to the new host. | 19:39 |
*** X-dark has quit IRC | 19:40 | |
*** X-dark_ is now known as X-dark | 19:40 | |
jeblair | downside for that is it's an extra bit of mta configuration that needs its own testing | 19:40 |
fungi | true, and that's only a few lines of exim config | 19:40 |
fungi | but right, we'd probably want to test it somewhere else beforehand | 19:40 |
clarkb | I think we can take a few minutes downtime for queuing | 19:40 |
jeblair | the worst part of this is that we will lose our ip and its reputation | 19:41 |
fungi | so maybe we should just take volunteers to work on the planet replacement and to work on the lists replacement and maintenance plan? | 19:41 |
clarkb | and worst worst case some small number of people might need to resend their emails? | 19:41 |
clarkb | jeblair: we could try an upgrade in place... | 19:42 |
jeblair | yeah. we can practice with snapshots. | 19:42 |
fungi | it worked reasonably well for the wiki server | 19:42 |
fungi | and while that would preserve our ip address, it's fairly out of character for us to upgrade that way | 19:43 |
clarkb | having had ubuntu lts' installs upgraded in place over years it ends up being pretty messy | 19:43 |
fungi | but worth considering nonetheless | 19:43 |
clarkb | but functional | 19:43 |
clarkb | jeblair: how important is that reputation? do you expect we will end up being rejected by a bunch of MXes if we change IPs? | 19:44 |
fungi | worth noting, i strongly suspect a redeploy from scratch will end up renotifying all the listadmins in the lists class manifest about their lists being created (along with the default listadmin password) | 19:45 |
ianw | probably depends on who had that IP before :) | 19:45 |
jeblair | clarkb: it would not surprise me if it took a few days or a week to settle out. | 19:45 |
fungi | yeah, quite the gamble | 19:45 |
jeblair | rackspace's vetting usually means we're not getting spammer ips, but still. | 19:45 |
fungi | #link https://www.senderbase.org/lookup/?search_string=lists.openstack.org | 19:46 |
ianw | i can take bringing up a xenial planet if you like; i maintained a planet in a previous life | 19:46 |
clarkb | so probably worht testing the inplace upgrade with a snapshot then? | 19:46 |
fungi | email rep. is "good" for both ipv4 and ipv6 addresses | 19:46 |
fungi | ianw: awesome, pleia2 indicated it should be viable on xenial, we just weren't quite ready to run xenial servers yet at that time | 19:47 |
jeblair | yeah, i'm thinking in-place may be worth trying for this. | 19:47 |
fungi | no objection here | 19:47 |
pabelanger | worth a try | 19:47 |
fungi | #action ianw try booting a Xenial-based replacement for planet.openstack.org | 19:47 |
ianw | it's pretty much the same mailman version right? | 19:48 |
fungi | #agreed We'll attempt an in-place upgrade of lists.openstack.org from Precise to Trusty, practicing on instance snapshots beforehand | 19:48 |
*** dmorita has joined #openstack-meeting | 19:48 | |
clarkb | ianw: yes precise -> trusty mailman is baically the same | 19:48 |
fungi | #link http://packages.ubuntu.com/mailman | 19:48 |
clarkb | 2.1.14 -> 2.1.16 | 19:49 |
ianw | yep, that's good, not also shoehorning a v3 upgrade on top :) | 19:49 |
fungi | last news i read, mmv3 is still in a questionable state | 19:49 |
ianw | yeah, that was what i thought too, with all the configuration being quite different | 19:50 |
clarkb | is that something people will be able to work on soon? | 19:50 |
clarkb | any volunteers to work on mailman? I can help there but am definitely not an email expert | 19:50 |
fungi | if we're already incurring the pain on precise->trusty, do we want to follow that with a trusty->xenial in short order? anybody remember which release got the dmarc workaround patches? | 19:50 |
jeblair | clarkb: i will volunteer to help | 19:51 |
clarkb | fungi: I think we may want to do a single in place upgrade, evaluate how that went. Then decide from there if we want to d oa second to xenial | 19:51 |
fungi | #link https://wiki.list.org/DEV/DMARC says 2.1.26 added frim_is_list | 19:51 |
jeblair | better yet, i *do* volunteer to help | 19:51 |
fungi | #undo | 19:51 |
openstack | Removing item from minutes: #link https://wiki.list.org/DEV/DMARC | 19:51 |
fungi | #link https://wiki.list.org/DEV/DMARC says 2.1.16 added frim_is_list | 19:51 |
clarkb | fungi: oh 2.1.16 is what precise has so maybe thats less urgent? | 19:52 |
fungi | so trusty should get us dmarc-related options without needing to consider xenial quite yet | 19:52 |
fungi | yep | 19:52 |
fungi | 2.1.18 added some more stuff though per that wiki | 19:52 |
clarkb | (I think we should also work to xenialify in the near future too, but don't want to make the goalposts to far ahead since precise is eol real soon now) | 19:52 |
fungi | xenial would get us 2.1.20 | 19:52 |
jeblair | to be honest, i'm not sure we should enable that option | 19:53 |
fungi | i too am fine with sticking to our guns on ignoring dmarc | 19:53 |
fungi | some listservs i've got subscriptions on have decided to unsubscribe and block subscribers from affected domains instead | 19:53 |
fungi | well, block posts from | 19:53 |
jeblair | that is appropriate and consistent with what those domains have expressed as their policy via dmarc. | 19:54 |
jeblair | i'm intrigued by the 2.1.18 dmarc behaviors. i'll have to think about that a bit. | 19:54 |
fungi | yea, half the blame is on dmarc-asserting domains for not telling their users they shouldn't post to mailing lists, and the other half on dmarc-validating mtas on ignoring the incompleteness which is dmarc | 19:55 |
jeblair | i'm going to spend the rest of the day trying to shoehorn "systemdmarc" into a sentence somehow. | 19:56 |
fungi | so anyway, i can volunteer to help on the lists.o.o stuff too (i feel fairly confident with its cil utilities, pickle file manipulating tool and archive filesystem layout), though i worry i don't have time to drive the effort | 19:56 |
fungi | jeblair: i'm sure lennart already has a plan for that one | 19:57 |
clarkb | do we wnat to pick a specific time next week to work on this further or let volunteers poke at it as they are able? | 19:57 |
*** cdent has joined #openstack-meeting | 19:57 | |
clarkb | I guess jeblair and ianw can grab fungi and me for help as needed and go from there? | 19:58 |
fungi | or is there any other infra-root who wants to gain a deeper understanding for mailman? | 19:58 |
fungi | there's nothing like the stress of an upgrade to hammer home key concepts ;) | 19:58 |
* Shrews hides in the darkest corner | 19:58 | |
jeblair | fungi, clarkb: maybe let's poke at it as able, but plan on spending thurs-fri next week making real headway if we don't before then? | 19:58 |
clarkb | jeblair: ++ | 19:58 |
fungi | jeblair: i'm happy to commit to that | 19:59 |
ianw | are we defaulting to rax as a provider for these hosts? | 19:59 |
ianw | well clearly the inplace upgrade stays | 19:59 |
clarkb | ianw: for lists yes due to IP | 19:59 |
*** ihrachys has quit IRC | 19:59 | |
jeblair | (hopefully that gives us some time to asynchronously make some snapshots, etc). maybe keep an etherpad with a work log. | 19:59 |
fungi | that's a good question we don't have time to answer in the next 30 seconds | 19:59 |
clarkb | planet could potentially be hosted by vexxhost? | 19:59 |
fungi | i'm fine with that idea | 19:59 |
*** gordc has joined #openstack-meeting | 19:59 | |
jeblair | no objections to planet vexxhost | 19:59 |
*** hashar has joined #openstack-meeting | 20:00 | |
fungi | obviously the plan for lists.o.o is rackspace for now since we're doing in-place | 20:00 |
fungi | and we're out of time | 20:00 |
fungi | thanks everyone! | 20:00 |
fungi | #endmeeting | 20:00 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 20:00 | |
openstack | Meeting ended Tue Mar 14 20:00:17 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 20:00 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-03-14-19.03.html | 20:00 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-03-14-19.03.txt | 20:00 |
openstack | Log: http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-03-14-19.03.log.html | 20:00 |
ttx | ohai | 20:00 |
fungi | all yours, tc | 20:00 |
*** Shrews has left #openstack-meeting | 20:00 | |
fungi | why, thank you, infra! | 20:00 |
sdague | o/ | 20:00 |
johnthetubaguy | o/ | 20:00 |
dtroyer | o/ | 20:00 |
EmilienM | o/ | 20:00 |
ttx | dhellmann, dims, flaper87, mordred, stevemar: around ? | 20:00 |
* edleafe finds a comfortable chair | 20:01 | |
ttx | mtreinish is on a plane, or sleeping, or both | 20:01 |
ttx | thingee is out too | 20:01 |
dhellmann | o/ | 20:01 |
sdague | on a plane, he got out before the snow storm in NY | 20:01 |
ttx | #startmeeting tc | 20:01 |
openstack | Meeting started Tue Mar 14 20:01:24 2017 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. | 20:01 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 20:01 |
*** openstack changes topic to " (Meeting topic: tc)" | 20:01 | |
openstack | The meeting name has been set to 'tc' | 20:01 |
dims | o/ | 20:01 |
ttx | Hi everyone! | 20:01 |
* lbragstad finds the next most comfy chair next to edleafe | 20:01 | |
ttx | Our agenda for today is at: | 20:01 |
* mugsie lurks | 20:01 | |
ttx | #link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee | 20:01 |
ttx | We have three big sections | 20:01 |
ttx | #topic New working groups | 20:01 |
*** openstack changes topic to "New working groups (Meeting topic: tc)" | 20:01 | |
ttx | I'm a bit torn on those, as I really don't want to make it look like you need to apply to the TC in order to set up a working group | 20:02 |
ttx | I mean, anyone should be able to form a group on anything | 20:02 |
ttx | I get that a formal resolution gives the group some weight though, which is why the Stewardship WG was created from a TC resolution | 20:02 |
fungi | (and in fact they do, often) | 20:02 |
ttx | Opinions on that, before we dive in the specific requests ? | 20:02 |
sdague | yeh, my feeling is people should just start gathering and doing useful things | 20:02 |
EmilienM | +1 | 20:02 |
dtroyer | I generally agree | 20:02 |
johnthetubaguy | I don't want to make a resolution required | 20:02 |
EmilienM | ttx: I can abandon mine if it makes no sense and just keep Wiki updated | 20:02 |
johnthetubaguy | but then I do like the TC saying something is important, and needs addressing | 20:03 |
sdague | it feels like TC appoval ends up making these look like permanent institutions, vs. people coming together to solve things | 20:03 |
fungi | any time we create a new list of things in governance, people will want to try to add to it | 20:03 |
sdague | fungi: ++ | 20:03 |
johnthetubaguy | sdague: thats a good point | 20:03 |
dtroyer | I guess the question to the authors is "what might make these worth the exception"? | 20:03 |
ttx | EmilienM: we could maintain a registry of the workgroups but it feels overkill too | 20:03 |
*** ociuhandu has quit IRC | 20:03 | |
EmilienM | yeah | 20:03 |
dhellmann | I do think there will be cases where we want to "charter" working groups, but both of these cases feel like we could skip that step | 20:03 |
johnthetubaguy | ttx: although the UC was talking about the issues they had without a registry | 20:03 |
ttx | johnthetubaguy: ah ? | 20:03 |
dhellmann | a registry makes a lot of sense to improve discoverability | 20:04 |
dtroyer | a directory? | 20:04 |
dhellmann | and that doesn't need to be in the governance repo | 20:04 |
dtroyer | less official sounding | 20:04 |
sdague | so, I think the real issues are, if people are coming together to solve a thing: a) how does anyone discover they exist? b) how would one get involved if they wanted to c) what do those folks see as their scope | 20:04 |
johnthetubaguy | them mentioned at the board meeting, they found it hard having no ... directory I guess | 20:04 |
ttx | We could list them on the governance website | 20:04 |
fungi | a registry for the uc is somewhat necessary, as it factors into their electorate | 20:04 |
*** ihrachys has joined #openstack-meeting | 20:04 | |
johnthetubaguy | I mean a wiki page would totally work | 20:04 |
ttx | but that means extar review | 20:04 |
sdague | a wiki page solves it all except discovery | 20:04 |
dtroyer | ++ | 20:04 |
johnthetubaguy | fungi: true | 20:04 |
ttx | We can point to the wiki page from the governance website | 20:04 |
dhellmann | we could link to the wiki from the governance site, or we could share a registry with the uc | 20:04 |
ttx | avoids crazy reviewing | 20:04 |
fungi | would we want to extend separate election privileges to "active" members of these working groups who are not already active technical contributors through other means? | 20:05 |
johnthetubaguy | ttx: yeah was about to type the same | 20:05 |
persia | If the need for a directory is partially driven by UC electorate concerns, might it make sense for the UC to perform the reviews to extend the directory? | 20:05 |
dhellmann | persia : the uc has its own working groups | 20:05 |
*** lpetrut has quit IRC | 20:05 | |
dtroyer | I like the combination of linking to the wiki from governance, it seems to strike the right official vs "just do it balance" | 20:05 |
ttx | ok, let's dive into each specifically | 20:05 |
ttx | #topic Propose VM and Bare-metal Platform Working Group | 20:05 |
*** openstack changes topic to "Propose VM and Bare-metal Platform Working Group (Meeting topic: tc)" | 20:05 | |
ttx | #link https://review.openstack.org/442387 | 20:05 |
ttx | johnthetubaguy: want to introduce this ? | 20:05 |
johnthetubaguy | so this really is an thing that keep coming up over beer | 20:06 |
johnthetubaguy | get a group to worry about the VM + baremetal platform | 20:06 |
ttx | workgroups: no resolution needed, but beer welcome | 20:06 |
johnthetubaguy | :) | 20:06 |
johnthetubaguy | there are a few problems that keep coming | 20:06 |
johnthetubaguy | up | 20:06 |
johnthetubaguy | mostly user experience related | 20:07 |
johnthetubaguy | both in the human and machine case | 20:07 |
johnthetubaguy | humans using REST APIs, horizon, etc | 20:07 |
ttx | sure, feels like a good vehicle to solve inter-project pains within that platform | 20:07 |
*** armax has quit IRC | 20:07 | |
fungi | it sounds like there are already people who worry about this, so the point is to just provide some rallying point for them? | 20:07 |
johnthetubaguy | yeah, its more about looking at the whole problem, and priorities between the efforts | 20:07 |
ttx | fungi: also creates some inter-PTL agreement on priorities | 20:07 |
johnthetubaguy | one example, I think we should work together to work out what needs to happen at the forum for that set of use cases | 20:08 |
dhellmann | how is this group different from the architecture working group? | 20:08 |
* jroll sneaks in the back, late | 20:08 | |
cdent | on the topic of having groups be something that involves tc application: a win from that is that it is easier to get support from an employer to spend time on it when it is officially sanctioned | 20:08 |
johnthetubaguy | dhellmann: the main thing here, is the reduced scope | 20:08 |
mugsie | or API-WG ? | 20:08 |
ttx | dhellmann: arguably a VM+Baremetal platform focused Arch WG | 20:08 |
dhellmann | cdent : good point | 20:08 |
mugsie | (for the eaxmple of humans using a rest API) | 20:08 |
dhellmann | johnthetubaguy : how are conflicting decisions between the two groups resolved? | 20:08 |
*** ihrachys has quit IRC | 20:08 | |
dims | johnthetubaguy : how does the TC stamp help? (curious) | 20:08 |
johnthetubaguy | discussions between the groups | 20:09 |
ttx | cdent: could make it worth the pain of maintaining the list as a governance doc, good point | 20:09 |
lbragstad | would everything the done by the PWG fall under the umbrella of the API or Arch WG? | 20:09 |
johnthetubaguy | so the TC stamp here, was more to identify a set of problems that need attention | 20:09 |
dhellmann | dims : we've had plenty of companies only give permission for folks to work on "official" projects | 20:09 |
sdague | johnthetubaguy: ok, so the API-WG started with a rough plan and 3 people | 20:09 |
fungi | cdent: if it gets employer support to work more upstream, i'm happy to rubber stamp numerous taskforce resolutions ;) | 20:09 |
ttx | dhellmann: I suspect conflicting decisions don't get solved | 20:09 |
dims | dhellmann : ack | 20:09 |
johnthetubaguy | sdague: yep, I think thats what this needs too | 20:09 |
sdague | I guess my practical question is who are the key players here besides yourself? | 20:09 |
dhellmann | ttx: or they come up to the tc? | 20:09 |
ttx | dhellmann: yes | 20:09 |
cdent | (sorry for making that statement after we had moved on a bit, but I had been pulled away momentarily) | 20:09 |
sdague | because, I think we still have the johnthetubaguy's not allowed to sign up for more things by himself rule enforced on alternate tuesdays | 20:10 |
johnthetubaguy | sdague: not got commitment from folks yet | 20:10 |
johnthetubaguy | sdague: heh, that should be a thing | 20:10 |
dhellmann | in the past, we've also said we wanted new groups to show that they're actually doing work before approving them. does that apply to working groups, too? | 20:10 |
johnthetubaguy | dhellmann: that makes sense | 20:10 |
sdague | dhellmann: yes please | 20:11 |
dims | ++ dhellmann | 20:11 |
*** kaisers_ has joined #openstack-meeting | 20:11 | |
johnthetubaguy | so there is one piece that I wanted to check we are in agreement | 20:11 |
dhellmann | and for the record, I think it's fine to have a group doing this, I just want to work out whatever approval process details we need worked out | 20:11 |
sdague | the last thing I want to see is a ton of shadow governance locks on problems | 20:11 |
dhellmann | right | 20:11 |
ttx | at the same time I don't want to spend time vetting working groups | 20:11 |
dhellmann | that doesn't seem like a good use of our time, no | 20:12 |
ttx | they just should not exist if they are not doing things | 20:12 |
fungi | to sdague's point, it would be unfortunate to approve a working group who ends up having no time to commit to the issue at hand, but ends up preventing others who are available from making progress on the same problem space themselves | 20:12 |
*** david-lyle_ is now known as david-lyle | 20:12 | |
sdague | right, which is why I kind of think staying out of blessing is best. It was a long time before the api-wg became "official" | 20:12 |
johnthetubaguy | so my idea was more to identify these problems need fixing | 20:12 |
johnthetubaguy | a resolution is probably a poor way of doing it | 20:12 |
cdent | johnthetubaguy: that list of issues is a good one | 20:13 |
johnthetubaguy | it feels good if we as the TC can flag those things up | 20:13 |
dhellmann | it may work better to start a ML thread and ask people who are interested in solving those issues to self-organize | 20:13 |
*** e0ne has joined #openstack-meeting | 20:13 | |
mugsie | dhellmann: ++ | 20:13 |
sdague | johnthetubaguy: honestly, I'd be totally happy if we took that list of issues, made an attempt at 1-N prioritization | 20:13 |
sdague | and if a collection of people show up to help there, ++ | 20:13 |
ttx | johnthetubaguy: it feels like you should define your set of issues, start working... and if you need the TC to point to you and say: "that's a good thing" there are a variety of ways to do it | 20:13 |
johnthetubaguy | sdague: who is we in this context | 20:13 |
johnthetubaguy | sdague: yeah, in the working group, if it becomes a thing | 20:13 |
dhellmann | right, if we need resolutions to codify specific decisions or something, we could do that | 20:14 |
sdague | johnthetubaguy: well, you, and perhaps the TC stamping the issue list | 20:14 |
johnthetubaguy | ttx: yes, I was just wondering if we as a TC should do something to high light the issues, frankly this discussion is probably enough | 20:14 |
fungi | perhaps simply making the "membership" or working groups fluid is sufficient to allow others to pick up the work without having to get some institutionalized group to relinquish it first? | 20:14 |
johnthetubaguy | sdague: OK, I see what you mean, propose the list, and maybe stamp it, that makes sense | 20:14 |
dims | i like the idea of TC saying this stuff needs attention | 20:14 |
ttx | johnthetubaguy: you could request some time to present the WG issues to the TC and have some pile of +1s | 20:14 |
sdague | because I think that's a very good starting point of key issues with the openstack platform | 20:14 |
cdent | dims++ | 20:14 |
johnthetubaguy | dims: thats the bit I am wondering about how we would do that | 20:15 |
dhellmann | iirc, last week the idea of some sort of priority list that wasn't tied to the goals process did come up | 20:15 |
sdague | that aren't horizontal, or vertical, but much more usage based | 20:15 |
ttx | johnthetubaguy: just ask for some time at a TC meeting and present* | 20:15 |
ttx | then I'm happy to pile it +1s | 20:15 |
sdague | and solving any single one of those would make openstack as whole better | 20:15 |
dims | ++ sdague | 20:15 |
ttx | pile up* | 20:15 |
johnthetubaguy | so maybe the key bit I am getting here, is "this is not crazy" | 20:16 |
ttx | we could also have that list of issues and "delegate" it to wgs | 20:16 |
fungi | not crazy, but maybe we lack the framework to slot this and similar priorities into? | 20:16 |
johnthetubaguy | I will try run with this to the ML, and see if there is a motley crew keen to work on this | 20:16 |
dhellmann | oh, yeah, the issue list idea came up with finding ways for new contributors to engage constructively, instead of through typo patches | 20:16 |
ttx | I basically prefer that we support the WGs rather than bless them | 20:17 |
mugsie | ls | 20:17 |
dhellmann | right | 20:17 |
johnthetubaguy | I quite like the flagging issues that need solving bit | 20:17 |
* fungi certainly doesn't want to have to get ordained | 20:17 | |
ttx | johnthetubaguy: ok so next step is to raise a ML thread. We can discuss visibility of a WG registry separately | 20:17 |
johnthetubaguy | yeah, we should move on | 20:18 |
dhellmann | and then someone needs to start a storyboard list of those issues :-) | 20:18 |
*** e0ne has quit IRC | 20:18 | |
ttx | #info Workgroup should get set up on the ML. TC is happy to supprot and encourage the work of the workgroup | 20:18 |
jroll | I like this | 20:18 |
dims | johnthetubaguy : throw in a etherpad | 20:18 |
EmilienM | ttx: +1 | 20:18 |
ttx | #info potential future work: how to maintain list of WGs and ensure discoverability, and a blessed list of high-value targets | 20:19 |
ttx | #topic Propose Deployment Working Group (DWG) | 20:19 |
*** openstack changes topic to "Propose Deployment Working Group (DWG) (Meeting topic: tc)" | 20:19 | |
ttx | #link https://review.openstack.org/442761 | 20:19 |
ttx | EmilienM: want to introduce this one ? | 20:19 |
EmilienM | #action EmilienM to transform https://review.openstack.org/#/c/442761 into a ML thread to communicate about this new WG and what we plan to do | 20:19 |
ttx | although I suspect it will meet the same fate | 20:19 |
EmilienM | ttx: no need to spend time on it IMHO | 20:20 |
fungi | it's like we just had most of this discussion already! ;) | 20:20 |
ttx | EmilienM: for the record, I like that workgroup too. | 20:20 |
sdague | ttx: ++, great start there EmilienM | 20:20 |
EmilienM | I like the fact you like :) | 20:20 |
fungi | it seems to already have more or less formed, based on discussions of related topics i've seen on the ml over the past couple weeks | 20:20 |
ttx | we need more of those interproject groups | 20:20 |
EmilienM | fungi: ++ indeed | 20:20 |
johnthetubaguy | yeah, seems like a good thing to do there too | 20:20 |
ttx | ok, moving on | 20:21 |
ttx | #topic Describe what upstream support means | 20:21 |
*** openstack changes topic to "Describe what upstream support means (Meeting topic: tc)" | 20:21 | |
ttx | #link https://review.openstack.org/440601 | 20:21 |
ttx | johnthetubaguy: you again | 20:21 |
dhellmann | ttx: another justification for some sort of registry may be to know which groups to ask about PTG and Forum space | 20:21 |
ttx | dhellmann: ack | 20:21 |
dhellmann | it could still be a wiki page | 20:21 |
fungi | dhellmann: i completely concur there | 20:21 |
*** e0ne has joined #openstack-meeting | 20:21 | |
johnthetubaguy | so this came up in the postgresSQL discussion | 20:21 |
johnthetubaguy | "supported upstream" is a strange phrase right now | 20:22 |
*** nadya has quit IRC | 20:22 | |
johnthetubaguy | so I attempted to write down some ideas | 20:22 |
ttx | I like it -- still a bit of polishing work needed | 20:22 |
johnthetubaguy | seeing some good comments from ttx and dtroyer on there | 20:22 |
johnthetubaguy | I like the idea of defining the conditions for claiming support | 20:22 |
ttx | avoids the weird "volunteer" mention | 20:23 |
ttx | (although I see what you mean by that) | 20:23 |
johnthetubaguy | I totally stole the phrase from fungi as I couldn't come up with a better one | 20:23 |
* dims has not reviewed that yet | 20:23 | |
fungi | i still like the word | 20:23 |
johnthetubaguy | should we just say "upstream support" then? | 20:23 |
johnthetubaguy | I also don't really want to get bogged down into listing all the requirements for support | 20:24 |
fungi | volunteers may refer to the individuals, or to the employers who volunteer their employees' time to participate, after all | 20:24 |
johnthetubaguy | I was more wanting to baseline on definitions really | 20:24 |
ttx | johnthetubaguy: yes, I like we keep it inspirational | 20:24 |
johnthetubaguy | fungi: totally | 20:24 |
dhellmann | this feels a bit like "open source 101" | 20:24 |
*** matrohon has joined #openstack-meeting | 20:24 | |
ttx | fungi: yes -- just know that some people will read it wrong | 20:25 |
fungi | we have a disproportionately high number of users (and even contributors) who could use a regular support of "open source 101" | 20:25 |
dtroyer | unfortunately ++ | 20:25 |
dhellmann | agreed | 20:25 |
fungi | er, regular dose | 20:25 |
johnthetubaguy | dhellmann: maybe, but its good to write down our shared assumptions | 20:25 |
*** artom has joined #openstack-meeting | 20:25 | |
ttx | johnthetubaguy: maybe make it clear that this is nothing new, more of a reminder | 20:25 |
dhellmann | johnthetubaguy : oh, I'm not objecting, just making the comment | 20:25 |
johnthetubaguy | ttx: yeah | 20:26 |
fungi | all those people who think openstack is "like free vmware" are wondering where their support contract is | 20:26 |
johnthetubaguy | dhellmann: very fair comment too | 20:26 |
dtroyer | more in the spirit of writing down our principles? | 20:26 |
johnthetubaguy | dtroyer: yep | 20:26 |
johnthetubaguy | on that note, is it really a "definition" rather than a resolution? | 20:26 |
ttx | johnthetubaguy: hmm... wondering if it could fit in the project team guide... although I guess it's more directed to specific tactical groups | 20:26 |
johnthetubaguy | so lives near the principles not the resolutions? | 20:26 |
*** ociuhandu has joined #openstack-meeting | 20:27 | |
johnthetubaguy | anyways, answers on a postcard, I mean gerrit review comment | 20:27 |
ttx | johnthetubaguy: I think it's a statement, not a living document | 20:27 |
ttx | so I'd rather file it under resolutions/ | 20:27 |
dhellmann | it seems reasonable to have a resolution saying "we're going to delete things when people stop contributing to them" | 20:27 |
sdague | dhellmann: yeh | 20:28 |
fungi | i think it's a statement at a point in time (resolution) which could be used to inform future updates to a living document such as principles et cetera | 20:28 |
johnthetubaguy | ttx: OK, I just never like trying to get things correct first time | 20:28 |
ttx | ok, let's iterate on the review | 20:28 |
johnthetubaguy | cool | 20:28 |
ttx | and move on | 20:28 |
sdague | or even that we delete things that are considered debt if it helps us move the whole platform forward | 20:28 |
ttx | johnthetubaguy: thanks for pushing those | 20:28 |
johnthetubaguy | sdague: didn't want to repeat the standard deprecation tag, but lets see what we come up with | 20:28 |
sdague | because, I kind of think that's really what's behind the next one... | 20:28 |
fungi | when you prune a shrub, you may lose a few live branches in the process ;) | 20:28 |
johnthetubaguy | sdague: yeah, thats totally why I raised this one | 20:29 |
dims | ooh, i got to write that down fungi :) | 20:29 |
*** henrynash has joined #openstack-meeting | 20:29 | |
ttx | which brings us to.... | 20:29 |
ttx | #topic Deprecate postgresql in OpenStack | 20:29 |
*** openstack changes topic to "Deprecate postgresql in OpenStack (Meeting topic: tc)" | 20:29 | |
ttx | #link https://review.openstack.org/427880 | 20:29 |
ttx | So this one is a bit stuck, although the previous resolution will help with it | 20:29 |
ttx | I think there are multiple ways to slice this one | 20:29 |
ttx | 0/ Make a statement that we'll deprecate it unless there is more consistent upstream work to support it | 20:29 |
ttx | 1/ Pass a resolution now saying it's generally deprecated due to lack of upstream support | 20:30 |
ttx | 2/ Contract the "database" base service to the MySQL family (now or after the deprecation period) | 20:30 |
ttx | (That last one would signal we can start breaking non-MySQL deployments) | 20:30 |
ttx | Before we do (2) I'd like to give people a last chance to step up and save it. Maybe that's my soft side speaking though... | 20:30 |
dhellmann | have we had any input at all from Huawei or SuSE? | 20:30 |
johnthetubaguy | you know how I said we should find a way to flag problems, how about we just say "the status quo of supporting many databases isn't working"? | 20:30 |
ttx | Also before we do (2) I'd prefer non-MySQL numbers to drop below 5% (currently at ~10%) | 20:30 |
dhellmann | I mean in the sense of their interest in supporting PG? | 20:30 |
dtroyer | it feels like we've done that already, but not this formally? | 20:30 |
dtroyer | ttx: ^^^ | 20:31 |
smcginnis | Might be better to start with 1, with the statement that 2 will follow. | 20:31 |
fungi | under 2/, are we feeling obligated to provide conversion/migration tools or instructions for people switching at upgrade time? | 20:31 |
ttx | we haven't done anything formal. I guess the question is should we do (0) or jump directly to (1) | 20:31 |
*** spilla has left #openstack-meeting | 20:31 | |
dhellmann | fungi : maybe | 20:31 |
ttx | this proposal is basically (1) | 20:31 |
dtroyer | I would pref to go straight to 1 to help signal "we mean it this time" | 20:31 |
johnthetubaguy | I don't see deprecation as a one way process, so I am fine with (1) | 20:31 |
gordc | dhellmann: can we define what 'more consistent upstream work to support it' means? | 20:31 |
dims | ttx : i vote for (1) | 20:31 |
dhellmann | gordc : excellent question. | 20:32 |
*** Patifa has quit IRC | 20:32 | |
ttx | it feels like more than one person asked "what consistent upstream work means", so (0) seems warranted | 20:32 |
johnthetubaguy | part of me things part of fixing this problem is digging deep to understand what the real issue is, and enumerate the possible solutions | 20:32 |
ttx | although I wasn't involved in previous iterations of the discussion so I may ignore how many times (0) was already done | 20:33 |
dhellmann | I also want us to answer clearly yes/no whether we *want* that contribution, or if we're more interested in dropping support than having help with maintenance. | 20:33 |
fungi | i do feel like we're still operating a little on the misconception that it was already broken when we stopped testing it. i stand by the reasons for ceasing testing, but there were no outward complaints of breakage until the issue ceilo hit recently | 20:33 |
sdague | dhellmann: right, I think we don't want that contribution | 20:33 |
*** henrynash has quit IRC | 20:33 | |
johnthetubaguy | dhellmann: I don't think we can, till someone has all the options laid out | 20:33 |
cdent | fungi++ | 20:33 |
dhellmann | sdague : how do we determine consensus on that? | 20:34 |
johnthetubaguy | I think we need to do (1) before we make that decision | 20:34 |
dhellmann | johnthetubaguy : aren't the options (1) someone says they will work on gate failures and we support pg or (2) we do not want anyone working on gate failures, pg is going away? | 20:34 |
johnthetubaguy | dhellmann: its more about how you avoid the gate failures in the first place, not working on that seems bad at this point | 20:35 |
ttx | that's two different ways of writing (1), for sure | 20:35 |
dhellmann | johnthetubaguy, ttx : option 1 presumes we would want support if someone showed up. We should not ask for help if we're going to turn people away. | 20:35 |
sdague | my slightly snark answer to gordc's question is: | 20:35 |
*** dprince has joined #openstack-meeting | 20:35 | |
gordc | dhellmann: + | 20:35 |
sdague | when pg folks implement consistent unicode name support for both mysql and pg across the starter kit | 20:35 |
dhellmann | the real option 1 seems to be that we do not want to support it because we want to use $features of mysql | 20:35 |
*** Patifa has joined #openstack-meeting | 20:35 | |
sdague | because the issue is that the community has to pay a pg tax on every feature, even if a small one | 20:36 |
dims | we have to signal that we are "contracting" the options | 20:36 |
johnthetubaguy | its more about stopping trying to think about all these different database on every patch, somehow | 20:36 |
gordc | sdague: cool, i dont know what that issue is personally. but good to have some qualifer | 20:36 |
sdague | and saying that pg folks only need to be engaged when it's entirely their platform at issue, instead of helping on general things to pay back that tax | 20:36 |
johnthetubaguy | dims: +1 thats why I want (1) to start the deeper discussions | 20:36 |
dhellmann | sure, but then let's be honest. it's not about lack of support from anyone in our community, right? it's about a fundamental underlying difference in the database engines. | 20:36 |
ttx | dims: I don't think we should contract until the alternate option is below 5% though | 20:36 |
ttx | I mean... open question | 20:37 |
sdague | dhellmann: right, it's based on the fact the dev community and operator community largely has the skills knowledge on one backend | 20:37 |
*** jkilpatr has quit IRC | 20:37 | |
ttx | what's the adoption bar under which it's fine to contract ? | 20:37 |
ttx | 20% ? 10% ? 5% ? | 20:37 |
gordc | dhellmann: tbh, i don't think we can accept/support pgsql if there is no gate on it since it's going to be impossible to measure if it's maintained or not. | 20:37 |
sdague | and "make it work for this other one too" is a real cost, even just at coming up with base plans | 20:37 |
ttx | PG is currently ~9% of deploys | 20:37 |
dhellmann | sdague : are the unicode issues addressable via sqlalchemy, for example? | 20:37 |
sdague | dhellmann: no | 20:37 |
fungi | there was a distinct impression in the joint board/tc/uc meeting last week where the ecosystem perceives openstack as complex, and overall we need to shed some weight (in terms of providing deployers/users too much flexibility) to simplify it | 20:38 |
sdague | fungi: ++ | 20:38 |
dtroyer | fungi: ++ | 20:38 |
dims | yep fungi | 20:38 |
johnthetubaguy | fungi ++ | 20:38 |
*** dimtruck is now known as zz_dimtruck | 20:38 | |
dhellmann | sure, I don't have a problem with that, I just want us to be honest about the reason we're doing it. | 20:38 |
fungi | easy ways include removing backend options where the ecosystem has already mostly chosen a winner | 20:38 |
*** prateek has quit IRC | 20:38 | |
johnthetubaguy | so the request for help is helping people move between databases? | 20:38 |
ttx | yes, we shouldn't say it's for lack of upstream commitment then | 20:38 |
fungi | and thos in particular seemed like a fairly clear-cut example of that scenario | 20:39 |
fungi | s/thos/this/ | 20:39 |
ttx | which makes johnthetubaguy's resolution a bit redundant | 20:39 |
dhellmann | johnthetubaguy : would we accept features in service projects to ease that migration? like some sort of db-neutral dump and import tool? | 20:39 |
johnthetubaguy | well, irrelevant I guess | 20:39 |
dims | we can cite both reasons ttx | 20:39 |
sdague | right, and hopefully prevent more people from being on the "wrong" side of a "don't worry wesley, likely to kill you in the morning" | 20:39 |
johnthetubaguy | dhellmann: thats the kind of thing I was thinking | 20:39 |
ttx | dims: I would argue it should just be submitted as a base-services.rst patch then | 20:40 |
* dhellmann has a use case for that tool independent of a db transition | 20:40 | |
johnthetubaguy | dhellmann: maybe os-ops scripts that use some alembic magic, but something | 20:40 |
dims | ttx : agree | 20:40 |
ttx | dims: no need for a resolution citing lack of commitment if we'd do it anyway in the name of contracting options | 20:40 |
sdague | because I suspect that suse and huawei ended up over on that side of the line based on us not being properly expressive that there was a preference here upstream | 20:40 |
dhellmann | johnthetubaguy : I want it to be schema-neutral for my use case, too | 20:40 |
dhellmann | sdague : exactly. let's not make it worse by suggesting there is any amount of upstream commitment that could reverse this course. | 20:41 |
gordc | sdague: not really from huawei pov. | 20:41 |
johnthetubaguy | did we get explicit about rabbitmq already? | 20:41 |
ttx | johnthetubaguy: nope | 20:41 |
dims | johnthetubaguy : we can line both up :) | 20:41 |
sdague | johnthetubaguy: the non rabbit solutions hard failed enough that a resolution was never really needed practically | 20:41 |
johnthetubaguy | sdague: true, but its good to let folks know that | 20:42 |
dhellmann | there are people actively working on zeromq, and maybe other drivers | 20:42 |
johnthetubaguy | dhellmann: maybe its time to tell them to stop that (unless it fixes rabbitmq ha) | 20:42 |
dhellmann | so we need to engage those teams when we start talking about deprecations there | 20:42 |
dims | dhellmann : mirantis has stopped work on zeromq | 20:42 |
ttx | dhellmann: it fixes a specific distributed cloud case | 20:42 |
dhellmann | dims : ok, I thought it was someone else | 20:42 |
ttx | different discussion though | 20:43 |
dhellmann | ttx: right, my point is someone still thinks there's active work to be done there | 20:43 |
johnthetubaguy | feels like they should both get the same treatment | 20:43 |
*** jaypipes has quit IRC | 20:43 | |
dtroyer | I think that is a reasonable starting point | 20:43 |
johnthetubaguy | "hey we tried to abstract this stuff, we failed, sorry" | 20:43 |
dhellmann | we'll want to consider the rpc and notification cases separately, I think, but yeah | 20:44 |
EmilienM | we're also investing in amqp driver (without rabbitmq) in tripleo | 20:44 |
ttx | OK, so two different facets to polish: be clear why we are doing it to not open false hopes, and also be clear of when we'd be fine with breaking setups (after deprecation period I guess) | 20:44 |
johnthetubaguy | dhellmann: thats true, I was thinking RPC | 20:44 |
EmilienM | which would solve the rabbitmq ha | 20:44 |
sdague | johnthetubaguy: or more importantly, the abstraction isn't going to make anyone really happy | 20:44 |
johnthetubaguy | sdague: true, thats realisation here really | 20:44 |
dhellmann | ttx: and suggest that folks start thinking about transition plans, and encourage project teams to allow feature additions to support that transition. | 20:45 |
ttx | johnthetubaguy: I prefer to see it as the natural end of an expand/contracting of options, once the market /operators picked a winner | 20:45 |
ttx | not a failure in abstracting | 20:45 |
ttx | anyway, I think we know what to work on to improve the proposal(s), let's move on to next topic | 20:45 |
johnthetubaguy | ttx: maybe... a bit of both for sure | 20:46 |
dhellmann | johnthetubaguy : that last thing I said may be something to add to your resolution (that we'd want projects to build transition tools) | 20:46 |
ttx | #info two different facets to polish: be clear why we are doing it to not open false hopes, and also be clear of when we'd be fine with breaking setups (after deprecation period I guess) | 20:46 |
johnthetubaguy | dhellmann: I think thats covered in the deprecation tag already, but I will check | 20:46 |
dhellmann | johnthetubaguy : ok | 20:46 |
*** browne has left #openstack-meeting | 20:47 | |
ttx | #info if we'd do it to contract options, maybe the resolution on upstream support is unnecessary | 20:47 |
ttx | #topic Status update on other proposals | 20:47 |
*** openstack changes topic to "Status update on other proposals (Meeting topic: tc)" | 20:47 | |
ttx | Let's go quick on those | 20:47 |
ttx | * Golang CTI (https://review.openstack.org/410355) and Dims's Small steps for Go (https://etherpad.openstack.org/p/go-and-containers) | 20:47 |
ttx | dtroyer, dims: quick update ? | 20:47 |
dtroyer | I rev'ed the CTI doc Friday, think I got the comments, and see one last tab fail on my part | 20:47 |
dims | we have a git repo for golang-commons for oslo style ini and logs. trying to rustle up some contributors | 20:48 |
dtroyer | golang-client is current on the proposal (as far as it goes) for a real-world example | 20:48 |
ttx | ok so still WIP | 20:48 |
*** armax has joined #openstack-meeting | 20:48 | |
notmyname | I have a quick question on this topic | 20:48 |
ttx | dtroyer: let me know when ready for formal vote | 20:48 |
ttx | notmyname: sure | 20:48 |
*** askb has joined #openstack-meeting | 20:49 | |
dtroyer | ttx: there are a few details to be added, but the only thing really missing from the CTI is a translation story | 20:49 |
notmyname | does the TC want to see the dims/dtroyer work happen before anythign else? how does it fit with the things in the flavio resolution? what order does the tc want to see things happen in? | 20:49 |
dims | dtroyer : k8s folks are struggling there too | 20:49 |
dhellmann | dtroyer : translation may not be a high priority unless the i18n team is planning to change their scope to include non-ui tools | 20:50 |
clarkb | dtroyer: dims no gettext support in Go? | 20:50 |
dims | clarkb : tools around it | 20:50 |
ttx | notmyname: I think flaper87's framework calls for approval of the technical case before we work on how that would work | 20:50 |
fungi | also we should be pretty up-front with reasons golang-client is not a replacement of gophercloud. we already have enough reputation problems outside our community when it comes to reinventing other people's wheels | 20:50 |
dtroyer | clarkb: honestly I haven't spent more than an hour on it so far, so IDK | 20:50 |
dims | fungi : right | 20:50 |
ttx | notmyname: here they started working on part 2 assuming you would file something | 20:51 |
ttx | I think | 20:51 |
ttx | dims: ? | 20:51 |
dtroyer | I added a short history of that to dims' etherpad, and am using it here because it existed and I already had core on it and could iterate quickly wihtout impacting anyone else | 20:51 |
notmyname | we've held off once the new ML thread and proposals started | 20:51 |
dhellmann | #link https://governance.openstack.org/tc/reference/new-language-requirements.html | 20:51 |
ttx | (I feel like we went over the technical use case for Swift already, but we could use some formal stamp) | 20:52 |
dims | notmyname : i'd like swift team to help with the golang-commons if possible | 20:52 |
johnthetubaguy | ttx: +1 I was going to check the same thing | 20:52 |
dhellmann | fungi : +1 | 20:52 |
cdent | it was unclear to me if the "why not gophercloud?" question was answered? | 20:52 |
notmyname | dims: from what I've seen, the new golang commons thing looks like a client tool? which was never under the no not python rule | 20:52 |
notmyname | which was somewhat confusing | 20:53 |
mugsie | cdent: me too | 20:53 |
notmyname | figuring out the ci and stuff like that is good, but the specifics seemed tangental | 20:53 |
ttx | notmyname: so we still need some "use case analysis" around swift to be approved. I don't think you need a lot more than what you already presented, but we need it to go through the new proces (and be approved rather than rejected) | 20:53 |
ttx | I suspect dims will help you do that | 20:53 |
notmyname | ttx: yeah, and we're planning on that. but my question is if the tc wants to see that before or after the current dims/dtroyer work | 20:54 |
ttx | (assumed that was in progress) | 20:54 |
ttx | I would say before | 20:54 |
dims | notmyname : it's not a client tool, it's code that can help with standardzing some of the operator visible things like logs and ini files | 20:54 |
ttx | based on "step 1" in that document coming before "step 2" | 20:54 |
ttx | need to switch to open discussion, as I had a couple topics to cover there | 20:55 |
dtroyer | ccdent, mugsie: let's talk in -dev after this if I can answer more | 20:55 |
notmyname | ttx: ack | 20:55 |
ttx | we can continue in #openstack-dev the discussion between dims and notmyname | 20:55 |
ttx | #topic Open discussion | 20:55 |
*** openstack changes topic to "Open discussion (Meeting topic: tc)" | 20:55 | |
ttx | I have two topics to cover | 20:55 |
ttx | #info Encouraging Forum brainstorming | 20:55 |
ttx | Looks like we have a lot of "we could discuss this with operators at the Forum" moments, but not so many translate into ideas on the etherpads | 20:55 |
ttx | #link https://wiki.openstack.org/wiki/Forum/Boston2017 | 20:55 |
ttx | Last week we discussed using the Forum to fill the missing link between user stories and implementation ideas and complete the feedback loop | 20:56 |
ttx | (in particular build up-to-date gap analysis by involving developers in the discussion) | 20:56 |
ttx | It feels like email reminders are not really cutting it, so I'd like to encourage you to get personal | 20:56 |
ttx | try to encourage people to think about and post discussion topics ideas | 20:56 |
ttx | Plan was to start filing formal topic ideas next week, so that the committee would be able to select a schedule for first half of April | 20:56 |
ttx | The deadline was pushed back one week | 20:56 |
*** Patifa has quit IRC | 20:56 | |
ttx | (initial deadline was ~today) | 20:56 |
ttx | But maybe the whole timing is too short, I don't know | 20:57 |
johnthetubaguy | it feels quite soon after the PTG, but having the topics soon helps with requesting budget to attend | 20:57 |
dhellmann | the mysql/pg and messaging deprecations should go on that list | 20:57 |
ttx | yeah, wondering if the whole timing is not just too short | 20:57 |
ttx | goal was to publish schedule a month early | 20:58 |
ttx | (before the event) | 20:58 |
*** DFFlanders has joined #openstack-meeting | 20:58 | |
johnthetubaguy | ttx: I totally missed we had a deadline, I probably did know, but I think my head is assuming we sort that all much nearer the time | 20:58 |
dhellmann | I don't see a list from the Arch WG, is there one somewhere? | 20:58 |
ttx | on one hand we want time to figure out which topics are interesting, on the other we need the schedule published so people realize what will be discussed | 20:58 |
*** jkilpatr has joined #openstack-meeting | 20:58 | |
johnthetubaguy | ttx: I don't have all the specs approved for this cycle yet, so I am not totally thinking about next cycle | 20:59 |
ttx | dhellmann: I posted mines on the TC catchall | 20:59 |
ttx | My other topic was around Vision exercise feedback | 20:59 |
ttx | we can cover that one next week | 20:59 |
*** adisky_ has quit IRC | 20:59 | |
johnthetubaguy | I have a photo with 6 bullet points on it, that looks good | 20:59 |
ttx | ok, we are out of time. | 21:00 |
*** gordc has left #openstack-meeting | 21:00 | |
*** Patifa has joined #openstack-meeting | 21:00 | |
ttx | Thanks everyone! | 21:00 |
cdent | if folks get a chance look at https://github.com/Jermolene/TiddlyWiki5/pull/2371 | 21:00 |
*** matrohon has quit IRC | 21:00 | |
ttx | let's overflow to #openstack-dev | 21:00 |
cdent | whoops not that! | 21:00 |
jroll | thanks ttx | 21:00 |
ttx | #endmeeting | 21:00 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 21:00 | |
openstack | Meeting ended Tue Mar 14 21:00:45 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 21:00 |
cdent | this https://review.openstack.org/#/c/421846/ | 21:00 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-03-14-20.01.html | 21:00 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-03-14-20.01.txt | 21:00 |
openstack | Log: http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-03-14-20.01.log.html | 21:00 |
ttx | cdent: oops | 21:01 |
*** zz_dimtruck is now known as dimtruck | 21:03 | |
cdent | such is life in the world of cut and paste | 21:03 |
*** ociuhandu has quit IRC | 21:04 | |
dims | cdent : starred it | 21:05 |
cdent | thanks dims | 21:05 |
*** Apoorva has joined #openstack-meeting | 21:06 | |
*** cdent has left #openstack-meeting | 21:09 | |
*** e0ne has quit IRC | 21:15 | |
*** raildo has quit IRC | 21:15 | |
*** e0ne has joined #openstack-meeting | 21:17 | |
*** abalutoiu has joined #openstack-meeting | 21:20 | |
*** aysyd has quit IRC | 21:25 | |
*** gouthamr has quit IRC | 21:25 | |
*** Patifa has quit IRC | 21:27 | |
*** e0ne has quit IRC | 21:28 | |
*** jmckind has quit IRC | 21:29 | |
*** jrobinson has joined #openstack-meeting | 21:30 | |
*** pradk has quit IRC | 21:30 | |
*** felipemonteiro has quit IRC | 21:32 | |
*** zara_the_lemur__ has left #openstack-meeting | 21:32 | |
*** Patifa has joined #openstack-meeting | 21:32 | |
*** e0ne has joined #openstack-meeting | 21:32 | |
*** Patifa has quit IRC | 21:33 | |
*** tonytan_brb has quit IRC | 21:36 | |
*** dimtruck is now known as zz_dimtruck | 21:36 | |
*** Sukhdev has quit IRC | 21:37 | |
*** zz_dimtruck is now known as dimtruck | 21:37 | |
*** eharney has quit IRC | 21:38 | |
*** Julien-zte has joined #openstack-meeting | 21:41 | |
*** e0ne has quit IRC | 21:42 | |
*** Patifa has joined #openstack-meeting | 21:42 | |
*** dmacpher-afk has quit IRC | 21:46 | |
*** Sukhdev has joined #openstack-meeting | 21:52 | |
*** rbak_ has quit IRC | 21:53 | |
*** rfolco has quit IRC | 21:53 | |
*** Patifa has quit IRC | 21:53 | |
*** xyang1 has quit IRC | 21:54 | |
*** rbak_ has joined #openstack-meeting | 21:54 | |
*** dprince has quit IRC | 21:56 | |
*** pradk has joined #openstack-meeting | 21:57 | |
*** ociuhandu has joined #openstack-meeting | 22:03 | |
*** kjw3 has quit IRC | 22:06 | |
*** kaisers_ has quit IRC | 22:07 | |
*** ihrachys has joined #openstack-meeting | 22:08 | |
*** claudiub has quit IRC | 22:11 | |
*** bobh has quit IRC | 22:12 | |
*** tobberydberg has joined #openstack-meeting | 22:13 | |
*** esberglu has quit IRC | 22:15 | |
*** ihrachys has quit IRC | 22:16 | |
*** tobberydberg has quit IRC | 22:17 | |
*** gouthamr has joined #openstack-meeting | 22:19 | |
*** hashar has quit IRC | 22:19 | |
*** Julien-zte has quit IRC | 22:19 | |
*** Julien-z_ has joined #openstack-meeting | 22:19 | |
*** priteau has quit IRC | 22:20 | |
*** hashar has joined #openstack-meeting | 22:20 | |
*** Leo_ has quit IRC | 22:24 | |
*** lamt has quit IRC | 22:25 | |
*** lamt has joined #openstack-meeting | 22:26 | |
*** lamt has quit IRC | 22:30 | |
*** esberglu has joined #openstack-meeting | 22:32 | |
*** esberglu has quit IRC | 22:33 | |
*** Patifa has joined #openstack-meeting | 22:38 | |
*** galstrom is now known as galstrom_zzz | 22:40 | |
*** pradk has quit IRC | 22:44 | |
*** ijw has joined #openstack-meeting | 22:45 | |
*** fnaval has quit IRC | 22:48 | |
*** Leo_ has joined #openstack-meeting | 22:51 | |
*** rfolco has joined #openstack-meeting | 22:54 | |
*** Leo_ has quit IRC | 22:55 | |
*** fnaval has joined #openstack-meeting | 23:01 | |
*** Julien-z_ has quit IRC | 23:02 | |
*** Julien-zte has joined #openstack-meeting | 23:03 | |
*** Leo_ has joined #openstack-meeting | 23:03 | |
*** Julien-zte has quit IRC | 23:03 | |
*** kaisers_ has joined #openstack-meeting | 23:03 | |
*** Julien-zte has joined #openstack-meeting | 23:04 | |
*** Julien-zte has quit IRC | 23:04 | |
*** Julien-zte has joined #openstack-meeting | 23:04 | |
*** Julien-zte has quit IRC | 23:05 | |
*** chris_morrell has quit IRC | 23:07 | |
*** kaisers_ has quit IRC | 23:09 | |
*** Swami has quit IRC | 23:11 | |
*** bobh has joined #openstack-meeting | 23:13 | |
*** Leo_ has quit IRC | 23:17 | |
*** henrynash has joined #openstack-meeting | 23:21 | |
*** ykatabam has joined #openstack-meeting | 23:23 | |
*** ykatabam1 has joined #openstack-meeting | 23:24 | |
*** henrynash has quit IRC | 23:26 | |
*** baoli has quit IRC | 23:26 | |
*** henrynash has joined #openstack-meeting | 23:27 | |
*** ykatabam has quit IRC | 23:27 | |
*** Leo_ has joined #openstack-meeting | 23:27 | |
*** sdague has quit IRC | 23:29 | |
*** Patifa has quit IRC | 23:30 | |
*** dimtruck is now known as zz_dimtruck | 23:31 | |
*** henrynash has quit IRC | 23:32 | |
*** fnaval has quit IRC | 23:38 | |
*** unicell has quit IRC | 23:44 | |
*** hongbin has quit IRC | 23:45 | |
*** unicell has joined #openstack-meeting | 23:47 | |
*** hashar has quit IRC | 23:51 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!