*** ykatabam has quit IRC | 00:04 | |
*** rcernin has joined #openstack-meeting | 00:11 | |
*** jamesmcarthur has joined #openstack-meeting | 00:11 | |
*** rcernin_ has quit IRC | 00:12 | |
*** rcernin has quit IRC | 00:13 | |
*** rcernin has joined #openstack-meeting | 00:14 | |
*** jamesmcarthur has quit IRC | 00:16 | |
*** mjturek has quit IRC | 00:22 | |
*** ssbarnea has joined #openstack-meeting | 00:22 | |
*** ykatabam has joined #openstack-meeting | 00:23 | |
*** jamesmcarthur has joined #openstack-meeting | 00:30 | |
*** longkb has joined #openstack-meeting | 00:37 | |
*** ykatabam has quit IRC | 00:39 | |
*** ykatabam has joined #openstack-meeting | 00:40 | |
*** tetsuro has joined #openstack-meeting | 00:45 | |
*** gouthamr has joined #openstack-meeting | 00:47 | |
*** dmellado has joined #openstack-meeting | 00:51 | |
*** tetsuro has quit IRC | 01:06 | |
*** tetsuro_ has joined #openstack-meeting | 01:06 | |
*** stevebaker has joined #openstack-meeting | 01:06 | |
*** imacdonn has quit IRC | 01:23 | |
*** imacdonn has joined #openstack-meeting | 01:23 | |
*** markvoelker has joined #openstack-meeting | 01:25 | |
*** hongbin has joined #openstack-meeting | 01:27 | |
*** cloudrancher has quit IRC | 01:33 | |
*** cloudrancher has joined #openstack-meeting | 01:34 | |
*** hongbin has quit IRC | 01:36 | |
*** hongbin has joined #openstack-meeting | 01:37 | |
*** yamahata has quit IRC | 01:40 | |
*** jamesmcarthur has quit IRC | 01:41 | |
*** hongbin_ has joined #openstack-meeting | 01:41 | |
*** cloudrancher has quit IRC | 01:41 | |
*** cloudrancher has joined #openstack-meeting | 01:42 | |
*** hongbin has quit IRC | 01:43 | |
*** mhen has quit IRC | 01:44 | |
*** mhen has joined #openstack-meeting | 01:47 | |
*** jamesmcarthur has joined #openstack-meeting | 02:00 | |
*** hongbin has joined #openstack-meeting | 02:05 | |
*** jamesmcarthur has quit IRC | 02:05 | |
*** hongbin_ has quit IRC | 02:07 | |
*** jamesmcarthur has joined #openstack-meeting | 02:18 | |
*** jamesmcarthur has quit IRC | 02:34 | |
*** jamesmcarthur has joined #openstack-meeting | 02:39 | |
*** luobin-smile has joined #openstack-meeting | 02:52 | |
*** psachin has joined #openstack-meeting | 02:57 | |
*** jamesmcarthur has quit IRC | 02:59 | |
*** munimeha1 has quit IRC | 03:01 | |
*** shilpasd_ has joined #openstack-meeting | 03:02 | |
*** shilpasd_ has quit IRC | 03:08 | |
*** yamahata has joined #openstack-meeting | 03:49 | |
*** tpatil has joined #openstack-meeting | 03:50 | |
*** hongbin has quit IRC | 03:52 | |
*** sagara has joined #openstack-meeting | 04:01 | |
*** samP has joined #openstack-meeting | 04:01 | |
samP | Hi | 04:01 |
---|---|---|
sagara | samP: Hi | 04:02 |
tpatil | Hi | 04:02 |
samP | #startmeeting masakari | 04:02 |
openstack | Meeting started Tue Oct 23 04:02:34 2018 UTC and is due to finish in 60 minutes. The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot. | 04:02 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 04:02 |
*** openstack changes topic to " (Meeting topic: masakari)" | 04:02 | |
openstack | The meeting name has been set to 'masakari' | 04:02 |
samP | Hi all | 04:02 |
samP | sorry for the delay | 04:02 |
samP | Let's start | 04:02 |
samP | #topic Critical Bugs/Patches | 04:03 |
*** openstack changes topic to "Critical Bugs/Patches (Meeting topic: masakari)" | 04:03 | |
*** ShilpaSD has joined #openstack-meeting | 04:03 | |
samP | Any critical bugs or patches need to discuss? | 04:04 |
samP | #link https://review.openstack.org/#/c/606652/1 | 04:04 |
samP | Please review this ^^, LGTM | 04:04 |
tpatil | Done | 04:05 |
tpatil | https://bugs.launchpad.net/masakari/+bug/1798496 | 04:05 |
openstack | Launchpad bug 1798496 in masakari "masakari-dasboard : DateTime parameters are displayed in UTC format" [Undecided,New] | 04:05 |
tpatil | This bug is not critical | 04:05 |
tpatil | In masakari dashboard and elsewhere in horizon, date is displayed in UTC format | 04:05 |
*** mrhillsman is now known as openlab | 04:05 | |
tpatil | As an user, I would like to see the date time parameters in local timezone | 04:06 |
*** openlab is now known as mrhillsman | 04:06 | |
samP | tpatil: Can it change from horizon side? | 04:07 |
tpatil | Let me check | 04:07 |
tpatil | It's there in settings | 04:08 |
tpatil | Will mark this bug as invalid | 04:08 |
samP | tpatil: Thanks. | 04:09 |
tpatil | There are some bugs whose status is not marked correctly even after the proposed patches are merged | 04:10 |
tpatil | e.g. https://bugs.launchpad.net/masakari/+bug/1779752 | 04:10 |
openstack | Launchpad bug 1779752 in masakari-monitors "masakari segment-list returns error (openstack queens)" [Critical,Confirmed] - Assigned to Shilpa Devharakar (shilpasd) | 04:10 |
samP | tpatil: yes, specially those queens issues. | 04:10 |
samP | We need to check them and re-set the status | 04:11 |
tpatil | ok, Can I mark it's status to fix committed? | 04:13 |
samP | tpatil: sure, thanks | 04:14 |
samP | I will check for python-masakariclient and masakari-monitors | 04:14 |
tpatil | Ok, will do | 04:15 |
samP | tpatil: thanks | 04:16 |
*** yamamoto has quit IRC | 04:17 | |
*** yamamoto has joined #openstack-meeting | 04:17 | |
samP | I am looking for the rootwrap issue in masakari monitors, with no luck | 04:17 |
*** jamesmcarthur has joined #openstack-meeting | 04:18 | |
tpatil | it's not reproducible | 04:18 |
*** yamahata has quit IRC | 04:19 | |
samP | tpatil: OK, let's discuss that if it surface again. | 04:19 |
*** yamahata has joined #openstack-meeting | 04:19 | |
samP | #topic Stein Work Items | 04:20 |
*** openstack changes topic to "Stein Work Items (Meeting topic: masakari)" | 04:20 | |
tpatil | Functional test in openstacksdk | 04:20 |
samP | Please share if you have any updates from last week | 04:20 |
tpatil | couldn't push patches in the last week. Will target in this week | 04:20 |
samP | tpatil: thanks | 04:21 |
tpatil | in openstacksdk, we will add minimal functional tests | 04:21 |
*** tashiromt_ has joined #openstack-meeting | 04:21 | |
samP | tpatil: sure | 04:21 |
tpatil | Notification workflow events, In the last meeting, it was decided to write a specs for this | 04:22 |
*** jamesmcarthur has quit IRC | 04:22 | |
samP | need to update spec repo | 04:22 |
tpatil | I checked the task flow library and it has support to persist task flow details in backend | 04:22 |
tpatil | I think we should leverage that functionality instead of adding our own | 04:23 |
tpatil | checking how to pass masakari backend to task flow so that the required db tables can be added in masakari db | 04:23 |
samP | tpatil: great. No need to add same functionality to masakari, if we can use one in faskflow lib | 04:24 |
tpatil | samP: Presently, understanding what changes we would need to do to pass useful information in each task | 04:25 |
tpatil | once it's clear, I will write a specs for this | 04:26 |
samP | BTW, Greg Hill started the discussion about moving taskflow out of openstack/oslo to github. | 04:26 |
tpatil | samP: Yes , I was that mailing thread | 04:26 |
samP | Do we have to worry about this? | 04:26 |
tpatil | I don' think so | 04:27 |
tpatil | Add event notification feature to masakari: https://review.openstack.org/#/c/473057 | 04:27 |
tpatil | Internal review is in progress. Will push patches soon | 04:28 |
samP | tpatil: sure. Thanks | 04:28 |
*** rfolco|rover has quit IRC | 04:30 | |
samP | Any other updates? | 04:31 |
sagara | samP: for my side, nothing | 04:32 |
tpatil | No | 04:32 |
samP | No updates from my side. | 04:33 |
samP | #topic AOB | 04:33 |
*** openstack changes topic to "AOB (Meeting topic: masakari)" | 04:33 | |
samP | Any other issues to discuss? | 04:33 |
sagara | no | 04:33 |
tpatil | No | 04:34 |
samP | OK then, if any please use openstack-dev ML with [masakari] or #openstack-masakari @freenode | 04:34 |
samP | Let's finish today's meeting | 04:34 |
samP | Thank you for your time | 04:35 |
samP | #endmeeting | 04:35 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 04:35 | |
openstack | Meeting ended Tue Oct 23 04:35:12 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 04:35 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-10-23-04.02.html | 04:35 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-10-23-04.02.txt | 04:35 |
openstack | Log: http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-10-23-04.02.log.html | 04:35 |
*** sagara has quit IRC | 04:37 | |
*** mahatic has joined #openstack-meeting | 04:41 | |
*** tpatil has left #openstack-meeting | 04:44 | |
*** janki has joined #openstack-meeting | 04:59 | |
*** jiaopengju has quit IRC | 05:20 | |
*** jiaopengju has joined #openstack-meeting | 05:23 | |
*** ralonsoh has joined #openstack-meeting | 05:40 | |
*** ttsiouts has quit IRC | 05:42 | |
*** ttsiouts has joined #openstack-meeting | 05:43 | |
*** Luzi has joined #openstack-meeting | 05:44 | |
*** ttsiouts has quit IRC | 05:47 | |
*** tetsuro_ has quit IRC | 05:50 | |
*** tashiromt_ has quit IRC | 06:35 | |
*** slaweq has joined #openstack-meeting | 06:43 | |
*** njohnston has quit IRC | 06:47 | |
*** pcaruana has joined #openstack-meeting | 06:56 | |
*** ykatabam has quit IRC | 07:03 | |
*** felipemonteiro has joined #openstack-meeting | 07:04 | |
*** armax has quit IRC | 07:04 | |
*** rcernin has quit IRC | 07:06 | |
*** felipemonteiro has quit IRC | 07:22 | |
*** jamesmcarthur has joined #openstack-meeting | 07:34 | |
*** aojea has joined #openstack-meeting | 07:37 | |
*** jamesmcarthur has quit IRC | 07:38 | |
*** tpatil has joined #openstack-meeting | 07:49 | |
*** bhagyashris has joined #openstack-meeting | 07:53 | |
*** phuoch has joined #openstack-meeting | 08:04 | |
*** phuoch has quit IRC | 08:09 | |
*** ttsiouts has joined #openstack-meeting | 08:17 | |
*** e0ne has joined #openstack-meeting | 08:23 | |
*** a-pugachev has joined #openstack-meeting | 08:25 | |
*** electrofelix has joined #openstack-meeting | 08:29 | |
*** gouthamr has quit IRC | 08:32 | |
*** dmellado has quit IRC | 08:34 | |
*** stevebaker has quit IRC | 08:35 | |
*** priteau has joined #openstack-meeting | 08:45 | |
*** yinweiishere has joined #openstack-meeting | 08:58 | |
*** dtrainor has quit IRC | 08:59 | |
jiaopengju | #startmeeting karbor | 09:01 |
openstack | Meeting started Tue Oct 23 09:01:01 2018 UTC and is due to finish in 60 minutes. The chair is jiaopengju. Information about MeetBot at http://wiki.debian.org/MeetBot. | 09:01 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 09:01 |
*** openstack changes topic to " (Meeting topic: karbor)" | 09:01 | |
openstack | The meeting name has been set to 'karbor' | 09:01 |
jiaopengju | hi guys | 09:01 |
yinweiishere | hi | 09:01 |
luobin-smile | hi | 09:01 |
jiaopengju | hi yinweiishere, luobin-smile | 09:01 |
yinweiishere | hi pengju | 09:01 |
yinweiishere | have we got any schedule for S version new features? | 09:02 |
jiaopengju | I saw the meeging agenda has been updated here, https://wiki.openstack.org/wiki/Meetings/Karbor | 09:02 |
yinweiishere | yeach | 09:02 |
yinweiishere | we wanna propose add snapshot feature there | 09:03 |
yinweiishere | and just now luobin and I checked current karbor code | 09:03 |
jiaopengju | yinweiishere, I have do some plan for the S version, mainly focus on optimization | 09:03 |
yinweiishere | we found some problems for snapshot there | 09:03 |
yinweiishere | any wiki page for S version plan? | 09:03 |
jiaopengju | I will send an etherpad link after meeting | 09:04 |
yinweiishere | OK, good | 09:05 |
jiaopengju | We can talk about the feature in the agenda first | 09:05 |
yinweiishere | sure | 09:05 |
jiaopengju | #topic add snapshot feature to Karbor to support crash consistency and app consistency further | 09:05 |
*** openstack changes topic to "add snapshot feature to Karbor to support crash consistency and app consistency further (Meeting topic: karbor)" | 09:05 | |
yinweiishere | I'd also like to hear your ideas for optimization | 09:05 |
jiaopengju | :) | 09:06 |
yinweiishere | since as I know Yuval has done a lot opt there :) | 09:06 |
yinweiishere | ok | 09:06 |
yinweiishere | so for snapshot | 09:06 |
jiaopengju | now you can describe the snapshot feature | 09:06 |
yinweiishere | as we know, snapshot has two usages | 09:06 |
yinweiishere | one to restore another instance from snapshot | 09:07 |
yinweiishere | the other is to rollback current instance to the snapshot | 09:07 |
yinweiishere | here, the instance I mean server or volume or volume groups | 09:07 |
jiaopengju | get it | 09:07 |
yinweiishere | we checked current implementation in karbor | 09:07 |
yinweiishere | we only provide restore API for snapshot, where we can't rollback current instance | 09:08 |
yinweiishere | if you check actual nova libvirt snapshot or ceph rbd snapshot, the backends all provide rbd snapshot rollback | 09:09 |
yinweiishere | so, for the API aspect, the snapshot feature is missing there | 09:10 |
jiaopengju | This means we should add rollback operation in the protection plugins? | 09:10 |
jiaopengju | just like verify, copy and so on | 09:10 |
yinweiishere | first add rollback API in restore | 09:10 |
yinweiishere | part | 09:10 |
*** gouthamr has joined #openstack-meeting | 09:11 | |
yinweiishere | then, for snapshot protection plugin, support it | 09:11 |
jiaopengju | yes | 09:11 |
yinweiishere | so this is the API part | 09:11 |
yinweiishere | second, snapshot has a consistency semantics | 09:11 |
yinweiishere | now Karbor's checkpoint doesn't support any level's consistency | 09:12 |
yinweiishere | do you agree? | 09:12 |
*** geguileo has joined #openstack-meeting | 09:12 | |
jiaopengju | yes, agree | 09:13 |
*** tetsuro has joined #openstack-meeting | 09:14 | |
yinweiishere | when we initially started this project, the founder agreed to postpone the consistency issue. But without consistency, neither the snapshot or the checkpoint (what ever you call) it doesn't satisfy 'protect' semantic in fact. | 09:14 |
yinweiishere | actually, there're two levels for consistensy | 09:15 |
yinweiishere | the initial level: crash consistency | 09:15 |
yinweiishere | the higher level: app consistency | 09:15 |
yinweiishere | although Karbor has analyzed dependencies among resources, it still fails to support even crash consistency | 09:16 |
jiaopengju | do you have specs for these two level? | 09:17 |
jiaopengju | or some docmentation link | 09:17 |
yinweiishere | look at how we protect server and its volumes/volume groups, we didn't maintain the consistency there | 09:18 |
*** dmellado has joined #openstack-meeting | 09:18 | |
yinweiishere | we propose to support snapshot with two levels consistency step by step | 09:18 |
yinweiishere | first crash consistency and then app level consistency | 09:18 |
yinweiishere | yes, we do have some ideas there | 09:19 |
yinweiishere | want to achieve consensus first before writing it to spec | 09:19 |
*** bzhao__ has quit IRC | 09:20 | |
yinweiishere | pengju, are you there? | 09:20 |
jiaopengju | yes, can you give more messages about crash consistency? | 09:21 |
yinweiishere | sure | 09:21 |
yinweiishere | actually, I'm thinking that we need a pair of APIs for snapshot:take_snapshot(consistency_level) and rollback_snapshot(checkpoint_id) | 09:22 |
yinweiishere | to differenciate existed protect/restore API, which support loose restriction on consistency | 09:23 |
jiaopengju | do you mean that, if we take a snapshot in karbor, then the checkpoints info that matched to this snapshot will be saved? | 09:23 |
yinweiishere | yes, the snapshot will be the backend resource of the checkpoint | 09:24 |
yinweiishere | similar to the backup id | 09:24 |
jiaopengju | ok, I understand, that sounds useful | 09:24 |
yinweiishere | or we can merge it with protect API with consistency level params, none means current way | 09:25 |
yinweiishere | those are details, we can discuss it in spec | 09:25 |
yinweiishere | and for crash consistency | 09:25 |
*** tpatil has quit IRC | 09:26 | |
yinweiishere | we need pause the server, flush the memory to disk, and then call volume/volume group's backend snapshot methods | 09:26 |
yinweiishere | on contrast, currently we never pause server, but only backup each volumes attached to the server if it booted from a volume. If it booted from an image, we never backup the changes in system volume. | 09:28 |
yinweiishere | that's the crash consistency | 09:28 |
yinweiishere | where the system could really boot from the snapshot, and apps | 09:28 |
yinweiishere | won't crash | 09:28 |
jiaopengju | I have talked the vms that booted from an image with yuval and chenying before | 09:29 |
jiaopengju | But if we pause server in karbor, this will a few intrusive to the end user | 09:31 |
yinweiishere | our current way may backup at a wrong moment,that the system and the apps haven't saved the necessary status to disk and they may fail to boot without those status. | 09:31 |
yinweiishere | that's the protection plugin | 09:31 |
jiaopengju | part of karbor | 09:32 |
yinweiishere | sure | 09:32 |
yinweiishere | that's dependent on the consistency param | 09:32 |
yinweiishere | if user asks for crash consistency, it means he/she understands what does it mean | 09:33 |
yinweiishere | for crash consistency itself, that's the way it should be | 09:33 |
jiaopengju | ok, understand, this is the detail info, you can write it in the spec | 09:34 |
jiaopengju | app consistency? | 09:35 |
*** stevebaker has joined #openstack-meeting | 09:36 | |
jiaopengju | yinweiishere are you there? | 09:37 |
yinweiishere | yes, I'm here | 09:37 |
yinweiishere | app consistency is a bit complicated | 09:37 |
yinweiishere | Luobin, could you pls. elaborate here? | 09:38 |
yinweiishere | it's about global consistent snapshot | 09:39 |
yinweiishere | which requires some background knowledge | 09:39 |
jiaopengju | app , the resource that matched to openstack is a couple of resources, or a group of resources? | 09:39 |
*** bhagyashris has quit IRC | 09:39 | |
yinweiishere | have you heard of chandy-lamport algorithm for distributed snapshot? | 09:39 |
yinweiishere | this algorithm is enhanced as ABS algorithm and applied in stream engine in flink | 09:40 |
yinweiishere | our idea is to enhance ABS and apply it in karbor | 09:41 |
yinweiishere | we can put it as a more long term target | 09:41 |
yinweiishere | the paper of ABS is here | 09:42 |
yinweiishere | https://arxiv.org/pdf/1506.08603.pdf | 09:42 |
yinweiishere | for your reference | 09:42 |
*** jamesmcarthur has joined #openstack-meeting | 09:43 | |
jiaopengju | actually I think we should define which resource that mapped to openstack we protected in app consistency scene | 09:43 |
jiaopengju | and then how | 09:43 |
yinweiishere | resources are the same | 09:44 |
yinweiishere | the problem is how to make the app aware of the snapshot | 09:45 |
yinweiishere | and, as there are many apps in one plan's servers | 09:45 |
yinweiishere | how to make sure all apps are consistent | 09:45 |
yinweiishere | the distributed snapshot issue is to make sure the causal ordering is correct | 09:46 |
yinweiishere | as, APP1 is the input of APP2 | 09:46 |
yinweiishere | we take snapshot on the whole system | 09:47 |
*** jamesmcarthur has quit IRC | 09:47 | |
yinweiishere | but the snapshot command may get triggered at different timming on server1 and server2 | 09:47 |
jiaopengju | ok, a little understand, I will see the reference you send after meeting | 09:47 |
yinweiishere | since there're events on the fly | 09:47 |
yinweiishere | yeach | 09:47 |
yinweiishere | similar to crash consistency | 09:48 |
yinweiishere | we need maintain the dependencies among APPs | 09:48 |
yinweiishere | ok | 09:48 |
yinweiishere | that's all for my part | 09:48 |
jiaopengju | thanks for giving this useful idea | 09:49 |
yinweiishere | you can send out the schedule link | 09:50 |
jiaopengju | we can add this to stein plan | 09:50 |
yinweiishere | and we can put the effort there to see if more people will get interested there | 09:50 |
yinweiishere | yes, we can support it step by step | 09:50 |
jiaopengju | I can easily describe the plan in stein cycle here: optimization of multiple nodes of operation engine (yuval provide the first version) | 09:52 |
jiaopengju | 2. cross-site backup and restore (cross keystone) | 09:52 |
yinweiishere | haho | 09:52 |
jiaopengju | 3. documentation | 09:52 |
yinweiishere | cross site is what I proposed long long ago | 09:53 |
jiaopengju | yes, some people has asked questions about it | 09:53 |
yinweiishere | it's really useful, right? | 09:53 |
jiaopengju | cross keystone seems not | 09:53 |
yinweiishere | I think cross region/AZ is necessary | 09:54 |
yinweiishere | cross keystone is a bit difficult | 09:54 |
jiaopengju | at the same time, we do not have documentation enough about it | 09:54 |
yinweiishere | again, step by step is more feasible | 09:55 |
jiaopengju | yes, agree | 09:55 |
yinweiishere | ok, I think the time is run out | 09:55 |
jiaopengju | yeah, so I will end the meeting soon and we can talk about it in karbor channel | 09:55 |
yinweiishere | if you have made the schedule link, pls. let us know in karbor channel | 09:56 |
jiaopengju | ok | 09:56 |
jiaopengju | #endmeeting | 09:56 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 09:56 | |
openstack | Meeting ended Tue Oct 23 09:56:33 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:56 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/karbor/2018/karbor.2018-10-23-09.01.html | 09:56 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/karbor/2018/karbor.2018-10-23-09.01.txt | 09:56 |
openstack | Log: http://eavesdrop.openstack.org/meetings/karbor/2018/karbor.2018-10-23-09.01.log.html | 09:56 |
*** rossella_s has quit IRC | 09:57 | |
*** a-pugachev has quit IRC | 10:03 | |
*** a-pugachev has joined #openstack-meeting | 10:04 | |
*** rfolco has joined #openstack-meeting | 10:12 | |
*** ssbarnea_ has joined #openstack-meeting | 10:16 | |
*** ianychoi has quit IRC | 10:22 | |
*** ianychoi has joined #openstack-meeting | 10:25 | |
*** apetrich has quit IRC | 10:38 | |
*** dtrainor has joined #openstack-meeting | 10:48 | |
*** apetrich has joined #openstack-meeting | 10:54 | |
*** erlon has joined #openstack-meeting | 10:58 | |
*** yamamoto has quit IRC | 11:03 | |
*** yamamoto has joined #openstack-meeting | 11:04 | |
*** ttsiouts has quit IRC | 11:04 | |
*** yamamoto has quit IRC | 11:08 | |
*** yikun has quit IRC | 11:09 | |
*** tetsuro has quit IRC | 11:12 | |
*** longkb has quit IRC | 11:19 | |
*** yamamoto has joined #openstack-meeting | 11:21 | |
*** rfolco is now known as rfolco|rucker | 11:23 | |
*** janki has quit IRC | 11:41 | |
*** ttsiouts has joined #openstack-meeting | 11:43 | |
*** eharney has joined #openstack-meeting | 11:45 | |
*** markvoelker has quit IRC | 11:45 | |
*** ttsiouts has quit IRC | 11:48 | |
*** mmethot has joined #openstack-meeting | 11:54 | |
*** ttsiouts has joined #openstack-meeting | 12:02 | |
*** a-pugachev has quit IRC | 12:09 | |
*** janki has joined #openstack-meeting | 12:14 | |
*** cloudrancher has quit IRC | 12:19 | |
*** cloudrancher has joined #openstack-meeting | 12:19 | |
*** janki has quit IRC | 12:25 | |
*** janki has joined #openstack-meeting | 12:25 | |
*** janki has quit IRC | 12:27 | |
*** tobberydberg has quit IRC | 12:30 | |
*** janki has joined #openstack-meeting | 12:34 | |
*** rubasov has joined #openstack-meeting | 12:36 | |
*** markvoelker has joined #openstack-meeting | 12:36 | |
*** markvoelker has quit IRC | 12:37 | |
*** jchhatbar has joined #openstack-meeting | 12:38 | |
*** janki has quit IRC | 12:40 | |
*** jchhatbar is now known as janki | 12:50 | |
*** dustins has joined #openstack-meeting | 12:51 | |
*** dustins is now known as dschoenb|worksho | 12:52 | |
*** dschoenb|worksho is now known as dustins | 12:52 | |
*** yamamoto has quit IRC | 13:02 | |
*** bnemec has joined #openstack-meeting | 13:08 | |
*** psachin has quit IRC | 13:10 | |
*** a-pugachev has joined #openstack-meeting | 13:13 | |
*** e0ne has quit IRC | 13:19 | |
*** longkb has joined #openstack-meeting | 13:28 | |
*** kailun has joined #openstack-meeting | 13:29 | |
*** bobh has joined #openstack-meeting | 13:31 | |
*** mriedem has joined #openstack-meeting | 13:34 | |
*** yamamoto has joined #openstack-meeting | 13:35 | |
*** awaugama has joined #openstack-meeting | 13:42 | |
*** cloudrancher has quit IRC | 13:44 | |
*** cloudrancher has joined #openstack-meeting | 13:45 | |
*** mjturek has joined #openstack-meeting | 13:47 | |
*** liuyulong has joined #openstack-meeting | 13:48 | |
*** kiennt26 has joined #openstack-meeting | 13:50 | |
*** mlavalle has joined #openstack-meeting | 13:53 | |
*** kiennt26 has quit IRC | 13:56 | |
*** a-pugachev has quit IRC | 13:58 | |
*** Leo_m has joined #openstack-meeting | 13:58 | |
*** edmondsw has joined #openstack-meeting | 14:00 | |
*** hongbin has joined #openstack-meeting | 14:00 | |
mlavalle | #startmeeting networking | 14:01 |
openstack | Meeting started Tue Oct 23 14:01:29 2018 UTC and is due to finish in 60 minutes. The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:01 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:01 |
*** openstack changes topic to " (Meeting topic: networking)" | 14:01 | |
openstack | The meeting name has been set to 'networking' | 14:01 |
slaweq | hi | 14:01 |
amotoki | hi | 14:01 |
longkb | hi :) | 14:01 |
rubasov | o/ | 14:01 |
tidwellr | hi | 14:02 |
hongbin | o/ | 14:02 |
mlavalle | #topic Announcements | 14:02 |
*** a-pugachev has joined #openstack-meeting | 14:02 | |
*** openstack changes topic to "Announcements (Meeting topic: networking)" | 14:02 | |
mlavalle | This week we reached the Stein-1 milestone | 14:03 |
*** annp_ has joined #openstack-meeting | 14:03 | |
mlavalle | And we are a little more than two weeks away from the Berlin Summit | 14:04 |
mlavalle | Any other announcements to share with the team? | 14:04 |
*** njohnston has joined #openstack-meeting | 14:04 | |
njohnston | o/ | 14:04 |
*** lajoskatona_ has joined #openstack-meeting | 14:04 | |
mlavalle | ok, let's move on | 14:05 |
mlavalle | #topic Blueprints | 14:05 |
*** openstack changes topic to "Blueprints (Meeting topic: networking)" | 14:05 | |
lajoskatona_ | Hi | 14:05 |
mlavalle | These are the blueprints we are targeting: https://launchpad.net/neutron/+milestone/stein-1 | 14:05 |
mlavalle | Does anybode have an update or request? | 14:06 |
mlavalle | regarding blueprints | 14:06 |
*** Luzi has quit IRC | 14:06 | |
mlavalle | amotoki: all good to cut the milestone? | 14:07 |
amotoki | mlavalle: yeah. I will prepare a release patch around Thu | 14:07 |
mlavalle | amotoki: are we also releasing the neutron stable branches? | 14:07 |
amotoki | mlavalle: we can, but it depends on pending patches. | 14:08 |
amotoki | i haven't checked the status. I need to sync with you. | 14:08 |
mlavalle | amotoki: ok | 14:08 |
mlavalle | Last week I was approached by someone asking a Queens release | 14:09 |
mlavalle | so let's do it | 14:09 |
amotoki | agree | 14:09 |
mlavalle | ok, moving on | 14:09 |
mlavalle | #topic Community goals | 14:10 |
*** openstack changes topic to "Community goals (Meeting topic: networking)" | 14:10 | |
mlavalle | amotoki: any updates with policy in code? | 14:10 |
amotoki | regarding policy-in-code, I just pushed a new patch set. sorry for late, but I believe neutron side will be in good shape. | 14:10 |
mlavalle | do you have the pointer handy? | 14:11 |
amotoki | https://review.openstack.org/585037 | 14:11 |
mlavalle | Thanks amotoki :-) | 14:11 |
amotoki | I think I am in limited bandwidth, so once I prepared neutron-fwaas patch, I would like to gather volunteers for other stadium projects. | 14:11 |
amotoki | * to make the progress fast | 14:12 |
amotoki | neutron-fwaas patch would be a good example for other projects. | 14:12 |
mlavalle | do we need a volunteer for each Stadium project? | 14:13 |
amotoki | I don't think we need each per project | 14:13 |
mlavalle | ok, let us know when the fwaas patch is ready and we can use it as a model | 14:14 |
amotoki | sure | 14:14 |
mlavalle | and to request volunteers | 14:14 |
mlavalle | thanks for the update | 14:14 |
mlavalle | njohnston: anything on py3? | 14:14 |
njohnston | Nothing at present; there has been a thread on openstack-dev about how to handle py35 vs py36 vs py37, and so I have been waiting to make sure the aproach is not going to change. I think a relative consensus has been reached. | 14:15 |
njohnston | So I am revisiting some of those changes this morning. | 14:16 |
mlavalle | Thanks for the update, njohnston | 14:16 |
amotoki | this thread is related to python3 future http://lists.openstack.org/pipermail/openstack-dev/2018-October/135892.html | 14:17 |
amotoki | this is just FYI | 14:17 |
njohnston | Thanks amotoki, I was just looking for the link | 14:17 |
*** boden has joined #openstack-meeting | 14:17 | |
mlavalle | slaweq: anything worth mentioning on Support Pre Upgrade Checks? | 14:17 |
slaweq | only that patch https://review.openstack.org/#/c/608444/ with base cli tool is ready for review | 14:18 |
slaweq | next step will be for me to add support for checks to be loaded using stevedore that e.g. stadium projects or some 3rd party plugins will be able to add own checks there | 14:18 |
mlavalle | ok, I will take a look at this patch today. Thanks | 14:20 |
slaweq | thx mlavalle | 14:20 |
mlavalle | #topic Bugs | 14:20 |
*** openstack changes topic to "Bugs (Meeting topic: networking)" | 14:20 | |
mlavalle | haleyb was our bugs deputy last week | 14:21 |
mlavalle | He sent this update to the ML: http://lists.openstack.org/pipermail/openstack-dev/2018-October/135969.html | 14:21 |
*** janki has quit IRC | 14:21 | |
mlavalle | I thought we had gotten rid of this one a couple of weeks ago: https://bugs.launchpad.net/neutron/+bug/1798688 | 14:23 |
openstack | Launchpad bug 1798688 in neutron "iptables_hybrid tests tempest.api.compute.servers.test_servers_negative.ServersNegativeTestJSON.test_shelve_shelved_server failed " [Undecided,Incomplete] | 14:23 |
mlavalle | I will take a look at it | 14:24 |
slaweq | mlavalle: few weeks ago it was visible mostly in dvr tests | 14:24 |
slaweq | IIRC | 14:24 |
mlavalle | yes | 14:25 |
slaweq | and then You couldn't reproduce it | 14:25 |
slaweq | but it looks that it still happen from time to time | 14:25 |
mlavalle | yeah, I will look again | 14:26 |
mlavalle | any other comments on the bugs report? | 14:27 |
mlavalle | ok, this week, our deputy is armax, so we are covered | 14:27 |
mlavalle | and next week the deputy is Zhao Bo. I will send him an email to make sure he is ready | 14:28 |
mlavalle | moving on | 14:28 |
mlavalle | #topic os-ken | 14:28 |
*** openstack changes topic to "os-ken (Meeting topic: networking)" | 14:28 | |
*** e0ne has joined #openstack-meeting | 14:29 | |
mlavalle | hongbin: any updates on this? | 14:29 |
hongbin | hi | 14:29 |
hongbin | so last week, there are a couple of progress on os-ken | 14:29 |
hongbin | 1. the pep8 job is setup: https://review.openstack.org/#/c/609121/ | 14:29 |
hongbin | 2. the unit test is setup: https://review.openstack.org/#/c/609148/ | 14:30 |
hongbin | 3. the lower constratnt is setup: https://review.openstack.org/#/c/609100/ | 14:30 |
hongbin | 4. the doc building job is under review | 14:30 |
hongbin | #link https://review.openstack.org/#/q/project:openstack/os-ken | 14:30 |
hongbin | for the requirement side, we have a patch up for review | 14:31 |
amotoki | hongbin: I added a minor question on doc fix patch https://review.openstack.org/#/c/610706/4/doc/source/snort_integrate.rst@90 | 14:31 |
hongbin | #link https://review.openstack.org/#/c/609018/ | 14:31 |
hongbin | amotoki: thanks, i will get back to it | 14:31 |
amotoki | i am okay to merge this as is, but I would like you to check it before it :) | 14:32 |
hongbin | i am fine with it | 14:32 |
hongbin | so, right now, we are basically waiting for the requirement patch | 14:33 |
mlavalle | should we ping Mathew? | 14:33 |
hongbin | sure, we can ping him to look at it again | 14:34 |
mlavalle | ok | 14:34 |
mlavalle | anything else? | 14:34 |
hongbin | nothing else from my side | 14:34 |
mlavalle | Thanks! | 14:34 |
mlavalle | #topic CLI / SDK | 14:35 |
*** openstack changes topic to "CLI / SDK (Meeting topic: networking)" | 14:35 | |
mlavalle | amotoki: any updates on this topic? | 14:35 |
*** aojeagarcia has joined #openstack-meeting | 14:35 | |
amotoki | nothing from me this week. | 14:35 |
mlavalle | ok, moving on | 14:35 |
*** aojea has quit IRC | 14:35 | |
mlavalle | #topic neutron-lib | 14:35 |
*** openstack changes topic to "neutron-lib (Meeting topic: networking)" | 14:35 | |
mlavalle | boden: you are up | 14:36 |
boden | hi | 14:36 |
boden | much of the same as last week; working on the db consumption patches along with the switch to payload style args for callbacks | 14:36 |
boden | a few patches I would like to ask for reviews on that would help keep things moving | 14:36 |
boden | for the db decouple: https://review.openstack.org/#/c/612527/ should be ready | 14:37 |
boden | and for payloads: https://review.openstack.org/#/c/597561/ and https://review.openstack.org/#/c/596959/ | 14:37 |
boden | if folks get time, it would help to keep these moving :) | 14:37 |
boden | that's all the exciting news I have for neutron-lib unless others have something | 14:37 |
mlavalle | added all of them to my pile | 14:38 |
slaweq | I wanted to ask about one thing | 14:38 |
mlavalle | I think we need to ask amotoki to take a look at https://review.openstack.org/#/c/596959/ | 14:38 |
*** felipemonteiro has joined #openstack-meeting | 14:38 | |
mlavalle | don't we? | 14:38 |
slaweq | do we backport patches to stable branches in neutron-lib? or it don't work like that there? | 14:39 |
amotoki | mlavalle: boden: sorry for that... we discussed it with boden and we agree that we can go as-is. will check it. | 14:39 |
mlavalle | amotoki: thanks ;-) | 14:39 |
boden | slaweq is there some bug we need fixed? | 14:40 |
slaweq | boden: I was thinking about backport of https://review.openstack.org/#/c/609633/ | 14:40 |
slaweq | but I don't know if that makes sense so I'm asking here :) | 14:40 |
boden | slaweq honestly I'm not sure unless we were to re-release an old version of neutron-lib since everything is pulled from pypi?? | 14:41 |
boden | may need ot ask the release team if we do need that backported... not sure we've done this to date that I'm aware of | 14:42 |
mlavalle | I don't think we have done it | 14:42 |
slaweq | that's why I'm asking, I saw stable/XXX branches in neutron-lib repo but I'm not sure if we are releasing such stable releases with bugfixes only | 14:42 |
amotoki | in theory, if we have bug fixes worth backported in neutorn-lib stable branches, we can backport and release it. | 14:43 |
amotoki | we didn't have such so far, but we can if needed. | 14:43 |
boden | I think we can, but woudl be a minor release (of whatever version we released for rocky say) right??? | 14:43 |
amotoki | it would be a patch release | 14:44 |
amotoki | it means only Z can be incremented in X.Y.Z | 14:44 |
slaweq | ok, so that would be more question to stable core team then, if this patch is worth to be backported :) | 14:44 |
boden | yes, that's what I Was trying to say | 14:44 |
boden | slaweq do you need me to follow-up with them, or you will? | 14:45 |
slaweq | mlavalle: can You take a look at this patch and check if that is worth to be backported? :) | 14:45 |
mlavalle | slaweq: sure | 14:45 |
slaweq | thx | 14:45 |
mlavalle | anything else on neutron-lib | 14:46 |
mlavalle | ? | 14:46 |
boden | not from me | 14:46 |
mlavalle | ok, let's move on | 14:46 |
mlavalle | #topic On demand agenda | 14:46 |
*** openstack changes topic to "On demand agenda (Meeting topic: networking)" | 14:46 | |
mlavalle | anything else we should bring up to the team today? | 14:46 |
mlavalle | ok, thanks for attending | 14:47 |
mlavalle | Have a great week! | 14:47 |
mlavalle | #endmeeting | 14:47 |
njohnston | thanks! | 14:47 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 14:47 | |
openstack | Meeting ended Tue Oct 23 14:47:41 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:47 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-10-23-14.01.html | 14:47 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-10-23-14.01.txt | 14:47 |
openstack | Log: http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-10-23-14.01.log.html | 14:47 |
*** boden has left #openstack-meeting | 14:47 | |
amotoki | o/ | 14:48 |
slaweq | o/ | 14:48 |
bcafarel | o/ (yep joining after the meeting end) | 14:52 |
mlavalle | bcafarel: LOL | 14:59 |
slaweq | #startmeeting neutron_qos | 15:00 |
openstack | Meeting started Tue Oct 23 15:00:34 2018 UTC and is due to finish in 60 minutes. The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:00 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
*** openstack changes topic to " (Meeting topic: neutron_qos)" | 15:00 | |
openstack | The meeting name has been set to 'neutron_qos' | 15:00 |
ralonsoh | o/ | 15:00 |
rubasov | o/ | 15:01 |
njohnston | o/ | 15:01 |
* mlavalle is not feeling very well today. stomach flue | 15:01 | |
lajoskatona_ | o/ | 15:01 |
slaweq | mlavalle: :( | 15:02 |
slaweq | ok, let's start | 15:02 |
slaweq | #topic RFEs | 15:02 |
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)" | 15:02 | |
slaweq | first one on the list is: | 15:02 |
*** Leo_m_ has joined #openstack-meeting | 15:02 | |
slaweq | #link https://bugs.launchpad.net/neutron/+bug/1560963 | 15:02 |
openstack | Launchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,In progress] | 15:02 |
slaweq | and there is still no any progress on this one | 15:02 |
slaweq | so I think we can quickly go to the next one, which is: | 15:03 |
slaweq | #link https://bugs.launchpad.net/neutron/+bug/1727578 | 15:03 |
openstack | Launchpad bug 1727578 in neutron "[RFE]Support apply qos policy in VPN service" [Wishlist,Triaged] | 15:03 |
mlavalle | Zhao Bo will be working on this one this cycle | 15:04 |
slaweq | I think there wasn't any update on this one since last meeting: patches by topic: https://review.openstack.org/#/q/topic:qos-vpn+(status:open+OR+status:merged) | 15:04 |
mlavalle | yes, he'll get to it soon | 15:04 |
slaweq | great, thx mlavalle for info | 15:04 |
*** Leo_m has quit IRC | 15:04 | |
*** vishalmanchanda has quit IRC | 15:04 | |
slaweq | next is: | 15:05 |
slaweq | #link https://bugs.launchpad.net/neutron/+bug/1757044 | 15:05 |
openstack | Launchpad bug 1757044 in neutron "[RFE] neutron L3 router gateway IP QoS" [Wishlist,In progress] - Assigned to LIU Yulong (dragon889) | 15:05 |
slaweq | there are patches for that one: | 15:05 |
liuyulong | I will rebase the patch set since there is a conflicts patch is getting merged. | 15:05 |
slaweq | #link https://review.openstack.org/#/c/424468/ - server side patch, | 15:05 |
slaweq | #link https://review.openstack.org/#/c/568526/ - agent side patch, | 15:05 |
slaweq | in server side patch I posted some comments recently | 15:05 |
liuyulong | Yes, waiting for a rebase. | 15:05 |
slaweq | I'm now not sure if it is necessary to add additional binding between qos and router's gateway | 15:06 |
slaweq | as router's gateway has got port in neutron so why we can't just use qos policy associated to this port? | 15:06 |
liuyulong | Binding to the gateway port is already done. | 15:07 |
liuyulong | I've explained this before in the patch set. We are try to do QoS stuff for L3 IPs. | 15:08 |
liuyulong | `Binding qos to the gateway port` is something in L2 view. | 15:08 |
slaweq | but can gateway IP have more than one IP address? | 15:09 |
*** Leo_m_ has quit IRC | 15:09 | |
liuyulong | And that will influence all the traffic through the router gateway port. | 15:09 |
*** Leo_m has joined #openstack-meeting | 15:09 | |
liuyulong | Yep, the patch now handle all the gateway IPv4 set. | 15:10 |
slaweq | ok, I will have to take a look at it once again then | 15:11 |
*** longkb has quit IRC | 15:11 | |
*** cloudrancher has quit IRC | 15:12 | |
slaweq | lets move on then | 15:12 |
slaweq | next one: #link https://bugs.launchpad.net/neutron/+bug/1777627 | 15:12 |
openstack | Launchpad bug 1777627 in neutron "RFE: QoS – rule's management (set,delete, show…) requires <qos-policy> parameter in addition to <rule-id>" [Wishlist,In progress] - Assigned to Miguel Lavalle (minsel) | 15:12 |
slaweq | We have merged neutron-lib's api definition for that: https://review.openstack.org/#/q/topic:bug/1777627+(status:open+OR+status:merged) | 15:12 |
slaweq | thx mlavalle :) | 15:12 |
slaweq | Now we need implementation on neutron's side also, right? | 15:12 |
mlavalle | yes | 15:12 |
mlavalle | I have patch in my local system | 15:12 |
*** jamesmcarthur has joined #openstack-meeting | 15:12 | |
mlavalle | close to b pushed | 15:12 |
slaweq | great :) | 15:12 |
mlavalle | plan was to push last night, but then the stomach flu stroke | 15:13 |
*** cloudrancher has joined #openstack-meeting | 15:13 | |
mlavalle | hoping to push it later today | 15:13 |
slaweq | no worries, pleaese push it when You will feel better :) | 15:13 |
slaweq | and the last one on my list is: | 15:14 |
slaweq | #link https://bugs.launchpad.net/neutron/+bug/1578989 | 15:14 |
openstack | Launchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Bence Romsics (bence-romsics) | 15:14 |
slaweq | rubasov: lajoskatona_: any updates? | 15:14 |
rubasov | lajoskatona_: do you want to give an update this week? | 15:14 |
lajoskatona_ | rubasov: sure | 15:14 |
lajoskatona_ | slaweq: I think we ar eprogresing slowly, as I checked we have some merged patches in neutron side, thatnks for the review. | 15:15 |
lajoskatona_ | slaweq: otherwise we started to concentrate more on the Berlin demo, rubasov and gibi has some slides, and I try to have some working lab environment, hope that will be ok | 15:16 |
slaweq | sure, lets focus on that for now :) | 15:16 |
slaweq | we can continue work on patches after summit | 15:16 |
lajoskatona_ | slaweq: by progressing slowly, I meant I feel it quite good, but we need some "mini retro" to see if we will be ready as we planned :-) | 15:16 |
lajoskatona_ | slaweq: thanks | 15:17 |
slaweq | ok, thx for update lajoskatona_ | 15:19 |
slaweq | that's all about RFEs which I have for today | 15:19 |
slaweq | anyone wants to add something? | 15:19 |
* mlavalle has https://review.openstack.org/#/c/581364/ next in his pile | 15:19 | |
rubasov | mlavalle: cool, thanks | 15:20 |
slaweq | ok, lets move on to the next topic then | 15:22 |
slaweq | #topic Bugs | 15:22 |
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)" | 15:22 | |
slaweq | there isn't anything new related to qos here | 15:22 |
slaweq | so let's only talk about few existing bugs | 15:22 |
slaweq | #link https://bugs.launchpad.net/neutron/+bug/1784006 | 15:22 |
openstack | Launchpad bug 1784006 in neutron "Instances miss neutron QoS on their ports after unrescue and soft reboot" [Medium,Confirmed] - Assigned to Miguel Lavalle (minsel) | 15:22 |
slaweq | mlavalle: any progress on this one? | 15:22 |
mlavalle | no, I haven't made progress on this one | 15:23 |
slaweq | ok | 15:24 |
slaweq | next one is: | 15:24 |
slaweq | #link https://bugs.launchpad.net/neutron/+bug/1776160 | 15:25 |
openstack | Launchpad bug 1776160 in neutron "'burst' does not take effect for neutron egress qos bindlimit by ovs" [Undecided,New] | 15:25 |
slaweq | and this is still not confirmed as I didn't have any time for that | 15:25 |
slaweq | if there is anyone who wants to verfify (and then fix) it, that would be great :) | 15:25 |
*** armax has joined #openstack-meeting | 15:25 | |
ralonsoh | slaweq: maybe at the end of this week | 15:26 |
slaweq | ralonsoh: sure, thx a lot | 15:26 |
slaweq | :) | 15:26 |
slaweq | it's already waiting many weeks so that should be not a problem at all ;) | 15:26 |
slaweq | ok, and the last one on the list is: | 15:27 |
slaweq | #link https://bugs.launchpad.net/neutron/+bug/1785189 | 15:27 |
openstack | Launchpad bug 1785189 in neutron "Floatingip and router bandwidth speed limit failure" [Undecided,In progress] - Assigned to Brian Haley (brian-haley) | 15:27 |
slaweq | patch for it is proposed: https://review.openstack.org/#/c/596637/ | 15:27 |
slaweq | but it's waiting for reply for liuyulong's questions still | 15:28 |
slaweq | and I'm not sure if author of this patch is really interested in contining work on it | 15:29 |
slaweq | *continue work on it | 15:29 |
liuyulong | We set 64kb for a really long time since then. | 15:29 |
slaweq | liuyulong: IIRC packets bigger than this MTU value will be simply dropped by tc from qdisc | 15:30 |
liuyulong | slaweq, yes, it should be. | 15:32 |
slaweq | so why You are asking about "what happened to this 68130 length packet,"? | 15:32 |
*** kopecmartin is now known as kopecmartin|off | 15:33 | |
slaweq | liuyulong: so why You think that changing this value is not good idea? | 15:35 |
slaweq | I didn't test that but from what I can see in https://launchpadlibrarian.net/383646973/result.pdf it looks that this solves some problem in fact, no? | 15:35 |
liuyulong | TC does not drop it since the MTU is now 70kb, but what happened on the physical host NIC or the physical switch? | 15:35 |
*** ianychoi_ has joined #openstack-meeting | 15:36 | |
liuyulong | Because I can still see some RETY according to the author's test result. | 15:36 |
slaweq | ok, lets wait for reply from author of the patch maybe | 15:37 |
slaweq | that's all from what I have for today | 15:38 |
slaweq | anyone wants to talk about something else? | 15:38 |
slaweq | #topic Open Discussion | 15:38 |
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)" | 15:38 | |
slaweq | if no, I think we can finish a bit earlier today | 15:38 |
mlavalle | Thabks! | 15:39 |
ralonsoh | bye! | 15:39 |
mlavalle | thanks! | 15:39 |
slaweq | #endmeeting | 15:39 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 15:39 | |
rubasov | bye | 15:39 |
openstack | Meeting ended Tue Oct 23 15:39:21 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:39 |
slaweq | thx for attending :) | 15:39 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-10-23-15.00.html | 15:39 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-10-23-15.00.txt | 15:39 |
slaweq | o/ | 15:39 |
openstack | Log: http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-10-23-15.00.log.html | 15:39 |
*** e0ne has quit IRC | 15:39 | |
lajoskatona_ | bye | 15:39 |
*** lajoskatona_ has quit IRC | 15:39 | |
*** rubasov has left #openstack-meeting | 15:40 | |
*** ianychoi has quit IRC | 15:40 | |
liuyulong | bye team, and good night~ | 15:40 |
*** liuyulong is now known as liuyulong|away | 15:41 | |
slaweq | #startmeeting neutron_ci | 16:00 |
openstack | Meeting started Tue Oct 23 16:00:36 2018 UTC and is due to finish in 60 minutes. The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:00 |
slaweq | hi | 16:00 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:00 |
*** openstack changes topic to " (Meeting topic: neutron_ci)" | 16:00 | |
openstack | The meeting name has been set to 'neutron_ci' | 16:00 |
mlavalle | o/ | 16:00 |
*** ShilpaSD has left #openstack-meeting | 16:00 | |
ralonsoh | o/ | 16:00 |
*** rfolco|rucker is now known as rfolco|brb | 16:01 | |
slaweq | #topic Actions from previous meetings | 16:01 |
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)" | 16:01 | |
slaweq | lets start | 16:01 |
slaweq | slaweq to continue checking how jobs will run on Bionic nodes | 16:01 |
slaweq | I didn't have time to work on this during last week | 16:02 |
slaweq | sorry for that | 16:02 |
slaweq | I will assign it to my for next week also | 16:02 |
slaweq | #action slaweq to continue checking how jobs will run on Bionic nodes | 16:02 |
slaweq | next one: | 16:02 |
slaweq | mlavalle to continue debugging issue with not reachable FIP in scenario jobs | 16:02 |
mlavalle | I went over a coouple more failures | 16:03 |
mlavalle | and left notes in the bug | 16:03 |
mlavalle | I created an enviroment to test it loclly | 16:03 |
mlavalle | locally | 16:03 |
njohnston | o/ | 16:03 |
mlavalle | so I am running it | 16:03 |
mlavalle | in my local environment | 16:03 |
slaweq | and was You able to reproduce it locally? | 16:04 |
mlavalle | not yet | 16:04 |
mlavalle | I'll try today and tomorrow | 16:04 |
mlavalle | if I don't succeed then I will try to debug in zuul | 16:04 |
mlavalle | following slaweq's recipe | 16:04 |
slaweq | ok, thx for update and for working on this mlavalle | 16:05 |
slaweq | #action mlavalle to continue debugging issue with not reachable FIP in scenario jobs | 16:05 |
slaweq | ok, next one is | 16:05 |
slaweq | * mlavalle to send an email about moving tempest plugins from stadium to separate repo | 16:05 |
mlavalle | I did earlier today | 16:05 |
mlavalle | http://lists.openstack.org/pipermail/openstack-dev/2018-October/135977.html | 16:06 |
slaweq | thx mlavalle | 16:06 |
slaweq | lets wait for response from stadium projects now | 16:07 |
slaweq | next one was: | 16:07 |
slaweq | * slaweq to report a bug about issue with process ending in fullstack tests | 16:07 |
slaweq | Done: https://bugs.launchpad.net/neutron/+bug/1798472 | 16:07 |
openstack | Launchpad bug 1798472 in neutron "Fullstack tests fails because process is not killed properly" [High,Confirmed] | 16:07 |
slaweq | I only reported it but I didn't have possibility to work on this | 16:07 |
slaweq | so it's free to take if someone wants :) | 16:08 |
slaweq | it's maybe not "low-hanging-fruit" but may be interesting to debug ;) | 16:08 |
mlavalle | I might take it after I finsih debugging the previous to do that I have | 16:08 |
slaweq | thx mlavalle | 16:08 |
slaweq | ok, next one: | 16:09 |
slaweq | * haleyb to check issue with failing FIP transition to down state | 16:09 |
slaweq | I think haleyb is not around today | 16:09 |
haleyb | i just got here | 16:09 |
*** felipemonteiro has quit IRC | 16:09 | |
slaweq | ohh, hi haleyb :) | 16:09 |
haleyb | i looked into it, test seems good still, don't know why associated port gets into BUILD state, still looking | 16:09 |
slaweq | so it's port to which FIP is associated is in build state? | 16:10 |
haleyb | right, so fip stays in ACTIVE (from my memory) | 16:11 |
haleyb | so i'll continue the fight | 16:12 |
slaweq | can it be maybe related to https://review.openstack.org/#/c/606827/ somehow? | 16:13 |
slaweq | there is info that port may stuck in DOWN state but I don't know, maybe it's something similar? | 16:14 |
haleyb | i'll look, but in the original issue there is no live migration, it just removes the device from the VM | 16:15 |
slaweq | ahh, ok | 16:15 |
slaweq | so maybe that other issue then | 16:15 |
slaweq | from what I know port is in BUILD if L2 agent will not send info that port is ACTIVE (or DOWN) | 16:15 |
slaweq | so You should check in L2 agent's logs if port was wired properly | 16:16 |
slaweq | and dig from there IMHO | 16:16 |
*** ttsiouts has quit IRC | 16:16 | |
haleyb | sure, will look there | 16:16 |
haleyb | thanks! | 16:16 |
*** annp_ has quit IRC | 16:16 | |
*** gyee has joined #openstack-meeting | 16:16 | |
slaweq | ok, move on then | 16:17 |
slaweq | next was: | 16:17 |
*** ttsiouts has joined #openstack-meeting | 16:17 | |
slaweq | slaweq to add e-r query for know fullstack issue (when bug will be reported) | 16:17 |
slaweq | Done: https://review.openstack.org/#/c/611529/ | 16:17 |
slaweq | patch is merged already | 16:17 |
slaweq | and that's all for actions from previous week | 16:18 |
slaweq | anyone wants to add anything? | 16:18 |
mlavalle | not me | 16:18 |
slaweq | ok, lets move on then | 16:18 |
slaweq | #topic Grafana | 16:18 |
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)" | 16:18 | |
slaweq | #link http://grafana.openstack.org/dashboard/db/neutron-failure-rate | 16:19 |
slaweq | there was some spike during the weekend on some jobs, but as it was similar on man different jobs I suspect it's related to some infra issue maybe | 16:20 |
slaweq | I don't know about anything on our side which could cause such issue | 16:21 |
*** ttsiouts has quit IRC | 16:21 | |
slaweq | anything specific You want to discuss now? | 16:21 |
mlavalle | no, I'm good | 16:22 |
slaweq | or can we go to talk about different jobs as usually? | 16:22 |
mlavalle | yes, let's do that | 16:22 |
slaweq | #topic fullstack/functional | 16:22 |
*** openstack changes topic to "fullstack/functional (Meeting topic: neutron_ci)" | 16:22 | |
slaweq | speaing about fullstack, I found 2 issues recently | 16:23 |
slaweq | one was mentioned before: * https://bugs.launchpad.net/neutron/+bug/1798472 | 16:23 |
openstack | Launchpad bug 1798472 in neutron "Fullstack tests fails because process is not killed properly" [High,Confirmed] | 16:23 |
slaweq | and second is * https://bugs.launchpad.net/neutron/+bug/1798475 | 16:23 |
openstack | Launchpad bug 1798475 in neutron "Fullstack test test_ha_router_restart_agents_no_packet_lost failing" [High,Confirmed] | 16:23 |
slaweq | where looks that restart of L3 agents with ha routers again cause some packet loss sometimes | 16:24 |
mlavalle | They are in haleyb's bug report | 16:24 |
slaweq | mlavalle: yes, both are there | 16:24 |
slaweq | currently it's not hitting as very often but if this second issue will be very annoying we can mark this test as unstable | 16:26 |
slaweq | but I would like first to try to fix it maybe :) | 16:26 |
slaweq | and speaking about functional tests, we also have still some issues there | 16:26 |
slaweq | I still saw sometimes that db migration tests are still failing, even with timeout set to 300 seconds | 16:27 |
slaweq | I checked in logs that those tests can take even up to 400 seconds (I found such numbers at least) | 16:28 |
slaweq | so I proposed another patch: https://review.openstack.org/#/c/612505/ | 16:28 |
slaweq | I know that it's not the best "solution" but I don't think we can do anything else with it :/ | 16:28 |
slaweq | so please check that patch | 16:28 |
mlavalle | I just +2ed it | 16:29 |
slaweq | thx mlavalle | 16:29 |
mlavalle | and I will push it when zuul returns green | 16:29 |
slaweq | and second issue which I found from time to time is failing test: neutron.tests.functional.agent.l3.test_ha_router.LinuxBridgeL3HATestCase.test_ha_router_namespace_has_ipv6_forwarding_disabled | 16:29 |
slaweq | like e.g. in http://logs.openstack.org/37/610737/2/gate/neutron-functional/286402b/logs/testr_results.html.gz | 16:29 |
slaweq | I think that it may be related to failing fullstack test: https://bugs.launchpad.net/neutron/+bug/1798475 but that should be checked in logs first | 16:30 |
openstack | Launchpad bug 1798475 in neutron "Fullstack test test_ha_router_restart_agents_no_packet_lost failing" [High,Confirmed] | 16:30 |
slaweq | and I will check that this week | 16:30 |
slaweq | #action slaweq to check if failing test_ha_router_namespace_has_ipv6_forwarding_disabled is related to bug https://bugs.launchpad.net/neutron/+bug/1798475 | 16:31 |
slaweq | and that's all about fullstack/functional for today on my side | 16:31 |
slaweq | do You want to add something? | 16:31 |
mlavalle | +1 | 16:31 |
mlavalle | no | 16:32 |
slaweq | ok, so next topic | 16:32 |
slaweq | #topic Tempest/Scenario | 16:32 |
*** openstack changes topic to "Tempest/Scenario (Meeting topic: neutron_ci)" | 16:32 | |
slaweq | I was looking at tempest jobs this week | 16:32 |
slaweq | and I found out that we have some timeouts reached for neutron-tempest-xxx jobs from time to time | 16:33 |
slaweq | it hits jobs like: | 16:33 |
slaweq | neutron-tempest-iptables_hybrid | 16:33 |
*** iyamahat has joined #openstack-meeting | 16:33 | |
slaweq | neutron-tempest-linuxbridge | 16:33 |
slaweq | and | 16:34 |
slaweq | neutron-tempest-dvr | 16:34 |
slaweq | all of them has got timeout configured for 7800 seconds | 16:34 |
slaweq | maybe we should increase it? | 16:34 |
mlavalle | we can give it a try | 16:34 |
slaweq | I can imagine that sometimes job can go to cloud node which is under heavy load and tests runs slower there | 16:35 |
slaweq | so I think it's better to wait e.g. 3h for results then recheck | 16:35 |
slaweq | and from what I was checking neutron related tests aren't in top of longest ones in those jobs :) | 16:35 |
slaweq | so mlavalle, would it be good to add 1h to those timeouts? | 16:36 |
mlavalle | yes | 16:36 |
slaweq | ok, I will do that | 16:36 |
*** yamahata has quit IRC | 16:36 | |
njohnston | +1 | 16:36 |
slaweq | #action slaweq to increase neutron-tempest jobs timeouts | 16:37 |
slaweq | I hope it will make jobs at least a bit more stable | 16:37 |
slaweq | that's all from me about scenario/tempest jobs for this week | 16:37 |
slaweq | do You have anything to add? | 16:37 |
mlavalle | nope | 16:37 |
slaweq | so last topic for today is | 16:38 |
slaweq | #topic Open discussion | 16:38 |
*** openstack changes topic to "Open discussion (Meeting topic: neutron_ci)" | 16:38 | |
slaweq | and I wanted to ask here about few things | 16:38 |
slaweq | first of all: we have currently 2 quite big topics related to CI jobs: | 16:38 |
slaweq | running jobs with python 3 | 16:38 |
slaweq | and second | 16:38 |
slaweq | use of Bionic instead of Xenial | 16:39 |
njohnston | indeed | 16:39 |
slaweq | what do You think to add to agenda of this meeting topics about those two things? | 16:39 |
slaweq | to track progress on both of them weekly? | 16:39 |
njohnston | sure, I think that is a good idea | 16:39 |
mlavalle | that's a good proposal | 16:39 |
slaweq | ok, so I will include it in next meeting then, thx :) | 16:40 |
slaweq | and also I have one more question | 16:40 |
slaweq | related to patch https://review.openstack.org/#/c/573933/ | 16:40 |
slaweq | it's waiting for review since long time | 16:40 |
*** iyamahat has quit IRC | 16:41 | |
slaweq | but I'm not sure if we really want to maintain something like that in our repo | 16:41 |
slaweq | so I wanted to ask You about opinions about it | 16:41 |
slaweq | it You didn't saw it yet, please add it to Your review list and check it this week maybe | 16:41 |
mlavalle | I'll look at it slowly and leave my comments | 16:41 |
slaweq | thx mlavalle | 16:42 |
njohnston | Since it's meant for developers to run by hand, it seems to me it's more of a dev tool than a CI tool at least at this point | 16:42 |
*** a-pugachev has quit IRC | 16:42 | |
njohnston | I'll have to run it and see what he's trying to do | 16:42 |
slaweq | njohnston: yes, for me it's some kind of UT framework for bash | 16:42 |
slaweq | and I'm not sure it is something what should land in our repo but I would like to know others' opinion about it :) | 16:44 |
slaweq | ok, and that's all from my side for today | 16:44 |
mlavalle | cool | 16:44 |
slaweq | anything else You want to discuss? | 16:44 |
mlavalle | not from me | 16:44 |
* mlavalle is going to rest for a while | 16:44 | |
ralonsoh | get well soon | 16:44 |
slaweq | ok, thx for attending guys | 16:45 |
mlavalle | thanks! | 16:45 |
ralonsoh | bye | 16:45 |
slaweq | and feel better soon mlavalle :) | 16:45 |
mlavalle | thanks! | 16:45 |
slaweq | #endmeeting | 16:45 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 16:45 | |
openstack | Meeting ended Tue Oct 23 16:45:33 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:45 |
slaweq | o/ | 16:45 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-10-23-16.00.html | 16:45 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-10-23-16.00.txt | 16:45 |
openstack | Log: http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-10-23-16.00.log.html | 16:45 |
mlavalle | o/ | 16:45 |
*** armstrong has joined #openstack-meeting | 16:46 | |
*** jamesmcarthur has quit IRC | 16:46 | |
*** a-pugachev has joined #openstack-meeting | 16:47 | |
*** a-pugachev has quit IRC | 16:50 | |
*** vishalmanchanda has joined #openstack-meeting | 16:52 | |
*** raildo has joined #openstack-meeting | 16:55 | |
*** dtruong has quit IRC | 16:56 | |
*** iyamahat has joined #openstack-meeting | 17:05 | |
*** iyamahat has quit IRC | 17:05 | |
*** iyamahat has joined #openstack-meeting | 17:06 | |
*** bobh has quit IRC | 17:08 | |
*** e0ne has joined #openstack-meeting | 17:08 | |
*** bobh has joined #openstack-meeting | 17:09 | |
*** bobh has quit IRC | 17:14 | |
*** iyamahat_ has joined #openstack-meeting | 17:15 | |
*** rfolco|brb is now known as rfolco|rucker | 17:16 | |
*** lbragstad is now known as lbragstad_f00d | 17:17 | |
*** aojeagarcia has quit IRC | 17:18 | |
*** iyamahat has quit IRC | 17:18 | |
*** yamahata has joined #openstack-meeting | 17:24 | |
*** tpsilva has joined #openstack-meeting | 17:40 | |
*** e0ne has quit IRC | 17:45 | |
*** lbragstad_f00d is now known as lbragstad | 17:45 | |
*** felipemonteiro has joined #openstack-meeting | 17:45 | |
*** ralonsoh has quit IRC | 17:57 | |
*** gary_perkins has quit IRC | 18:00 | |
*** bobh has joined #openstack-meeting | 18:07 | |
*** jamesmcarthur has joined #openstack-meeting | 18:07 | |
*** jamesmcarthur has quit IRC | 18:08 | |
*** jamesmcarthur has joined #openstack-meeting | 18:09 | |
*** cloudrancher has quit IRC | 18:10 | |
*** cloudrancher has joined #openstack-meeting | 18:10 | |
*** bobh has quit IRC | 18:12 | |
*** apetrich has quit IRC | 18:16 | |
*** apetrich has joined #openstack-meeting | 18:17 | |
*** bobh has joined #openstack-meeting | 18:28 | |
*** e0ne has joined #openstack-meeting | 18:31 | |
*** e0ne has quit IRC | 18:31 | |
*** felipemonteiro has quit IRC | 18:34 | |
*** irclogbot_3 has joined #openstack-meeting | 18:35 | |
*** chandankumar is now known as chkumar|off | 18:37 | |
*** gary_perkins has joined #openstack-meeting | 18:41 | |
*** Shrews has joined #openstack-meeting | 18:51 | |
*** bobh has quit IRC | 18:57 | |
*** dmsimard has joined #openstack-meeting | 18:59 | |
clarkb | Hello infra, anyone here for the meeting? | 19:00 |
corvus | yay! | 19:00 |
ssbarnea | me | 19:00 |
gary_perkins | o/ Hi! | 19:00 |
Shrews | i'm here for the cookies | 19:00 |
clarkb | oh no I forgot the cookies | 19:01 |
clarkb | #startmeeting infra | 19:01 |
openstack | Meeting started Tue Oct 23 19:01:10 2018 UTC and is due to finish in 60 minutes. The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot. | 19:01 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 19:01 |
*** openstack changes topic to " (Meeting topic: infra)" | 19:01 | |
openstack | The meeting name has been set to 'infra' | 19:01 |
ianw | o. | 19:01 |
clarkb | #link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting | 19:01 |
ianw | o/ | 19:01 |
clarkb | #topic Announcements | 19:01 |
*** openstack changes topic to "Announcements (Meeting topic: infra)" | 19:01 | |
clarkb | Just another friendly reminder that the summit and forum fast appraoch and you may wish to double check the schedule | 19:01 |
clarkb | #link https://www.openstack.org/summit/berlin-2018/summit-schedule/#track=262 Berlin Forum schedule up for feedback | 19:01 |
fungi | so fast | 19:02 |
clarkb | I think it is fairly solid at this point so mostly just a reminder to go look at the schedule if you haven't arleady. Unsure if changes can be made easily now | 19:02 |
clarkb | fungi: There is rumor that food awaits me after the meeting. Good motivation :) | 19:02 |
fungi | oh, i was simply commenting on the fast approach of the summit and forum | 19:03 |
clarkb | oh that :) | 19:03 |
fungi | but yes, fast food too | 19:03 |
clarkb | indeed it is like 3 weeks away | 19:03 |
clarkb | I'll be visiting the dentist tomorrow midday, but don't expect any drilling or drugs to happen so should be around. Otherwise not seen any announcements | 19:03 |
clarkb | #topic Actions from last meeting | 19:04 |
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)" | 19:04 | |
clarkb | #link http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-10-16-19.01.txt minutes from last meeting | 19:04 |
clarkb | No explicit actions called out but we did some work on things we talked about (which we'll get to later in the agenda) | 19:04 |
*** weshay has joined #openstack-meeting | 19:05 | |
clarkb | #topic Specs approval | 19:05 |
*** openstack changes topic to "Specs approval (Meeting topic: infra)" | 19:05 | |
clarkb | Any specs we should be aware of? I think we are mostly head down on implementing work that is already captured by specs or general maintenance | 19:05 |
clarkb | I guess the storyboard spec is still outstanding. And I keep meaning to read it | 19:06 |
fungi | you and a bunch of us | 19:06 |
fungi | well, at least me anyway | 19:06 |
clarkb | #link https://review.openstack.org/#/c/607377/ Storyboard attachments spec. Not ready, but input would be helpful | 19:06 |
clarkb | frickler has review comments. diablo_rojo not sure if you've seen those | 19:07 |
clarkb | #topic Priority Efforts | 19:08 |
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)" | 19:08 | |
clarkb | #topic Storyboard | 19:08 |
*** openstack changes topic to "Storyboard (Meeting topic: infra)" | 19:08 | |
clarkb | That makes a good transition to storyboard topic | 19:08 |
diablo_rojo | clarkb, I saw them, was waiting for some more before I did an update | 19:08 |
diablo_rojo | just poked SotK for comments | 19:09 |
clarkb | diablo_rojo: ok, I'll try to take a look at it today after the nodepool builder work | 19:09 |
diablo_rojo | clarkb, that would be suuuper helpful | 19:09 |
diablo_rojo | fungi, too if you have some free time in between the house stuff. | 19:09 |
clarkb | mordred: not sure if you are here, but I think you started looking at using pbrx with storyboard to work on server upgrades? | 19:09 |
fungi | yep! | 19:09 |
* clarkb will try to be a stand in for mordred | 19:10 | |
clarkb | mordred volunteered to work on the storyboard trusty server upgrades and seems to have taken the appraoch of using storaybord(-dev) as an early container deployment system | 19:10 |
diablo_rojo | Seems like a good approach to me | 19:10 |
clarkb | The upside to this is as a python + js application it is actually fairly similar to zuul which means pbrx should work for it | 19:11 |
fungi | it's a fairly self-contained service so might be a good test case | 19:11 |
*** vishalmanchanda has quit IRC | 19:11 | |
*** caboucha has joined #openstack-meeting | 19:11 | |
clarkb | I want to say the early work has been in udpating bindep.txt type files to have pbrx produce working container images for storyboard | 19:11 |
clarkb | if you are interested in this aspect of the config mgmt updates this is probably a good place to follow along and/or participate | 19:11 |
fungi | the api server is straightforward and the webclient is just a wad of files that need to be splatted somewhere a webserver can find | 19:11 |
clarkb | ianw: ^ you may have thoughts in particular since you've looked at similar with graphite | 19:12 |
fungi | though there's also the need to have rabbitmq running, and also the worker process | 19:12 |
fungi | so i guess not completely straightforward | 19:12 |
clarkb | fungi: it should be a good real world application though as it isn't trivial | 19:13 |
clarkb | while still tying into the toolin we've already built | 19:13 |
ianw | clarkb: yeah, i need to get back to the actual "get docker on control plane server bit", some prelim reviews out there that didn't quite work | 19:13 |
clarkb | diablo_rojo: fungi any other storyboard topics to bring up before we move on to the config mgmt udpates? | 19:14 |
fungi | nah | 19:14 |
diablo_rojo | I don't think so. | 19:14 |
fungi | thanks! | 19:14 |
diablo_rojo | Thank you :) | 19:14 |
clarkb | #topic Config Mgmt Update | 19:14 |
*** openstack changes topic to "Config Mgmt Update (Meeting topic: infra)" | 19:14 | |
clarkb | As mentioned in the context of storyboard the work of updating our config management processes continues to happen | 19:15 |
*** e0ne has joined #openstack-meeting | 19:15 | |
fungi | i guess there are a couple base classes of work going on there? 1. contanierizing things, and 2. automatic deployment/replacement of containers? | 19:16 |
clarkb | #link https://review.openstack.org/#/c/604925/ add zuul user to bridge.o.o for CD activities could use a second review | 19:16 |
corvus | also https://review.openstack.org/609556 | 19:16 |
clarkb | fungi: ya part of the spec is the idea that we'll build images regularly to pick up updates and to avoid being stuck on insecure software unexpectedly | 19:16 |
corvus | i guess i should have used the topic on that | 19:16 |
clarkb | fungi: to make that useful we also need to update the running deployments with the newi mages | 19:16 |
clarkb | #link https://review.openstack.org/#/c/609556/ Install ansible 2.7.0 release on bridge.openstack.org | 19:17 |
clarkb | mostly I think the work here needs a few reviews. The topic:puppet-4 stuff is largely blocked on reviews as well | 19:18 |
clarkb | if we can find time to take a look at topic:puppet-4 and topic:update-cfg-mgmt we should be able to make some pretty big progress over the short term | 19:18 |
dmsimard | FWIW I sent patches to see what it would look like to enable ara on bridge.o.o, would love feedback https://review.openstack.org/#/q/topic:ara-on-bridge | 19:18 |
clarkb | #link https://review.openstack.org/#/q/topic:ara-on-bridge changes to run ara on the bridge server to visualize ansible runs there | 19:19 |
corvus | should we change the topic to update-cfg-mgmt? | 19:19 |
corvus | i think ara is in scope for that | 19:19 |
clarkb | corvus: dmsimard ++ I think this is an aid for that spec and could use the topic | 19:19 |
dmsimard | sure | 19:19 |
dmsimard | updated | 19:20 |
clarkb | Other than "please review as you can" any other items for this topic? | 19:21 |
corvus | re ara -- | 19:22 |
corvus | do we need a mysql db for that or are we going to stick with sqlite for now? | 19:22 |
dmsimard | sqlite works well in the context of executors, each job is running on it's own database | 19:22 |
dmsimard | the problem with sqlite is write concurrency | 19:22 |
fungi | sounded like there was a concurrent write issue with sqlite? | 19:22 |
fungi | yeah, that | 19:22 |
*** jamesmcarthur has quit IRC | 19:22 | |
corvus | so we should have an infra-root set up a mysql db before we land those ara changes? | 19:23 |
* mordred waves | 19:23 | |
*** pcaruana has quit IRC | 19:23 | |
fungi | do we want trove or just orchestrate a mysql service onto the bridge server? | 19:23 |
clarkb | or add that to the changes and run one locally? | 19:23 |
*** jamesmcarthur has joined #openstack-meeting | 19:23 | |
dmsimard | corvus: the legwork is done in hostvars on bridge.o.o, pabelanger helped | 19:23 |
clarkb | dmsimard: meaning there is already a mysql db running somewhere? | 19:24 |
dmsimard | yes, a trove instance | 19:24 |
corvus | dmsimard: did he provide the connection info so we can update that change to use it? | 19:25 |
dmsimard | We can definitely start with sqlite, I'm just not sure how things might behave with concurrency | 19:25 |
corvus | let's not start with sqlite, let's use the trove which apparently exists :) | 19:25 |
clarkb | and would be helpful if we remember to #status log changes like that that happen outside of config mgmt | 19:26 |
dmsimard | clarkb: my default | 19:26 |
dmsimard | fault* | 19:26 |
clarkb | corvus: ++ | 19:26 |
dmsimard | corvus: the connection information is secret though, so it needs to live on bridge.o.o ? | 19:26 |
dmsimard | I guess we could add a node to the job, install mysql on it and use that for the testinfra tests | 19:27 |
corvus | dmsimard: only the password i think; paul should have added that to private hiera and given you the key he put it under so the change can reference thta key | 19:27 |
corvus | i think sqlite is ok for testinfra | 19:27 |
*** jamesmcarthur has quit IRC | 19:27 | |
*** david-lyle has joined #openstack-meeting | 19:27 | |
fungi | if it's a trove instance, we usually keep the hostname secret too | 19:27 |
corvus | ok 2 things then :) | 19:28 |
fungi | since there is no connection security there | 19:28 |
*** dklyle has quit IRC | 19:28 | |
dmsimard | corvus: I'm the one who committed the changes, they're in hostvars for bridge.o.o as well as ara.o.o | 19:28 |
*** jamesmcarthur has joined #openstack-meeting | 19:28 | |
ianw | is there some potential for keys/passwords to make it into this? do we care? | 19:28 |
fungi | any machine for any tenant in that same region can open sockets to the trove mysql service for it, after all | 19:28 |
dmsimard | pabelanger helped me through the process of doing that, he didn't do it for me, sorry for the confusion | 19:28 |
clarkb | ianw: that was going to be my next question. Do we need to use no_log type attributes on tasks to avoid data exposure? | 19:28 |
corvus | dmsimard: oh i thought you said paul did it. ok then :) | 19:29 |
clarkb | maybe to start we should run it locally only and we have to ssh port forward into bridge to see the web server? | 19:29 |
clarkb | to get a feel for what data is exposed | 19:29 |
corvus | clarkb: wfm | 19:29 |
dmsimard | clarkb: yes | 19:29 |
dmsimard | ianw: and yes, data can be exposed | 19:29 |
fungi | sounds fine | 19:30 |
fungi | (not publishing the ara reports i mean) | 19:30 |
clarkb | ok lets start with localhost only webserver to see what we are exposing, remediate it and learn from there then maybe make it public | 19:30 |
*** jamesmcarthur has quit IRC | 19:30 | |
corvus | and go ahead and have bridge report to mysql | 19:30 |
clarkb | (goal should be making it open in some capacity though) | 19:30 |
clarkb | corvus: yup | 19:30 |
ianw | oh, i wasn't really thinking publishing the website, i was more back at "data at rest not on bridge.o.o" tbh | 19:31 |
fungi | yeah, eventually it would be nice to get back what we lost with puppetboard being abandoned | 19:31 |
dmsimard | clarkb: the original spec was to replace puppetboard | 19:31 |
corvus | dmsimard: thanks for this, it's going to help a lot :) | 19:31 |
clarkb | ianw: ah the actual db contents themselves | 19:32 |
fungi | that's also a great point | 19:32 |
*** jamesmcarthur has joined #openstack-meeting | 19:32 | |
dmsimard | are the trove instances on the public internet ? | 19:32 |
clarkb | dmsimard: no | 19:32 |
fungi | possible we're compromising the security of bridge.o.o by putting the database somewhere not locally on that server | 19:32 |
clarkb | they are on the rax private network | 19:32 |
*** bobh has joined #openstack-meeting | 19:32 | |
fungi | dmsimard: they might as well be though | 19:32 |
clarkb | which is "private" | 19:33 |
fungi | they're on the shared "private" network which all rackspace tenants can access | 19:33 |
dmsimard | if this is a concern, putting mysql on bridge.o.o is another option which would also happen to reduce latency and improve performance (i.e, no roundtrip to put stuff in a remote database far away) | 19:33 |
fungi | so you need access to a rackspace account/vm and to know (or guess) the database address and credentials | 19:33 |
fungi | or a pre-authentication zero-day vulnerability in mysql | 19:34 |
dmsimard | but then we might as well set up the web application there as well (instead of a dedicated ara.o.o server) | 19:34 |
ianw | yeah, also possibly the communications aren't encrypted? | 19:34 |
corvus | bridge is not sized correctly to even run ansible; there's no way we can add mysql there without a rebuild. | 19:34 |
fungi | ianw: no possible about it. the database connections aren't encrypted, so someone with the ability to subvert that network could also sniff them maybe? i can't remember whether they're sent in the clear or as a challenge/response | 19:35 |
clarkb | another option would be to run a mysql off host ourselves | 19:35 |
clarkb | then add encryption and such | 19:35 |
fungi | but also possible to inject into an established socket with some effort i guess | 19:35 |
clarkb | then we don't need to rebuild bridge.o.o for this | 19:36 |
dmsimard | Need to drop momentarily to pick up kids | 19:36 |
corvus | meh, we need to rebuild bridge anyway, so if we want to stick with on-host, i wouldn't count that as a strike against it | 19:36 |
clarkb | also possible trove has grown the feature to allow us to use tls/ssl for connections | 19:36 |
clarkb | corvus: fair neough | 19:36 |
fungi | maybe we use trove initially with the understanding that when (not if) we resize bridge (because it's already not appropriately-sized for ansible anyway) we add enough capacity to also put mysql on it? | 19:36 |
fungi | or also what corvus said | 19:36 |
clarkb | why don't we pick this back up in #openstack-infra when dmsimard can rejoin? and we can continue with the meeting agenda? | 19:37 |
ianw | it may also be that we consider it low risk enough that we are leaking in the first place, it doesn't matter | 19:37 |
ianw | or what fungi said :) ++ | 19:37 |
clarkb | I do think being careful around this is worthwhile while we work to understand what we are exposing | 19:37 |
corvus | yeah, we're not *supposed* to be putting private stuff in this db, the question is what happens if we accidentally do | 19:37 |
fungi | we're all just repeating one another at this point anyway, so yeah we can pick it back up in #-infra later ;) | 19:37 |
corvus | maybe we should pick it back up in #-infra later | 19:38 |
fungi | heh | 19:38 |
clarkb | #topic General topics | 19:38 |
*** openstack changes topic to "General topics (Meeting topic: infra)" | 19:38 | |
*** bobh has quit IRC | 19:38 | |
clarkb | I'll take that as a cue | 19:38 |
clarkb | OpenDev is a thing and we now have some concrete early task items planned out. Step 0 is getting dns servers running for opendev.org (thank your corvus for getting this going) | 19:39 |
clarkb | before we can start using opendev.org everywhere we need to communicate what we mean by opendev and what the goals we have are | 19:39 |
clarkb | #link https://etherpad.openstack.org/p/infra-to-opendev-messaging is the document we started working with yesterday between the infra team and the foundation staff to try and capture some of that | 19:40 |
clarkb | I will be working with the foundation staff to write up the short message with a Q&A and use that to send a community wide email type thing. There is also plan to talk about this at the summit at least at the board meeting | 19:40 |
clarkb | My hunch is once we get through the summit we'll be able to start concretely using opendev and maybe etherpad becomes etherpad.opendev.org the week after summit | 19:41 |
clarkb | Still a lot of details to sort out, I expect we'll be reviewing documents in the near future to make sure they make sense from our perspective | 19:41 |
clarkb | and for anyone wondering the current working one liner is: "Community hosted tools and infrastructure for developing and maintaining open source software." | 19:41 |
clarkb | questions, concerns about ^? | 19:42 |
fungi | i like the specificity of "free/libre open source software" but as a first go it's not bad | 19:43 |
fungi | "community hosted and operated" might also be a good expansion | 19:44 |
clarkb | Feel free to reach out to me directly as well if this venue doesn't work for you | 19:44 |
clarkb | I'm reachable via email and irc | 19:44 |
fungi | something to make it more obvious we're running these things as a community, not just hosting them for communities | 19:44 |
clarkb | fungi: you should add those thoughts to the etherpad :) | 19:44 |
fungi | yup | 19:44 |
corvus | ++ | 19:44 |
clarkb | Next item is the trusty upgrade sprint. Last week ended up being a wierd week for this as various individuals had less availabiltiy then initially anticipated | 19:45 |
*** armstrong has quit IRC | 19:46 | |
clarkb | That said I did manage to upgrade logstash.o.o, etherpad-dev.o.o, and etherpad.o.o and am working with shrews this week to delete nodepool.o.o and use our newer zookeeper cluster instead | 19:46 |
clarkb | Thank you to all of you that helped me with random reviews to make that possible | 19:46 |
*** mjturek has quit IRC | 19:46 | |
clarkb | I'd like to keep pushing on this as a persistent thing because trusty EOL is about 6 months away | 19:46 |
clarkb | if we are able to do a handful of servers a week we should be done relatively quickly | 19:46 |
clarkb | #link https://etherpad.openstack.org/p/201808-infra-server-upgrades-and-cleanup list of trusty servers that need to be upgraded. Please put your name next to those you can help with | 19:47 |
clarkb | That brings up the last thing I wanted to talk about which is the zookeeper cluster move | 19:48 |
clarkb | I got the zookeeper cluster up and running as a cluster yesterday. Shrews and I will be moving the nodepool builders to the cluster after this meeting | 19:48 |
clarkb | Those will then run for a day and a half or so to populate images on the new db | 19:48 |
clarkb | Then on thursday I'd like us to update the zookeeper config on the nodepool launchers and zuul scheduler to use the new cluster | 19:49 |
clarkb | We will likely implement this as a full cluster shutdown (may as well get everything running latest code, and maybe zuul can make a release based on that) | 19:49 |
clarkb | hrm apparently thursday is the stein-1 milestone day though :/ | 19:50 |
fungi | sounds great, thanks for working on that | 19:50 |
clarkb | we might have to wait for the milestone stuff to happen first? | 19:50 |
clarkb | I'll talk to release team after htis meeting | 19:50 |
fungi | milestone 1 is usually a non-event, especially now that openstack is no longer tagging milestones | 19:50 |
*** lbragstad has quit IRC | 19:50 | |
clarkb | oh in that case ya should be fine. But I will double check | 19:51 |
fungi | though they may force releases for cycle-with-intermediary projects which haven't released prior to the milestone week | 19:51 |
clarkb | Once all that is done we'll want to go back through and cleanup any images and nodepool nodes that are not automatically cleaned up | 19:51 |
clarkb | I'm volunteering myself to drive and do a lot of that because I do think this is an important switch and early cycle is the time to do it | 19:52 |
clarkb | you are now all warned and if you want to follow along or help let me know :) | 19:52 |
clarkb | #topic Open Discussion | 19:52 |
*** openstack changes topic to "Open Discussion (Meeting topic: infra)" | 19:52 | |
clarkb | And now ~7 minutes for anything else | 19:52 |
Shrews | we need to get them cleaned up since the image numbers will reset (and thus avoid name collisions), but we should have plenty of leeway on doing that | 19:52 |
*** lbragstad has joined #openstack-meeting | 19:53 | |
*** david-lyle is now known as dklyle | 19:53 | |
clarkb | thats a good point, but ya ~1 year of nodepool with zk should give us a big runway for that | 19:53 |
Shrews | smallest sequence number i saw was 300 some, but still plenty | 19:54 |
corvus | we will definitely. almost certainly. probably. get it all cleaned up in a year. | 19:54 |
fungi | i like your optimism! | 19:54 |
clarkb | if anyone is wondering zk has weird way of determining which ip address to listen to | 19:56 |
clarkb | you configure a list of all the cluster members and for the entry that belongs to the current host it binds to the address in that entry | 19:57 |
clarkb | so if you use hostnames that resolve to localhost because /etc/hosts then you only listen to localhost and can't talk to your cluster | 19:57 |
*** jamesmcarthur has quit IRC | 19:58 | |
clarkb | looks/sounds like we are basically done here. Thank you everyone. Find us on the openstack-infra mailing list or in #openstack-infra for further discussion | 19:58 |
clarkb | I'll go ahead and end the meeting now | 19:58 |
clarkb | #endmeeting | 19:58 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 19:58 | |
openstack | Meeting ended Tue Oct 23 19:58:25 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 19:58 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-10-23-19.01.html | 19:58 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-10-23-19.01.txt | 19:58 |
openstack | Log: http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-10-23-19.01.log.html | 19:58 |
fungi | thanks clarkb! | 19:58 |
*** Shrews has left #openstack-meeting | 19:58 | |
*** jamesmcarthur has joined #openstack-meeting | 20:02 | |
*** luobin-smile has quit IRC | 20:03 | |
*** bobh has joined #openstack-meeting | 20:05 | |
*** jamesmcarthur has quit IRC | 20:06 | |
*** jamesmcarthur has joined #openstack-meeting | 20:09 | |
*** bobh has quit IRC | 20:09 | |
*** mjturek has joined #openstack-meeting | 20:14 | |
*** cloudrancher has quit IRC | 20:21 | |
*** cloudrancher has joined #openstack-meeting | 20:22 | |
*** SWDevAngel has joined #openstack-meeting | 20:28 | |
*** ssbarnea_ has quit IRC | 20:36 | |
*** mjturek has quit IRC | 20:39 | |
*** mjturek has joined #openstack-meeting | 20:40 | |
*** mjturek has quit IRC | 20:41 | |
*** mjturek has joined #openstack-meeting | 20:44 | |
*** ttsiouts has joined #openstack-meeting | 20:56 | |
*** bobh has joined #openstack-meeting | 20:56 | |
*** bobh has quit IRC | 20:59 | |
*** bobh_ has joined #openstack-meeting | 20:59 | |
*** bobh_ has quit IRC | 21:00 | |
*** bobh has joined #openstack-meeting | 21:01 | |
*** erlon has quit IRC | 21:03 | |
*** mlavalle has left #openstack-meeting | 21:04 | |
*** e0ne has quit IRC | 21:04 | |
*** bobh has quit IRC | 21:06 | |
*** priteau has quit IRC | 21:09 | |
*** felipemonteiro has joined #openstack-meeting | 21:13 | |
*** dustins has quit IRC | 21:19 | |
*** dklyle has quit IRC | 21:19 | |
*** dklyle has joined #openstack-meeting | 21:20 | |
*** raildo has quit IRC | 21:23 | |
*** jamesmcarthur has quit IRC | 21:29 | |
*** cloudrancher has quit IRC | 21:35 | |
*** cloudrancher has joined #openstack-meeting | 21:36 | |
*** slaweq has quit IRC | 21:39 | |
*** awaugama has quit IRC | 21:39 | |
*** rtjure has quit IRC | 21:39 | |
*** cloudrancher has quit IRC | 21:40 | |
*** cloudrancher has joined #openstack-meeting | 21:40 | |
*** dustins has joined #openstack-meeting | 21:41 | |
*** munimeha1 has joined #openstack-meeting | 21:44 | |
*** felipemonteiro has quit IRC | 21:52 | |
*** felipemonteiro has joined #openstack-meeting | 21:54 | |
*** slaweq has joined #openstack-meeting | 22:04 | |
*** ttsiouts has quit IRC | 22:06 | |
*** ttsiouts has joined #openstack-meeting | 22:06 | |
*** mjturek has quit IRC | 22:08 | |
*** munimeha1 has quit IRC | 22:10 | |
*** ttsiouts has quit IRC | 22:11 | |
*** felipemonteiro has quit IRC | 22:12 | |
*** eharney has quit IRC | 22:13 | |
*** dustins has quit IRC | 22:15 | |
*** ykatabam has joined #openstack-meeting | 22:23 | |
*** rcernin has joined #openstack-meeting | 22:24 | |
*** bnemec has quit IRC | 22:25 | |
*** mriedem has quit IRC | 22:26 | |
*** slaweq has quit IRC | 22:38 | |
*** caboucha has quit IRC | 22:44 | |
*** diablo_rojo has quit IRC | 22:57 | |
*** diablo_rojo has joined #openstack-meeting | 23:08 | |
*** hongbin has quit IRC | 23:10 | |
*** slaweq has joined #openstack-meeting | 23:11 | |
*** tpsilva has quit IRC | 23:11 | |
*** ykatabam has quit IRC | 23:21 | |
*** ykatabam has joined #openstack-meeting | 23:37 | |
*** slaweq has quit IRC | 23:45 | |
*** gyee has quit IRC | 23:46 | |
*** mjturek has joined #openstack-meeting | 23:59 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!