Thursday, 2021-07-01

xuanyWhat's the version Y's full name?02:25
*** bhagyashris is now known as bhagyashris|ruck05:22
*** akekane_ is now known as abhishekk06:32
lpetrutHi, I've just noticed that it's still hard to tell which actions can be performed against a given volume. The capabilities API seems to be admin only and describes only a few capabilities. We're working on a service that consumes Openstack APIs and we might have to avoid certain features (e.g. snapshot revert) because it's hard to tell if the volume backend supports it.06:47
opendevreviewLee Yarwood proposed openstack/os-brick master: linuxscsi: Only raise and log multipathd errors when required
*** dviroel|out is now known as dviroel11:32
opendevreviewBrian Rosmaita proposed openstack/python-cinderclient master: Remove skip_missing_interpreters
rosmaitalpetrut: that came up at the Xena PTG, though my summary doesn't really focus on that part, so you may want to run through the recording12:59
rosmaitalpetrut: also, see the third bullet point in the "A few issues came up in the course of this discussion" list:
rosmaitalpetrut: though what's described there is probably still going to be an "admin api" because it exposes backend capabilities13:02
rosmaitalpetrut: and finally, there is an approved spec for Xena to expose some capabilities to end users which could be a basis for what you want (maybe):
lpetrutrosmaita: interesting, thanks a lot! it's a step forward, but it needs the capabilities to be explicitly requested through volume types. I see that a new user visible API for the volume capabilities was also mentioned as an alternative.13:14
rosmaitalpetrut: yes, what we need at this point is someone with a coherent vision to step up and articulate exactly what should be exposed ... sounds like you could be a candidate13:19
rosmaitawe have a midcycle coming up at week R-9, could be a good time to discuss ideas with the team, and then follow up at the PTG to plan something for the Y release13:20
rosmaitalpetrut: and chat with eharney, he has definite opinions on how a capabilities API should work13:21
lpetrutrosmaita: unfortunately, very little of my time goes to upstream development these days so I may not be able to contribute (much) code. But for sure, I'll add the PTG to my calendar and provide some feedback.13:28
rosmaitalpetrut: that's a bummer, but on the optimistic side, it would be really helpful to have real-life use cases to work with, so you could help there13:34
*** dviroel is now known as dviroel|lunch16:00
*** dviroel|lunch is now known as dviroel16:28
opendevreviewLee Yarwood proposed openstack/os-brick master: linuxscsi: Only raise and log multipathd errors when required
opendevreviewkatari manoj kumar proposed openstack/cinder master: [SVF]:Fix add volumes to GMCV group
*** dviroel is now known as dviroel|sfk19:00
*** dviroel|sfk is now known as dviroel|afk19:01
opendevreviewBrian Rosmaita proposed openstack/rbd-iscsi-client master: [trivial] Add two missing periods
opendevreviewMerged openstack/rbd-iscsi-client master: [trivial] Add two missing periods
*** dviroel|afk is now known as dviroel20:21
*** dviroel is now known as dviroel|out21:52

Generated by 2.17.2 by Marius Gedminas - find it at!