*** slaweq has quit IRC | 00:03 | |
*** artom has joined #openstack-meeting | 00:05 | |
*** jgriffith has quit IRC | 00:22 | |
*** slaweq has joined #openstack-meeting | 00:23 | |
*** jgriffith has joined #openstack-meeting | 00:24 | |
*** mriedem_away has quit IRC | 00:30 | |
*** ykatabam has quit IRC | 00:30 | |
*** ykatabam has joined #openstack-meeting | 00:32 | |
*** slaweq has quit IRC | 00:33 | |
*** yamamoto has quit IRC | 00:34 | |
*** mattw4 has quit IRC | 00:44 | |
*** brault has joined #openstack-meeting | 00:44 | |
*** brault has quit IRC | 00:49 | |
*** diablo_rojo has quit IRC | 00:49 | |
*** slaweq has joined #openstack-meeting | 00:51 | |
*** ziyu has joined #openstack-meeting | 00:55 | |
*** XSM_HUST has joined #openstack-meeting | 00:57 | |
*** zhangchi has joined #openstack-meeting | 00:58 | |
*** Liang__ has joined #openstack-meeting | 01:00 | |
*** Yipei has joined #openstack-meeting | 01:02 | |
zhangchi | #startmeeting tricircle | 01:03 |
---|---|---|
openstack | Meeting started Wed Jun 5 01:03:10 2019 UTC and is due to finish in 60 minutes. The chair is zhangchi. Information about MeetBot at http://wiki.debian.org/MeetBot. | 01:03 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 01:03 |
*** openstack changes topic to " (Meeting topic: tricircle)" | 01:03 | |
openstack | The meeting name has been set to 'tricircle' | 01:03 |
*** njohnston has quit IRC | 01:03 | |
*** slaweq has quit IRC | 01:03 | |
zhangchi | Morning Yipei | 01:03 |
Yipei | hi, zhangchi | 01:03 |
XSM_HUST | hi all | 01:03 |
zhangchi | Hi Yipei XSM Nice to meet you all | 01:04 |
zhangchi | is every one here | 01:04 |
zhangchi | welcome back to our bi-weekly meeting | 01:04 |
ziyu | hi | 01:05 |
zhangchi | hi ziyu | 01:05 |
zhangchi | let check and begin our topics today | 01:05 |
zhangchi | The container eviroment need zun and kuyrr add configuration | 01:08 |
zhangchi | #info XSM_hust I think you can submit a bug or patch on lanuchpad | 01:09 |
XSM_HUST | ok | 01:09 |
zhangchi | ziyu what about you ipv6_mode function test | 01:11 |
ziyu | that already merged | 01:12 |
ziyu | I with yaguang are studying zull v3 | 01:12 |
ziyu | maybe you can help us to have a look, after the meeting. | 01:12 |
zhangchi | ok let's check the zull v3 later | 01:16 |
ziyu | good! | 01:17 |
*** cyg has joined #openstack-meeting | 01:17 | |
*** enriquetaso has quit IRC | 01:21 | |
*** slaweq has joined #openstack-meeting | 01:21 | |
zhangchi | some format changed between zuul v3 and v2 | 01:23 |
zhangchi | https://docs.openstack.org/infra/system-config/zuulv3.html | 01:24 |
ziyu | thank you! | 01:24 |
zhangchi | xiaohan is now working on funtional test over 80%, now reached 78% | 01:25 |
Yipei | Sorry, guys, I have some personal business to address. I have to leave now. | 01:25 |
zhangchi | ok Yipei take your time | 01:26 |
Yipei | Thank you, bye | 01:26 |
*** baojg has joined #openstack-meeting | 01:26 | |
*** boxiang has quit IRC | 01:26 | |
zhangchi | Ok bye Yipei | 01:27 |
*** Yipei has quit IRC | 01:27 | |
*** boxiang has joined #openstack-meeting | 01:27 | |
zhangchi | what about the else topics now | 01:28 |
zhangchi | #info xsm please show me the bugs link later we'all check later | 01:29 |
XSM_HUST | ok | 01:29 |
*** zhangchi has quit IRC | 01:33 | |
*** ziyu has quit IRC | 01:33 | |
*** slaweq has quit IRC | 01:33 | |
*** cyg has quit IRC | 01:35 | |
*** cyg has joined #openstack-meeting | 01:35 | |
*** zhangchi has joined #openstack-meeting | 01:36 | |
zhangchi | right now we are planning to make tricirle and trio2o working together, on plan stage now | 01:36 |
zhangchi | any other topics now | 01:38 |
zhangchi | if not we'all end right now | 01:39 |
zhangchi | bye | 01:39 |
zhangchi | #endmeeting | 01:39 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 01:39 | |
openstack | Meeting ended Wed Jun 5 01:39:29 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 01:39 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/tricircle/2019/tricircle.2019-06-05-01.03.html | 01:39 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/tricircle/2019/tricircle.2019-06-05-01.03.txt | 01:39 |
openstack | Log: http://eavesdrop.openstack.org/meetings/tricircle/2019/tricircle.2019-06-05-01.03.log.html | 01:39 |
*** zhangchi has quit IRC | 01:39 | |
*** rfolco has quit IRC | 01:46 | |
*** hongbin has joined #openstack-meeting | 01:47 | |
*** rfolco has joined #openstack-meeting | 01:47 | |
*** cyg has quit IRC | 01:53 | |
*** XSM_HUST has quit IRC | 01:54 | |
*** slaweq has joined #openstack-meeting | 01:54 | |
*** ykatabam has quit IRC | 01:55 | |
*** apetrich has quit IRC | 01:57 | |
*** XSM_HUST has joined #openstack-meeting | 01:58 | |
*** lseki has quit IRC | 02:02 | |
*** slaweq has quit IRC | 02:03 | |
*** lbragstad has quit IRC | 02:14 | |
*** slaweq has joined #openstack-meeting | 02:14 | |
*** boxiang_ has joined #openstack-meeting | 02:16 | |
*** boxiang has quit IRC | 02:18 | |
*** yamamoto has joined #openstack-meeting | 02:23 | |
*** slaweq has quit IRC | 02:25 | |
*** slaweq has joined #openstack-meeting | 02:41 | |
*** ykatabam has joined #openstack-meeting | 02:43 | |
*** yamahata has quit IRC | 02:48 | |
*** iyamahat_ has quit IRC | 02:49 | |
*** slaweq has quit IRC | 02:54 | |
*** markvoelker has joined #openstack-meeting | 02:59 | |
*** XSM_HUST has quit IRC | 03:15 | |
*** slaweq has joined #openstack-meeting | 03:15 | |
*** slaweq has quit IRC | 03:26 | |
*** markvoelker has quit IRC | 03:30 | |
*** slaweq has joined #openstack-meeting | 03:42 | |
*** Liang__ has quit IRC | 03:43 | |
*** Liang__ has joined #openstack-meeting | 03:45 | |
*** hongbin has quit IRC | 03:52 | |
*** slaweq has quit IRC | 03:55 | |
*** ricolin has joined #openstack-meeting | 03:58 | |
*** gyee has quit IRC | 04:02 | |
*** imsurit has joined #openstack-meeting | 04:04 | |
*** slaweq has joined #openstack-meeting | 04:12 | |
*** ykatabam has quit IRC | 04:13 | |
*** bnemec has quit IRC | 04:23 | |
*** gmann has quit IRC | 04:23 | |
*** slaweq has quit IRC | 04:25 | |
*** bnemec has joined #openstack-meeting | 04:25 | |
*** markvoelker has joined #openstack-meeting | 04:27 | |
*** gmann has joined #openstack-meeting | 04:27 | |
*** pcaruana has joined #openstack-meeting | 04:30 | |
*** ykatabam has joined #openstack-meeting | 04:46 | |
*** markvoelker has quit IRC | 05:00 | |
*** slaweq has joined #openstack-meeting | 05:02 | |
*** rubasov has quit IRC | 05:31 | |
*** kopecmartin|off is now known as kopecmartin | 05:34 | |
*** radeks has joined #openstack-meeting | 05:39 | |
*** markvoelker has joined #openstack-meeting | 05:56 | |
*** radeks_ has joined #openstack-meeting | 06:00 | |
*** radeks has quit IRC | 06:03 | |
*** markvoelker has quit IRC | 06:28 | |
*** e0ne has joined #openstack-meeting | 06:31 | |
*** takamatsu has joined #openstack-meeting | 06:32 | |
*** apetrich has joined #openstack-meeting | 06:33 | |
*** radeks_ has quit IRC | 06:39 | |
*** heikkine has joined #openstack-meeting | 06:55 | |
*** ykatabam has quit IRC | 06:58 | |
*** lpetrut has joined #openstack-meeting | 06:58 | |
*** liuyulong_ has joined #openstack-meeting | 06:58 | |
*** rcernin has quit IRC | 06:59 | |
*** brault has joined #openstack-meeting | 07:02 | |
*** tssurya has joined #openstack-meeting | 07:13 | |
*** e0ne has quit IRC | 07:15 | |
*** aloga has quit IRC | 07:23 | |
*** aloga has joined #openstack-meeting | 07:23 | |
*** tesseract has joined #openstack-meeting | 07:25 | |
*** liuyulong_ has quit IRC | 07:26 | |
*** ttsiouts has joined #openstack-meeting | 07:27 | |
*** ttsiouts has quit IRC | 07:37 | |
*** whoami-rajat has joined #openstack-meeting | 07:45 | |
*** ralonsoh has joined #openstack-meeting | 07:51 | |
*** heikkine has quit IRC | 07:58 | |
*** heikkine has joined #openstack-meeting | 08:00 | |
*** heikkine has left #openstack-meeting | 08:00 | |
*** ttsiouts has joined #openstack-meeting | 08:02 | |
*** heikkine has joined #openstack-meeting | 08:03 | |
*** tetsuro has joined #openstack-meeting | 08:05 | |
*** Lucas_Gray has joined #openstack-meeting | 08:13 | |
*** panda|ruck has quit IRC | 08:14 | |
*** markvoelker has joined #openstack-meeting | 08:26 | |
*** panda has joined #openstack-meeting | 08:28 | |
*** ykatabam has joined #openstack-meeting | 08:35 | |
*** radeks has joined #openstack-meeting | 08:38 | |
*** ykatabam has quit IRC | 08:39 | |
*** ykatabam has joined #openstack-meeting | 08:42 | |
*** tetsuro has quit IRC | 08:46 | |
*** panda is now known as panda|ruck | 08:52 | |
*** imsurit has quit IRC | 08:56 | |
*** rcernin has joined #openstack-meeting | 08:58 | |
*** markvoelker has quit IRC | 08:59 | |
*** hberaud has joined #openstack-meeting | 09:15 | |
*** priteau has joined #openstack-meeting | 09:22 | |
*** e0ne has joined #openstack-meeting | 09:30 | |
*** Liang__ has quit IRC | 09:36 | |
*** yamamoto has quit IRC | 09:50 | |
*** miloa has joined #openstack-meeting | 09:54 | |
*** markvoelker has joined #openstack-meeting | 09:57 | |
*** lpetrut has quit IRC | 10:09 | |
*** boxiang_ has quit IRC | 10:10 | |
*** boxiang has joined #openstack-meeting | 10:10 | |
*** verdurin has joined #openstack-meeting | 10:11 | |
*** ttsiouts has quit IRC | 10:15 | |
*** ttsiouts has joined #openstack-meeting | 10:16 | |
*** ttsiouts has quit IRC | 10:20 | |
*** lpetrut has joined #openstack-meeting | 10:22 | |
*** yamamoto has joined #openstack-meeting | 10:24 | |
*** baojg has quit IRC | 10:28 | |
*** markvoelker has quit IRC | 10:29 | |
*** yamamoto has quit IRC | 10:33 | |
*** yamamoto has joined #openstack-meeting | 10:34 | |
*** yamamoto has quit IRC | 10:35 | |
*** oneswig has joined #openstack-meeting | 10:38 | |
*** ricolin has quit IRC | 10:47 | |
*** yamamoto has joined #openstack-meeting | 10:48 | |
*** janders has joined #openstack-meeting | 10:51 | |
*** yamamoto has quit IRC | 10:53 | |
*** boxiang_ has joined #openstack-meeting | 10:54 | |
*** dh3 has joined #openstack-meeting | 10:55 | |
*** boxiang has quit IRC | 10:57 | |
*** martial_ has joined #openstack-meeting | 11:00 | |
oneswig | #startmeeting scientific-sig | 11:00 |
openstack | Meeting started Wed Jun 5 11:00:25 2019 UTC and is due to finish in 60 minutes. The chair is oneswig. Information about MeetBot at http://wiki.debian.org/MeetBot. | 11:00 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 11:00 |
*** openstack changes topic to " (Meeting topic: scientific-sig)" | 11:00 | |
openstack | The meeting name has been set to 'scientific_sig' | 11:00 |
oneswig | yarr \o/ | 11:00 |
janders | hi All | 11:00 |
*** mgoddard has joined #openstack-meeting | 11:00 | |
martial_ | Good morning/day/evening :) | 11:00 |
janders | oneswig: would you mind if we start with the SDN discussion? I need to pop out for half an hour soon | 11:00 |
oneswig | hi janders, g'day | 11:00 |
verdurin | Afternoon. | 11:00 |
oneswig | certainly, lets do that. | 11:01 |
oneswig | hi verdurin | 11:01 |
oneswig | #link Agenda for today https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_June_5th_2019 | 11:01 |
*** b1airo has joined #openstack-meeting | 11:01 | |
oneswig | OK, let's start by ignoring the running order... | 11:01 |
dh3 | hi all | 11:01 |
mgoddard | o/ | 11:01 |
oneswig | #topic Coherent SDN fabrics | 11:01 |
*** openstack changes topic to "Coherent SDN fabrics (Meeting topic: scientific-sig)" | 11:01 | |
b1airo | 'ello | 11:01 |
oneswig | janders: you raised this at teh PTG | 11:01 |
janders | only a brief update from my side: I've had a brief chat with the Mellanox guys. Overall they don't see an issue with this, but I'd like to get more detailed feedback off them | 11:01 |
oneswig | #chair b1airo martial_ | 11:01 |
openstack | Current chairs: b1airo martial_ oneswig | 11:02 |
janders | last week's neutron-driver meeting got cancelled so haven't spoken to the Neutron guys in detail either | 11:02 |
janders | indeed - this is follow up to the SDN consistency issues that we raised in the SIG | 11:02 |
oneswig | janders: ah that's too bad on the cancelled meeting | 11:02 |
oneswig | hi mgoddard thanks for coming | 11:02 |
oneswig | did you see what this is about? | 11:02 |
*** ttsiouts has joined #openstack-meeting | 11:03 | |
mgoddard | hi oneswig yes I did, and thought I'd pop along | 11:03 |
janders | hey Mark thanks for coming | 11:03 |
oneswig | #link Spec in review https://review.opendev.org/#/c/565463/ | 11:03 |
mgoddard | I haven't got as far through the neutron spec as I'd like | 11:03 |
oneswig | Me neither. Still a little concerned it's tied to one implementation | 11:04 |
oneswig | We could come back to this in 15 minutes to allow some reading time? | 11:05 |
hberaud | o/ | 11:05 |
janders | my understanding is they're trying to model on ODL but are trying to make the consistency check mechanism generic | 11:05 |
janders | what we can also do is - I will give you guys some time to go through this more in detail - and if you could make comments in the bug, that would be great | 11:06 |
oneswig | Hi hberaud, welcome | 11:06 |
*** yamamoto has joined #openstack-meeting | 11:06 | |
janders | doesn't have to be during the meeting | 11:06 |
hberaud | oneswig: thx | 11:06 |
oneswig | janders: +1 makes sense to get the feedback out there | 11:06 |
mgoddard | one key difference between mlnx and OVS is the async update | 11:07 |
janders | but I think if we could provide some feedback to the Neutron guys before Friday's driver meeting, that would be great | 11:07 |
mgoddard | the mellanox driver updates NEO in an async thread | 11:07 |
mgoddard | so not only have we committed the update to the neutron DB, we've actually finished processing the original update request by the time NEO is updated | 11:07 |
janders | right! that matches my experience/observations | 11:08 |
oneswig | mgoddard: in extreme cases could this cause a provisioned instance to be transiently connected to a different tenant network? Is there any means of blocking on completion of an operation? | 11:09 |
*** ociuhandu has joined #openstack-meeting | 11:09 | |
b1airo | o_0 ! | 11:10 |
mgoddard | oneswig: potentially | 11:10 |
mgoddard | oneswig: neutron does have a blocking mechanism, but I don't think mlnx uses it | 11:10 |
janders | which part of this would need to go into neutron-core, and which part would be mlnx-specific changes? | 11:10 |
mgoddard | there is a thing called provisioning blocks which can be used for this | 11:11 |
mgoddard | agents are inherently aysnc, so it's nothing new. You just have to know how to use it | 11:11 |
janders | convincing mlnx to use that definitely sounds like a good idea | 11:11 |
oneswig | Ah OK. Feature not bug | 11:11 |
janders | but how about detecting state divergence and addressing it? what we're talking about doesn't address that right? | 11:12 |
janders | or would it? | 11:12 |
mgoddard | Probably bug not feature :) | 11:12 |
b1airo | state divergence is always a potential problem if the controller can be changed/updated independently of Neutron | 11:13 |
oneswig | janders: yes this doesn't relate to the missing port updates | 11:13 |
janders | my idea behind the bug was implementing a mechanism that brings SDN-based approaches on par with ovs - so that state divergence can be detected/addressed | 11:14 |
janders | https://review.opendev.org/#/c/565463/12/specs/stein/sbi-database-consistency.rst@332 looks like it might be able to address that | 11:14 |
janders | however it would be great to have your feedback | 11:14 |
janders | in general I think it would be worthwhile to split the discussion into two parts - the generic one (which the neutron team need to address) and the specific ones (which I'm happy to bring up with Mellanox) | 11:15 |
janders | I totally see value of improvements around provisioning blocks as suggested by mgoddard | 11:16 |
oneswig | Makes sense. First part may be gated, for example, on the difficulty of associating a revision number on applied config in arbitrary SDN implementations. That's reviewing the spec I guess | 11:17 |
mgoddard | I think provisioning blocks could be an easy win | 11:17 |
mgoddard | then the spec might be able to prevent subsequent drift | 11:17 |
oneswig | janders: think you can entice your friendly mlnx engineer here for part 2? | 11:17 |
janders | I have to disappear for about half an hour now - can I please ask you to make comments on what you like/dislike/any suggestions around the generic part in the bug report? It would be great to see some activity there, it would help get attention from the devs | 11:17 |
janders | oneswig: yes, I'm happy to! :) | 11:18 |
oneswig | +1 | 11:18 |
janders | excellent - thanks guys | 11:18 |
janders | hopefully I'll be back before the end of the meeting | 11:18 |
oneswig | #action janders Involve Mellanox tech team on the issue | 11:18 |
oneswig | #action oneswig mgoddard add comments to the bug report and/or spec | 11:18 |
oneswig | OK, thanks janders and all, next | 11:19 |
*** panda|ruck is now known as panda|ruck|eat | 11:19 | |
oneswig | #topic CERN OpenStack roundup | 11:19 |
*** openstack changes topic to "CERN OpenStack roundup (Meeting topic: scientific-sig)" | 11:19 | |
oneswig | that was fun, the CERN team laid on a great day | 11:19 |
oneswig | dh3: great talk | 11:19 |
dh3 | you are too kind *blush* | 11:19 |
oneswig | How's the eagle recovering from being swabbed? :-) | 11:19 |
dh3 | I hear there are some interesting stories from field expeditions ("Real Science") | 11:20 |
oneswig | I once had a support call that ended "can we get this fixed because there's a plane flying over antartica right now that needs the service back onilne..." | 11:20 |
oneswig | In a previous job | 11:21 |
b1airo | looked like a good time on Slack and Twitter | 11:21 |
oneswig | I enjoyed it. In the afternoon the talk on OpenStack control plane tracing was especially interesting. | 11:21 |
dh3 | Yes I think osprofiler could be educational as well as useful | 11:22 |
oneswig | #link Ilya's presentation https://indico.cern.ch/event/776411/contributions/3402240/attachments/1851629/3039923/08_-_Distributed_Tracing_in_OpenStack.pptx.pdf | 11:22 |
*** ykatabam has quit IRC | 11:22 | |
oneswig | I think we'll be doing plenty of that in due course | 11:23 |
martial_ | nice, thanks | 11:24 |
*** Lucas_Gray has quit IRC | 11:24 | |
oneswig | Erwan Gallens talk on face recognition was good too - nice to cover more on the algorithms. | 11:25 |
oneswig | OK we should move on I think | 11:25 |
oneswig | #topic Secure Computing Environments | 11:26 |
*** openstack changes topic to "Secure Computing Environments (Meeting topic: scientific-sig)" | 11:26 | |
*** markvoelker has joined #openstack-meeting | 11:26 | |
oneswig | One question from the audience at CERN last week related to how to find best practice for controlled-access data processing | 11:26 |
oneswig | This is something we've attempted to grapple with previously but not got very far towards common ground. | 11:27 |
oneswig | Once more unto the breach... | 11:27 |
oneswig | Jani from Basel University and I presented on a project underway there | 11:28 |
oneswig | #link BioMedIT project in Basel https://indico.cern.ch/event/776411/contributions/3345191/attachments/1851634/3039929/05_-_Secure_IT_framework_for_Personalised_Health_data.pdf | 11:28 |
oneswig | This was a lightning talk though so no time to cover anything at all in depth | 11:28 |
martial_ | #link https://indico.cern.ch/event/776411/contributions/ | 11:28 |
martial_ | this had all the talks | 11:29 |
oneswig | cool, thanks martial_ | 11:29 |
dh3 | We don't have a best practice as such - we are still offering all the various compute/storage facilities to data owners/principal investigators and trying to help them choose the right one for their data access and analysis workload | 11:30 |
dh3 | buffet table vs a la carte I guess | 11:30 |
verdurin | On our side, the first meeting to discuss a paper about our work with restricted data is coming up. That will be science as well as infrastructure. | 11:31 |
*** ttsiouts has quit IRC | 11:31 | |
oneswig | I saw a useful paper recently on classification of security levels across various domains, but I'm struggling to find it alas | 11:32 |
*** ttsiouts has joined #openstack-meeting | 11:32 | |
b1airo | interesting set of slides | 11:32 |
b1airo | looks like a decent architecture, though the thing often missing is mapping of various controls to any particular framework of reference | 11:34 |
oneswig | Something I'd like to see is authoritative research of the form "to achieve this level of security / standard, you must implement this...' | 11:34 |
dh3 | oneswig: do you have something like ISO 27001/2 in mind? | 11:35 |
oneswig | Yes, that kind of thing, but also there are different classification systems in different sectors - government, health data, etc. | 11:36 |
*** ttsiouts has quit IRC | 11:36 | |
b1airo | yes agreed oneswig... starting with a basic multi-tenant cloud implementation, what bits of OpenStack or other standard tooling can you sprinkle in to achieve sufficient confidence in the architecture and visibility of drift or abnormalities, you then need to layer in incident response requirements, so on and so forth | 11:38 |
oneswig | b1airo: infrastructure configuration is certainly not the only requirement, true. | 11:39 |
verdurin | Yes, in my experience, lots of policies, and possibly even the setting up of new administrative bodies. | 11:40 |
oneswig | I'm drawing a blank on this paper, may follow up to the Slack workspace if I find it. | 11:40 |
b1airo | to achieve compliance with any standard there's necessarily a layer of abstraction down to specific controls, procedures (and sometimes the organisational units & heads that are responsible for them) | 11:40 |
dh3 | I've never had to work with that sort of published standard but experience says that it will reach from infra/admins through application devs too | 11:41 |
b1airo | in OpenStack today I don't think we even have a reference list of controls, let alone reference architectures | 11:42 |
oneswig | dh3: do you need specific standards to host eg UK BioBank data? (Or was that just animals and plants?) | 11:42 |
*** raildo has joined #openstack-meeting | 11:42 | |
verdurin | oneswig: it's actually more complicated than that, there are many varieties of UKB data, with their own special requirements. | 11:43 |
dh3 | oneswig: it's not really my area but I know that for some data (human identifiable) we have had to implement separate networks, virt platforms, storage.... | 11:43 |
*** yamamoto has quit IRC | 11:44 | |
oneswig | dh3: does Sanger have policy guidelines for this that are public? | 11:44 |
dh3 | our UKB vanguard data is in our production OpenStack environment, but in a separate host aggregate (for perf isolation but does bring security) and separate storage/networking (via provider network) | 11:44 |
dh3 | oneswig: not that I have seen! but I can ask | 11:45 |
heikkine | dh3 Jani from Basel here, I agree with requirement for separate networks, etc. | 11:45 |
oneswig | Might be really useful! | 11:45 |
oneswig | hi heikkine, thanks for coming | 11:45 |
heikkine | I may drop off any moment but trying to follow what I can | 11:45 |
oneswig | dh3: do you go as far as separate physical storage? | 11:46 |
dh3 | oneswig: yes in some cases, "identifiable human data" is the usual trigger but not always | 11:47 |
heikkine | dh3: what is in your case separate physical storage? Separate from OpenStack? | 11:47 |
dh3 | heikkine: taking UKB as an example, we have it on a separate Lustre system, it's only accessible from that tenant's provider network. | 11:48 |
oneswig | so separate from OpenStack and separate from other projects too | 11:49 |
janders | would software-defined-storage help in this sense? | 11:49 |
heikkine | I see. So you do tenant isolation that way. We are starting with NFS but I have done tests with BeeGFS | 11:49 |
janders | as in - having a pool of JBOFs - and then spinning up a "private" storage cluster of a certain scale on demand | 11:49 |
verdurin | We are looking at Lustre to cover this kind of case in the future, given it's more amenable than GPFS. | 11:49 |
oneswig | A substantial discussion in its own right | 11:49 |
b1airo | there are some US standards that actually specify isolated physical storage | 11:50 |
dh3 | janders: it depends - again not entirely my area but I understand that some data access agreements are restrictive on where data can be kept (physically and geographically) - and SDS makes it harder to show an auditor "it's here" | 11:50 |
oneswig | Over the summer it may be good to gather some of these pieces together into a joint study. Does anyone object to being involved? | 11:51 |
b1airo | e.g. think ITAR data cannot be mixed with non-ITAR data on same physical storage | 11:51 |
martial_ | I think this is correct, Blair | 11:51 |
b1airo | lol, love the phrasing of that question oneswig ! | 11:51 |
janders | right! whether it works is one thing, whether it ticks compliance box might be another thing. Very useful feedback, thank you. | 11:51 |
verdurin | janders: yes, to echo dh3's comments, I'm dealing with a project at the moment in which the form would not cope well with such a setup. | 11:51 |
dh3 | SDS also makes proving secure deletion more difficult (can't even identify which HDDs to take out and shred...) | 11:52 |
oneswig | b1airo: opt-out from being volunteered :-) | 11:52 |
janders | (I suppose node cleaning doesn't cut it :) | 11:52 |
dh3 | node cleaning + DBAN maybe :) | 11:52 |
b1airo | janders: actually if you are using self-encrypting disks then it might... | 11:53 |
verdurin | Don't deprive the workshop people of their longer-for chances to deploy the angle grinder | 11:53 |
verdurin | longed-for | 11:53 |
oneswig | verdurin: --yes-i-really-mean-it ... | 11:53 |
janders | :D | 11:53 |
b1airo | because we know hardware level security is so good... *cough* | 11:53 |
oneswig | One more topic to cover today, can we follow up on this perhaps via the slack channel? | 11:54 |
b1airo | sounds good | 11:54 |
oneswig | dh3: are you on there? | 11:54 |
oneswig | I can send an invite - unless you're too secure for Slack of course :-) | 11:54 |
oneswig | #topic Justification whitepaper for on premise cloud for research and scientific computing | 11:55 |
*** openstack changes topic to "Justification whitepaper for on premise cloud for research and scientific computing (Meeting topic: scientific-sig)" | 11:55 | |
dh3 | oneswig: no (not yet - do invite me please) | 11:55 |
oneswig | dh3: will do | 11:55 |
oneswig | just a quick mention, some of the US folks are very interested in pooling together on a paper that lays out the private cloud case | 11:55 |
oneswig | This was raised at the SIG session in the Denver PTG | 11:56 |
b1airo | there's a great NASA tech paper i came across today that looks at this from the HPC perspective: https://www.nas.nasa.gov/assets/pdf/papers/NAS_Technical_Report_NAS-2018-01.pdf | 11:56 |
oneswig | Anyone in this session recently made this case themselves? | 11:56 |
oneswig | thanks b1airo | 11:56 |
oneswig | During the session somebody mentioned the talk by Andrew Jones of NAG at the UKRI Cloud Workshop in January | 11:57 |
oneswig | #link Andrew Jones presentation https://www.linkedin.com/pulse/cloud-hpc-dose-reality-andrew-jones/ | 11:57 |
oneswig | The hope is that this material might make a useful resource to draw upon when writing procurement proposals. | 11:58 |
janders | lots of follow up reading after today's meeting - thanks for some great links guys | 11:58 |
b1airo | a key thing to establish early on here would be the kinds of applications that are being supported on the private cloud | 11:59 |
dh3 | hadn't seen that, thanks (but we are "strategically" going cloud-wards anyway) | 11:59 |
oneswig | b1airo: very true | 11:59 |
b1airo | and a valid answer might be "all of them" | 11:59 |
oneswig | OK nearly out of time - final comments on this? | 11:59 |
b1airo | raise it again for next week's timezone i guess | 11:59 |
*** markvoelker has quit IRC | 12:00 | |
oneswig | b1airo: +1, will do. | 12:00 |
oneswig | OK all, time to stop - thanks everyone | 12:00 |
janders | thanks guys! again - any comments in the SDN bug will be very welcome by the Neutron team | 12:00 |
martial_ | Thanks ;) | 12:00 |
oneswig | janders: will do | 12:00 |
oneswig | #endmeeting | 12:00 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 12:00 | |
openstack | Meeting ended Wed Jun 5 12:00:46 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 12:00 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/scientific_sig/2019/scientific_sig.2019-06-05-11.00.html | 12:00 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/scientific_sig/2019/scientific_sig.2019-06-05-11.00.txt | 12:00 |
openstack | Log: http://eavesdrop.openstack.org/meetings/scientific_sig/2019/scientific_sig.2019-06-05-11.00.log.html | 12:00 |
dh3 | thanks all, talk soon | 12:01 |
verdurin | Thanks, bye. | 12:01 |
oneswig | Until next time | 12:01 |
b1airo | cheerio! | 12:01 |
*** mgoddard has left #openstack-meeting | 12:02 | |
*** gmann has quit IRC | 12:03 | |
*** ricolin has joined #openstack-meeting | 12:03 | |
*** janders has quit IRC | 12:04 | |
*** ociuhandu_ has joined #openstack-meeting | 12:06 | |
*** dh3 has quit IRC | 12:06 | |
*** ociuhandu has quit IRC | 12:06 | |
*** yamamoto has joined #openstack-meeting | 12:09 | |
*** ttsiouts has joined #openstack-meeting | 12:10 | |
*** jaypipes has joined #openstack-meeting | 12:28 | |
*** panda|ruck|eat is now known as panda|ruck | 12:30 | |
*** oneswig has left #openstack-meeting | 12:35 | |
*** rcernin has quit IRC | 12:37 | |
*** priteau has quit IRC | 12:41 | |
*** radeks has quit IRC | 12:48 | |
*** radeks has joined #openstack-meeting | 12:50 | |
*** priteau has joined #openstack-meeting | 12:54 | |
*** njohnston has joined #openstack-meeting | 12:59 | |
*** ttsiouts has quit IRC | 13:01 | |
*** ttsiouts has joined #openstack-meeting | 13:01 | |
*** ttsiouts has quit IRC | 13:05 | |
*** eharney has joined #openstack-meeting | 13:06 | |
*** mriedem has joined #openstack-meeting | 13:10 | |
*** apetrich has quit IRC | 13:10 | |
*** baojg has joined #openstack-meeting | 13:11 | |
*** lbragstad has joined #openstack-meeting | 13:17 | |
*** ayoung has joined #openstack-meeting | 13:17 | |
*** ttsiouts has joined #openstack-meeting | 13:22 | |
*** apetrich has joined #openstack-meeting | 13:23 | |
*** _erlon_ has joined #openstack-meeting | 13:27 | |
*** yamamoto has quit IRC | 13:28 | |
*** cheng1__ has joined #openstack-meeting | 13:36 | |
*** lseki has joined #openstack-meeting | 13:40 | |
*** eharney has quit IRC | 13:41 | |
*** rcernin has joined #openstack-meeting | 13:42 | |
*** bobh has joined #openstack-meeting | 13:47 | |
*** jamesmcarthur has joined #openstack-meeting | 13:48 | |
*** bdperkin has quit IRC | 13:49 | |
*** bobh has quit IRC | 13:50 | |
*** dtrainor has quit IRC | 13:52 | |
*** enriquetaso has joined #openstack-meeting | 13:53 | |
*** eharney has joined #openstack-meeting | 13:57 | |
*** baojg has quit IRC | 13:59 | |
*** mlavalle has joined #openstack-meeting | 14:00 | |
mlavalle | #startmeeting neutron_l3 | 14:01 |
openstack | Meeting started Wed Jun 5 14:01:00 2019 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: neutron_l3)" | 14:01 | |
openstack | The meeting name has been set to 'neutron_l3' | 14:01 |
njohnston | o/ | 14:01 |
tidwellr | hi | 14:01 |
slaweq | hi | 14:02 |
*** eharney has quit IRC | 14:02 | |
haleyb | hi | 14:02 |
mlavalle | #topic Announcements | 14:03 |
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)" | 14:03 | |
mlavalle | Just a quick reminder that this is the Train-1 milestone week | 14:04 |
mlavalle | #link https://releases.openstack.org/train/schedule.html | 14:04 |
mlavalle | we reviewed the blueprints we were targeting for this milestone yesterday and we made solid progress | 14:05 |
mlavalle | thanks for all your hard waork | 14:05 |
*** miloa has quit IRC | 14:05 | |
mlavalle | Please also remember that July 2nd is the deadline for the Shanghai Summit CFP | 14:06 |
mlavalle | any other announcements? | 14:06 |
mlavalle | ok | 14:07 |
mlavalle | moving on | 14:07 |
mlavalle | #topic Bugs | 14:07 |
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)" | 14:07 | |
mlavalle | First one in the list is https://bugs.launchpad.net/neutron/+bug/1821912 | 14:08 |
openstack | Launchpad bug 1821912 in neutron "intermittent ssh failures in various scenario tests" [High,In progress] - Assigned to LIU Yulong (dragon889) | 14:08 |
mlavalle | slaweq: any update with the authentication problem? | 14:08 |
*** martial_ has quit IRC | 14:09 | |
slaweq | mlavalle: nope | 14:09 |
*** jamesmcarthur has quit IRC | 14:09 | |
slaweq | I didn't make any progress on this one | 14:09 |
mlavalle | still working on it? | 14:10 |
slaweq | mlavalle: I will look if I will have some time | 14:11 |
slaweq | but I can't promise it will be this or next week | 14:11 |
mlavalle | ok | 14:11 |
mlavalle | related to this is https://bugs.launchpad.net/neutron/+bug/1830763 | 14:11 |
openstack | Launchpad bug 1830763 in neutron "Debug neutron-tempest-plugin-dvr-multinode-scenario failures" [High,Confirmed] - Assigned to Miguel Lavalle (minsel) | 14:11 |
*** radeks_ has joined #openstack-meeting | 14:12 | |
mlavalle | I spent time yesterday reproducing locally the failure of test_connectivity_thorugh_2_routers | 14:12 |
mlavalle | I can reproduce it exactly as it happens in the zuul | 14:13 |
mlavalle | and the test case attempts to ping one VM from the other | 14:13 |
mlavalle | in sshing to the VM that is going to send the ping, I get an ssh failure | 14:13 |
mlavalle | so it will probably help with 1821912 | 14:14 |
mlavalle | I'll report any further discovery in both bugs | 14:14 |
*** radeks has quit IRC | 14:14 | |
mlavalle | Next one is https://bugs.launchpad.net/neutron/+bug/1831534 | 14:15 |
openstack | Launchpad bug 1831534 in neutron "[l3][dvr] with openflow security group east-west traffic between different vlan networks is broken" [High,In progress] - Assigned to LIU Yulong (dragon889) | 14:15 |
*** artom has quit IRC | 14:15 | |
mlavalle | this one recently reported | 14:15 |
*** eharney has joined #openstack-meeting | 14:15 | |
mlavalle | and liuyulong is working on a fix | 14:16 |
mlavalle | this is a related patch https://review.opendev.org/#/c/662925/ | 14:16 |
mlavalle | those are all the bugs I have today | 14:17 |
mlavalle | any other bugs we should discuss today? | 14:17 |
haleyb | i have more :( | 14:17 |
mlavalle | fire away | 14:17 |
haleyb | https://bugs.launchpad.net/neutron/+bug/1831575 | 14:17 |
openstack | Launchpad bug 1831575 in neutron "br-tun gets a wrong arp drop rule when dvr is connected to a network but not used as gateway" [High,Fix released] - Assigned to Slawek Kaplonski (slaweq) | 14:17 |
*** thgcorrea has joined #openstack-meeting | 14:17 | |
haleyb | oh, sorry, that one just merged... | 14:18 |
haleyb | there are backports to do | 14:18 |
*** Lucas_Gray has joined #openstack-meeting | 14:18 | |
haleyb | s/do/approve | 14:18 |
*** jamesmcarthur has joined #openstack-meeting | 14:18 | |
mlavalle | ok | 14:18 |
haleyb | https://bugs.launchpad.net/neutron/+bug/1831706 | 14:18 |
openstack | Launchpad bug 1831706 in neutron "[DVR] Modify `in_port` field of packets which from remote qr-* port" [Undecided,New] | 14:18 |
haleyb | there was a comment from the submitter this could be related to https://bugs.launchpad.net/neutron/+bug/1732067 | 14:19 |
openstack | Launchpad bug 1732067 in neutron "openvswitch firewall flows cause flooding on integration bridge" [High,In progress] - Assigned to Zhengdong Wu (zhengdong.wu) | 14:19 |
haleyb | liuyulong: can you take a look at that as you were also active in the review for ^^^ | 14:20 |
haleyb | i will follow-up with him since he's not here | 14:21 |
haleyb | those where the only other bugs i had | 14:21 |
mlavalle | thanks haleyb | 14:22 |
*** jamesmcarthur has quit IRC | 14:22 | |
mlavalle | #topic On demand agenda | 14:22 |
*** openstack changes topic to "On demand agenda (Meeting topic: neutron_l3)" | 14:22 | |
mlavalle | anything lese we should discuss today? | 14:23 |
*** bnemec has quit IRC | 14:23 | |
tidwellr | if anyone has a minute, I resurrected https://review.opendev.org/#/c/486450 | 14:24 |
*** bnemec has joined #openstack-meeting | 14:25 | |
mlavalle | yes, I noticed that | 14:25 |
mlavalle | I will take a look soon | 14:25 |
mlavalle | it's in my pile | 14:25 |
mlavalle | thanks for following up | 14:25 |
*** jamesmcarthur has joined #openstack-meeting | 14:26 | |
*** cheng1__ has quit IRC | 14:26 | |
mlavalle | cool | 14:26 |
mlavalle | this was a quick one | 14:26 |
mlavalle | enjoy the rest of your day | 14:26 |
mlavalle | #endmeetring | 14:27 |
mlavalle | #endmeeting | 14:27 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 14:27 | |
openstack | Meeting ended Wed Jun 5 14:27:06 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:27 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/neutron_l3/2019/neutron_l3.2019-06-05-14.01.html | 14:27 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2019/neutron_l3.2019-06-05-14.01.txt | 14:27 |
openstack | Log: http://eavesdrop.openstack.org/meetings/neutron_l3/2019/neutron_l3.2019-06-05-14.01.log.html | 14:27 |
*** dtrainor has joined #openstack-meeting | 14:27 | |
*** yamamoto has joined #openstack-meeting | 14:27 | |
slaweq | o/ | 14:27 |
*** lpetrut has quit IRC | 14:28 | |
*** b1airo has quit IRC | 14:30 | |
*** yamamoto has quit IRC | 14:32 | |
*** dtrainor has quit IRC | 14:32 | |
*** eharney has quit IRC | 14:35 | |
*** bdperkin has joined #openstack-meeting | 14:39 | |
*** mlavalle has left #openstack-meeting | 14:40 | |
*** dtrainor has joined #openstack-meeting | 14:45 | |
*** eharney has joined #openstack-meeting | 14:48 | |
*** boxiang has joined #openstack-meeting | 14:49 | |
*** akhil_jain has joined #openstack-meeting | 14:50 | |
*** artom has joined #openstack-meeting | 14:51 | |
*** lpetrut has joined #openstack-meeting | 14:52 | |
*** eharney has quit IRC | 14:54 | |
*** lpetrut has quit IRC | 14:54 | |
*** lpetrut has joined #openstack-meeting | 14:55 | |
*** cheng1__ has joined #openstack-meeting | 15:00 | |
*** boxiang has quit IRC | 15:03 | |
*** lennyb has quit IRC | 15:07 | |
*** lennyb has joined #openstack-meeting | 15:07 | |
*** eharney has joined #openstack-meeting | 15:07 | |
*** diablo_rojo has joined #openstack-meeting | 15:16 | |
*** panda|ruck is now known as panda | 15:19 | |
*** woojay has joined #openstack-meeting | 15:19 | |
*** cheng1__ has quit IRC | 15:20 | |
*** cheng1__ has joined #openstack-meeting | 15:21 | |
*** rcernin has quit IRC | 15:26 | |
*** liuyulong has quit IRC | 15:26 | |
*** gyee has joined #openstack-meeting | 15:27 | |
*** aarents has joined #openstack-meeting | 15:29 | |
*** cheng1__ has quit IRC | 15:31 | |
*** cheng1__ has joined #openstack-meeting | 15:32 | |
*** ttsiouts has quit IRC | 15:32 | |
*** ttsiouts has joined #openstack-meeting | 15:33 | |
*** enriquetaso has quit IRC | 15:35 | |
*** enriquetaso has joined #openstack-meeting | 15:35 | |
*** tssurya has quit IRC | 15:36 | |
*** ttsiouts has quit IRC | 15:38 | |
*** kopecmartin is now known as kopecmartin|off | 15:53 | |
*** rosmaita has joined #openstack-meeting | 15:54 | |
*** Qiming has quit IRC | 15:54 | |
*** cheng1__ has quit IRC | 15:55 | |
*** Lucas_Gray has quit IRC | 15:55 | |
*** davidsha has joined #openstack-meeting | 15:57 | |
*** _erlon_ has quit IRC | 15:57 | |
*** Qiming has joined #openstack-meeting | 15:58 | |
*** m5z_|mszwed| has joined #openstack-meeting | 15:58 | |
jungleboyj | #startmeeting Cinder | 16:00 |
openstack | Meeting started Wed Jun 5 16:00:26 2019 UTC and is due to finish in 60 minutes. The chair is jungleboyj. 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: Cinder)" | 16:00 | |
openstack | The meeting name has been set to 'cinder' | 16:00 |
whoami-rajat | Hi | 16:00 |
jungleboyj | courtesy ping: jungleboyj whoami-rajat rajinir lseki carloss pots woojay erlon geguileo eharney rosmaita enriquetaso e0ne smcginnis davidsha walshh_ xyang hemna _hemna eharney | 16:00 |
walshh_ | hi | 16:00 |
enriquetaso | o/ | 16:00 |
davidsha | hey | 16:00 |
e0ne | hi | 16:00 |
geguileo | hi! o/ | 16:00 |
m5z_|mszwed| | hi :) | 16:00 |
xyang | hi | 16:00 |
smcginnis | o/ | 16:01 |
jungleboyj | Agenda: https://etherpad.openstack.org/p/cinder-train-meetings | 16:01 |
rosmaita | o/ | 16:01 |
jungleboyj | @! | 16:01 |
_pewp_ | jungleboyj (;-_-)ノ | 16:01 |
hemna | @! | 16:01 |
_pewp_ | hemna (✧∇✧)╯ | 16:01 |
woojay | hi | 16:02 |
jungleboyj | @! | 16:02 |
_pewp_ | jungleboyj (*ï¾ŸÍ âˆ€ Í )ノ | 16:02 |
carloss | hi | 16:02 |
* jungleboyj misses _pewp_ in the cinder channel | 16:02 | |
lseki | o/ | 16:02 |
*** panda is now known as panda|off | 16:02 | |
jungleboyj | Ok. Lets get started. | 16:03 |
jungleboyj | #topic announcements | 16:03 |
*** openstack changes topic to "announcements (Meeting topic: Cinder)" | 16:03 | |
*** markvoelker has joined #openstack-meeting | 16:04 | |
jungleboyj | Just a friendly reminder that we have the Train Mid-Cycle planning going on. | 16:04 |
jungleboyj | #link https://etherpad.openstack.org/p/cinder-train-mid-cycle-planning | 16:04 |
rajinir | o/ | 16:04 |
jungleboyj | If you can make it please add your name. | 16:05 |
jungleboyj | Start planning ahead so we can have a good turnout. | 16:05 |
_pewp_ | hemna (/ .□.) ︵╰(゜Д゜)╯︵ /(.□. ) | 16:05 |
_pewp_ | hemna (/ .□.) ︵╰(゜Д゜)╯︵ /(.□. ) | 16:05 |
_pewp_ | hemna (/ .□.) ︵╰(゜Д゜)╯︵ /(.□. ) | 16:05 |
_pewp_ | hemna (/ .□.) ︵╰(゜Д゜)╯︵ /(.□. ) | 16:05 |
_pewp_ | hemna (/ .□.) ︵╰(゜Д゜)╯︵ /(.□. ) | 16:05 |
_pewp_ | ... | 16:05 |
_pewp_ | ... | 16:05 |
_pewp_ | ... | 16:05 |
hemna | shit | 16:05 |
hemna | wtf was that | 16:05 |
* jungleboyj is laughing | 16:05 | |
jungleboyj | _pewp_: Is mad at you | 16:05 |
hemna | evidently | 16:05 |
geguileo | lol | 16:05 |
jungleboyj | Anyone have other announcements? | 16:06 |
e0ne | jungleboyj: will you cut train-1 for cinder tomorrow? | 16:06 |
e0ne | AFAIK, it's not required anymore | 16:06 |
jungleboyj | e0ne: Good question. I thought that we didn't have to do that anymore. | 16:06 |
jungleboyj | smcginnis: ^^ | 16:07 |
rosmaita | pretty sure it is up to us | 16:07 |
e0ne | jungleboyj: it's up to the team | 16:07 |
smcginnis | The cycle-with-intermediary deliverables will be proposed, but no need to do beta releases of the services anymore. | 16:07 |
smcginnis | Only reason to do a x.x.x.0b1 release is if you actually know someone downstream wants to pick it up and do something with it. | 16:08 |
jungleboyj | smcginnis: Ok, that is what I thought. | 16:08 |
jungleboyj | eharney: geguileo Anything you guys need a beta for? | 16:08 |
geguileo | jungleboyj: I don't think so... | 16:09 |
* jungleboyj hears crickets | 16:09 | |
geguileo | eharney: ^ | 16:09 |
jungleboyj | Ok. Good. So, I would say we just keep rolling forward. | 16:09 |
smcginnis | Based on what we saw, those usually were not being used. | 16:09 |
jungleboyj | We also don't have any deadlines for T-1 . | 16:09 |
jungleboyj | Though, now we need to make sure we are helping get people to T-2. | 16:10 |
jungleboyj | Doing driver reviews, reviewing spes. | 16:10 |
jungleboyj | *specs | 16:10 |
smcginnis | Gotta get those drivers reviewed. | 16:10 |
jungleboyj | smcginnis: ++ | 16:11 |
jungleboyj | So, a todo for the whole team is to please work on reviewing drivers and specs. | 16:12 |
jungleboyj | :-) | 16:13 |
* jungleboyj is included | 16:13 | |
eharney | i don't think we have any need for it | 16:13 |
*** mattw4 has joined #openstack-meeting | 16:13 | |
jungleboyj | Ok. I think we can move on. | 16:13 |
jungleboyj | #topic Driver Unsupported Patches | 16:14 |
*** openstack changes topic to "Driver Unsupported Patches (Meeting topic: Cinder)" | 16:14 | |
jungleboyj | I have a list in the agenda of the drivers I have unsupported. | 16:14 |
hemna | is there a review topic for those? | 16:15 |
jungleboyj | Appreciate help getting those merged. | 16:15 |
jungleboyj | They all start with 'unsupport' | 16:15 |
jungleboyj | Guess I should have made that more general. | 16:16 |
jungleboyj | :-( | 16:16 |
jungleboyj | I could set them to a review topic. | 16:17 |
hemna | maybe change the topic on all of them, to the same? | 16:17 |
smcginnis | jungleboyj: I think I had always used "ci-unsupported" to make it easy to find all of them. | 16:17 |
jungleboyj | Ok. I will do that. | 16:17 |
rajinir | Is there a link that can list them? | 16:19 |
jungleboyj | I am also going to try to work on getting driver removal patches up yet this week so that is all taken care of. | 16:19 |
jungleboyj | rajinir: They are in the agenda right now: https://etherpad.openstack.org/p/cinder-train-meetings | 16:19 |
smcginnis | rajinir: If they all have the same topic, then it's easy to list the gerrit query to list them all | 16:19 |
jungleboyj | Or you can just click on the topic and get a list. | 16:19 |
smcginnis | Similar to what I set for the new drivers: https://review.opendev.org/#/q/topic:train-drivers | 16:19 |
rajinir | ++ | 16:20 |
smcginnis | jungleboyj: Had the ci_unsupported wrong (-/_): https://review.opendev.org/#/q/topic:ci_unsupported | 16:21 |
jungleboyj | Ah, you do that for removal too. Ok. Good. | 16:21 |
* jungleboyj thinks that is something to add to our documentation. :-) | 16:22 | |
rajinir | smcginnis: thanks | 16:22 |
jungleboyj | So, I will keep all the patches under that topic. | 16:23 |
jungleboyj | So, I think that is all I have there. | 16:24 |
jungleboyj | #topic Update on Ceph iSCSI driver | 16:24 |
*** openstack changes topic to "Update on Ceph iSCSI driver (Meeting topic: Cinder)" | 16:24 | |
hemna | ok I guess I'm up | 16:24 |
hemna | so I've been doing some research on an iscsi ceph driver | 16:25 |
jungleboyj | hemna: If you don't mind. | 16:25 |
hemna | I have an etherpad here: https://etherpad.openstack.org/p/cinder-ceph-iscsi-research | 16:25 |
hemna | and a WIP of the driver here: https://review.opendev.org/#/c/662829/ | 16:25 |
jungleboyj | Awesome. | 16:26 |
hemna | the driver assumes that it has access to the rbd-target-api from the http://github.com/ceph/ceph-iscsi project | 16:26 |
hemna | the rbd-target-api python REST flask server is meant to coordinate the iscsi gw configs between ceph iscsi gateways | 16:27 |
hemna | so it's not really meant to do what I'm using it for | 16:27 |
hemna | but it happens to work at this point | 16:27 |
hemna | I'm getting close to having the initialize_connection working | 16:27 |
hemna | I was able to get a single attach and detach work | 16:27 |
hemna | once | 16:27 |
hemna | but then discovered issues, which is leading to more work for both initialize_connection and terminate_connection | 16:27 |
*** lpetrut has quit IRC | 16:28 | |
hemna | there is zero documentation on how to properly use the rbd-target-api to do an export | 16:28 |
hemna | but I'm kinda figuring it out as a go from a standalone script using my ceph_iscsi_client.py REST client | 16:28 |
smcginnis | Any conversations in the ceph community to just get some assurance that this is an acceptable use of it? | 16:28 |
hemna | nah not yet | 16:29 |
hemna | my hope is to verify that this works | 16:29 |
hemna | then the thought was to create a separate client pypi project | 16:29 |
hemna | that is the REST client that can talk to the rbd-target-api | 16:29 |
hemna | which is my ceph_iscsi_client.py | 16:30 |
* jungleboyj is thinking it is good that you are the one working on this. | 16:30 | |
hemna | the rbd-iscsi.py driver is a derivation of the existing rbd.py cinder driver | 16:30 |
hemna | so I got most of the functionality for free so far | 16:30 |
hemna | other than attach/detach | 16:30 |
jungleboyj | hemna: Awesome. I was hoping that that would be the case. | 16:31 |
hemna | but I've done zero testing with it other than create a few volumes and work on attach/detach | 16:31 |
hemna | this is a research project still at this point | 16:31 |
jungleboyj | Understood. | 16:31 |
hemna | with the hopes that it can get stabilized and then work on cleaning it up and making it a viable driver | 16:31 |
geguileo | great progress!! | 16:32 |
jungleboyj | ++ | 16:32 |
hemna | there is a lot of setup on the ceph cluster side to make sure the iscsi gateway works properly | 16:32 |
hemna | so I'm not sure how much effort it'd take to do the CI side of things | 16:32 |
hemna | if someone is familiar with the existing ceph CI, I could help them on the iscsi gw setup | 16:32 |
hemna | for CI | 16:32 |
jungleboyj | We have automation in Lenovo that I think does some of that. | 16:33 |
jungleboyj | I wonder if we can help with that. | 16:33 |
hemna | I had to manually update my 7 ubuntu VMs to linux kernel 4.18 | 16:33 |
smcginnis | That's going to be a big issue. | 16:33 |
jungleboyj | :-( | 16:33 |
hemna | 4.15 wasn't happy | 16:33 |
*** panda|off has quit IRC | 16:33 | |
hemna | luckily it's an apt-get install | 16:34 |
hemna | instead of a compile | 16:34 |
hemna | so I'm hoping in the next day or so, to stabilize initialize_connection | 16:34 |
hemna | it's still giving me fits | 16:34 |
*** panda has joined #openstack-meeting | 16:35 | |
hemna | the rbd-target-api is a bit compilicated in what it needs done at certain times. | 16:35 |
hemna | anyone wants to help with the CI side of things I'd appreciate it | 16:35 |
hemna | but at least the driver is possible at this point still. so I'm hopeful | 16:36 |
jungleboyj | hemna: Ok. Let me see if there is anything we have from the iSCSI work we did previously in Lenovo. | 16:36 |
jungleboyj | Will get back to you. | 16:36 |
jungleboyj | hemna: Hopeful is good! | 16:36 |
hemna | I'll keep updating the driver review with code as I go along | 16:37 |
jungleboyj | hemna: Anything else? | 16:37 |
hemna | that's it. | 16:37 |
jungleboyj | Cool. Thank you for the update. | 16:37 |
eharney | i assume the CI work would involve adding a new mode to devstack-plugin-ceph? | 16:37 |
geguileo | hemna: thanks for the update and the work! | 16:37 |
jungleboyj | geguileo: ++ | 16:38 |
hemna | eharney: yah I'm assuming so | 16:38 |
hemna | installing all the required ceph-iscsi packages | 16:38 |
hemna | and setting up the rbd-target-gw | 16:38 |
hemna | and installing the rbd-target-api | 16:38 |
hemna | I documented as much as I could in the etherpad | 16:39 |
*** panda has quit IRC | 16:39 | |
hemna | geguileo: np. I'd really love to get this working and in cinder. | 16:40 |
jungleboyj | hemna: ++ | 16:40 |
jungleboyj | Ok. That was all we had for topics this week. | 16:40 |
jungleboyj | #topic Open Discussion | 16:40 |
*** openstack changes topic to "Open Discussion (Meeting topic: Cinder)" | 16:40 | |
whoami-rajat | I've something that was brought up yesterday | 16:40 |
eharney | i'd love to get lvm multiattach fixed in stable: https://review.opendev.org/#/q/Icabc4a67d3f5462fe24e4027e84e56a001e1b2b8 | 16:41 |
hemna | eharney: ++ | 16:42 |
whoami-rajat | tempest is capping its api-extensions in devstack [1] that is blocked by cinder as we "mistakely" removed an extension in a MV bump which wasn't backward compatible. i've a patch up for it, will appreciate some reviews on it. https://review.opendev.org/#/c/663049/ | 16:42 |
whoami-rajat | [1] https://review.opendev.org/#/q/topic:cap-extensions+(status:open+OR+status:merged) | 16:42 |
jungleboyj | eharney: Ok, will watch those and get them through. | 16:43 |
smcginnis | geguileo: Do we still need to sort out this whole mess? https://review.opendev.org/574681 | 16:43 |
eharney | i looked at the os-sch-hnt change and was fairly unclear on the details involved there | 16:44 |
*** bnemec has quit IRC | 16:44 | |
geguileo | smcginnis: not sure... | 16:44 |
smcginnis | eharney: Which part? | 16:44 |
eharney | smcginnis: i think e0ne was going to follow up on syncing scheduler stats from the ptg, which i think is the same area that spec is about | 16:45 |
geguileo | smcginnis: I mean, the issue is still there, that's for sure | 16:45 |
smcginnis | Oh right, forgot about that from the PTG. | 16:45 |
jungleboyj | eharney: ++ | 16:45 |
*** haleyb has quit IRC | 16:46 | |
smcginnis | Wasn't sure if that spec should be abandoned or not. Sounds like it should be. | 16:46 |
whoami-rajat | eharney: i replied to your comment there, hope it helps. | 16:46 |
geguileo | smcginnis: probably a good idea to abandon it for now... | 16:46 |
e0ne | I need to read Tommy's spec | 16:46 |
smcginnis | e0ne: I think he had three different ones out there at one point trying to get opinions on different approaches. | 16:47 |
*** panda has joined #openstack-meeting | 16:48 | |
jungleboyj | :-) That is one way to do it. | 16:48 |
jungleboyj | Other topics for today? | 16:50 |
jungleboyj | Doesn't sound like it ... | 16:51 |
jungleboyj | Ok. So lets wrap this up. | 16:52 |
jungleboyj | Thanks everyone for joining and for continuing to work on Cinder. | 16:52 |
smcginnis | Thanks! | 16:52 |
jungleboyj | #endmeeting | 16:52 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 16:52 | |
openstack | Meeting ended Wed Jun 5 16:52:54 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:52 |
*** woojay has left #openstack-meeting | 16:52 | |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-06-05-16.00.html | 16:52 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-06-05-16.00.txt | 16:52 |
openstack | Log: http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-06-05-16.00.log.html | 16:53 |
*** dviroel has left #openstack-meeting | 16:53 | |
geguileo | thanks! | 16:53 |
m5z_|mszwed| | bye :) | 16:53 |
*** e0ne has quit IRC | 16:53 | |
*** ekcs has joined #openstack-meeting | 16:55 | |
*** m5z_|mszwed| has left #openstack-meeting | 16:55 | |
*** davidsha has quit IRC | 17:00 | |
*** rosmaita has left #openstack-meeting | 17:03 | |
*** hberaud is now known as hberaud|gone | 17:18 | |
*** iyamahat has joined #openstack-meeting | 17:27 | |
*** ralonsoh has quit IRC | 17:28 | |
*** _hemna has joined #openstack-meeting | 17:31 | |
*** ociuhandu has joined #openstack-meeting | 17:33 | |
*** iyamahat has quit IRC | 17:34 | |
*** ociuhandu_ has quit IRC | 17:36 | |
*** haleyb has joined #openstack-meeting | 17:37 | |
*** ociuhandu has quit IRC | 17:39 | |
*** akhil_jain has quit IRC | 17:40 | |
*** yamahata has joined #openstack-meeting | 17:45 | |
*** yamamoto has joined #openstack-meeting | 17:48 | |
*** iyamahat has joined #openstack-meeting | 17:51 | |
*** yamamoto has quit IRC | 17:53 | |
*** tesseract has quit IRC | 17:57 | |
*** _hemna has quit IRC | 18:02 | |
*** ankita-2798 has joined #openstack-meeting | 18:08 | |
*** enriquetaso has quit IRC | 18:17 | |
*** enriquetaso has joined #openstack-meeting | 18:17 | |
*** thgcorrea has quit IRC | 18:19 | |
*** e0ne has joined #openstack-meeting | 18:20 | |
*** ricolin has quit IRC | 18:41 | |
*** tidwellr has quit IRC | 18:54 | |
*** ociuhandu has joined #openstack-meeting | 19:02 | |
SotK | anyone around for the storyboard meeting? | 19:02 |
SotK | #startmeeting storyboard | 19:03 |
openstack | Meeting started Wed Jun 5 19:03:05 2019 UTC and is due to finish in 60 minutes. The chair is SotK. Information about MeetBot at http://wiki.debian.org/MeetBot. | 19:03 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 19:03 |
*** openstack changes topic to " (Meeting topic: storyboard)" | 19:03 | |
openstack | The meeting name has been set to 'storyboard' | 19:03 |
SotK | #link https://wiki.openstack.org/wiki/Meetings/StoryBoard#Agenda_for_next_meeting Agenda | 19:03 |
diablo_rojo | o/ | 19:03 |
SotK | #topic Migration Updates | 19:03 |
*** openstack changes topic to "Migration Updates (Meeting topic: storyboard)" | 19:03 | |
SotK | I don't think there's been anything new this week right? | 19:04 |
diablo_rojo | No negative feedback.. or any feedback for that matter from Swift | 19:04 |
diablo_rojo | Nothing new | 19:04 |
SotK | I guess we just give them a bit more time for now? | 19:04 |
fungi | yeah, wouldn't rush it | 19:04 |
notmyname | the swift team meeting is today. it should be raised there for people to offer comments | 19:05 |
notmyname | (in about 3 hours) | 19:05 |
notmyname | sorry, in 2 hours | 19:05 |
fungi | getting feedback isn't time-sensitive, they should take all the time they need to try stuff out | 19:06 |
SotK | +1 | 19:06 |
*** priteau has quit IRC | 19:06 | |
diablo_rojo | Yeah I agree | 19:06 |
diablo_rojo | Definitely not rushing | 19:07 |
diablo_rojo | More just noting that there isnt any yet. | 19:07 |
*** priteau has joined #openstack-meeting | 19:08 | |
SotK | #topic Release Progress | 19:08 |
*** openstack changes topic to "Release Progress (Meeting topic: storyboard)" | 19:08 | |
SotK | so I think we decided on most of the things we needed to after the meeting last week | 19:09 |
diablo_rojo | What are the next steps? | 19:09 |
fungi | well, a recap of that decision would help too | 19:09 |
diablo_rojo | Oh yeah | 19:09 |
*** ociuhandu has quit IRC | 19:09 | |
diablo_rojo | for logging purposes | 19:09 |
fungi | i mean, it's in the #storyboard channel logs, but for posterity having it mentioned in the meeting would be great | 19:10 |
SotK | :) | 19:10 |
diablo_rojo | SO I think we decided on storyboard-api for pypi? | 19:10 |
fungi | that matches my recollection | 19:10 |
SotK | #info we'll rename the python package to storyboard-api | 19:10 |
fungi | which i think just needs a minor update to the existing patch? | 19:10 |
SotK | yeah | 19:10 |
SotK | #info we'll number the first release 1.0.0 | 19:11 |
fungi | i can do that unless someone has already started | 19:11 |
diablo_rojo | And someday...might rename the storyboard repo to storyboard-api | 19:11 |
diablo_rojo | fungi, go for it :) | 19:11 |
diablo_rojo | I haven't touched it. | 19:11 |
SotK | me neither | 19:11 |
fungi | i'll check with tonyb first to see if he wants to | 19:12 |
fungi | since it is his patch | 19:12 |
fungi | i'll leave a review comment real quick at least | 19:12 |
SotK | thanks | 19:12 |
SotK | we didn't firmly decide on when to do a release | 19:12 |
SotK | but I think we should just do it when we've finished planning what we need to do to do a release | 19:12 |
fungi | there was something you wanted merged first... the attachments implementation? security teams? | 19:13 |
fungi | or we could make those 1.1.0 et cetera | 19:13 |
fungi | and just release as soon as the dist name is updated | 19:13 |
SotK | yeah I mentioned attachments, but I ended up preferring the idea of "here's 1.1.0, now with attachments!" | 19:13 |
diablo_rojo | Yeah I think we decided early and often? | 19:14 |
fungi | basically the process (once we're using an available dist name) is to make a 1.0.0 signed tag and push it to gerrit | 19:14 |
fungi | oh, we needed to add jobs ;) | 19:14 |
fungi | i'll check into what jobs we're missing for release automation | 19:15 |
SotK | nice, thanks | 19:15 |
fungi | with the correct jobs added we'll upload an sdist and a wheel to pypi automatically each time a new tag is pushed to gerrit | 19:15 |
SotK | I think that adding jobs is the only other thing we need to do then | 19:16 |
fungi | yep, i concur | 19:17 |
diablo_rojo | Sounds pretty easy | 19:17 |
SotK | on a related note, what about webclient releases? | 19:17 |
fungi | i may also push a manual build to test.pypi.org just to make sure the package metadata isn't going to be rejected by warehouse | 19:17 |
SotK | that sounds like a good idea | 19:18 |
fungi | storyboard-webclient will need different sorts of jobs, presumably | 19:18 |
fungi | i know less about javascript, but i believe we do have some js-based projects doing automatic releases to npm, if that's where it makes sense | 19:19 |
SotK | yep, we'll want jobs to upload to npm I expect | 19:19 |
*** panda has quit IRC | 19:19 | |
SotK | I'm not totally sure if that makes sense, but will look into being more sure | 19:19 |
fungi | i can probably work out what those are using to accomplish that, but less sure how to safely test that it'll work ahead of time and not sure what sorts of package registration we need to do | 19:19 |
fungi | mordred might have ideas there too | 19:20 |
SotK | also, do we want to keep version numbers in sync and release them simultaneously? | 19:20 |
diablo_rojo | Do we want to to outline some actions for logging's sake? | 19:20 |
SotK | my initial feeling is "not really" | 19:20 |
*** panda has joined #openstack-meeting | 19:20 | |
fungi | i would not try to sync releases | 19:20 |
diablo_rojo | I would agree with the not really | 19:20 |
fungi | release them whenever makes sense for each project | 19:21 |
diablo_rojo | I feel like there will be more stuff in the api we want to/need to release than in the webclient | 19:21 |
SotK | #action SotK to decide if npm makes sense as a place to release the webclient, and what it entails | 19:21 |
fungi | and if the demo docker image is something we think is useful, i believe we have jobs which could build that and publish to dockerhub too | 19:21 |
SotK | #action fungi to investigate what jobs we are missing for api releases | 19:22 |
diablo_rojo | That would be cool. | 19:23 |
*** lpetrut has joined #openstack-meeting | 19:23 | |
diablo_rojo | (the docker image) | 19:23 |
diablo_rojo | Though I dont think its a priority | 19:23 |
SotK | +1, but I'm not sure it actually exists yet | 19:23 |
SotK | it would definitely be useful, but we can probably wait for an updated version of https://review.opendev.org/#/c/611191/ | 19:24 |
SotK | #topic Forum + PTG Summary | 19:25 |
*** openstack changes topic to "Forum + PTG Summary (Meeting topic: storyboard)" | 19:25 | |
SotK | #link http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006214.html Summary email | 19:26 |
diablo_rojo | So did all the stories we have on the etherpad get added? | 19:27 |
diablo_rojo | I know you were working on that Friday | 19:27 |
diablo_rojo | I didnt have time to circle back | 19:27 |
SotK | #link https://etherpad.openstack.org/p/sb-train-ptg PTG Etherpad | 19:27 |
*** lpetrut has quit IRC | 19:27 | |
diablo_rojo | Yeah that etherpad :) | 19:27 |
SotK | I think there are still a couple of story-less things | 19:27 |
SotK | we should do as the agenda suggests and go through tagging things and creating the last couple of stories | 19:28 |
SotK | at some point | 19:28 |
SotK | the missing ones are "Integration tests", "Search is slow", and "Archive tasks/stories" | 19:29 |
diablo_rojo | SotK, I feel like we should schedule a meeting.. | 19:30 |
diablo_rojo | Heh | 19:31 |
SotK | heh, that's probably a good idea | 19:31 |
diablo_rojo | Whats the rest of your week look like? | 19:31 |
diablo_rojo | My Friday is very open. | 19:31 |
diablo_rojo | Anywhere from like.. 15:00 UTC onward | 19:32 |
SotK | anything after 16:00 UTC works for me tomorrow or Friday | 19:32 |
diablo_rojo | Lets do like.. 17 UTC on Friday | 19:33 |
diablo_rojo | we can use my zoom | 19:33 |
SotK | wfm | 19:33 |
diablo_rojo | https://zoom.us/j/8341652381 | 19:34 |
diablo_rojo | for those interested in participating | 19:34 |
diablo_rojo | I'm sure it will be thrilling | 19:34 |
ankita-2798 | diablo_rojo, what is the agenda for the meeting? | 19:35 |
diablo_rojo | ankita-2798, https://wiki.openstack.org/wiki/Meetings/StoryBoard#Agenda_for_next_meeting | 19:37 |
diablo_rojo | Or for Friday? | 19:37 |
diablo_rojo | Which meeting? lol | 19:37 |
diablo_rojo | the wiki link is for the meeting now | 19:38 |
diablo_rojo | SotK, do I need to make an invite? | 19:38 |
ankita-2798 | the one you are planning for Friday | 19:38 |
diablo_rojo | Or you just want to write it down | 19:38 |
SotK | if you like, I've added it to my calendar already though :) | 19:38 |
diablo_rojo | ankita-2798, its just to finish a triage of the active stories in the storyboard project group that we started at the Project Team Gathering a few weeks ago | 19:39 |
diablo_rojo | SotK, if you dont need one I wont ;) | 19:39 |
ankita-2798 | Oh, okay | 19:39 |
SotK | anything else on this? | 19:40 |
ankita-2798 | No, thank you :) | 19:41 |
diablo_rojo | None from me | 19:42 |
SotK | #topic In Progress Work | 19:42 |
*** openstack changes topic to "In Progress Work (Meeting topic: storyboard)" | 19:42 | |
diablo_rojo | Did we ever get mkarray's work merged? | 19:42 |
* SotK reviewed it and left some comments | 19:43 | |
SotK | mostly just some things that I'd like to neaten up before we merge them | 19:43 |
diablo_rojo | SotK, not sure he is around much anymore. | 19:44 |
diablo_rojo | I can take a look and update based on your comments and then you can merge it? | 19:44 |
SotK | me neither, I noted in the reviews that I can make the fixes if he doesn't have time, and was planning to do so if I didn't hear anything | 19:44 |
SotK | but feel free to beat me to it :) | 19:44 |
fungi | or can always add a followup change with the suggested improvements and approve them both at the same time if that's more palatable | 19:44 |
SotK | either works for me, there was nothing too problematic in them | 19:45 |
*** slaweq has quit IRC | 19:47 | |
SotK | diablo_rojo: do you have a preference? | 19:47 |
*** slaweq has joined #openstack-meeting | 19:47 | |
*** artom has quit IRC | 19:48 | |
diablo_rojo | I'll just go make the changes and ping you when I have the patchset up | 19:48 |
SotK | ok, sounds good | 19:48 |
SotK | also, thanks for reviewing the security teams stuff :) | 19:48 |
fungi | i'm almost through the api side of that stack as well | 19:48 |
fungi | should hopefully see it merged by the end of the day | 19:49 |
SotK | excellent, thanks | 19:49 |
SotK | the issues that diablo_rojo noted on the webclient side of that should go away once the api side is deployed on storyboard-dev too I think | 19:50 |
fungi | awesome, and yeah that's why i started on the api stack | 19:50 |
diablo_rojo | YAY! | 19:50 |
SotK | I'll try to continue getting through my review/rework backlog | 19:50 |
diablo_rojo | So excited :) | 19:51 |
SotK | it would also be spectacular to merge https://review.opendev.org/#/c/643323/ | 19:51 |
SotK | I think that should help reduce the complexity of that 3 minute long query | 19:52 |
fungi | yes indeed | 19:52 |
fungi | thanks for the reminder | 19:52 |
SotK | same goes for https://review.opendev.org/#/c/643303/ too, but that query is a bit less bad to start with | 19:53 |
SotK | in fact, that isn't much better | 19:53 |
SotK | but its a bit better at least | 19:53 |
* diablo_rojo opens tabs | 19:54 | |
diablo_rojo | (5 min left) | 19:54 |
SotK | I think that's everything I have to mention for in progress work | 19:55 |
SotK | anyone else? | 19:55 |
fungi | ankita-2798 likely will want to track 643323 and 643303 since that may alter some of the queries in the slow query log data she asked about in #storyboard earlier | 19:56 |
diablo_rojo | Good point | 19:56 |
fungi | we can also grab a fresh log after those are in place and see if they made a difference | 19:56 |
ankita-2798 | Regarding the Search Improvement, I have been currently going through the storyboard's backend's codebase, learning the frameworks etc. I am yet to study the logs provided by corvus. | 19:57 |
ankita-2798 | fungi, yeah I already took a note of these reviews :) | 19:57 |
fungi | awesome! | 19:58 |
*** brault has quit IRC | 19:58 | |
*** _hemna has joined #openstack-meeting | 19:59 | |
*** jamesmcarthur has quit IRC | 19:59 | |
SotK | and with that we're out of time, thanks for coming folks! | 20:00 |
SotK | #endmeeting | 20:00 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 20:00 | |
openstack | Meeting ended Wed Jun 5 20:00:08 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 20:00 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/storyboard/2019/storyboard.2019-06-05-19.03.html | 20:00 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/storyboard/2019/storyboard.2019-06-05-19.03.txt | 20:00 |
openstack | Log: http://eavesdrop.openstack.org/meetings/storyboard/2019/storyboard.2019-06-05-19.03.log.html | 20:00 |
fungi | thanks SotK! | 20:00 |
diablo_rojo | Thanks SotK! | 20:01 |
ankita-2798 | Thank you! | 20:08 |
*** ankita-2798 has quit IRC | 20:13 | |
*** radeks_ has quit IRC | 20:29 | |
*** _hemna has quit IRC | 20:33 | |
*** pcaruana has quit IRC | 20:59 | |
*** tdasilva has joined #openstack-meeting | 21:00 | |
timburke_ | #startmeeting swift | 21:01 |
openstack | Meeting started Wed Jun 5 21:01:49 2019 UTC and is due to finish in 60 minutes. The chair is timburke_. Information about MeetBot at http://wiki.debian.org/MeetBot. | 21:01 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 21:01 |
*** openstack changes topic to " (Meeting topic: swift)" | 21:01 | |
openstack | The meeting name has been set to 'swift' | 21:01 |
timburke_ | who's here for the swift meeting? | 21:02 |
kota_ | hello | 21:02 |
notmyname | o/ | 21:02 |
tdasilva | hi | 21:02 |
mattoliverau | o/ | 21:02 |
rledisez | o/ | 21:02 |
*** _hemna has joined #openstack-meeting | 21:03 | |
*** brault has joined #openstack-meeting | 21:03 | |
clayg | o/ | 21:03 |
timburke_ | i forgot the update the agenda to reflect the actual state of what we need to discuss, but the broad topics are right | 21:03 |
timburke_ | #agenda https://wiki.openstack.org/wiki/Meetings/Swift | 21:04 |
timburke_ | #topic migration to story board | 21:04 |
*** openstack changes topic to "migration to story board (Meeting topic: swift)" | 21:04 | |
timburke_ | who's had a chance to play around in the storyboard sandbox? | 21:04 |
timburke_ | #link https://storyboard-dev.openstack.org/#!/project/openstack/swift | 21:04 |
mattoliverau | Opps, I was meaning to play with the sandbox.. but didn't. | 21:04 |
* diablo_rojo lurks | 21:05 | |
mattoliverau | Opps did I just say that out loud :p | 21:05 |
timburke_ | diablo_rojo, well, i've got some feedback :-) | 21:06 |
timburke_ | responsiveness is a bit of a problem. 10-12s to load a story and 14-15s to load the first 10 active stories for a project? launchpad has its own issues, but i don't recall it being *this* bad | 21:06 |
timburke_ | being able to have **bold**, *italics*, and `code` is nice. i can especially see the ability to have code blocks being good for tracebacks and curl output, for instance | 21:07 |
diablo_rojo | timburke_, we set up a slow log query and are starting to look over it to make improvements on loading times | 21:07 |
timburke_ | (iirc, launchpad would lose all the indents for tracebacks) | 21:07 |
diablo_rojo | and by 'we' I mean corvus :) Thanks corvus :) | 21:07 |
timburke_ | applying styling to migrated stories is an interesting choice -- i maybe would've put everything in code blocks to preserve the monospaced formatting that launchpad does (again, thinking about tracebacks and sample output), but i could see arguments either way | 21:07 |
timburke_ | being able to get to a project's resolved stories quickly is good. finding a related (but closed) issue is definitely one of the more annoying things about launchpad IMO | 21:08 |
*** patchbot has joined #openstack-meeting | 21:08 | |
*** brault has quit IRC | 21:08 | |
timburke_ | search field could use some help text; what operators do i get? how do i combine them? as a result, finding all stories that i'm subscribed to (for example) is not obvious | 21:08 |
timburke_ | on the stories search, it's not clear what projects are in play for a given story; i have to click through to the story, which is worsened by the responsiveness problems | 21:08 |
timburke_ | would be nice if i could specify a default set of filters when i go to the story list; "all open stories, across all projects, sorted by most-recently updated" is unlikely to be right for anyone | 21:08 |
timburke_ | sorry, that was a bunch all at once :-) | 21:08 |
diablo_rojo | timburke_, you can set up an automatic worklist with those default filter criteria | 21:09 |
diablo_rojo | timburke_, happy to have feedback :) | 21:09 |
timburke_ | cool! i hadn't gotten around to messing with worklists -- i just knew that i wanted to go looking for some stories, so i clicked on "stories" :-) | 21:09 |
diablo_rojo | If its a common set of criteria you will go back to repeatedly I would make a worklist | 21:10 |
diablo_rojo | an automatic one | 21:10 |
*** priteau has quit IRC | 21:10 | |
timburke_ | for me, the two biggest things would be "open stories for these projects" and "stories i'm subscribed to" | 21:11 |
tdasilva | is a worklist a global/public list or owned/visible by user? | 21:12 |
timburke_ | with the latter maybe getting split into "in this set of projects that i have a lot of interest in" and "outside of that set" | 21:12 |
diablo_rojo | they are public but they are owned by the person that creates them. Other can subscribe to them but I think you need to add people to them if they are going to make changes to the worklist. | 21:12 |
diablo_rojo | If there are private things in the worklist, sb is smart and wont show the user if they dont have the correct permissions | 21:13 |
timburke_ | "stories/tasks assigned to me" might also be useful, but i feel like at that point i'm more likely to be thinking in terms of reviews and looking to gerrit instead | 21:13 |
diablo_rojo | timburke_, you should be able to see that on your dashboard | 21:13 |
timburke_ | makes sense | 21:14 |
mattoliverau | Interestingly we might be able to have worlists for things like py3 migration and maybe priority reviews. | 21:14 |
diablo_rojo | stories and tasks you created as well | 21:14 |
diablo_rojo | mattoliverau, yep :) and you could put that all in a board if you wanted or have them exist separately | 21:14 |
diablo_rojo | Depends on how you want to view the info | 21:14 |
diablo_rojo | and organize yourselves | 21:15 |
timburke_ | py3 seems like it'd be its own story, with a (likely large) number of tasks to do the porting and testing | 21:15 |
timburke_ | i think? | 21:15 |
timburke_ | *shrug* | 21:15 |
diablo_rojo | Could be done either way. | 21:15 |
diablo_rojo | Depends on how granular you want to get I suppose. | 21:16 |
*** dmsimard has quit IRC | 21:16 | |
*** dmsimard8 has joined #openstack-meeting | 21:16 | |
*** dmsimard8 is now known as dmsimard | 21:16 | |
diablo_rojo | Looking at your wiki of priority reviews.. I might lean towards a worklist | 21:16 |
timburke_ | are there guidelines on what makes sense as a story vs as a task? or is the expectation that teams will figure out what works for them? | 21:16 |
diablo_rojo | and then have a story for each of the py3fun tests, a story for middleware, and a story bor 'obj' | 21:17 |
diablo_rojo | and then the tasks would be the patches under each of those larger topics | 21:17 |
diablo_rojo | Make sense? | 21:17 |
timburke_ | i think so | 21:17 |
diablo_rojo | A task is the actual change in the repo. A story is the more general thing to get done | 21:18 |
diablo_rojo | So like.. if I had a new feature I would make a story for it and the tasks would be like.. a task for the cli update and another for the api change | 21:18 |
diablo_rojo | And if you did docs or tests as separate patches you could have a task for each of those too. | 21:18 |
diablo_rojo | If you wanted to do a release right after that you could also make a task associated with the releases repo in that story | 21:19 |
diablo_rojo | so that its all together in one place | 21:19 |
timburke_ | cool | 21:20 |
diablo_rojo | Any other questions atm? :) | 21:20 |
timburke_ | did anyone else have comments of questions for diablo_rojo? | 21:20 |
diablo_rojo | If you think of them later come bother us in #storyboard :) | 21:20 |
timburke_ | cool, thanks diablo_rojo! | 21:21 |
timburke_ | #topic libec | 21:21 |
*** openstack changes topic to "libec (Meeting topic: swift)" | 21:21 | |
timburke_ | it's under openstack/ again! | 21:21 |
mattoliverau | nice | 21:21 |
kota_ | nice! | 21:21 |
timburke_ | new release synced over to https://github.com/openstack/liberasurecode/releases just fine | 21:22 |
tdasilva | sweeeeet! | 21:22 |
timburke_ | i might poke at https://github.com/alpinelinux/aports/blob/master/testing/liberasurecode/APKBUILD to pick it up | 21:22 |
timburke_ | in light of the impending https://review.opendev.org/#/c/662615/ | 21:23 |
patchbot | patch 662615 - swift - Installing liberasurecode from Alpine Linux repos ... - 3 patch sets | 21:23 |
timburke_ | we still owe the quadiron guys some reviews :-/ | 21:23 |
timburke_ | and i still need to follow up with the libphazr guys about whether they'd get broken by some of the proposed changes, and how we'd know without a gate job | 21:24 |
timburke_ | but... that'll probably be later, because we've got other priorities! | 21:25 |
timburke_ | #topic py3 | 21:25 |
*** openstack changes topic to "py3 (Meeting topic: swift)" | 21:25 | |
timburke_ | i got some good comments on the ssync patch; pushed up a new patchset this morning | 21:26 |
timburke_ | https://review.opendev.org/#/c/660542/ | 21:26 |
patchbot | patch 660542 - swift - py3: port ssync - 5 patch sets | 21:26 |
timburke_ | got the memcache fixup at https://review.opendev.org/#/c/662115/ | 21:26 |
patchbot | patch 662115 - swift - Fix up how we memcache on py3 - 2 patch sets | 21:26 |
timburke_ | that's going to be needed for tempurl https://review.opendev.org/#/c/652928/ | 21:27 |
patchbot | patch 652928 - swift - py3: Port the tempurl middleware - 5 patch sets | 21:27 |
*** rcernin has joined #openstack-meeting | 21:27 | |
timburke_ | on top of *that*, i've started working on getting func tests running under py2 passing against services running under py3 | 21:27 |
timburke_ | nothing in terms of a gate job just yet, but so far things are really promising! | 21:28 |
kota_ | interesting | 21:29 |
timburke_ | there were two spots of trouble i hit: first was non-ascii header names | 21:29 |
timburke_ | which led to https://review.opendev.org/#/c/662546/ | 21:29 |
patchbot | patch 662546 - swift - py3: Stop truncating response headers - 1 patch set | 21:29 |
timburke_ | (see https://github.com/openstack/swift/blob/2.21.0/test/functional/test_container.py#L156-L163 for one of the tests that exercises that -- and note that it already has a `if tf.web_front_end == 'integral':` guard) | 21:30 |
timburke_ | the other is something i happened to hit because i was using an EC policy by default -- apparently there's some bad interaction between SegmentedIterable and ECAppIter that trips a `ValueError: generator already executing` when closing iters at the end of the response | 21:32 |
timburke_ | still not sure what's going on there, but it doesn't happen on py2 :-/ | 21:33 |
timburke_ | while trying to characterize that, i found https://bugs.launchpad.net/swift/+bug/1831790 | 21:34 |
openstack | Launchpad bug 1831790 in OpenStack Object Storage (swift) "Multi-range GET of DLO returns bad data" [Undecided,New] | 21:34 |
timburke_ | and proposed https://review.opendev.org/#/c/663403/ to fix it | 21:34 |
patchbot | patch 663403 - swift - dlo: Respond 200 on multi-range GETs - 1 patch set | 21:34 |
timburke_ | apparently we never really intended to be able to do multi-ranged gets on DLOs | 21:35 |
timburke_ | i think that's about all the progress i've got -- mattoliverau, zaitcev, anything to add? | 21:36 |
*** _hemna has quit IRC | 21:36 | |
mattoliverau | Nice summary, nothing to add for me. I'll go look at the memcache one to hopefully unblock tempurl | 21:37 |
*** enriquetaso has quit IRC | 21:38 | |
timburke_ | mattoliverau, anything else you'd like before landing https://review.opendev.org/#/c/662294/ ? | 21:38 |
patchbot | patch 662294 - swift - py3: symlink follow-up - 2 patch sets | 21:38 |
mattoliverau | nope, I'm happy with it. | 21:40 |
timburke_ | yay, more py3 func tests! | 21:40 |
timburke_ | #topic lots of small files | 21:41 |
*** openstack changes topic to "lots of small files (Meeting topic: swift)" | 21:41 | |
timburke_ | rledisez, kota_, how's it going? | 21:41 |
rledisez | no real moves from ovh side. last there were a holiday and alex is sick these days | 21:42 |
rledisez | *last week | 21:42 |
mattoliverau | timburke_: +A'ed | 21:42 |
timburke_ | thanks mattoliverau | 21:42 |
timburke_ | i saw kota_ proposed a merge from master, which is great. just approved | 21:43 |
kota_ | yup, | 21:44 |
kota_ | but not yet have time to look at alex's test improvement sorry | 21:45 |
*** gmann has joined #openstack-meeting | 21:45 | |
timburke_ | is there any particular order we should look at things on https://review.opendev.org/#/q/status:open+project:openstack/swift+branch:feature/losf ? | 21:45 |
kota_ | let me check | 21:46 |
timburke_ | i know there are some unit test patches that conflict; which should we try to land first? i might make sure they can run under py3 ;-) | 21:46 |
kota_ | i think, https://review.opendev.org/#/c/660381/ and https://review.opendev.org/#/c/659515/ are easy and able to be reviewed | 21:47 |
patchbot | patch 660381 - swift (feature/losf) - Add tests for vfile_utils - 1 patch set | 21:47 |
patchbot | patch 659515 - swift (feature/losf) - Add small unit tests for vfile and related modules - 2 patch sets | 21:47 |
timburke_ | cool! sounds good | 21:47 |
kota_ | Alex's improvement starts from https://review.opendev.org/#/c/659254/ ... not sure, but probably we need to know what exactly problem is | 21:48 |
patchbot | patch 659254 - swift (feature/losf) - In _get_vfile(), handle the case when a referenced... - 1 patch set | 21:48 |
kota_ | I'll try to catch up those. | 21:49 |
timburke_ | fwiw, notmyname got me excited about this over lunch yesterday -- reminded me that losf is giving us a model for how we can have more experimentation in the backend, and that getting https://review.opendev.org/#/c/427911/ really opens up the scope of what kinds of experiments would be possible | 21:50 |
patchbot | patch 427911 - swift - Replace MIME with PUT+POST for EC and Encryption - 37 patch sets | 21:50 |
notmyname | :-) | 21:51 |
timburke_ | after py3, i'm fairly certain these should be the priority | 21:52 |
*** slaweq has quit IRC | 21:52 | |
kota_ | thanks a lot | 21:52 |
timburke_ | #topic swift 2.22.0 release | 21:52 |
*** openstack changes topic to "swift 2.22.0 release (Meeting topic: swift)" | 21:52 | |
kota_ | i know py3 is the top priority. | 21:52 |
timburke_ | speaking of... i'd like to cut a release shortly after the py3 unit tests are ported | 21:53 |
timburke_ | i maybe would've liked to have func tests, too, but i think we can get ourselves confident enough for "experimental" py3 support by running func tests manually under py2 | 21:54 |
kota_ | sounds reasonable to me | 21:55 |
timburke_ | in light of that plan, what *else* should be getting in? anyone have patches they think would be good to land concurrent with the py3 work? | 21:55 |
mattoliverau | experimental py3 release would be exciting, and the distros would love to see that we've made that kind of porgress. | 21:55 |
timburke_ | (alternatively, does anyone feel that this is a terrible plan and premature; we need to get func tests *first*?) | 21:55 |
mattoliverau | Well I'd like func tests, but if we can somehow do the py2 func to a py3 then I'm happy with that. | 21:57 |
timburke_ | well, keep thinking about both what other patches we'd want for a release, and what we can do to feel more confident in the eventual (experimental) py3 support :-) | 21:58 |
timburke_ | the sooner we can get the experimental release out, the more confidence we can have when we have for the *next* release when we say we *really* support it | 21:59 |
timburke_ | we're about at time | 21:59 |
timburke_ | thank you all for coming, and thank you for working on swift! | 21:59 |
timburke_ | #endmeeting | 21:59 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 21:59 | |
openstack | Meeting ended Wed Jun 5 21:59:45 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 21:59 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-06-05-21.01.html | 21:59 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-06-05-21.01.txt | 21:59 |
openstack | Log: http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-06-05-21.01.log.html | 21:59 |
*** whoami-rajat has quit IRC | 22:00 | |
*** patchbot has left #openstack-meeting | 22:00 | |
mattoliverau | thanks timburke_ | 22:00 |
*** slaweq has joined #openstack-meeting | 22:02 | |
*** manjeets has joined #openstack-meeting | 22:03 | |
*** rcernin has quit IRC | 22:04 | |
*** slaweq has quit IRC | 22:08 | |
*** manjeets has quit IRC | 22:12 | |
*** e0ne has quit IRC | 22:13 | |
*** yamamoto has joined #openstack-meeting | 22:46 | |
*** tdasilva has quit IRC | 22:53 | |
*** raildo has quit IRC | 22:58 | |
*** artom has joined #openstack-meeting | 23:09 | |
*** carloss has quit IRC | 23:21 | |
*** _hemna has joined #openstack-meeting | 23:33 | |
*** ykatabam has joined #openstack-meeting | 23:42 | |
*** ykatabam has quit IRC | 23:48 | |
*** slaweq has joined #openstack-meeting | 23:48 | |
*** yamamoto has quit IRC | 23:48 | |
*** bobh has joined #openstack-meeting | 23:56 | |
*** ykatabam has joined #openstack-meeting | 23:58 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!