cc_staff
10
edits
Automating VM creation: Difference between revisions
Jump to navigation
Jump to search
no edit summary
m (Fix typo) |
No edit summary |
||
| Line 6: | Line 6: | ||
<!--T:2--> | <!--T:2--> | ||
The below virtual machine (VM) setup files are intended to be used to quickly create VMs and clusters of VMs. The files come in two forms, [https://wiki.openstack.org/wiki/Heat Heat] templates, and [https://cloudinit.readthedocs.io/en/latest/ CloudInit] files; both use the [https://en.wikipedia.org/wiki/YAML YAML] file format. CloudInit files are used to initialize a particular VM and run within that VM. They can be thought of as a way to automate tasks you would perform at the command line while logged into your VM. They can be used to perform tasks such as updating the operating system, installing and configuring applications, creating files, running commands, and create users and groups. Heat templates are even more powerful, they can be used to automate tasks performed in the OpenStack dashboard such as creating multiple VMs at once, configuring security groups, creating and configuring networks, and creating and attaching volumes to VMs. Heat templates can be used in conjunction with CloudInit files, once Heat has created the VM it can pass a cloudInit file to that VM to perform setup tasks and even include information about other resources dynamically in the CloudInit files (e.g. floating IPs of other VMs). | The below virtual machine (VM) setup files are intended to be used to quickly create VMs and clusters of VMs. The files come in two forms, [https://wiki.openstack.org/wiki/Heat Heat] templates, and [https://cloudinit.readthedocs.io/en/latest/ CloudInit] files; both use the [https://en.wikipedia.org/wiki/YAML YAML] file format. CloudInit files are used to initialize a particular VM and run within that VM. They can be thought of as a way to automate tasks you would perform at the command line while logged into your VM. They can be used to perform tasks such as updating the operating system, installing and configuring applications, creating files, running commands, and create users and groups. Heat templates are even more powerful, they can be used to automate tasks performed in the OpenStack dashboard such as creating multiple VMs at once, configuring security groups, creating and configuring networks, and creating and attaching volumes to VMs. Heat templates can be used in conjunction with CloudInit files, once Heat has created the VM it can pass a cloudInit file to that VM to perform setup tasks and even include information about other resources dynamically in the CloudInit files (e.g. floating IPs of other VMs). | ||
==Enabling CVMFS on your VM== <!--T:3--> | |||
CVMFS is a CERNVM based file system that provides a scalable, reliable, and low maintenance research software distribution service. At the client end, users just need to mount CVMFS and to use software or libraries directly without worrying about compiling, building, or patching. All the software are compiled for common OS flavors and even modulized so that users can simply load it as a module. | |||
CVMFS has been installed on Compute Canada cluster systems such as Cedar, Graham, Beluga. While on cloud systems, users need to enable it by hand. Here is the instruction: [https://github.com/ComputeCanada/cvmfs/tree/main/cvmfs_on_cloud CVMFS On Cloud]. | |||
==Using CloudInit== <!--T:3--> | ==Using CloudInit== <!--T:3--> | ||