Remove orphaned releasenotes
These releasenotes appear to be originally from https://opendev.org/openstack/openstack-ansible-plugins and do not pertain to anything in the config_template module. Change-Id: I23f0395d52e2c639dc987b37e0f251b8f3ea418b
This commit is contained in:
parent
78e7f22caa
commit
ed68c9d67d
@ -1,9 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- The ``py_pkgs`` lookup plugin now has strict ordering for requirement files
|
||||
discovered. These files are used to add additional requirements to the
|
||||
python packages discovered. The order is defined by the constant,
|
||||
``REQUIREMENTS_FILE_TYPES`` which contains the following entries,
|
||||
'test-requirements.txt', 'dev-requirements.txt', 'requirements.txt',
|
||||
'global-requirements.txt', 'global-requirement-pins.txt'. The items in this
|
||||
list are arranged from least to most priority.
|
@ -1,9 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- Add ``get_networks`` command to the neutron library.
|
||||
This will return network information for all networks,
|
||||
and fail if the specified ``net_name`` network is not
|
||||
present. If no ``net_name`` is specified network
|
||||
information will for all networks will be returned
|
||||
without performing a check on an existing ``net_name``
|
||||
network.
|
@ -1,7 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- The `get_nested` filter has been added, allowing for simplified
|
||||
value lookups inside of nested dictionaries.
|
||||
|
||||
`ansible_local|get_nested('openstack_ansible.swift')`, for example,
|
||||
will look 2 levels down and return the result.
|
@ -1,12 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- The default behaviour of ``ensure_endpoint`` in the
|
||||
keystone module has changed to update an existing
|
||||
endpoint, if one exists that matches the service
|
||||
name, type, region and interface. This ensures that
|
||||
no duplicate service entries can exist per region.
|
||||
deprecations:
|
||||
- The ``update`` state for the ``ensure_endpoint``
|
||||
method of the ``keystone`` module is now deprecated,
|
||||
and will be removed in the Queens cycle. Setting
|
||||
state to ``present`` will achieve the same result.
|
@ -1,42 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The ability to support login user domain and login project domain has been added to the
|
||||
keystone module.
|
||||
|
||||
::
|
||||
|
||||
# Example usage
|
||||
- keystone:
|
||||
command: ensure_user
|
||||
endpoint: "{{ keystone_admin_endpoint }}"
|
||||
login_user: admin
|
||||
login_password: admin
|
||||
login_project_name: admin
|
||||
login_user_domain_name: custom
|
||||
login_project_domain_name: custom
|
||||
user_name: demo
|
||||
password: demo
|
||||
project_name: demo
|
||||
domain_name: custom
|
||||
|
||||
fixes:
|
||||
- |
|
||||
The ability to support login user domain and login project domain has been added to the
|
||||
keystone module. This resolves https://bugs.launchpad.net/openstack-ansible/+bug/1574000
|
||||
|
||||
::
|
||||
|
||||
# Example usage
|
||||
- keystone:
|
||||
command: ensure_user
|
||||
endpoint: "{{ keystone_admin_endpoint }}"
|
||||
login_user: admin
|
||||
login_password: admin
|
||||
login_project_name: admin
|
||||
login_user_domain_name: custom
|
||||
login_project_domain_name: custom
|
||||
user_name: demo
|
||||
password: demo
|
||||
project_name: demo
|
||||
domain_name: custom
|
@ -1,8 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- The new provider network attribute ``sriov_host_interfaces``
|
||||
is added to support SR-IOV network mappings inside Neutron.
|
||||
The provider_network adds new items network_sriov_mappings
|
||||
and network_sriov_mappings_list to the provider_networks
|
||||
dictionary.
|
||||
Multiple interfaces can be defined by comma separation.
|
@ -1,11 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- An opportunistic Ansible execution strategy has been implemented. This
|
||||
allows the Ansible linear strategy to skip tasks with conditionals faster
|
||||
by never queuing the task when the conditional is evaluated to be false.
|
||||
- The Ansible SSH plugin has been modified to support running commands within
|
||||
containers without having to directly ssh into them. The change will detect
|
||||
presence of a container. If a container is found the physical host will be
|
||||
used as the SSH target and commands will be run directly. This will improve
|
||||
system reliability and speed while also opening up the possibility for SSH
|
||||
to be disabled from within the container itself.
|
@ -1,5 +0,0 @@
|
||||
---
|
||||
upgrade:
|
||||
- The ``glance`` library has been removed from OpenStack-Ansible's
|
||||
plugins. Upstream Ansible modules for managing OpenStack image
|
||||
resources should be used instead.
|
@ -1,5 +0,0 @@
|
||||
---
|
||||
upgrade:
|
||||
- The ``neutron`` library has been removed from OpenStack-Ansible's
|
||||
plugins. Upstream Ansible modules for managing OpenStack network
|
||||
resources should be used instead.
|
@ -1,6 +0,0 @@
|
||||
---
|
||||
other:
|
||||
- The vars plugin ``override_folder.py`` has been removed. With the move to
|
||||
Ansible 2.4 ["https://review.openstack.org/#/c/522778"] this plugin is no
|
||||
longer required. The functionality this plugin provided has been replaced
|
||||
with the native Ansible inventory plugin.
|
@ -1,22 +0,0 @@
|
||||
---
|
||||
features:
|
||||
- The deployer can now define an environment variable
|
||||
``GROUP_VARS_PATH`` with the folders of its choice
|
||||
(separated by the colon sign) to define an user
|
||||
space group_vars folder. These vars will apply but
|
||||
be (currently) overriden by the OpenStack-Ansible
|
||||
default group vars, by the set facts, and by the
|
||||
user_* variables. If the deployer defines multiple
|
||||
paths, the variables found are merged, and
|
||||
precedence is increasing from left to right
|
||||
(the last defined in GROUP_VARS_PATH wins)
|
||||
- The deployer can now define an environment variable
|
||||
``HOST_VARS_PATH`` with the folders of its choice
|
||||
(separated by the colon sign) to define an user
|
||||
space host_vars folder. These vars will apply but
|
||||
be (currently) overriden by the OpenStack-Ansible
|
||||
default host vars, by the set facts, and by the
|
||||
user_* variables. If the deployer defines multiple
|
||||
paths, the variables found are merged, and
|
||||
precedence is increasing from left to right
|
||||
(the last defined in HOST_VARS_PATH wins)
|
Loading…
Reference in New Issue
Block a user