| *** igordc has quit IRC | 00:13 | |
| *** k_mouza has quit IRC | 00:16 | |
| *** k_mouza has joined #openstack-meeting-4 | 00:17 | |
| *** k_mouza has quit IRC | 00:21 | |
| *** k_mouza has joined #openstack-meeting-4 | 00:23 | |
| *** k_mouza has quit IRC | 00:44 | |
| *** k_mouza has joined #openstack-meeting-4 | 00:58 | |
| *** Liang__ has joined #openstack-meeting-4 | 01:12 | |
| *** k_mouza has quit IRC | 01:28 | |
| *** dave-mccowan has joined #openstack-meeting-4 | 02:00 | |
| *** pmesserli has joined #openstack-meeting-4 | 02:03 | |
| *** lvbin02 has joined #openstack-meeting-4 | 02:18 | |
| *** lvbin01 has quit IRC | 02:21 | |
| *** lvbin02 has quit IRC | 02:21 | |
| *** lvbin01 has joined #openstack-meeting-4 | 02:22 | |
| *** dave-mccowan has quit IRC | 02:55 | |
| *** k_mouza has joined #openstack-meeting-4 | 03:29 | |
| *** k_mouza has quit IRC | 03:34 | |
| *** psachin has joined #openstack-meeting-4 | 03:41 | |
| *** diablo_rojo has quit IRC | 04:29 | |
| *** dansmith has quit IRC | 05:10 | |
| *** dansmith has joined #openstack-meeting-4 | 05:14 | |
| *** pcaruana has joined #openstack-meeting-4 | 06:09 | |
| *** lpetrut has joined #openstack-meeting-4 | 07:18 | |
| *** k_mouza has joined #openstack-meeting-4 | 07:30 | |
| *** k_mouza has quit IRC | 07:34 | |
| *** gibi_off is now known as gibi | 07:44 | |
| *** gcheresh has joined #openstack-meeting-4 | 07:47 | |
| *** slaweq has joined #openstack-meeting-4 | 07:47 | |
| *** lemko has joined #openstack-meeting-4 | 07:53 | |
| *** eyalb1 has joined #openstack-meeting-4 | 07:54 | |
| *** belmoreira has joined #openstack-meeting-4 | 07:56 | |
| *** e0ne has joined #openstack-meeting-4 | 07:59 | |
| eyalb1 | #startmeeting vitrage | 08:00 |
|---|---|---|
| eyalb1 | #startmeeting vitrage | 08:00 |
| openstack | Meeting started Wed Dec 11 08:00:27 2019 UTC and is due to finish in 60 minutes. The chair is eyalb1. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:00 |
| *** openstack changes topic to " (Meeting topic: vitrage)" | 08:00 | |
| e0ne | hi | 08:00 |
| openstack | The meeting name has been set to 'vitrage' | 08:00 |
| eyalb1 | hi | 08:00 |
| eyalb1 | i have no updates | 08:01 |
| eyalb1 | idan fixed some bugs | 08:01 |
| eyalb1 | thats all for me | 08:01 |
| e0ne | neither for me:(. I just returned for an active upstream development | 08:01 |
| eyalb1 | ok | 08:01 |
| e0ne | I hope I'll have updates next week | 08:01 |
| eyalb1 | ok then we will end now | 08:01 |
| eyalb1 | bye | 08:02 |
| e0ne | see you next week | 08:02 |
| eyalb1 | #endmeeting vitrage | 08:02 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 08:02 | |
| openstack | Meeting ended Wed Dec 11 08:02:17 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 08:02 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/vitrage/2019/vitrage.2019-12-11-08.00.html | 08:02 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2019/vitrage.2019-12-11-08.00.txt | 08:02 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/vitrage/2019/vitrage.2019-12-11-08.00.log.html | 08:02 |
| *** e0ne has quit IRC | 08:06 | |
| *** bobmel has quit IRC | 08:08 | |
| *** e0ne has joined #openstack-meeting-4 | 08:19 | |
| *** pcaruana has quit IRC | 08:22 | |
| *** e0ne has quit IRC | 08:28 | |
| *** links has joined #openstack-meeting-4 | 08:44 | |
| *** ralonsoh has joined #openstack-meeting-4 | 08:55 | |
| *** k_mouza has joined #openstack-meeting-4 | 09:21 | |
| *** k_mouza has quit IRC | 09:22 | |
| *** k_mouza has joined #openstack-meeting-4 | 09:22 | |
| *** k_mouza has quit IRC | 09:26 | |
| *** k_mouza has joined #openstack-meeting-4 | 09:27 | |
| *** k_mouza has quit IRC | 09:28 | |
| *** k_mouza has joined #openstack-meeting-4 | 09:29 | |
| *** e0ne has joined #openstack-meeting-4 | 10:05 | |
| *** vishalmanchanda has joined #openstack-meeting-4 | 10:11 | |
| *** Liang__ has quit IRC | 10:17 | |
| *** salmankhan has joined #openstack-meeting-4 | 10:31 | |
| *** salmankhan has quit IRC | 10:32 | |
| *** salmankhan has joined #openstack-meeting-4 | 10:32 | |
| *** belmoreira has quit IRC | 10:44 | |
| *** belmoreira has joined #openstack-meeting-4 | 10:45 | |
| *** belmoreira has quit IRC | 10:49 | |
| *** k_mouza has quit IRC | 11:17 | |
| *** k_mouza has joined #openstack-meeting-4 | 11:17 | |
| *** pcaruana has joined #openstack-meeting-4 | 11:36 | |
| *** k_mouza has quit IRC | 11:55 | |
| *** k_mouza has joined #openstack-meeting-4 | 11:56 | |
| *** spsurya has joined #openstack-meeting-4 | 12:05 | |
| *** Liang__ has joined #openstack-meeting-4 | 12:27 | |
| *** eyalb has joined #openstack-meeting-4 | 12:30 | |
| *** eyalb1 has quit IRC | 12:33 | |
| *** k_mouza_ has joined #openstack-meeting-4 | 12:44 | |
| *** k_mouza has quit IRC | 12:47 | |
| *** k_mouza_ has quit IRC | 12:49 | |
| *** k_mouza has joined #openstack-meeting-4 | 12:49 | |
| *** whoami-rajat has joined #openstack-meeting-4 | 13:09 | |
| *** k_mouza has quit IRC | 13:11 | |
| *** eyalb has left #openstack-meeting-4 | 13:19 | |
| *** tosky has joined #openstack-meeting-4 | 13:20 | |
| *** anastzhyr has joined #openstack-meeting-4 | 13:21 | |
| *** k_mouza has joined #openstack-meeting-4 | 13:26 | |
| *** wuchunyang has quit IRC | 13:33 | |
| *** Liang__ is now known as LiangFang | 13:54 | |
| *** rosmaita has joined #openstack-meeting-4 | 13:56 | |
| rosmaita | courtesy meeting reminder: cinder weekly meeting here at 14:00 UTC | 13:59 |
| rosmaita | jungleboyj rosmaita smcginnis tosky whoami-rajat m5z e0ne geguileo eharney walshh_ ^^ | 13:59 |
| geguileo | hi! o/ | 13:59 |
| whoami-rajat | Hi | 13:59 |
| rosmaita | #startmeeting cinder | 14:00 |
| openstack | Meeting started Wed Dec 11 14:00:00 2019 UTC and is due to finish in 60 minutes. The chair is rosmaita. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
| *** openstack changes topic to " (Meeting topic: cinder)" | 14:00 | |
| openstack | The meeting name has been set to 'cinder' | 14:00 |
| smcginnis | o/ | 14:00 |
| LiangFang | o/ | 14:00 |
| rosmaita | #topic roll call | 14:00 |
| *** openstack changes topic to "roll call (Meeting topic: cinder)" | 14:00 | |
| rosmaita | \o | 14:00 |
| jungleboyj | o/ | 14:00 |
| tosky | o/ | 14:00 |
| *** bnemec has joined #openstack-meeting-4 | 14:01 | |
| rosmaita | guess that's everyone | 14:01 |
| rosmaita | just out of curiosity, can everyone state their UTC offset? | 14:02 |
| rosmaita | -5 | 14:02 |
| jungleboyj | -6 | 14:02 |
| LiangFang | +8 | 14:02 |
| smcginnis | -6 | 14:02 |
| whoami-rajat | +5:30 | 14:03 |
| jungleboyj | smcginnis: and I agree. That is a good sign. :-) | 14:03 |
| rosmaita | :) | 14:03 |
| tosky | +1 | 14:03 |
| smcginnis | ;) | 14:03 |
| rosmaita | geguileo: i think you are +1 ? | 14:03 |
| geguileo | +1 to what? | 14:04 |
| tosky | he is (unless he is travelling) (even though he is physically on +0, but that's a long story) | 14:04 |
| geguileo | rofl | 14:04 |
| geguileo | oh TZ | 14:04 |
| geguileo | yup +1 now | 14:04 |
| rosmaita | i will have to get that story some time | 14:04 |
| rosmaita | ok, thanks | 14:04 |
| rosmaita | #topic updates | 14:05 |
| *** openstack changes topic to "updates (Meeting topic: cinder)" | 14:05 | |
| rosmaita | this week is milestone-1, but since we don't have to release any more, it's not that big a deal | 14:05 |
| rosmaita | but, it's time to do our every-2-month release from stable branches | 14:05 |
| rosmaita | #link https://etherpad.openstack.org/p/cinder-releases-tracking | 14:06 |
| rosmaita | so, basically, cinder and os-brick could use releases | 14:06 |
| rosmaita | but, there is a pep8 failure happening in brick backports | 14:06 |
| rosmaita | you can see an example here: https://review.opendev.org/#/c/697116/1 | 14:07 |
| *** k_mouza has quit IRC | 14:07 | |
| *** k_mouza has joined #openstack-meeting-4 | 14:07 | |
| rosmaita | it's over W503 and W504 | 14:07 |
| rosmaita | which have to do with whether an operator should end or begin a continued line | 14:07 |
| rosmaita | pep8 has gone back and forth on that | 14:08 |
| rosmaita | and master and train for us ignore them both | 14:08 |
| *** kaisers has joined #openstack-meeting-4 | 14:08 | |
| rosmaita | anyway, i think we should backport the ignore to the stable branches that don't have it | 14:08 |
| rosmaita | because i'd rather not have to edit cherry picks for something silly like this | 14:09 |
| rosmaita | save that for serious conflicts | 14:09 |
| rosmaita | so i have proposed | 14:09 |
| rosmaita | #link https://review.opendev.org/#/c/698471/ | 14:09 |
| rosmaita | if everyone is cool with that plan, what i'd like to do is | 14:09 |
| rosmaita | get the pep8 ignore change backported | 14:09 |
| rosmaita | then complete the backport of the actual fix, which is "iscsi: Add _get_device_link retry when waiting for /dev/disk/by-id/ to populate" | 14:10 |
| rosmaita | and then do point releases of os-brick | 14:10 |
| smcginnis | Obviously the right answer is it should be end of line, but best to ignore. :D | 14:10 |
| rosmaita | maybe it's because of my eyeglass prescription, but i don't see that well all the way out to column 79 | 14:11 |
| rosmaita | so i prefer it at the front! | 14:11 |
| rosmaita | but yeah, this is a contentious issue | 14:11 |
| rosmaita | but i guess the key point here is we should do it the same from master on back | 14:11 |
| rosmaita | until we take a definitive stand | 14:12 |
| rosmaita | ok, so if everyone is OK with that plan, please keep an eye out for the patches so we can get it merged | 14:13 |
| rosmaita | i have not looked at cinder, python-cinderclient to see what they have for this | 14:13 |
| rosmaita | probably should | 14:13 |
| rosmaita | #action rosmaita check pep8 ignores in all cinder projects | 14:13 |
| rosmaita | ok | 14:13 |
| rosmaita | one more thing: cinderlib is ready for its train release | 14:14 |
| rosmaita | thanks to geguileo | 14:14 |
| rosmaita | this will be 1.0.0 ! | 14:14 |
| geguileo | awesome!! XD | 14:14 |
| rosmaita | and i think since we remove py2 support in ussuri, the first ussuri release will be 2.0.0 | 14:14 |
| rosmaita | that project is moving right along! | 14:14 |
| Roamer` | yeah, sort of off-topic (sowwy), but I'd like to thank geguileo for his work on cinderlib - it already exposed two (very minor) bugs in the StorPool driver | 14:15 |
| geguileo | Roamer`: nice!! | 14:15 |
| rosmaita | Roamer`: thanks to geguileo are always on topic | 14:15 |
| geguileo | lol | 14:15 |
| rosmaita | that's good news though, glad to see that it's helping keep the cinder drivers stable | 14:16 |
| rosmaita | ok, the final thing: branch closure situation | 14:16 |
| rosmaita | #link http://lists.openstack.org/pipermail/openstack-discuss/2019-December/011378.html | 14:17 |
| rosmaita | as we discussed last week, i sent a proposal to the ML to EOL the driverfixes branches, but keep o and p in EM | 14:17 |
| rosmaita | from the absence of responses, it sounds like that's acceptable to the community | 14:17 |
| rosmaita | so, i'll revise my EOL patch and resubmit it early next week | 14:18 |
| rosmaita | (give the release team time to handle all the M-1 releases this week) | 14:18 |
| rosmaita | so if anyone wants to save driverfixes/newton, this is your last chance | 14:18 |
| rosmaita | i guess the only other announcement is a reminder to everyone to review open cinder-specs | 14:19 |
| *** eharney has joined #openstack-meeting-4 | 14:19 | |
| rosmaita | #topic the FCZM situation | 14:20 |
| *** openstack changes topic to "the FCZM situation (Meeting topic: cinder)" | 14:20 | |
| rosmaita | #link https://review.opendev.org/#/c/696857/ | 14:20 |
| rosmaita | ok, so the situation is that we currently have 2 zonemanagers for fibre channel | 14:21 |
| rosmaita | brocade has announced EOL for its driver | 14:21 |
| rosmaita | last supported release for them is Train | 14:21 |
| rosmaita | unfortunately, this got announced the week before train release | 14:22 |
| rosmaita | so we did not deprecate the driver in Train | 14:22 |
| smcginnis | They have also reached out directly and asked us to clean things up since they are not able to. | 14:22 |
| rosmaita | yes, they are dropping and running | 14:23 |
| geguileo | rosmaita: lol | 14:23 |
| rosmaita | so the first issue is: | 14:23 |
| rosmaita | can we consider their EOL announcement to customers as a deprecation in Train, so we could remove the driver now in ussuri? | 14:23 |
| rosmaita | my reason for this is that we don't know if it will run under py3 | 14:24 |
| rosmaita | (the py3 compat seems to have been the final straw for them) | 14:24 |
| geguileo | I would hate it for us to have only 1 FCZM driver | 14:25 |
| geguileo | even if we mark it as unsupported | 14:25 |
| rosmaita | hemna feels that way, too | 14:25 |
| jungleboyj | geguileo: ++ | 14:26 |
| geguileo | would the community be willing to get leave it as unsupported if I can confirm it works for Py3? | 14:26 |
| smcginnis | I don't like it, but if the vendor isn't going to support it, then we can only provide the one that does. | 14:26 |
| geguileo | Or if I can fix it and make it work for py3? | 14:26 |
| rosmaita | i am not against that, at least not short-term | 14:27 |
| rosmaita | if we confirm that it works on py3, i will withdraw my proposal to remove it it ussuri | 14:27 |
| smcginnis | I would prefer if we keep it unsupported in Ussuri, but I don't think it should fall on the community to support it and keep it around past that. | 14:27 |
| rosmaita | yeah, we don't want to set a bad precedent | 14:27 |
| smcginnis | So even if we fix any py3 issues, I think it's safer if we clearly announce it is going away in V. | 14:28 |
| geguileo | I think not having that as a FCZM will be a big problem for OpenStack customers | 14:28 |
| rosmaita | well, we can state "subject to removal in V as per the openstack deprecation policy" | 14:29 |
| rosmaita | that gives us some room to keep it around longer if we decide it's a good idea | 14:29 |
| geguileo | rosmaita: and what are customers going to do? | 14:29 |
| jungleboyj | geguileo: ++ | 14:29 |
| geguileo | rosmaita: ok | 14:29 |
| jungleboyj | Too bad hemna isn't here. He thought maybe we could help leverage HPE. | 14:29 |
| rosmaita | geguileo: i really don't know -- i would hope that customers would lean on brocade to keep it around | 14:30 |
| geguileo | I will look for a cheap brocade FC switch I can use to test/fix the driver at home | 14:30 |
| smcginnis | Well, if Brocade isn't going to support it, I think that's a pretty strong statement. | 14:30 |
| smcginnis | Customers can complain to them and get them to bring it back if it's that badly needed. | 14:30 |
| geguileo | smcginnis: it is, but it will have a big effect on the perception of Cinder/OpenStack on customers | 14:30 |
| rosmaita | i think that's already happened, though, by their announcement | 14:31 |
| smcginnis | Only with FC. I don't think that's too big of a perception issue. :D | 14:31 |
| smcginnis | rosmaita: ++ | 14:31 |
| geguileo | as a customer I would complain, and if that gets me nowhere I may decide to go to other platform... :-( | 14:31 |
| rosmaita | right | 14:31 |
| geguileo | ok, let's go with rosmaita's suggestion and see if I can get this fixed tested | 14:32 |
| rosmaita | ok, well the key issue i wanted to sort out today was our community attitude | 14:32 |
| geguileo | and I can bring the topic back once I do that | 14:32 |
| rosmaita | so sounds like: | 14:32 |
| rosmaita | we deprecate it now "subject to removal in V as per policy" | 14:32 |
| rosmaita | (2) geguileo figures out the py3 situation | 14:32 |
| rosmaita | and then we discuss again | 14:33 |
| geguileo | sounds good to me | 14:33 |
| jungleboyj | Great. | 14:33 |
| rosmaita | ok, thanks geguileo -- you are addressing my major concern | 14:33 |
| jungleboyj | geguileo: To the rescue again. | 14:34 |
| rosmaita | in the mean time, i don't know if there's anything we can do to encourage more FC participation? | 14:34 |
| geguileo | rosmaita: maybe the effort we discussed in the PTG | 14:34 |
| geguileo | of making it easy to have a CI | 14:34 |
| geguileo | that would lessen the burden | 14:35 |
| rosmaita | true | 14:35 |
| rosmaita | ok, that gives us a reason to keep that as a priority | 14:35 |
| rosmaita | it's weird -- everyone wants excellent performance, but they also want to use commodity hardware | 14:36 |
| rosmaita | but that's off topic | 14:36 |
| geguileo | I believe we discussed the software factory thingy that the RDO folks have to do the 3rd party CI | 14:36 |
| geguileo | and I think tosky started documenting some of it | 14:36 |
| rosmaita | i'll check in with tosky and see what i can do to help | 14:37 |
| jungleboyj | It would be so nice if someone could make 3rd Party CI easy. | 14:38 |
| rosmaita | amen, you are singing to the choir | 14:38 |
| tosky | I collected some information; the softwarefactory people are going to release a new version these days, with more documentation | 14:38 |
| rosmaita | great | 14:38 |
| tosky | the idea is that following their documentation should be enough to get started | 14:38 |
| geguileo | tosky: that's awesome!! | 14:38 |
| rosmaita | and we can always submit clarifying patches | 14:39 |
| rosmaita | that's really good news | 14:39 |
| rosmaita | #topic support volume local cache | 14:39 |
| *** openstack changes topic to "support volume local cache (Meeting topic: cinder)" | 14:39 | |
| *** walshh_ has joined #openstack-meeting-4 | 14:39 | |
| rosmaita | LiangFang: that's you | 14:39 |
| LiangFang | I work for the poc code change | 14:40 |
| LiangFang | and the poc is almost finished | 14:40 |
| LiangFang | will push to review in coming days | 14:40 |
| LiangFang | poc code is almost finished | 14:40 |
| LiangFang | one question is | 14:40 |
| LiangFang | the cache software will have some configuration | 14:41 |
| LiangFang | e.g. cache id | 14:41 |
| LiangFang | normally if we use one fast ssd as cache, the the cache id will be 1 | 14:41 |
| LiangFang | the use two ssd, it may be 2 | 14:41 |
| LiangFang | then if we use this ssd to cache for a remote volume, we need to specify the cache id (means the fast ssd) | 14:42 |
| LiangFang | but we can specify the cache id as a big number, e.g. 9999 | 14:43 |
| LiangFang | choice1: the cache id can be set in nova-cpu.conf | 14:43 |
| LiangFang | choice2, the cache id can be hard coded in os-brick, but the number should be large enough, e.g. 9999, so this number will not be used by others | 14:44 |
| LiangFang | choice 2 is easy for coding | 14:45 |
| LiangFang | choice 1 need the configuration change in nova | 14:45 |
| LiangFang | I prefer choice 1. | 14:45 |
| geguileo | LiangFang: I am not following sorry | 14:46 |
| geguileo | LiangFang: where do we use this cache ID? | 14:46 |
| geguileo | Is this ID something that matches a hardware ID of the cache? | 14:46 |
| rosmaita | is the issue that there may be multiple caches available, and we need to know which one to use? | 14:46 |
| geguileo | what if there are multiple caches? | 14:46 |
| LiangFang | when caching a remote volume, should specify which cache to use | 14:46 |
| LiangFang | rosmaita: yes | 14:46 |
| LiangFang | normally one cache in system, but it can be multiple caches | 14:47 |
| geguileo | what if we want to use multiple caches? | 14:47 |
| *** eharney has quit IRC | 14:47 | |
| LiangFang | I just need one cache | 14:47 |
| geguileo | but what if you have 2 and you want to use both? | 14:48 |
| geguileo | we don't need to solve it now, but the solution should be able to support it in the future | 14:48 |
| geguileo | without having to change everything | 14:48 |
| LiangFang | I plan to use only one | 14:48 |
| LiangFang | the cache id is increase one by one by default if not specified | 14:49 |
| geguileo | but someone else may want to use 2, right? | 14:49 |
| *** links has quit IRC | 14:49 | |
| geguileo | LiangFang: is increased by the Linux system? | 14:49 |
| LiangFang | by the opencas software | 14:49 |
| geguileo | and that ID may change when you reboot the system? | 14:50 |
| LiangFang | it can add more than one cache. the first cache's id if 1 by default, the second id would be 2 by default | 14:50 |
| geguileo | what happens if you reboot? | 14:50 |
| geguileo | can they have different IDs then? | 14:50 |
| LiangFang | it can be configured in opencas configuration file, or use the opencas admin tool | 14:50 |
| geguileo | don't caches have a unique ID somewhere? | 14:51 |
| LiangFang | I mean, os-brick don't know which cache to use | 14:51 |
| LiangFang | one way is let nova to tell os-brick | 14:51 |
| geguileo | yes, but if nova tells os-brick use 1 | 14:52 |
| LiangFang | another way is os-brick just use a hard coded cache id, e.g. 9999 | 14:52 |
| geguileo | and the system have 1 and 2 | 14:52 |
| geguileo | then we reboot | 14:52 |
| geguileo | and now the cache that was 1 before is now using id 2 | 14:52 |
| geguileo | then we won't be using the cache we want | 14:52 |
| LiangFang | the cache id will not change after reboot | 14:53 |
| geguileo | oh, ok | 14:53 |
| geguileo | then we are good | 14:53 |
| LiangFang | it is configured in opencas configuration file | 14:53 |
| geguileo | I prefer the nova conf, same as you | 14:53 |
| LiangFang | thing is: how os-brick know which cache to use | 14:53 |
| LiangFang | one is : nova tell it | 14:54 |
| LiangFang | another is hard coded in os-brick | 14:54 |
| geguileo | the nova approach seems like the right one | 14:54 |
| LiangFang | second way is easy, but need to document: cache id is 9999 | 14:54 |
| jungleboyj | geguileo: ++ | 14:55 |
| rosmaita | ok, that asnwers my question ... the operator would have to configure a cache with id 9999 | 14:55 |
| jungleboyj | Hardcoded values always seem dangerous to me. | 14:55 |
| LiangFang | rosmaita: yes, if 9999 is hard coded in os-brick | 14:55 |
| LiangFang | ok... | 14:55 |
| rosmaita | so with choice 1, you would define a dedicated cache id for brick to use in nova.conf ? | 14:56 |
| LiangFang | so nova configuration file need to be changed | 14:56 |
| LiangFang | rosmaita: yes | 14:56 |
| rosmaita | ok | 14:56 |
| LiangFang | but 9999 would be safe for opencas forever | 14:56 |
| geguileo | I think that's the best approach | 14:56 |
| LiangFang | ok | 14:56 |
| geguileo | I don't like the hardcoding magical numbers in our code | 14:57 |
| rosmaita | probably everyone will use 9999, but making this configurable is better | 14:57 |
| LiangFang | ok | 14:57 |
| LiangFang | so I will change my poc code | 14:57 |
| rosmaita | ok, we are down to 2.5 minutes | 14:57 |
| rosmaita | LiangFang: did you get all the answers you need? | 14:58 |
| rosmaita | (for now) | 14:58 |
| LiangFang | I'm write a white paper about this with our telecom customer these 3 weeks, will let you know when we finished | 14:58 |
| geguileo | LiangFang: thanks | 14:58 |
| geguileo | LiangFang: awesome!! | 14:58 |
| *** wuchunyang has joined #openstack-meeting-4 | 14:58 | |
| LiangFang | rosmaita: yes, thanks | 14:58 |
| rosmaita | yes, it will be helpful to see how all this works for real | 14:59 |
| rosmaita | ok, 1 minute for | 14:59 |
| rosmaita | #topic open discussion | 14:59 |
| *** openstack changes topic to "open discussion (Meeting topic: cinder)" | 14:59 | |
| rosmaita | ok, well thanks for a productive meeting everyone! | 14:59 |
| jungleboyj | Thanks rosmaita ! | 14:59 |
| rosmaita | see you next week | 15:00 |
| rosmaita | don't forget to review cinder-specs! | 15:00 |
| LiangFang | see you, thanks | 15:00 |
| rosmaita | #endmeeting | 15:00 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 15:00 | |
| whoami-rajat | Thanks everyone! | 15:00 |
| openstack | Meeting ended Wed Dec 11 15:00:12 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:00 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-12-11-14.00.html | 15:00 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-12-11-14.00.txt | 15:00 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-12-11-14.00.log.html | 15:00 |
| *** wuchunyang has quit IRC | 15:02 | |
| *** lemko has quit IRC | 15:03 | |
| *** whoami-rajat has quit IRC | 15:18 | |
| *** tosky has left #openstack-meeting-4 | 15:22 | |
| *** eharney has joined #openstack-meeting-4 | 15:23 | |
| *** lpetrut has quit IRC | 15:32 | |
| *** links has joined #openstack-meeting-4 | 15:38 | |
| *** gcheresh_ has joined #openstack-meeting-4 | 16:04 | |
| *** gcheresh has quit IRC | 16:04 | |
| *** gcheresh_ has quit IRC | 16:09 | |
| *** k_mouza has quit IRC | 16:25 | |
| *** k_mouza_ has joined #openstack-meeting-4 | 16:25 | |
| *** gcheresh_ has joined #openstack-meeting-4 | 16:30 | |
| *** k_mouza has joined #openstack-meeting-4 | 16:30 | |
| *** rosmaita has left #openstack-meeting-4 | 16:32 | |
| *** k_mouza_ has quit IRC | 16:32 | |
| *** gcheresh_ has quit IRC | 16:39 | |
| *** LiangFang has quit IRC | 17:01 | |
| *** wuchunyang has joined #openstack-meeting-4 | 17:03 | |
| *** wuchunyang has quit IRC | 17:08 | |
| *** wuchunyang has joined #openstack-meeting-4 | 17:14 | |
| *** wuchunyang has quit IRC | 17:19 | |
| *** psachin has quit IRC | 17:19 | |
| *** jlvillal has left #openstack-meeting-4 | 17:20 | |
| *** links has quit IRC | 17:22 | |
| *** wuchunyang has joined #openstack-meeting-4 | 17:40 | |
| *** igordc has joined #openstack-meeting-4 | 17:42 | |
| *** diablo_rojo has joined #openstack-meeting-4 | 17:44 | |
| *** wuchunyang has quit IRC | 17:44 | |
| *** k_mouza has quit IRC | 17:45 | |
| *** k_mouza has joined #openstack-meeting-4 | 17:48 | |
| *** k_mouza has quit IRC | 17:49 | |
| *** wuchunyang has joined #openstack-meeting-4 | 17:50 | |
| *** wuchunyang has quit IRC | 17:55 | |
| *** wuchunyang has joined #openstack-meeting-4 | 17:59 | |
| *** wuchunyang has quit IRC | 18:04 | |
| *** wuchunyang has joined #openstack-meeting-4 | 18:10 | |
| *** igordc has quit IRC | 18:13 | |
| *** igordc has joined #openstack-meeting-4 | 18:14 | |
| *** e0ne has quit IRC | 18:14 | |
| *** wuchunyang has quit IRC | 18:16 | |
| *** salmankhan has quit IRC | 18:19 | |
| *** igordc has quit IRC | 18:25 | |
| *** k_mouza has joined #openstack-meeting-4 | 18:39 | |
| *** anastzhyr has quit IRC | 18:41 | |
| *** k_mouza has quit IRC | 18:43 | |
| *** ralonsoh has quit IRC | 18:55 | |
| *** wuchunyang has joined #openstack-meeting-4 | 18:56 | |
| *** wuchunyang has quit IRC | 19:05 | |
| *** wuchunyang has joined #openstack-meeting-4 | 19:13 | |
| *** spsurya has quit IRC | 19:14 | |
| *** wuchunyang has quit IRC | 19:17 | |
| *** wuchunyang has joined #openstack-meeting-4 | 19:24 | |
| *** wuchunyang has quit IRC | 19:29 | |
| *** eharney has quit IRC | 19:30 | |
| *** lpetrut has joined #openstack-meeting-4 | 19:33 | |
| *** wuchunyang has joined #openstack-meeting-4 | 19:33 | |
| *** wuchunyang has quit IRC | 19:37 | |
| *** wuchunyang has joined #openstack-meeting-4 | 19:39 | |
| *** wuchunyang has quit IRC | 19:43 | |
| *** lpetrut has quit IRC | 19:46 | |
| *** wuchunyang has joined #openstack-meeting-4 | 19:48 | |
| *** wuchunyang has quit IRC | 19:55 | |
| *** eharney has joined #openstack-meeting-4 | 20:12 | |
| *** wuchunyang has joined #openstack-meeting-4 | 20:20 | |
| *** wuchunyang has quit IRC | 20:32 | |
| *** wuchunyang has joined #openstack-meeting-4 | 20:39 | |
| *** wuchunyang has quit IRC | 20:44 | |
| *** wuchunyang has joined #openstack-meeting-4 | 20:44 | |
| *** wuchunyang has quit IRC | 20:52 | |
| *** wuchunyang has joined #openstack-meeting-4 | 20:56 | |
| *** wuchunyang has quit IRC | 21:00 | |
| *** slaweq has quit IRC | 21:03 | |
| *** slaweq has joined #openstack-meeting-4 | 21:11 | |
| *** slaweq has quit IRC | 21:16 | |
| *** wuchunyang has joined #openstack-meeting-4 | 21:24 | |
| *** wuchunyang has quit IRC | 21:38 | |
| *** pcaruana has quit IRC | 21:38 | |
| *** wuchunyang has joined #openstack-meeting-4 | 21:44 | |
| *** k_mouza has joined #openstack-meeting-4 | 21:50 | |
| *** wuchunyang has quit IRC | 21:51 | |
| *** k_mouza has quit IRC | 21:55 | |
| *** wuchunyang has joined #openstack-meeting-4 | 21:58 | |
| *** wuchunyang has quit IRC | 22:02 | |
| *** slaweq has joined #openstack-meeting-4 | 22:11 | |
| *** wuchunyang has joined #openstack-meeting-4 | 22:13 | |
| *** slaweq has quit IRC | 22:16 | |
| *** wuchunyang has quit IRC | 22:18 | |
| *** wuchunyang has joined #openstack-meeting-4 | 22:23 | |
| *** wuchunyang has quit IRC | 22:25 | |
| *** wuchunyang has joined #openstack-meeting-4 | 22:30 | |
| *** wuchunyang has quit IRC | 22:35 | |
| *** wuchunyang has joined #openstack-meeting-4 | 22:36 | |
| *** wuchunyang has quit IRC | 22:43 | |
| *** wuchunyang has joined #openstack-meeting-4 | 23:05 | |
| *** slaweq has joined #openstack-meeting-4 | 23:11 | |
| *** wuchunyang has quit IRC | 23:13 | |
| *** slaweq has quit IRC | 23:15 | |
| *** wuchunyang has joined #openstack-meeting-4 | 23:17 | |
| *** Liang__ has joined #openstack-meeting-4 | 23:20 | |
| *** wuchunyang has quit IRC | 23:25 | |
| *** wuchunyang has joined #openstack-meeting-4 | 23:26 | |
| *** wuchunyang has quit IRC | 23:30 | |
| *** slaweq has joined #openstack-meeting-4 | 23:32 | |
| *** wuchunyang has joined #openstack-meeting-4 | 23:33 | |
| *** slaweq has quit IRC | 23:41 | |
| *** Liang__ has quit IRC | 23:42 | |
| *** wuchunyang has quit IRC | 23:42 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!