Update documentation based on 301 permanent redirects (#43675)
This commit is contained in:
Andreas Olsson
Alicia Cozine
parent
b0542217e2
commit
00e5123e4c
25 changed files with 43 additions and 43 deletions
|
|
@ -70,6 +70,6 @@ participate. For more information about Ansible meetings, consult the `meeting s
|
|||
Tower Support Questions
|
||||
========================
|
||||
|
||||
Ansible `Tower <https://ansible.com/tower>`_ is a UI, Server, and REST endpoint for Ansible.
|
||||
Ansible `Tower <https://www.ansible.com/products/tower>`_ is a UI, Server, and REST endpoint for Ansible.
|
||||
|
||||
If you have a question about Ansible Tower, visit `Red Hat support <https://access.redhat.com/products/ansible-tower-red-hat/>`_ rather than using the IRC channel or the general project mailing list.
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ A great way to help the Ansible project is to become a power user:
|
|||
* Take tutorials and classes
|
||||
* Read the :ref:`official documentation <ansible_documentation>`
|
||||
* Study some of the `many excellent books <https://www.amazon.com/s/ref=nb_sb_ss_c_2_7?url=search-alias%3Dstripbooks&field-keywords=ansible&sprefix=ansible%2Caps%2C260>`_ about Ansible
|
||||
* `Get certified <https://www.ansible.com/training-certification>`_.
|
||||
* `Get certified <https://www.ansible.com/products/training-certification>`_.
|
||||
|
||||
When you become a power user, your ability and opportunities to help the Ansible project in other ways will multiply quickly.
|
||||
|
||||
|
|
@ -32,7 +32,7 @@ Participate in your local meetup
|
|||
|
||||
There are Ansible meetups `all over the world <https://www.meetup.com/topics/ansible/>`_. Join your local meetup. Attend regularly. Ask good questions. Volunteer to give a presentation about how you use Ansible.
|
||||
|
||||
If there isn't a meetup near you, we'll be happy to help you `start one <https://www.ansible.com/ansible-meetup-organizer>`_.
|
||||
If there isn't a meetup near you, we'll be happy to help you `start one <https://www.ansible.com/community/events/ansible-meetups>`_.
|
||||
|
||||
File and verify issues
|
||||
----------------------
|
||||
|
|
@ -47,7 +47,7 @@ Review and submit pull requests
|
|||
|
||||
As you become more familiar with how Ansible works, you may be able to fix issues or develop new features yourself. If you think you've got a solution to a bug you've found in Ansible, or if you've got a new feature that you've written and would like to share with millions of Ansible users, read all about the :ref:`Ansible development process <community_development_process>` to learn how to get your code accepted into Ansible.
|
||||
|
||||
Another good way to help is to review pull requests that other Ansible users have submitted. The Ansible community keeps a full list of `open pull requests by file <https://ansible.sivel.net/byfile.html>`_, so if there's a particular module or plug-in that particularly interests you, you can easily keep track of all the relevant new pull requests and provide testing or feedback.
|
||||
Another good way to help is to review pull requests that other Ansible users have submitted. The Ansible community keeps a full list of `open pull requests by file <https://ansible.sivel.net/pr/byfile.html>`_, so if there's a particular module or plug-in that particularly interests you, you can easily keep track of all the relevant new pull requests and provide testing or feedback.
|
||||
|
||||
Become a module maintainer
|
||||
--------------------------
|
||||
|
|
|
|||
|
|
@ -342,7 +342,7 @@ An easy way to see how this should look is using :ref:`ansible-inventory`, which
|
|||
How to develop modules
|
||||
:doc:`developing_plugins`
|
||||
How to develop plugins
|
||||
`Ansible Tower <https://ansible.com/ansible-tower>`_
|
||||
`Ansible Tower <https://www.ansible.com/products/tower>`_
|
||||
REST API endpoint and GUI for Ansible, syncs with dynamic inventory
|
||||
`Development Mailing List <https://groups.google.com/group/ansible-devel>`_
|
||||
Mailing list for development topics
|
||||
|
|
|
|||
|
|
@ -417,7 +417,7 @@ Example usage::
|
|||
See also M(win_copy) or M(win_template).
|
||||
...
|
||||
Time zone names are from the L(tz database,https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)
|
||||
See U(https://www.ansible.com/tower) for an overview.
|
||||
See U(https://www.ansible.com/products/tower) for an overview.
|
||||
...
|
||||
See L(IOS Platform Options guide, ../network/user_guide/platform_ios.html)
|
||||
|
||||
|
|
|
|||
|
|
@ -336,7 +336,7 @@ the most popular are
|
|||
- `Powershell ISE`_
|
||||
- `Visual Studio Code`_
|
||||
|
||||
.. _Powershell ISE: https://msdn.microsoft.com/en-us/powershell/scripting/core-powershell/ise/how-to-debug-scripts-in-windows-powershell-ise
|
||||
.. _Powershell ISE: https://docs.microsoft.com/en-us/powershell/scripting/core-powershell/ise/how-to-debug-scripts-in-windows-powershell-ise
|
||||
.. _Visual Studio Code: https://blogs.technet.microsoft.com/heyscriptingguy/2017/02/06/debugging-powershell-script-in-visual-studio-code-part-1/
|
||||
|
||||
To be able to view the arguments as passed by Ansible to the module follow
|
||||
|
|
|
|||
|
|
@ -553,7 +553,7 @@ the code in Ansible to trigger that failure.
|
|||
The documentation of pytest - the framework actually used to run Ansible unit tests
|
||||
`Development Mailing List <https://groups.google.com/group/ansible-devel>`_
|
||||
Mailing list for development topics
|
||||
`Testing Your Code (from The Hitchhiker's Guide to Python!) <https://docs.python-guide.org/en/latest/writing/tests/>`_
|
||||
`Testing Your Code (from The Hitchhiker's Guide to Python!) <https://docs.python-guide.org/writing/tests/>`_
|
||||
General advice on testing Python code
|
||||
`Uncle Bob's many videos on YouTube <https://www.youtube.com/watch?v=QedpQjxBPMA&list=PLlu0CT-JnSasQzGrGzddSczJQQU7295D2>`_
|
||||
Unit testing is a part of the of various philosophies of software development, including
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ as a ".rpmnew" file (or other) as appropriate in the case of updates.
|
|||
If you installed Ansible from pip or from source, you may want to create this file in order to override
|
||||
default settings in Ansible.
|
||||
|
||||
An `example file is available on Github <https://raw.github.com/ansible/ansible/devel/examples/ansible.cfg>`_.
|
||||
An `example file is available on Github <https://raw.githubusercontent.com/ansible/ansible/devel/examples/ansible.cfg>`_.
|
||||
|
||||
For more details and a full listing of available configurations go to :ref:`configuration_settings<ansible_configuration_settings>`. Starting with Ansible version 2.4, you can use the :ref:`ansible-config` command line utility to list your available options and inspect the current values.
|
||||
|
||||
|
|
|
|||
|
|
@ -139,7 +139,7 @@ You can also build an RPM yourself. From the root of a checkout or tarball, use
|
|||
Latest Releases Via Apt (Ubuntu)
|
||||
++++++++++++++++++++++++++++++++
|
||||
|
||||
Ubuntu builds are available `in a PPA here <https://launchpad.net/~ansible/+archive/ansible>`_.
|
||||
Ubuntu builds are available `in a PPA here <https://launchpad.net/~ansible/+archive/ubuntu/ansible>`_.
|
||||
|
||||
To configure the PPA on your machine and install ansible run these commands:
|
||||
|
||||
|
|
|
|||
|
|
@ -49,8 +49,8 @@ Text
|
|||
|
||||
Read more about Ansible for Network Automation:
|
||||
|
||||
- Network Automation on the `Ansible website <https://ansible.com/overview/networking>`_
|
||||
- Ansible Network `Blog posts <https://ansible.com/blog/topic/networks>`_
|
||||
- Network Automation on the `Ansible website <https://www.ansible.com/overview/networking>`_
|
||||
- Ansible Network `Blog posts <https://www.ansible.com/blog/topic/networks>`_
|
||||
|
||||
Events (on Video and in Person)
|
||||
--------------------------------
|
||||
|
|
|
|||
|
|
@ -467,9 +467,9 @@ Also array notation allows for dynamic variable composition, see dynamic_variabl
|
|||
Can I get training on Ansible?
|
||||
++++++++++++++++++++++++++++++
|
||||
|
||||
Yes! See our `services page <https://www.ansible.com/consulting>`_ for information on our services and training offerings. Email `info@ansible.com <mailto:info@ansible.com>`_ for further details.
|
||||
Yes! See our `services page <https://www.ansible.com/products/consulting>`_ for information on our services and training offerings. Email `info@ansible.com <mailto:info@ansible.com>`_ for further details.
|
||||
|
||||
We also offer free web-based training classes on a regular basis. See our `webinar page <https://www.ansible.com/webinars-training>`_ for more info on upcoming webinars.
|
||||
We also offer free web-based training classes on a regular basis. See our `webinar page <https://www.ansible.com/resources/webinars-training>`_ for more info on upcoming webinars.
|
||||
|
||||
|
||||
.. _web_interface:
|
||||
|
|
|
|||
|
|
@ -3,10 +3,10 @@
|
|||
Ansible Tower
|
||||
=============
|
||||
|
||||
`Ansible Tower <https://ansible.com/tower>`_ (formerly 'AWX') is a web-based solution that makes Ansible even more easy to use for IT teams of all kinds. It's designed to be the hub for all of your automation tasks.
|
||||
`Ansible Tower <https://www.ansible.com/products/tower>`_ (formerly 'AWX') is a web-based solution that makes Ansible even more easy to use for IT teams of all kinds. It's designed to be the hub for all of your automation tasks.
|
||||
|
||||
Tower allows you to control access to who can access what, even allowing sharing of SSH credentials without someone being able to transfer those credentials. Inventory can be graphically managed or synced with a wide variety of cloud sources. It logs all of your jobs, integrates well with LDAP, and has an amazing browsable REST API. Command line tools are available for easy integration with Jenkins as well. Provisioning callbacks provide great support for autoscaling topologies.
|
||||
|
||||
Find out more about Tower features and how to download it on the `Ansible Tower webpage <https://ansible.com/tower>`_. Tower
|
||||
Find out more about Tower features and how to download it on the `Ansible Tower webpage <https://www.ansible.com/products/tower>`_. Tower
|
||||
is free for usage for up to 10 nodes, and comes bundled with amazing support from Ansible, Inc. As you would expect, Tower is
|
||||
installed using Ansible playbooks!
|
||||
|
|
|
|||
|
|
@ -163,4 +163,4 @@ ansible-ssh
|
|||
|
||||
- https://github.com/2ndQuadrant/ansible-ssh
|
||||
- https://github.com/haad/ansible-ssh
|
||||
- https://github.com/mlvnd/ansible-ssh
|
||||
- https://github.com/mlvnd/ansible-tools
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ instructions on how to actually use the modules and authenticate with the Azure
|
|||
Using Service Principal
|
||||
.......................
|
||||
|
||||
There is now a detailed official tutorial describing `how to create a service principal <https://azure.microsoft.com/en-us/documentation/articles/resource-group-create-service-principal-portal/>`_.
|
||||
There is now a detailed official tutorial describing `how to create a service principal <https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal>`_.
|
||||
|
||||
After stepping through the tutorial you will have:
|
||||
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@ Still using Dockerfile to build images? Check out `ansible-container <https://gi
|
|||
and start building images from your Ansible playbooks.
|
||||
|
||||
Use the *shipit* command in `ansible-container <https://github.com/ansible/ansible-container>`_
|
||||
to launch your docker-compose file on `OpenShift <https://www.openshift.org/>`_. Go from an app on your laptop to a fully
|
||||
to launch your docker-compose file on `OpenShift <https://www.okd.io/>`_. Go from an app on your laptop to a fully
|
||||
scalable app in the cloud in just a few moments.
|
||||
|
||||
There's more planned. See the latest ideas and thinking at the `Ansible proposal repo <https://github.com/ansible/proposals/tree/master/docker>`_.
|
||||
|
|
|
|||
|
|
@ -58,7 +58,7 @@ Setting the environment parameter RAX_CREDS_FILE to the path of this file will h
|
|||
this information.
|
||||
|
||||
More information about this credentials file can be found at
|
||||
https://github.com/rackspace/pyrax/blob/master/docs/getting_started.md#authenticating
|
||||
https://github.com/pycontribs/pyrax/blob/master/docs/getting_started.md#authenticating
|
||||
|
||||
|
||||
.. _virtual_environment:
|
||||
|
|
|
|||
|
|
@ -278,7 +278,7 @@ For other load balancers, you may need to send shell commands to them (like we d
|
|||
Continuous Delivery End-To-End
|
||||
``````````````````````````````
|
||||
|
||||
Now that you have an automated way to deploy updates to your application, how do you tie it all together? A lot of organizations use a continuous integration tool like `Jenkins <http://jenkins-ci.org/>`_ or `Atlassian Bamboo <https://www.atlassian.com/software/bamboo>`_ to tie the development, test, release, and deploy steps together. You may also want to use a tool like `Gerrit <https://code.google.com/p/gerrit/>`_ to add a code review step to commits to either the application code itself, or to your Ansible playbooks, or both.
|
||||
Now that you have an automated way to deploy updates to your application, how do you tie it all together? A lot of organizations use a continuous integration tool like `Jenkins <https://jenkins.io/>`_ or `Atlassian Bamboo <https://www.atlassian.com/software/bamboo>`_ to tie the development, test, release, and deploy steps together. You may also want to use a tool like `Gerrit <https://www.gerritcodereview.com/>`_ to add a code review step to commits to either the application code itself, or to your Ansible playbooks, or both.
|
||||
|
||||
Depending on your environment, you might be deploying continuously to a test environment, running an integration test battery against that environment, and then deploying automatically into production. Or you could keep it simple and just use the rolling-update for on-demand deployment into test or production specifically. This is all up to you.
|
||||
|
||||
|
|
@ -296,7 +296,7 @@ This should give you a good idea of how to structure a multi-tier application wi
|
|||
An introduction to playbook roles
|
||||
:ref:`playbooks_variables`
|
||||
An introduction to Ansible variables
|
||||
`Ansible.com: Continuous Delivery <https://www.ansible.com/ansible-continuous-delivery>`_
|
||||
`Ansible.com: Continuous Delivery <https://www.ansible.com/use-cases/continuous-delivery>`_
|
||||
An introduction to Continuous Delivery with Ansible
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ Using Vagrant and Ansible
|
|||
Introduction
|
||||
````````````
|
||||
|
||||
`Vagrant <https://vagrantup.com/>`_ is a tool to manage virtual machine
|
||||
`Vagrant <https://www.vagrantup.com/>`_ is a tool to manage virtual machine
|
||||
environments, and allows you to configure and use reproducible work
|
||||
environments on top of various virtualization and cloud platforms.
|
||||
It also has integration with Ansible as a provisioner for these virtual
|
||||
|
|
@ -15,7 +15,7 @@ machines, and the two tools work together well.
|
|||
This guide will describe how to use Vagrant 1.7+ and Ansible together.
|
||||
|
||||
If you're not familiar with Vagrant, you should visit `the documentation
|
||||
<https://docs.vagrantup.com/v2/>`_.
|
||||
<https://www.vagrantup.com/docs/>`_.
|
||||
|
||||
This guide assumes that you already have Ansible installed and working.
|
||||
Running from a Git checkout is fine. Follow the :ref:`installation_guide`
|
||||
|
|
@ -44,7 +44,7 @@ Ansible provisioner to manage a single machine:
|
|||
|
||||
# Disable the new default behavior introduced in Vagrant 1.7, to
|
||||
# ensure that all Vagrant machines will use the same SSH key pair.
|
||||
# See https://github.com/mitchellh/vagrant/issues/5005
|
||||
# See https://github.com/hashicorp/vagrant/issues/5005
|
||||
config.ssh.insert_key = false
|
||||
|
||||
config.vm.provision "ansible" do |ansible|
|
||||
|
|
@ -60,7 +60,7 @@ access.
|
|||
|
||||
There are a lot of Ansible options you can configure in your ``Vagrantfile``.
|
||||
Visit the `Ansible Provisioner documentation
|
||||
<https://docs.vagrantup.com/v2/provisioning/ansible.html>`_ for more
|
||||
<https://www.vagrantup.com/docs/provisioning/ansible.html>`_ for more
|
||||
information.
|
||||
|
||||
.. code-block:: bash
|
||||
|
|
@ -134,7 +134,7 @@ Advanced Usages
|
|||
```````````````
|
||||
|
||||
The "Tips and Tricks" chapter of the `Ansible Provisioner documentation
|
||||
<https://docs.vagrantup.com/v2/provisioning/ansible.html>`_ provides detailed information about more advanced Ansible features like:
|
||||
<https://www.vagrantup.com/docs/provisioning/ansible.html>`_ provides detailed information about more advanced Ansible features like:
|
||||
|
||||
- how to parallely execute a playbook in a multi-machine environment
|
||||
- how to integrate a local ``ansible.cfg`` configuration file
|
||||
|
|
@ -143,11 +143,11 @@ The "Tips and Tricks" chapter of the `Ansible Provisioner documentation
|
|||
|
||||
`Vagrant Home <https://www.vagrantup.com/>`_
|
||||
The Vagrant homepage with downloads
|
||||
`Vagrant Documentation <https://docs.vagrantup.com/v2/>`_
|
||||
`Vagrant Documentation <https://www.vagrantup.com/docs/>`_
|
||||
Vagrant Documentation
|
||||
`Ansible Provisioner <https://docs.vagrantup.com/v2/provisioning/ansible.html>`_
|
||||
`Ansible Provisioner <https://www.vagrantup.com/docs/provisioning/ansible.html>`_
|
||||
The Vagrant documentation for the Ansible provisioner
|
||||
`Vagrant Issue Tracker <https://github.com/mitchellh/vagrant/issues?q=is%3Aopen+is%3Aissue+label%3Aprovisioners%2Fansible>`_
|
||||
`Vagrant Issue Tracker <https://github.com/hashicorp/vagrant/issues?q=is%3Aopen+is%3Aissue+label%3Aprovisioners%2Fansible>`_
|
||||
The open issues for the Ansible provisioner in the Vagrant project
|
||||
:ref:`working_with_playbooks`
|
||||
An introduction to playbooks
|
||||
|
|
|
|||
|
|
@ -395,7 +395,7 @@ If running on a version of Ansible that is older than 2.5 or the normal
|
|||
full control over the operating system. No user is given this privilege by
|
||||
default, and care should be taken if you grant this privilege to a user or group.
|
||||
For more information on this privilege, please see
|
||||
`Act as part of the operating system <https://technet.microsoft.com/en-us/library/dn221957(v=ws.11).aspx>`_.
|
||||
`Act as part of the operating system <https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn221957(v=ws.11)>`_.
|
||||
You can use the below task to set this privilege on a Windows host::
|
||||
|
||||
- name: grant the ansible user the SeTcbPrivilege right
|
||||
|
|
@ -453,7 +453,7 @@ variables like normal but either do not define ``ansible_become_pass`` or set
|
|||
``ansible_become_pass: ''``.
|
||||
|
||||
Before become can work on an account like this, the local policy
|
||||
`Accounts: Limit local account use of blank passwords to console logon only <https://technet.microsoft.com/en-us/library/jj852174.aspx>`_
|
||||
`Accounts: Limit local account use of blank passwords to console logon only <https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj852174(v=ws.11)>`_
|
||||
must be disabled. This can either be done through a Group Policy Object (GPO)
|
||||
or with this Ansible task:
|
||||
|
||||
|
|
@ -511,7 +511,7 @@ can be set to one of the following:
|
|||
logon session as running a normal WinRM process with credential delegation.
|
||||
|
||||
For more information, see
|
||||
`dwLogonType <https://msdn.microsoft.com/en-au/library/windows/desktop/aa378184.aspx>`_.
|
||||
`dwLogonType <https://docs.microsoft.com/en-gb/windows/desktop/api/winbase/nf-winbase-logonusera>`_.
|
||||
|
||||
The ``logon_flags`` key specifies how Windows will log the user on when creating
|
||||
the new process. The value can be set to none or multiple of the following:
|
||||
|
|
@ -528,7 +528,7 @@ By default ``logon_flags=with_profile`` is set, if the profile should not be
|
|||
loaded set ``logon_flags=`` or if the profile should be loaded with
|
||||
``netcredentials_only``, set ``logon_flags=with_profile,netcredentials_only``.
|
||||
|
||||
For more information, see `dwLogonFlags <https://msdn.microsoft.com/en-us/library/windows/desktop/ms682434.aspx>`_.
|
||||
For more information, see `dwLogonFlags <https://docs.microsoft.com/en-gb/windows/desktop/api/winbase/nf-winbase-createprocesswithtokenw>`_.
|
||||
|
||||
Here are some examples of how to use ``become_flags`` with Windows tasks:
|
||||
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ While primarily used to kickoff OS installations and manage DHCP and DNS, Cobble
|
|||
layer that allows it to represent data for multiple configuration management systems (even at the same time), and has
|
||||
been referred to as a 'lightweight CMDB' by some admins.
|
||||
|
||||
To tie Ansible's inventory to Cobbler (optional), copy `this script <https://raw.github.com/ansible/ansible/devel/contrib/inventory/cobbler.py>`_ to ``/etc/ansible`` and ``chmod +x`` the file. cobblerd will now need
|
||||
To tie Ansible's inventory to Cobbler (optional), copy `this script <https://raw.githubusercontent.com/ansible/ansible/devel/contrib/inventory/cobbler.py>`_ to ``/etc/ansible`` and ``chmod +x`` the file. cobblerd will now need
|
||||
to be running when you are using Ansible and you'll need to use Ansible's ``-i`` command line option (e.g. ``-i /etc/ansible/cobbler.py``).
|
||||
This particular script will communicate with Cobbler using Cobbler's XMLRPC API.
|
||||
|
||||
|
|
@ -103,7 +103,7 @@ So in other words, you can use those variables in arguments/actions as well.
|
|||
Example: AWS EC2 External Inventory Script
|
||||
``````````````````````````````````````````
|
||||
|
||||
If you use Amazon Web Services EC2, maintaining an inventory file might not be the best approach, because hosts may come and go over time, be managed by external applications, or you might even be using AWS autoscaling. For this reason, you can use the `EC2 external inventory <https://raw.github.com/ansible/ansible/devel/contrib/inventory/ec2.py>`_ script.
|
||||
If you use Amazon Web Services EC2, maintaining an inventory file might not be the best approach, because hosts may come and go over time, be managed by external applications, or you might even be using AWS autoscaling. For this reason, you can use the `EC2 external inventory <https://raw.githubusercontent.com/ansible/ansible/devel/contrib/inventory/ec2.py>`_ script.
|
||||
|
||||
You can use this script in one of two ways. The easiest is to use Ansible's ``-i`` command line option and specify the path to the script after
|
||||
marking it executable::
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ Ansible Quickstart
|
|||
|
||||
We've recorded a short video that introduces Ansible.
|
||||
|
||||
The `quickstart video <https://www.ansible.com/quick-start-video>`_ is about 13 minutes long and gives you a high level
|
||||
The `quickstart video <https://www.ansible.com/resources/videos/quick-start-video>`_ is about 13 minutes long and gives you a high level
|
||||
introduction to Ansible -- what it does and how to use it. We'll also tell you about other products in the Ansible ecosystem.
|
||||
|
||||
Enjoy, and be sure to visit the rest of the documentation to learn more.
|
||||
|
|
|
|||
|
|
@ -371,7 +371,7 @@ standard:
|
|||
.. Note:: You should only quote strings when it is absolutely
|
||||
necessary or required by YAML, and then use single quotes.
|
||||
|
||||
The YAML specification considers the following `escape sequences <http://www.yaml.org/spec/current.html#id2517668>`_:
|
||||
The YAML specification considers the following `escape sequences <http://yaml.org/spec/current.html#id2517668>`_:
|
||||
|
||||
* ``\0``, ``\\``, ``\"``, ``\_``, ``\a``, ``\b``, ``\e``, ``\f``, ``\n``, ``\r``, ``\t``,
|
||||
``\v``, ``\L``, ``\N`` and ``\P`` -- Single character escape
|
||||
|
|
|
|||
|
|
@ -98,7 +98,7 @@ This can be done using one of the following methods:
|
|||
|
||||
Active Directory Certificate Services is beyond of scope in this documentation but may be
|
||||
the best option to use when running in a domain environment. For more information,
|
||||
see the `Active Directory Certificate Services documentation <https://technet.microsoft.com/en-us/library/cc732625(v=ws.11).aspx>`_.
|
||||
see the `Active Directory Certificate Services documentation <https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc732625(v=ws.11)>`_.
|
||||
|
||||
.. Note:: Using the PowerShell cmdlet ``New-SelfSignedCertificate`` to generate
|
||||
a certificate for authentication only works when being generated from a
|
||||
|
|
@ -483,7 +483,7 @@ There are two ways that older hosts can be used with CredSSP:
|
|||
has no way of supporting TLS 1.2
|
||||
|
||||
To enable TLS 1.2 support on Server 2008 R2 and Windows 7, the optional update
|
||||
`KRB3080079 <https://support.microsoft.com/en-us/help/3080079/update-to-add-rds-support-for-tls-1.1-and-tls-1.2-in-windows-7-or-windows-server-2008-r2>`_
|
||||
`KRB3080079 <https://support.microsoft.com/en-us/help/3080079/update-to-add-rds-support-for-tls-1-1-and-tls-1-2-in-windows-7-or-wind>`_
|
||||
needs to be installed.
|
||||
|
||||
Once the update has been applied and the Windows host rebooted, run the following
|
||||
|
|
|
|||
|
|
@ -90,7 +90,7 @@ In this use case / example, we will be selecting a virtual machine template and
|
|||
|
||||
Since Ansible utilizes the VMware API to perform actions, in this use case we will be connecting directly to the API from our localhost. This means that our playbooks will not be running from the vCenter or ESXi Server. We do not necessarily need to collect facts about our localhost, so the ``gather_facts`` parameter will be disabled. You can run these modules against another server that would then connect to the API if your localhost does not have access to vCenter. If so, the required Python modules will need to be installed on that target server.
|
||||
|
||||
To begin, there are a few bits of information we will need. First and foremost is the hostname of the ESXi server or vCenter server. After this, you will need the username and password for this server. For now, you will be entering these directly, but in a more advanced playbook this can be abstracted out and stored in a more secure fashion using :ref:`ansible-vault` or using `Ansible Tower credentials <http://docs.ansible.com/ansible-tower/latest/html/userguide/credentials.html>`_. If your vCenter or ESXi server is not setup with proper CA certificates that can be verified from the Ansible server, then it is necessary to disable validation of these certificates by using the ``validate_certs`` parameter. To do this you need to set ``validate_certs=False`` in your playbook.
|
||||
To begin, there are a few bits of information we will need. First and foremost is the hostname of the ESXi server or vCenter server. After this, you will need the username and password for this server. For now, you will be entering these directly, but in a more advanced playbook this can be abstracted out and stored in a more secure fashion using :ref:`ansible-vault` or using `Ansible Tower credentials <https://docs.ansible.com/ansible-tower/latest/html/userguide/credentials.html>`_. If your vCenter or ESXi server is not setup with proper CA certificates that can be verified from the Ansible server, then it is necessary to disable validation of these certificates by using the ``validate_certs`` parameter. To do this you need to set ``validate_certs=False`` in your playbook.
|
||||
|
||||
Now you need to supply the information about the virtual machine which will be created. Give your virtual machine a name, one that conforms to all VMware requirements for naming conventions. Next, select the display name of the template from which you want to clone new virtual machine. This must match what's displayed in VMware Web UI exactly. Then you can specify a folder to place this new virtual machine in. This path can either be a relative path or a full path to the folder including the Datacenter. You may need to specify a state for the virtual machine. This simply tells the module which action you want to take, in this case you will be ensure that the virtual machine exists and is powered on. An optional parameter is ``wait_for_ip_address``, this will tell Ansible to wait for the virtual machine to fully boot up and VMware Tools is running before completing this task.
|
||||
|
||||
|
|
|
|||
|
|
@ -85,7 +85,7 @@ Before you begin, make sure you have:
|
|||
- Username and password for the ESXi or vCenter server
|
||||
- Name of the existing Virtual Machine for which you want to collect folder path
|
||||
|
||||
For now, you will be entering these directly, but in a more advanced playbook this can be abstracted out and stored in a more secure fashion using :ref:`ansible-vault` or using `Ansible Tower credentials <http://docs.ansible.com/ansible-tower/latest/html/userguide/credentials.html>`_.
|
||||
For now, you will be entering these directly, but in a more advanced playbook this can be abstracted out and stored in a more secure fashion using :ref:`ansible-vault` or using `Ansible Tower credentials <https://docs.ansible.com/ansible-tower/latest/html/userguide/credentials.html>`_.
|
||||
|
||||
If your vCenter or ESXi server is not setup with proper CA certificates that can be verified from the Ansible server, then it is necessary to disable validation of these certificates by using the ``validate_certs`` parameter. To do this you need to set ``validate_certs=False`` in your playbook.
|
||||
|
||||
|
|
|
|||
|
|
@ -11,4 +11,4 @@ Following is the list of various external documentation and guides which can hel
|
|||
* `VCSIM test container image <https://quay.io/repository/ansible/vcenter-test-container>`_
|
||||
* `Ansible VMware community wiki page <https://github.com/ansible/community/wiki/VMware>`_
|
||||
* `VMware's official Guest Operating system customization matrix <https://partnerweb.vmware.com/programs/guestOS/guest-os-customization-matrix.pdf>`_
|
||||
* `VMware Compatibility Guide <https://partnerweb.vmware.com/comp_guide2/search.php>`_
|
||||
* `VMware Compatibility Guide <https://www.vmware.com/resources/compatibility/search.php>`_
|
||||
|
|
|
|||
Loading…
Reference in a new issue