-
Notifications
You must be signed in to change notification settings - Fork 107
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
Introduce deploy-centralvm.sh #10014
Conversation
Jenkins results:
|
2ff4e63
to
a13fd35
Compare
Jenkins results:
|
Jenkins results:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't have an opportunity to test it yet, but it looks fine. Thanks Todor.
Actually, @todor-ivanov please squash those commits. |
Add initial parameters verification. Fix Help function. Fix Help function.
11eb768
to
47d8ab6
Compare
Thanks @amaltaro. I just squashed them. |
Jenkins results:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
Fixes #10013
Status
ready
Description
This is supposed to be used for automated central services deployment in a VM, similarly to the
deploy-wmagent.sh
script. Mostly for development purposes. In case we find it useful we may use the same strategy for automation of the process of personal deployment and development when we are done with the migration Kubernetes. This one basically follows the instructions provided here [2][1]
https://github.com/dmwm/WMCore/blob/master/deploy/deploy-wmagent.sh
[2]
https://github.com/dmwm/WMCore/wiki/Deploy-central-services-in-a-VM
Is it backward compatible (if not, which system it affects?)
YES
Related PRs
NO
External dependencies / deployment changes
<Does it require deployment changes? Does it rely on third-party libraries?>