warewulf_worker_node_images
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
warewulf_worker_node_images [2020/06/26 20:54] deadline created |
warewulf_worker_node_images [2021/05/20 17:18] (current) brandonm [Updating Limulus Node VNFS Images] Word, spelling, formatting, hyphenation, and phrasing fixes |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| =====Warewulf Worker Node Images===== | =====Warewulf Worker Node Images===== | ||
| - | All Limulus HPC system | + | All Limulus HPC systems |
| Note: Data Analytics systems use [[https:// | Note: Data Analytics systems use [[https:// | ||
| Line 7: | Line 7: | ||
| ====Using Warewulf (Quick Start)==== | ====Using Warewulf (Quick Start)==== | ||
| - | Managing | + | Under normal circumstances, |
| - | - **File System Images** - Each worker node is provided a RAM disk file system image. This image contains all the " | + | - **File System Images** - Each worker node is provided a RAM disk file system image. This image contains all the " |
| - | - **Boostrap Kernel** - a kernel image that used to start the worker node. This image usually contains the same kernel version as the main node, but it is not required. | + | - **Boostrap Kernel** - A kernel image used to start the worker node. This image usually contains the same kernel version as the main node, but it is not required |
| - | - **Files** - these are generally configuration files that are maintained on the main node and sent to worker nodes when booting and then periodically as the node runs (if Warewulf notes any changes in the files). These files can be the same as the ones used on the head node or they can be specific to the worker nodes. | + | - **Files** - These are generally configuration files that are maintained on the main node and sent to worker nodes when booting and then periodically as the node runs (if Warewulf notes any changes in the files). These files can be the same as the ones used on the headnode, |
| - | VNF images, bootstrap kernels,and files can all be loaded into the Warewulf database. See the "Modifying Limulus VNFS, Bootstrap, and System Files" | + | VNFS images, bootstrap kernels, and files can all be loaded into the Warewulf database. See the [[warewulf_worker_node_images# |
| - | To view the installed **VNFS Images** use the '' | + | To view the installed **VNFS Images**, use the '' |
| - | * you start an Warewuf | + | * You can start a Warewulf |
| - | * incomplete command | + | * Incomplete arguments |
| < | < | ||
| Line 28: | Line 28: | ||
| This example shows two VNFS images, // | This example shows two VNFS images, // | ||
| - | Similarly the available **bootstrap kernels** can be listed as follows. | + | Similarly, the available **bootstrap kernels** can be listed as follows. |
| < | < | ||
| Line 36: | Line 36: | ||
| </ | </ | ||
| - | **Node specific files** can be delivered to the nodes at boot time. The '' | + | **Node-specific files** can be delivered to the nodes at boot time. The '' |
| < | < | ||
| Line 53: | Line 53: | ||
| </ | </ | ||
| - | The **node provisioning** can be viewed using the '' | + | The **node provisioning** can be viewed using the '' |
| < | < | ||
| Line 64: | Line 64: | ||
| </ | </ | ||
| - | A much longer and detailed listing can be generated by using '' | + | A much longer and detailed |
| < | < | ||
| Line 75: | Line 75: | ||
| </ | </ | ||
| - | The '' | + | The '' |
| ====Updating Limulus Node VNFS Images==== | ====Updating Limulus Node VNFS Images==== | ||
| - | Limulus Computing provides Warewulf node images in an RPM package. These are easily installed and manages | + | Limulus Computing provides Warewulf node images in an RPM package. These are easily installed and managed |
| As configured, Limulus HPC systems have a basic node image that can be used to run the worker nodes. | As configured, Limulus HPC systems have a basic node image that can be used to run the worker nodes. | ||
| - | Form time to time Limulus Computing may update the Warewulf images. These can be installed by | + | From time to time Limulus Computing may update the Warewulf images. These can be installed by |
| - | first deleting the existing | + | first deleting the existing |
| (Note: the update can take several minutes). | (Note: the update can take several minutes). | ||
| < | < | ||
| - | rpm -e vnfs-co7_base | + | # rpm -e vnfs-co7_base |
| - | </ | + | |
| - | + | ||
| - | < | + | |
| # yum install vnfs-co7_base | # yum install vnfs-co7_base | ||
| Loaded plugins: fastestmirror, | Loaded plugins: fastestmirror, | ||
| Line 98: | Line 94: | ||
| </ | </ | ||
| - | The next step is to assign the new VNFS to the worker nodes. Assuming the new VNFS installed properly, the <tt>wwsh provision</ | + | The next step is to assign the new VNFS to the worker nodes. Assuming the new VNFS installed properly, the '' |
| < | < | ||
| Line 109: | Line 105: | ||
| </ | </ | ||
| - | The current node provisioning can be checked by using the " | + | The current node provisioning can be checked by using the " |
| < | < | ||
| Line 120: | Line 116: | ||
| </ | </ | ||
| - | The system should be ready to reuse the new images when the nodes are rebooted. To reboot all the nodes enter: | + | The system should be ready to use the new images when the nodes are rebooted. To reboot all nodes enter: |
| < | < | ||
| - | pdsh reboot | + | # pdsh reboot |
| </ | </ | ||
| - | After a few minutes the nodes should be up and runing | + | After a few minutes the nodes should be up and running |
| ====Updating Limulus Node Bootstrap Images==== | ====Updating Limulus Node Bootstrap Images==== | ||
warewulf_worker_node_images.1593204879.txt.gz · Last modified: 2020/06/26 20:54 by deadline
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
