Skip to content

Commit e5682f8

Browse files
committed
DOC-034: Rename section title 'virtual machine software' to 'software related to virtual machines' to remove ambiguity with simulation software, and activate Ansible and Vagrant URLs.
1 parent e9f6670 commit e5682f8

File tree

1 file changed

+15
-14
lines changed

1 file changed

+15
-14
lines changed

docs/virtual-machine-software.rst

Lines changed: 15 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,8 @@ single files representing the equivalent of a hard disk of the machine, as well
2323
as a description of the hardware that the virtual machine emulates. This makes
2424
them simple to distribute.
2525

26-
Virtual Machine Software
27-
------------------------
26+
Software Related to Virtual Machines
27+
------------------------------------
2828

2929
Virtual machines must be supported by software in order to function. Only
3030
provider software is necessary to run a virtual machine, but managers and
@@ -52,14 +52,14 @@ Managers
5252

5353
While not essential for starting :term:`virtual machine`\s, specialist software
5454
is useful for managing :term:`virtual environment`\s. Vagrant
55-
(www.vagrantup.com) is an example of a virtual machine manager. It provides a
56-
command-line interface to the creation and provision of virtual machines from
57-
virtual environments. HashiCorp, the company behind Vagrant, also provides a
58-
framework for sharing virtual environments. Most importantly for our purpose,
59-
Vagrant can be automated to generate virtual machines containing an environment
60-
without user intervention. This environment can then be used to complete our
61-
objectives. To specify this environment however, provisioning software is
62-
required.
55+
(https://www.vagrantup.com) is an example of a virtual machine manager. It
56+
provides a command-line interface to the creation and provision of virtual
57+
machines from virtual environments. HashiCorp, the company behind Vagrant, also
58+
provides a framework for sharing virtual environments. Most importantly for our
59+
purpose, Vagrant can be automated to generate virtual machines containing an
60+
environment without user intervention. This environment can then be used to
61+
complete our objectives. To specify this environment however, provisioning
62+
software is required.
6363

6464
.. _software-provisioners:
6565

@@ -73,10 +73,11 @@ provisioner describes the desired state of the system, and the provisioner
7373
makes it so. In the absence of a provisioner, shell commands can be executed to
7474
specify the state, but this becomes unwieldy for large projects because focus
7575
is placed on the instructions needed to obtain the desired state, as opposed to
76-
the state itself. Provisioning software, such as Ansible (www.ansible.com)
77-
alleviates this problem. Ansible uses Yet Another Markup Language (YAML) to
78-
describe plays to run on a machine to enact the desired end state. Since the
79-
focus is on the end state of the system, :term:`idempotency` is essential.
76+
the state itself. Provisioning software, such as Ansible
77+
(https://www.ansible.com) alleviates this problem. Ansible uses Yet Another
78+
Markup Language (YAML) to describe plays to run on a machine to enact the
79+
desired end state. Since the focus is on the end state of the system,
80+
:term:`idempotency` is essential.
8081

8182
.. _software-summary:
8283

0 commit comments

Comments
 (0)