topic Lots of question about Service Level Manager in Active IQ Unified Manager Discussions https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Lots-of-question-about-Service-Level-Manager/m-p/134636#M24436 <P>Hello&nbsp;</P><P>&nbsp;</P><P>I hope you will not be discouraged by so many questions</P><P>&nbsp;</P><UL><LI>&nbsp;Is OCUM or OPM mandatory for SLM to work ?</LI><LI>If OCUM or OPM is not mandatory but missing in SLM setting what features are lost ?<UL><LI>Does Conformance check use OPM counters or perf. counters directly from cluster ?</LI></UL></LI><LI>When importing workload what hapen if some workloads cannot be imported ?<UL><LI>Does this mean that QOS policy could not be applied to these workloads ?</LI><LI>Does this mean that storage pool budgeting could not take into account these workloads and so distort results ?</LI></UL></LI><LI>Volumes with both CIFS and NFS shares seems to be unimportable in SLM 1.0. Right ? Some plan to support it on future release ?<UL><LI>When we have on a volume with several qtrees with CIFS and NFS shares defined on them, Can SLM manage SLO/QOS on this volume which hosts these qtrees ?</LI></UL></LI><LI>What is the criteria used by SLM to provision a volume into a storage pool (aggregate)<UL><LI>available space in the storage pool: <STRONG>OK</STRONG></LI><LI>available IOPS on storage pool. <STRONG>QUESTION HERE</STRONG>:<UL><LI>Only based on budgeting and not on the real measured IOPS ?</LI></UL></LI><LI>requested space: <STRONG>OK</STRONG></LI><LI>requested SLO: <STRONG>QUESTION HERE</STRONG><UL><LI>How IOPS limit is computed from SLO while the used volume size is 0 &nbsp;?</LI><LI>Use Absolute Minimum IOPS parameter ?</LI></UL></LI></UL></LI><LI>What is IOPS limit set on the volume QOS policy<UL><LI>SLO peak (IOPS/TB) * volume used size (TB) ?</LI><LI>SLO Expected (IOPS/TB) * volume used size (TB) ?</LI><LI>... ?</LI></UL></LI><LI>More general question: How SLO parameters are used to set QOS or check conformance, etc...<UL><LI>Peak IOPS/TB</LI><LI>Expected IOPS/TB</LI><LI>Peak Latency</LI><LI>Initial Peak IOPS Allocation</LI><LI>Over-subscribe Expected IOPS</LI><LI>Absolute Minimum</LI></UL></LI><LI>Something I do not understand in the documentation. That look controdictory for me about the provision of new workloads. Thanks to clarify<UL><LI>Page 6: Standard capacities: Automatic provisioning per the storage service level by using APIs</LI><LI>Page 9: Configuring new workloads for using storage service levels (SSLs) and service level objective-based (SLO-based) APIs involves enabling the SLO advanced license</LI><LI>in my understanding "configuring new workload" means "provisioning new workload" but maybe I am worng</LI></UL></LI></UL><P>&nbsp;</P><P>Thanks in advance for your patience</P><P>Regards</P><P>Christian</P> Wed, 04 Jun 2025 14:35:00 GMT christig 2025-06-04T14:35:00Z Lots of question about Service Level Manager https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Lots-of-question-about-Service-Level-Manager/m-p/134636#M24436 <P>Hello&nbsp;</P><P>&nbsp;</P><P>I hope you will not be discouraged by so many questions</P><P>&nbsp;</P><UL><LI>&nbsp;Is OCUM or OPM mandatory for SLM to work ?</LI><LI>If OCUM or OPM is not mandatory but missing in SLM setting what features are lost ?<UL><LI>Does Conformance check use OPM counters or perf. counters directly from cluster ?</LI></UL></LI><LI>When importing workload what hapen if some workloads cannot be imported ?<UL><LI>Does this mean that QOS policy could not be applied to these workloads ?</LI><LI>Does this mean that storage pool budgeting could not take into account these workloads and so distort results ?</LI></UL></LI><LI>Volumes with both CIFS and NFS shares seems to be unimportable in SLM 1.0. Right ? Some plan to support it on future release ?<UL><LI>When we have on a volume with several qtrees with CIFS and NFS shares defined on them, Can SLM manage SLO/QOS on this volume which hosts these qtrees ?</LI></UL></LI><LI>What is the criteria used by SLM to provision a volume into a storage pool (aggregate)<UL><LI>available space in the storage pool: <STRONG>OK</STRONG></LI><LI>available IOPS on storage pool. <STRONG>QUESTION HERE</STRONG>:<UL><LI>Only based on budgeting and not on the real measured IOPS ?</LI></UL></LI><LI>requested space: <STRONG>OK</STRONG></LI><LI>requested SLO: <STRONG>QUESTION HERE</STRONG><UL><LI>How IOPS limit is computed from SLO while the used volume size is 0 &nbsp;?</LI><LI>Use Absolute Minimum IOPS parameter ?</LI></UL></LI></UL></LI><LI>What is IOPS limit set on the volume QOS policy<UL><LI>SLO peak (IOPS/TB) * volume used size (TB) ?</LI><LI>SLO Expected (IOPS/TB) * volume used size (TB) ?</LI><LI>... ?</LI></UL></LI><LI>More general question: How SLO parameters are used to set QOS or check conformance, etc...<UL><LI>Peak IOPS/TB</LI><LI>Expected IOPS/TB</LI><LI>Peak Latency</LI><LI>Initial Peak IOPS Allocation</LI><LI>Over-subscribe Expected IOPS</LI><LI>Absolute Minimum</LI></UL></LI><LI>Something I do not understand in the documentation. That look controdictory for me about the provision of new workloads. Thanks to clarify<UL><LI>Page 6: Standard capacities: Automatic provisioning per the storage service level by using APIs</LI><LI>Page 9: Configuring new workloads for using storage service levels (SSLs) and service level objective-based (SLO-based) APIs involves enabling the SLO advanced license</LI><LI>in my understanding "configuring new workload" means "provisioning new workload" but maybe I am worng</LI></UL></LI></UL><P>&nbsp;</P><P>Thanks in advance for your patience</P><P>Regards</P><P>Christian</P> Wed, 04 Jun 2025 14:35:00 GMT https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Lots-of-question-about-Service-Level-Manager/m-p/134636#M24436 christig 2025-06-04T14:35:00Z