RosiKyu commented on PR #10957: URL: https://github.com/apache/cloudstack/pull/10957#issuecomment-3801676752
> Hey @RosiKyu, thanks for your tests! I would just like to point out that the JS interpreter is not working as intended at the current moment (see #12515). Hence, selectors that choose a secondary storage based on information about the volume/account/domain/existing secondary storages will not work as expected. > > You can, however, test this PR by using a simple rule that directs all volumes to a specific secondary storage, for instance: > > ```shell > (admin) 🐱 > create secondarystorageselector name="direct volumes to secondary storage X" description="directs volumes to secondary storage X" zoneid=13b319e9-108c-4925-96aa-ae556d9a11b2 heuristicrule="'<uuid-of-secondary-storage-X>'" type=VOLUME > ``` > > With this selector, all volumes will pass through secondary storage X during cold migration. Thanks @winterhazel for the clarification! I was hitting exactly that issue - when enabling `js.interpretation.enabled=true` on the current 4.20 branch (required for createSecondaryStorageSelector API), the management server hangs during startup at the module loading phase. Have logged it here, before seeing your comment: https://github.com/apache/cloudstack/issues/12523 Good to know PR #12515 addresses this. I'll proceed with testing PR #10957 using the simple rule workaround you suggested: -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
