forked from jprorama/CRI_XCBC
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Celery service #1
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The install file is over 75MB and incurs a significant transfer overhead during the initialization of the ansible environments when used with a provisioning framework like vagrant which stages ansible on the target node. This install file should likely be downloaded from an online source.
The default user aligns with the conventions of the image provisioning framework. For the centos cloud image that user name is "centos".
The internal network nic for the head node relies on static IP address assignement. Explicitly assign the IP address via so NetworkManager doesn't default to requesting an IP address via DHCP and causing the eth1 interface to pend configuration idefinitly. Without eth1 all communication with the head node on the cluster network will fail, e.g. sacctmgr setup.
…-openstack Corrects master internal IP set in /etc/hosts from a static value in config to the actual assigned value for the interface.
For packer to build compute image
Now support 10 compute nodes: c0 to c9
The two files added here come from compute_build_nodes and nodes_vivify roles. These two new files will be modified for suitable cloud operations.
The home dir would not mount on OOD if we did not disable the firewalld in OHPC, it was working in our previous setup while deploying in vagrant as the VBox VM was running and was never turned off during the setup, but in the cloud deploy we have to preserve the state we have in the build phase (i.e. after packer builds the image). We need to disable it so it would not get turned back on after we boot the image during deploy
We dont use DHCP broadcasts for auto node discovery so we set this flag to false.
In cloud deploy PXE boot is no longer required so those tasks are removed.
we don't use DHCP broadcast for node discovery, so we remove the wwnodescan task and DHCP restart task.
* Specify the full paht for git repo to be installed in * Changing the pattern for what to find and change * Using shell script to start ood_account_create in background
…-error Patch fix easybuild error
It seems this was inherited from earlier use on ood. Firewall should be off by default on ohpc as currently deployed in dev. We should figure out the ports needed.
Installing rabbitmq-server on ohpc node
Add rabbitmq agents as service
python pip version update for Flask User reg app
Change the config file to ProxyPass the request to uwsgi
Tell ansible to use venv module provided by python3
wsgi file tell uwsgi which app to run ini file config uwsgi service file create system service that runs uwsgi
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.