| opendevreview | 陈希 proposed openstack/cinder master: Support zte vstorage driver https://review.opendev.org/c/openstack/cinder/+/923016 | 03:36 |
|---|---|---|
| opendevreview | 陈希 proposed openstack/cinder master: Support zte vstorage driver https://review.opendev.org/c/openstack/cinder/+/923016 | 06:55 |
| opendevreview | Josephine Seifert proposed openstack/cinder-specs master: Spec for user visible information in volume types https://review.opendev.org/c/openstack/cinder-specs/+/909195 | 07:55 |
| opendevreview | Merged openstack/cinder master: StorPool: create_cloned_volume() improvements https://review.opendev.org/c/openstack/cinder/+/843277 | 08:25 |
| joa | Hello ! I'm part of a (relatively?) small company, that is slowly switching its home-made software infrastructure to Openstack. I've been tasked to adapt an automated backup design/solution that we originally planned for our legacy stack, and am currently looking for the best way to do this. So far, I've not found much except basic primitives in cinder-backup, and the almost-dead project that is | 08:43 |
| joa | Freezer (I found a mail thread dating 3 months back about people wondering if they shoud use it or not, and there was some thought put into possibly reviving it). | 08:43 |
| joa | So with this introduction out of the way, here are my more straight-forward questions: | 08:43 |
| joa | 1. Our existing design relies on backend-assisted data-transfer, and no such concept seem to be available in cinder-backup, as the volumes seem to always be Attached to the cinder-backup host for the transfers (in the backup.manager.BackupManager class). Did I understand this correctly ? Is there any interest for a contribution towards a capability-based logic selection of cinder-backup driven | 08:45 |
| joa | transfer versus storage-backend-assissted transfer logic ? | 08:45 |
| joa | 2. While this question may not be cinder-specific, you probably are well aware of the matter: For the automation part of the backup, I'm wondering if Freezer is still the recommended way for integrating an automated backup in an openstack-based infrastructure, or if another path is preferable ? | 08:47 |
| *** whoami-rajat_ is now known as whoami-rajat | 11:25 | |
| rosmaita | joa: with respect to #1, i think this driver (removed in wallaby) did something like you propose, so there's a precedent | 13:02 |
| rosmaita | not sure about #2, you may want to ask in the operators channel, or on the mailing list | 13:03 |
| rosmaita | also, not sure what kind of timeline you are looking at, you could consider talking about this at the next midcycle video meeting: | 13:04 |
| rosmaita | https://releases.openstack.org/dalmatian/schedule.html#d-cinder-mid-cycle-ptg-2 | 13:04 |
| rosmaita | and, i just realized i forgot to give you the link for #1 | 13:04 |
| rosmaita | https://review.opendev.org/c/openstack/cinder/+/75856 | 13:04 |
| kpdev | hi | 13:09 |
| kpdev | can someone from core-team review https://review.opendev.org/c/openstack/os-brick/+/887575 ? | 13:09 |
| kpdev | this has one +2 from Rajat, need another one for merge | 13:09 |
| eharney | kpdev: i -1'd it | 13:45 |
| opendevreview | kiran pawar proposed openstack/os-brick master: storpool.py: Use StorPool's API for Attach/Detach https://review.opendev.org/c/openstack/os-brick/+/887575 | 14:02 |
| kpdev | @eharney: fixed, please recheck | 14:03 |
| raghavendrat | hi core team, i have proposed below patch | 15:36 |
| raghavendrat | HPE 3par - Add NVMe FC support | 15:36 |
| raghavendrat | https://review.opendev.org/c/openstack/cinder/+/919424 | 15:36 |
| raghavendrat | Zuul and CI have passed. | 15:36 |
| raghavendrat | Not sure if it would be considered as new driver or just new feature. | 15:37 |
| raghavendrat | It would be great if someone can share feedback. Thanks. | 15:37 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!