Skip to content
Snippets Groups Projects

Compare revisions

Changes are shown as if the source revision was being merged into the target revision. Learn more about comparing revisions.

Source

Select target project
No results found

Target

Select target project
  • tr27p/ohpc_vagrant
  • jpr/ohpc_vagrant
  • louistw/ohpc_vagrant
  • krish94/ohpc_vagrant
  • mmoo97/ohpc_vagrant
  • chirag24/ohpc_vagrant
  • noe121/ohpc_vagrant
  • ishan747/ohpc_vagrant
  • alansill/ohpc_vagrant
  • atlurie/ohpc_vagrant
  • rrand11/ohpc_vagrant
11 results
Show changes
Commits on Source (19)
[submodule "CRI_XCBC"]
path = CRI_XCBC
url = git@github.com:jprorama/CRI_XCBC.git
url = https://github.com/jprorama/CRI_XCBC.git
Subproject commit 78c14f733aef0f288b7e6298096e862322a7eaf0
Subproject commit ce62e52ee2c03a9db4e60b256c73dee3f99a7715
......@@ -29,6 +29,11 @@ cluster with vagrant:
vagrant up ohpc
```
NOTE: After you run the above command if you were to get a `"kernel mismatch error"`. To get past this error please run:
`vagrant ssh ohpc -c "uname -r"`.
Copy and paste this kernel version in the group_vars/all to update the kernel version in the `build_kernel_ver` variable.
The ansible config will bring the master node to the point where its
ready to ingest compute nodes via wwnodescan and prompt to you
start a compute node. You can create a compute node and start it with
......@@ -87,12 +92,17 @@ with Open OnDemand. After the cluster is up boot the ood node with:
vagrant up ood
```
This will provision the node and near the end of the provisioning provide several
This will provision the node.
NOTE: Near the end of the ood provisioning, the ansible scripts will display several
sudo commands that need to be run on the ohpc node to register the ood node
with the cluster, ensuring data synchronization and slurm work.
with the cluster. The commands ensure system file synchronization and slurm work.
You will need to copy and paste these sudo commands to a shell in ohpc. The
ansible script will pause for 90 seconds to give you time to do this.
After the node is provisioned (or booted) you need to work around mount issue
with NFS mounts and issue the `mount -a` command on the ood node:
After the node is provisioned (or booted) you need to work around a mount issue
with NFS mounts in the centos/7 vagrant box and issue the `mount -a` command
on the ood node:
```
vagrant ssh ood -c "sudo mount -a"
```
......@@ -100,6 +110,15 @@ vagrant ssh ood -c "sudo mount -a"
After this point you can connect to the web ui of the ood node, typically via
(the port mapping may change in your local vagrant env):
http://localhost/8080
http://localhost:8080
The default user name and password for the web UI is 'vagrant'.
## Issues and Work arounds
If you encounter an issue with OHPC node provisioning due to GPG key errors as mentioned in https://github.com/jprorama/CRI_XCBC/issues/77. Please run the following command:
```
vagrant box update
```
If you encounter an issue with nodes_vivify role in updating the slurm status on nodes, specifically the error `slurm_update error: Invalid node state specified`. Please increase the compute node memory. For example if you're using 4GB already increase the memory to 6GB in your Virtual Box.
......@@ -17,7 +17,7 @@ fi
# Download the ipxe.iso boot image if it doesn't already exist
if [[ ! -f "$HOME/iso/ipxe.iso" ]]; then
echo "Downloading the network boot ipxe.iso file"
crul -o ~/iso/ipxe.iso http://boot.ipxe.org/ipxe.iso
curl -o ~/iso/ipxe.iso http://boot.ipxe.org/ipxe.iso
fi
VBoxManage createvm --name "$nodename" --register
......