From 1f83ed0533d6ded3b8ef7efa514a38ec7b9d4f2e Mon Sep 17 00:00:00 2001 From: songwenping Date: Tue, 19 Mar 2024 17:13:00 +0800 Subject: [PATCH] Fix the ansible intro_inventory.html link Change-Id: I0f35c2ea1400ea25fdb253580c6c1b2e06ae591e --- doc/source/user/multinode.rst | 4 ++-- etc/kolla/globals.yml | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/source/user/multinode.rst b/doc/source/user/multinode.rst index 5074fa728b..eab510e49d 100644 --- a/doc/source/user/multinode.rst +++ b/doc/source/user/multinode.rst @@ -60,7 +60,7 @@ controls how ansible interacts with remote hosts. Ansible uses SSH to connect the deployment host and target hosts. For more information about SSH authentication please reference - `Ansible documentation `__. + `Ansible documentation `__. .. code-block:: ini @@ -75,7 +75,7 @@ controls how ansible interacts with remote hosts. Additional inventory parameters might be required according to your environment setup. Reference `Ansible Documentation - `__ for more + `__ for more information. diff --git a/etc/kolla/globals.yml b/etc/kolla/globals.yml index 171211b3fa..d16db8fe9e 100644 --- a/etc/kolla/globals.yml +++ b/etc/kolla/globals.yml @@ -130,7 +130,7 @@ workaround_ansible_issue_8743: yes # interface by default. This interface must contain an IP address. # It is possible for hosts to have non-matching names of interfaces - these can # be set in an inventory file per host or per group or stored separately, see -# http://docs.ansible.com/ansible/intro_inventory.html +# http://docs.ansible.com/ansible/latest/intro_inventory.html # Yet another way to workaround the naming problem is to create a bond for the # interface on all hosts and give the bond name here. Similar strategy can be # followed for other types of interfaces.