*** ihrachys has joined #openstack-meeting | 00:01 | |
*** enriquetaso has quit IRC | 00:03 | |
*** ivar-lazzaro has joined #openstack-meeting | 00:04 | |
*** ssalagame has quit IRC | 00:04 | |
*** numans has quit IRC | 00:04 | |
*** singhj has quit IRC | 00:04 | |
*** nkinder has quit IRC | 00:05 | |
*** roxanaghe has quit IRC | 00:05 | |
*** anteaya has quit IRC | 00:09 | |
*** shaohe_feng has quit IRC | 00:09 | |
*** anteaya has joined #openstack-meeting | 00:09 | |
*** shaohe_feng has joined #openstack-meeting | 00:10 | |
*** Julien-zte has joined #openstack-meeting | 00:10 | |
*** dmorita has quit IRC | 00:14 | |
*** claudiub has quit IRC | 00:15 | |
*** rrecio has quit IRC | 00:17 | |
*** ihrachys has quit IRC | 00:17 | |
*** sarob has quit IRC | 00:17 | |
*** jamesdenton has joined #openstack-meeting | 00:18 | |
*** shaohe_feng has quit IRC | 00:19 | |
*** thorst has joined #openstack-meeting | 00:19 | |
*** shaohe_feng has joined #openstack-meeting | 00:20 | |
*** sacharya has joined #openstack-meeting | 00:20 | |
*** sacharya_ has quit IRC | 00:20 | |
*** pvaneck has quit IRC | 00:20 | |
*** sarob has joined #openstack-meeting | 00:21 | |
*** dmacpher has quit IRC | 00:21 | |
*** gyee has quit IRC | 00:21 | |
*** garthb has quit IRC | 00:22 | |
*** lyrrad has quit IRC | 00:25 | |
*** mbound has joined #openstack-meeting | 00:25 | |
*** piet_ has joined #openstack-meeting | 00:26 | |
*** yuanying has quit IRC | 00:27 | |
*** JRobinson__ is now known as JRobinson__afk | 00:27 | |
*** yuanying has joined #openstack-meeting | 00:27 | |
*** baoli has quit IRC | 00:28 | |
*** dneary has quit IRC | 00:28 | |
*** baoli has joined #openstack-meeting | 00:28 | |
*** betherly has quit IRC | 00:28 | |
*** betherly has joined #openstack-meeting | 00:29 | |
*** shaohe_feng has quit IRC | 00:29 | |
*** mtanin___ has joined #openstack-meeting | 00:30 | |
*** yujunz has joined #openstack-meeting | 00:30 | |
*** yamahata has quit IRC | 00:30 | |
*** mbound has quit IRC | 00:30 | |
*** shaohe_feng has joined #openstack-meeting | 00:30 | |
*** SotK has quit IRC | 00:31 | |
*** mtanino has quit IRC | 00:31 | |
*** SotK has joined #openstack-meeting | 00:31 | |
*** yamahata has joined #openstack-meeting | 00:32 | |
*** azbiswas has quit IRC | 00:32 | |
*** sarob has quit IRC | 00:34 | |
*** amitgandhinz has quit IRC | 00:35 | |
*** kzaitsev_mb has quit IRC | 00:37 | |
*** rrecio has joined #openstack-meeting | 00:37 | |
*** numans has joined #openstack-meeting | 00:37 | |
*** JRobinson__afk has quit IRC | 00:38 | |
*** rrecio_ has joined #openstack-meeting | 00:38 | |
*** shaohe_feng has quit IRC | 00:39 | |
*** jamesmcarthur has joined #openstack-meeting | 00:40 | |
*** yamada-h has joined #openstack-meeting | 00:40 | |
*** sarob has joined #openstack-meeting | 00:40 | |
*** thorst has quit IRC | 00:40 | |
*** sarob has quit IRC | 00:40 | |
*** shaohe_feng has joined #openstack-meeting | 00:40 | |
*** sacharya has quit IRC | 00:41 | |
*** zz_dimtruck is now known as dimtruck | 00:41 | |
*** thorst has joined #openstack-meeting | 00:41 | |
*** rrecio has quit IRC | 00:41 | |
*** jamesmcarthur has quit IRC | 00:44 | |
*** yamada-h has quit IRC | 00:44 | |
*** Sukhdev has quit IRC | 00:49 | |
*** rrecio_ has quit IRC | 00:49 | |
*** thorst has quit IRC | 00:49 | |
*** shaohe_feng has quit IRC | 00:50 | |
*** shaohe_feng has joined #openstack-meeting | 00:50 | |
*** ijw has quit IRC | 00:51 | |
*** baoli has quit IRC | 00:53 | |
*** longxiongqiu has joined #openstack-meeting | 00:54 | |
*** ijw has joined #openstack-meeting | 00:55 | |
*** azbiswas has joined #openstack-meeting | 00:56 | |
*** dimtruck is now known as zz_dimtruck | 00:57 | |
*** zhhuabj has joined #openstack-meeting | 00:58 | |
*** hoangcx has quit IRC | 00:59 | |
*** yujunz has quit IRC | 00:59 | |
*** shaohe_feng has quit IRC | 01:00 | |
*** shaohe_feng has joined #openstack-meeting | 01:00 | |
*** azbiswas has quit IRC | 01:01 | |
*** zul has joined #openstack-meeting | 01:04 | |
*** Apoorva_ has quit IRC | 01:04 | |
*** dmorita has joined #openstack-meeting | 01:05 | |
*** karthikp_ has joined #openstack-meeting | 01:05 | |
*** amotoki has joined #openstack-meeting | 01:06 | |
*** ivar-lazzaro has quit IRC | 01:07 | |
*** dmorita has quit IRC | 01:10 | |
*** shaohe_feng has quit IRC | 01:10 | |
*** shaohe_feng has joined #openstack-meeting | 01:11 | |
*** edtubill has joined #openstack-meeting | 01:12 | |
*** Daisy has joined #openstack-meeting | 01:12 | |
*** ivar-lazzaro has joined #openstack-meeting | 01:13 | |
*** ijw has quit IRC | 01:13 | |
*** hoangcx has joined #openstack-meeting | 01:13 | |
*** yujunz has joined #openstack-meeting | 01:15 | |
*** baoli has joined #openstack-meeting | 01:16 | |
*** dmacpher has joined #openstack-meeting | 01:18 | |
*** shaohe_feng has quit IRC | 01:20 | |
*** amotoki has quit IRC | 01:21 | |
*** shaohe_feng has joined #openstack-meeting | 01:21 | |
*** s3wong has quit IRC | 01:22 | |
*** edtubill has quit IRC | 01:24 | |
*** hoangcx has quit IRC | 01:25 | |
*** baoli has quit IRC | 01:26 | |
*** grassass has joined #openstack-meeting | 01:26 | |
*** hoangcx has joined #openstack-meeting | 01:27 | |
*** rwsu has quit IRC | 01:30 | |
*** shaohe_feng has quit IRC | 01:31 | |
*** shaohe_feng has joined #openstack-meeting | 01:31 | |
*** edtubill has joined #openstack-meeting | 01:33 | |
*** thorst has joined #openstack-meeting | 01:34 | |
*** Daisy has quit IRC | 01:34 | |
*** Daisy has joined #openstack-meeting | 01:35 | |
*** Daisy_ has joined #openstack-meeting | 01:35 | |
*** amitgandhinz has joined #openstack-meeting | 01:36 | |
*** Daisy_ has quit IRC | 01:36 | |
*** Daisy_ has joined #openstack-meeting | 01:36 | |
*** zhangshuai has joined #openstack-meeting | 01:38 | |
*** piet_ has quit IRC | 01:39 | |
*** Daisy has quit IRC | 01:39 | |
*** amotoki has joined #openstack-meeting | 01:39 | |
*** edtubill has quit IRC | 01:40 | |
*** zz_dimtruck is now known as dimtruck | 01:41 | |
*** zul has quit IRC | 01:41 | |
*** shaohe_feng has quit IRC | 01:41 | |
*** amitgandhinz has quit IRC | 01:41 | |
*** shaohe_feng has joined #openstack-meeting | 01:42 | |
*** yamada-h has joined #openstack-meeting | 01:43 | |
*** tfukushima has joined #openstack-meeting | 01:44 | |
*** yamada-h has quit IRC | 01:47 | |
*** hoangcx has quit IRC | 01:48 | |
*** JRobinson__ has joined #openstack-meeting | 01:50 | |
*** hoangcx_ has joined #openstack-meeting | 01:50 | |
*** shaohe_feng has quit IRC | 01:51 | |
*** hoangcx_ has left #openstack-meeting | 01:52 | |
*** shaohe_feng has joined #openstack-meeting | 01:52 | |
*** abcxyz has joined #openstack-meeting | 01:52 | |
*** hoangcx_ has joined #openstack-meeting | 01:53 | |
*** zul has joined #openstack-meeting | 01:54 | |
*** abcxyz has quit IRC | 01:55 | |
*** hoangcx_ is now known as hoangcx | 01:56 | |
*** hoangcx has left #openstack-meeting | 01:56 | |
*** Daisy has joined #openstack-meeting | 01:58 | |
*** abcxyz has joined #openstack-meeting | 01:59 | |
*** sacharya has joined #openstack-meeting | 01:59 | |
*** sacharya has quit IRC | 01:59 | |
*** Daisy_ has quit IRC | 02:00 | |
*** lblanchard has joined #openstack-meeting | 02:01 | |
*** shaohe_feng has quit IRC | 02:01 | |
*** shaohe_feng has joined #openstack-meeting | 02:02 | |
*** fnaval has quit IRC | 02:04 | |
*** dimtruck is now known as zz_dimtruck | 02:06 | |
*** erlon has quit IRC | 02:06 | |
*** hoangcx has joined #openstack-meeting | 02:06 | |
*** zz_dimtruck is now known as dimtruck | 02:06 | |
*** hoangcx has left #openstack-meeting | 02:06 | |
*** amotoki has quit IRC | 02:07 | |
*** piet_ has joined #openstack-meeting | 02:07 | |
*** abcxyz has quit IRC | 02:07 | |
*** amotoki has joined #openstack-meeting | 02:07 | |
*** abcxyz has joined #openstack-meeting | 02:07 | |
*** samP has joined #openstack-meeting | 02:08 | |
*** Daisy has quit IRC | 02:11 | |
*** jungleboyj has joined #openstack-meeting | 02:11 | |
*** Daisy has joined #openstack-meeting | 02:11 | |
*** zhangshuai_ has joined #openstack-meeting | 02:11 | |
*** iyamahat has quit IRC | 02:11 | |
*** shaohe_feng has quit IRC | 02:12 | |
*** yamahata has quit IRC | 02:12 | |
*** shaohe_feng has joined #openstack-meeting | 02:13 | |
*** dneary has joined #openstack-meeting | 02:14 | |
*** zhangshuai has quit IRC | 02:15 | |
*** mtanino has joined #openstack-meeting | 02:16 | |
*** sarob has joined #openstack-meeting | 02:16 | |
*** huangtianhua has quit IRC | 02:17 | |
*** r-mibu has quit IRC | 02:17 | |
*** huangtianhua has joined #openstack-meeting | 02:18 | |
*** mtanin___ has quit IRC | 02:18 | |
*** sbalukoff has quit IRC | 02:18 | |
*** lblanchard has quit IRC | 02:19 | |
*** Daisy_ has joined #openstack-meeting | 02:20 | |
*** sarob has quit IRC | 02:21 | |
*** Swanson has quit IRC | 02:22 | |
*** ivar-laz_ has joined #openstack-meeting | 02:22 | |
*** shaohe_feng has quit IRC | 02:22 | |
*** JRobinson__ has quit IRC | 02:22 | |
*** Swanson has joined #openstack-meeting | 02:22 | |
*** ivar-laz_ has quit IRC | 02:22 | |
*** shaohe_feng has joined #openstack-meeting | 02:23 | |
*** JRobinson__ has joined #openstack-meeting | 02:23 | |
*** Daisy has quit IRC | 02:23 | |
*** fnaval has joined #openstack-meeting | 02:23 | |
*** ivar-lazzaro has quit IRC | 02:25 | |
*** banix has quit IRC | 02:26 | |
*** zhurong has joined #openstack-meeting | 02:27 | |
*** julim has joined #openstack-meeting | 02:29 | |
*** tfukushima has quit IRC | 02:29 | |
*** shaohe_feng has quit IRC | 02:32 | |
*** abcxyz has quit IRC | 02:32 | |
*** shaohe_feng has joined #openstack-meeting | 02:33 | |
*** sacharya has joined #openstack-meeting | 02:34 | |
*** abcxyz has joined #openstack-meeting | 02:34 | |
*** chenpengzi has joined #openstack-meeting | 02:36 | |
*** mtanino has quit IRC | 02:37 | |
*** r-mibu has joined #openstack-meeting | 02:37 | |
*** amitgandhinz has joined #openstack-meeting | 02:38 | |
*** tfukushima has joined #openstack-meeting | 02:38 | |
*** banix has joined #openstack-meeting | 02:39 | |
*** nkinder has joined #openstack-meeting | 02:40 | |
*** amotoki has quit IRC | 02:40 | |
*** ssalagame has joined #openstack-meeting | 02:42 | |
*** amitgandhinz has quit IRC | 02:42 | |
*** shaohe_feng has quit IRC | 02:42 | |
*** shaohe_feng has joined #openstack-meeting | 02:43 | |
*** chenpengzi has quit IRC | 02:43 | |
*** zhurong has quit IRC | 02:44 | |
*** jckasper has quit IRC | 02:44 | |
*** jckasper has joined #openstack-meeting | 02:44 | |
*** zhurong has joined #openstack-meeting | 02:44 | |
*** asingh has quit IRC | 02:45 | |
*** timothyb89 has quit IRC | 02:45 | |
*** timothyb89 has joined #openstack-meeting | 02:47 | |
*** jamesdenton has quit IRC | 02:48 | |
*** woodster_ has quit IRC | 02:48 | |
*** sacharya_ has joined #openstack-meeting | 02:49 | |
*** yuanying has quit IRC | 02:50 | |
*** yamamoto_ has joined #openstack-meeting | 02:50 | |
*** mkrai has joined #openstack-meeting | 02:51 | |
*** sacharya has quit IRC | 02:52 | |
*** yuanying has joined #openstack-meeting | 02:52 | |
*** sudipto has joined #openstack-meeting | 02:52 | |
*** epico has joined #openstack-meeting | 02:53 | |
*** shaohe_feng has quit IRC | 02:53 | |
*** Leo_ has joined #openstack-meeting | 02:53 | |
*** amotoki has joined #openstack-meeting | 02:54 | |
*** haiwei_ has joined #openstack-meeting | 02:55 | |
*** ijw has joined #openstack-meeting | 02:56 | |
*** shaohe_feng has joined #openstack-meeting | 02:56 | |
*** yujunz has quit IRC | 02:56 | |
*** edtubill has joined #openstack-meeting | 02:56 | |
*** amotoki has quit IRC | 02:57 | |
*** Namrata has joined #openstack-meeting | 02:57 | |
*** hongbin has joined #openstack-meeting | 02:57 | |
hongbin | #startmeeting zun | 03:00 |
---|---|---|
*** samP has quit IRC | 03:00 | |
openstack | Meeting started Tue Jun 14 03:00:04 2016 UTC and is due to finish in 60 minutes. The chair is hongbin. Information about MeetBot at http://wiki.debian.org/MeetBot. | 03:00 |
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_2016-06-14_0300_UTC Today's agenda | 03:00 |
*** thorst has quit IRC | 03:00 | |
eliqiao | o/ | 03:00 |
hongbin | #topic Roll Call | 03:00 |
*** openstack changes topic to "Roll Call (Meeting topic: zun)" | 03:00 | |
mkrai | Madhuri Kumari | 03:00 |
sudipto | o/ | 03:00 |
eliqiao | o/ | 03:00 |
Wenzhi | Wenzhi Yu | 03:00 |
Namrata | o/ | 03:00 |
haiwei_ | hi | 03:00 |
*** thorst has joined #openstack-meeting | 03:00 | |
hongbin | Thanks for joining the meeting eliqiao mkrai eliqiao sudipto Wenzhi Namrata haiwei_ | 03:01 |
hongbin | Pause a few seconds for future pacticipants | 03:01 |
*** mickeys has quit IRC | 03:01 | |
*** edtubill has quit IRC | 03:01 | |
*** xiucai has joined #openstack-meeting | 03:01 | |
Qiming | hi | 03:02 |
*** adisky has joined #openstack-meeting | 03:02 | |
*** mickeys has joined #openstack-meeting | 03:02 | |
*** yanyanhu has joined #openstack-meeting | 03:02 | |
*** Vivek__ has joined #openstack-meeting | 03:02 | |
hongbin | Qiming: hey | 03:02 |
yanyanhu | hi, sorry I'm late | 03:02 |
hongbin | NP | 03:02 |
Vivek__ | Hi | 03:02 |
hongbin | #topic Announcements | 03:02 |
adisky | hi.. | 03:02 |
*** openstack changes topic to "Announcements (Meeting topic: zun)" | 03:02 | |
hongbin | Eli Qiao is now a Zun cores! | 03:02 |
*** yamamoto_ has quit IRC | 03:02 | |
adisky | :) | 03:02 |
eliqiao | thanks hongbin and team. | 03:02 |
hongbin | Thanks Eli for your contribution and commitment | 03:03 |
haiwei_ | welcome Eli Qiao | 03:03 |
mkrai | Great addition | 03:03 |
mkrai | Welcome eliqiao | 03:03 |
*** shaohe_feng has quit IRC | 03:03 | |
yanyanhu | con :) | 03:03 |
hongbin | For others, if you want to join the core team, please feel free to ping me | 03:03 |
eliqiao | thx all. | 03:03 |
hongbin | The standard will be similar to recent added core | 03:03 |
hongbin | #topic Review Action Items | 03:03 |
*** openstack changes topic to "Review Action Items (Meeting topic: zun)" | 03:03 | |
hongbin | 1. hongbin submit a request to rename the project (Done by Eli Qiao) | 03:04 |
*** shaohe_feng has joined #openstack-meeting | 03:04 | |
hongbin | #link https://review.openstack.org/#/c/326306/ | 03:04 |
hongbin | #link https://review.openstack.org/#/c/329247/ | 03:04 |
hongbin | Eli proposed two patches to rename hte project | 03:04 |
hongbin | The first patch rename the IRC and launchpad | 03:04 |
*** ijw has quit IRC | 03:04 | |
hongbin | The second patch rename in gerrit and git | 03:04 |
hongbin | It looks the second patch will take a while to land | 03:05 |
yanyanhu | need to wait for infra team's schedule to change gerrit and git | 03:05 |
*** banix has quit IRC | 03:05 | |
hongbin | Hopefully, the first patch will land soon | 03:05 |
hongbin | yes | 03:05 |
*** abcxyz has quit IRC | 03:05 | |
*** yamamoto_ has joined #openstack-meeting | 03:05 | |
hongbin | I was told that we should expect months for the next rename | 03:05 |
xiucai | hi, xiucai just act as an auditor now :), may be core in someday. | 03:05 |
hongbin | We will talk about the transition period during these few months | 03:06 |
*** mickeys has quit IRC | 03:06 | |
hongbin | xiucai: Hey, welcome to the team meeting | 03:06 |
hongbin | 2. hongbin create a bp for glance integration (DONE) | 03:06 |
hongbin | #link https://blueprints.launchpad.net/zun/+spec/glance-integration | 03:06 |
hongbin | Any comment for the review actio item? | 03:07 |
hongbin | #topic Project rename procedure | 03:07 |
*** openstack changes topic to "Project rename procedure (Meeting topic: zun)" | 03:07 | |
hongbin | #link https://review.openstack.org/#/c/326306/ Rename request for infra team | 03:07 |
hongbin | Let's discuss how should we do for the transition period | 03:07 |
yanyanhu | hi, hongbin, so the job in gate side may not work during this migratin? | 03:07 |
yanyanhu | s/migratin/migration | 03:07 |
hongbin | which is from right now to the next rename | 03:08 |
hongbin | yanyanhu: It looks the gate is working fine | 03:08 |
*** links has joined #openstack-meeting | 03:08 | |
yanyanhu | hongbin, nice | 03:08 |
hongbin | I saw the gate job passed | 03:08 |
yanyanhu | so we just need to revise the gate job template after gerrit name is changed | 03:08 |
flwang | o/ | 03:09 |
flwang | sorry in another meeting | 03:09 |
*** thorst has quit IRC | 03:09 | |
eliqiao | hongbin: one more thing, dsvm only setup services, there is no any test case yet. | 03:09 |
*** abcxyz has joined #openstack-meeting | 03:09 | |
eliqiao | hongbin: so we'd better to manually check devstack logs/screen log of service | 03:09 |
hongbin | yanyanhu: maybe. Yes | 03:09 |
hongbin | flwang: hey. NP | 03:09 |
eliqiao | hongbin: I just enable zun-compute service | 03:09 |
eliqiao | #link https://review.openstack.org/328854 | 03:10 |
yanyanhu | hi, eliqiao, has post/pre_test hook been set up | 03:10 |
hongbin | eliqiao: ack | 03:10 |
eliqiao | yanyanhu: not yet right now. | 03:10 |
yanyanhu | if so, it's easy to add real test cases | 03:10 |
yanyanhu | I see | 03:10 |
hongbin | Then, I guess here is the plan | 03:11 |
eliqiao | yanyanhu: I will try to see if I can enable post hook. but if some one is interested with it, I am gald to help | 03:11 |
yanyanhu | eliqiao, thanks :) | 03:11 |
*** grassass has quit IRC | 03:12 | |
hongbin | Plan 1. starting using [zun] for email, wiki, launchpad | 03:12 |
Qiming | what is zun-compute? | 03:12 |
Qiming | what is zun-conductor? | 03:12 |
hongbin | Yes, let's discuss the architecure | 03:12 |
yanyanhu | it's easy, just need to add them to gate template. And the first version of test_hooks can be empty script | 03:12 |
adisky | yes i have few doubts on architecture.. | 03:13 |
hongbin | OK. Before we talk about the archtecture, anything else for the renaming periodi | 03:13 |
hongbin | period | 03:13 |
*** shaohe_feng has quit IRC | 03:13 | |
haiwei_ | the design looks like Nova's design? | 03:13 |
mkrai | https://review.openstack.org/#/c/317699/ | 03:13 |
mkrai | hongbin: We should add Zunclient also | 03:14 |
mkrai | #link https://review.openstack.org/#/c/317699/ | 03:14 |
*** ub has quit IRC | 03:14 | |
hongbin | mkrai: I think we should land that patch right now (not wait for the renam) | 03:14 |
hongbin | rename | 03:14 |
mkrai | Ok I will do that | 03:14 |
hongbin | Then we have a client to work with | 03:14 |
hongbin | mkrai: thx | 03:14 |
hongbin | Any other comment for the renaming? | 03:14 |
hongbin | OK. Let's discuss the architecture | 03:15 |
hongbin | #topic Zun architecture | 03:15 |
*** openstack changes topic to "Zun architecture (Meeting topic: zun)" | 03:15 | |
hongbin | From my understanding, the architecture is a copy of Nova. correct? | 03:16 |
mkrai | Yes it seems so | 03:16 |
*** shaohe_feng has joined #openstack-meeting | 03:16 | |
*** piet_ has quit IRC | 03:16 | |
sudipto | I could see some patches that copied the exact code from nova, including the objects | 03:16 |
mkrai | But we need to look at our requirement also before copying | 03:16 |
adisky | yes.. | 03:16 |
hongbin | agree | 03:17 |
hongbin | Nova architecture is not necessary fit for us | 03:17 |
mkrai | Because as told many times containers lifecycle is different from VMs | 03:17 |
sudipto | yeah - was the same thought in my head too. | 03:17 |
mkrai | So do we need compute service? | 03:18 |
yanyanhu | versioned object is very helpful I think :) we should support it if possible. Although some effort to set it up | 03:18 |
*** dimtruck is now known as zz_dimtruck | 03:18 | |
eliqiao | yanyanhu: Sure, we need object | 03:18 |
eliqiao | mkrai: yeah, we need to discuss about compute serive | 03:18 |
sudipto | yanyanhu, agreed, before we write the objects though, we need to discuss the data model and use cases in detail IMO | 03:19 |
*** abcxyz has quit IRC | 03:19 | |
*** ssalagame has quit IRC | 03:19 | |
yanyanhu | sudipto, yes, agree | 03:19 |
haiwei_ | what about making some specs and then starting to code | 03:19 |
sudipto | It seems that the API layer in Nova is kinda similar to what we would want to do... | 03:19 |
eliqiao | The thing is how we connect with HOST from zun-conductor? | 03:19 |
Wenzhi | speaking of objects and data model, I have a patch intend to add container object https://review.openstack.org/#/c/328726/ | 03:19 |
yanyanhu | about whether we need sun-compute, I think that depends on what responsibility we want conductor to take | 03:19 |
yanyanhu | eliqiao, bingo, I have the same question | 03:20 |
*** abcxyz has joined #openstack-meeting | 03:20 | |
hongbin | I think we need a sort-of local agent | 03:20 |
hongbin | In nova, it is nova-compute, in aws, it is called ecs-agent or somthing | 03:21 |
yanyanhu | in nova, conductor is a bridge between compute and API? | 03:21 |
eliqiao | should we though REST (for exmaple we can use docker-py to connect a remote docker daemon), but I think we may need to control NIC/Storage later .. | 03:21 |
sudipto | yanyanhu, it's between the compute and the DB. | 03:21 |
yanyanhu | ah, right | 03:21 |
hongbin | Basically, nova-conductor is a proxy to DB | 03:21 |
haiwei_ | conductor seems a bridge between compute and DB, yanyanhu? | 03:21 |
eliqiao | conductor is for upgrade and access DB and also it's task flow manager. | 03:21 |
*** zhurong has quit IRC | 03:22 | |
mkrai | eliqiao: We would need docker on the host to connect | 03:22 |
yanyanhu | yes, basically a bridge between compute agent and core service | 03:22 |
yanyanhu | which talks with DB directly | 03:22 |
Qiming | Wenzhi, thanks for the patch (https://review.openstack.org/#/c/328726/) but it is really tooooo big to review, it is combining a lot of things into a single patch | 03:22 |
Wenzhi | actually nova-conductor also handle some build/rebuild tasks | 03:22 |
Wenzhi | and also call nova-scheduler to filter out dest compute host | 03:23 |
eliqiao | mkrai: but if we have zun-compute, the connection between conductor and host is, conductor talk to compute and compute talk to docker daemon locally. | 03:23 |
sudipto | I do believe there's a need for an agent, that is probably going to have stevedoor plugins loaded - based on the driver (backend) used. | 03:23 |
Wenzhi | Qiming: sorry, I will split it into several small patches | 03:23 |
sudipto | s/stevedoor/stevedore | 03:23 |
haiwei_ | It seems we are coding first, and then discussing the design | 03:23 |
sudipto | haiwei_, +1 | 03:23 |
*** shaohe_feng has quit IRC | 03:23 | |
yanyanhu | haiwei_, :) | 03:24 |
mkrai | eliqiao: Ack. Later we might need to talk to openstack services also to manage things. So we would need compute service | 03:24 |
Qiming | why don't we have the conductor talk to the local daemon directly? | 03:24 |
eliqiao | sudipto: agree, I think zun-compute(agent) could be a option compoment (driver specific) | 03:24 |
haiwei_ | it is right? | 03:24 |
yanyanhu | mkrai, agree | 03:24 |
hongbin | Qiming: good question. What is the pros and cons? | 03:24 |
*** csomerville has quit IRC | 03:24 | |
*** Wang_Jian has joined #openstack-meeting | 03:24 | |
*** shaohe_feng has joined #openstack-meeting | 03:24 | |
mkrai | Qiming: Later we might need to talk to openstack services also to manage things. So we would need compute service | 03:24 |
eliqiao | Qiming: do you mean we run conductor on each host? | 03:25 |
Qiming | we can have a single conductor (conceptually single ...) to talk to container daemons on all nodes | 03:25 |
*** tochi has quit IRC | 03:26 | |
*** jungleboyj has quit IRC | 03:26 | |
hongbin | Qiming: what is the advantage? | 03:26 |
Qiming | have that single conductor to speak different dialects | 03:26 |
sudipto | Qiming, then you would complicate the conductor IMo | 03:26 |
eliqiao | per my understanding, if we want to use kuryr, we need to install kuryr and neutron agent on each host, right? | 03:27 |
Qiming | one of the key value of zun, as I see it, is it can provide a LCD among all container backends | 03:27 |
eliqiao | Qiming: could you tell what LCD stand for? | 03:27 |
*** sacharya_ has quit IRC | 03:27 | |
sudipto | Qiming, what would be the LCD in this case? | 03:27 |
hongbin | Lowest common dinominator | 03:27 |
Qiming | yes | 03:28 |
*** sacharya has joined #openstack-meeting | 03:28 | |
*** coolsvap has joined #openstack-meeting | 03:28 | |
eliqiao | Thanks hongbin , good to know that. | 03:28 |
hongbin | Qiming: but both Nova and AWS have local agents. If Zun don't have it, I guess we will face limitation to perform local operations | 03:28 |
Qiming | from a deployer/user's perspective, each deployed components need to be managed | 03:29 |
hongbin | Qiming: e.g. setting up the network, storage, image, file system etc. | 03:29 |
*** yamahata has joined #openstack-meeting | 03:29 | |
hongbin | ok | 03:29 |
mkrai | hongbin: Agree | 03:29 |
Wenzhi | hongbin: agree | 03:29 |
eliqiao | hongbin: yes, I have same question on network, storaget etc, @ Qiming how to manage them locally? | 03:30 |
*** yamamoto_ has quit IRC | 03:30 | |
*** sacharya_ has joined #openstack-meeting | 03:30 | |
Qiming | I'm leaning more towards a remote management | 03:30 |
Qiming | the ansible way of managing things, instead of the chef/puppet way | 03:30 |
hongbin | Like a lean agent, and a heavy conductor? | 03:31 |
Qiming | in an ideal setup, we don't need agents at all, if possible | 03:31 |
*** abcxyz has quit IRC | 03:31 | |
*** iyamahat has joined #openstack-meeting | 03:32 | |
*** abcxyz has joined #openstack-meeting | 03:32 | |
*** sacharya has quit IRC | 03:32 | |
hongbin | Yes, maybe | 03:32 |
Qiming | just some ideas for team to consider | 03:32 |
Qiming | maybe eventually, we will need agents installed, configured and maintained on each underlying nodes | 03:32 |
*** yuanying has quit IRC | 03:33 | |
Qiming | when we are there, we will know it | 03:33 |
eliqiao | hmm... I got a question, if we leverage kuryr, we will install kuryr and nerutron agent on host... in this case, it's not good. | 03:33 |
*** sacharya has joined #openstack-meeting | 03:33 | |
*** julenlar has joined #openstack-meeting | 03:33 | |
sudipto | Qiming, it's a good thought but i guess there are some unavoidable cases. For example - how do you configure the bridges? | 03:33 |
yanyanhu | eliqiao, installation is easy, but configure and setup... | 03:34 |
Qiming | eliqiao, you mean having zun to install kuryr ? | 03:34 |
*** shaohe_feng has quit IRC | 03:34 | |
*** yuanying has joined #openstack-meeting | 03:34 | |
*** karthikp_ has quit IRC | 03:34 | |
*** karthikp_ has joined #openstack-meeting | 03:34 | |
*** shaohe_feng has joined #openstack-meeting | 03:34 | |
hongbin | If we follows Nova pattern, operators install Kuryr and Kuryr agents | 03:34 |
Qiming | my knowledge on kuryr is very very limited, but can we offload those set up to kuryr? | 03:35 |
hongbin | And Kuryr agents needs to be installed at each host | 03:35 |
hongbin | sure | 03:35 |
Qiming | then we talk to Kuryr? | 03:35 |
hongbin | For networking part, I guess that will work | 03:35 |
eliqiao | Qiming: I am not sure, just thinking about your view of "agent", too many agent been installed on host. | 03:36 |
*** yamamoto_ has joined #openstack-meeting | 03:36 | |
Qiming | yes, that is what I am really worrying about | 03:36 |
*** sacharya_ has quit IRC | 03:36 | |
eliqiao | hongbin: Kuryr is only a connect bridge of neutron and docker, seems zun shouldn't talk with it at all. | 03:36 |
sudipto | From the API per say - the request sent is more like "I want the container to be deployed" - that's one REST call...and then the local agent is responsible for orchestrating that whole request by making several local calls to the local daemon/ovs/xyz and fullfills that request. So i see a benefit there. | 03:37 |
*** julenl has quit IRC | 03:37 | |
* sudipto states the benefits of a local agent | 03:37 | |
Qiming | em, the benefit sounds real | 03:38 |
*** amitgandhinz has joined #openstack-meeting | 03:39 | |
* eliqiao has some concerns with sudipto, but yes agent bring maintain effort. | 03:39 | |
*** klkumar has joined #openstack-meeting | 03:39 | |
*** asselin_ has quit IRC | 03:40 | |
*** darvon has quit IRC | 03:40 | |
hongbin | Qiming: do you change your point of view about local agent, or this needs to be discussed further? | 03:40 |
* eliqiao s/some/same | 03:40 | |
Qiming | I'll keep the viewpoint to myself | 03:40 |
*** darvon has joined #openstack-meeting | 03:40 | |
hongbin | ok | 03:41 |
Qiming | do not want to block the team from progressing | 03:41 |
sudipto | Qiming, it's a very good thought IMHO, and we could think about this as we go maybe. | 03:41 |
hongbin | Qiming: If the team want to implement a local agent, what you will suggest about the implementation? | 03:41 |
Qiming | my suggestion is that we can focus on things we MUST do in this cycle | 03:41 |
hongbin | agree | 03:42 |
sudipto | agreed. | 03:42 |
eliqiao | +1 | 03:42 |
Qiming | some basic data models, a generic, minimal API design/implementation, with test case covered | 03:42 |
Wenzhi | agreed | 03:43 |
eliqiao | Qiming: I am +1 on the basic stuff. | 03:43 |
*** amitgandhinz has quit IRC | 03:43 | |
hongbin | I would suggest to implement the local agent as light as possible, if possibly, containerize the local agent | 03:44 |
hongbin | For this, reference AWS agent implementation | 03:44 |
haiwei_ | it's better tolist out the basic tasks somewhere | 03:44 |
*** shaohe_feng has quit IRC | 03:44 | |
*** vishwanathj has joined #openstack-meeting | 03:44 | |
hongbin | #link https://github.com/aws/amazon-ecs-agent | 03:44 |
*** shaohe_feng has joined #openstack-meeting | 03:44 | |
*** ociuhandu has quit IRC | 03:45 | |
Qiming | +1 haiwei_ | 03:45 |
hongbin | OK, want an etherpad for that? | 03:45 |
*** azbiswas has joined #openstack-meeting | 03:45 | |
sudipto | hongbin, an etherpad would be nice I feel. | 03:46 |
mkrai | Yes would be great | 03:46 |
hongbin | #link https://etherpad.openstack.org/p/zun-basic-tasks | 03:46 |
hongbin | We have 15 minutes left | 03:46 |
hongbin | 10 minutes to work on it maybe | 03:47 |
hongbin | 5 minutes open discussion | 03:47 |
Qiming | any updates from API work now? | 03:47 |
mkrai | I have posted a patch for Container API controller | 03:47 |
mkrai | But that needs update | 03:47 |
Qiming | thx, mkrai | 03:47 |
mkrai | #link https://review.openstack.org/#/c/328444/ | 03:48 |
Qiming | hoho, 1718 lines added | 03:49 |
*** ociuhandu has joined #openstack-meeting | 03:49 | |
Qiming | need two days to go through them, :) | 03:49 |
hongbin | :) | 03:49 |
yuanying | It seems almost code are copied from old magnum | 03:50 |
*** azbiswas has quit IRC | 03:50 | |
*** tochi has joined #openstack-meeting | 03:50 | |
mkrai | Yes yuanying | 03:50 |
mkrai | Need to remove wsme code | 03:50 |
hongbin | Yes, it looks most folks are from Magnum | 03:50 |
yanyanhu | :) | 03:51 |
mkrai | hongbin: :) | 03:51 |
yuanying | I don't like start/stop.../action_controller.. personally | 03:51 |
*** abcxyz has quit IRC | 03:51 | |
yanyanhu | so we learned something about magnum as well :P | 03:51 |
*** abcxyz has joined #openstack-meeting | 03:52 | |
sudipto | One thing is - just making zun as a service in openstack that manages containers - need further detailing w.r.t USPs IMHO. As in are we targeting just the OpenStack existing environments or are we also telling - that this provides something unique? | 03:52 |
*** JRobinson__ is now known as JRobinson__afl | 03:52 | |
*** JRobinson__afl is now known as JRobinson__afk | 03:52 | |
mkrai | yuanying: Please comment on the patch. I will update accordingly | 03:52 |
mkrai | Thanks for your input yuanying | 03:52 |
hongbin | sudipto: good point | 03:52 |
sudipto | At this point in time, we are in rush to replicate another openstack service i feel. | 03:52 |
* Qiming shares the same feeling | 03:53 | |
*** cody-somerville has joined #openstack-meeting | 03:53 | |
hongbin | Yes, I am thinking we need a spec to clarify the overall design and roadmap | 03:53 |
mkrai | +1 hongbin | 03:53 |
*** longxiongqiu has quit IRC | 03:53 | |
*** zhangshuai_ has quit IRC | 03:53 | |
Wenzhi | agree hongbin | 03:53 |
mkrai | I am interested in working on the spec. But would need support from all | 03:53 |
hongbin | I can work on that, but need a few more meetings to discuss with you to drive consensus on the overall design first | 03:54 |
hongbin | sure, we could put the spec in an etherpad | 03:54 |
hongbin | THen, everyone can contribute | 03:54 |
*** shaohe_feng has quit IRC | 03:54 | |
mkrai | It will be huge | 03:54 |
hongbin | #topic Open Discussion | 03:54 |
*** openstack changes topic to "Open Discussion (Meeting topic: zun)" | 03:54 | |
hongbin | #action hongbin create an etherpad as a draft of Zun design spec | 03:55 |
*** shaohe_feng has joined #openstack-meeting | 03:55 | |
sudipto | I would urge everyone to put your thoughts on that etherpad - and come up with ideas that could be unique to zun (not about how similar it is to nova/docker or xyz) | 03:56 |
*** ayoung has quit IRC | 03:56 | |
hongbin | agree | 03:56 |
hongbin | OK. Anything else to discuss? | 03:57 |
hongbin | If not, let's wrap up a bit earlier | 03:57 |
*** vishwanathj has quit IRC | 03:58 | |
hongbin | All, thanks for joining ht emeeting | 03:58 |
mkrai | Thanks everyone | 03:58 |
hongbin | Hope to see you all in the next meeting | 03:58 |
hongbin | #endmeeting | 03:58 |
yanyanhu | thanks | 03:58 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 03:58 | |
openstack | Meeting ended Tue Jun 14 03:58:28 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 03:58 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/zun/2016/zun.2016-06-14-03.00.html | 03:58 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/zun/2016/zun.2016-06-14-03.00.txt | 03:58 |
openstack | Log: http://eavesdrop.openstack.org/meetings/zun/2016/zun.2016-06-14-03.00.log.html | 03:58 |
*** amotoki has joined #openstack-meeting | 03:58 | |
*** vishwanathj has joined #openstack-meeting | 03:58 | |
*** haiwei_ has quit IRC | 03:59 | |
*** edtubill has joined #openstack-meeting | 03:59 | |
*** hongbin has quit IRC | 04:00 | |
*** abcxyz has quit IRC | 04:00 | |
*** Vivek__ has quit IRC | 04:01 | |
*** abcxyz has joined #openstack-meeting | 04:03 | |
*** yamada-h has joined #openstack-meeting | 04:03 | |
*** xiucai has left #openstack-meeting | 04:04 | |
*** myoung has quit IRC | 04:04 | |
*** shaohe_feng has quit IRC | 04:04 | |
*** myoung has joined #openstack-meeting | 04:05 | |
*** yuanying has quit IRC | 04:05 | |
*** shaohe_feng has joined #openstack-meeting | 04:05 | |
*** ociuhandu has quit IRC | 04:05 | |
*** Poornima has joined #openstack-meeting | 04:07 | |
*** thorst has joined #openstack-meeting | 04:07 | |
*** yuanying has joined #openstack-meeting | 04:07 | |
*** ssalagame has joined #openstack-meeting | 04:08 | |
*** manjeets has left #openstack-meeting | 04:08 | |
*** dmorita has joined #openstack-meeting | 04:11 | |
*** shz has joined #openstack-meeting | 04:11 | |
*** hanzhang has quit IRC | 04:14 | |
*** thorst has quit IRC | 04:14 | |
*** Namrata has quit IRC | 04:14 | |
*** shaohe_feng has quit IRC | 04:15 | |
*** edtubill has quit IRC | 04:15 | |
*** shaohe_feng has joined #openstack-meeting | 04:15 | |
*** markvoelker has quit IRC | 04:16 | |
*** vishwana_ has joined #openstack-meeting | 04:17 | |
*** longxiongqiu has joined #openstack-meeting | 04:18 | |
*** anilvenkata has joined #openstack-meeting | 04:20 | |
*** vishwanathj has quit IRC | 04:20 | |
*** vishwana_ has quit IRC | 04:22 | |
*** cody-somerville_ has joined #openstack-meeting | 04:23 | |
*** longxiongqiu has quit IRC | 04:23 | |
*** vishwanathj has joined #openstack-meeting | 04:24 | |
*** grassass has joined #openstack-meeting | 04:24 | |
*** zhurong has joined #openstack-meeting | 04:25 | |
*** shaohe_feng has quit IRC | 04:25 | |
*** shaohe_feng has joined #openstack-meeting | 04:26 | |
*** Daisy_ has quit IRC | 04:26 | |
*** cartik has joined #openstack-meeting | 04:27 | |
*** garthb has joined #openstack-meeting | 04:27 | |
*** dmorita has quit IRC | 04:27 | |
*** dtrainor has quit IRC | 04:29 | |
*** zhurong has quit IRC | 04:29 | |
*** dneary has quit IRC | 04:32 | |
*** fnaval has quit IRC | 04:32 | |
*** comay has quit IRC | 04:32 | |
*** hdaniel has joined #openstack-meeting | 04:32 | |
*** fnaval has joined #openstack-meeting | 04:33 | |
*** sbalukoff has joined #openstack-meeting | 04:34 | |
*** shaohe_feng has quit IRC | 04:35 | |
*** shaohe_feng has joined #openstack-meeting | 04:35 | |
*** abcxyz has quit IRC | 04:36 | |
*** cody-somerville has quit IRC | 04:37 | |
*** sudipto has quit IRC | 04:37 | |
*** zhurong has joined #openstack-meeting | 04:38 | |
*** abcxyz has joined #openstack-meeting | 04:39 | |
*** pcaruana has quit IRC | 04:39 | |
*** amitgandhinz has joined #openstack-meeting | 04:39 | |
*** Leo_ has quit IRC | 04:40 | |
*** irenab has quit IRC | 04:41 | |
*** Poornima has quit IRC | 04:43 | |
*** Poornima has joined #openstack-meeting | 04:43 | |
*** amitgandhinz has quit IRC | 04:44 | |
*** dmacpher has quit IRC | 04:44 | |
*** ekcs has joined #openstack-meeting | 04:45 | |
*** shaohe_feng has quit IRC | 04:45 | |
*** shaohe_feng has joined #openstack-meeting | 04:46 | |
*** ekcs has quit IRC | 04:49 | |
*** nadya has joined #openstack-meeting | 04:51 | |
*** yamada-h has quit IRC | 04:53 | |
*** klkumar has quit IRC | 04:53 | |
*** klkumar1 has joined #openstack-meeting | 04:53 | |
*** klkumar1 has quit IRC | 04:54 | |
*** yamada-h has joined #openstack-meeting | 04:54 | |
*** klkumar has joined #openstack-meeting | 04:55 | |
*** ssalagame has quit IRC | 04:55 | |
*** shaohe_feng has quit IRC | 04:56 | |
*** shaohe_feng has joined #openstack-meeting | 04:56 | |
*** edtubill has joined #openstack-meeting | 04:57 | |
*** mrmartin has joined #openstack-meeting | 04:58 | |
*** yamada-h has quit IRC | 04:59 | |
*** ub has joined #openstack-meeting | 05:04 | |
*** sheel has joined #openstack-meeting | 05:05 | |
*** yamada-h has joined #openstack-meeting | 05:05 | |
*** shaohe_feng has quit IRC | 05:06 | |
*** shaohe_feng has joined #openstack-meeting | 05:07 | |
*** Daisy has joined #openstack-meeting | 05:07 | |
*** iyamahat has quit IRC | 05:08 | |
*** lpetrut has joined #openstack-meeting | 05:09 | |
*** Niham has joined #openstack-meeting | 05:10 | |
*** Daisy_ has joined #openstack-meeting | 05:11 | |
*** Daisy has quit IRC | 05:11 | |
*** cody-somerville has joined #openstack-meeting | 05:12 | |
*** cody-somerville has quit IRC | 05:12 | |
*** cody-somerville has joined #openstack-meeting | 05:12 | |
*** thorst has joined #openstack-meeting | 05:12 | |
*** sacharya has quit IRC | 05:16 | |
*** cody-somerville has quit IRC | 05:16 | |
*** cody-somerville_ has quit IRC | 05:16 | |
*** sacharya has joined #openstack-meeting | 05:16 | |
*** shaohe_feng has quit IRC | 05:16 | |
*** markvoelker has joined #openstack-meeting | 05:17 | |
*** shaohe_feng has joined #openstack-meeting | 05:17 | |
*** salv-orl_ has quit IRC | 05:17 | |
*** ljxiash has joined #openstack-meeting | 05:17 | |
*** salv-orlando has joined #openstack-meeting | 05:18 | |
*** sridharg has joined #openstack-meeting | 05:18 | |
*** cartik has quit IRC | 05:19 | |
*** azbiswas has joined #openstack-meeting | 05:19 | |
*** thorst has quit IRC | 05:19 | |
*** dneary has joined #openstack-meeting | 05:19 | |
*** itzdilip has joined #openstack-meeting | 05:20 | |
*** azbiswas has quit IRC | 05:21 | |
*** markvoelker has quit IRC | 05:22 | |
*** azbiswas has joined #openstack-meeting | 05:23 | |
*** azbiswas has quit IRC | 05:23 | |
*** karthikp_ has quit IRC | 05:24 | |
*** jprovazn has joined #openstack-meeting | 05:24 | |
*** mrmartin has quit IRC | 05:24 | |
*** JRobinson__afk is now known as JRobinson__ | 05:26 | |
*** shaohe_feng has quit IRC | 05:26 | |
*** ekcs has joined #openstack-meeting | 05:27 | |
*** dneary has quit IRC | 05:27 | |
*** shaohe_feng has joined #openstack-meeting | 05:27 | |
*** dmorita has joined #openstack-meeting | 05:27 | |
*** Niham has quit IRC | 05:27 | |
*** yamamoto_ has quit IRC | 05:28 | |
*** salv-orl_ has joined #openstack-meeting | 05:29 | |
*** nadya has quit IRC | 05:29 | |
*** salv-orlando has quit IRC | 05:31 | |
*** dmorita has quit IRC | 05:31 | |
*** Niham has joined #openstack-meeting | 05:32 | |
*** salv-orl_ has quit IRC | 05:34 | |
*** salv-orlando has joined #openstack-meeting | 05:34 | |
*** shaohe_feng has quit IRC | 05:37 | |
*** shaohe_feng has joined #openstack-meeting | 05:37 | |
*** yujunz has joined #openstack-meeting | 05:38 | |
*** amitgandhinz has joined #openstack-meeting | 05:40 | |
*** nadya has joined #openstack-meeting | 05:41 | |
*** sarob has joined #openstack-meeting | 05:41 | |
*** ekcs has quit IRC | 05:41 | |
*** amitgandhinz has quit IRC | 05:44 | |
*** sarob has quit IRC | 05:46 | |
*** shaohe_feng has quit IRC | 05:47 | |
*** tfukushi_ has joined #openstack-meeting | 05:47 | |
*** garthb has quit IRC | 05:47 | |
*** shaohe_feng has joined #openstack-meeting | 05:48 | |
*** tfukushima has quit IRC | 05:49 | |
*** vishwanathj has quit IRC | 05:54 | |
*** mbound has joined #openstack-meeting | 05:55 | |
*** nadya has quit IRC | 05:55 | |
*** ekcs has joined #openstack-meeting | 05:56 | |
*** shaohe_feng has quit IRC | 05:57 | |
*** shaohe_feng has joined #openstack-meeting | 05:58 | |
*** Sukhdev has joined #openstack-meeting | 06:00 | |
*** roxanaghe has joined #openstack-meeting | 06:00 | |
*** mbound has quit IRC | 06:00 | |
*** AndroUser2 has joined #openstack-meeting | 06:00 | |
*** roxanaghe has quit IRC | 06:00 | |
*** yuval has joined #openstack-meeting | 06:04 | |
*** AndroUser2 has quit IRC | 06:07 | |
*** shaohe_feng has quit IRC | 06:07 | |
*** edtubill has quit IRC | 06:08 | |
*** shaohe_feng has joined #openstack-meeting | 06:08 | |
*** reedip has joined #openstack-meeting | 06:09 | |
*** JRobinson__ has quit IRC | 06:10 | |
*** rcernin has joined #openstack-meeting | 06:11 | |
*** Daisy_ has quit IRC | 06:11 | |
*** comay has joined #openstack-meeting | 06:11 | |
*** Daisy has joined #openstack-meeting | 06:12 | |
*** pfallenop has quit IRC | 06:12 | |
*** edtubill has joined #openstack-meeting | 06:12 | |
*** salv-orlando has quit IRC | 06:13 | |
*** salv-orlando has joined #openstack-meeting | 06:14 | |
*** pfallenop has joined #openstack-meeting | 06:15 | |
*** Daisy has quit IRC | 06:16 | |
*** pcaruana has joined #openstack-meeting | 06:16 | |
*** thorst has joined #openstack-meeting | 06:16 | |
*** Poornima has quit IRC | 06:17 | |
*** yamamoto_ has joined #openstack-meeting | 06:17 | |
*** shaohe_feng has quit IRC | 06:18 | |
*** vishwanathj has joined #openstack-meeting | 06:19 | |
*** shaohe_feng has joined #openstack-meeting | 06:21 | |
*** abcxyz has quit IRC | 06:21 | |
*** rbartal has joined #openstack-meeting | 06:21 | |
*** abcxyz has joined #openstack-meeting | 06:22 | |
*** yamahata has quit IRC | 06:23 | |
*** edtubill has quit IRC | 06:24 | |
*** thorst has quit IRC | 06:24 | |
*** iyamahat has joined #openstack-meeting | 06:25 | |
*** azbiswas has joined #openstack-meeting | 06:25 | |
*** yamahata has joined #openstack-meeting | 06:26 | |
*** xinwu has joined #openstack-meeting | 06:27 | |
*** shaohe_feng has quit IRC | 06:28 | |
*** shaohe_feng has joined #openstack-meeting | 06:29 | |
*** azbiswas has quit IRC | 06:30 | |
*** henrynash_ has joined #openstack-meeting | 06:30 | |
*** Poornima has joined #openstack-meeting | 06:32 | |
*** Daisy has joined #openstack-meeting | 06:33 | |
*** shaohe_feng has quit IRC | 06:38 | |
*** shaohe_feng has joined #openstack-meeting | 06:39 | |
*** Sukhdev has quit IRC | 06:39 | |
*** amitgandhinz has joined #openstack-meeting | 06:41 | |
*** ihrachys has joined #openstack-meeting | 06:41 | |
*** mrmartin has joined #openstack-meeting | 06:42 | |
*** andreas_s has joined #openstack-meeting | 06:42 | |
*** sudipto has joined #openstack-meeting | 06:44 | |
*** ekcs has quit IRC | 06:44 | |
*** amitgandhinz has quit IRC | 06:45 | |
*** abcxyz has quit IRC | 06:46 | |
*** nmagnezi has joined #openstack-meeting | 06:46 | |
*** shaohe_feng has quit IRC | 06:48 | |
*** shaohe_feng has joined #openstack-meeting | 06:49 | |
*** adiantum has joined #openstack-meeting | 06:49 | |
*** ociuhandu has joined #openstack-meeting | 06:50 | |
*** tesseract has joined #openstack-meeting | 06:56 | |
*** Hosam has joined #openstack-meeting | 06:56 | |
*** Hosam has quit IRC | 06:56 | |
*** Hosam has joined #openstack-meeting | 06:56 | |
*** iyamahat has quit IRC | 06:59 | |
*** shaohe_feng has quit IRC | 06:59 | |
*** shaohe_feng has joined #openstack-meeting | 06:59 | |
*** mrmartin has quit IRC | 06:59 | |
*** rossella_s has joined #openstack-meeting | 07:00 | |
*** abcxyz has joined #openstack-meeting | 07:00 | |
*** grassass has quit IRC | 07:02 | |
*** sacharya has quit IRC | 07:03 | |
*** abcxyz has quit IRC | 07:04 | |
*** hoangcx has joined #openstack-meeting | 07:06 | |
*** shaohe_feng has quit IRC | 07:09 | |
*** shaohe_feng has joined #openstack-meeting | 07:10 | |
*** zeih has joined #openstack-meeting | 07:11 | |
*** adiantum has quit IRC | 07:12 | |
*** mrmartin has joined #openstack-meeting | 07:12 | |
*** Guest90337 has joined #openstack-meeting | 07:15 | |
*** hoangcx has quit IRC | 07:17 | |
*** markvoelker has joined #openstack-meeting | 07:18 | |
*** shaohe_feng has quit IRC | 07:19 | |
*** shaohe_feng has joined #openstack-meeting | 07:20 | |
*** tfukushi_ has quit IRC | 07:20 | |
*** tfukushima has joined #openstack-meeting | 07:21 | |
*** pece has joined #openstack-meeting | 07:21 | |
*** jichen has joined #openstack-meeting | 07:21 | |
*** thorst has joined #openstack-meeting | 07:22 | |
*** tfukushima has quit IRC | 07:22 | |
*** tfukushima has joined #openstack-meeting | 07:22 | |
*** markvoelker has quit IRC | 07:22 | |
*** longxiongqiu has joined #openstack-meeting | 07:23 | |
*** jlanoux has joined #openstack-meeting | 07:26 | |
*** fzdarsky|afk has joined #openstack-meeting | 07:27 | |
*** hoangcx has joined #openstack-meeting | 07:28 | |
*** epico has quit IRC | 07:29 | |
*** thorst has quit IRC | 07:29 | |
*** shaohe_feng has quit IRC | 07:29 | |
*** shaohe_feng has joined #openstack-meeting | 07:30 | |
*** dixiaoli has joined #openstack-meeting | 07:30 | |
*** grassass has joined #openstack-meeting | 07:30 | |
*** pece has quit IRC | 07:32 | |
*** akamyshnikova has joined #openstack-meeting | 07:33 | |
*** irenab has joined #openstack-meeting | 07:35 | |
yamamoto_ | anyone here for networking-midonet meeting? | 07:35 |
yamamoto_ | #startmeeting networking_midonet | 07:36 |
openstack | Meeting started Tue Jun 14 07:36:21 2016 UTC and is due to finish in 60 minutes. The chair is yamamoto_. Information about MeetBot at http://wiki.debian.org/MeetBot. | 07:36 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 07:36 |
*** openstack changes topic to " (Meeting topic: networking_midonet)" | 07:36 | |
openstack | The meeting name has been set to 'networking_midonet' | 07:36 |
yamamoto_ | #topic agenda | 07:36 |
*** openstack changes topic to "agenda (Meeting topic: networking_midonet)" | 07:36 | |
yamamoto_ | #link https://wiki.openstack.org/wiki/Meetings/NetworkingMidoNet#Agenda_.282016-06-14.29 | 07:36 |
yamamoto_ | #topic announcements | 07:37 |
*** openstack changes topic to "announcements (Meeting topic: networking_midonet)" | 07:37 | |
*** jlanoux has quit IRC | 07:37 | |
*** tfukushima has quit IRC | 07:37 | |
yamamoto_ | ~1 month until n-2 | 07:38 |
*** jlanoux has joined #openstack-meeting | 07:38 | |
yamamoto_ | but we are still working on mitaka... | 07:38 |
*** iyamahat has joined #openstack-meeting | 07:38 | |
yamamoto_ | #link http://releases.openstack.org/newton/schedule.html | 07:38 |
*** tfukushima has joined #openstack-meeting | 07:39 | |
yamamoto_ | #topic bugs | 07:39 |
*** openstack changes topic to "bugs (Meeting topic: networking_midonet)" | 07:39 | |
*** epico has joined #openstack-meeting | 07:39 | |
yamamoto_ | #link https://bugs.launchpad.net/networking-midonet/ | 07:39 |
yamamoto_ | there are a few gate breaking bugs | 07:39 |
*** jlanoux has quit IRC | 07:39 | |
*** shaohe_feng has quit IRC | 07:40 | |
*** tfukushima has quit IRC | 07:40 | |
*** Wang_Jian has quit IRC | 07:40 | |
*** shaohe_feng has joined #openstack-meeting | 07:40 | |
yamamoto_ | i'll continue bug deputy | 07:41 |
yamamoto_ | honestly i'm getting skeptic about bug deputy role, as we don't actually rotate it. | 07:41 |
*** tfukushima has joined #openstack-meeting | 07:41 | |
*** yamahata has quit IRC | 07:41 | |
* yamamoto_ editing the bug deputy chart on wiki | 07:41 | |
*** amitgandhinz has joined #openstack-meeting | 07:41 | |
*** toscalix has joined #openstack-meeting | 07:42 | |
*** lpetrut has quit IRC | 07:42 | |
*** sarob has joined #openstack-meeting | 07:42 | |
yamamoto_ | #topic Open Discussion | 07:42 |
*** openstack changes topic to "Open Discussion (Meeting topic: networking_midonet)" | 07:42 | |
* yamamoto_ waiting a few minutes before closing the meeting | 07:43 | |
*** ub has quit IRC | 07:43 | |
*** salv-orlando has quit IRC | 07:44 | |
*** salv-orlando has joined #openstack-meeting | 07:44 | |
*** iyamahat has quit IRC | 07:46 | |
*** amitgandhinz has quit IRC | 07:46 | |
*** sarob has quit IRC | 07:47 | |
*** zeih has quit IRC | 07:47 | |
*** Na3iL has joined #openstack-meeting | 07:47 | |
*** grazzazz has joined #openstack-meeting | 07:49 | |
*** grassass has quit IRC | 07:49 | |
*** nadya has joined #openstack-meeting | 07:50 | |
*** bcafarel has joined #openstack-meeting | 07:50 | |
*** dbecker has joined #openstack-meeting | 07:50 | |
*** nadya is now known as _nadya_ | 07:50 | |
*** shaohe_feng has quit IRC | 07:50 | |
*** shaohe_feng has joined #openstack-meeting | 07:50 | |
*** grazzazz has quit IRC | 07:50 | |
*** grassass has joined #openstack-meeting | 07:51 | |
*** Na3iL has quit IRC | 07:54 | |
*** bcafarelli has joined #openstack-meeting | 07:54 | |
*** bcafarel has quit IRC | 07:56 | |
*** hoangcx has quit IRC | 07:57 | |
*** hoangcx has joined #openstack-meeting | 07:58 | |
*** shaohe_feng has quit IRC | 08:00 | |
*** Na3iL has joined #openstack-meeting | 08:00 | |
*** jlanoux has joined #openstack-meeting | 08:02 | |
*** shaohe_feng has joined #openstack-meeting | 08:03 | |
*** zeih has joined #openstack-meeting | 08:05 | |
*** e0ne has joined #openstack-meeting | 08:05 | |
*** zeih has quit IRC | 08:06 | |
*** pnavarro has joined #openstack-meeting | 08:08 | |
*** zeih has joined #openstack-meeting | 08:09 | |
*** shaohe_feng has quit IRC | 08:10 | |
*** shaohe_feng has joined #openstack-meeting | 08:11 | |
*** egallen has joined #openstack-meeting | 08:17 | |
*** iyamahat has joined #openstack-meeting | 08:18 | |
*** Daisy has quit IRC | 08:19 | |
*** Daisy has joined #openstack-meeting | 08:19 | |
*** fzdarsky|afk has quit IRC | 08:19 | |
*** ub has joined #openstack-meeting | 08:19 | |
*** ljxiash has quit IRC | 08:20 | |
*** shaohe_feng has quit IRC | 08:21 | |
*** shaohe_feng has joined #openstack-meeting | 08:22 | |
*** iyamahat has quit IRC | 08:23 | |
*** muawiakhan has joined #openstack-meeting | 08:24 | |
*** itzdilip has quit IRC | 08:25 | |
*** mkrai has quit IRC | 08:25 | |
*** rmizuno has quit IRC | 08:25 | |
*** shu-mutou-AFK has quit IRC | 08:25 | |
*** thorst has joined #openstack-meeting | 08:26 | |
*** pece has joined #openstack-meeting | 08:28 | |
*** henrynash_ has quit IRC | 08:29 | |
*** shaohe_feng has quit IRC | 08:31 | |
*** shaohe_feng has joined #openstack-meeting | 08:32 | |
*** ljxiash has joined #openstack-meeting | 08:32 | |
*** hoangcx has quit IRC | 08:33 | |
*** xinwu has quit IRC | 08:34 | |
*** thorst has quit IRC | 08:34 | |
*** zhhuabj has quit IRC | 08:35 | |
*** hoangcx has joined #openstack-meeting | 08:35 | |
*** sshnaidm has quit IRC | 08:39 | |
*** manikanta_tadi has joined #openstack-meeting | 08:40 | |
*** vishwanathj has quit IRC | 08:40 | |
*** vishwanathj has joined #openstack-meeting | 08:41 | |
*** mickeys has joined #openstack-meeting | 08:41 | |
*** manikanta_tadi has quit IRC | 08:41 | |
*** shaohe_feng has quit IRC | 08:41 | |
*** manikanta_tadi has joined #openstack-meeting | 08:41 | |
*** shaohe_feng has joined #openstack-meeting | 08:42 | |
*** amitgandhinz has joined #openstack-meeting | 08:42 | |
*** Qiming is now known as Qiming_afk | 08:43 | |
*** mickeys has quit IRC | 08:43 | |
*** kzaitsev_mb has joined #openstack-meeting | 08:43 | |
*** Julien-zte has quit IRC | 08:44 | |
*** hoangcx has quit IRC | 08:45 | |
*** toddjohn has joined #openstack-meeting | 08:46 | |
*** amitgandhinz has quit IRC | 08:47 | |
*** yassine has joined #openstack-meeting | 08:48 | |
*** zhhuabj has joined #openstack-meeting | 08:48 | |
*** kzaitsev_mb has quit IRC | 08:50 | |
*** matrohon has joined #openstack-meeting | 08:50 | |
*** shaohe_feng has quit IRC | 08:51 | |
*** shaohe_feng has joined #openstack-meeting | 08:52 | |
*** manikanta_tadi has quit IRC | 08:54 | |
*** numans has quit IRC | 08:55 | |
*** vuntz has quit IRC | 08:58 | |
*** acoles_ is now known as acoles | 08:58 | |
*** vuntz has joined #openstack-meeting | 08:59 | |
*** shaohe_feng has quit IRC | 09:02 | |
*** hashar has joined #openstack-meeting | 09:02 | |
*** shaohe_feng has joined #openstack-meeting | 09:02 | |
*** Daisy_ has joined #openstack-meeting | 09:02 | |
*** vgridnev has quit IRC | 09:03 | |
*** Qiming_afk is now known as Qiming | 09:06 | |
*** Daisy has quit IRC | 09:06 | |
*** manikanta_tadi has joined #openstack-meeting | 09:07 | |
*** adiantum has joined #openstack-meeting | 09:08 | |
*** toddjohn has quit IRC | 09:08 | |
*** toddjohn has joined #openstack-meeting | 09:09 | |
*** lpetrut has joined #openstack-meeting | 09:10 | |
*** Daisy_ has quit IRC | 09:10 | |
*** Daisy has joined #openstack-meeting | 09:11 | |
*** shaohe_feng has quit IRC | 09:12 | |
*** shaohe_feng has joined #openstack-meeting | 09:12 | |
*** Niham has quit IRC | 09:13 | |
*** sambetts|afk is now known as sambetts | 09:14 | |
*** toddjohn has quit IRC | 09:14 | |
*** zeih has quit IRC | 09:15 | |
*** Daisy has quit IRC | 09:15 | |
*** amotoki has quit IRC | 09:15 | |
*** Na3iL has quit IRC | 09:19 | |
*** numans has joined #openstack-meeting | 09:19 | |
*** shaohe_feng has quit IRC | 09:22 | |
*** Guest90337 has quit IRC | 09:22 | |
*** shaohe_feng has joined #openstack-meeting | 09:23 | |
*** electrofelix has joined #openstack-meeting | 09:26 | |
*** zeih has joined #openstack-meeting | 09:27 | |
*** fzdarsky|afk has joined #openstack-meeting | 09:27 | |
*** julenlar is now known as julenl | 09:28 | |
*** thorst has joined #openstack-meeting | 09:32 | |
*** nisha_ has joined #openstack-meeting | 09:32 | |
*** shaohe_feng has quit IRC | 09:32 | |
*** shaohe_feng has joined #openstack-meeting | 09:33 | |
*** Na3iL has joined #openstack-meeting | 09:34 | |
*** yamada-h has quit IRC | 09:35 | |
*** ljxiash has quit IRC | 09:38 | |
*** ljxiash has joined #openstack-meeting | 09:38 | |
*** yujunz has quit IRC | 09:38 | |
*** thorst has quit IRC | 09:39 | |
*** sshnaidm has joined #openstack-meeting | 09:41 | |
*** shaohe_feng has quit IRC | 09:43 | |
*** amitgandhinz has joined #openstack-meeting | 09:43 | |
*** sarob has joined #openstack-meeting | 09:43 | |
*** ljxiash has quit IRC | 09:43 | |
*** shaohe_feng has joined #openstack-meeting | 09:43 | |
*** toddjohn has joined #openstack-meeting | 09:43 | |
*** nisha_ has quit IRC | 09:47 | |
*** amitgandhinz has quit IRC | 09:47 | |
*** toddjohn has quit IRC | 09:48 | |
*** sarob has quit IRC | 09:48 | |
*** zeih has quit IRC | 09:48 | |
*** ociuhandu has quit IRC | 09:51 | |
*** ygbo has joined #openstack-meeting | 09:51 | |
*** henrynash_ has joined #openstack-meeting | 09:52 | |
*** shaohe_feng has quit IRC | 09:53 | |
*** Niham has joined #openstack-meeting | 09:53 | |
*** shaohe_feng has joined #openstack-meeting | 09:54 | |
*** yanyanhu has left #openstack-meeting | 09:56 | |
*** tfukushima has quit IRC | 10:01 | |
*** claudiub has joined #openstack-meeting | 10:02 | |
*** neel has joined #openstack-meeting | 10:02 | |
*** kzaitsev_mb has joined #openstack-meeting | 10:02 | |
*** shaohe_feng has quit IRC | 10:03 | |
*** amotoki has joined #openstack-meeting | 10:04 | |
*** dixiaoli has quit IRC | 10:04 | |
*** nisha_ has joined #openstack-meeting | 10:04 | |
*** neel has left #openstack-meeting | 10:05 | |
*** shaohe_feng has joined #openstack-meeting | 10:06 | |
*** links has quit IRC | 10:07 | |
*** zhhuabj has quit IRC | 10:07 | |
*** AndroUser2 has joined #openstack-meeting | 10:08 | |
*** yujunz has joined #openstack-meeting | 10:10 | |
*** hoangcx has joined #openstack-meeting | 10:10 | |
*** AndroUser2 has quit IRC | 10:10 | |
*** mbound has joined #openstack-meeting | 10:13 | |
*** ociuhandu has joined #openstack-meeting | 10:13 | |
*** shaohe_feng has quit IRC | 10:13 | |
*** shaohe_feng has joined #openstack-meeting | 10:14 | |
*** dixiaoli has joined #openstack-meeting | 10:20 | |
*** muawiakhan has quit IRC | 10:20 | |
*** links has joined #openstack-meeting | 10:20 | |
*** nisha__ has joined #openstack-meeting | 10:21 | |
*** ivc_ has joined #openstack-meeting | 10:22 | |
*** zeih has joined #openstack-meeting | 10:23 | |
*** shaohe_feng has quit IRC | 10:24 | |
*** zhhuabj has joined #openstack-meeting | 10:24 | |
*** shaohe_feng has joined #openstack-meeting | 10:24 | |
*** zhurong has quit IRC | 10:24 | |
*** nisha_ has quit IRC | 10:25 | |
*** jlanoux_ has joined #openstack-meeting | 10:25 | |
*** hoangcx has quit IRC | 10:26 | |
*** hoangcx has joined #openstack-meeting | 10:26 | |
*** zeih has quit IRC | 10:27 | |
*** dmorita has joined #openstack-meeting | 10:28 | |
*** jlanoux has quit IRC | 10:28 | |
*** zeih has joined #openstack-meeting | 10:28 | |
*** obondarev has joined #openstack-meeting | 10:29 | |
*** egallen has quit IRC | 10:31 | |
*** sdague has joined #openstack-meeting | 10:31 | |
*** dmorita has quit IRC | 10:32 | |
*** amotoki_ has joined #openstack-meeting | 10:34 | |
*** shaohe_feng has quit IRC | 10:34 | |
*** epico has quit IRC | 10:35 | |
*** shaohe_feng has joined #openstack-meeting | 10:35 | |
*** thorst has joined #openstack-meeting | 10:35 | |
*** yamada-h has joined #openstack-meeting | 10:36 | |
*** toddjohn has joined #openstack-meeting | 10:37 | |
*** amotoki_ has quit IRC | 10:37 | |
*** amotoki_ has joined #openstack-meeting | 10:38 | |
*** salv-orlando has quit IRC | 10:38 | |
*** salv-orlando has joined #openstack-meeting | 10:39 | |
*** yamada-h has quit IRC | 10:41 | |
*** toddjohn has quit IRC | 10:42 | |
*** nisha__ is now known as nisha_ | 10:42 | |
*** amotoki has quit IRC | 10:42 | |
*** amitgandhinz has joined #openstack-meeting | 10:44 | |
*** thorst has quit IRC | 10:44 | |
*** shaohe_feng has quit IRC | 10:44 | |
*** shaohe_feng has joined #openstack-meeting | 10:45 | |
*** hoangcx has quit IRC | 10:45 | |
*** jlanoux has joined #openstack-meeting | 10:46 | |
*** ljxiash has joined #openstack-meeting | 10:46 | |
*** hoangcx has joined #openstack-meeting | 10:47 | |
*** jlanoux_ has quit IRC | 10:48 | |
*** amitgandhinz has quit IRC | 10:48 | |
*** amotoki_ has quit IRC | 10:52 | |
*** amotoki has joined #openstack-meeting | 10:52 | |
*** ljxiash has quit IRC | 10:53 | |
*** shaohe_feng has quit IRC | 10:54 | |
*** yassine has quit IRC | 10:55 | |
*** shaohe_feng has joined #openstack-meeting | 10:56 | |
*** sudipto has quit IRC | 10:56 | |
*** salv-orlando has quit IRC | 10:58 | |
*** nisha__ has joined #openstack-meeting | 10:58 | |
*** salv-orlando has joined #openstack-meeting | 10:58 | |
*** obondarev has quit IRC | 11:01 | |
*** nisha_ has quit IRC | 11:02 | |
*** zeih_ has joined #openstack-meeting | 11:02 | |
*** zeih has quit IRC | 11:02 | |
*** fzdarsky|afk is now known as fzdarsky | 11:03 | |
*** shaohe_feng has quit IRC | 11:05 | |
*** shaohe_feng has joined #openstack-meeting | 11:06 | |
*** permalac has quit IRC | 11:09 | |
*** yujunz has quit IRC | 11:11 | |
*** shaohe_feng has quit IRC | 11:15 | |
*** sheel has quit IRC | 11:15 | |
*** shaohe_feng has joined #openstack-meeting | 11:16 | |
*** rtheis has joined #openstack-meeting | 11:16 | |
*** alyson_ has joined #openstack-meeting | 11:17 | |
*** ljxiash has joined #openstack-meeting | 11:18 | |
*** ljxiash has quit IRC | 11:23 | |
*** tellesnobrega is now known as tellesnobrega_af | 11:23 | |
*** ociuhandu has quit IRC | 11:23 | |
*** ociuhandu has joined #openstack-meeting | 11:23 | |
*** ivc_ has quit IRC | 11:24 | |
*** egallen has joined #openstack-meeting | 11:25 | |
*** xenogear has quit IRC | 11:25 | |
*** shaohe_feng has quit IRC | 11:25 | |
*** shaohe_feng has joined #openstack-meeting | 11:26 | |
*** ociuhandu has quit IRC | 11:26 | |
*** ociuhandu has joined #openstack-meeting | 11:26 | |
*** salv-orl_ has joined #openstack-meeting | 11:28 | |
*** weshay has joined #openstack-meeting | 11:30 | |
*** toddjohn has joined #openstack-meeting | 11:31 | |
*** salv-orlando has quit IRC | 11:32 | |
*** zeih_ has quit IRC | 11:32 | |
*** rodrigods has quit IRC | 11:35 | |
*** rodrigods has joined #openstack-meeting | 11:35 | |
*** shaohe_feng has quit IRC | 11:35 | |
*** toddjohn has quit IRC | 11:36 | |
*** shaohe_feng has joined #openstack-meeting | 11:36 | |
*** thorst has joined #openstack-meeting | 11:41 | |
*** thorst_ has joined #openstack-meeting | 11:43 | |
*** sarob has joined #openstack-meeting | 11:44 | |
*** piet has joined #openstack-meeting | 11:44 | |
*** amitgandhinz has joined #openstack-meeting | 11:44 | |
*** Marcus5 has joined #openstack-meeting | 11:45 | |
Marcus5 | hey | 11:45 |
*** obondarev has joined #openstack-meeting | 11:45 | |
*** shaohe_feng has quit IRC | 11:46 | |
*** shaohe_feng has joined #openstack-meeting | 11:47 | |
*** thorst has quit IRC | 11:47 | |
*** amotoki has quit IRC | 11:48 | |
*** sarob has quit IRC | 11:48 | |
*** thorst_ is now known as thorst | 11:49 | |
*** amitgandhinz has quit IRC | 11:49 | |
*** tochi has quit IRC | 11:50 | |
*** azbiswas has joined #openstack-meeting | 11:51 | |
*** coolsvap has quit IRC | 11:51 | |
*** baoli has joined #openstack-meeting | 11:51 | |
*** baoli_ has joined #openstack-meeting | 11:52 | |
*** raildo-afk is now known as raildo | 11:54 | |
*** fzdarsky is now known as fzdarsky|afk | 11:55 | |
*** shaohe_feng has quit IRC | 11:56 | |
*** baoli has quit IRC | 11:56 | |
*** azbiswas has quit IRC | 11:56 | |
*** ivc_ has joined #openstack-meeting | 11:56 | |
*** aysyd has joined #openstack-meeting | 11:57 | |
*** shaohe_feng has joined #openstack-meeting | 11:57 | |
*** piet has quit IRC | 11:58 | |
*** dmacpher has joined #openstack-meeting | 11:58 | |
*** ljxiash has joined #openstack-meeting | 11:59 | |
*** fzdarsky|afk has quit IRC | 12:00 | |
*** ljxiash has quit IRC | 12:05 | |
*** zeih has joined #openstack-meeting | 12:06 | |
*** yamada-h has joined #openstack-meeting | 12:06 | |
*** shaohe_feng has quit IRC | 12:06 | |
*** shaohe_feng has joined #openstack-meeting | 12:07 | |
*** Marcus5 has quit IRC | 12:08 | |
*** yamada-h has quit IRC | 12:10 | |
*** epcim has joined #openstack-meeting | 12:11 | |
*** yamamoto_ has quit IRC | 12:11 | |
*** pradk has joined #openstack-meeting | 12:12 | |
*** ub has quit IRC | 12:12 | |
*** markvoelker has joined #openstack-meeting | 12:13 | |
*** matrohon has quit IRC | 12:15 | |
*** noslzzp_ has quit IRC | 12:16 | |
*** jckasper has quit IRC | 12:16 | |
*** shaohe_feng has quit IRC | 12:16 | |
*** noslzzp has joined #openstack-meeting | 12:17 | |
*** nisha__ is now known as nisha_ | 12:17 | |
*** shaohe_feng has joined #openstack-meeting | 12:17 | |
*** numans has quit IRC | 12:17 | |
*** adrianofr has joined #openstack-meeting | 12:19 | |
*** ljxiash has joined #openstack-meeting | 12:19 | |
*** ssalagame has joined #openstack-meeting | 12:19 | |
*** manikanta_tadi has quit IRC | 12:20 | |
*** zeih has quit IRC | 12:21 | |
*** ljxiash has quit IRC | 12:24 | |
*** matrohon has joined #openstack-meeting | 12:25 | |
*** toddjohn has joined #openstack-meeting | 12:26 | |
*** shaohe_feng has quit IRC | 12:27 | |
*** shaohe_feng has joined #openstack-meeting | 12:28 | |
*** kaisers1 has quit IRC | 12:29 | |
*** Hosam has quit IRC | 12:29 | |
*** fwdit has joined #openstack-meeting | 12:30 | |
*** Hosam has joined #openstack-meeting | 12:30 | |
*** lamt has joined #openstack-meeting | 12:30 | |
*** Niham has quit IRC | 12:31 | |
*** toddjohn has quit IRC | 12:31 | |
*** ub has joined #openstack-meeting | 12:31 | |
*** salv-orl_ has quit IRC | 12:33 | |
*** salv-orlando has joined #openstack-meeting | 12:34 | |
*** Hosam has quit IRC | 12:34 | |
*** zeih has joined #openstack-meeting | 12:36 | |
*** shaohe_feng has quit IRC | 12:37 | |
*** shaohe_feng has joined #openstack-meeting | 12:38 | |
*** dane_leblanc has joined #openstack-meeting | 12:38 | |
*** yassine has joined #openstack-meeting | 12:40 | |
*** sarob has joined #openstack-meeting | 12:42 | |
*** ivc_ has quit IRC | 12:44 | |
*** ivc_ has joined #openstack-meeting | 12:44 | |
*** amitgandhinz has joined #openstack-meeting | 12:45 | |
*** sarob has quit IRC | 12:47 | |
*** shaohe_feng has quit IRC | 12:47 | |
*** shaohe_feng has joined #openstack-meeting | 12:48 | |
*** mrmartin has quit IRC | 12:49 | |
*** piet has joined #openstack-meeting | 12:49 | |
*** jamesdenton has joined #openstack-meeting | 12:50 | |
*** amitgandhinz has quit IRC | 12:50 | |
*** piet has quit IRC | 12:51 | |
*** piet has joined #openstack-meeting | 12:53 | |
*** yamamoto has joined #openstack-meeting | 12:53 | |
*** zeih has quit IRC | 12:54 | |
*** rossella_s has quit IRC | 12:54 | |
*** klkumar has quit IRC | 12:55 | |
*** cbouch has joined #openstack-meeting | 12:55 | |
*** elynn has joined #openstack-meeting | 12:56 | |
*** nisha_ has quit IRC | 12:56 | |
*** haiwei_ has joined #openstack-meeting | 12:57 | |
*** lixinhui_ has joined #openstack-meeting | 12:57 | |
*** shaohe_feng has quit IRC | 12:57 | |
*** shaohe_feng has joined #openstack-meeting | 12:58 | |
*** zeih has joined #openstack-meeting | 12:59 | |
*** yanyanhu has joined #openstack-meeting | 13:00 | |
*** salv-orlando has quit IRC | 13:00 | |
Qiming | #startmeeting senlin | 13:00 |
openstack | Qiming: Error: Can't start another meeting, one is in progress. Use #endmeeting first. | 13:00 |
*** salv-orlando has joined #openstack-meeting | 13:00 | |
*** dneary has joined #openstack-meeting | 13:00 | |
Qiming | em, networking_midonet is not ended ... | 13:01 |
Qiming | #endmeeting | 13:01 |
*** zeih has quit IRC | 13:01 | |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 13:01 | |
elynn | is it work? | 13:01 |
openstack | Meeting ended Tue Jun 14 13:01:32 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:01 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/networking_midonet/2016/networking_midonet.2016-06-14-07.36.html | 13:01 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/networking_midonet/2016/networking_midonet.2016-06-14-07.36.txt | 13:01 |
openstack | Log: http://eavesdrop.openstack.org/meetings/networking_midonet/2016/networking_midonet.2016-06-14-07.36.log.html | 13:01 |
Qiming | #startmeeting senlin | 13:02 |
openstack | Meeting started Tue Jun 14 13:02:03 2016 UTC and is due to finish in 60 minutes. The chair is Qiming. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:02 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:02 |
*** openstack changes topic to " (Meeting topic: senlin)" | 13:02 | |
openstack | The meeting name has been set to 'senlin' | 13:02 |
yanyanhu | hi | 13:02 |
Qiming | seems working | 13:02 |
Qiming | cool | 13:02 |
*** cschulz_ has joined #openstack-meeting | 13:02 | |
haiwei_ | hi | 13:02 |
Qiming | morning/evening | 13:02 |
elynn | good | 13:02 |
cschulz_ | Hi | 13:02 |
lixinhui_ | hi | 13:02 |
Qiming | pls feel free to add items to the agenda if you have topics | 13:02 |
Qiming | #link https://wiki.openstack.org/wiki/Meetings/SenlinAgenda#Weekly_Senlin_.28Clustering.29_meeting | 13:03 |
Qiming | hi, everyone | 13:03 |
Qiming | let's start with the etherpad | 13:03 |
Qiming | #link https://etherpad.openstack.org/p/senlin-newton-workitems | 13:03 |
*** xyang1 has joined #openstack-meeting | 13:04 | |
Qiming | tempest testing side, we have made some really good progress on api tests, especially those negative ones | 13:04 |
elynn | yes | 13:04 |
yanyanhu | yes, almost done I think. just need negative test case for cluster actions | 13:05 |
elynn | How many negative tests left? | 13:05 |
yanyanhu | about 10 I think | 13:05 |
Qiming | great! | 13:05 |
yanyanhu | one for each action | 13:05 |
elynn | Great! | 13:05 |
Qiming | then we may need to migrate functional tests to use tempest? | 13:06 |
*** amakarov_away is now known as amakarov | 13:06 | |
yanyanhu | Qiming, yes, I think so | 13:06 |
Qiming | or, do we want to do the migration at all? | 13:06 |
yanyanhu | maybe we can put them into scenario dir? | 13:06 |
Qiming | :) | 13:06 |
yanyanhu | Qiming, if possible, we should :) | 13:07 |
Qiming | okay | 13:07 |
*** yamamoto has quit IRC | 13:07 | |
Qiming | then we do it | 13:07 |
*** yamamoto has joined #openstack-meeting | 13:07 | |
yanyanhu | then we don't need to maintain functional gate job | 13:07 |
elynn | Or we can create a functional dir? | 13:07 |
yanyanhu | all these tests will be done using tempest | 13:07 |
yanyanhu | although we may need tempest scenario test job? | 13:07 |
*** designbybeck has joined #openstack-meeting | 13:08 | |
*** shaohe_feng has quit IRC | 13:08 | |
yanyanhu | yes | 13:08 |
*** rossella_s has joined #openstack-meeting | 13:08 | |
yanyanhu | functional is also ok I think | 13:08 |
*** shaohe_feng has joined #openstack-meeting | 13:08 | |
Qiming | functional tests will still use fake drivers | 13:09 |
yanyanhu | right | 13:09 |
Qiming | how about scenario tests? | 13:09 |
yanyanhu | that is the same as API test | 13:09 |
yanyanhu | actually in my mind, our current functional test is more like 'scenario' test :) | 13:09 |
yanyanhu | just the backend driver is fake | 13:10 |
elynn | scenario will use real driver, right? | 13:10 |
yanyanhu | um, that can be integration :) | 13:10 |
yanyanhu | integration test | 13:10 |
Qiming | right | 13:10 |
yanyanhu | seems there is no strict definition for these test types... | 13:11 |
elynn | oh, I thought they are the same... | 13:11 |
yanyanhu | elynn, that's confusing :) | 13:11 |
Qiming | api test focuses on the api surface | 13:11 |
Qiming | functional tests is more about exercising the senlin-engine | 13:11 |
*** yamamoto has quit IRC | 13:12 | |
Qiming | then I'm doubting if we should treat scenario test and integration test as the same thing | 13:12 |
yanyanhu | I'm ok with both functional and scenario. We just need to differentiate those two cases using real driver or not. | 13:13 |
elynn | Speaking of that, seems defcore tends to use the tests in tempest tree. | 13:14 |
*** fzdarsky has joined #openstack-meeting | 13:14 | |
elynn | Do we need to put some tests there? | 13:14 |
Qiming | if needed, we can copy the code there | 13:14 |
yanyanhu | I think we don't need to test complicated engine logic in integration test | 13:14 |
Qiming | defcore only cares about api surface, right? | 13:14 |
*** klkumar has joined #openstack-meeting | 13:14 | |
yanyanhu | just need to ensure senlin works well with other backend services I guess | 13:15 |
*** zhurong has joined #openstack-meeting | 13:15 | |
elynn | Qiming: yes | 13:15 |
Qiming | yanyanhu, agree, but we need to test some tricky, corner cases as well | 13:15 |
yanyanhu | yes, like lb policy | 13:15 |
elynn | Agree | 13:15 |
elynn | like lb policy and health management | 13:15 |
Qiming | integration test is more of exercises for profiles and policies | 13:15 |
yanyanhu | right | 13:15 |
yanyanhu | yep | 13:16 |
Qiming | so we can skip scenario tests? | 13:16 |
yanyanhu | ok | 13:16 |
*** mrmartin has joined #openstack-meeting | 13:16 | |
*** asselin_ has joined #openstack-meeting | 13:16 | |
Qiming | have functional focusing on engine testing, integration tests focusing on profiles/policies | 13:16 |
yanyanhu | move existing functional tests to tempest dir | 13:17 |
Qiming | the former still use the fake driver, the latter use real drivers | 13:17 |
elynn | Anyway, these tests are only tools to help us to make sure our services works as expected. Naming is not import :) | 13:17 |
yanyanhu | s/move/re-implement | 13:17 |
elynn | We can add any tests we want to tests. | 13:17 |
yanyanhu | elynn, +1 | 13:17 |
*** jckasper has joined #openstack-meeting | 13:17 | |
Qiming | elynn, yep, but we have to speak the same language | 13:17 |
Qiming | we agree we won't talk about scenario tests | 13:18 |
Qiming | true? | 13:18 |
*** shaohe_feng has quit IRC | 13:18 | |
*** zhurong has quit IRC | 13:18 | |
*** vuntz has quit IRC | 13:18 | |
elynn | agree | 13:18 |
yanyanhu | ok | 13:19 |
*** shaohe_feng has joined #openstack-meeting | 13:19 | |
Qiming | okay, let's keep things simple | 13:19 |
Qiming | stress testing | 13:19 |
*** zhurong has joined #openstack-meeting | 13:19 | |
Qiming | noticed your patch about rally testing, yanyan | 13:19 |
Qiming | quite some nits found when reviewing it | 13:19 |
*** kylek3h has joined #openstack-meeting | 13:19 | |
Qiming | pls check | 13:20 |
yanyanhu | yes, have read your comments | 13:20 |
yanyanhu | will fix it tomorrow | 13:20 |
Qiming | also, we have got some comments from rally team about that plugin testing | 13:20 |
yanyanhu | Qiming, yes, definitely | 13:20 |
Qiming | pls help keep the balls rolling | 13:21 |
*** Niham has joined #openstack-meeting | 13:21 | |
yanyanhu | I noticed roman just left some comments on my patch for adding cluster plugin | 13:21 |
yanyanhu | will reply and update patch | 13:21 |
Qiming | we may want to check if cmcc guys want to help on rally test cases | 13:21 |
*** fzdarsky has quit IRC | 13:21 | |
yanyanhu | finally, all those plugins will stay in rally repo and we can remove our local copy | 13:21 |
*** fzdarsky has joined #openstack-meeting | 13:21 | |
yanyanhu | Qiming, yes, just didn't get msg from eldon zhao | 13:22 |
Qiming | you mean the rally_jobs subdir? | 13:22 |
yanyanhu | will contact with him to see whether there is anything we can help them | 13:22 |
yanyanhu | Qiming, yes, we just need to keep job description files | 13:22 |
*** piet has quit IRC | 13:22 | |
yanyanhu | no need to keep local plugins if they have been merged to rally | 13:22 |
Qiming | okay | 13:23 |
Qiming | moving on | 13:23 |
Qiming | last week we talked about the health threshold problem | 13:23 |
Qiming | have you guys got some new ideas? thoughts? | 13:23 |
*** fwdit has quit IRC | 13:24 | |
*** amotoki has joined #openstack-meeting | 13:24 | |
yanyanhu | hmm, still not very sure about it | 13:24 |
Qiming | ... | 13:25 |
yanyanhu | in my mind, there could be a property like percentage to describe the threshold of health status | 13:25 |
yanyanhu | which is based on desired_capacity | 13:25 |
yanyanhu | :) | 13:25 |
*** vuntz has joined #openstack-meeting | 13:26 | |
Qiming | yes, I know what you mean | 13:26 |
yanyanhu | which means if the current size of cluster is less than %* of user desired size, the cluster will be marked as unhealthy | 13:26 |
yanyanhu | yes | 13:26 |
Qiming | then we have four numbers, min_size, health_threshold, desired_capacity, max_size | 13:26 |
yanyanhu | yes, that's my original idea | 13:26 |
Qiming | how would you map the different node count to cluster status? | 13:27 |
*** ivc_ has quit IRC | 13:27 | |
yanyanhu | node count? you mean count of node in health status? | 13:28 |
*** ivc_ has joined #openstack-meeting | 13:28 | |
Qiming | each time the cluster is resized, a user is supposed to adjust the health_threshold? | 13:28 |
*** shaohe_feng has quit IRC | 13:28 | |
yanyanhu | no, I think user should expect a stable/fix health_threshold no matter how large the cluster is | 13:28 |
Qiming | suppose we have the 4 numbers as these: 1, 3, 5, 7 | 13:29 |
Qiming | the cluster now has 2 nodes active | 13:29 |
Qiming | what the cluster status would be? | 13:29 |
yanyanhu | that means they always want at least 80% of nodes in their cluster is health. e.g. | 13:29 |
yanyanhu | even when they have a very large cluster | 13:29 |
*** ericksonsantos has joined #openstack-meeting | 13:29 | |
Qiming | then the health_threshold can only be a percentage? | 13:29 |
yanyanhu | 3 is health threshold? | 13:30 |
yanyanhu | yes | 13:30 |
yanyanhu | 60% in this case | 13:30 |
Qiming | the cluster has 2 nodes active, what should the cluster's status be? | 13:30 |
yanyanhu | but this is just my thought. I think we really need to find user's consideration about this issue | 13:30 |
yanyanhu | if the threshold is 60%, desired_capacity is 5, then I think the status should be warning/unhealthy | 13:31 |
*** shaohe_feng has joined #openstack-meeting | 13:31 | |
yanyanhu | if there are 3 healthy nodes, we can mark cluster as healthy | 13:31 |
Qiming | the cluster's desired_capacity is 5 | 13:32 |
Qiming | 2 nodes is less than that | 13:32 |
Qiming | it is no good | 13:32 |
yanyanhu | so in my idea, desired_capacity actually become the 'IDEAL' size | 13:32 |
Qiming | then what is 'desired_capacity' used for? | 13:32 |
yanyanhu | actually it's not 'desired_capacity' | 13:32 |
*** rfolco has joined #openstack-meeting | 13:33 | |
*** woodster_ has joined #openstack-meeting | 13:33 | |
yanyanhu | you can't always get what you want, haha | 13:33 |
Qiming | health_threshold becomes the new 'desired'? | 13:33 |
yanyanhu | that why I have that idea :) | 13:33 |
yanyanhu | Qiming, seems so | 13:33 |
yanyanhu | so I said I'm not so sure about it after all these thinking | 13:33 |
Qiming | then we can completely abandon 'desired_capacity' | 13:33 |
*** mriedem_away is now known as mriedem | 13:33 | |
yanyanhu | that depends on how user understand those conceptions, like desired_capacity | 13:34 |
*** banix has joined #openstack-meeting | 13:34 | |
yanyanhu | Qiming, maybe, or we use it as real 'desired' capacity | 13:34 |
Qiming | I was having problems explaining these four numbers to a user | 13:34 |
Qiming | when you do recovery | 13:35 |
*** erlon has joined #openstack-meeting | 13:35 | |
Qiming | you recover to the health_threshold (3) nodes or desired_capacity (5) nodes? | 13:35 |
Qiming | if the cluster has 4 nodes active now | 13:35 |
Qiming | do you need to recover it? | 13:35 |
Qiming | it is not ideal (one less than the desired) | 13:35 |
*** lblanchard has joined #openstack-meeting | 13:35 | |
yanyanhu | for recovery, I think we should try to recover to desired_capacity | 13:36 |
Qiming | recover to health_theshold would already make the cluster healthy | 13:36 |
yanyanhu | hmm, I think your right, we should only maintain three conceptions here | 13:36 |
Qiming | I've been struggling on this for a long time | 13:36 |
*** obondarev has quit IRC | 13:37 | |
Qiming | was trying to get some more brains on this | 13:37 |
yanyanhu | then we need to explain the difference between 'ideal' and 'what your want' | 13:37 |
yanyanhu | that's too confusing | 13:38 |
*** ivc_ has quit IRC | 13:38 | |
Qiming | yes, that was my thought a long time ago | 13:38 |
Qiming | what you want == ideal | 13:38 |
*** edtubill has joined #openstack-meeting | 13:38 | |
Qiming | because the reality always changes | 13:38 |
yanyanhu | so if we only have desired_capacity, that is the threshold of healthy and also 'what user wants' | 13:38 |
yanyanhu | we always try to make the cluster size match it | 13:38 |
*** shaohe_feng has quit IRC | 13:38 | |
*** piet has joined #openstack-meeting | 13:39 | |
*** banix has quit IRC | 13:39 | |
Qiming | that is the *desired* capacity | 13:39 |
*** shaohe_feng has joined #openstack-meeting | 13:39 | |
yanyanhu | yes | 13:39 |
Qiming | it could be an over simplification | 13:39 |
yanyanhu | desired means what user wants | 13:39 |
*** banix has joined #openstack-meeting | 13:39 | |
yanyanhu | and we try to meet their requirement when creating/recovering cluster | 13:40 |
Qiming | yep, what else could it be ... | 13:40 |
*** jjmorman has joined #openstack-meeting | 13:40 | |
*** ssalagame has quit IRC | 13:40 | |
yanyanhu | if we fail to achieve that goal, the cluster is unhealthy since it doesn't meet user's expectation | 13:40 |
*** cbouch has quit IRC | 13:40 | |
Qiming | yes, the engine will always try it best to "kind of converge" the cluster to that size | 13:40 |
yanyanhu | ok, I'm much clearer now | 13:41 |
yanyanhu | about this | 13:41 |
*** ljxiash has joined #openstack-meeting | 13:41 | |
*** edtubill has quit IRC | 13:41 | |
Qiming | okay, if we all agree on this "over" simplification | 13:42 |
Qiming | we can start closing the loop | 13:42 |
yanyanhu | yes | 13:42 |
elynn | sounds good! | 13:42 |
Qiming | we can hear node (VM) failure events now | 13:42 |
Qiming | the basic health management will do some recover with and without guidance from a policy | 13:43 |
*** mtanino has joined #openstack-meeting | 13:43 | |
Qiming | kind of a convergence to the desired_capacity | 13:43 |
*** longxiongqiu has quit IRC | 13:43 | |
yanyanhu | yes, so policy just make it "automatic" and "smarter" | 13:44 |
Qiming | in future, when needed, we can add an option: the engine can optionally converge the cluster size to a number you want, not necessarily the 'desired_capacity' | 13:44 |
Qiming | that is sort of equivalent to health_threshold | 13:44 |
*** ivc_ has joined #openstack-meeting | 13:44 | |
*** R_lixh has joined #openstack-meeting | 13:44 | |
Qiming | maybe a policy option or something | 13:44 |
*** lixinhui_ has quit IRC | 13:45 | |
*** eharney has joined #openstack-meeting | 13:45 | |
yanyanhu | yes, define that property in policy makes more sense IMHO | 13:45 |
Qiming | moving on | 13:45 |
Qiming | no update on documentation, though I did fixed some links on senlin wiki | 13:45 |
Qiming | reinstalled ceilometer along with aodh, will try workout some tutorial docs on manual/auto scaling | 13:46 |
yanyanhu | nice | 13:46 |
Qiming | haiwei_, progress on container support? | 13:46 |
*** longxiongqiu has joined #openstack-meeting | 13:46 | |
*** amitgandhinz has joined #openstack-meeting | 13:46 | |
haiwei_ | no progress this week | 13:46 |
*** fifieldt has joined #openstack-meeting | 13:47 | |
haiwei_ | waiting for your review on the initial patch | 13:47 |
Qiming | okay, let us know if you need someone for a discussion | 13:47 |
haiwei_ | ok | 13:47 |
Qiming | I haven't reviewed that? ... | 13:47 |
Qiming | my fault | 13:47 |
Qiming | sorry | 13:47 |
haiwei_ | its ok | 13:48 |
Qiming | no progress on event/notification yet | 13:48 |
Qiming | though I have a half-baked patch on generalizing the backend | 13:48 |
Qiming | oops, we only have 12 mins left | 13:48 |
Qiming | #topic cluster-collect call | 13:49 |
*** openstack changes topic to "cluster-collect call (Meeting topic: senlin)" | 13:49 | |
*** shaohe_feng has quit IRC | 13:49 | |
Qiming | let me walk you quickly thru the cluster-collect call I'm adding | 13:49 |
*** shaohe_feng has joined #openstack-meeting | 13:49 | |
Qiming | the basic requirement is that when you created a cluster of nova servers, for example | 13:49 |
Qiming | you want to get a list of the IP addresses of all nodes | 13:50 |
Qiming | this is a command being added, which necessitates a new engine version and a new api version | 13:50 |
*** longxiongqiu has quit IRC | 13:50 | |
Qiming | you will be able to do things like this: | 13:50 |
Qiming | senlin cluster-collect -p details.addresses.private[0] <cluster_name> | 13:50 |
haiwei_ | this function is useful in container cluster, I think | 13:51 |
*** lblanchard has quit IRC | 13:51 | |
Qiming | the "details.addresses.private[0]" is modeled as a json path | 13:51 |
*** amitgandhinz has quit IRC | 13:51 | |
Qiming | I have some local patches to be commited to senlin/sdk/senlinclient | 13:51 |
Qiming | still trying to iron out some issues | 13:52 |
*** mrmartin has quit IRC | 13:52 | |
Qiming | but basically, it works pretty good | 13:52 |
Qiming | in the simple case you can do: senlin cluster-collect -p name <cluster_name> | 13:52 |
*** liamji has joined #openstack-meeting | 13:53 | |
Qiming | that will give you a list of names on command line | 13:53 |
Qiming | you can also do: senlin cluster-collect -p details.addresses.private[0] -L <cluster_name> | 13:53 |
Qiming | the "-L" switch will print the output into a two-columned table | 13:53 |
Qiming | the first column is the node id, the second is the attribute value | 13:54 |
*** mrmartin has joined #openstack-meeting | 13:54 | |
yanyanhu | nice. Have you decided which type of data collect operation will return? list or dict | 13:54 |
Qiming | engine patch and rpc patches are ready for review, I'm working on the api layer | 13:54 |
*** coolsvap has joined #openstack-meeting | 13:54 | |
Qiming | if you review the code | 13:54 |
*** nisha_ has joined #openstack-meeting | 13:55 | |
*** rbak has joined #openstack-meeting | 13:55 | |
Qiming | you will see it is returning something like this: {'cluster_attributes': [{'id': 'NODE1', 'value': 'V1'}, {'id': 'NODE2', 'value': 'V2'}]} | 13:55 |
*** cdelatte has joined #openstack-meeting | 13:56 | |
yanyanhu | I see | 13:56 |
Qiming | that's a quick update on cluster-collect call | 13:56 |
*** lblanchard has joined #openstack-meeting | 13:56 | |
*** irenab has quit IRC | 13:56 | |
Qiming | #topic open discussions | 13:56 |
*** openstack changes topic to "open discussions (Meeting topic: senlin)" | 13:56 | |
*** yamamoto has joined #openstack-meeting | 13:56 | |
Qiming | open for questions/comments/suggestions | 13:56 |
yanyanhu | nothing from my side | 13:57 |
Qiming | btw, I have got a company internal call for presentation for Barcelona summit | 13:57 |
Qiming | time flies | 13:57 |
yanyanhu | yes... | 13:57 |
yanyanhu | the end of oct. | 13:58 |
elynn | yes... | 13:58 |
yanyanhu | will think about it | 13:58 |
*** rderose has joined #openstack-meeting | 13:58 | |
elynn | lao si ji, dai dai wo. | 13:58 |
yanyanhu | :P | 13:59 |
yanyanhu | I can read it | 13:59 |
Qiming | :) | 13:59 |
yanyanhu | maybe we can have a brainstorming for it | 13:59 |
*** shaohe_feng has quit IRC | 13:59 | |
Qiming | time's up | 13:59 |
yanyanhu | in coffee time | 13:59 |
elynn | yes | 13:59 |
Qiming | thanks for joining guys | 13:59 |
Qiming | have a good night/day | 13:59 |
*** yuval has quit IRC | 13:59 | |
yanyanhu | thanks | 13:59 |
Qiming | #endmeeting | 14:00 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 14:00 | |
openstack | Meeting ended Tue Jun 14 14:00:00 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:00 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-06-14-13.02.html | 14:00 |
elynn | good night | 14:00 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-06-14-13.02.txt | 14:00 |
openstack | Log: http://eavesdrop.openstack.org/meetings/senlin/2016/senlin.2016-06-14-13.02.log.html | 14:00 |
*** shaohe_feng has joined #openstack-meeting | 14:00 | |
*** elynn has quit IRC | 14:00 | |
*** Niham has quit IRC | 14:01 | |
*** Julien-zte has joined #openstack-meeting | 14:02 | |
*** Julien-z_ has joined #openstack-meeting | 14:03 | |
*** zz_dimtruck is now known as dimtruck | 14:03 | |
*** haiwei_ has quit IRC | 14:04 | |
*** yanyanhu has quit IRC | 14:04 | |
*** mrmartin has quit IRC | 14:06 | |
*** Julien-zte has quit IRC | 14:07 | |
*** sudipto has joined #openstack-meeting | 14:07 | |
*** longxiongqiu has joined #openstack-meeting | 14:08 | |
*** galstrom_zzz is now known as galstrom | 14:08 | |
*** shaohe_feng has quit IRC | 14:09 | |
*** edtubill has joined #openstack-meeting | 14:10 | |
*** amitgandhinz has joined #openstack-meeting | 14:11 | |
*** amitgandhinz has quit IRC | 14:11 | |
*** cody-somerville has joined #openstack-meeting | 14:11 | |
*** cody-somerville has quit IRC | 14:11 | |
*** cody-somerville has joined #openstack-meeting | 14:11 | |
*** amitgandhinz has joined #openstack-meeting | 14:12 | |
*** shaohe_feng has joined #openstack-meeting | 14:12 | |
*** jmckind has joined #openstack-meeting | 14:13 | |
*** links has quit IRC | 14:14 | |
*** jckasper has quit IRC | 14:14 | |
*** jckasper has joined #openstack-meeting | 14:14 | |
*** huangtianhua has quit IRC | 14:15 | |
*** cody-somerville has quit IRC | 14:16 | |
*** jckasper_ has joined #openstack-meeting | 14:16 | |
*** tiantian has joined #openstack-meeting | 14:16 | |
*** henrynash_ has quit IRC | 14:16 | |
*** MaxPC has joined #openstack-meeting | 14:16 | |
*** Reedip_ has joined #openstack-meeting | 14:16 | |
*** jckasper has quit IRC | 14:19 | |
*** Reedip_ has left #openstack-meeting | 14:19 | |
*** shaohe_feng has quit IRC | 14:20 | |
*** jckasper_ has quit IRC | 14:20 | |
*** bill_az has joined #openstack-meeting | 14:22 | |
*** spotz_zzz is now known as spotz | 14:23 | |
*** akuznetsov has joined #openstack-meeting | 14:24 | |
*** shaohe_feng has joined #openstack-meeting | 14:24 | |
*** anilvenkata has quit IRC | 14:26 | |
*** tellesnobrega_af is now known as tellesnobrega | 14:26 | |
*** Nag_ has joined #openstack-meeting | 14:28 | |
*** dmorita has joined #openstack-meeting | 14:29 | |
*** nmagnezi has quit IRC | 14:29 | |
*** longxiongqiu has quit IRC | 14:30 | |
*** shaohe_feng has quit IRC | 14:30 | |
*** longxiongqiu has joined #openstack-meeting | 14:30 | |
*** shaohe_feng has joined #openstack-meeting | 14:30 | |
*** reduxio has joined #openstack-meeting | 14:30 | |
*** adisky has quit IRC | 14:30 | |
*** mriedem1 has joined #openstack-meeting | 14:31 | |
*** _nadya_ has quit IRC | 14:32 | |
reduxio | Hello. Can anyone point me to where i need to go to register as a third party driver developer? | 14:32 |
*** _nadya_ has joined #openstack-meeting | 14:33 | |
*** mriedem has quit IRC | 14:33 | |
*** kaisers has joined #openstack-meeting | 14:33 | |
*** dmorita has quit IRC | 14:33 | |
*** _nadya_ has quit IRC | 14:35 | |
*** jamesmcarthur has joined #openstack-meeting | 14:35 | |
*** Hosam has joined #openstack-meeting | 14:35 | |
*** ayoung has joined #openstack-meeting | 14:36 | |
*** _nadya_ has joined #openstack-meeting | 14:37 | |
*** rfolco has quit IRC | 14:37 | |
*** jrist has quit IRC | 14:38 | |
*** shaohe_feng has quit IRC | 14:40 | |
*** iyamahat has joined #openstack-meeting | 14:40 | |
*** shaohe_feng has joined #openstack-meeting | 14:41 | |
*** _nadya_ has quit IRC | 14:41 | |
*** nmagnezi has joined #openstack-meeting | 14:42 | |
reduxio | Hello. I'm having trouble logging in to openstack wiki. getting server error (http 500). can anyone help with that? | 14:43 |
*** ssalagame has joined #openstack-meeting | 14:44 | |
*** ajmiller has quit IRC | 14:45 | |
dasm | reduxio: as far as i remember (but may be wrong) creating new accounts on wiki was disabled, because of spammers. | 14:45 |
*** ajmiller has joined #openstack-meeting | 14:45 | |
*** eharney has quit IRC | 14:45 | |
*** rfolco has joined #openstack-meeting | 14:46 | |
*** stajkowski has joined #openstack-meeting | 14:46 | |
reduxio | Oh? So i do i add my company as a third party running CI? the documentation link pointed me to the wiki (at least that is what i understood..) | 14:47 |
*** timcline has joined #openstack-meeting | 14:47 | |
*** julim has quit IRC | 14:47 | |
clarkb | reduxio: if you wander over to #openstack-infra you can get a wiki admin to temporarily allow user creation then create your user | 14:47 |
dasm | clarkb: yeah. i just noticed, where on openstack-meeting not *-infra. | 14:48 |
*** rbartal has quit IRC | 14:48 | |
dasm | reduxio: join #openstack-infra and talk to admins. | 14:48 |
*** timcline has quit IRC | 14:48 | |
reduxio | dasm: thanks! | 14:48 |
dasm | *we're | 14:48 |
*** chenying has joined #openstack-meeting | 14:48 | |
*** timcline has joined #openstack-meeting | 14:49 | |
dasm | reduxio: np. it's clarkb who suggested this :) | 14:49 |
*** chenzeng has joined #openstack-meeting | 14:49 | |
*** xiangxinyong456 has joined #openstack-meeting | 14:49 | |
*** jrist has joined #openstack-meeting | 14:50 | |
*** saggi has joined #openstack-meeting | 14:50 | |
*** shaohe_feng has quit IRC | 14:50 | |
*** shaohe_feng has joined #openstack-meeting | 14:51 | |
*** akuznetsov has quit IRC | 14:51 | |
*** cschulz_ has quit IRC | 14:51 | |
*** zhurong has quit IRC | 14:52 | |
*** klkumar has quit IRC | 14:52 | |
*** chenzeng has quit IRC | 14:52 | |
*** fnaval has quit IRC | 14:53 | |
*** singhj has joined #openstack-meeting | 14:53 | |
*** rrecio has joined #openstack-meeting | 14:54 | |
*** klkumar has joined #openstack-meeting | 14:54 | |
*** rrecio_ has joined #openstack-meeting | 14:54 | |
*** bill_az has quit IRC | 14:54 | |
*** amotoki has quit IRC | 14:55 | |
*** eharney has joined #openstack-meeting | 14:56 | |
*** zhonghua has joined #openstack-meeting | 14:57 | |
*** rrecio has quit IRC | 14:58 | |
*** mickeys has joined #openstack-meeting | 14:58 | |
*** sacharya has joined #openstack-meeting | 14:58 | |
*** yuval has joined #openstack-meeting | 14:59 | |
saggi | #startmeeting smaug | 15:00 |
openstack | Meeting started Tue Jun 14 15:00:01 2016 UTC and is due to finish in 60 minutes. The chair is saggi. 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: smaug)" | 15:00 | |
openstack | The meeting name has been set to 'smaug' | 15:00 |
saggi | Hi everybody | 15:00 |
yuval | hey | 15:00 |
zhonghua | hi | 15:00 |
xiangxinyong456 | hi | 15:00 |
chenying | hi:-) | 15:00 |
saggi | Is everyone aptly excited about tonight? | 15:00 |
zhonghua | yeah, | 15:00 |
xiangxinyong456 | yeah | 15:00 |
xiangxinyong456 | we are all here. | 15:00 |
saggi | OK | 15:00 |
chenying | yeah | 15:00 |
*** shaohe_feng has quit IRC | 15:01 | |
*** sacharya_ has joined #openstack-meeting | 15:01 | |
saggi | is yinwei coming? | 15:01 |
*** chenzeng has joined #openstack-meeting | 15:01 | |
zhonghua | xiangxinyong: :) | 15:01 |
*** jamesmcarthur has quit IRC | 15:01 | |
*** shaohe_feng has joined #openstack-meeting | 15:01 | |
saggi | #topic testing | 15:02 |
*** openstack changes topic to "testing (Meeting topic: smaug)" | 15:02 | |
chenzeng | hello,guys | 15:02 |
saggi | How close are we for all the tests to run on the CI? | 15:02 |
yuval | this patch: https://review.openstack.org/328927 | 15:02 |
yuval | should fix fullstack as part of the gate | 15:02 |
yuval | we have 2 patches by zhangshuai to test protect and restore | 15:03 |
yuval | https://review.openstack.org/327041 | 15:03 |
chenying | need fix swift client config error | 15:03 |
yuval | https://review.openstack.org/326946 | 15:03 |
*** jamesmcarthur has joined #openstack-meeting | 15:03 | |
yuval | chenying: yes, see my comment in my patch | 15:03 |
chenying | yuval Does your patch work? | 15:04 |
*** sacharya has quit IRC | 15:04 | |
yuval | chenying: yes. we can either merge it, or port the configuration settings to your patch | 15:04 |
chenying | I think we only merge your patch. | 15:05 |
*** jckasper has joined #openstack-meeting | 15:05 | |
yuval | great, then please review it: https://review.openstack.org/328927 | 15:05 |
chenying | I abondan my patch | 15:05 |
*** garthb has joined #openstack-meeting | 15:05 | |
*** yamahata has joined #openstack-meeting | 15:05 | |
chenying | ok I will reivew it later. | 15:06 |
saggi | anything else wrt testing? | 15:06 |
*** fnaval has joined #openstack-meeting | 15:06 | |
xiangxinyong456 | ? | 15:06 |
yuval | nope imo | 15:07 |
*** emagana has joined #openstack-meeting | 15:07 | |
saggi | OK | 15:07 |
saggi | #topic documentation | 15:07 |
*** openstack changes topic to "documentation (Meeting topic: smaug)" | 15:07 | |
saggi | I still haven't put the generated api doc up. Slipped my mind. | 15:07 |
chenying | a patch about doc have been merged | 15:07 |
chenying | about user example doc | 15:08 |
yuval | we are still missing a guide about writing plugins (protectable, protection, bank) | 15:08 |
*** fifieldt has quit IRC | 15:08 | |
saggi | We can only really do it once the API is solid and supported. We don't want to do that until version 1. | 15:09 |
chenying | yes | 15:09 |
*** emagana has quit IRC | 15:09 | |
saggi | Anything else? | 15:10 |
*** jckasper has quit IRC | 15:10 | |
zhonghua | yuval:where the guide doc should be located? | 15:10 |
yuval | doc/source/ | 15:10 |
zhonghua | yuval:readme? | 15:10 |
saggi | There should be a way to generate the wiki from the source tree. But IIRC gampel said you need to be a very special kind of project for that to be approved for you. | 15:11 |
yuval | we should drop it in doc/source and link to it from index.rst | 15:11 |
*** shaohe_feng has quit IRC | 15:11 | |
*** pradk has quit IRC | 15:11 | |
saggi | But I might be misremembering | 15:11 |
*** rcernin has quit IRC | 15:11 | |
saggi | #topic TC meeting prep | 15:11 |
*** openstack changes topic to "TC meeting prep (Meeting topic: smaug)" | 15:11 | |
saggi | Who is going to attend (apart from me)? | 15:11 |
*** shaohe_feng has joined #openstack-meeting | 15:11 | |
*** karthikp_ has joined #openstack-meeting | 15:12 | |
*** enriquetaso has joined #openstack-meeting | 15:12 | |
zhonghua | i hope i will | 15:12 |
yuval | me | 15:12 |
chenzeng | I will | 15:12 |
chenying | I will | 15:12 |
zhonghua | it is so late for me | 15:12 |
xiangxinyong456 | we all join the tc meeting | 15:12 |
saggi | There no real need. From what I hear we can't really influence things either way. | 15:13 |
saggi | So don't worry if it's to late for you. | 15:13 |
zhonghua | saggi: exciting moment | 15:13 |
xiangxinyong456 | we want to see the great moment | 15:13 |
*** obondarev has joined #openstack-meeting | 15:13 | |
*** asingh has joined #openstack-meeting | 15:14 | |
*** julim has joined #openstack-meeting | 15:14 | |
saggi | OK, anyone spoke with people from the TC and has any idea where the winds are blowing? | 15:14 |
*** pece has quit IRC | 15:15 | |
yuval | flavio popped into our channel, asked where glance_store could fit | 15:15 |
zhonghua | i want to know too | 15:15 |
chenzeng | blow the good direct | 15:15 |
zhonghua | saggi:any update about that? | 15:16 |
xiangxinyong456 | yuval: you mean where did glance data store? | 15:16 |
*** jckasper has joined #openstack-meeting | 15:17 | |
yuval | https://launchpad.net/glance-store | 15:17 |
yuval | https://github.com/openstack/glance_store | 15:17 |
*** jlanoux has quit IRC | 15:18 | |
saggi | glance_store seems to be an API for image repositories. | 15:18 |
chenying | need some time to research the project. | 15:19 |
saggi | true | 15:19 |
chenzeng | yuval:do you mean we can use the glance-store to protect image | 15:19 |
zhonghua | is there anyone know that project well? | 15:19 |
*** rmizuno_ has joined #openstack-meeting | 15:20 | |
yuval | chenzeng: afaik, it is used mostly by glance, but fit for other uses as well | 15:20 |
saggi | the documentation are very sparse | 15:20 |
*** shaohe_feng has quit IRC | 15:21 | |
saggi | #topic Open Discussion | 15:21 |
*** openstack changes topic to "Open Discussion (Meeting topic: smaug)" | 15:21 | |
saggi | Anything else? | 15:21 |
xiangxinyong456 | do we need to answer the favio? | 15:22 |
*** rderose has quit IRC | 15:22 | |
saggi | yuval: ? | 15:22 |
xiangxinyong456 | immediattly? | 15:22 |
*** jaugustine has joined #openstack-meeting | 15:22 | |
*** dmorita has joined #openstack-meeting | 15:22 | |
*** jaugustine has left #openstack-meeting | 15:22 | |
yuval | I already answered him, that glance_store might fit as a bank plugin, and could be used by protection plugins to store data | 15:22 |
saggi | OK | 15:23 |
xiangxinyong456 | yuval: good job:) | 15:23 |
chenying | I will research the porject tomorrow | 15:23 |
*** rderose has joined #openstack-meeting | 15:24 | |
*** shaohe_feng has joined #openstack-meeting | 15:24 | |
chenzeng | the operation engine can not work untill merge my several patches.please review them | 15:24 |
saggi | I'm sorry I'm cutting the meeting short but I have a lot on my plate. | 15:25 |
saggi | So unless anyone has something to say I'll end the meeting | 15:25 |
*** jungleboyj has joined #openstack-meeting | 15:25 | |
*** salv-orlando has quit IRC | 15:25 | |
xiangxinyong456 | good luck, guys. | 15:25 |
xiangxinyong456 | see you later. | 15:25 |
yuval | I suggest you guys at China should get some sleep too :) | 15:26 |
*** ub has quit IRC | 15:26 | |
*** salv-orlando has joined #openstack-meeting | 15:26 | |
xiangxinyong456 | we are excited now. | 15:26 |
saggi | :) | 15:26 |
xiangxinyong456 | :) | 15:26 |
saggi | #endmeeting | 15:26 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 15:26 | |
openstack | Meeting ended Tue Jun 14 15:26:28 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:26 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/smaug/2016/smaug.2016-06-14-15.00.html | 15:26 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/smaug/2016/smaug.2016-06-14-15.00.txt | 15:26 |
openstack | Log: http://eavesdrop.openstack.org/meetings/smaug/2016/smaug.2016-06-14-15.00.log.html | 15:26 |
yuval | bye, see you all later | 15:26 |
*** henrynash_ has joined #openstack-meeting | 15:26 | |
xiangxinyong456 | bye | 15:26 |
*** yuval has quit IRC | 15:26 | |
*** rrecio_ has quit IRC | 15:27 | |
*** rrecio has joined #openstack-meeting | 15:27 | |
*** jaugustine has joined #openstack-meeting | 15:27 | |
*** zhonghua has quit IRC | 15:27 | |
*** oshidoshi has joined #openstack-meeting | 15:28 | |
*** Julien-z_ has quit IRC | 15:28 | |
*** saggi has left #openstack-meeting | 15:29 | |
*** chenzeng has quit IRC | 15:29 | |
*** salv-orlando has quit IRC | 15:30 | |
*** salv-orlando has joined #openstack-meeting | 15:30 | |
*** tongli has joined #openstack-meeting | 15:31 | |
*** shaohe_feng has quit IRC | 15:31 | |
*** tellesnobrega is now known as tellesnobrega_af | 15:32 | |
*** shaohe_feng has joined #openstack-meeting | 15:32 | |
*** zeih has joined #openstack-meeting | 15:32 | |
*** chenying has quit IRC | 15:32 | |
*** zeih has quit IRC | 15:32 | |
*** zeih has joined #openstack-meeting | 15:32 | |
*** jaugustine has quit IRC | 15:33 | |
*** Poornima has quit IRC | 15:33 | |
*** jtomasek_ has joined #openstack-meeting | 15:34 | |
*** ivc_ has quit IRC | 15:35 | |
*** azbiswas has joined #openstack-meeting | 15:36 | |
*** Na3iL has quit IRC | 15:36 | |
*** azbiswas_ has joined #openstack-meeting | 15:37 | |
*** zeih has quit IRC | 15:38 | |
*** permalac has joined #openstack-meeting | 15:38 | |
*** cbouch has joined #openstack-meeting | 15:39 | |
*** cbouch_ has joined #openstack-meeting | 15:40 | |
*** azbiswas has quit IRC | 15:40 | |
*** nmagnezi has quit IRC | 15:40 | |
*** roxanaghe has joined #openstack-meeting | 15:41 | |
*** shaohe_feng has quit IRC | 15:42 | |
*** shaohe_feng has joined #openstack-meeting | 15:43 | |
*** cbouch has quit IRC | 15:43 | |
*** yamamoto has quit IRC | 15:43 | |
*** xinwu has joined #openstack-meeting | 15:44 | |
*** delattec has joined #openstack-meeting | 15:44 | |
*** pradk has joined #openstack-meeting | 15:44 | |
*** zeih has joined #openstack-meeting | 15:44 | |
*** yamamoto has joined #openstack-meeting | 15:44 | |
*** roxanaghe has quit IRC | 15:46 | |
*** cdelatte has quit IRC | 15:47 | |
*** yamamoto has quit IRC | 15:47 | |
*** yamamoto has joined #openstack-meeting | 15:48 | |
*** cbouch_ has quit IRC | 15:48 | |
*** yamamoto has quit IRC | 15:50 | |
*** delattec has quit IRC | 15:51 | |
*** jlanoux has joined #openstack-meeting | 15:52 | |
*** rmizuno_ has quit IRC | 15:52 | |
*** shaohe_feng has quit IRC | 15:52 | |
*** shaohe_feng has joined #openstack-meeting | 15:53 | |
*** jamesmcarthur has quit IRC | 15:53 | |
*** ivc_ has joined #openstack-meeting | 15:53 | |
*** andreas_s has quit IRC | 15:53 | |
*** delattec has joined #openstack-meeting | 15:53 | |
*** jtomasek_ has quit IRC | 15:54 | |
*** nisha__ has joined #openstack-meeting | 15:55 | |
*** yamamoto has joined #openstack-meeting | 15:55 | |
*** gcb has quit IRC | 15:55 | |
*** rmizuno_ has joined #openstack-meeting | 15:55 | |
*** jamesmcarthur has joined #openstack-meeting | 15:56 | |
*** gcb has joined #openstack-meeting | 15:56 | |
*** nisha_ has quit IRC | 15:56 | |
*** brucet has joined #openstack-meeting | 15:57 | |
*** KanagarajM has joined #openstack-meeting | 15:57 | |
*** Leo_ has joined #openstack-meeting | 15:57 | |
*** sshnaidm has quit IRC | 15:58 | |
*** yassine has quit IRC | 15:58 | |
*** santoshk has joined #openstack-meeting | 15:58 | |
*** jaypipes has joined #openstack-meeting | 15:59 | |
*** sripriya_ has joined #openstack-meeting | 15:59 | |
*** tung_doan has joined #openstack-meeting | 15:59 | |
*** Leom has joined #openstack-meeting | 16:00 | |
*** e0ne has quit IRC | 16:00 | |
sridhar_ram | #startmeeting tacker | 16:00 |
openstack | Meeting started Tue Jun 14 16:00:33 2016 UTC and is due to finish in 60 minutes. The chair is sridhar_ram. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:00 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:00 |
*** openstack changes topic to " (Meeting topic: tacker)" | 16:00 | |
openstack | The meeting name has been set to 'tacker' | 16:00 |
sridhar_ram | #topic Roll Call | 16:00 |
*** openstack changes topic to "Roll Call (Meeting topic: tacker)" | 16:00 | |
vishwanathj | o/ | 16:00 |
*** s3wong has joined #openstack-meeting | 16:00 | |
sripriya_ | o/ | 16:01 |
*** _nadya_ has joined #openstack-meeting | 16:01 | |
s3wong | o/ | 16:01 |
santoshk | o/ | 16:01 |
*** thorst is now known as thorst_afk | 16:01 | |
sridhar_ram | howdy all ! let's give a min before we start... | 16:01 |
*** fnaval has quit IRC | 16:01 | |
*** yamamoto has quit IRC | 16:01 | |
*** _nadya_ has quit IRC | 16:02 | |
*** rderose_ has joined #openstack-meeting | 16:02 | |
*** hemnafk is now known as hemna | 16:02 | |
tung_doan | Hi all | 16:02 |
*** shaohe_feng has quit IRC | 16:02 | |
sridhar_ram | i know bobh and tbh are out today | 16:02 |
sridhar_ram | tung_doan: hi there! | 16:02 |
*** Leo_ has quit IRC | 16:02 | |
sridhar_ram | KanagarajM: are you here ? | 16:02 |
KanagarajM | sridhar_ram: hi | 16:02 |
*** sripriya_ is now known as sripriya | 16:02 | |
sridhar_ram | okay, lets start... | 16:03 |
sridhar_ram | #topic Agenda | 16:03 |
*** shaohe_feng has joined #openstack-meeting | 16:03 | |
*** openstack changes topic to "Agenda (Meeting topic: tacker)" | 16:03 | |
sridhar_ram | #link https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_June_14.2C_2016 | 16:03 |
*** longxiongqiu has quit IRC | 16:03 | |
sridhar_ram | anything else to discuss ? we might have some time for open topics | 16:03 |
*** matrohon has quit IRC | 16:04 | |
sridhar_ram | alright... | 16:04 |
sridhar_ram | #topic Annoucements | 16:04 |
*** openstack changes topic to "Annoucements (Meeting topic: tacker)" | 16:04 | |
sridhar_ram | We have a bug fix release 0.3.1 out for Mitaka ... | 16:04 |
*** xinwu has quit IRC | 16:04 | |
sridhar_ram | tacker 0.3.1 (mitaka) bug fix release | 16:04 |
sridhar_ram | #link http://lists.openstack.org/pipermail/openstack-announce/2016-June/001213.html | 16:04 |
*** hashar is now known as hasharOut | 16:04 | |
sridhar_ram | tacker-horizon 0.3.1 (mitaka) bug fix release | 16:04 |
sridhar_ram | http://lists.openstack.org/pipermail/openstack-announce/2016-June/001216.html | 16:05 |
*** rderose has quit IRC | 16:05 | |
sridhar_ram | python-tackerclient 0.3.1 (mitaka) bug fix release | 16:05 |
sridhar_ram | http://lists.openstack.org/pipermail/openstack-announce/2016-June/001223.html | 16:05 |
*** ljxiash has quit IRC | 16:05 | |
sridhar_ram | Thanks for all those cherrypicks... | 16:05 |
sridhar_ram | Also, I'd like to thank the reviewers as we have picked up our review response / merge rate! | 16:06 |
*** fnaval has joined #openstack-meeting | 16:06 | |
*** leeantho has joined #openstack-meeting | 16:06 | |
*** bluex has joined #openstack-meeting | 16:06 | |
sridhar_ram | Heads up, i'm out whole next week for OPNFV Summit @ Berlin.. | 16:06 |
sridhar_ram | I'll cancel next week's mtg unless someone else wants to host it | 16:06 |
sridhar_ram | moving on.. | 16:07 |
sridhar_ram | #topic Monitoring & Scaling specs | 16:07 |
*** openstack changes topic to "Monitoring & Scaling specs (Meeting topic: tacker)" | 16:07 | |
*** jaugustine has joined #openstack-meeting | 16:07 | |
*** rderose_ has quit IRC | 16:08 | |
KanagarajM | https://review.openstack.org/#/c/318577/7/specs/newton/manual-and-auto-scaling.rst | 16:08 |
sridhar_ram | KanagarajM: tung_doan: do you | 16:08 |
* sridhar_ram oops | 16:08 | |
sridhar_ram | KanagarajM: tung_doan: do you've any specific subtopics / design issues in these specs to discuss now ? | 16:08 |
tung_doan | sridhar_ram: also, my spec is updated: https://review.openstack.org/#/c/306562/12/specs/newton/alarm-based-monitoring-driver.rst | 16:08 |
KanagarajM | sridhar_ram: I have got some comments from sripriya and answered them ... and today i tried to define the schema for the new types | 16:09 |
*** ygbo has quit IRC | 16:09 | |
*** rderose has joined #openstack-meeting | 16:09 | |
KanagarajM | sridhar_ram: yeah, so would like to get feedback on https://review.openstack.org/#/c/329528/1/tacker/vm/tosca/lib/tacker_defs.yaml | 16:09 |
tung_doan | sridhar_ram: yes, some things related to alarm-url in monitoring driver | 16:09 |
sridhar_ram | unfortunately we are missing both bobh & tbh who can advise on tosca lib | 16:10 |
KanagarajM | sridhar_ram: trying to introduce a scalegroup after refering a tosca simple profile | 16:10 |
*** yamamoto has joined #openstack-meeting | 16:10 | |
*** xyang1 has quit IRC | 16:10 | |
tung_doan | sridhar_ram: please have a look at L114 | 16:10 |
* sridhar_ram is looking | 16:10 | |
sripriya | KanagarajM: sridhar_ram: i would like to know if it is beneficial to show scaling stats all the way to the user or are they supposed to get that from heat? | 16:10 |
sridhar_ram | KanagarajM: hang on, lets take one at a time :) | 16:11 |
*** ijw has joined #openstack-meeting | 16:11 | |
*** zeih has quit IRC | 16:11 | |
KanagarajM | sridhar_ram: yeah, sure, will wait on scaling :) | 16:11 |
*** yamamoto_ has joined #openstack-meeting | 16:11 | |
sridhar_ram | for TOSCA changes for both monitoring and scaling, tacker_defs.yaml is the right approach as this is not really coming from TOSCA NFV profile | 16:12 |
*** yamamoto has quit IRC | 16:12 | |
sridhar_ram | basing it off TOSCA Simple Profile is the right approach | 16:12 |
*** shaohe_feng has quit IRC | 16:12 | |
sridhar_ram | fyi... TOSCA Simple Profile is here http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.0/TOSCA-Simple-Profile-YAML-v1.0.html | 16:13 |
*** natarajk has joined #openstack-meeting | 16:13 | |
*** xyang1 has joined #openstack-meeting | 16:13 | |
*** sridharg has quit IRC | 16:13 | |
*** shaohe_feng has joined #openstack-meeting | 16:13 | |
sridhar_ram | tung_doan: do this make sense? we shd insert Monitoring node type in tacker_defs.yaml | 16:13 |
sripriya | KanagarajM: why don't we push this new type to tosca parser project? | 16:13 |
*** bluex has left #openstack-meeting | 16:14 | |
sridhar_ram | KanagarajM: oh, sure we could.. that is the preferred approach | 16:14 |
*** iyamahat has quit IRC | 16:14 | |
tung_doan | sridhar_ram: sure. | 16:14 |
*** LouisF has joined #openstack-meeting | 16:14 | |
*** yamahata has quit IRC | 16:14 | |
KanagarajM | sridhar_ram: ok. thanks i will update the spec with the new def in place, | 16:15 |
sridhar_ram | if we are blocked due to some reason in tosca-parser project, we can temporarily host it in tacker_defs.yaml | 16:15 |
*** mriedem has joined #openstack-meeting | 16:15 | |
sridhar_ram | tung_doan: you had a question on alarm-url in monitoring driver ? | 16:15 |
*** yamamoto_ has quit IRC | 16:15 | |
KanagarajM | sridhar_ram: sure. I will try to catch sahdev | 16:16 |
tung_doan | sridhar_ram: right... let take a lookpleae :) | 16:16 |
*** lblanchard has quit IRC | 16:16 | |
sridhar_ram | tung_doan: link please ? | 16:16 |
*** permalac has quit IRC | 16:16 | |
tung_doan | sridhar_ram: https://review.openstack.org/#/c/306562/12/specs/newton/alarm-based-monitoring-driver.rst | 16:16 |
tung_doan | Line 114 | 16:16 |
KanagarajM | sripriya: I think, we could retrieve from heat when ever user make a request, or do you want to store in the deviceattributes table about the current state of scaling? | 16:16 |
*** Apoorva has joined #openstack-meeting | 16:16 | |
*** zeih has joined #openstack-meeting | 16:17 | |
sridhar_ram | tung_doan: i have doubts exactly in the same spot as well.. | 16:17 |
*** Apoorva has quit IRC | 16:17 | |
sripriya | KanagarajM: probably we could take this up once we finish monitoring discussion? | 16:17 |
*** yamahata has joined #openstack-meeting | 16:18 | |
*** bluex has joined #openstack-meeting | 16:18 | |
*** Apoorva has joined #openstack-meeting | 16:18 | |
*** kebray has joined #openstack-meeting | 16:18 | |
KanagarajM | sripriya: Ah, sure. thats right :) | 16:18 |
tung_doan | sridhar_ram: does it make sense, sridhar? | 16:18 |
*** jaugustine has quit IRC | 16:18 | |
*** mriedem1 has quit IRC | 16:18 | |
sridhar_ram | KanagarajM: tung_doan: referring to monitoring policy id and scaling id in the API URI doesn't make sense | 16:18 |
sridhar_ram | these id, as far as I understand, refers to the policy name in the TOSCA template ? | 16:19 |
KanagarajM | sridhar_ram: its an name of the policies | 16:19 |
KanagarajM | sridhar_ram: yeah right | 16:19 |
sridhar_ram | so the URL will look like ... | 16:19 |
tung_doan | sridhar_ram: but srihar.. monitoirng policy can some actions | 16:19 |
sridhar_ram | "v1.0/vnfs/df2323-234234df2-23c23f32-3r4r234/vdu1_cpu_usage_monitoring_policy/<action-id> | 16:20 |
KanagarajM | RESTful API does allows to have action names it in | 16:20 |
tung_doan | sridhar_ram: sounds good | 16:20 |
*** timcline has quit IRC | 16:20 | |
KanagarajM | sridhar_ram: yes, its should be fine IMO | 16:20 |
KanagarajM | instead of action-id, it could be action-name | 16:21 |
*** timcline has joined #openstack-meeting | 16:21 | |
sridhar_ram | okay, this means we need to decompose tosca template node names into addressable attributes | 16:21 |
KanagarajM | so that it would confuse by terms | 16:21 |
sripriya | KanagarajM: again that is unique only tot he VNF | 16:21 |
sridhar_ram | doable | 16:21 |
*** dtrainor has joined #openstack-meeting | 16:21 | |
sripriya | KanagarajM: i could have another VNF with same policy name and the url will only defer on the uuid | 16:21 |
KanagarajM | sripriya: yes, | 16:22 |
*** bcafarelli has quit IRC | 16:22 | |
*** Nag_ has quit IRC | 16:22 | |
*** lyrrad has joined #openstack-meeting | 16:22 | |
tung_doan | KanagarajM: i already mentioned "action_name" in my spec | 16:22 |
*** zeih has quit IRC | 16:22 | |
KanagarajM | tung_doan: sure. | 16:22 |
*** shaohe_feng has quit IRC | 16:23 | |
sridhar_ram | tung_doan: KanagarajM: we need a pick one name! | 16:23 |
tung_doan | sridhar_ram: that's why I come today :) | 16:23 |
*** shaohe_feng has joined #openstack-meeting | 16:23 | |
sridhar_ram | tung_doan: cool, worth it :) | 16:23 |
*** longxiongqiu has joined #openstack-meeting | 16:23 | |
sridhar_ram | tung_doan: another question.. | 16:23 |
*** xinwu has joined #openstack-meeting | 16:24 | |
tung_doan | KanagarajM: could I mentioned to metadata in my spec | 16:24 |
tung_doan | KanagarajM: in case if auto-scaling | 16:24 |
sridhar_ram | tung_doan: are we going to run a oslo_service/wsgi endpoint to take these webhook callback ? | 16:24 |
KanagarajM | sridhar_ram: yes, i believe so | 16:25 |
sridhar_ram | tung_doan: does it going a separate threads to process these callbacks ? | 16:25 |
*** xinwu has quit IRC | 16:25 | |
sripriya | sridhar_ram: +1 | 16:25 |
*** timcline has quit IRC | 16:25 | |
sridhar_ram | okay, then we need this part to be scalable (in the sense, to set num_thread/ workers) | 16:25 |
tung_doan | sridhar_ram: right | 16:25 |
*** pradk has quit IRC | 16:26 | |
KanagarajM | sridhar_ram: similar concept of heat :) | 16:26 |
sridhar_ram | KanagarajM: sure, now how secure this can be ... ? | 16:26 |
sridhar_ram | what if some malicious code can call this webhook ? is there a randon webhook identifier for each invocation ? | 16:26 |
*** rwsu has joined #openstack-meeting | 16:27 | |
*** ekcs has joined #openstack-meeting | 16:27 | |
KanagarajM | sridhar_ram: its right question, heat earlier gives by means of EC2 signing and i think now keystone deprecating it | 16:27 |
KanagarajM | sridhar_ram: so, we need to with tacker RBAC and in case of signaling we should see how to make ceilometer to invoke tacker with required credentails in place | 16:27 |
*** longxiongqiu has quit IRC | 16:28 | |
sridhar_ram | KanagarajM: i thought other projects generate a specific only time identifier (per webhook) | 16:28 |
KanagarajM | sridhar_ram: time identifier ? | 16:28 |
sridhar_ram | .. and as long as the original call is https we would have some level of protection | 16:28 |
sridhar_ram | oops, i meant one-time identifier | 16:29 |
KanagarajM | sridhar_ram: no, its getting used always in case of EC2 signed url in auto-scaling | 16:29 |
sridhar_ram | we can take this offline, but we need some solution to secure the calls coming through this channel (webhook) | 16:30 |
*** njohnston|afk is now known as njohnston | 16:30 | |
KanagarajM | sridhar_ram: yes, | 16:30 |
sridhar_ram | KanagarajM: i see | 16:30 |
sridhar_ram | tung_doan: just to wrap up monitoring.... | 16:30 |
KanagarajM | tung_doan: if possible, could you please check with ceilometer | 16:30 |
tung_doan | sridhar_ram: Kanagaraj: OK | 16:30 |
*** Sukhdev has joined #openstack-meeting | 16:31 | |
sridhar_ram | tung_doan: can you please describe your design for the oslo_service/wsgi endpoint, multi-thread handler for the webhook callback and how you are planning to have this scale ? | 16:31 |
sridhar_ram | tung_doan: .. in meant, in your next patchset | 16:31 |
tung_doan | sridhar_ram: Ok.. I will think about them... | 16:32 |
sridhar_ram | IMO, with that and a some kind of handle on the callback security, we should wrap this spec and land it | 16:32 |
sridhar_ram | let's move onto scaling... | 16:32 |
sridhar_ram | KanagarajM: sorry, you got interrupted.. please continue | 16:33 |
*** shaohe_feng has quit IRC | 16:33 | |
KanagarajM | sridhar_ram: for scaling, i belive we could go with https://review.openstack.org/#/c/329528/1/tacker/vm/tosca/lib/tacker_defs.yaml | 16:33 |
tung_doan | sridhar_ram: anw, please review my spec.. thanks | 16:33 |
*** ijw has quit IRC | 16:33 | |
sridhar_ram | tung_doan: will do, thanks again for join at this late hour | 16:34 |
sridhar_ram | *joining | 16:34 |
*** shaohe_feng has joined #openstack-meeting | 16:34 | |
*** nkrinner is now known as nkrinner_afk | 16:34 | |
KanagarajM | sridhar_ram: and i will place it in tacker and contiune the dev | 16:34 |
*** jaypipes has quit IRC | 16:35 | |
*** ijw has joined #openstack-meeting | 16:35 | |
KanagarajM | sridhar_ram: in parallel, i would check with sahdev on how to take it tosca-parser + heat-translator | 16:35 |
KanagarajM | sridhar_ram: is that fine? | 16:35 |
*** gyee has joined #openstack-meeting | 16:35 | |
*** jlanoux has quit IRC | 16:36 | |
sridhar_ram | KanagarajM: fine, we still need to follow up https://review.openstack.org/#/c/302636/ ? | 16:36 |
*** yamamoto has joined #openstack-meeting | 16:36 | |
*** bzhao has quit IRC | 16:36 | |
KanagarajM | sridhar_ram: yes, sure | 16:36 |
*** bzhao has joined #openstack-meeting | 16:37 | |
sridhar_ram | KanagarajM: for the call back handler .. | 16:37 |
sridhar_ram | KanagarajM: .. you need to coordinate w/ tung_doan, correct? | 16:38 |
*** manikanta_tadi has joined #openstack-meeting | 16:38 | |
KanagarajM | sridhar_ram: for call back, i have asked tung_doan to check with ceilometer | 16:38 |
*** davidsha has joined #openstack-meeting | 16:38 | |
KanagarajM | and follow up on it. | 16:38 |
sridhar_ram | okay.. thanks | 16:38 |
sridhar_ram | one last.. | 16:38 |
*** timcline has joined #openstack-meeting | 16:39 | |
sridhar_ram | have you figured out the dependency between your two work items ? who is going to go first ? | 16:39 |
*** roxanaghe has joined #openstack-meeting | 16:39 | |
sridhar_ram | again, you can decide offline.. but it will be good to have a plan.. | 16:39 |
*** tongli has quit IRC | 16:39 | |
KanagarajM | sridhar_ram: it should go in parallel, and for the auto-scaling from the alarm-monitor can go last | 16:40 |
sridhar_ram | .. so that you don't trip each other :) | 16:40 |
*** obondarev has quit IRC | 16:40 | |
KanagarajM | sridhar_ram: 1. scaling and/or monitoring 2. auto-scaling from monitor driver | 16:40 |
sridhar_ram | KanagarajM: sounds good :) | 16:40 |
sridhar_ram | tung_doan: KanagarajM: thanks! | 16:40 |
tung_doan | sridhar_ram: np :) | 16:40 |
*** rbartal has joined #openstack-meeting | 16:40 | |
KanagarajM | sridhar_ram: so i don't see any dependency for manual scaling | 16:41 |
sridhar_ram | okay.. i've a clarification on that, but will take it offline.. | 16:41 |
sripriya | KanagarajM: sridhar_ram: should we capture scalign stats in tacker? | 16:41 |
sripriya | *scaling | 16:41 |
KanagarajM | sripriya: you had some questions, and i answered, kindly let me know your feed back | 16:41 |
sridhar_ram | KanagarajM: what you mean by scaling stats ? | 16:41 |
sripriya | KanagarajM: sure, will respond to that | 16:41 |
sripriya | sridhar_ram: no. of vdus currently scaled and related metrics? | 16:42 |
KanagarajM | sridhar_ram: sripriya has mentioned that its better toc apture the current state like number of VDUS | 16:42 |
*** toscalix has quit IRC | 16:42 | |
sripriya | sridhar_ram: with scaling coming in, we may start off with 2 instances per vdu and then scale out to 3 based on policies | 16:43 |
*** tesseract has quit IRC | 16:43 | |
*** prashantD__ has joined #openstack-meeting | 16:43 | |
sridhar_ram | that will be usefull | 16:43 |
sripriya | sridhar_ram: the only way to see this is going through heat | 16:43 |
*** shaohe_feng has quit IRC | 16:43 | |
*** e0ne has joined #openstack-meeting | 16:43 | |
sridhar_ram | apart from the event-logging on every scale event | 16:43 |
*** nisha__ has quit IRC | 16:43 | |
*** nisha_ has joined #openstack-meeting | 16:43 | |
*** shaohe_feng has joined #openstack-meeting | 16:44 | |
sripriya | sridhar_ram: yes... | 16:44 |
sridhar_ram | KanagarajM: we got to probe heat to get that stat ? again, depends on the effort .. we can always do this in a follow on | 16:44 |
*** e0ne has quit IRC | 16:44 | |
*** brucet has quit IRC | 16:44 | |
KanagarajM | sridhar_ram: yeah, thats better plan. | 16:45 |
sripriya | KanagarajM: sounds good | 16:45 |
*** azbiswas_ has quit IRC | 16:45 | |
sridhar_ram | KanagarajM: i'd suggest we split it into a follow on RFE if that is going to be long poll | 16:45 |
KanagarajM | sridhar_ram: yeah sure. | 16:45 |
KanagarajM | sridhar_ram: it would be great if you could help to merge the spec before your OPNFV summit trip :) | 16:46 |
KanagarajM | sridhar_ram: i could use that week to impl | 16:46 |
sridhar_ram | yes, we should shoot for that.. :) | 16:46 |
*** coolsvap has quit IRC | 16:46 | |
KanagarajM | sripriya: i would seek your help too :) | 16:47 |
KanagarajM | sridhar_ram: yeah sure :) | 16:47 |
sripriya | KanagarajM: sure | 16:47 |
sridhar_ram | tung_doan: KanagarajM: lets sync up to catchup in the #tacker channel and/or ML to keep this moving.. so that we don't wait for this weekly meeting | 16:47 |
*** xiangxinyong456 has quit IRC | 16:47 | |
sridhar_ram | moving to the next topic... | 16:47 |
tung_doan | sridhar_ram: agree | 16:47 |
KanagarajM | sridhar_ram: sure. | 16:47 |
sridhar_ram | #topic Midcycle Meetup - Virtual vs F2F | 16:48 |
*** openstack changes topic to "Midcycle Meetup - Virtual vs F2F (Meeting topic: tacker)" | 16:48 | |
*** adiantum has quit IRC | 16:48 | |
sridhar_ram | based on the doodle pool .. http://doodle.com/poll/2p62zzgevg6h5xkn | 16:48 |
*** ivc_ has quit IRC | 16:49 | |
sridhar_ram | .. we unanimously prefer a virtual midcycle meetup | 16:49 |
*** salv-orlando has quit IRC | 16:49 | |
sridhar_ram | i propose we do a two-day Virtual Meetup with two different timeslots.. | 16:49 |
sridhar_ram | .. one Asia friendly and another w/ US / Europe | 16:50 |
sridhar_ram | thoughts ? | 16:50 |
*** salv-orlando has joined #openstack-meeting | 16:50 | |
*** ijw has quit IRC | 16:50 | |
*** jlibosva has joined #openstack-meeting | 16:50 | |
sripriya | +1 | 16:51 |
sridhar_ram | anyways, i will create another doodle poll to finalize the timeslots | 16:51 |
manikanta_tadi | +1 | 16:51 |
s3wong | +1 | 16:51 |
KanagarajM | sridhar_ram: nice | 16:51 |
sridhar_ram | i was start an etherpad as well.. and we should start collecting ideas for topics to discuss | 16:52 |
*** Daisy has joined #openstack-meeting | 16:52 | |
sridhar_ram | Here it is https://etherpad.openstack.org/p/tacker-newton-midcycle | 16:52 |
*** hdaniel has quit IRC | 16:53 | |
sridhar_ram | zeih offered an EU location.. i wish we can go there for tacker midcycle one day :) | 16:53 |
sridhar_ram | moving on... | 16:53 |
*** shaohe_feng has quit IRC | 16:53 | |
sridhar_ram | #topic Bugs, RFE and Open Discussion | 16:53 |
*** openstack changes topic to "Bugs, RFE and Open Discussion (Meeting topic: tacker)" | 16:53 | |
*** sshnaidm has joined #openstack-meeting | 16:54 | |
sridhar_ram | I know we have many bugs and RFEs in flight... | 16:54 |
sridhar_ram | in fact, lots of small but significant things are coming in as RFEs.. | 16:54 |
*** shaohe_feng has joined #openstack-meeting | 16:54 | |
sridhar_ram | i'd like to thankg gongysh for all those oslo refactoring! | 16:54 |
sridhar_ram | anyone have a specific bug or RFE to discuss ? | 16:55 |
*** ja3 has joined #openstack-meeting | 16:55 | |
KanagarajM | sridhar_ram: i am trying to set the retry count to 3 in heat driver | 16:55 |
KanagarajM | sridhar_ram: as 60 is big in number https://review.openstack.org/329527 | 16:55 |
sridhar_ram | KanagarajM: stack retry | 16:55 |
sridhar_ram | ? | 16:55 |
KanagarajM | sridhar_ram: sripriya yes | 16:56 |
*** Daisy has quit IRC | 16:56 | |
KanagarajM | sridhar_ram: yes it was 60 earlier | 16:57 |
sridhar_ram | KanagarajM: well, what to say.. we don't give up trying that easily ;-) | 16:57 |
KanagarajM | sridhar_ram: :) | 16:57 |
sridhar_ram | alright.. please keep the bug fixes, RFEs coming.. | 16:57 |
sripriya | KanagarajM: 300 was the time out keeping vms in mind which take nearly 2 -3 minutes to bring up an instance | 16:58 |
KanagarajM | sridhar_ram: in heat also we try for 3 as default for resource | 16:58 |
*** sajeesh has joined #openstack-meeting | 16:58 | |
sridhar_ram | KanagarajM: sounds good & make sense! | 16:58 |
sripriya | KanagarajM: tacker was false setting VNF to ERROR state even though the actual instance did come up after like 2 minutes on VMs with starved specs | 16:58 |
*** cathy_ has joined #openstack-meeting | 16:59 | |
sridhar_ram | KanagarajM: yeah, thats bad | 16:59 |
*** acabot has quit IRC | 16:59 | |
*** garthb_ has joined #openstack-meeting | 16:59 | |
sridhar_ram | we are out of time.. | 16:59 |
sridhar_ram | thanks everyone who joined.. | 16:59 |
sridhar_ram | again, no meeting next week.. | 16:59 |
sridhar_ram | will meet the week after next... | 16:59 |
sridhar_ram | thanks everyone! | 17:00 |
*** natarajk has left #openstack-meeting | 17:00 | |
s3wong | have fun in Berlin! | 17:00 |
s3wong | bye | 17:00 |
vishwanathj | bye | 17:00 |
KanagarajM | sridhar_ram: will come to tacker | 17:00 |
sridhar_ram | s3wong: thanks! | 17:00 |
sridhar_ram | #endmeeting | 17:00 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 17:00 | |
KanagarajM | sripriya: will come to tacker | 17:00 |
openstack | Meeting ended Tue Jun 14 17:00:18 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 17:00 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-06-14-16.00.html | 17:00 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-06-14-16.00.txt | 17:00 |
openstack | Log: http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-06-14-16.00.log.html | 17:00 |
cathy_ | #startmeeting network_common_flow_classifier | 17:00 |
openstack | Meeting started Tue Jun 14 17:00:28 2016 UTC and is due to finish in 60 minutes. The chair is cathy_. Information about MeetBot at http://wiki.debian.org/MeetBot. | 17:00 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 17:00 |
*** openstack changes topic to " (Meeting topic: network_common_flow_classifier)" | 17:00 | |
openstack | The meeting name has been set to 'network_common_flow_classifier' | 17:00 |
*** xinwu has joined #openstack-meeting | 17:00 | |
*** santoshk has quit IRC | 17:00 | |
*** garthb has quit IRC | 17:00 | |
davidsha | Hi | 17:00 |
cathy_ | Hi everyone | 17:00 |
s3wong | hello | 17:00 |
LouisF | hi cathy_ | 17:00 |
ihrachys | o/ | 17:00 |
*** rderose has quit IRC | 17:00 | |
jlibosva | o/ | 17:00 |
*** mohankumar_ has joined #openstack-meeting | 17:01 | |
asselin_ | is this meeting time double-booked? | 17:01 |
cathy_ | I have posted the agenda in the wiki page https://wiki.openstack.org/wiki/Neutron/CommonFlowClassifier#Contributors | 17:01 |
mohankumar_ | Hi cathy_ | 17:01 |
cathy_ | asselin_: not as far as I know | 17:01 |
mmedvede | this was usually third-party meeting spot | 17:01 |
ja3 | asselin: looking that way | 17:01 |
*** irenab has joined #openstack-meeting | 17:02 | |
jlibosva | asselin_: is third-party weekly mtg? | 17:02 |
jlibosva | or bi-weekly? | 17:02 |
mmedvede | jlibosva: it is bi-weekly | 17:02 |
asselin_ | mabye it's that biweekly bug? | 17:02 |
s3wong | this is approved at openstack-infra, which the software would ensure no double booking | 17:02 |
asselin_ | for ical | 17:02 |
*** kebray has quit IRC | 17:03 | |
asselin_ | link? | 17:03 |
*** KanagarajM has left #openstack-meeting | 17:03 | |
mohankumar_ | Neutron Common Classifier meeting booked for odd weeks | 17:03 |
*** acabot has joined #openstack-meeting | 17:03 | |
mmedvede | ok, for third-party folks, lets convene in #openstack-third-party-ci channel | 17:03 |
*** shaohe_feng has quit IRC | 17:04 | |
cathy_ | mmedvede: sorry about this. Thanks. We will check the time slot again | 17:04 |
mmedvede | and figure it out after, as we do not have a big agenda | 17:04 |
ihrachys | looking at http://eavesdrop.openstack.org/#Neutron_Service_Chaining_meeting | 17:04 |
*** rderose has joined #openstack-meeting | 17:04 | |
ihrachys | I see that it's Thursdays for SFC | 17:04 |
*** shaohe_feng has joined #openstack-meeting | 17:04 | |
cathy_ | ihrachys: this is not for service chaining specific | 17:04 |
ihrachys | oh sorry | 17:04 |
cathy_ | ihrachys: it is for the Neutron Common Flow Classifier | 17:05 |
jlibosva | ihrachys: it;s Neutron Common Classifier meeting | 17:05 |
*** lpetrut has quit IRC | 17:05 | |
*** sajeesh has quit IRC | 17:05 | |
cathy_ | ihrachys: np | 17:05 |
cathy_ | OK, let's start | 17:05 |
ihrachys | as per .ical file, it's next week | 17:05 |
mohankumar_ | ihrachys , yes , classifier meeting on odd weeks .. there is some confusion | 17:06 |
cathy_ | ihrachys: yes, some confusion here. how is it considered odd week? | 17:06 |
*** tellesnobrega_af is now known as tellesnobrega | 17:06 | |
cathy_ | This is the 3rd week of June, isn't it? | 17:06 |
asselin_ | i remember and even/odd week bug for ical where jan 2016 was 2 odd weeks in a row | 17:06 |
ihrachys | cathy_: how do you count? from the start of the year? | 17:07 |
*** sripriya has left #openstack-meeting | 17:07 | |
ihrachys | cathy_: it's annual, not monthly | 17:07 |
mohankumar_ | This is Week 24 in this year | 17:07 |
cathy_ | So count from the start of the year? | 17:07 |
*** thorst_afk is now known as thorst | 17:07 | |
ihrachys | aha | 17:07 |
ihrachys | or just rely on .ical to calculate it for you | 17:08 |
cathy_ | ihrachys: OK, my bad. Sorry folks. I will correct this starting from next meeting | 17:08 |
*** bzhao has quit IRC | 17:08 | |
*** bzhao has joined #openstack-meeting | 17:08 | |
cathy_ | ihrachys: what do you mean by .ical? | 17:08 |
ihrachys | cathy_: http://eavesdrop.openstack.org/#Neutron_Common_Classifier_meeting | 17:09 |
davidsha | cathy_: file for outlook that saves an appoinment | 17:09 |
ihrachys | see the "ICS file for this specific meeting" | 17:09 |
*** ivc_ has joined #openstack-meeting | 17:09 | |
ihrachys | download it and add to your calendar app | 17:09 |
ihrachys | it's .ics actually, sorry | 17:09 |
cathy_ | ihrachys: got it. Thanks! | 17:09 |
mohankumar_ | cathy_ , you can download @ http://eavesdrop.openstack.org/#Neutron_Common_Classifier_meeting | 17:10 |
*** ivar-lazzaro has joined #openstack-meeting | 17:10 | |
cathy_ | mohankumar_: yes, thanks | 17:10 |
*** garthb_ has quit IRC | 17:10 | |
cathy_ | now let's start with the first topic | 17:10 |
ihrachys | +1 | 17:10 |
cathy_ | #topic Bug Status: developed as a RFE over neutron-core? | 17:10 |
*** openstack changes topic to "Bug Status: developed as a RFE over neutron-core? (Meeting topic: network_common_flow_classifier)" | 17:10 | |
*** garthb_ has joined #openstack-meeting | 17:10 | |
*** rossella_s has quit IRC | 17:11 | |
cathy_ | there are two bugs associated with this feature | 17:11 |
cathy_ | #link https://bugs.launchpad.net/neutron/+bug/1583299 | 17:11 |
openstack | Launchpad bug 1476527 in neutron "duplicate for #1583299 [RFE] Add common classifier resource" [Wishlist,In progress] | 17:11 |
cathy_ | #link https://bugs.launchpad.net/neutron/+bug/1476527 | 17:11 |
openstack | Launchpad bug 1476527 in neutron "[RFE] Add common classifier resource" [Wishlist,In progress] | 17:11 |
*** timcline has quit IRC | 17:11 | |
cathy_ | one is duped to the other | 17:11 |
*** timcline has joined #openstack-meeting | 17:12 | |
cathy_ | In our last meeting, the consensus is to developed this feature as a RFE over neutron-core. | 17:12 |
*** e0ne has joined #openstack-meeting | 17:12 | |
cathy_ | Does anyone know whether the neutron team had re-take a look at this bug which has been there for quite some time? https://bugs.launchpad.net/neutron/+bug/1476527 | 17:13 |
openstack | Launchpad bug 1476527 in neutron "[RFE] Add common classifier resource" [Wishlist,In progress] | 17:13 |
cathy_ | ihrachys: Do you know? | 17:13 |
*** anilvenkata has joined #openstack-meeting | 17:14 | |
*** shaohe_feng has quit IRC | 17:14 | |
ihrachys | hm, it's approved so what is missing? | 17:14 |
ihrachys | note that as per armax, "but eventually this would end up being its own neutron stadium repo/LP project, and *not* the Neutron/Neutron-specs repos." | 17:14 |
*** shaohe_feng has joined #openstack-meeting | 17:15 | |
ihrachys | if you want drivers to get back to it for some reason, we probably need to tag it as rfe again | 17:15 |
ihrachys | but I would better talk to armax | 17:15 |
ihrachys | so, is the latest resolution not in line with your vision? | 17:16 |
*** timcline has quit IRC | 17:16 | |
*** klkumar has quit IRC | 17:17 | |
cathy_ | ihrachys: per our discussion in last meeting, we would like it to be tagged as rfe-approved, not as a new stadium project | 17:17 |
*** pradk has joined #openstack-meeting | 17:17 | |
ihrachys | cathy_: then I guess we need to run the RFE bug thru drivers team again | 17:17 |
cathy_ | similar to the way L2 agent feature is handled | 17:17 |
*** tung_doan has quit IRC | 17:17 | |
*** ijw__ has joined #openstack-meeting | 17:17 | |
*** ijw__ has quit IRC | 17:18 | |
ihrachys | I agree it's core to the project goals | 17:18 |
cathy_ | ihrachys: Anything we need to do for "run the RFE bug thru drivers team again"? | 17:18 |
ihrachys | I think we should just replace rfe-approved tag with rfe | 17:18 |
ihrachys | lemme handle it | 17:19 |
cathy_ | ihrachys: OK, thanks! | 17:19 |
igordcard | what about neutron-classifier? | 17:19 |
*** ssalagame has quit IRC | 17:19 | |
cathy_ | This is the neutron-classifier feature | 17:19 |
cathy_ | igordcard: This is the neutron-classifier feature | 17:19 |
*** ijw__ has joined #openstack-meeting | 17:19 | |
*** ekcs has joined #openstack-meeting | 17:19 | |
cathy_ | #action ihrachys will run the RFE bug thru drivers team again | 17:20 |
igordcard | neutron-classifier can still be core even if it is in its own repo | 17:20 |
*** sean-k-mooney has joined #openstack-meeting | 17:20 | |
igordcard | this common classifier seems like a new effort that doesn't use neutron-classifier at all | 17:20 |
ihrachys | not that there is much to use there, right? | 17:21 |
cathy_ | igordcard: we will only have one classifier for the Neutron and the team will work together for that goal | 17:21 |
cathy_ | ihrachys: I think so | 17:21 |
cathy_ | ihrachys: but we will try to reuse existing implementation as much as possible | 17:21 |
sean-k-mooney | cathy_: there is a datamodle | 17:21 |
*** vuntz has quit IRC | 17:22 | |
cathy_ | sean-k-mooney: yes. | 17:22 |
igordcard | cathy_: but the model proposed in the CC wiki looks completely different from openstack/neutron-classifier | 17:22 |
*** vishnoianil has quit IRC | 17:22 | |
sean-k-mooney | the implementation in the neutron-classifyer is type based so it is different form what exists in the security group api and networking-sfc | 17:22 |
*** lixiaoy1 has quit IRC | 17:22 | |
*** alex_xu has quit IRC | 17:22 | |
cathy_ | I think we need to first agree on the API, data model design, then we can evaluate existing cdoe | 17:23 |
sean-k-mooney | cathy_: yes i think that is a better first step | 17:23 |
LouisF | cathy_: agree | 17:23 |
s3wong | cathy_: true | 17:24 |
*** lixiaoy1 has joined #openstack-meeting | 17:24 | |
*** shaohe_feng has quit IRC | 17:24 | |
mohankumar_ | cathy_ : +1 | 17:24 |
sean-k-mooney | so in terms of design i see two different proposals for the api | 17:24 |
*** alex_xu has joined #openstack-meeting | 17:25 | |
sean-k-mooney | form the security group api and networking sfc the l1-7 classifcaion exist withing a singel api resource | 17:25 |
*** mjturek1 has joined #openstack-meeting | 17:26 | |
*** mjturek1 has left #openstack-meeting | 17:26 | |
*** salv-orlando has quit IRC | 17:26 | |
cathy_ | #topic API design discussion | 17:26 |
*** openstack changes topic to "API design discussion (Meeting topic: network_common_flow_classifier)" | 17:26 | |
*** yamamoto has quit IRC | 17:26 | |
sean-k-mooney | in the neutron-classifier the classification is a compostion | 17:26 |
*** salv-orlando has joined #openstack-meeting | 17:26 | |
cathy_ | sean-k-mooney: good point. | 17:27 |
*** shaohe_feng has joined #openstack-meeting | 17:27 | |
LouisF | sean-k-mooney: can you elaborate | 17:27 |
igordcard | sean-k-mooney: cathy_ : this second approach is also described in more detail at https://bugs.launchpad.net/neutron/+bug/1476527/comments/26 | 17:27 |
openstack | Launchpad bug 1476527 in neutron "[RFE] Add common classifier resource" [Wishlist,In progress] | 17:27 |
cathy_ | how about someone evaluate the pros and cons of the two ways | 17:28 |
*** noslzzp has quit IRC | 17:28 | |
cathy_ | anyone would like to take this evaluation work? | 17:28 |
sean-k-mooney | cathy_: i think it would be better to dicuss in a spec rather then one person evaluating | 17:29 |
*** noslzzp has joined #openstack-meeting | 17:29 | |
ihrachys | + for a spec | 17:29 |
igordcard | I'll post a spec | 17:29 |
*** salv-orl_ has joined #openstack-meeting | 17:29 | |
cathy_ | igordcard: thanks! | 17:29 |
igordcard | sorry I need to leave the meeting now - will catchup afterwards with the logs | 17:30 |
cathy_ | #action igordcard will post a spec on the pros and cons of the two classification ways | 17:30 |
igordcard | cya, thanks | 17:30 |
*** lblanchard has joined #openstack-meeting | 17:30 | |
davidsha | bye | 17:31 |
sean-k-mooney | well should the spec not capture the implentation approch rather then the pros and cons | 17:31 |
*** banix_ has joined #openstack-meeting | 17:31 | |
*** banix has quit IRC | 17:31 | |
*** banix_ is now known as banix | 17:31 | |
sean-k-mooney | ie discribe the datamodels and api for both solutions | 17:31 |
cathy_ | sean-k-mooney: yes, that should be included otherwise people can not evaluate whether the pros and cons make sense | 17:32 |
sean-k-mooney | as the spec is reviewed we can then converge on one implenttion that meets the contraitns | 17:32 |
*** salv-orlando has quit IRC | 17:32 | |
cathy_ | sean-k-mooney: I would think before we decide on one approach, no need to dive into very detail | 17:32 |
cathy_ | after the team reaches consensus on one way, we can have another spec detailing the API, data model etc. | 17:33 |
*** s3wong has quit IRC | 17:33 | |
cathy_ | I think we first need to agree on the high level which way to go (with enough detail for the team to make decision) | 17:33 |
*** vuntz has joined #openstack-meeting | 17:34 | |
*** Leom has quit IRC | 17:34 | |
*** shaohe_feng has quit IRC | 17:34 | |
sean-k-mooney | sure though at least a preliminay defintion of the api and data model will be needed but i will not neet to be complete | 17:34 |
cathy_ | sean-k-mooney: yes, agree. | 17:35 |
*** mohankumar_ has quit IRC | 17:35 | |
*** shaohe_feng has joined #openstack-meeting | 17:35 | |
sean-k-mooney | something akin to https://review.openstack.org/#/c/318317/5/doc/source/devref/openvswitch_agent.rst i think would be a good guide | 17:35 |
cathy_ | I think we have completed the second topic on the agenda:-) | 17:35 |
LouisF | sean-k-mooney: yes that is a good example for the spec | 17:36 |
cathy_ | sean-k-mooney: This is "implementation detail", which should be the spec. But for evaluation, we probably do not need this detail. | 17:37 |
ihrachys | you can always start with a less detailed draft and then fill it in with details | 17:37 |
*** mriedem1 has joined #openstack-meeting | 17:38 | |
LouisF | there should be sufficient to be able to identify the pros/cons of each approach | 17:38 |
sean-k-mooney | cathy_: yes that was the implentation but i was using it to illistrate how both options are compared rather then present one as the solution and the other as an alternitive | 17:39 |
LouisF | sufficient detail | 17:39 |
*** ja3 has quit IRC | 17:39 | |
cathy_ | sean-k-mooney: OK, Sure | 17:39 |
cathy_ | sean-k-mooney: I think it is important not to present one as the solution and the other as alternative | 17:40 |
*** mriedem has quit IRC | 17:40 | |
cathy_ | I will work with igordcard on this comparison spec | 17:40 |
cathy_ | anyone else would like to contribute to this spec? | 17:40 |
*** e0ne has quit IRC | 17:41 | |
*** tonytan4ever has joined #openstack-meeting | 17:41 | |
*** pnavarro has quit IRC | 17:41 | |
cathy_ | ihrachys: yes | 17:41 |
*** electrofelix has quit IRC | 17:41 | |
cathy_ | We are done with the topics on the agenda. Any other topic you would like to discuss? | 17:41 |
*** mriedem1 is now known as mriedem | 17:42 | |
*** sambetts is now known as sambetts|afk | 17:42 | |
davidsha | cathy_: I've made some PoC code for the Flow manager if people would like to give their opinions | 17:42 |
*** yohoffman_ has joined #openstack-meeting | 17:42 | |
*** _nadya_ has joined #openstack-meeting | 17:42 | |
davidsha | #link https://review.openstack.org/#/c/323963/ | 17:42 |
*** mohankumar__ has joined #openstack-meeting | 17:42 | |
cathy_ | davidsha: that is related to L2 agent extension, not quite the flow classifier, right? | 17:43 |
*** roxanagh_ has joined #openstack-meeting | 17:43 | |
jlibosva | davidsha: is it implementing the draft that ajo proposed? | 17:43 |
LouisF | cathy_: I can help with spec also | 17:44 |
cathy_ | LouisF: great, thanks! | 17:44 |
*** asselin_ has quit IRC | 17:44 | |
cathy_ | #action Louis and Cathy will work with igordcard on the spec | 17:44 |
davidsha | cathy_, jlibosva : kinda, it's a bit out of date now but I'm working on it. | 17:44 |
*** shaohe_feng has quit IRC | 17:45 | |
*** ociuhandu has quit IRC | 17:45 | |
ihrachys | davidsha: not related to the meeting, but looks less scary than I thought :) | 17:45 |
davidsha | ihrachys: You haven't seen the prioritization yet @.@ | 17:45 |
*** shaohe_feng has joined #openstack-meeting | 17:45 | |
cathy_ | davidsha: yes not related to the meeting since this meeting is specific to FC:-) | 17:45 |
cathy_ | davidsha: but I will take a look after you update it. Could you add me as reviewer? | 17:46 |
ihrachys | ok folks, I need to run. ciao. | 17:46 |
cathy_ | ihrachys: ok, thanks for joining | 17:46 |
*** ihrachys has quit IRC | 17:46 | |
davidsha | cathy_: kk, I'll do that now. | 17:46 |
*** jlibosva has quit IRC | 17:46 | |
cathy_ | davidsha: thanks. | 17:46 |
cathy_ | I will end this meeting if no other topic on FC. | 17:47 |
cathy_ | 5 | 17:47 |
cathy_ | 4 | 17:47 |
cathy_ | 3 | 17:47 |
*** timcline has joined #openstack-meeting | 17:47 | |
cathy_ | 2 | 17:47 |
cathy_ | 1 | 17:47 |
cathy_ | thanks everyone | 17:47 |
davidsha | thanks | 17:47 |
mohankumar__ | bye | 17:47 |
cathy_ | bye for now | 17:47 |
*** roxanagh_ has quit IRC | 17:47 | |
cathy_ | we will start the next meeting in 3 weeks | 17:47 |
cathy_ | #endmeeting | 17:48 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 17:48 | |
openstack | Meeting ended Tue Jun 14 17:48:04 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 17:48 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2016/network_common_flow_classifier.2016-06-14-17.00.html | 17:48 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2016/network_common_flow_classifier.2016-06-14-17.00.txt | 17:48 |
openstack | Log: http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2016/network_common_flow_classifier.2016-06-14-17.00.log.html | 17:48 |
*** jesusaur has quit IRC | 17:48 | |
*** sean-k-mooney has left #openstack-meeting | 17:48 | |
davidsha | cya | 17:48 |
*** cathy_ has quit IRC | 17:48 | |
*** davidsha has quit IRC | 17:49 | |
*** huangtianhua has joined #openstack-meeting | 17:49 | |
*** jesusaur has joined #openstack-meeting | 17:49 | |
*** pvaneck has joined #openstack-meeting | 17:49 | |
*** toddjohn has joined #openstack-meeting | 17:50 | |
*** mtanino has quit IRC | 17:51 | |
*** tiantian has quit IRC | 17:51 | |
*** timcline has quit IRC | 17:51 | |
*** singhj has quit IRC | 17:53 | |
*** toddjohn has quit IRC | 17:55 | |
*** shaohe_feng has quit IRC | 17:55 | |
*** s3wong has joined #openstack-meeting | 17:55 | |
*** prashantD__ has quit IRC | 17:55 | |
*** browne has joined #openstack-meeting | 17:55 | |
*** vishwanathj has quit IRC | 17:56 | |
*** nisha__ has joined #openstack-meeting | 17:56 | |
*** shaohe_feng has joined #openstack-meeting | 17:56 | |
*** jaugustine has joined #openstack-meeting | 17:57 | |
*** xenogear has joined #openstack-meeting | 17:57 | |
*** Rockyg has joined #openstack-meeting | 17:58 | |
*** ajmiller_ has joined #openstack-meeting | 17:58 | |
*** nisha_ has quit IRC | 17:59 | |
* ayoung early to get good seat | 17:59 | |
stevemar | meeting reminder ajayaa, amakarov, ayoung, breton, browne, crinkle, claudiub, davechen, david8hu, dolphm, dstanek, edmondsw, gyee, henrynash, hogepodge, htruta, jamielennox, joesavak, jorge_munoz, knikolla, lbragstad, lhcheng, marekd, MaxPC, morgan, nkinder, notmorgan, raildo, rodrigods, rderose, roxanaghe, samleon, samueldmq, shaleh, stevemar, tjcocozz, tsymanczyk, topol, vivekd, wanghong, xek | 17:59 |
rodrigods | o/ | 17:59 |
amakarov | hi! | 17:59 |
dolphm | \o | 17:59 |
knikolla | o/ hi! | 17:59 |
*** gagehugo has joined #openstack-meeting | 17:59 | |
raildo | o/ | 17:59 |
htruta | o/ | 17:59 |
rderose | o/ | 17:59 |
roxanaghe | o/ | 17:59 |
MaxPC | o/ | 17:59 |
*** azbiswas has joined #openstack-meeting | 17:59 | |
rmizuno_ | o/ | 17:59 |
bknudson | hi | 17:59 |
ayoung | rodrigods, hey, meant to tell you...that test you showed me yesterday? It is suppsed to work that way | 17:59 |
gagehugo | o_/ | 17:59 |
samueldmq | hi o/ | 17:59 |
ayoung | Federation should be able to match an existing user | 17:59 |
notmorgan | o/ | 17:59 |
jaugustine | o/ | 17:59 |
crinkle | o/ | 17:59 |
nisha__ | o/ | 17:59 |
rodrigods | ayoung, hmm | 17:59 |
browne | o/ | 17:59 |
stevemar | ohhh packed house today | 18:00 |
*** nisha__ is now known as nisha_ | 18:00 | |
notmorgan | oh we have a stevemar back. welcome back stevemar :) | 18:00 |
gyee | \o | 18:00 |
stevemar | glad to be back notmorgan | 18:00 |
ayoung | rodrigods, say you are using Kerberos via federation, and want to map to an existing LDAP database for groups | 18:00 |
*** MeganR has joined #openstack-meeting | 18:00 | |
stevemar | it's a nice break from diapers | 18:00 |
ayoung | etc etc | 18:00 |
stevemar | #startmeeting keystone | 18:00 |
openstack | Meeting started Tue Jun 14 18:00:34 2016 UTC and is due to finish in 60 minutes. The chair is stevemar. Information about MeetBot at http://wiki.debian.org/MeetBot. | 18:00 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 18:00 |
*** openstack changes topic to " (Meeting topic: keystone)" | 18:00 | |
*** shaleh has joined #openstack-meeting | 18:00 | |
openstack | The meeting name has been set to 'keystone' | 18:00 |
dstanek | o/ | 18:00 |
MeganR | o/ | 18:00 |
shaleh | \o | 18:00 |
*** ajmiller has quit IRC | 18:01 | |
stevemar | let's jump right into it | 18:01 |
stevemar | rmizuno_: you here? | 18:01 |
notmorgan | link the agenda? | 18:01 |
*** dmorita has quit IRC | 18:01 | |
*** timcline has joined #openstack-meeting | 18:01 | |
*** prashantD has joined #openstack-meeting | 18:01 | |
stevemar | notmorgan: thanks, is my rust showing :) | 18:01 |
stevemar | #link https://etherpad.openstack.org/p/keystone-weekly-meeting | 18:01 |
ayoung | \m/ d(-v-)b \m/ | 18:01 |
*** banix has quit IRC | 18:01 | |
lbragstad | o/ | 18:01 |
*** jamielennox has joined #openstack-meeting | 18:01 | |
rmizuno_ | stevemar: yes | 18:02 |
*** dmorita has joined #openstack-meeting | 18:02 | |
stevemar | rmizuno_: doesn't seem to be here, so i'll skip to the next topic, if he... oh there you are | 18:02 |
stevemar | #topic Add resource name to the notification event | 18:02 |
*** openstack changes topic to "Add resource name to the notification event (Meeting topic: keystone)" | 18:02 | |
stevemar | rmizuno_: the floor is yours | 18:02 |
gyee | just do it! | 18:02 |
stevemar | gyee: but names are mutable and domain scoped o_O | 18:02 |
ayoung | we only do IDs now, and that is hard to match, I take it? | 18:02 |
henrynash_ | (hi) | 18:03 |
stevemar | ayoung: yep | 18:03 |
rmizuno_ | #link: https://review.openstack.org/#/c/320299/ | 18:03 |
ayoung | audit events are going to get big | 18:03 |
*** toddjohn has joined #openstack-meeting | 18:03 | |
rmizuno_ | this patch was intended to add a name to the audit notification when the project deleted. | 18:03 |
gyee | stevemar, notification and audits is a snapshot in time | 18:03 |
gyee | nothing more | 18:03 |
dolphm | ayoung: ++ | 18:03 |
rmizuno_ | but, it seems odd to do it just for deleting project. | 18:03 |
* lbragstad we had a similar request here - https://bugs.launchpad.net/keystone/+bug/1552795 | 18:03 | |
openstack | Launchpad bug 1552795 in OpenStack Identity (keystone) "enhance notification for user events with user name" [Wishlist,In progress] - Assigned to Lance Bragstad (lbragstad) | 18:03 |
ayoung | rmizuno_, is this a case of the cure being worse than the disease? | 18:03 |
rmizuno_ | so, I want to gain approval about adding the resource name to all audit notification. | 18:03 |
dstanek | #link https://bugs.launchpad.net/keystone/+bug/1552795 similar bug | 18:03 |
lbragstad | and there were some good points made in that report | 18:03 |
stevemar | rmizuno_: so, i understand the need for doing this for projects | 18:04 |
gyee | we have to understand what notifications and events are for | 18:04 |
gyee | to facilitate monitoring, auditing, and forensics | 18:04 |
stevemar | rmizuno_: but i'd like the code to be done in a way that it's extensible, so users, roles, etc... can also add names to the event | 18:04 |
dolphm | ID's certainly fulfill that requirement | 18:04 |
*** nk2527 has joined #openstack-meeting | 18:04 | |
notmorgan | dolphm: ++ if not being super friendly, but are guaranteed immutable and unique within a deployment | 18:04 |
*** rbartal has quit IRC | 18:05 | |
notmorgan | so are *safe* for such actions | 18:05 |
stevemar | rmizuno_: also, we need to include domain name | 18:05 |
dstanek | gyee: you're missing your implied requirement to tie things back to your source system | 18:05 |
dolphm | the use case in the bug report, and the one we've discussed before, is primarily around the ** user experience ** of receiving an audit notification | 18:05 |
jamielennox | but particularly for a delete action you can't resolve an ID into a name later | 18:05 |
dolphm | not the functionality of audit notifications | 18:05 |
*** shaohe_feng has quit IRC | 18:05 | |
stevemar | dolphm: right, this is totally a UX thing | 18:05 |
gyee | dstanek, its a snapshot of the resource at that time, whatever it was/is | 18:05 |
*** samleon has joined #openstack-meeting | 18:05 | |
ayoung | What if we had a utility to populate it ex-post-facto instead? | 18:05 |
stevemar | if you're using the name as the canonical source, tis your own fault :P | 18:05 |
dstanek | gyee: not saying you're wrong, just that you need to clarify the requirements | 18:06 |
ayoung | lkeep the audit events small, but have a "expand audit log ids" CLI | 18:06 |
*** banix has joined #openstack-meeting | 18:06 | |
bknudson | unless you're keeping essentially a duplicate of the keystone database there's no way you could get the name on a delete event. | 18:06 |
*** shaohe_feng has joined #openstack-meeting | 18:06 | |
dolphm | ayoung: then we have to keep deleted entities around to make that work | 18:06 |
lbragstad | bknudson which is something that can be done today | 18:06 |
stevemar | bknudson: fetch the resource from the backend before deleting? i think we do that now today? | 18:06 |
notmorgan | dolphm: we may want to do that for many reasons [change the course from today] | 18:06 |
dolphm | bknudson: which is not a bad or strange idea at all if you care about your data that deeply | 18:06 |
*** shihanzhang has joined #openstack-meeting | 18:06 | |
ayoung | dolphm, seems like that would be a shrotcoming of the current system, wouldn'tit | 18:06 |
*** shz has quit IRC | 18:07 | |
ayoung | so...better to have the names in there at least for deletes | 18:07 |
gyee | I would hate to have my monitoring system to do a resource looking in order to display meaningful/reading stuff | 18:07 |
lbragstad | bknudson i highlighted that in a summary of this discussion from the summit - http://lbragstad.com/improving-auditing-in-keystone/ | 18:07 |
ayoung | and for anything that is deleted, we would have no way of mapping... | 18:07 |
shaleh | even the ID is useless post delete right? Sure it was unique but what was it..... | 18:07 |
gyee | not to mention having to configure a credential in my monitoring in order to lookup stuff | 18:07 |
*** jamesmcarthur has quit IRC | 18:07 | |
stevemar | shaleh: that was mfisch's point too | 18:07 |
notmorgan | i'm more inclined to make delete not be a "remove the row from the DB" | 18:07 |
notmorgan | fwiw | 18:07 |
*** _nadya_ has quit IRC | 18:07 | |
* ayoung too | 18:07 | |
*** anilvenkata has quit IRC | 18:07 | |
ayoung | soft delets | 18:07 |
ayoung | deletes | 18:07 |
dolphm | gyee: the current audit records *are* meaningful - don't confuse this for a lack of functionality | 18:08 |
notmorgan | ayoung: lets not call it that please... | 18:08 |
dstanek | a side effect is dealing with uniqueness in code | 18:08 |
raildo | notmorgan: ++ for soft deletes | 18:08 |
notmorgan | ayoung: just change what the delete means. | 18:08 |
bknudson | if I've kept a copy of the data (ID -> name) from before the delete I could use the ID to look up the name | 18:08 |
*** sudipto has quit IRC | 18:08 | |
raildo | (or whatever other name for this) | 18:08 |
gyee | dolphm, just display the resource ID in the screen? | 18:08 |
dolphm | verbose cadf vs soft deletes vs shadow tables: http://lbragstad.com/improving-auditing-in-keystone/ | 18:08 |
*** mtanino has joined #openstack-meeting | 18:08 | |
dolphm | gyee: ? | 18:08 |
notmorgan | please no shadow tables | 18:08 |
notmorgan | i'll take verbose cadf easily before that | 18:09 |
dolphm | notmorgan: that'd be an operator solution, not upstream | 18:09 |
rderose | notmorgan: ++ | 18:09 |
dolphm | notmorgan: operators can do that today | 18:09 |
ayoung | notmorgan, it was the term he used on the blog post | 18:09 |
notmorgan | dolphm: true.. but nova did that in their tree | 18:09 |
notmorgan | i don't want to see that replicated ;) | 18:09 |
stevemar | dolphm: from an implementation point of view, adding the names is the easiest of those 3 | 18:09 |
*** elopez has joined #openstack-meeting | 18:09 | |
dolphm | notmorgan: or maybe it's something we can document upstream as our recommended solution if you want those behaviors | 18:09 |
dstanek | notmorgan: what did they do? | 18:09 |
notmorgan | dstanek: they have all sorts of internal shadow tables for book keeping on deletes | 18:09 |
bknudson | who would have a problem with adding name to the audit payload? | 18:10 |
*** elopez is now known as Guest12814 | 18:10 | |
notmorgan | dstanek: accross services etc. | 18:10 |
stevemar | bknudson: presumably only keystone devs :P | 18:10 |
*** acoles is now known as acoles_ | 18:10 | |
dolphm | notmorgan: didn't know that, that sounds awful. are they using mongo? | 18:10 |
gyee | dolphm, when monitor system receiving an event which containing only resource ID, it has to make a call to Keystone to lookup the resource (if it still there) in order to display something that is *readable* | 18:10 |
lbragstad | well what if an operator doesn't want a particular attribute in the payload | 18:10 |
samueldmq | verbose notifications would be something configured in the config file right? | 18:10 |
notmorgan | easiest solution: verbose cadf, best solution don't delete the rows, worst of both worlds shadow tables | 18:10 |
*** salv-orl_ has quit IRC | 18:10 | |
lbragstad | and we put it in there | 18:10 |
samueldmq | somehting like configuring the log level | 18:10 |
samueldmq | notificaiton levle ? | 18:10 |
notmorgan | samueldmq: no. lets not do that | 18:10 |
*** uxdanielle has joined #openstack-meeting | 18:10 | |
dstanek | dolphm: doubt it, because they could use just a single 'audit' collection | 18:10 |
ayoung | you know what...I'm not really engaged in this. Any of the options would suffice by me | 18:10 |
notmorgan | samueldmq: please lets not add knobs to what is in notifications. | 18:10 |
shaleh | notmorgan: ++ | 18:10 |
dolphm | gyee: again, the use case your describing is user experience, not system auditing | 18:10 |
* stevemar thinks we should make cadf the default notification format | 18:11 | |
shaleh | I like soft deletes. It is kind of the norm really. | 18:11 |
*** jaugustine has quit IRC | 18:11 | |
shaleh | easier to ensure uniqueness too. | 18:11 |
*** salv-orlando has joined #openstack-meeting | 18:11 | |
stevemar | it's been ten minutes, doesn't seem like there's consensus here | 18:11 |
dstanek | if we just always put ids and names in the audit records would that satisfy 90% of the needs for more data? | 18:11 |
gyee | user experience matters | 18:11 |
*** jaugustine has joined #openstack-meeting | 18:11 | |
stevemar | dstanek: i think so | 18:11 |
*** salv-orlando has quit IRC | 18:11 | |
dolphm | notmorgan: ++ | 18:11 |
samueldmq | what is a notification ? is it supposed to only contain operation/entity_id ? | 18:11 |
shaleh | dstanek: I think so | 18:11 |
notmorgan | in fact i recommend adding name to cadf AND not deleteing rows | 18:12 |
*** liamji has quit IRC | 18:12 | |
*** salv-orlando has joined #openstack-meeting | 18:12 | |
*** dmorita has quit IRC | 18:12 | |
notmorgan | for different reasons | 18:12 |
shaleh | notmorgan: agreed on not deleting. | 18:12 |
notmorgan | but it would be the most complete solution | 18:12 |
stevemar | notmorgan: ++ | 18:12 |
notmorgan | so lets do that | 18:12 |
stevemar | *why not both* | 18:12 |
notmorgan | name first, not delete rows second | 18:12 |
stevemar | yep | 18:12 |
shaleh | ++ | 18:12 |
stevemar | rmizuno_: consider it approved | 18:12 |
samueldmq | so adding names for ALL entities right? | 18:12 |
bknudson | we'll just run lbragstad's performance tests with the change and see what the effect is. | 18:13 |
samueldmq | not just projects | 18:13 |
dolphm | why not full objects? because that's the next request | 18:13 |
gyee | for the second part, we need a more comprehensive resource lifecycle management framework | 18:13 |
dolphm | #slipperyslope | 18:13 |
stevemar | rmizuno_: please try to make the code so other resources can use it | 18:13 |
samueldmq | dolphm: ++ and their memory refs | 18:13 |
notmorgan | dolphm: because we wont delete the objects | 18:13 |
notmorgan | dolphm: to avoid that | 18:13 |
lbragstad | stevemar i would be in favor of having a single notification format... having configurable notification stuff is confusing | 18:13 |
stevemar | dolphm: we won't include the description too :P | 18:13 |
dolphm | bknudson: i don't think there is any messaging support in the benchmark | 18:13 |
notmorgan | dolphm: provide real lifecycle management on the resorces | 18:13 |
rmizuno_ | stevemar: ok | 18:13 |
rmizuno_ | thanks! all! | 18:13 |
dstanek | if we stop deleting rows we'll have to start enforcing rules in python that the db currently handles | 18:13 |
stevemar | lbragstad: i agree, as it stands now the 'audit' format is not default | 18:13 |
lbragstad | right | 18:14 |
shaleh | lbragstad: if we can come up with a minimal, sufficient format I am +1 to that | 18:14 |
samueldmq | if we're going to not delete rows, why not start with that | 18:14 |
samueldmq | instead of adding names -> stop dleeting rows ? | 18:14 |
stevemar | samueldmq: adding names is much easier to do | 18:14 |
samueldmq | let's do it right from the start :) | 18:14 |
raildo | it is not wrong adding names, it just simpler for now | 18:14 |
dolphm | dstanek: ++ :( | 18:15 |
samueldmq | stevemar: and after when we don't delete roles anymore, we won't be able to remove names from the events anymore | 18:15 |
notmorgan | dstanek: not really, the db can still handle it, it is just changing how we handle unique constraints | 18:15 |
*** Sukhdev has quit IRC | 18:15 | |
notmorgan | dstanek: i can show you the migrations for it. it isn't too terrible | 18:15 |
dstanek | notmorgan: how would you do that? | 18:15 |
*** shaohe_feng has quit IRC | 18:15 | |
notmorgan | dstanek: unique(deleted(notNull, Bool), delete_time(notNull, default=0) | 18:15 |
stevemar | we still have a lot on the agenda, can we discuss this in -keystone or in the patch? | 18:16 |
notmorgan | dstanek: add in name etc constraints | 18:16 |
samueldmq | stevemar: ++ | 18:16 |
*** shaohe_feng has joined #openstack-meeting | 18:16 | |
notmorgan | it basically means you unique on "not-deleted, and delete time 0, and <other thing>" | 18:16 |
notmorgan | and ids still remain unique | 18:16 |
notmorgan | dstanek: i'll go over it more with you post meeting | 18:16 |
notmorgan | (s) | 18:16 |
notmorgan | it's not that hard to do. | 18:16 |
stevemar | #topic Drop support for Driver Versioning | 18:16 |
*** openstack changes topic to "Drop support for Driver Versioning (Meeting topic: keystone)" | 18:16 | |
stevemar | rderose: ^ | 18:17 |
notmorgan | stevemar: just rubber stamp this. | 18:17 |
rderose | So the spec proposes dropping support for driver versioning. | 18:17 |
rderose | There is a maintenance/development burden, however small you think it is. | 18:17 |
rderose | I don't like our approach and question whether operators are actually benefiting from it. | 18:17 |
stevemar | i saw the ML post, but no one replied to it :( | 18:17 |
notmorgan | stevemar: no one seems to care [though i dislike not having a clear contract, i'm willing to go with the general community consensus] | 18:17 |
rderose | And to me it's not unreasonable to say, if you want to upgrade Openstack, you'll need to upgrade and test your custom drivers. That's it. | 18:17 |
dolphm | stevemar: i'd rather have some decisions than try to rush through a rediculously long agenda | 18:17 |
notmorgan | and i'm the reason for the original proposal. | 18:17 |
dstanek | notmorgan: we can have a clear contract without supporting old versions of it | 18:17 |
gyee | oh I love the terms "technical debt" | 18:18 |
notmorgan | dstanek: either not really a contract [or unchanging?] or need versioning | 18:18 |
*** singhj has joined #openstack-meeting | 18:18 | |
lbragstad | i imagine we would have to provide better documentation when interfaces change? | 18:18 |
ayoung | we did "delete means disable" for tokens for a long time | 18:18 |
bknudson | what's wrong the approach? | 18:18 |
stevemar | dolphm: fair enough, we can circle back to it. i'll drop my item | 18:18 |
henrynash_ | so my question is why do we think the answer is different today than we did 3 releases ago? | 18:18 |
bknudson | maybe we can fix the approach | 18:18 |
notmorgan | henrynash_: because fewer deployments run custom drivers now. iirc | 18:18 |
dstanek | henrynash_: i didn't actually like it then either | 18:19 |
*** ivc_ has quit IRC | 18:19 | |
notmorgan | i haven't heard of folks doing it in the last year | 18:19 |
*** epcim has quit IRC | 18:19 | |
henrynash_ | dstanek: I think we all felt it was a necessary evil | 18:19 |
notmorgan | it was much more prevalent when i proposed this | 18:19 |
ayoung | lets kill driver versioning and if people are doing customer drivers break them willy and nilly. | 18:19 |
bknudson | we'll likely wind up running a custom driver here. | 18:19 |
*** sarob has joined #openstack-meeting | 18:19 | |
amakarov | rderose, is this support is dropped immediately after spec merge or we still have to support versions and adapters in between for 2 releases? | 18:19 |
stevemar | bknudson: would keeping the versioned drivers make things easier for you? | 18:19 |
dolphm | henrynash_: the maintenance cost of the current approach is astronomical compared to the supposed benefit | 18:20 |
samueldmq | we should listen to deployers and take our decision to keep or not supporting it | 18:20 |
*** sarob has quit IRC | 18:20 | |
stevemar | amakarov: it would be 2 releases i think | 18:20 |
dolphm | samueldmq: deployers have not expressed any support on the mailing list either way | 18:20 |
notmorgan | samueldmq: i hear no deployers asking for it at this point | 18:20 |
notmorgan | previously there were a number | 18:20 |
bknudson | stevemar: I don't think the versioned drivers actually would help us much. | 18:20 |
notmorgan | dreamhost, hp, etc | 18:20 |
ayoung | the only way to find out who is using it is to remove it. For any value of *it* | 18:20 |
samueldmq | dolphm: notmorgan: so I fully support dropping support for custom drivers | 18:20 |
bknudson | we'll have to change our driver eventually so will likely just do it when we upgrade. | 18:20 |
samueldmq | maintanance costs are high | 18:20 |
notmorgan | samueldmq: no. | 18:20 |
bknudson | and write our own translation code. | 18:20 |
rderose | bknudson: for complicated drivers, "faking out" methods is difficult | 18:20 |
notmorgan | samueldmq: verioned drivers. | 18:21 |
amakarov | stevemar, so delegation driver adapters I'm working should still introduce new assignement and trust driver versions instead of just changing them? | 18:21 |
notmorgan | samueldmq: someone can still write a custom driver. | 18:21 |
stevemar | notmorgan: so why did hp & dreamhost change? | 18:21 |
notmorgan | stevemar: hp doesn't run a public cloud now. | 18:21 |
*** dmorita has joined #openstack-meeting | 18:21 | |
ayoung | dreamhost changed because I broken them | 18:21 |
notmorgan | stevemar: dreamhost moved to pure upstream. | 18:21 |
samueldmq | notmorgan: ok, so we keep supporting withouth the headache of versioning them | 18:21 |
notmorgan | stevemar: afaik | 18:21 |
ayoung | when we split ID into id and assignment. | 18:21 |
gyee | stevemar, I can't get us to contribute the mongodb driver, so I won't cry if we drop it | 18:21 |
samueldmq | notmorgan: yes that's what I MEANT | 18:21 |
ayoung | poort thingy | 18:21 |
notmorgan | samueldmq: basically | 18:21 |
jamielennox | the thing i like about the custom drivers is the backwards support from version to version. If we think we can do upgrade notes etc on drviers and deprecation periods etc then they're not needed - but historically we didn't | 18:21 |
samueldmq | notmorgan: ++ I support that | 18:21 |
ayoung | better to push for code going in upstream | 18:22 |
gyee | iSuck | 18:22 |
notmorgan | we could also just 2-cycle support the backend driver contract - no versions | 18:22 |
*** jamesmcarthur has joined #openstack-meeting | 18:22 | |
shaleh | jamielennox: good points | 18:22 |
samueldmq | let's create better docs about driver contract changes; and to be honet they're pretty good right now since we do release notes | 18:22 |
notmorgan | but as the original champion of this - i'm fine with it being dropped. i hear very few people [zero] asking for this now. | 18:22 |
bknudson | we don't really have a driver contract anyways. | 18:22 |
dolphm | samueldmq: we can't avoid driver contract changes... | 18:22 |
notmorgan | we aren't ironic, we aren't cinder with 3rd party drivers | 18:23 |
amakarov | ayoung, the problem I see, is we're saying: "You can write your own drivers with this interface which is subject to change anytime we please" | 18:23 |
bknudson | even the backends we supply now work differently in many cases | 18:23 |
stevemar | i'm OK with not creating any new drivers and removing the current versioned drivers when they have been deprecated | 18:23 |
samueldmq | dolphm: exactly, so let's just document the changes better (with release notes). and drop support for versioning | 18:23 |
notmorgan | amakarov: well not once release happens for a given cycle | 18:23 |
rderose | amakarov: basically notify in newton and remove in O | 18:23 |
notmorgan | amakarov: but if you're chasing master, do it at your own risk | 18:23 |
jamielennox | samueldmq: we lack the notes saying to upgrade you need to implement these functions and drop these others, with the versioning it's easy to see what you need to implement rather than scattered deprecation notices | 18:23 |
dolphm | samueldmq: oh, sure ++ | 18:23 |
gyee | samueldmq, the code is the document :-) | 18:23 |
notmorgan | we wont change [barring security issues etc] the backend interfaces on a given release. | 18:24 |
*** ivc_ has joined #openstack-meeting | 18:24 | |
raildo | gyee: the better way, always :D | 18:24 |
notmorgan | gyee: don't even joke about that :P | 18:24 |
dolphm | stable releases are stable, and that's never changed | 18:24 |
samueldmq | jamielennox: that info is available in the release notes, at least the ones I've seen from henrynash_ iirc | 18:24 |
bknudson | at this point the code is the document | 18:24 |
notmorgan | dolphm: ++ | 18:24 |
notmorgan | anyway. | 18:24 |
bknudson | since we don't document the interface. | 18:24 |
stevemar | i think we're all in agreement (except maybe henrynash_) ? | 18:24 |
jamielennox | but i've advocated before we should create a keystone/lib dir and treat it like a real library and put in there anything that is supposed to be consumed from others | 18:24 |
samueldmq | knikolla: we can do that with release notes pretty easily | 18:24 |
notmorgan | genral consensus - drop it? | 18:24 |
samueldmq | vote ? | 18:24 |
notmorgan | and document better? | 18:24 |
dstanek | notmorgan: drop & doc! | 18:25 |
henrynash_ | stevemar: I’m just leary of removing something we thought was important with zero input from deployers | 18:25 |
dolphm | dstanek: ++ | 18:25 |
shaleh | do what jamielennox is proposing | 18:25 |
gyee | I don't always agree with dstanek, but not this time | 18:25 |
stevemar | samueldmq: i think henrynash_ is the only one on the fence | 18:25 |
samueldmq | stevemar: notmorgan: should we vote? shoud be quick | 18:25 |
ayoung | amakarov, I've never said that. I always saw driver as internal code | 18:25 |
raildo | and who will do this? rderose? :D | 18:25 |
dolphm | henrynash_: we asked for input, we heard crickets | 18:25 |
notmorgan | dolphm: ++ | 18:25 |
rderose | raildo: dstanek: volunteered | 18:25 |
henrynash_ | I’ll certainly support the consenus | 18:26 |
*** shaohe_feng has quit IRC | 18:26 | |
ayoung | lets hold off on removing versioned drivers until after the next summit, and get it before the operators | 18:26 |
*** lpetrut has joined #openstack-meeting | 18:26 | |
samueldmq | henrynash_: let's senf an email notifying the decision | 18:26 |
amakarov | ayoung, and we expose 'driver' parameter to config for people to override it | 18:26 |
raildo | rderose: dstanek awesome :) | 18:26 |
ayoung | its probably just busy work, but we have committed to it | 18:26 |
samueldmq | they will say something if they disagree | 18:26 |
notmorgan | and everyone who has complained to me previously have stopped doing custom drivers as i know | 18:26 |
samueldmq | at least this time :) | 18:26 |
dstanek | the question is whether we just drop all support of honor the existing contracts for a release | 18:26 |
henrynash_ | dolphm: which meant they weren;t listeneing, didn’t get the question or don’t care…but we don;t know which | 18:26 |
ayoung | amakarov, I just saw that as a way to switch between existing ones in tree | 18:26 |
shaleh | dstanek: honor for at least a release | 18:26 |
dolphm | #info gyee doesn't always agree with dstanek, but not this time | 18:26 |
gyee | hahah | 18:26 |
*** shaohe_feng has joined #openstack-meeting | 18:26 | |
shaleh | as ayoung says, we do not really know what is out there | 18:26 |
amakarov | ayoung, anyway, whoever customizes driver get a maintainance problem, and it's his problem :) | 18:27 |
stevemar | #startvote drop version driver support? Yes, No | 18:27 |
openstack | Begin voting on: drop version driver support? Valid vote options are Yes, No. | 18:27 |
openstack | Vote using '#vote OPTION'. Only your last vote counts. | 18:27 |
notmorgan | announce the versions go away in O | 18:27 |
samueldmq | #vote Yest | 18:27 |
openstack | samueldmq: Yest is not a valid option. Valid options are Yes, No. | 18:27 |
samueldmq | #vote Yes | 18:27 |
bknudson | #vote Yes | 18:27 |
rderose | Yes | 18:27 |
samueldmq | oops | 18:27 |
notmorgan | #vote idontcare | 18:27 |
openstack | notmorgan: idontcare is not a valid option. Valid options are Yes, No. | 18:27 |
amakarov | #vote yes | 18:27 |
stevemar | #vote yes | 18:27 |
ayoung | wait...when? | 18:27 |
rderose | #vote yes | 18:27 |
dolphm | #vote Yes | 18:27 |
shaleh | #vote later | 18:27 |
openstack | shaleh: later is not a valid option. Valid options are Yes, No. | 18:27 |
henrynash_ | #vote no | 18:27 |
ayoung | I want to do so eventually | 18:27 |
lbragstad | #vote yes | 18:27 |
jamielennox | #vote yes | 18:27 |
ayoung | is a yes vot for dropping immediately? | 18:27 |
raildo | #vote yes | 18:27 |
rodrigods | #vote yes | 18:27 |
dstanek | #vote more_yes_than_yes | 18:27 |
openstack | dstanek: more_yes_than_yes is not a valid option. Valid options are Yes, No. | 18:27 |
dolphm | #viteinfo | 18:27 |
samueldmq | dstanek: heh | 18:27 |
dstanek | #vote yes | 18:27 |
dolphm | #voteinfo | 18:27 |
notmorgan | dolphm: VITEINFO! | 18:27 |
stevemar | ayoung: yes means we just don't create new ones, and let the exisitng ones deprecate | 18:27 |
browne | #vote yes | 18:27 |
ayoung | #vote yes | 18:27 |
knikolla | #vote yes | 18:28 |
nisha_ | #vote yes | 18:28 |
jamielennox | but i want to say there's really no rush to this | 18:28 |
dolphm | #showvote | 18:28 |
openstack | Yes (15): rodrigods, nisha_, lbragstad, ayoung, rderose, bknudson, browne, dstanek, samueldmq, jamielennox, knikolla, amakarov, dolphm, raildo, stevemar | 18:28 |
openstack | No (1): henrynash_ | 18:28 |
stevemar | #endvote | 18:28 |
openstack | Voted on "drop version driver support?" Results are | 18:28 |
openstack | Yes (15): rodrigods, nisha_, lbragstad, ayoung, rderose, bknudson, browne, dstanek, samueldmq, jamielennox, knikolla, amakarov, dolphm, raildo, stevemar | 18:28 |
openstack | No (1): henrynash_ | 18:28 |
henrynash_ | (someone’s gotta stand out from the crowd) | 18:28 |
rderose | :) | 18:28 |
shaleh | henrynash_: ++ | 18:28 |
bknudson | he's a wild duck. | 18:28 |
dstanek | if people end up not liking this then we can always start creating new versions | 18:28 |
stevemar | rderose: interpret what you may from the results :) | 18:28 |
samueldmq | nice, I think we can discuss about how we do it in -keystone | 18:28 |
*** jprovazn has quit IRC | 18:28 | |
stevemar | dstanek: lol | 18:28 |
henrynash_ | ok, done…next topic! | 18:28 |
rderose | stevemar: ++ what, you mean henry hates me now | 18:28 |
shaleh | I just feel like wearing Monty's hat and saying operators might be bitten if we act too quickly | 18:28 |
stevemar | henrynash_: actually... i'm going to circle back to the previous one | 18:29 |
rderose | henry: beer is on me at mid | 18:29 |
stevemar | #topic Add resource name to the notification event | 18:29 |
*** openstack changes topic to "Add resource name to the notification event (Meeting topic: keystone)" | 18:29 | |
notmorgan | shaleh: you should invoke mordred when putting on his hat | 18:29 |
gyee | rderose, do pay attention to who's walking behind you on the next summit | 18:29 |
henrynash_ | redose: as the person who ended writing nealy all teh bl**dy wrappers, no I’m happy (in a perverse way!) | 18:29 |
stevemar | let's get a concrete action item out of this | 18:29 |
dolphm | rderose: follow up on your mailing list post with the outcome of this meeting | 18:29 |
stevemar | dolphm: good call | 18:29 |
rderose | dolphm: will do | 18:29 |
*** baoli_ has quit IRC | 18:29 | |
stevemar | so back to the whole names in audit events thing | 18:30 |
notmorgan | shaleh: (though i think he's in meetings all day) | 18:30 |
*** hasharOut has quit IRC | 18:30 | |
*** harlowja has quit IRC | 18:30 | |
shaleh | notmorgan: yeah... | 18:30 |
samueldmq | dolphm: ++ | 18:30 |
rderose | gyee: ++ | 18:30 |
*** iyamahat has joined #openstack-meeting | 18:30 | |
stevemar | i'm ok with adding the resource name and domain name | 18:30 |
rderose | henrynash: ++ | 18:30 |
shaleh | stevemar: a) add names now b) move towards soft deletes | 18:30 |
notmorgan | shaleh: ++ | 18:30 |
samueldmq | shaleh: ++ | 18:30 |
gyee | ++ | 18:30 |
stevemar | dolphm, you seem concerned | 18:30 |
samueldmq | maybe we should vote again ? :-) | 18:30 |
notmorgan | shaleh: but can we never call them "soft deletes" again ;) | 18:31 |
*** jaugustine has quit IRC | 18:31 | |
notmorgan | shaleh: just call them "deletes" ;) | 18:31 |
dolphm | stevemar: i'm in favor of A, with the caveat that names are not unique across domains, and we're not including domain references | 18:31 |
samueldmq | I think we should go to b) from now, that shouldn't be a hurry to add the name | 18:31 |
*** rbowen has quit IRC | 18:31 | |
dolphm | stevemar: so i'm inclined to suggest we should just dump the full object into the cadf payload | 18:31 |
gyee | samueldmq, b) is quite a bit of work | 18:31 |
lbragstad | dolphm so keeping the notification payload reasonably sized, right? | 18:31 |
dolphm | lbragstad: not necessarily lol | 18:31 |
samueldmq | gyee: can't be done in this release or next ? | 18:31 |
*** jaugustine has joined #openstack-meeting | 18:32 | |
jamielennox | i'm ok with adding names, with all the regular caveats that names can change and you should be storing ids | 18:32 |
notmorgan | gyee: it really isn't that much work. - also it buys us the "restore a deleted resource" option w/o needing magic "inject data into the db" commands | 18:32 |
samueldmq | gyee: in worst case it will get in next cycle (1 release after the name can be added) | 18:32 |
notmorgan | for free. | 18:32 |
shaleh | jamielennox: if we log BOTH it is better than just ids | 18:32 |
gyee | samueldmq, not this release I don't think, but miracle do happen | 18:32 |
jamielennox | notmorgan: it's always the API that bugs me about that, how do you request a deleted project? | 18:32 |
*** ssalagame has joined #openstack-meeting | 18:32 | |
*** harlowja has joined #openstack-meeting | 18:32 | |
raildo | we will still with name + id right? so this will be a unique combination across domains | 18:32 |
stevemar | dolphm: by "not including domain references" you mean the entire domain ref, we still need the domain name | 18:32 |
notmorgan | jamielennox: same way as with nova ?deleted=true | 18:32 |
jamielennox | shaleh: yes, logging both is fine | 18:32 |
shaleh | notmorgan: ++ | 18:32 |
bknudson | the project was deleted, not the domain, so we only need the domain ID | 18:33 |
gyee | normorgan, that's not lifecycle managment, just a delete hack | 18:33 |
samueldmq | /v3/projects/<id>?RESSURRECT | 18:33 |
notmorgan | gyee: no it allows us to do lifecycle management | 18:33 |
notmorgan | gyee: right now... we don't really have that option | 18:33 |
shaleh | IFF IDS <-> mapping live forever we can just log IDs | 18:33 |
dstanek | jamielennox: not only that what if a project already exists with the deleted name... | 18:33 |
notmorgan | short of a custom driver. | 18:33 |
rderose | samueldmq: ++ | 18:33 |
*** vishnoianil has joined #openstack-meeting | 18:33 | |
shaleh | until then we need both | 18:33 |
dolphm | stevemar: i do just mean the flat ref | 18:33 |
notmorgan | dolphm: i'm actually ok with just shoving all relevant data in cadf. | 18:33 |
ayoung | we have a lot more to discuss and we are half done | 18:34 |
notmorgan | dolphm: if we don't blow out a maximum size | 18:34 |
dolphm | stevemar: if the domain hasn't changed, you can cache your GET /domains/{domain_id} call | 18:34 |
stevemar | dolphm: the flat ref will have the domain_id in there, that's good enough for me | 18:34 |
ayoung | Perf, use requests, name constraints | 18:34 |
ayoung | Swift ACLs | 18:34 |
jamielennox | dstanek: notmorgan has explained his uniqueness theory before, it's a bit twisty but it would work | 18:34 |
notmorgan | ayoung: swift ACLs should just be a "go read the ML thread and comment" | 18:34 |
samueldmq | should we vote ? or is it just me wanting to do the delete thing now ? | 18:34 |
notmorgan | samueldmq: no | 18:34 |
jamielennox | no soft delete now | 18:34 |
shaleh | soft delete is step 2 | 18:34 |
notmorgan | just do the name thing. | 18:35 |
stevemar | i think we're OK now, dolph -- you good? | 18:35 |
*** e0ne has joined #openstack-meeting | 18:35 | |
gyee | our resource objects arn't that big | 18:35 |
ayoung | step 3 is profit? | 18:35 |
shaleh | ayoung: always | 18:35 |
stevemar | flat ref in the notification? | 18:35 |
dolphm | stevemar: are we saying no to soft deletes in the application layer, then? | 18:35 |
notmorgan | the change on how deletes are handled (don't call it "soft deletes") should be a proposed spec for O release ( shaleh you should write this) | 18:35 |
stevemar | dolphm: ^ | 18:35 |
notmorgan | dolphm: today. i want a spec for O on this | 18:35 |
notmorgan | not in newton | 18:35 |
notmorgan | not worth it | 18:35 |
stevemar | right | 18:35 |
notmorgan | too short of time | 18:35 |
jamielennox | notmorgan: you can fight this all you like and implement it how you like - but the concept is what people refer to as soft deletes | 18:36 |
notmorgan | jamielennox: shhhhhhh | 18:36 |
*** shaohe_feng has quit IRC | 18:36 | |
dolphm | i'm okay with saying no to soft deletes later then :P | 18:36 |
samueldmq | notmorgan: my concern is that we add name/domain-name now and that won't be removed we support those deletes | 18:36 |
samueldmq | next cycle | 18:36 |
stevemar | dolphm: lol | 18:36 |
samueldmq | notmorgan: s/we/when | 18:36 |
notmorgan | dolphm: i think we should do it for the main resources that "own" things, but that is a case to be made in the spec. | 18:36 |
stevemar | dolphm: alright, next topic? is this horse dead enough? | 18:36 |
*** shaohe_feng has joined #openstack-meeting | 18:36 | |
dolphm | (i'm not entirely opposed to soft deletes, i'm just used to letting the db handle them) | 18:36 |
notmorgan | dolphm: not *all* resources. | 18:36 |
ayoung | Horse has been turned int dogfood and glue | 18:37 |
notmorgan | dolphm: and also i want the DB to handle most all of it still. ftr. | 18:37 |
dolphm | or *something* else besides the app | 18:37 |
stevemar | #topic Performance testing is available | 18:37 |
*** openstack changes topic to "Performance testing is available (Meeting topic: keystone)" | 18:37 | |
stevemar | lbragstad: you've got 3 minutes :P | 18:37 |
notmorgan | i'll work with shaleh to make the spec clear on that. | 18:37 |
ayoung | Perf testing of what? | 18:37 |
stevemar | i'm kidding | 18:37 |
lbragstad | well this is going to be short | 18:37 |
lbragstad | it's there, you can use it | 18:37 |
lbragstad | but im interested in feedback | 18:37 |
shaleh | lbragstad: this is a great start | 18:37 |
lbragstad | https://github.com/lbragstad/keystone-performance | 18:37 |
bknudson | we could use updates to the developer docs to say how to use this | 18:37 |
notmorgan | lbragstad: does it make sense to move into gerrit? | 18:37 |
notmorgan | my only question | 18:37 |
notmorgan | but awesome work | 18:38 |
lbragstad | notmorgan good question, maybe at some point | 18:38 |
gyee | lbragstad, nice handwriting! | 18:38 |
lbragstad | but right now I for sure what to improve things and make the whole system a bit better before moving it into gerrit | 18:38 |
raildo | lbragstad: thanks to be working on it! awesome work :) | 18:38 |
rderose | lbragstad: awesome | 18:38 |
lbragstad | so - feel free to use it, but it is only running on a single node | 18:38 |
lbragstad | so don't add 'check performance' to every patch in review | 18:38 |
stevemar | lbragstad: so it's the same machine every time? | 18:39 |
lbragstad | yes | 18:39 |
* notmorgan makes a bot for that | 18:39 | |
lbragstad | using containers as the app node | 18:39 |
notmorgan | lbragstad: did you get a proper 3rd party ci account? | 18:39 |
lbragstad | yes | 18:39 |
notmorgan | ok cool | 18:39 |
lbragstad | it's call the 'OSIC Performance Bot' | 18:39 |
samueldmq | how's that different from rally ? | 18:39 |
lbragstad | because I can't name things for crap | 18:39 |
lbragstad | it's running on dedicated hardware | 18:39 |
notmorgan | samueldmq: a lot of history, lets not cover that here | 18:40 |
jamielennox | samueldmq: much more focused on the hot path we care about | 18:40 |
* samueldmq nods | 18:40 | |
lbragstad | if you have specific questions, please ask | 18:40 |
lbragstad | but I'd like to try and get this improved and exposed to a bunch of feedback this release | 18:40 |
stevemar | lbragstad: so how do i invoke the perf tests on a given patch? | 18:40 |
shaleh | read the docs stevemar | 18:40 |
lbragstad | leave a comment with 'check performance' | 18:41 |
ayoung | cool | 18:41 |
lbragstad | in the message | 18:41 |
henrynash_ | nice | 18:41 |
stevemar | shaleh: i did, i was just trying to force lbragstad to write it out in the meeting for everyone's convenience | 18:41 |
*** Leo_ has joined #openstack-meeting | 18:41 | |
shaleh | stevemar: :-) | 18:41 |
stevemar | ;) | 18:41 |
stevemar | lbragstad: awesome stuff | 18:41 |
samueldmq | stevemar: shaleh :-) | 18:41 |
henrynash_ | hey siri…check... | 18:41 |
bknudson | write a bitcoin miner and recheck performance. | 18:41 |
gyee | lbragstad, so benchmark spit out a html/pdf report? | 18:41 |
lbragstad | i've also tried to add a bunch of docs about the infra. | 18:41 |
stevemar | so, let's use it ! | 18:42 |
lbragstad | so - open issues if you find anything is missing | 18:42 |
stevemar | thanks lbragstad | 18:42 |
lbragstad | or want to see enhancements, | 18:42 |
bknudson | this is great | 18:42 |
lbragstad | no problem. | 18:42 |
knikolla | awesome work! | 18:42 |
lbragstad | PRs welcome | 18:42 |
lbragstad | :_ | 18:42 |
stevemar | next topic jamielennox | 18:42 |
bknudson | I've been looking at performance problems for a couple weeks now. | 18:42 |
lbragstad | :) | 18:42 |
stevemar | #topic Use a request object in keystone | 18:42 |
*** openstack changes topic to "Use a request object in keystone (Meeting topic: keystone)" | 18:42 | |
jamielennox | ok, i'll keep this quick | 18:42 |
jamielennox | #link https://review.openstack.org/#/c/318658/ | 18:42 |
ayoung | what is the difference between a request and a context | 18:42 |
bknudson | what's the performance impact of using a request object in keystone? | 18:42 |
stevemar | bknudson: leave a comment on the patch and see :O | 18:43 |
ayoung | bknudson, premature optimization... | 18:43 |
shaleh | stevemar: ++ | 18:43 |
jamielennox | so we've passed around this weird dict of context forever now and it results in all this checking whether things are in the dict or not and making guesses | 18:43 |
* notmorgan checks performance on all the patches! | 18:43 | |
jamielennox | particularly given we end up passing the environment around everywhere in that dict anyway | 18:43 |
notmorgan | jamielennox: i like using the real request objects | 18:44 |
jamielennox | we need to integrate better with oslo.context and the objects passed down out of auth_token middleware | 18:44 |
ayoung | its better organization, I'll admit. Do we need to structure things more than just "request has a context dict" over time? | 18:44 |
bknudson | doesn't every openstack app pass around a dict of context? | 18:44 |
ayoung | and if so, what doe the end state look like? | 18:44 |
jamielennox | so instead of just adding more crap to the dict i want to use real objects - with properties and stuff for attributes we care about | 18:44 |
notmorgan | bknudson: somewhat, but a lot of it is now centralized in oslo_context (thread local things) | 18:44 |
dstanek | jamielennox: as long as request objects don't bleed lower than the controllers, then i'm on board | 18:44 |
ayoung | https://tomcat.apache.org/tomcat-5.5-doc/servletapi/javax/servlet/http/HttpServletRequest.html | 18:44 |
samueldmq | notmorgan: couldn't we just use oslo.context then ? | 18:44 |
bknudson | we've got a oslo_context.RequestContext (was added for request ID) | 18:44 |
notmorgan | bknudson: and we use it for the request_local caching too | 18:45 |
jamielennox | so this patch is kind of big because it has to do a lot of router/controller level stuff in one go, but things beyond that should be normal review size again | 18:45 |
*** salv-orlando has quit IRC | 18:45 | |
ayoung | the general pattern in Servlet programming was that you only read from the request, and write new data tothe response | 18:45 |
notmorgan | bknudson: so we could just use oslo_context | 18:45 |
jamielennox | dstanek: i see no reason for them to go futher than context does now | 18:45 |
amakarov | samueldmq, it will add even more spagetti code | 18:45 |
ayoung | and state was saved ewither in the session (which we have none) and the database | 18:45 |
dstanek | jamielennox: +2 from me then | 18:45 |
*** sdague has quit IRC | 18:46 | |
ayoung | so...why only a request object, and not a response? | 18:46 |
stevemar | i'm OK with it, i always found the way we pass the context around a bit weird | 18:46 |
*** salv-orlando has joined #openstack-meeting | 18:46 | |
samueldmq | amakarov: so other openstack projects adoption oslo.context are making spaghetti code ? | 18:46 |
dstanek | samueldmq: yes | 18:46 |
*** shaohe_feng has quit IRC | 18:46 | |
amakarov | samueldmq, I think so | 18:46 |
ayoung | yeah....jamie this is long overdue | 18:46 |
*** toddjohn has quit IRC | 18:46 | |
*** lifeless has quit IRC | 18:46 | |
jamielennox | anyway, i want to make it so that everyone knew about this and there are a number of conflicting reviews so i would like to get this merged if we all agree | 18:46 |
dolphm | ayoung: next step? | 18:46 |
samueldmq | jamielennox: ++ | 18:47 |
*** rbowen has joined #openstack-meeting | 18:47 | |
stevemar | henrynash_: you'll have the rest of the time for your topic | 18:47 |
jamielennox | ayoung: because ATM i need more access to the inputs and haven't had to worry about the writing | 18:47 |
*** shaohe_feng has joined #openstack-meeting | 18:47 | |
stevemar | jamielennox: sounds good | 18:47 |
henrynash_ | stevemar: thx | 18:47 |
stevemar | jamielennox: sounds like everyone is okay with it | 18:47 |
*** lifeless has joined #openstack-meeting | 18:47 | |
jamielennox | ayoung: but i'm silently keen to change up all the routers as well one day | 18:47 |
ayoung | its a start | 18:47 |
*** ekcs has quit IRC | 18:47 | |
dolphm | jamielennox: flask? | 18:47 |
ayoung | I want a proper token/auth-data pipeline | 18:48 |
notmorgan | dolphm: ++ | 18:48 |
stevemar | next topic coming up | 18:48 |
notmorgan | dolphm: yes flask! | 18:48 |
dolphm | brace yourselves | 18:48 |
stevemar | #topic Project name constraints & project hierarchical naming | 18:48 |
*** openstack changes topic to "Project name constraints & project hierarchical naming (Meeting topic: keystone)" | 18:48 | |
jamielennox | dolphm: i looked and it's just a massive change that requires rewriting all the protected stuff | 18:48 |
henrynash_ | ok | 18:48 |
stevemar | brace yourselves is right | 18:48 |
jamielennox | dolphm: this at least gets us to request objects which is a step in the direction | 18:48 |
* stevemar sits back and grabs popcorn | 18:48 | |
dolphm | jamielennox: ++ | 18:48 |
raildo | stevemar: lol | 18:48 |
henrynash_ | so we;ve been hashing this one around a while | 18:48 |
dolphm | stevemar: scoot over | 18:48 |
dstanek | jamielennox: take a look at my flask patch - it wasn't terrible to do | 18:48 |
* notmorgan has nothing else to add that isn't on the ML/talked with henrynash_ directly | 18:48 | |
henrynash_ | (more accurately morgan has been knockig holes in various suggestions!) | 18:49 |
* gyee is comfortable numb | 18:49 | |
stevemar | https://media.giphy.com/media/qR6UR8K1Ia2BO/giphy.gif | 18:49 |
henrynash_ | latest incarnation is https://review.openstack.org/#/c/318605/ | 18:49 |
henrynash_ | which goes for the “make project name the path” approach | 18:49 |
shaleh | are we gonna -2 this or not? Is there anything left to say? | 18:49 |
*** sarob has joined #openstack-meeting | 18:50 | |
amakarov | dstanek, for me flask is better than the pylons legacy we call routers now :) | 18:50 |
stevemar | i'll admit i haven't read the latest ML posts | 18:50 |
henrynash_ | as described, I think this does not allow us to maintain compatibility with v3.6 clients and before | 18:50 |
ayoung | henrynash_, we can't config value our way out of this hole? | 18:50 |
notmorgan | ayoung: not really | 18:51 |
dstanek | amakarov: i'm going to bring back that patch | 18:51 |
stevemar | henrynash_: did someone poke a hole in clint's suggestion? name and basename? | 18:51 |
*** ekcs has joined #openstack-meeting | 18:51 | |
notmorgan | stevemar: doesn | 18:51 |
stevemar | it seemed the least breaky to me | 18:51 |
*** pabelanger has joined #openstack-meeting | 18:51 | |
gyee | what's stopping V4? | 18:51 |
notmorgan | solve the unique name constraing in 3.6 | 18:51 |
dolphm | stevemar: isn't that eventually backwards incompatible? | 18:52 |
notmorgan | stevemar: unless you never expect post 3.7 projects to 3.6 | 18:52 |
*** jmills_nasa has joined #openstack-meeting | 18:52 | |
henrynash_ | stevemar: so I articulated the compatibilit requiremenets in a reponse on the mailing list, I don’t see how we maintain 3.6 cleints | 18:52 |
notmorgan | expose* | 18:52 |
notmorgan | dolphm: yes. | 18:52 |
dolphm | well, then, hole poked. | 18:52 |
henrynash_ | with that approacj | 18:52 |
stevemar | dolphm: very much so | 18:52 |
notmorgan | dolphm: it was the same hole i poked in removing 3.6 at all | 18:52 |
amakarov | gyee, we haven't dragged OpenStack from v3 to v3 yet, and now you want to announce v4? People will linch us! | 18:52 |
stevemar | amakarov: also true | 18:53 |
amakarov | s/v3/v2/ | 18:53 |
henrynash_ | no v4 required | 18:53 |
rderose | amakarov: ++ | 18:53 |
henrynash_ | so two questions for y’all to ponder: | 18:53 |
*** e0ne has quit IRC | 18:53 | |
*** mrmartin has joined #openstack-meeting | 18:53 | |
notmorgan | henrynash_: "full name" also might be a good attr instead of "path" ? | 18:53 |
notmorgan | henrynash_: side thought. | 18:53 |
samueldmq | that's all because we hadn't the full roadmap when we first implemneted hierarchical projects :( | 18:53 |
notmorgan | henrynash_: but that is bike-shedding | 18:53 |
samueldmq | :( | 18:53 |
henrynash_ | 1) Since this is the only cure we could come up with (that maintains compatility), is the cure still worse than the disease? | 18:54 |
notmorgan | samueldmq: even if we had, we'd have broken a TON of people | 18:54 |
notmorgan | samueldmq: and it would still be a no-go | 18:54 |
ayoung | I can't keep track of the objections and the counter solutions | 18:54 |
notmorgan | i strongly believe that the reseller case is better with domains | 18:54 |
henrynash_ | 2) (much more minor) severel questions on consistency in the current proposal (e.g. should you be abel to use name including a path on create project) | 18:54 |
notmorgan | and de-uniquing the names in a given domain doesn't provide a lot on that front | 18:54 |
samueldmq | notmorgan: maybe it wouldn't break that much if we made hierarchical project experimental and come with this in the next cycle | 18:55 |
samueldmq | notmorgan: but nevermind, let's solve what we have today | 18:55 |
notmorgan | samueldmq: it breaks auth | 18:55 |
notmorgan | samueldmq: that is the issue. | 18:55 |
ayoung | we could go with ldap style naming "domain=pepsi,project_name=top,project_name=middle" | 18:55 |
dolphm | (let's not break auth) | 18:55 |
samueldmq | notmorgan: because root projects now have a parent (is_domain ?) | 18:55 |
amakarov | henrynash_, closure table can be used to identify projects without unique naming and storing full path in the name | 18:55 |
notmorgan | ayoung: thats basically what i've proposed, just with / instead | 18:55 |
ayoung | sorry, we need to make that longer | 18:55 |
ayoung | we could go with ldap style naming "domain_name=pepsi,project_name=top,project_name=middle" | 18:55 |
*** adiantum has joined #openstack-meeting | 18:55 | |
notmorgan | samueldmq: i'll go over that outside of here | 18:55 |
*** nisha_ has quit IRC | 18:55 | |
ayoung | so "domain_name=pepsi/project_name=top/project_name=middle" | 18:56 |
gyee | ayoung, UX people will look for ya | 18:56 |
jamielennox | ayoung: no, never | 18:56 |
*** zhonghua has joined #openstack-meeting | 18:56 | |
stevemar | yeesh | 18:56 |
henrynash_ | OK, back to the question | 18:56 |
notmorgan | ayoung: that is effectively my proposal fwow, but was domain/px/py/pz | 18:56 |
amakarov | ayoung, let's writhe our own LDAP! | 18:56 |
ayoung | jamielennox, scared at how quick people take me seriously | 18:56 |
shaleh | ayoung: that is too convenient. Make it more cumbersom please | 18:56 |
bknudson | what if my name was domain_name=pepsi/project_name=top ? | 18:56 |
notmorgan | ayoung: since domains are always the root. | 18:56 |
amakarov | write | 18:56 |
ayoung | shaleh, XML? | 18:56 |
jamielennox | ayoung: this was erring on the side of caution | 18:56 |
*** shaohe_feng has quit IRC | 18:56 | |
ayoung | heh | 18:56 |
shaleh | ayoung: good start | 18:56 |
henrynash_ | Assuming you agree that we CAN solve this, without breaking compatibility (as per the current poposal https://review.openstack.org/#/c/318605/), is this worth doing | 18:57 |
*** zhonghua has quit IRC | 18:57 | |
*** shaohe_feng has joined #openstack-meeting | 18:57 | |
ayoung | so OS_PROJECT_NAME="domain/pepsi/top/middle" would work for scoping a token | 18:57 |
ayoung | henrynash_, oh yes it is | 18:57 |
amakarov | henrynash_, we don't need it: https://review.openstack.org/#/c/285521/ | 18:57 |
*** prometheanfire has joined #openstack-meeting | 18:57 | |
henrynash_ | ayoung: yes (although with a leading /) | 18:57 |
*** toddjohn has joined #openstack-meeting | 18:57 | |
gyee | yes we can, lets make it great again, a future we believe in | 18:58 |
*** sarob has quit IRC | 18:58 | |
ayoung | OS_PROJECT_NAME="/domain/pepsi/top/middle" would work for scoping a token | 18:58 |
amakarov | henrynash_, do you want materialized path with names? | 18:58 |
henrynash_ | ayoungL yes | 18:58 |
henrynash_ | amakaraov: implmentation detail | 18:58 |
notmorgan | ayoung: that would be the idea. it would match "name" or "path" | 18:58 |
ayoung | henrynash_, and what hoops do we need to jump throughto get there | 18:58 |
notmorgan | ayoung: in the case of old projects. | 18:58 |
notmorgan | ayoung: since some projects might be "ProjectName" only | 18:58 |
stevemar | this is getting nasty | 18:58 |
stevemar | voice opinions on the ML or https://review.openstack.org/#/c/318605/ (or both) | 18:59 |
ayoung | notmorgan, /domain becomes a reserved project name? | 18:59 |
notmorgan | stevemar: i don't think we need this, but i offered an alternative when i poked holes in it | 18:59 |
jamielennox | so, i don't know how to say this better - but it's just not nice | 18:59 |
ayoung | not allowed as either project or domain, or as the start of either? | 18:59 |
notmorgan | ayoung: no /<domainname>/<projextName>/<otherProject> | 18:59 |
stevemar | notmorgan: that's my next question, do we need this? | 18:59 |
amakarov | colleagues, closure table will allow to address project by path, index hierarchies, and leave project name be | 18:59 |
stevemar | but we're at time... | 18:59 |
notmorgan | stevemar: i don't think we need it. but there is a ux concern | 18:59 |
stevemar | to -keystone | 18:59 |
notmorgan | some orgs want /domain/acc/dev | 19:00 |
ayoung | notmorgan, so first link is alwyas domain? | 19:00 |
stevemar | thanks to everyone for joining | 19:00 |
notmorgan | and /domain/ops/dev | 19:00 |
stevemar | #endmeeting | 19:00 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 19:00 | |
openstack | Meeting ended Tue Jun 14 19:00:15 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 19:00 |
notmorgan | ayoung: is always *a* domain | 19:00 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-06-14-18.00.html | 19:00 |
samueldmq | stevemar: thanks | 19:00 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-06-14-18.00.txt | 19:00 |
openstack | Log: http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-06-14-18.00.log.html | 19:00 |
fungi | infra team, i summon thee | 19:00 |
*** shaleh has left #openstack-meeting | 19:00 | |
pleia2 | o/ | 19:00 |
* jeblair lurches in | 19:00 | |
clarkb | hello | 19:00 |
notmorgan | ayoung: since we know it is always _KeystoneRoot/<domain>/<poroject> | 19:00 |
crinkle | o/ | 19:00 |
fungi | topics proposed by pabelanger, crinkle, zaro | 19:00 |
* notmorgan stops talking keystone here | 19:00 | |
notmorgan | o/ | 19:00 |
pabelanger | beep boop | 19:00 |
SotK | o/ | 19:01 |
zaro | o/ | 19:01 |
aimeeu | o/ | 19:01 |
docaedo | o/ | 19:01 |
ianw | o/ | 19:01 |
prometheanfire | o/ | 19:01 |
Zara | o/ | 19:01 |
*** zhonghua has joined #openstack-meeting | 19:01 | |
*** jamielennox has left #openstack-meeting | 19:02 | |
*** toddjohn has quit IRC | 19:02 | |
notmorgan | The role of OpenStack Proposal Bot will be played by pabelanger today :P | 19:02 |
fungi | #startmeeting infra | 19:02 |
openstack | Meeting started Tue Jun 14 19:02:43 2016 UTC and is due to finish in 60 minutes. The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot. | 19:02 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 19:02 |
*** openstack changes topic to " (Meeting topic: infra)" | 19:02 | |
openstack | The meeting name has been set to 'infra' | 19:02 |
fungi | #link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting | 19:03 |
fungi | #topic Announcements | 19:03 |
*** openstack changes topic to "Announcements (Meeting topic: infra)" | 19:03 | |
*** amakarov is now known as amakarov_away | 19:03 | |
fungi | #info CI outage Friday, June 17 for ~2 hours so we can upgrade the operating system for zuul.openstack.org and logs.openstack.org, time TBD | 19:03 |
fungi | pabelanger: did you have an announcement worked up for that yet? (sent?) | 19:03 |
pabelanger | fungi: no, I have not. Apologies. I will do that now | 19:03 |
pabelanger | an etherpad link I mean | 19:03 |
rcarrillocruz | o/ | 19:03 |
fungi | i wpn't #action it, since the window is prior to next meeting anyway | 19:04 |
*** dmorita has quit IRC | 19:04 | |
pabelanger | agreed | 19:04 |
fungi | also rehashed from last week's announcements for those who might have missed it... | 19:04 |
fungi | #info Tentative late-cycle joint Infra/QA get together to be held September 19-21 (CW38) in at SAP offices in Walldorf, DE | 19:04 |
fungi | check with mkoderer and oomichi for details | 19:04 |
fungi | #link https://wiki.openstack.org/wiki/Sprints/QAInfraNewtonSprint | 19:04 |
*** dmorita has joined #openstack-meeting | 19:04 | |
*** dmorita has joined #openstack-meeting | 19:05 | |
fungi | also here's a good one! | 19:05 |
*** rbak has quit IRC | 19:05 | |
fungi | #info StoryBoard Bug Squash! 22nd and 23rd of June | 19:05 |
fungi | #link http://lists.openstack.org/pipermail/openstack-infra/2016-June/004402.html | 19:05 |
Zara | \o/ | 19:05 |
oomichi | fungi: yeah, we will write the detail on the wiki with mkorderer and notice for you :) | 19:05 |
*** mickeys has quit IRC | 19:05 | |
fungi | thanks, oomichi! | 19:06 |
fungi | anyone know any other important upcoming things i've missed announcing before i move on? | 19:06 |
anteaya | I'm hoping to have an gerrit storyboard interacting by bug squash | 19:06 |
SotK | \o/ | 19:06 |
Zara | :D | 19:06 |
anteaya | at least on test servers | 19:06 |
*** sdake has quit IRC | 19:06 | |
*** shaohe_feng has quit IRC | 19:07 | |
*** sdake has joined #openstack-meeting | 19:07 | |
fungi | #topic Actions from last meeting | 19:07 |
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)" | 19:07 | |
pleia2 | we didn't formally #action it, but at the last meeting I said I'd draft up the wiki upgrade spec, review here: https://review.openstack.org/#/c/328455/ (also topical from discussions in channel this morning) | 19:07 |
anteaya | pleia2: yay | 19:07 |
*** gagehugo has left #openstack-meeting | 19:07 | |
*** shaohe_feng has joined #openstack-meeting | 19:07 | |
fungi | pleia2: ahh, yep, i'd like to have that up for council approval next week, but doesn't mean we can't get started implementing sooner | 19:07 |
pleia2 | anteaya: thanks for your review | 19:07 |
*** olaph has joined #openstack-meeting | 19:08 | |
fungi | #link http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-06-07-19.03.html | 19:08 |
*** fzdarsky has quit IRC | 19:08 | |
anteaya | thanks for writing the spec | 19:08 |
olaph | o/ | 19:08 |
fungi | (none) | 19:08 |
fungi | #topic Specs approval | 19:08 |
*** openstack changes topic to "Specs approval (Meeting topic: infra)" | 19:08 | |
fungi | none this week, but as mentioned above, wiki upgrade spec is up for review and should hopefully be ready for approval next week | 19:08 |
fungi | #link https://review.openstack.org/328455 | 19:08 |
fungi | #topic Priority Efforts | 19:09 |
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)" | 19:09 | |
*** zhonghua has quit IRC | 19:09 | |
fungi | i started a ml thread reviewing the current priority list, proposing some cleanup, asking for suggestions | 19:09 |
fungi | #link #link http://lists.openstack.org/pipermail/openstack-infra/2016-June/004374.html | 19:09 |
fungi | i meant to have an update to infra-specs encapsulating the feedback up for today, but ran out of time so expect it in the next day or two hopefully | 19:10 |
rcarrillocruz | i started looking on the ansible-puppet issues | 19:10 |
fungi | in the meantime, please follow up there on the ml if you have anything to add | 19:10 |
fungi | thanks rcarrillocruz! | 19:10 |
rcarrillocruz | already pushed https://review.openstack.org/#/c/327789/ , for syslogging on puppetmaster | 19:10 |
fungi | #topic Priority Efforts: Use Diskimage Builder in Nodepool (pabelanger) | 19:11 |
*** openstack changes topic to "Priority Efforts: Use Diskimage Builder in Nodepool (pabelanger) (Meeting topic: infra)" | 19:11 | |
rcarrillocruz | puppetdb on 3.x and all will go shortly | 19:11 |
fungi | i approved the change to close this one out a few minutes ago | 19:11 |
fungi | #link https://review.openstack.org/329080 | 19:11 |
pleia2 | \o/ | 19:11 |
pabelanger | Yes! | 19:11 |
pleia2 | congrats all | 19:11 |
fungi | another one down! | 19:11 |
pabelanger | indeed, congrats to everybody on that | 19:11 |
fungi | excellent work, everyone | 19:11 |
fungi | is there any redux/post-mortem needed on it? | 19:12 |
clarkb | fungi: maybe as part of removing snapshot builds from nodepool we can write something up | 19:12 |
clarkb | "hey this happened this is why" etc | 19:12 |
*** LouisF has quit IRC | 19:12 | |
fungi | i think this is one of those which started out a little vague and grew too many tentacles whichi should have been treated as related/prerequisite priority efforts | 19:13 |
pabelanger | https://review.openstack.org/#/c/325339/ for deprecating | 19:13 |
*** jaugustine has quit IRC | 19:14 | |
*** jaugustine has joined #openstack-meeting | 19:14 | |
fungi | in the future, we should keep in mind that scope changes on existing priority efforts might be better off as additional (perhaps small) specs which we can just declare as a de facto priority because of being a blocking prerequisite for a priority we've approved. it makes it a little easier to be able to see the progress being made and keeps us from ending up with specs which linger forever without | 19:14 |
fungi | clear reasons for taking so long | 19:14 |
fungi | i'm partially to blame on this one for deciding to tack on bindep implementation in jobs without creating a separate blocking spec to cover that | 19:15 |
clarkb | glean was another massive thing that jammed the works | 19:15 |
fungi | yep, same sort of situation | 19:16 |
clarkb | not strictly required but we went down the rabbit hole so far that we didn't really have a choice but to dig out the other side | 19:16 |
*** dmorita has quit IRC | 19:16 | |
jeblair | well, i pushed that too. it was administratively easy to do at the time, but is perhaps worth the extra effort as you say | 19:16 |
*** jmills_nasa has quit IRC | 19:16 | |
fungi | anyway, awesome all of this is done and we can now reap the benefits of using our own images and _only_ our own images in ci | 19:17 |
fungi | thanks again everyone | 19:17 |
*** shaohe_feng has quit IRC | 19:17 | |
jeblair | ++ | 19:17 |
rcarrillocruz | yay glean | 19:17 |
prometheanfire | rcarrillocruz: :D | 19:17 |
*** shaohe_feng has joined #openstack-meeting | 19:17 | |
fungi | #topic Priority Efforts: Infra-cloud (crinkle) | 19:17 |
*** openstack changes topic to "Priority Efforts: Infra-cloud (crinkle) (Meeting topic: infra)" | 19:17 | |
crinkle | so when we shut down the servers in fort collins some of them were on kilo and some were on liberty | 19:18 |
crinkle | we now have code to update the puppet module for mitaka | 19:18 |
crinkle | i recall we decided our upgrade strategy was just to do a full redeploy | 19:18 |
fungi | and rcarrillocruz is redeploying everything as we speak | 19:18 |
crinkle | so i think it makes sense to just merge the mitaka code and have mitaka? | 19:18 |
rcarrillocruz | well, fixing inventory | 19:18 |
rcarrillocruz | we haven't gone that far to redeploy (yet) | 19:18 |
fungi | okay, right, not up to the redeploy stage yet | 19:19 |
crinkle | yeah i think we're some work away from redeploy but still | 19:19 |
jeblair | fungi: nice try -- next time you say that, it'll be true! :) | 19:19 |
pabelanger | baremetal00.vanilla.ic.openstack.org is online and managed by ansible / puppet again too | 19:19 |
rcarrillocruz | i'd say yes to mitaka | 19:19 |
anteaya | crinkle: what is the downside of merging the mitaka code? | 19:19 |
pleia2 | I've been using the mitaka puppet modules elsewhere, they're in good shape | 19:19 |
fungi | but i agree, trying to redeploy with mitaka and working out obvious bugs would be a great use of the environment while we have it (until the upcoming move) | 19:19 |
rcarrillocruz | :-) | 19:19 |
nibalizer | o/ | 19:19 |
crinkle | pabelanger suggested i check and see if anyone had strong feelings about upgrading all to mitaka as opposed to equalizing to liberty | 19:19 |
crinkle | anteaya: none that i can see really | 19:19 |
rcarrillocruz | which, unofficially, will happen end of next month | 19:19 |
clarkb | I think we should mitaka | 19:19 |
anteaya | crinkle: great, thanks then I am in favour of merging | 19:20 |
pabelanger | I'm for mitaka too | 19:20 |
rcarrillocruz | we'll pass on info as we get it | 19:20 |
fungi | yeah, redeploy means we don't really care that there's a release skip for some of the systems in the mix | 19:20 |
*** mrmartin has quit IRC | 19:20 | |
fungi | so no objection fromme. if anything, complete agreement | 19:21 |
crinkle | okay sounds good | 19:21 |
rcarrillocruz | ++ | 19:21 |
fungi | #agreed upcoming infra-cloud redeploy should be 100% mitaka | 19:21 |
crinkle | #link https://review.openstack.org/#/c/312319/ | 19:21 |
crinkle | #link https://review.openstack.org/#/c/304946/ | 19:21 |
anteaya | fromme means pious apparently | 19:21 |
fungi | thanks crinkle, rcarrillocruz! | 19:21 |
fungi | ooh | 19:21 |
fungi | i like when my terrible typos have actual meaning in other languages | 19:22 |
anteaya | me too, it was a good one | 19:22 |
fungi | anything else on this? | 19:22 |
crinkle | not from me | 19:22 |
*** kzaitsev_mb has quit IRC | 19:22 | |
rcarrillocruz | neither from me | 19:23 |
fungi | #topic Updated Gerrit GC test results (zaro) | 19:23 |
*** openstack changes topic to "Updated Gerrit GC test results (zaro) (Meeting topic: infra)" | 19:23 | |
fungi | #link https://www.mail-archive.com/openstack-infra@lists.openstack.org/msg04374.html | 19:24 |
*** wcriswell has joined #openstack-meeting | 19:24 | |
fungi | hopefully everyone's been following the ml thread | 19:24 |
*** dmorita has joined #openstack-meeting | 19:24 | |
fungi | are there further objections to or test requests before turning on garbage collection and pruning? | 19:24 |
zaro | so i got more info. wondering if we wanted to make any changes to git repos? | 19:24 |
fungi | and was the suggestion to do git gc or jgit gc? noting that we'll presumably still need to git gc on the mirrors as well? | 19:25 |
*** tonytan4ever has quit IRC | 19:25 | |
zaro | maybe decide on interval as well? | 19:26 |
fungi | jeblair: ^ you were probably the most vocal as far as specific ideas of what should be tested first | 19:27 |
zaro | the existing repack is set for weekly. | 19:27 |
*** shaohe_feng has quit IRC | 19:27 | |
jeblair | zaro seems to have covered everything! :) | 19:27 |
zaro | i’ve prepared a change to switch out repack with gc (same interval), #link https://review.openstack.org/#/c/329566 | 19:27 |
*** shaohe_feng has joined #openstack-meeting | 19:28 | |
fungi | yeah, i'm satisfied we've got sufficient diligence on this, given the risk such a change potentially carries | 19:29 |
fungi | zaro: thanks so much for all the work trying out combinations and reporting stats | 19:29 |
*** ociuhandu has joined #openstack-meeting | 19:29 | |
zaro | np. glad to do :) | 19:29 |
fungi | and hashar (not in channel) for pitching in details from wikimedia foundation's deployment | 19:30 |
zaro | i’ve also prepared changes to upgrade to latest gerrit 2.11 but wanted to wait until gc change and see what happens | 19:30 |
*** dmorita has quit IRC | 19:30 | |
*** leifmadsen has joined #openstack-meeting | 19:31 | |
fungi | so the proposed change is to stick with git gc on the gerrit server rather than jgit gc in the background, since we can make it match what we do on the cgit servers, right? | 19:31 |
*** baoli has joined #openstack-meeting | 19:31 | |
jeblair | i like that approach | 19:31 |
zaro | makes sense to me. | 19:31 |
*** mriedem has quit IRC | 19:31 | |
*** dmorita has joined #openstack-meeting | 19:31 | |
*** sarob has joined #openstack-meeting | 19:32 | |
fungi | #agreed Let's start doing git garbage collection on review.openstack.org and the git.openstack.org servers | 19:32 |
fungi | anything else on this? | 19:32 |
zaro | nope. | 19:32 |
zaro | ohh wait, weekly ok? | 19:32 |
fungi | it's what we've done so far. i think it's a fine first step | 19:33 |
zaro | cool. | 19:33 |
*** adiantum has quit IRC | 19:33 | |
fungi | if we decide we want to even it out more, we can make it more frequent later now that we're at least comfortable it's a working solution | 19:33 |
clarkb | ++ | 19:33 |
fungi | #topic Open discussion | 19:33 |
*** openstack changes topic to "Open discussion (Meeting topic: infra)" | 19:33 | |
pleia2 | I should have added this to the agenda, but I could use a bit of help with the translations checksite, re: http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_check_site.html | 19:33 |
*** mriedem has joined #openstack-meeting | 19:34 | |
pleia2 | I've been working with Frank Kloeker, but we've run into some snags I'm not sure how to solve | 19:34 |
*** ijw__ has quit IRC | 19:34 | |
*** ayoung_ has joined #openstack-meeting | 19:34 | |
pleia2 | we have a new puppet module for installing devstack and pulling in the translations in openstack-infra/puppet-translation_checksite | 19:34 |
pleia2 | on a good day, it pretty much works (still needs a patch for a longer timeout) | 19:35 |
fungi | also, on the earlier topic of the wiki upgrade and improvements, i'm hoping to propose including it in the newton priorities list once the spec is approved. i at least intend to be spending a fair amount of effort getting it into better shape | 19:35 |
*** oshidoshi has quit IRC | 19:35 | |
prometheanfire | I have a couple of reviews I'd like looked at more gentoo stuff | 19:35 |
pleia2 | on most days, ./stack.sh will fail to build in some way and we're left with a broken instance | 19:35 |
crinkle | i'm curious if there are proposed topics for the infra/qa midcycle? i might have missed it | 19:36 |
prometheanfire | 5 weeks old :P https://review.openstack.org/#/c/310865/ | 19:36 |
fungi | crinkle: suggestions were zuul v3 or infra-cloud again | 19:36 |
*** ionutbalutoiu has quit IRC | 19:36 | |
*** dmorita has quit IRC | 19:36 | |
fungi | crinkle: but nothing solid yet. open to ideas! | 19:36 |
docaedo | I'd appreciate some feedback on my IRC spec (https://review.openstack.org/#/c/319506/1) and maybe some guidance on what to do next? Or just wait 'till the spec is approved and go from there? | 19:36 |
prometheanfire | ianw: you think I can unmark that wip? | 19:36 |
crinkle | fungi: thank you | 19:36 |
*** gyee has quit IRC | 19:36 | |
*** MeganR has quit IRC | 19:36 | |
*** mrmartin has joined #openstack-meeting | 19:37 | |
pleia2 | so our plan of refreshing devstack weekly as outlined in the spec is complicated 1) by the devstack builds failing 2) we have downtime when we rebuild devstack, though weekly for a couple hours seems reasonable assuming the build is successful | 19:37 |
prometheanfire | also need reviews for https://review.openstack.org/#/c/318994/ to clean up the nodepool dib elements | 19:37 |
*** shaohe_feng has quit IRC | 19:37 | |
clarkb | pleia2: do you think devstack is the right tool for this? | 19:37 |
pleia2 | I was wondering if we're going about this wrong, since we have tooling to build devstack instances already, and this is essentially a read-only instance from the perspective of translators | 19:37 |
fungi | docaedo: yeah, after looking into it, and alternatives, and watching some of the same discussion unfold for the python infra community i think i'm close to being in favor | 19:38 |
*** cbouch has joined #openstack-meeting | 19:38 | |
anteaya | pleia2: do you have thoughts on what approach would work better? | 19:38 |
pleia2 | clarkb: we need a build of openstack that we can apply the in-progress translations to during the last month before release, devstack seemed like the right thing | 19:38 |
*** shaohe_feng has joined #openstack-meeting | 19:38 | |
jeblair | pleia2: why do the devstack builds fail? | 19:38 |
anteaya | would a disk image builder image make more sense? | 19:38 |
ianw | prometheanfire: have you built a gentoo image? we can work on integrating it but the first step is to know that dib with all the infra elements is going to actually output a usable qcow2 | 19:39 |
clarkb | pleia2: ok I just ask because if it fails more often than not that seems like potentially a bad idea. But may be worth figuring out those fails too | 19:39 |
docaedo | fungi: thanks - since you're the spirit guide for it I'll just pester you occasionally for additional feedback ;) | 19:39 |
*** adiantum has joined #openstack-meeting | 19:39 | |
jeblair | (theoretically, devstack should almost always work -- it's gated) | 19:39 |
prometheanfire | ianw: I'll test tonight or tomorrow | 19:39 |
fungi | docaedo: was there a demo for the interface somewhere? | 19:39 |
pleia2 | jeblair: last time it was a puppet timeout, another time it was network weirdness on my instance, we have no fault tolerance in the module so any problems are fatal | 19:39 |
prometheanfire | ianw: https://review.openstack.org/#/c/318994/ shouldn't need to wait though | 19:39 |
*** oshidoshi has joined #openstack-meeting | 19:40 | |
docaedo | fungi: no, but I can make an account on my test server and PM you the details | 19:40 |
docaedo | fungi: user account management is a gap right now too, feel like that will need some discussion and a brilliant plan from you or some other genius on the infra team | 19:41 |
clarkb | pleia2: ah ok the fails are not in devstack itself but in the surrounding tooling/env | 19:41 |
*** yuval has joined #openstack-meeting | 19:41 | |
*** chenying__ has joined #openstack-meeting | 19:41 | |
*** ivar-lazzaro has quit IRC | 19:41 | |
fungi | docaedo: oh, that would be cool. and yeah account setup is one of those sticking points for wider adoption. while the idea has merit the opportunity to attract abusive users without vetting is high | 19:41 |
pleia2 | clarkb: yeah, once or twice it's been I got unlucky and devstack was actually broken, but toward the end of the cycle when translators are active this should not be a problem, devstack should be pretty solid by then | 19:42 |
jeblair | docaedo: could we hook it into openstackid/ipsilon? | 19:42 |
*** ivar-lazzaro has joined #openstack-meeting | 19:42 | |
*** weshay is now known as weshay_mtg | 19:42 | |
*** zhonghua-lee has joined #openstack-meeting | 19:42 | |
anteaya | jeblair: what is the current status of ipsilon progress? | 19:42 |
*** Sukhdev has joined #openstack-meeting | 19:42 | |
docaedo | jeblair: in theory, yes, but someone would need to write the JS for it as that doesn't exist in The Lounge right now | 19:43 |
*** rfolco has quit IRC | 19:43 | |
*** salv-orlando has quit IRC | 19:43 | |
fungi | basically running a thelounge instance without limiting it to specific users and specific channels would be likely to attract spammers and other abusive users because we'd basically just be operating an "open proxy" to freenode | 19:43 |
*** ajmiller_ has quit IRC | 19:44 | |
*** salv-orlando has joined #openstack-meeting | 19:44 | |
jeblair | anteaya: not yest begun | 19:44 |
docaedo | correct, even if it was tied to openstackID I would want some curated list of accounts that are active | 19:44 |
anteaya | jeblair: thanks | 19:44 |
*** dimtruck is now known as zz_dimtruck | 19:44 | |
notmorgan | docaedo: that is fair | 19:44 |
*** baoli has quit IRC | 19:44 | |
*** roxanagh_ has joined #openstack-meeting | 19:44 | |
*** delattec has quit IRC | 19:45 | |
pabelanger | First pass at our gerrit outage: https://etherpad.openstack.org/p/upgrade-zuul-trusty | 19:45 |
*** sarob has quit IRC | 19:45 | |
fungi | docaedo: limiting it to channels where openstack infra has ops would also be good, if we can do that | 19:45 |
*** baoli has joined #openstack-meeting | 19:45 | |
fungi | basically anything we can do to prevent freenode staff from blocking its ip address due to abuse | 19:45 |
*** harlowja_ has joined #openstack-meeting | 19:45 | |
fungi | because then, nobody's able to use it | 19:45 |
*** sarob has joined #openstack-meeting | 19:45 | |
docaedo | fungi: that's probably not too difficult, but I would argue that's not necessary if we're deciding who we set up with it (presumably a small audience of mostly working group people) | 19:45 |
*** ijw_ has joined #openstack-meeting | 19:46 | |
nibalizer | usually they limit connections at 10ish per ip anywyas, so we'd have to talk to them regardless | 19:46 |
docaedo | fungi: but yes, getting banned by freenode would not be great | 19:46 |
nibalizer | pleia2: likely knows more | 19:46 |
*** xiangxinyong has joined #openstack-meeting | 19:46 | |
pleia2 | yeah, we should notify them that we're hosting it | 19:46 |
jeblair | we might want to see if tomaw can provide some feedback on the idea | 19:46 |
fungi | docaedo: one solution would be to delegate account control to others in the community (working group leads or something) to field new account requests | 19:46 |
fungi | since they're likely to know when someone requesting access is legitimately needing it | 19:47 |
*** ivar-lazzaro has quit IRC | 19:47 | |
docaedo | fungi: I would be all for that, I do not want to be the person in charge of IRC accounts by any means | 19:47 |
*** shaohe_feng has quit IRC | 19:48 | |
fungi | as widespread and in touch with the community as our team is, we're not omnipotent and don't know a lot of the regulars on various board-appointed working groups and the like | 19:48 |
fungi | but opening it up to anyone with an openstack foundation member accuont is just likely to result in lots of people signing up as foundation members (with bogus info) so they can abuse the proxy | 19:48 |
*** roxanagh_ has quit IRC | 19:49 | |
*** saggi has joined #openstack-meeting | 19:49 | |
anteaya | what problem is this solving? | 19:49 |
*** harlowja has quit IRC | 19:49 | |
anteaya | sorry I haven't been following along | 19:49 |
anteaya | what are we fixing with this | 19:49 |
fungi | anteaya: https://review.openstack.org/319506 proposes a spec to host a persistent web irc client | 19:50 |
docaedo | anteaya: the short answer is helping people who aren't comfortable with IRC get on IRC | 19:50 |
*** shaohe_feng has joined #openstack-meeting | 19:50 | |
docaedo | anteaya: essentially giving them an IRCCloud account without them having to pay for it (by hosting an alternate with similar UX and functionality) | 19:50 |
*** cody-somerville has joined #openstack-meeting | 19:50 | |
*** cody-somerville has quit IRC | 19:50 | |
*** cody-somerville has joined #openstack-meeting | 19:50 | |
*** jsavak has joined #openstack-meeting | 19:50 | |
*** rfolco has joined #openstack-meeting | 19:50 | |
anteaya | given the amount of human work going to be needed to ensure the tool isn't abused would it make sense to offer instructions to those who are uncomfortable to become comfy? | 19:51 |
fungi | as opposed to pushing them to freenode's webchat (which doesn't catch scrollback when they're offline, so will miss async private messages) or irccloud (which costs money) | 19:51 |
anteaya | I mean humans will have to be actively montioring its use anyway | 19:51 |
anteaya | who needs to have to pay for irc? | 19:51 |
anteaya | I've never heard of having to pay to use irc | 19:51 |
pleia2 | irccloud is a popular paid service | 19:52 |
fungi | anteaya: to be frank, i pay for access to irc (because i run my irc client on a persistent virtual host in a public cloud provider) | 19:52 |
anteaya | fungi: well yes, that is true | 19:52 |
nibalizer | same as fungi | 19:52 |
anteaya | yes, good point | 19:52 |
docaedo | anteaya: theres a service (ircclloud.com) that has a free tier, but the paid tier gives you scrollback when you leave and return | 19:52 |
anteaya | so teaching folks xchat is off the table? | 19:52 |
* zaro pays for the ircloud | 19:52 | |
anteaya | if that has already been discarded then fine | 19:53 |
docaedo | anteaya: you could definitely give some feedback on the spec :) | 19:53 |
fungi | so take random project manager at $member_company who wants to participate in an openstack board-designated working group | 19:53 |
anteaya | it just seems this is going to be maintenance heavy | 19:53 |
docaedo | anteaya: the other thing I want to solve is the drive-by IRC use, where folks pop on just for a meeting, and don't use IRC again (ideally helping bring more people into our globally distributed IRC community) | 19:53 |
anteaya | docaedo: that is fair, I think there is value in helping them find where the channel logs are hosted | 19:54 |
docaedo | anteaya: it might be maintenance heavy, it's one of the concerns I noted in the spec | 19:54 |
fungi | the likely end results are 1. we convince them to use irc and having their meetings where the technical community has their meetings by providing a low-barrier-to-entry interface to irc for them, or 2. they use google hipmeets or whatever | 19:54 |
anteaya | okay I've said my bit, thanks for listening | 19:54 |
docaedo | fungi: exactly, well said, thanks. | 19:55 |
docaedo | fungi: also can you share an invite to google hipmeets if you have one? thanks! | 19:55 |
fungi | docaedo: i think it's integrated with orkut | 19:55 |
docaedo | fungi: :P | 19:56 |
*** sdague has joined #openstack-meeting | 19:56 | |
persia | A potentially relevant data point: one of the behaviours I see in many contexts for this class of folk is a reliance on conference calls, sometimes with IRC adjuncts, where the IRC consists of #action, #info, #topic, but no content. | 19:56 |
fungi | persia: thanks, that is certainly a distinct risk | 19:56 |
anteaya | persia: any suggestions for getting all the content on irc? | 19:56 |
anteaya | persia: or just an observation | 19:56 |
*** ivc_ has quit IRC | 19:56 | |
*** annegentle has joined #openstack-meeting | 19:56 | |
pleia2 | re: translations checksite, I'll get the stakeholders on a thread on the -infra list with a more cohesive explanation of what we're struggling with so we can ask more specific questions about the direction we're going in | 19:57 |
fungi | though i'd argue that having a meeting secretary shorthand the minutes into our meetbot is still better than nothing public at all | 19:57 |
persia | anteaya: Reduce barriers to entry for persistent IRC. Note that there are some engineering teams who contribute to parts of OpenStack (e.g. bits of Neutron) that have the behaviour I described. | 19:57 |
anteaya | persia: can you review https://review.openstack.org/#/c/319506/ with your observations | 19:58 |
persia | Sure. | 19:58 |
*** shaohe_feng has quit IRC | 19:58 | |
anteaya | also I acknowledge some Neutron folks still have this habit | 19:58 |
*** e0ne has joined #openstack-meeting | 19:58 | |
fungi | we're down to the last couple minutes. anybody have anything else? | 19:58 |
*** rwsu_ has joined #openstack-meeting | 19:58 | |
anteaya | though overall there has been great improvement in that project | 19:58 |
fungi | pleia2: sounds good re: the translations checksite | 19:58 |
anteaya | persia: thanks | 19:58 |
*** zengchen has joined #openstack-meeting | 19:58 | |
*** shaohe_feng has joined #openstack-meeting | 19:58 | |
fungi | i didn't expect running and periodically rebuilding a devstack instance would be trivial. after all, i've seen our ci jobs ;) | 19:59 |
pleia2 | indeed :) | 19:59 |
*** cdent has joined #openstack-meeting | 19:59 | |
fungi | okay, we're at time. thanks everyone! see you in #openstack-infra | 20:00 |
fungi | @endmeeting | 20:00 |
fungi | gah | 20:00 |
fungi | #endmeeting | 20:00 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 20:00 | |
openstack | Meeting ended Tue Jun 14 20:00:12 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 20:00 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-06-14-19.02.html | 20:00 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-06-14-19.02.txt | 20:00 |
openstack | Log: http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-06-14-19.02.log.html | 20:00 |
fungi | silly adjacent keys | 20:00 |
flaper87 | o/ | 20:00 |
ttx | o/ | 20:00 |
ttx | annegentle, dims, dhellmann, johnthetubaguy, mestery, mtreinish, thingee, mordred, morgan, russellb, sdague : around ? | 20:00 |
dhellmann | o/ | 20:00 |
sdague | o/ | 20:00 |
annegentle | here | 20:00 |
dims | o/ | 20:00 |
docaedo | fungi: don't feel bad, @endmeeting is how it works in hipmeets | 20:00 |
russellb | o/ | 20:00 |
saggi | o/ | 20:00 |
russellb | mestery sends his regrets | 20:00 |
yuval | o/ | 20:00 |
*** edleafe_ has joined #openstack-meeting | 20:00 | |
xiangxinyong | o/ | 20:00 |
*** rwsu has quit IRC | 20:00 | |
ttx | #startmeeting tc | 20:01 |
openstack | Meeting started Tue Jun 14 20:01:02 2016 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. | 20:01 |
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 |
notmorgan | o/ -ish | 20:01 |
oshidoshi | o/ | 20:01 |
mtreinish | o/ | 20:01 |
ttx | Small quorum but we'll make it happen | 20:01 |
ttx | Our agenda for today is: | 20:01 |
ttx | #link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee | 20:01 |
* edleafe_ lurks while in his parked car | 20:01 | |
ttx | #topic Tidy of item 5 of the vulnerability:managed tag | 20:01 |
*** openstack changes topic to "Tidy of item 5 of the vulnerability:managed tag (Meeting topic: tc)" | 20:01 | |
ttx | #link https://review.openstack.org/300698 | 20:01 |
flaper87 | edleafe_: please, open the windows or turn the AC on | 20:01 |
ttx | This one sounds like a good incremental improvement, now that the security folks are happy with it | 20:02 |
* flaper87 is happy with it | 20:02 | |
ttx | Still short of a few votes though | 20:02 |
fungi | vmt members are satisfied with sdake's proposal | 20:02 |
*** olaph has left #openstack-meeting | 20:02 | |
sdake | hi fungi :) | 20:02 |
notmorgan | fungi: ++ | 20:02 |
dims | +1 from me | 20:02 |
dims | thanks fungi | 20:02 |
notmorgan | as both TC and VMT, i think it's good. | 20:02 |
edleafe_ | flaper87: It's 97F. The AC is running | 20:02 |
ttx | need two more votes | 20:02 |
flaper87 | edleafe_: jeez | 20:03 |
* Rockyg suggests edleafe roll down w window to avoid heat stroke | 20:03 | |
annegentle | Rockyg: edleafe_ nope just keep the car running with AC! | 20:03 |
*** jsavak has quit IRC | 20:03 | |
notmorgan | ttx: oops looks like i forgot to rollcall vote on it | 20:03 |
notmorgan | fixed that | 20:03 |
ttx | looks like we have enough now | 20:03 |
ttx | ok, approved | 20:04 |
*** sarob has quit IRC | 20:04 | |
ttx | #topic Fast-tracking projects.yaml release tags / deliverable changes (dhellmann) | 20:04 |
*** openstack changes topic to "Fast-tracking projects.yaml release tags / deliverable changes (dhellmann) (Meeting topic: tc)" | 20:04 | |
* amrith wanders in ... | 20:04 | |
ttx | dhellmann: want to introduce this one ? | 20:04 |
dhellmann | sure | 20:04 |
*** rwsu_ is now known as rwsu | 20:04 | |
dhellmann | We’ve added some validation rules to the release request process that verify that the thing being released matches the thing as defined for governance. | 20:04 |
dhellmann | We’ve started noticing in a few cases that updates to the governance repository to “fix” release-related settings like release models and deliverable definitions have been delaying releases. | 20:04 |
dhellmann | I would like to propose a general exception to the review policy for openstack/governance that if the change does not effect governance, and are only related to tags managed by other teams, we not wait the week for “objections”. | 20:04 |
dhellmann | For example, changing the release model of an existing deliverable and adding (or removing) the tags for stable or security teams would only need to be reviewed by the relevant team, and then they can be approved by the chair. | 20:04 |
dhellmann | Splitting or combining deliverables is a similar sort of change that’s a bit more complex because making new deliverables may require the approval of multiple groups to set the appropriate tags. | 20:04 |
dhellmann | However, as long as no new repositories are added I think this sort of change should also be fast-tracked. | 20:04 |
* flaper87 notices dhellmann prepared hist intro ahead of the meeting | 20:04 | |
flaper87 | dhellmann: ++ | 20:04 |
dhellmann | Changes that add repositories, and therefore change the voter roles for the TC, should continue to go through the 1 week review period. | 20:04 |
* edleafe_ knows that annegentle knows south Texas heat | 20:05 | |
* dhellmann ends pastebomb | 20:05 | |
*** yamahata has quit IRC | 20:05 | |
russellb | sounds reasonable to me | 20:05 |
flaper87 | I'm in favor of this | 20:05 |
sdague | works for me | 20:05 |
johnthetubaguy | +1 from me | 20:06 |
notmorgan | sdague: ++ same | 20:06 |
*** prometheanfire has left #openstack-meeting | 20:06 | |
*** zz_dimtruck is now known as dimtruck | 20:06 | |
*** ajmiller has joined #openstack-meeting | 20:06 | |
ttx | I guess we could revert if a TC member ends up objecting two days after the fact | 20:06 |
dhellmann | ttx: yes, that's a good point. all of this is ultimately mutable. | 20:06 |
mtreinish | no issue from me | 20:06 |
annegentle | dhellmann: ooo my only tough sell point is the "splitting or combining deliverables" part... what's that like? Do you have an example? | 20:06 |
annegentle | dhellmann: gnocci/aodh/ceilometer type stuff? | 20:07 |
dhellmann | annegentle : the recent stuff with neutron | 20:07 |
ttx | dhellmann: so, release: and security: tags changes, + deliverable reorganization ? | 20:07 |
*** gordc has joined #openstack-meeting | 20:07 | |
dhellmann | ttx: and the stable tag | 20:07 |
ttx | if I have the correspodning PTL signoff I can fasttrack them | 20:07 |
dhellmann | and any other teams to which we've delegated management of tags in the future (like if annegentle's work turns into doc tags) | 20:07 |
* edleafe_ has to go - daughter is ready. | 20:07 | |
dhellmann | ttx: yes | 20:08 |
ttx | ok, let me capture that | 20:08 |
dhellmann | should I write this up more formally as a resolution, or can we agree to a procedural thing without that? | 20:08 |
*** shaohe_feng has quit IRC | 20:08 | |
dhellmann | we've made agreements on procedural decisions in-meeting in the past, iirc, like our current fast-track policy on typos | 20:08 |
ttx | #agreed for projects.yaml chnage affecting stable: security: or release: tags (or deliverable reorganization) the TC chait can fast-track approval if the corresponding PTL approved it | 20:08 |
flaper87 | I'm good with meeting agreement | 20:08 |
dims | ttx : dhellmann : am generally in favor..don't really see a need for resolution, we could update some instructions/readme somewhere | 20:08 |
ttx | dhellmann: no, it's a procedural agreement | 20:08 |
*** shaohe_feng has joined #openstack-meeting | 20:09 | |
*** dmorita has joined #openstack-meeting | 20:09 | |
*** uxdanielle has quit IRC | 20:09 | |
dhellmann | ok, cool, just making sure | 20:09 |
*** mrmartin has quit IRC | 20:09 | |
ttx | I guess we could document it as house rules | 20:09 |
annegentle | I'm ok with fast-track | 20:09 |
* flaper87 pictures dhellmann doing the "I don't need to write a resolution" dance | 20:09 | |
dhellmann | ttx: +1 to writing things down | 20:09 |
annegentle | I might regret it later :) but seems like trust is best | 20:09 |
ttx | #action ttx to document house rules | 20:09 |
ttx | (that's the speech I end up giving at every start of cycle) | 20:09 |
*** flwang has quit IRC | 20:10 | |
flaper87 | lol | 20:10 |
dhellmann | an alternative is to move some of those tags into the repo where we're using them and validating them, but we've been focusing on putting them all in the governance repo for consistency so... | 20:10 |
ttx | ok, anything else on that topic ? | 20:10 |
dims | haha | 20:10 |
dhellmann | ttx: that's it from me, if we've settled the question | 20:10 |
ttx | #topic Add project Smaug to OpenStack big-tent | 20:11 |
*** openstack changes topic to "Add project Smaug to OpenStack big-tent (Meeting topic: tc)" | 20:11 | |
ttx | #link https://review.openstack.org/326724 | 20:11 |
ttx | Smaug aims to provide data protection as a service (in a large sense of the word "data") | 20:11 |
ttx | I could not spot any good reason to deny them / delay their entry, so I'm tentatively +1 on this | 20:11 |
ttx | saggi: o/ | 20:12 |
ttx | Questions ? | 20:12 |
annegentle | one concept I read and read but couldn't understand is: | 20:12 |
saggi | I'm here | 20:12 |
annegentle | what are the plugable pieces? the protections? | 20:12 |
*** cdelatte has joined #openstack-meeting | 20:12 | |
*** mohankumar__ has quit IRC | 20:12 | |
saggi | There are 3 main pluggable pieces. | 20:12 |
saggi | 1. is what we call protectables | 20:13 |
annegentle | are "Protection Plugins" open source? | 20:13 |
saggi | It's the resources you want to protect and their relationships | 20:13 |
saggi | annegentle: yes | 20:13 |
annegentle | sorry saggi, I mispoke, I wondered about the plugins. What are some of the names? | 20:13 |
annegentle | of plugins? | 20:13 |
saggi | For protection we have cinder\nova\neutron. | 20:14 |
dhellmann | annegentle : are you asking about which plugins are implemented/planned or which areas of smaug can have plugins? | 20:14 |
russellb | https://wiki.openstack.org/wiki/Smaug#Available_Protectables | 20:14 |
*** browne has left #openstack-meeting | 20:14 | |
flaper87 | russellb: ++ | 20:14 |
russellb | clears up what "protectables" are for me | 20:14 |
*** uxdanielle has joined #openstack-meeting | 20:14 | |
saggi | Things you want to protect. The "what". | 20:14 |
annegentle | dhellmann: what are names of plugins, that's what I'm trying to understand. I understand what you want to protect | 20:15 |
sdague | right, it's basically calling out to existing services - https://github.com/openstack/smaug/blob/ce2b117a184ade8f376839178fdc34c2d70896b7/smaug/services/protection/protection_plugins/volume/cinder_protection_plugin.py#L41 | 20:15 |
saggi | The user can add external protectables if they are required for the application. They define new types of resources you can protect and how they relate | 20:15 |
dhellmann | I understood this to be a thing to put in front of different backup tools that would implement backup for different types of objects in an appropriate way. | 20:15 |
saggi | They define that a volume is needed by a VM | 20:15 |
annegentle | saggi: as an app developer, do I define a plugin that protects multiple protectables? | 20:16 |
saggi | it's pluggable in a sense that the user can add entity external to Openstack an they will be included in the tree. | 20:16 |
saggi | Protection Plugins are the "how" | 20:16 |
saggi | you can define multiple protection plugins to a single protectable. | 20:16 |
Rockyg | so, what would the manila plugin name look like? | 20:16 |
saggi | it's the admins responsibility to choose what protection plugin to map to what resource | 20:16 |
annegentle | saggi: is this an admin tool or an app developer tool? Are you protecting the service or resources run on the service? | 20:17 |
dhellmann | saggi : so I could have a protection plugin for storing things to swift and a protection plugin for writing things to magnetic tape, and then the admin would map the appropriate one to keystone data, cinder, data, etc.? | 20:17 |
*** kzaitsev_mb has joined #openstack-meeting | 20:17 | |
Rockyg | dhellmann, good question | 20:17 |
saggi | This will be a bank plugin. | 20:18 |
*** cdent has quit IRC | 20:18 | |
saggi | So the protection plugin takes a protectable and puts it in the bank. | 20:18 |
saggi | We don't enforce all the data being in the bank | 20:18 |
*** shaohe_feng has quit IRC | 20:18 | |
saggi | but it must put information on where to find the data to the bank | 20:18 |
*** shaohe_feng has joined #openstack-meeting | 20:19 | |
saggi | so when we restore we give that information to the plugin | 20:19 |
dhellmann | ok, I understand protectables and banks, but I don't understand protections then | 20:19 |
ttx | Personally I feel like it's a weird mix of very cloudy stuff (advanced service driven by an API) but which would likely be used on very non-cloud-native apps, but then we are no longer judging the usefulness. | 20:19 |
annegentle | saggi: I'm worried this is a really different way to use the term plugin. | 20:19 |
annegentle | ttx: I had that concern as well, that if you use this, you create pet apps even. | 20:19 |
annegentle | ttx: rather than using cloudy architectures | 20:19 |
sdague | annegentle: pet apps are fine | 20:20 |
saggi | annegentle: pet apps? | 20:20 |
russellb | looks like there's just a swift bank plugin today? | 20:20 |
saggi | yes | 20:20 |
annegentle | saggi: using the "pets vs cattle" analogy, does this mean you create apps that aren't cloudy? | 20:20 |
dims | saggi : what changes if any are needed in other projects for smaug to work (or work better). | 20:20 |
sdague | the value of openstack is that it spans the whole gambit | 20:20 |
annegentle | saggi: and therefore pet apps | 20:20 |
russellb | protectable: a glance image. protection plugin: glance (it knows how to back up an image). bank: a place to store stuff, like swift | 20:20 |
russellb | is that a fair summary? | 20:20 |
oshidoshi | annegentle: pet apps are a possibility, many companies still use them, that's not necessarily a bad thing | 20:21 |
russellb | trying to make a tl;dr :) | 20:21 |
ttx | annegentle: yeah, pet apps are fine. It's just the combination of using a cloud API to drive data protection on a pet app that sounds alien. But then I guess with a UI on top... | 20:21 |
jbryce | sdague: +1 | 20:21 |
saggi | russellb: you are correct | 20:21 |
russellb | saggi: ok thanks | 20:21 |
flaper87 | russellb: I believe it is. I asked earlier today in smaug's channel whether it'd make sense for smaug to use glance_Store to be able to talk to more stores | 20:21 |
flaper87 | saggi: ^ | 20:21 |
oshidoshi | russleb: + | 20:21 |
dhellmann | russellb : thanks, that's clear | 20:21 |
flaper87 | The answer was yes, and it can be implemented as a bank | 20:21 |
dims | russellb : thanks for that. makes it clearer | 20:22 |
dhellmann | sdague : s/gambit/gamut/ | 20:22 |
sdague | dhellmann: sure, that too :) | 20:22 |
russellb | ha | 20:22 |
dims | haha | 20:22 |
saggi | As far as pets vs cattle. Backing up and restoring glance images and network topology is important regardless. | 20:22 |
dhellmann | although some may say openstack is a gambit of sorts | 20:23 |
saggi | Also, since we don't limit the entities you want to protect you can also back up your heat templates. | 20:23 |
sdague | right, I think we decided a while ago that we were not going to focus on "perceived usefulness" and instead let projects play out and find their community or not | 20:23 |
ttx | Still short of a few votes. Any other questions you'd like to ask saggi ? | 20:23 |
dims | sdague ++ | 20:23 |
annegentle | sdague: yeah, still was curious | 20:23 |
johnthetubaguy | sdague +1 | 20:23 |
dhellmann | sdague : ++ | 20:24 |
sdague | this doesn't really overlap anything other projects are doing, definitely seems like some users want it | 20:24 |
* dims votes | 20:24 | |
dhellmann | saggi : thanks for clarifying the technical stuff | 20:24 |
amrith | do I understand correctly that this backs up not just the data but the metadata in openstack as well? | 20:24 |
annegentle | saggi: again, is this service intended for admins or app devs? | 20:24 |
russellb | i think the dependency graph approach to backup of different resources is interesting | 20:24 |
saggi | admins | 20:24 |
annegentle | saggi: or maybe I missed it, I'm on a terrible IRC client :) | 20:24 |
amrith | i.e. would it be used to backup an openstack deployment? | 20:24 |
russellb | happy to see it explored | 20:24 |
*** sarob has joined #openstack-meeting | 20:24 | |
saggi | but also tenant admins | 20:24 |
amrith | or to backup, say a database running in the openstack cloud? | 20:24 |
* dims sees amrith worry/think about trove's backup capabilities | 20:25 | |
saggi | amrith: The deployment, it might include backing up the DB in an optimized way. | 20:25 |
amrith | am wondering how this is different from, for example, snapshots of a cinder volume directly. | 20:25 |
Rockyg | saggi, ++ | 20:25 |
saggi | This is where cooperation with freezer comes into play | 20:25 |
thingee | ttx: o/ | 20:25 |
russellb | amitry: because it captures more than cinder volumes, and the relationships between them | 20:25 |
ttx | We now have a majority | 20:25 |
dhellmann | amrith : it includes the metadata, and relationships between objects, so you can restore all of that rather than just bits on a volume | 20:25 |
*** prashantD_ has joined #openstack-meeting | 20:25 | |
russellb | hopefully not duplicating the actual work of volume backup necessarily | 20:26 |
amrith | dhellmann, I'm trying to wrap my head around a practical use case | 20:26 |
*** flwang has joined #openstack-meeting | 20:26 | |
*** banix has quit IRC | 20:26 | |
russellb | anyway, that's a detail :) | 20:26 |
saggi | Classically you back up storage and make scripts. We want to eliminate the need for scripts. | 20:26 |
amrith | and finding it hard to relate smaug to a database | 20:26 |
ttx | keeping in mind it's pretty young at this stage | 20:26 |
*** noslzzp has quit IRC | 20:26 | |
amrith | managed by an admin or trove. | 20:26 |
amrith | so I'm wondering whether maybe databases are not the right target. | 20:26 |
amrith | for example, in a database there's config information and data | 20:26 |
amrith | and I'm wondering how one would express that to smaug | 20:26 |
amrith | and how smaug would, for example, know to quiesce a database and take a transaction consistent backup | 20:27 |
amrith | in a way that would be better than whatever the database vendor provides | 20:27 |
dhellmann | I think that's getting deeper into the tech than we need to. | 20:27 |
jroll | amrith: sounds like it's more, back up your flavors and such | 20:27 |
flaper87 | tbh, I think it's fine to explore all those questions after the meeting | 20:27 |
dims | ++ flaper87 | 20:27 |
saggi | amrith: We do it because the DB protectable will tell us it depends on the VM | 20:27 |
*** mriedem1 has joined #openstack-meeting | 20:27 | |
dhellmann | amrith : as a cloud user, I do not have access to my cloud provider's database backups | 20:27 |
saggi | this is where the relationships come into play | 20:27 |
amrith | will take it offline | 20:27 |
*** pabelanger has left #openstack-meeting | 20:27 | |
oshidoshi | amrith: you are welcome to contact us on our irc, we'll be happy to discuss | 20:28 |
dims | saggi : thanks! | 20:28 |
ttx | amrith: thx! | 20:28 |
*** prashantD has quit IRC | 20:28 | |
amrith | saggi, flaper87 dims dhellmann ... wondering how trove can use smaug. thanks! | 20:28 |
ttx | OK, approving now unless someone screams | 20:28 |
*** sarob has quit IRC | 20:28 | |
*** sarob has joined #openstack-meeting | 20:28 | |
annegentle | ttx: got my vote in | 20:28 |
*** jichen has quit IRC | 20:28 | |
*** shaohe_feng has quit IRC | 20:29 | |
ttx | approved | 20:29 |
saggi | We have docs about how we traverse the resource tree and build the task graph to make dependent tasks between resources happen. | 20:29 |
ttx | saggi: welcome | 20:29 |
Rockyg | Congratz! | 20:29 |
*** e0ne has quit IRC | 20:29 | |
saggi | horray! | 20:29 |
saggi | Thanks everyone | 20:29 |
annegentle | thanks saggi ! | 20:29 |
*** samleon has quit IRC | 20:29 | |
oshidoshi | thanks guys | 20:29 |
oshidoshi | and gals | 20:29 |
amrith | thx saggi will catch you later | 20:29 |
ttx | #topic Updates projects.yaml to indicate type:service only if a REST API is provided | 20:29 |
*** openstack changes topic to "Updates projects.yaml to indicate type:service only if a REST API is provided (Meeting topic: tc)" | 20:29 | |
ttx | #link https://review.openstack.org/317094 | 20:29 |
ttx | So... I raised this one since I'm not sure we want to overload the governance projects.yaml in this way | 20:29 |
*** shaohe_feng has joined #openstack-meeting | 20:30 | |
ttx | On this one Anne suggests we limit type:service to things which provide a REST service endpoint, so that it could be reused to build API doc links | 20:30 |
ttx | That results in removing it from Horizon, which I could agree with | 20:30 |
ttx | But I have three objections | 20:30 |
annegentle | ttx: I originally wanted a handy way to scan for "does this provide an API?" | 20:30 |
ttx | 1/ it implies that type:service is redefined, since Horizon fills the "provides a user-facing long-running service, usually with a REST API" requirement | 20:30 |
*** mriedem has quit IRC | 20:30 | |
annegentle | but fine with abandoning and going the "discover REST API docs" route | 20:30 |
ttx | 2/ it uses a deliverable type tag to specify something which is more of a technical property of a specific component (we have "deliverables" which provide multiple REST API endpoints) | 20:30 |
*** priteau has joined #openstack-meeting | 20:30 | |
ttx | 3/ it's a bit of a slippery slope to add extra type of data to projects.yaml, especially data which is not directly consumed by humans. It's not a service catalog imho | 20:31 |
annegentle | ttx: agreed on all 3 | 20:31 |
ttx | annegentle: ok cool :) | 20:31 |
annegentle | :) | 20:31 |
fungi | not to be pedantic, but whether a long-running service provides an api (rather than just ui) and what protocol is used for that api seem like separate facets too | 20:31 |
*** pradk has quit IRC | 20:31 | |
annegentle | if anyone has ideas for how to discover what API docs are where for each service please tell me :) | 20:32 |
*** mriedem1 is now known as mriedem | 20:32 | |
mtreinish | ttx: so add a provides:rest_api tag? | 20:32 |
ttx | fungi: hence the "usually" | 20:32 |
* dims nods to fungi's comment | 20:32 | |
annegentle | mtreinish: I think I'll do a docs: -api: http://blah url | 20:32 |
ttx | mtreinish: I don't think that would be useful | 20:32 |
annegentle | mtreinish: per deliverable | 20:32 |
fungi | mtreinish's suggestion is what i was thinking of as well | 20:32 |
ttx | my suggestion here would be to either extend the YAML grammar to make room for a list of APIs provided by the project team / deliverable / repository | 20:33 |
thingee | +1 | 20:33 |
dhellmann | yeah, if the point of this is to link to API docs, let's just do the simple thing and add the links. | 20:33 |
annegentle | would that idea work - per deliverable, does it have an API, and where are the docs? | 20:33 |
ttx | or move that to another repository / YAML file | 20:33 |
anteaya | dhellmann: ++ | 20:33 |
ttx | annegentle: the trick being some of those deliverable maybe propose multiple APIs (not sure) | 20:33 |
annegentle | dhellmann: one goal is to figure out which services we need to provide nav to on an API docs site | 20:33 |
fungi | i agree that this isn't something which necessarily needs describing and tracking by the tc (hence a governance tag) | 20:33 |
mtreinish | annegentle: I think having a link per deliverable would work fine | 20:33 |
dims | +1 to another repository / yaml file (maintained by doc team?) | 20:34 |
annegentle | ttx: eesh. well ok | 20:34 |
annegentle | dims: ugh. hm | 20:34 |
mtreinish | ttx: if there are multiple apis they can have a single doc still | 20:34 |
sdague | dims: if we go down that route, I think realistically we already have a different solution | 20:34 |
annegentle | dims: I mean docs already have to figure this out from non-truth-sources. I see projects.yaml as a source of truth. | 20:34 |
dhellmann | annegentle : sure. so maybe a deliverable tag here, and then when it comes to making sure those docs are linked elsewhere we can figure out the details of what "has an api" means for that deliverable? | 20:34 |
sdague | because we have a repo for the service types list, which went on hold when we actually hit this hard question | 20:34 |
annegentle | dhellmann: I like per-deliverable | 20:34 |
*** singhj has quit IRC | 20:34 | |
sdague | that api doc links weren't obvious | 20:34 |
* dims thinking | 20:34 | |
annegentle | sdague: yeah that too | 20:34 |
*** cody-somerville has quit IRC | 20:35 | |
dims | we need a tag and a url to where the api docs are? | 20:35 |
ttx | ok, so extend grammar to add collection of API doc links | 20:35 |
sdague | annegentle: if this is mostly just for api site nav, I think we probably should revive the service types authority and do that there | 20:35 |
ttx | dims: doesn't have to be a tag, especially if it needs to have a value | 20:35 |
mugsie | sdague: ++ | 20:35 |
dhellmann | do we need to keep a tag, or do we just need to review what we have in these repos one time so we can manage the links elsewhere? | 20:35 |
*** yuval has quit IRC | 20:36 | |
johnthetubaguy | sdague: oh, is that the stuff related to the service catalog? | 20:36 |
ttx | sdague: yeah, that was what I was hinting at | 20:36 |
annegentle | sdague: it's for nav, for outreach to teams... discoverability (how does anyone figure this out?) | 20:36 |
sdague | johnthetubaguy: yeh, it's been on a hiatus because api-ref was related and more important | 20:36 |
dhellmann | so maybe the tag is "has contributed their info to the service catalog working group"? | 20:36 |
dims | dhellmann : the "team" concept in releases/ repo ... | 20:36 |
*** jaugustine has quit IRC | 20:36 | |
ttx | dhellmann: in all cases I'd say it would not end up being a tag. Could be some new key on the YAML grammar | 20:36 |
johnthetubaguy | sdague: yeah, I see what you mean, what we need is a list of OpenStack APIs and how to find them | 20:37 |
ttx | since we need it to have a value | 20:37 |
annegentle | I'm definitely abandoning the service:type patch. Would like ideas for docs including APIs | 20:37 |
dhellmann | ttx: it sounded like the value is going to be kept in that other repo, though? | 20:37 |
*** ssalagame has quit IRC | 20:37 | |
ttx | annegentle: maybe we can come up with a solution by discussing that offline between you, sdague and me ? | 20:37 |
*** jaugustine has joined #openstack-meeting | 20:38 | |
annegentle | dhellmann: hopefully not, ideally it'll be expanded and agreed upon after https://review.openstack.org/#/c/316396/ | 20:38 |
sdague | yeh, lets have an offline chat just to figure out if there is another approach here | 20:38 |
annegentle | ttx: yeah that works. | 20:38 |
* thingee cuts out for next flight back home | 20:38 | |
annegentle | ttx: it's not urgent this week for sure :) | 20:38 |
amrith | safe travels thingee | 20:38 |
*** ssalagame has joined #openstack-meeting | 20:38 | |
ttx | annegentle: maybe over emails so that we can think about our responses more :) | 20:39 |
annegentle | ttx: I like email. a lot. too much. | 20:39 |
anteaya | annegentle: so the problem is in creating the motivation for projects to come to you with links? | 20:39 |
*** shaohe_feng has quit IRC | 20:39 | |
ttx | annegentle: could be a -dev thread | 20:39 |
*** cbouch_ has joined #openstack-meeting | 20:39 | |
annegentle | anteaya: problem space is varied :) discoverability, readability, navigation, and source-of-truth | 20:39 |
annegentle | ttx: yeah, ok | 20:39 |
*** cbouch has quit IRC | 20:39 | |
anteaya | annegentle: okay thanks | 20:39 |
ttx | ok, we have several topics to discuss in open discussion, so I'll move on | 20:39 |
dims | annegentle : not a small task for sure. thanks! | 20:40 |
ttx | annegentle: starting with describing all the goals sounds like a good start | 20:40 |
annegentle | heh | 20:40 |
ttx | #topic Open discussion | 20:40 |
annegentle | I'm a conflater. sigh. | 20:40 |
*** openstack changes topic to "Open discussion (Meeting topic: tc)" | 20:40 | |
dhellmann | ttx: ++ | 20:40 |
ttx | morgan wanted to discuss data files defined in setup.cfg and sdague the API rate limiting | 20:40 |
ttx | whoever speaks first wins | 20:40 |
*** cbouch__ has joined #openstack-meeting | 20:40 | |
notmorgan | o/ | 20:40 |
notmorgan | omg | 20:40 |
flaper87 | lol | 20:40 |
ttx | notmorgan wins by arguably cheating | 20:40 |
notmorgan | actually if sdague wants to go, i'll defer | 20:40 |
flaper87 | notmorgan: now you have to speak | 20:40 |
* dhellmann pictures confetti raining down on notmorgan | 20:40 | |
notmorgan | lol | 20:40 |
sdague | ok so my thing - http://lists.openstack.org/pipermail/openstack-operators/2016-June/010692.html | 20:40 |
flaper87 | LOL | 20:41 |
*** mickeys has joined #openstack-meeting | 20:41 | |
* notmorgan lets sdague talk | 20:41 | |
sdague | we used to have this toy rate limitter in nova | 20:41 |
*** jungleboyj has quit IRC | 20:41 | |
ttx | let's do sdague first to have one discussion at a time | 20:41 |
notmorgan | mine can wait until next week + have a resolution to governance | 20:41 |
notmorgan | if there is no time after | 20:41 |
sdague | which is now gone | 20:41 |
notmorgan | sdague: right. | 20:41 |
sdague | because it was a toy, and really bad. It was disabled in havana by default | 20:41 |
sdague | however, rate limiting is kind of a fundamentally important unit to API services with unknown users | 20:42 |
*** shaohe_feng has joined #openstack-meeting | 20:42 | |
*** singhj has joined #openstack-meeting | 20:42 | |
sdague | and it seems like we should try to figure out how to get our community on to the same, or a set of pages to collaborate there | 20:42 |
notmorgan | sdague: and i've see a number of bugs, some originally securiyt then made public, some just public around rate limiting. | 20:42 |
*** rfolco has quit IRC | 20:42 | |
dhellmann | so are you envisioning building our own version of something like https://pypi.python.org/pypi/turnstile ? | 20:42 |
fungi | case in point, the vmt fields numerous reports of "denial of service" vulnerabilities which boil down to no way to limit request volume | 20:42 |
ttx | sdague: the historical answer by the VMT was that this needs to be solved outside of openstack, so we avoided to consider rate-based attacks as vulnerabilities | 20:42 |
notmorgan | this has been a real thorn for a number of reasons. | 20:42 |
dhellmann | (which is old and apparently unmaintained) | 20:42 |
mtreinish | sdague: just thinking out loud, but can't you just do it in apache or whatever you use as a webserver? | 20:42 |
notmorgan | fungi: ++ | 20:42 |
dims | sdague : mod_ratelimit ? | 20:42 |
notmorgan | mtreinish: we can. | 20:43 |
mtreinish | and you're on your own if you decide to use eventlet as the server | 20:43 |
*** mrmartin has joined #openstack-meeting | 20:43 | |
dims | mtreinish : yep | 20:43 |
notmorgan | mtreinish: but regardless a clear message should be sent on how this is expected to work | 20:43 |
sdague | mtreinish: typically rate limitting for API services isn't just connects | 20:43 |
*** dfg_ has left #openstack-meeting | 20:43 | |
dhellmann | yeah, doesn't it have to be user- or project-aware? | 20:43 |
notmorgan | and this should be consistent across openstack - for pure connections, mod_ratelimit is good | 20:43 |
sdague | at least it wasn't in the toy implementation, or turnstile (which was Vek) | 20:43 |
*** cbouch_ has quit IRC | 20:43 | |
flaper87 | I've heard different opinions on this but I believe the general consensus among those opinions is that we shouldn't do it ourselves but instead let balancers/http servers do it. | 20:43 |
notmorgan | but for other things we should have a clear direction: this is what is looks like in openstack | 20:44 |
flaper87 | This might be an issue for some projects, of course | 20:44 |
amrith | sdague, as I said in email, one thought I had a couple of months ago was to have the delimiter project cover this. Looking at the history, Jay didn't like that idea. | 20:44 |
fungi | yeah, we've (vmt) traditionally punted rate limiter shortcomings to needing documentation/pointers to separate solutions | 20:44 |
sdague | because not every METHOD /PATH are the same cost | 20:44 |
notmorgan | because this is something that should be absolutely consistent in style across openstack (even if some things are more heavily limited than others) | 20:44 |
notmorgan | sdague: so the real issue here is going to be IPC. and house keeping. imo | 20:44 |
notmorgan | anyone can implement (toy or otherwise a rate limiter) | 20:45 |
*** jjmorman has quit IRC | 20:45 | |
sdague | dhellmann: it would only need to be project aware in having regex paths + METHODS ... which is basically what turnstile does actually | 20:45 |
notmorgan | though i think the richness of nginx/apache/etc to specify per-path matching is going to be the right way | 20:45 |
dhellmann | ok | 20:45 |
notmorgan | pet-path-per-method | 20:45 |
sdague | it was more or less the memcache cluster version of the toy limitter in nova | 20:45 |
notmorgan | less so about "user/project" awareness. | 20:45 |
sdague | so... I guess here is the set of questions: | 20:45 |
*** roxanagh_ has joined #openstack-meeting | 20:45 | |
notmorgan | since apache, nginx, haproxy all know how to track the conections | 20:45 |
dhellmann | sdague : so the question is how to get people to work on it? | 20:45 |
*** ssalagame has quit IRC | 20:45 | |
sdague | 1) is it important that we have a consistent thing here? | 20:46 |
sdague | 2) is it acceptable to be documentation | 20:46 |
sdague | 3) is anyone interested in working in this space? | 20:46 |
notmorgan | 1) I say absolutely to. | 20:46 |
dhellmann | 1) yes 2) maybe 3) no myself | 20:46 |
notmorgan | 2) probably. | 20:46 |
flaper87 | 1) yes 2) sure 3) not me | 20:46 |
notmorgan | 3) if i have time, I'll contribute | 20:46 |
johnthetubaguy | I think it would be good to be consistent about how the API users sees they are rate limited, and that might be documentation(?) | 20:46 |
notmorgan | but i can't write / doc / code it all on my own. | 20:46 |
*** raildo is now known as raildo-afk | 20:47 | |
dhellmann | I could also see it being helpful to build something that's aware of our API and user definition, though it seems like it wouldn't be too hard to make it generic. | 20:47 |
sdague | dhellmann: yeh, honestly, I think this could absolutely be pretty generic | 20:47 |
dhellmann | because if we build it, then we can include it in our interop testing | 20:47 |
dims | 1) yes 2) yes 3) no | 20:47 |
mtreinish | 1. yes, 2. I think so, 3. someone is always willing to work on something | 20:47 |
sdague | mtreinish: I would argue with your answer on 3 | 20:47 |
dhellmann | mtreinish : I know a lot of counter examples to #3 | 20:48 |
sdague | dhellmann: ++ | 20:48 |
annegentle | sdague: 1) I don't think it's as important because large cloud providers already solved it in ways that make sense to their ops teams and with the resources they have. | 20:48 |
dhellmann | sdague : is this the first example of the TC saying "we want X to exist, someone please make that"? | 20:48 |
sdague | annegentle: so every new cloud has to solve it for themselves? | 20:48 |
amrith | annegentle makes an interesting point. | 20:48 |
annegentle | 2) documentation can be generic as http://developer.openstack.org/api-guide/compute/limits.html is already | 20:48 |
mtreinish | heh, fair enough. I didn't mean to imply we ask and they show up. I meant more people pick weird things to work on and find interesting | 20:49 |
jroll | someone has done this before, but it's in java: http://www.openrepose.org/ | 20:49 |
annegentle | 3) there are many unsolved problems in OpenStack I don't think we would prioritize this one over others? | 20:49 |
dims | annegentle : Amen | 20:49 |
*** shaohe_feng has quit IRC | 20:49 | |
notmorgan | sdague: we have documentation being proposed in one of the projects that covers a lot of this | 20:49 |
dhellmann | mtreinish : that I agree with. | 20:49 |
edleafe | annegentle: especially when solutions already exist | 20:49 |
notmorgan | i think keystone maybe? | 20:49 |
notmorgan | we can probably adapt it | 20:49 |
notmorgan | more globally | 20:49 |
johnthetubaguy | so I don't think we should create a rate limiter, but I think we should help our users with rate limiting | 20:49 |
annegentle | sdague: they do now, and docs would be the biggest help since there are myriad considerations | 20:49 |
ttx | I'm with johnthetubaguy | 20:49 |
sdague | johnthetubaguy: yeh, that is probably the best path forward | 20:50 |
annegentle | johnthetubaguy: yeah, that's my sentiment as well | 20:50 |
ttx | Produce doc on how to solve rate limiting consistently | 20:50 |
*** roxanagh_ has quit IRC | 20:50 | |
flaper87 | And we should probably start by asking the OPs team how they do it | 20:50 |
johnthetubaguy | that might be more effort than building one, but I think our users will be happier afterwards! | 20:50 |
*** shaohe_feng has joined #openstack-meeting | 20:50 | |
annegentle | flaper87: yep that thread is started | 20:50 |
sdague | so... the seeds we have is keystone is writing up approaches based on apache, which should be applicable across the board, we start there? | 20:50 |
sdague | flaper87: see the link I posted | 20:50 |
ttx | It feels like something that could be driven from the ops side | 20:50 |
* flaper87 scrolls back | 20:50 | |
dims | sdague : sounds like a good plan | 20:50 |
johnthetubaguy | sdague: I like the apache base idea | 20:50 |
sdague | http://lists.openstack.org/pipermail/openstack-operators/2016-June/010692.html | 20:51 |
*** cbouch__ has quit IRC | 20:51 | |
*** _nadya_ has joined #openstack-meeting | 20:51 | |
flaper87 | my bad, missed it | 20:51 |
flaper87 | thanks | 20:51 |
ttx | sdague: yes, that's the right start | 20:51 |
fungi | i think some members of the security project team may also be useful resources for collaboration on protective rate limiting for openstack rest apis | 20:51 |
sdague | notmorgan: could you get into that thread and speak up about docs being built on the keystone side? | 20:51 |
dhellmann | sdague : ++ | 20:51 |
dhellmann | fungi : ++ | 20:51 |
*** oshidoshi has quit IRC | 20:51 | |
fungi | i know there's been some exploration in the space from their end | 20:51 |
ttx | fungi: yes they mentioned several options over time in OSSNs | 20:51 |
dims | fungi : +1 | 20:51 |
sdague | ok, so I think we'll be agreed that the ops thread should probably be the right place to keep this conversation going | 20:52 |
ttx | https://wiki.openstack.org/wiki/OSSN/OSSN-0008 | 20:52 |
sdague | and that as the TC we feel it's important there is some standard story here for folks | 20:52 |
flaper87 | sdague: yes | 20:52 |
*** mrmartin has quit IRC | 20:52 | |
flaper87 | ++ | 20:52 |
sdague | and we'll see if we can convince the keystone folks to solve it in docs for the rest of us? :) | 20:52 |
notmorgan | sdague: i'm ting to find it | 20:53 |
notmorgan | it's actually a review | 20:53 |
flaper87 | yup, and we should collect the output of that thread and document it somewhere | 20:53 |
dims | :) | 20:53 |
notmorgan | but it's hiding somewhere | 20:53 |
flaper87 | and notmorgan will do everything here | 20:53 |
sdague | \o/ | 20:53 |
ttx | notmorgan: you have 5 minutes for your topic if you think it's sufficient | 20:53 |
flaper87 | ttx: he's documenting the rate limit stuff... don't interrupt | 20:53 |
notmorgan | sure | 20:53 |
notmorgan | ttx: it's easy topic | 20:53 |
ttx | flaper87: I counted 2 minutes for that | 20:53 |
flaper87 | last famous words | 20:54 |
flaper87 | ttx: oh, ok | 20:54 |
flaper87 | :D | 20:54 |
*** longxiongqiu has joined #openstack-meeting | 20:54 | |
*** mbound has quit IRC | 20:54 | |
notmorgan | #link https://review.openstack.org/#/c/326152/ | 20:54 |
*** thorst has quit IRC | 20:54 | |
notmorgan | so we've seen changes go in to install config files with stup | 20:54 |
notmorgan | setup* | 20:54 |
notmorgan | also | 20:54 |
notmorgan | #link http://lists.openstack.org/pipermail/openstack-dev/2016-June/097123.html | 20:55 |
*** thorst has joined #openstack-meeting | 20:55 | |
notmorgan | basically, we, as the TC (imo) need to step in here and say explicitly "these are not data files we support" or "we should support, and do this with your data files for config" | 20:55 |
*** rbak has joined #openstack-meeting | 20:55 | |
notmorgan | simply | 20:55 |
notmorgan | i am in the camp personally of "don't install config with setup" | 20:55 |
notmorgan | we can have a tool to install it for you | 20:55 |
notmorgan | for venv, etc | 20:55 |
notmorgan | but it shouldn't be "setup", pbr, etc | 20:56 |
* flaper87 is in that camp too | 20:56 | |
notmorgan | specifically lifeless and mordred's responses to the thread | 20:56 |
ttx | these are not the data files you're looking for | 20:56 |
notmorgan | i'll propose a governance guideline to make sure we, as openstack, say "this is infact what data is" | 20:56 |
*** rbowen has quit IRC | 20:56 | |
dhellmann | yeah, the fact that it doesn't work consistently and correctly means we shouldn't do it, at least for now | 20:56 |
notmorgan | when you use data-files. | 20:56 |
notmorgan | we can change that later | 20:56 |
mtreinish | notmorgan: what about something like cli tooling that depends on data files? | 20:56 |
notmorgan | but i want this to be explicitly consistent | 20:56 |
notmorgan | mtreinish: "data files" are not "config files" | 20:56 |
notmorgan | we can have data files. | 20:57 |
dhellmann | we have the config generator for creating config files | 20:57 |
*** ayoung_ has quit IRC | 20:57 | |
* jroll is also in the notmorgan camp fwiw | 20:57 | |
*** oneswig has joined #openstack-meeting | 20:57 | |
notmorgan | but config files themselves should not be installed with pip/setup in /etc /usr/stc/ usr/share... etc | 20:57 |
*** ayoung has quit IRC | 20:57 | |
notmorgan | that isn't our call and it ends up inconsistent. | 20:57 |
sdague | notmorgan: so, curiously, we've got a big giant upgrade problem with privsep because of this stance | 20:57 |
notmorgan | depending on wheel, etc. | 20:57 |
mtreinish | dhellmann: well except the oslo config generator depends on a config file :) | 20:57 |
sdague | which blocked os-brick 1.4 | 20:57 |
*** jonmills has joined #openstack-meeting | 20:57 | |
notmorgan | sdague: i think we should have a clear tool for this. heck, i'll help write one | 20:57 |
sdague | http://lists.openstack.org/pipermail/openstack-dev/2016-June/097293.html | 20:57 |
*** mbound has joined #openstack-meeting | 20:58 | |
dhellmann | mtreinish : that config file can actually be delivered as a data file in the app, because it's data and not meant to be edited by the user | 20:58 |
*** MaxPC has quit IRC | 20:58 | |
*** longxiongqiu has quit IRC | 20:58 | |
*** jmckind has quit IRC | 20:58 | |
ttx | should that be a cross-project spec ? | 20:59 |
*** jaugustine has quit IRC | 20:59 | |
sdague | so while I understand the concerns about python managing etc files, because it does so terribly | 20:59 |
*** rtheis has quit IRC | 20:59 | |
ttx | Feels more appropriate than a TC resolution | 20:59 |
notmorgan | sdague: uhm. that is a case where frankly upgrade can't be "pip install" | 20:59 |
fungi | i strongly agree that non-configuration should not be expected in /etc | 20:59 |
flaper87 | ttx: ++ | 20:59 |
fungi | with my long-time sysadmin hat on | 20:59 |
*** thorst has quit IRC | 20:59 | |
*** shaohe_feng has quit IRC | 20:59 | |
ttx | bottom-up rather than top-down | 20:59 |
notmorgan | fungi: wht about configuration being installed from pip? | 20:59 |
sdague | notmorgan: so ... we've architected to break CD for everyone, which is what you are saying? | 20:59 |
*** _nadya_ has quit IRC | 20:59 | |
*** jmlowe has joined #openstack-meeting | 20:59 | |
dhellmann | fungi : I think the point here is rather that we shouldn't try to ship config files to be installed with python packages | 21:00 |
notmorgan | sdague: basically we need to work another way to do that | 21:00 |
fungi | notmorgan: pip doesn't know how, so no problem there? | 21:00 |
notmorgan | fungi: ++ | 21:00 |
flaper87 | time check | 21:00 |
fungi | install sample configurations as data | 21:00 |
ttx | feels like we'll need to continue this one on the thread | 21:00 |
notmorgan | sdague: please respond to the thread i linked, and we'll need to continue | 21:00 |
notmorgan | i didn't expect this to be resolved this week | 21:00 |
*** craigs has joined #openstack-meeting | 21:00 | |
notmorgan | i just wanted to flag it for attention :) | 21:00 |
fungi | distros already commonly do this when there is no sane out-of-the-box default config | 21:00 |
ttx | alrighty | 21:00 |
dims | notmorgan : ack. need to think more about it | 21:00 |
*** rbudden has joined #openstack-meeting | 21:01 | |
*** cody-somerville has joined #openstack-meeting | 21:01 | |
*** cody-somerville has quit IRC | 21:01 | |
*** cody-somerville has joined #openstack-meeting | 21:01 | |
notmorgan | thanks! | 21:01 |
*** jd__ has quit IRC | 21:01 | |
ttx | let's continue this on eon thread | 21:01 |
amrith | thanks ttx | 21:01 |
ttx | Thanks everyone | 21:01 |
ttx | #endmeeting | 21:01 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 21:01 | |
openstack | Meeting ended Tue Jun 14 21:01:16 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 21:01 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-06-14-20.01.html | 21:01 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-06-14-20.01.txt | 21:01 |
openstack | Log: http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-06-14-20.01.log.html | 21:01 |
*** jd__ has joined #openstack-meeting | 21:01 | |
*** eharney has quit IRC | 21:01 | |
notmorgan | sdague: and i hear your concern, i want to find a way to work through that but i just don't trust pip [or anything] to install sudo rules for example :) | 21:01 |
*** bIairo has joined #openstack-meeting | 21:01 | |
notmorgan | short of a distro package [that is out of our hands] | 21:01 |
sdague | notmorgan: sure, I'm fine with that | 21:01 |
oneswig | You there Blair? | 21:02 |
bIairo | hi oneswig | 21:02 |
fungi | i _maybe_ trust my distro to do itt | 21:02 |
*** leong has joined #openstack-meeting | 21:02 | |
notmorgan | sdague: so i'll think about how to handle these cases as well :) | 21:02 |
*** bIairo is now known as b1airo | 21:02 | |
oneswig | bIairo: another week, another nick! | 21:02 |
leong | o/ | 21:02 |
*** dfflanders has joined #openstack-meeting | 21:02 | |
*** shaohe_feng has joined #openstack-meeting | 21:02 | |
b1airo | can't get onto my znc bouncer this morning :-( | 21:02 |
sdague | notmorgan: taking to -dev | 21:02 |
b1airo | @startmeeting scientific-wg | 21:03 |
b1airo | #startmeeting scientific-wg | 21:03 |
openstack | Meeting started Tue Jun 14 21:03:24 2016 UTC and is due to finish in 60 minutes. The chair is b1airo. Information about MeetBot at http://wiki.debian.org/MeetBot. | 21:03 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 21:03 |
b1airo | oops | 21:03 |
*** openstack changes topic to " (Meeting topic: scientific-wg)" | 21:03 | |
openstack | The meeting name has been set to 'scientific_wg' | 21:03 |
b1airo | #chair oneswig | 21:03 |
openstack | Current chairs: b1airo oneswig | 21:03 |
*** csomerville has joined #openstack-meeting | 21:03 | |
oneswig | #link https://wiki.openstack.org/wiki/Scientific_working_group#IRC_Meeting_June_14th_2016 This week's agenda | 21:03 |
*** darrenc is now known as darrenc_afk | 21:03 | |
oneswig | Hello everyone | 21:04 |
rbudden | hello | 21:04 |
jonmills | Howdy | 21:04 |
oneswig | #topic roll-call | 21:04 |
*** openstack changes topic to "roll-call (Meeting topic: scientific-wg)" | 21:04 | |
jmlowe | Hello | 21:04 |
leong | o/ | 21:04 |
*** gordc has left #openstack-meeting | 21:04 | |
dfflanders | G'Day | 21:04 |
b1airo | does pasting the agenda work oneswig ? let's find out... | 21:04 |
craigs | o/ | 21:04 |
b1airo | IRC Meeting June 14th 2016 | 21:04 |
b1airo | 2016-06-14 2100 UTC in channel #openstack-meeting | 21:04 |
b1airo | New items: | 21:04 |
b1airo | Scientific OpenStack at Supercomputing 2016. OpenStack activities related to HPC and research computing at the annual Supercomputing conference in Salt Lake City in November. | 21:04 |
b1airo | Panel session on OpenStack for HPC & research computing | 21:04 |
b1airo | Proposal for a Birds-of-Feather session | 21:04 |
b1airo | White paper on OpenStack and HPC | 21:04 |
b1airo | Carried over from last meeting: | 21:04 |
b1airo | Bare metal | 21:04 |
b1airo | Feature development for Newton cycle | 21:04 |
b1airo | Parallel filesystems | 21:04 |
b1airo | Looking for a lead for this activity area | 21:05 |
b1airo | Accounting and scheduling | 21:05 |
b1airo | Looking for a lead for this activity area | 21:05 |
b1airo | Other business | 21:05 |
oneswig | You're just in it for the line count on eavesdrop, I shall retaliate with man bash | 21:05 |
b1airo | lol | 21:05 |
oneswig | :-) | 21:05 |
b1airo | brb - child has just thrown up on floor here :-/ | 21:05 |
anteaya | #link https://wiki.openstack.org/wiki/Scientific_working_group#IRC_Meeting_June_14th_2016 | 21:06 |
anteaya | for my benefit | 21:06 |
oneswig | Great, I think we are all pretty excited | 21:06 |
*** e0ne has joined #openstack-meeting | 21:06 | |
oneswig | anteaya: thanks | 21:06 |
oneswig | #topic SC2016 activities | 21:06 |
*** gyee has joined #openstack-meeting | 21:06 | |
*** openstack changes topic to "SC2016 activities (Meeting topic: scientific-wg)" | 21:06 | |
anteaya | oneswig: welcome | 21:06 |
oneswig | So, there are at least three things that might be going on at SC related to OpenStack | 21:06 |
*** cody-somerville has quit IRC | 21:07 | |
oneswig | The panel session organised by Bill Boas is first on the list | 21:07 |
Rockyg | o/ | 21:07 |
oneswig | The proposal for a birds-of-feather session | 21:07 |
*** aysyd has quit IRC | 21:08 | |
oneswig | And a whitepaper on OpenStack and HPC | 21:08 |
*** edtubill has quit IRC | 21:08 | |
b1airo | Bill is the planned moderator for that panel isn't he oneswig ? | 21:08 |
oneswig | dfflanders: will there be a booth? | 21:08 |
oneswig | Do you have a link to it on sc.org? | 21:08 |
dfflanders | we are trying to piggy back with someone who has one, we couldn't get one | 21:09 |
dfflanders | hoping UTSA might be able to help | 21:09 |
rbudden | PSC will have a booth, but I’m not sure I’m in the position to volunteer it ;) | 21:09 |
*** shaohe_feng has quit IRC | 21:10 | |
rbudden | I can always ask | 21:10 |
jmlowe | We have a large booth, grandfathered in from the late 90's, should I see if we can accommodate? | 21:10 |
b1airo | should try and have openstack stuff at every booth possible - tom has *lots* of stickers | 21:10 |
dfflanders | thank you rbudden | 21:10 |
*** shaohe_feng has joined #openstack-meeting | 21:10 | |
dfflanders | yes please jmlowe | 21:10 |
jonmills | NASA always has a booth. but also, I don't have authority to volunteer it. but I can ask... | 21:10 |
dfflanders | if anything we would like slots at booths to do mini trainings or the like? | 21:11 |
rbudden | rbudden: I’m sure we wouldn’t mind stickers, etc. and I will ask about the booth as well | 21:11 |
dfflanders | thank you jonmills | 21:11 |
rbudden | if we know more about what we’d like to do with a portion of booth space, etc. that would be good to know in advance | 21:11 |
dfflanders | options: stickers > whitepapers > banners > mini trainings | 21:12 |
jmlowe | I can volunteer room for stickers and other materials without asking, posters and displays will require checking | 21:12 |
oneswig | dfflanders: do you envisage openstack staff assisting with attending the 'mini-booth' | 21:12 |
*** yamahata has joined #openstack-meeting | 21:12 | |
jmlowe | booth space for demos is a go as well | 21:12 |
*** julim has quit IRC | 21:12 | |
dfflanders | yes myself and Chris will be in attendance | 21:12 |
jmlowe | just need to schedule the space for a few sessions | 21:13 |
oneswig | let me capture some actions | 21:13 |
*** piet has quit IRC | 21:14 | |
oneswig | #action jonmills jmlowe rbudden are at orgs that will have booths, enquire on the possibility of including some OpenStack content | 21:14 |
oneswig | #action dfflanders also investigate UTSA booth? | 21:15 |
*** bri365 has joined #openstack-meeting | 21:15 | |
oneswig | #topic SC2016 BoF | 21:16 |
*** openstack changes topic to "SC2016 BoF (Meeting topic: scientific-wg)" | 21:16 | |
b1airo | we sometimes jump on another aussie booth (e.g. with NCI), but i'm not across those plans yet | 21:16 |
priteau | Kate Keahey asked me to tell you that she will be happy to help organize activities at SC16 | 21:16 |
priteau | I assume we will have some Chameleon presence as well on TACC's booth | 21:16 |
oneswig | priteau: thanks! Is that through Chicago, Argonne or ? | 21:16 |
dfflanders | FTW | 21:16 |
b1airo | great thanks priteau - should we loop you into any such comms too? | 21:17 |
*** csomerville has quit IRC | 21:17 | |
priteau | b1airo: Rather Kate directly | 21:17 |
*** csomerville has joined #openstack-meeting | 21:18 | |
*** woodster_ has quit IRC | 21:18 | |
oneswig | Perhaps we form a distribution list including the SC participants here and Kate | 21:19 |
jonmills | +1 | 21:19 |
priteau | oneswig: We often have activities through the DoE booth | 21:19 |
*** shaohe_feng has quit IRC | 21:20 | |
oneswig | priteau: that's another interesting path, there are Openstack activities underway across the DoE | 21:20 |
*** shaohe_feng has joined #openstack-meeting | 21:20 | |
*** annegentle has quit IRC | 21:21 | |
oneswig | dfflanders: are you the point of contact in the Foundation for SC planning? | 21:21 |
dfflanders | yes that's fine as is Denise | 21:21 |
oneswig | #action oneswig to kick off an email distribution for SC planning discussions | 21:23 |
oneswig | I'll make sure you're all on it... | 21:23 |
oneswig | OK, Birds-of-a-feather? | 21:23 |
*** kzaitsev_mb has quit IRC | 21:24 | |
oneswig | jonmills: your previous BoF was more general but do we feel the scope can/should be narrowed to OpenStack? | 21:24 |
jonmills | Yeah, I'm in agreement. Last year we were trying to sneak in under the radar. | 21:25 |
*** sarob has quit IRC | 21:25 | |
jonmills | But the amount of interest, in my mind, justifies a dedicated topic | 21:25 |
oneswig | How big are the bof sessions typically at SC? | 21:25 |
b1airo | just got to looking at jonmills previous BoF format - looks the same as I was suggesting in email, i.e., short/lightening talks by a few folks and then open discussion with some possible guide questions | 21:26 |
b1airo | did that format work well jonmills ? | 21:26 |
jonmills | the discussion session was lively. very much so. a few of the presentations were rather dry. | 21:26 |
oneswig | b1airo: I think this is a good format. We can cover some of the capabilities members of this WG might rightly feel were worth sharing | 21:27 |
*** kzaitsev_mb has joined #openstack-meeting | 21:27 | |
jonmills | I would budget 2:1 discussion:presentation time | 21:27 |
*** amitgandhinz has quit IRC | 21:27 | |
*** amitgandhinz has joined #openstack-meeting | 21:27 | |
oneswig | Is the aim of a BoF more about sharing common problems or solutions do you think? | 21:28 |
jonmills | I think a challenge is going to be choosing the subtopics to discuss in BoF | 21:28 |
b1airo | sounds like good advice. do you have any feeling on what folks would be interested in hearing about in terms of presentations? i suspect high-level architecture overviews of real OpenStack+HPC deployments, what works, what doesn't? | 21:28 |
*** ivar-lazzaro has joined #openstack-meeting | 21:28 | |
anteaya | oneswig: BoF is just a gathering of folks with a common interest, you can do anything you want with the time | 21:29 |
*** leeantho has quit IRC | 21:29 | |
b1airo | oneswig, judging by the conversations in the DellXL/DellHPC forum i think there will be a lot of people testing the water | 21:29 |
jonmills | I'm very interested in the networking side of things. But we also have this topic of parallel filesystems that will find a sympathetic audience at SC | 21:29 |
b1airo | so the majority of the audience will probably not yet have any/much openstack experience | 21:29 |
rbudden | b1airo: +1 on the deployment scenario, i think people seeing how it’s currently being used in HPC will be of interest | 21:30 |
*** shaohe_feng has quit IRC | 21:30 | |
b1airo | jonmills, +1 (your email questions about network scaling are quite interesting to me as well) | 21:30 |
*** shaohe_feng has joined #openstack-meeting | 21:31 | |
dfflanders | The past three conferences have had more than 50% new to or never heard of OpenStack questions | 21:31 |
b1airo | rbudden, to flesh that idea out further i think we want to cover both virtualised and bare-metal openstacks there | 21:31 |
b1airo | dfflanders, you mean summit attendees? | 21:32 |
oneswig | b1airo: makes good sense, it's not one-size-fits-all after all | 21:32 |
jmlowe | +1 on bare metal vs virt, which one for which apps | 21:32 |
jonmills | @b1airo in terms of attendance, fire marshall was taking people out of the back of the room. You can't assume that the attendees are OpenStack newbies. Many will be those in existing HPC centers fighting to shoehorn OpenStack into the infrastructure | 21:32 |
dfflanders | different conferences: K8S, cloud foundry, pycon | 21:32 |
rbudden | b1airo: agreed. they both serve unique purposes in HPC | 21:32 |
oneswig | jmlowe: a worthy discussion on its own | 21:32 |
anteaya | as a note using @ in front of an irc nick is unnecessary | 21:33 |
b1airo | oneswig, jmlowe - and therein lays the problem for us in framing the BoF, so much to talk about! | 21:33 |
oneswig | jonmills: I think those people are tremendously useful, in that perhaps they have got this far by themselves and the community content could get them much further | 21:33 |
jmlowe | one existing deployment of each type, and a couple of apps they are best for | 21:34 |
*** edtubill has joined #openstack-meeting | 21:34 | |
jonmills | the BoF submission format I think allows you to guestimate the attendence, or room size. I wouldn't pick the smallest room | 21:34 |
oneswig | Do we have a volunteer for submitting the BoF proposal? | 21:35 |
jmlowe | I'd pick the biggest, having been very disappointed by being turned away at the door of the last one | 21:35 |
b1airo | oneswig, i think Bill was happy to coordinate the submission again | 21:36 |
jonmills | So I suggest a continuation of google doc shared editing, to construct the BoF submission | 21:36 |
b1airo | but we need to write the thing | 21:36 |
b1airo | jonmills, +1 | 21:36 |
dfflanders | I had 50ppl show up at PyCon for the training I did with zero promotion | 21:36 |
jonmills | and I'm willing to help contribute | 21:36 |
oneswig | jonmills: great and thanks | 21:36 |
dfflanders | Foundation will look to help promote given forthcoming whitepaper | 21:36 |
*** uxdanielle has quit IRC | 21:36 | |
jonmills | I can even submit it if you want, but it allows for listing co-contributors | 21:36 |
oneswig | b1airo: I think Bill was up for that too | 21:36 |
*** uxdanielle has joined #openstack-meeting | 21:37 | |
anteaya | does the group know about etherpad? https://etherpad.openstack.org/ an open source shared editing tool? | 21:37 |
oneswig | Lets follow up with Bill before we sign him up | 21:37 |
oneswig | anteaya: etherpad could be a good call here, better for multi-party editing | 21:37 |
anteaya | and open source! | 21:38 |
*** singhj has quit IRC | 21:38 | |
b1airo | anteaya, yes most of these folks were at the summit, but etherpad is not so good for building a doc i think | 21:38 |
jmlowe | anteaya: we used it several times in Austin, not so great for editing a paper for submission | 21:38 |
b1airo | i prefer commenting streams in gdoc | 21:38 |
jonmills | me too | 21:38 |
b1airo | but, i think we could use etherpad to good effect in the actual BoF session | 21:38 |
rbudden | etherpad would be handy maybe for notes from these meetings. I found them handy at the design summit session in Austin | 21:39 |
oneswig | I can do either... | 21:39 |
*** pradk has joined #openstack-meeting | 21:39 | |
*** jungleboyj has joined #openstack-meeting | 21:39 | |
jmlowe | organizing and brainstorming in prep for the bof submission would be a good use for etherpad | 21:39 |
rbudden | back on topic though, i’m available to contribute as well | 21:39 |
oneswig | rbudden: that's great | 21:39 |
*** cdelatte has quit IRC | 21:39 | |
persia | Seeing conference discussions: are there plans for anything at ISC-HPC next week? | 21:40 |
*** dweaver` has joined #openstack-meeting | 21:40 | |
*** shaohe_feng has quit IRC | 21:40 | |
*** singhj has joined #openstack-meeting | 21:40 | |
oneswig | So I think the consensus is we generate a google doc for submission and use etherpad's interactive strengths for meetings | 21:40 |
b1airo | hi persia - not that i'm aware of | 21:40 |
anteaya | persia: I do believe that is the topic under discussion | 21:40 |
anteaya | oh sorry | 21:41 |
dfflanders | persia wasn't on our radar, should it be? | 21:41 |
anteaya | persia: so many acryonyms, hard to keep track of them all | 21:41 |
oneswig | persia: nothing formal AFAIK but I'd be interested to hear? | 21:41 |
*** shaohe_feng has joined #openstack-meeting | 21:41 | |
b1airo | no doubt openstack will be part of a few papers presented there, but no specific sessions/groups that scientific-wg knows about | 21:41 |
b1airo | oneswig, agreed | 21:42 |
persia | dfflanders: probably late for this year, but my understanding is that it was kind of like SC Europe. I may be mistaken. | 21:42 |
oneswig | A couple of my colleagues are going and will be interested in OpenStack discussions there | 21:42 |
*** e0ne has quit IRC | 21:42 | |
b1airo | anteaya, no probs, just to clarify what we're talking about here is the Supercomputing Conference in November | 21:42 |
anteaya | b1airo: great thank you | 21:42 |
oneswig | persia: that's pretty much it | 21:42 |
anteaya | I had thought you were discussing the event next week | 21:42 |
b1airo | we submitted a panel proposal for that immediately following the summit and it was just accepted | 21:43 |
*** amitgandhinz has quit IRC | 21:43 | |
anteaya | b1airo: congratulations | 21:43 |
dfflanders | may we ask for some reports back persia oneswig so we can potentially go next year: number of ppl, hot topics, applicability to OS | 21:43 |
*** rderose has quit IRC | 21:43 | |
oneswig | persia: are you going? | 21:43 |
anteaya | dabukalam: is going | 21:44 |
persia | oneswig: yes, but unrelated to OpenStack. | 21:44 |
persia | dfflanders: happy to share. | 21:44 |
jmlowe | I went to ISC in 2011, my impression was that the exhibitor part was a fraction of the size but the academic portion of the conference was larger | 21:44 |
dfflanders | thank you persia | 21:44 |
oneswig | #action oneswig persia to report back on OpenStack activities and discussion at ISC next week | 21:44 |
b1airo | jmlowe, i've never been, but that's the 2nd hand impression i have too | 21:45 |
*** singhj has quit IRC | 21:45 | |
oneswig | OK, move on? | 21:45 |
dfflanders | jmlowe sounds promising especially for our scholarly app efforts | 21:45 |
jonmills | okay, so who is taking the action to launch the gdoc for the BoF and share the link to it? | 21:45 |
oneswig | jonmills: can you fork the layout of the last one? | 21:45 |
jonmills | I can | 21:46 |
*** Sukhdev has quit IRC | 21:46 | |
oneswig | That would be great, we can build on that I think | 21:46 |
b1airo | sounds good | 21:46 |
oneswig | Follow up with the upcoming distribution list for addresses to share | 21:46 |
oneswig | I'll note it | 21:47 |
oneswig | #action jonmills to fork previous submission for creating new submission for OpenStack/HPC BoF | 21:47 |
oneswig | Thanks Jon | 21:47 |
b1airo | suggest we paste in the panel proposal too and then go from there merging bits together and focusing more specifically on openstack. i think we can be explicit that this in an openstack scientific-wg outreach BoF? | 21:47 |
jonmills | np | 21:48 |
oneswig | b1airo: good plan | 21:48 |
dfflanders | +1 | 21:48 |
rbudden | b1airo: +1 | 21:48 |
oneswig | #topic SC2016 OpenStack/HPC whitepaper | 21:48 |
*** openstack changes topic to "SC2016 OpenStack/HPC whitepaper (Meeting topic: scientific-wg)" | 21:48 | |
oneswig | We've had previous discussions touching on this, I wanted to share an example of the kind of material the Foundation can produce: | 21:49 |
b1airo | so this is an SC thing now oneswig ? | 21:49 |
oneswig | #link https://www.openstack.org/assets/pdf-downloads/Containers-and-OpenStack.pdf example whitepaper on containers | 21:49 |
b1airo | or are we just aiming to have something released around that time? | 21:50 |
oneswig | b1airo: I think the Foundation wants it in time for SC, right dfflanders | 21:50 |
dfflanders | y | 21:50 |
dfflanders | launch at SC, not an SC thing | 21:50 |
oneswig | My coincidence is that I'm contracted to deliver something similar for Cambridge Uni earlier, and feed that into the foundation's efforts | 21:50 |
*** shaohe_feng has quit IRC | 21:51 | |
dfflanders | win win ;-) | 21:51 |
*** sileht has quit IRC | 21:51 | |
oneswig | In theory yes! | 21:51 |
*** shaohe_feng has joined #openstack-meeting | 21:51 | |
b1airo | hmm, anybody else get the TLDR feeling when looking at something like that in pdf form? | 21:51 |
*** sileht has joined #openstack-meeting | 21:52 | |
*** singhj has joined #openstack-meeting | 21:52 | |
jonmills | Well my eyes glaze over when I see marketing-looking stuff. I wanna see CLI commands LOL | 21:52 |
rbudden | lol | 21:53 |
anteaya | b1airo: I don't know whitepapers, how long are they usually? | 21:53 |
oneswig | b1airo: I like the content of the containers paper, but it's not instantly grabbing. There's more information in here than most booth content | 21:53 |
b1airo | i'm with you jonmills - i'm just so used to "whitepapers" being marketing fluff | 21:53 |
dfflanders | depends on audience, CIO/CTOs will read, dev no. Would be interesting to explore other non-PDF formats? | 21:53 |
*** sarob has joined #openstack-meeting | 21:53 | |
anteaya | yeah, I really would like to ensure this retains the integrity of meeting the needs of the scientific working group as to style and presentation | 21:53 |
*** darrenc_afk is now known as darrenc | 21:54 | |
b1airo | oneswig, yes it looks like there is decent content here, but i feel like it should be published as an online doc too. big problem is there is no index, which for 19 pages is not so great | 21:54 |
dfflanders | aside: been playing with gitbooks recently... though content first, format anon? | 21:54 |
oneswig | I'd prefer something thorough - agree on the online format - surely room for both | 21:54 |
oneswig | I had quality time today with sphinx-doc... | 21:55 |
anteaya | oneswig: how did it go? | 21:55 |
*** sbalukoff_ has joined #openstack-meeting | 21:55 | |
oneswig | the hours flew by! | 21:55 |
anteaya | oneswig: dhellmann is a great sphinx resource | 21:55 |
anteaya | oneswig: I bet | 21:55 |
b1airo | oneswig: lol | 21:55 |
dfflanders | I think the foundation would really like to see some of the members of scientific-wg willing to have interviews so we can publish case studies? | 21:55 |
dfflanders | ^^ does that sound content worthy? <-- @oneswig for your plans as well? | 21:56 |
*** csomerville has quit IRC | 21:56 | |
*** prashantD__ has joined #openstack-meeting | 21:56 | |
b1airo | and to clarify, dfflanders means other than oneswig and i (i think) | 21:56 |
*** kylek3h has quit IRC | 21:56 | |
anteaya | I thought the scientific working group has an subteam to publish case studies/user stories | 21:56 |
anteaya | or am I confused | 21:56 |
oneswig | I have the idea that we generate a paper as a collection of case studies for specific HPC capabilities. That way you get a comprehensive big study or a library of two-pagers | 21:57 |
b1airo | anteaya, correct | 21:57 |
*** csomerville has joined #openstack-meeting | 21:57 | |
dfflanders | +1 | 21:57 |
anteaya | okay thanks | 21:57 |
b1airo | #topic Other Business | 21:57 |
*** openstack changes topic to "Other Business (Meeting topic: scientific-wg)" | 21:57 | |
oneswig | The time! | 21:57 |
b1airo | better wrap this up i think o_0 | 21:57 |
anteaya | o/ | 21:57 |
anteaya | I have an item if I may | 21:58 |
b1airo | thanks anteaya - see you in the ether | 21:58 |
*** dimtruck is now known as zz_dimtruck | 21:58 | |
dfflanders | nothing like IRC and tea time in the morning :) goes by so fast... | 21:58 |
*** leong has left #openstack-meeting | 21:58 | |
oneswig | go ahead | 21:58 |
anteaya | thanks | 21:58 |
anteaya | sounds like tehre is a lot of emailing happening which is great | 21:58 |
b1airo | oh, that was a hand up, not a wave :-) | 21:58 |
*** sarob has quit IRC | 21:58 | |
anteaya | can folks work to defaulting to public lists for email? | 21:58 |
anteaya | I think there is some great deployment content here the devs would love to know about | 21:58 |
anteaya | if folks would be willing to default thier discussions to public | 21:59 |
anteaya | perhaps the user-committee mailing list? | 21:59 |
anteaya | thank you, that's all I had | 21:59 |
*** Sukhdev has joined #openstack-meeting | 21:59 | |
dfflanders | +1 for mailing lists wherever possible, please use user-committee with [scientific-wg] in the subject line | 21:59 |
oneswig | The discussions that have gone to the operators list have been picked up, it's a good point | 21:59 |
*** sbalukoff has quit IRC | 21:59 | |
b1airo | anteaya, definitely, i agree and we are actively doing that when a discussion arises | 21:59 |
dfflanders | and any other lists. | 21:59 |
anteaya | wonderful thank you | 22:00 |
*** prashantD_ has quit IRC | 22:00 | |
dfflanders | great meeting as usual blairo oneswig - thank you! | 22:00 |
oneswig | I think that is all we have time for - thank you everyone | 22:00 |
Rockyg | thanks! | 22:00 |
dfflanders | l8er | 22:00 |
rbudden | thanks | 22:00 |
*** dfflanders has quit IRC | 22:00 | |
jmlowe | looking forward to next time | 22:00 |
*** kzaitsev_mb has quit IRC | 22:00 | |
b1airo | just asked jonmills this morning if we can take his latest update to the list | 22:00 |
*** jmlowe has quit IRC | 22:00 | |
oneswig | great idea | 22:01 |
*** shaohe_feng has quit IRC | 22:01 | |
anteaya | priteau: are you available after the meeting to discuss in #openstack-infra? | 22:01 |
anteaya | b1airo: thank you | 22:01 |
anteaya | and thanks jonmills | 22:01 |
b1airo | thanks all! bfn | 22:01 |
b1airo | #endmeeting | 22:02 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 22:02 | |
openstack | Meeting ended Tue Jun 14 22:02:02 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 22:02 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/scientific_wg/2016/scientific_wg.2016-06-14-21.03.html | 22:02 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/scientific_wg/2016/scientific_wg.2016-06-14-21.03.txt | 22:02 |
openstack | Log: http://eavesdrop.openstack.org/meetings/scientific_wg/2016/scientific_wg.2016-06-14-21.03.log.html | 22:02 |
priteau | anteaya: Yes I can chat for a few minutes | 22:02 |
anteaya | priteau: great thank you | 22:02 |
*** craigs has quit IRC | 22:03 | |
*** oneswig has quit IRC | 22:04 | |
*** shaohe_feng has joined #openstack-meeting | 22:04 | |
*** bri365 has left #openstack-meeting | 22:04 | |
*** rbudden has left #openstack-meeting | 22:05 | |
*** njohnston is now known as njohnston|afk | 22:07 | |
*** egallen has quit IRC | 22:09 | |
*** ijw_ has quit IRC | 22:10 | |
*** jamesmcarthur has quit IRC | 22:10 | |
*** shaohe_feng has quit IRC | 22:11 | |
*** kzaitsev_mb has joined #openstack-meeting | 22:11 | |
*** mriedem is now known as mriedem_away | 22:12 | |
*** shaohe_feng has joined #openstack-meeting | 22:12 | |
*** b1airo has quit IRC | 22:12 | |
*** Rockyg has quit IRC | 22:12 | |
*** jamesdenton has quit IRC | 22:12 | |
*** Sukhdev has quit IRC | 22:14 | |
*** Sukhdev has joined #openstack-meeting | 22:15 | |
*** baoli has quit IRC | 22:15 | |
*** jonmills has quit IRC | 22:16 | |
*** Sukhdev has quit IRC | 22:16 | |
*** spotz is now known as spotz_zzz | 22:16 | |
*** Sukhdev has joined #openstack-meeting | 22:17 | |
*** priteau has quit IRC | 22:17 | |
*** kzaitsev_mb has quit IRC | 22:18 | |
*** kzaitsev_mb has joined #openstack-meeting | 22:21 | |
*** shaohe_feng has quit IRC | 22:21 | |
*** shaohe_feng has joined #openstack-meeting | 22:22 | |
*** sigmavirus24 is now known as sigmavirus24_awa | 22:23 | |
*** edleafe_ has quit IRC | 22:24 | |
*** openstack has joined #openstack-meeting | 22:25 | |
*** ChanServ sets mode: +o openstack | 22:25 | |
*** rcernin has joined #openstack-meeting | 22:27 | |
*** timcline has quit IRC | 22:27 | |
*** timcline has joined #openstack-meeting | 22:28 | |
*** xavierr is now known as xavierr-afk | 22:30 | |
*** jungleboyj has quit IRC | 22:30 | |
*** JRobinson__ has joined #openstack-meeting | 22:31 | |
*** singhj has quit IRC | 22:31 | |
*** shaohe_feng has quit IRC | 22:32 | |
*** shaohe_feng has joined #openstack-meeting | 22:32 | |
*** jckasper has quit IRC | 22:32 | |
*** timcline has quit IRC | 22:33 | |
*** jckasper has joined #openstack-meeting | 22:33 | |
*** adiantum has quit IRC | 22:34 | |
*** galstrom is now known as galstrom_zzz | 22:35 | |
*** singhj has joined #openstack-meeting | 22:35 | |
*** ijw_ has joined #openstack-meeting | 22:36 | |
*** jckasper has quit IRC | 22:37 | |
*** yohoffman_ has quit IRC | 22:38 | |
*** mtanino has quit IRC | 22:38 | |
*** singhj has quit IRC | 22:39 | |
*** shaohe_feng has quit IRC | 22:42 | |
*** dane_leblanc has quit IRC | 22:42 | |
*** shaohe_feng has joined #openstack-meeting | 22:43 | |
*** mtanino has joined #openstack-meeting | 22:43 | |
*** prashantD__ has quit IRC | 22:44 | |
*** amitgandhinz has joined #openstack-meeting | 22:44 | |
*** prashantD__ has joined #openstack-meeting | 22:44 | |
*** ajmiller has quit IRC | 22:44 | |
*** roxanagh_ has joined #openstack-meeting | 22:47 | |
*** amitgandhinz has quit IRC | 22:48 | |
*** ivar-lazzaro has quit IRC | 22:48 | |
*** gongysh has joined #openstack-meeting | 22:50 | |
*** roxanagh_ has quit IRC | 22:51 | |
*** ajmiller has joined #openstack-meeting | 22:51 | |
*** ivar-lazzaro has joined #openstack-meeting | 22:51 | |
*** ivar-lazzaro has quit IRC | 22:51 | |
*** Sukhdev has quit IRC | 22:51 | |
*** shaohe_feng has quit IRC | 22:52 | |
*** leeantho has joined #openstack-meeting | 22:52 | |
*** leeantho_ has joined #openstack-meeting | 22:52 | |
*** shaohe_feng has joined #openstack-meeting | 22:53 | |
*** singhj has joined #openstack-meeting | 22:53 | |
*** Leo_ has quit IRC | 22:55 | |
*** singhj has quit IRC | 22:58 | |
*** rmizuno_ has quit IRC | 23:00 | |
*** b1airo has joined #openstack-meeting | 23:01 | |
*** ajmiller_ has joined #openstack-meeting | 23:01 | |
*** leeantho_ has quit IRC | 23:02 | |
*** shaohe_feng has quit IRC | 23:02 | |
*** rbak has quit IRC | 23:04 | |
*** prashantD_ has joined #openstack-meeting | 23:05 | |
*** ajmiller has quit IRC | 23:05 | |
*** sbalukoff_ is now known as sbalukoff | 23:05 | |
*** shaohe_feng has joined #openstack-meeting | 23:05 | |
*** mathiasb has quit IRC | 23:06 | |
*** irenab_ has joined #openstack-meeting | 23:07 | |
*** alyson_ has quit IRC | 23:08 | |
*** prashantD__ has quit IRC | 23:08 | |
*** azbiswas has quit IRC | 23:08 | |
*** irenab has quit IRC | 23:10 | |
*** irenab_ is now known as irenab | 23:10 | |
*** jamesdenton has joined #openstack-meeting | 23:12 | |
*** shaohe_feng has quit IRC | 23:13 | |
*** salv-orlando has quit IRC | 23:14 | |
*** jamesden_ has joined #openstack-meeting | 23:14 | |
*** mathiasb has joined #openstack-meeting | 23:14 | |
*** salv-orlando has joined #openstack-meeting | 23:14 | |
*** shaohe_feng has joined #openstack-meeting | 23:15 | |
*** edtubill has quit IRC | 23:16 | |
*** ayoung has joined #openstack-meeting | 23:17 | |
*** jamesdenton has quit IRC | 23:17 | |
*** karthikp_ has quit IRC | 23:18 | |
*** hoangcx has quit IRC | 23:18 | |
*** Sukhdev has joined #openstack-meeting | 23:20 | |
*** sarob has joined #openstack-meeting | 23:20 | |
*** lpetrut has quit IRC | 23:22 | |
*** b1airo has quit IRC | 23:23 | |
*** shaohe_feng has quit IRC | 23:23 | |
*** shaohe_feng has joined #openstack-meeting | 23:23 | |
*** sarob has quit IRC | 23:24 | |
*** sarob has joined #openstack-meeting | 23:24 | |
*** prashantD__ has joined #openstack-meeting | 23:28 | |
*** salv-orl_ has joined #openstack-meeting | 23:29 | |
*** yamada-h has joined #openstack-meeting | 23:30 | |
*** prashantD has joined #openstack-meeting | 23:31 | |
*** prashantD_ has quit IRC | 23:31 | |
*** salv-orlando has quit IRC | 23:32 | |
*** sdake has quit IRC | 23:32 | |
*** shaohe_feng has quit IRC | 23:33 | |
*** sdake has joined #openstack-meeting | 23:33 | |
*** prashantD__ has quit IRC | 23:33 | |
*** shaohe_feng has joined #openstack-meeting | 23:34 | |
*** yamada-h has quit IRC | 23:34 | |
*** asingh has quit IRC | 23:39 | |
*** piet_ has joined #openstack-meeting | 23:39 | |
*** rderose has joined #openstack-meeting | 23:39 | |
*** tochi has joined #openstack-meeting | 23:40 | |
*** rcernin has quit IRC | 23:40 | |
*** asselin_ has joined #openstack-meeting | 23:40 | |
*** shaohe_feng has quit IRC | 23:43 | |
*** shaohe_feng has joined #openstack-meeting | 23:44 | |
*** amitgandhinz has joined #openstack-meeting | 23:44 | |
*** asselin_ has quit IRC | 23:45 | |
*** Sukhdev has quit IRC | 23:45 | |
*** lbeliveau has quit IRC | 23:46 | |
*** lbeliveau has joined #openstack-meeting | 23:47 | |
*** amitgandhinz has quit IRC | 23:49 | |
*** jckasper has joined #openstack-meeting | 23:51 | |
*** sdague has quit IRC | 23:53 | |
*** shaohe_feng has quit IRC | 23:54 | |
*** shaohe_feng has joined #openstack-meeting | 23:54 | |
*** hoangcx has joined #openstack-meeting | 23:55 | |
*** xyang1 has quit IRC | 23:56 | |
*** adahms has joined #openstack-meeting | 23:57 | |
*** ninag has joined #openstack-meeting | 23:58 | |
*** ninag has quit IRC | 23:58 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!