Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to restart two CAS controller with Viya-ark ? #99

Open
nhousset opened this issue Jul 19, 2023 · 1 comment
Open

How to restart two CAS controller with Viya-ark ? #99

nhousset opened this issue Jul 19, 2023 · 1 comment

Comments

@nhousset
Copy link

Hello,

We have an VIYA 3.5 environment 2two CAS controller (the first with 5 workers and the second with 3) and we would like to know if viya-ark supports this type of configuration.
Today, we have two inventory.ini files, one initial with all the machine definitions and groups, and a second with the second controller case and workers (this is the file used when deploying the second CAS controller ).

What's the best way to stop/start/resart all the process via viya-ark in this type of configuration?
Will it work to merge the two inventories, for stop/relaunch only?
Or, should you still use a second inventory, but remove the httpproxy definition, for example, to avoid the stop/relaunch of the second case controller stopping the http proxy on the MS server?

Thanks in advance for your suggestions.

Nicolas Housset

@erharb
Copy link
Member

erharb commented Jul 19, 2023

The viya-mmsu tool only acts upon a single inventory.ini at a time, most likely it should work just fine on the separated inventory.ini by running it once on each in the correct order. However, if you wish to create custom merged inventory just for the purposes of managing the services with viya-mmsu (and customized to omit httpproxy) then that could be a good idea as well as long as you don't attempt to run deployment operations using that custom inventory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants