Backing up your VM: Difference between revisions

No edit summary
Line 8: Line 8:


==Setup automation==
==Setup automation==
Provisioning tools such as [https://www.ansible.com/ ansible], [https://puppet.com/ puppet], [https://www.chef.io/ chef], and [https://saltstack.com/ saltstack] can be used to automate setup and configuration of software and operating systems. Recreating your virtual machine then becomes a trivial matter given specification files. These specification files can be managed with version control tools like [https://git-scm.com/ git]. Provisioning tools can be combined with orchestration tools such as heat and terraform (see [[Automating VM creation]]) to automate the entire process of virtual machine creation and software configuration. Any data which is generated or created outside this automation would then need to be backed up likely using a [[#File backup| file backup]] method.
Provisioning tools such as [https://www.ansible.com/ ansible], [https://puppet.com/ puppet], [https://www.chef.io/ chef], and [https://saltstack.com/ saltstack] can be used to automate setup and configuration of software and operating systems. Recreating your virtual machine then becomes a trivial matter given the right specification files for a given provisioning tool. These specification files can be managed with version control tools like [https://git-scm.com/ git]. Provisioning tools can be combined with orchestration tools such as heat and terraform (see [[Automating VM creation]]) to automate the entire process of virtual machine creation and software configuration. Any data which is generated or created outside this automation would then need to be backed up using one of the [[#File backup| file backup]] methods.


==OpenStack specific==
==OpenStack specific==
Bureaucrats, cc_docs_admin, cc_staff
2,306

edits