<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic RHEV and OCI in Active IQ Unified Manager Discussions</title>
    <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/RHEV-and-OCI/m-p/109893#M19402</link>
    <description>&lt;P&gt;Hey all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;if you are a Red Hat shop with RHEV on the floor, and are interested in RHEV support in OCI, we are a bit blocked by&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://bugzilla.redhat.com/show_bug.cgi?id=1264053" target="_blank"&gt;https://bugzilla.redhat.com/show_bug.cgi?id=1264053&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Basically, OCI host virtualization datasources expect to understand a hypervisor's FC WWNN and WWPNs, as well as iSCSI IQNs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There is apparently RHEV REST API tooling for the iSCSI stuff, but not the FC stuff. Given how much FC storage OCI monitors for customers around the world, this is a real inhibitor for us to bring a datasource without this information. The alternatives are not attractive - SSHing to each hypervisor, which may require root-like privileges?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Let Red Hat know if you are impacted, as my experience tells me product managers prefer more rather than less feedback from customers&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 23:16:59 GMT</pubDate>
    <dc:creator>ostiguy</dc:creator>
    <dc:date>2025-06-04T23:16:59Z</dc:date>
    <item>
      <title>RHEV and OCI</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/RHEV-and-OCI/m-p/109893#M19402</link>
      <description>&lt;P&gt;Hey all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;if you are a Red Hat shop with RHEV on the floor, and are interested in RHEV support in OCI, we are a bit blocked by&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://bugzilla.redhat.com/show_bug.cgi?id=1264053" target="_blank"&gt;https://bugzilla.redhat.com/show_bug.cgi?id=1264053&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Basically, OCI host virtualization datasources expect to understand a hypervisor's FC WWNN and WWPNs, as well as iSCSI IQNs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There is apparently RHEV REST API tooling for the iSCSI stuff, but not the FC stuff. Given how much FC storage OCI monitors for customers around the world, this is a real inhibitor for us to bring a datasource without this information. The alternatives are not attractive - SSHing to each hypervisor, which may require root-like privileges?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Let Red Hat know if you are impacted, as my experience tells me product managers prefer more rather than less feedback from customers&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 23:16:59 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/RHEV-and-OCI/m-p/109893#M19402</guid>
      <dc:creator>ostiguy</dc:creator>
      <dc:date>2025-06-04T23:16:59Z</dc:date>
    </item>
  </channel>
</rss>

