
<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">OK thanks, looks like there might be a bug here so have created<div class=""><br class=""></div><div class=""><a href="https://bugs.launchpad.net/cinder/+bug/1817802" class="">https://bugs.launchpad.net/cinder/+bug/1817802</a></div><div class=""><br class=""></div><div class=""><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Sam</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 26 Feb 2019, at 8:37 pm, Gorka Eguileor <<a href="mailto:geguileo@redhat.com" class="">geguileo@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On 26/02, Sam Morrison wrote:<br class=""><blockquote type="cite" class="">Hi,<br class="">Just wondering if extra_capabilities should be available in backend_state<br class="">to be able to be used by scheduler filters?<br class=""><br class="">I can't seem to use my custom capabilities within the capabilities filter.<br class=""><br class="">Thanks,<br class="">Sam<br class=""></blockquote><br class="">Hi Sam,<br class=""><br class="">As far as I know this is supported.<br class=""><br class="">The volume manager is sending this information to the scheduler and the<br class="">capabilities filter should be able to match the extra specs from the<br class="">volume type to the extra capabilities you have set in the configuration<br class="">of the cinder volume service using available operations: =, <in>, <is>,<br class="">etc.<br class=""><br class="">Cheers,<br class="">Gorka.<br class=""></div></div></blockquote></div><br class=""></div></div></body></html>