Hello Jordan ACS has three global configurations for defining system VM offerings: - consoleproxy.service.offering - secstorage.service.offering - router.service.offering
For console and secondary storage system VMs, those configurations are global, meaning that the offering defined there will be used by both zones. As far as I look at the code, there is no way yet to define an offering per zone for console or secondary storage system VM. For VRs, when you create a network or VPC, you can define a service offering of type 'domainrouter'. ACS first tries to use the service offering defined in the network/VPC offering. If it is not defined, then ACS will derive from the configuration 'router.service.offering', which is account scoped. Best regards, Sadi On 12/19/22 11:11, jordan j wrote:
Dear everyone, Is there any way to specify SVM offerings to be used by a zone for Console, Storage and VR system VMs? I could not find anything in Zone -> settings. The only available option is at Global settings - router.template.xen where VR offering can be defined but that will be applied for all zones. Here is the use case: ACS 4.17.2 with 2 zones. Each zone has 2 clusters. - zone 1 - cluster1 with tag infraA; cluster 2 with tag infraB - zone 2 - cluster1 with tag infraC; cluster 2 with tag infraD SSVM offerings for each zone should have different host tags to sit on the zone cluster 1. They can also have different parameters based on zone demand. If assignment of new SSVM offerings is not possible then why such can be created? Regards, Jordan
