Files
ddb31b12a817702bab435db08fd4c2d93d9aceea
openstack-ansible-os_cloudk... /defaults /main.yml

125 lines
5.0 KiB
YAML
Raw Normal View History

2016年05月08日 12:03:41 -05:00
---
# Copyright 2016, Rackspace US, Inc.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
## Verbosity Options
debug:False
Execute service setup against a delegated host using Ansible built-in modules In order to reduce the packages required to pip install on to the hosts, we allow the service setup to be delegated to a specific host, defaulting to the deploy host. We also switch as many tasks as possible to using the built-in Ansible modules which make use of the shade library. The 'virtualenv' package is now installed appropriately by the openstack_hosts role, so there's no need to install it any more. The 'httplib2' package is a legacy Ansible requirement for the get_url/get_uri module which is no longer needed. The keystone client library is not required any more now that we're using the upstream modules. As there are no required packages left, the task to install them is also removed. With the dependent patches, the openstack_openrc role is now executed once on the designated host, so it is no longer required as a meta-dependency for the role. Depends-On: https://review.openstack.org/579233 Depends-On: https://review.openstack.org/579959 Change-Id: Ib46638d1cb35e677ecfe789a32bb69a024042d6f
2018年07月03日 21:40:27 +01:00
# Set the host which will execute the shade modules
# for the service setup. The host must already have
# clouds.yaml properly configured.
cloudkitty_service_setup_host:"{{ openstack_service_setup_host | default('localhost') }}"
# Set the package install state for distribution and pip packages
# Options are 'present' and 'latest'
cloudkitty_package_state:"latest"
cloudkitty_pip_package_state:"latest"
cloudkitty_service_user_name:cloudkitty
cloudkitty_rabbitmq_userid:cloudkitty
cloudkitty_rabbitmq_vhost:/cloudkitty
cloudkitty_rabbitmq_port:5672
cloudkitty_rabbitmq_servers:127.0.0.1
cloudkitty_rabbitmq_use_ssl:False
cloudkitty_system_group_name:cloudkitty
cloudkitty_system_user_name:cloudkitty
cloudkitty_system_comment:meow
cloudkitty_system_shell:/bin/false
cloudkitty_system_home_folder:"/var/lib/{{ cloudkitty_system_user_name }}"
cloudkitty_venv_tag:untagged
cloudkitty_bin:"/openstack/venvs/cloudkitty-{{ cloudkitty_venv_tag }}/bin"
# venv_download, even when true, will use the fallback method of building the
# venv from scratch if the venv download fails.
cloudkitty_venv_download:"{{ not cloudkitty_developer_mode | bool }}"
cloudkitty_venv_download_url:http://127.0.0.1/venvs/untagged/ubuntu/cloudkitty.tgz
cloudkitty_git_repo:https://git.openstack.org/openstack/cloudkitty
2016年05月08日 12:03:41 -05:00
cloudkitty_git_install_branch:master
cloudkitty_developer_constraints:
- "git+{{ cloudkitty_git_repo }}@{{ cloudkitty_requirements_git_install_branch }}#egg=cloudkitty"
2016年05月08日 12:03:41 -05:00
cloudkitty_developer_mode:false
cloudkitty_notification_topics:notifications
cloudkitty_collected_services:compute
cloudkitty_collector:ceilometer
cloudkitty_service_project_domain_id:default
cloudkitty_service_project_name:"service"
cloudkitty_service_user_domain_id:default
cloudkitty_keystone_auth_plugin:password
cloudkitty_output_backend:cloudkitty.backend.file.FileBackend
cloudkitty_output_pipeline:osrf
cloudkitty_output_basepath:/var/cloudkitty/reports
Move database creation into role There is no record for why we implement the database creation outside of the role in the playbook, when we could do it inside the role. Implementing it inside the role allows us to reduce the quantity of group_vars duplicated from the role, and allows us to better document the required variables in the role. The delegation can still be done as it is done in the playbook too. In this patch we implement a new variable called 'cloudkitty_db_setup_host' which is used in the role to allow delegation of the database setup task to any host, but defaults to the first member of the galera_all host group. We also document the variable cloudkitty_galera_address which has been used for a long time, but never documented. Change-Id: I7bb3f38556558ef14723361d3672a1d06f839b52
2018年06月12日 20:39:26 +01:00
cloudkitty_db_setup_host:"{{ ('galera_all' in groups) | ternary(groups['galera_all'][0], 'localhost') }}"
cloudkitty_galera_address:"{{ galera_address | default('127.0.0.1') }}"
cloudkitty_galera_database:cloudkitty
cloudkitty_galera_user:cloudkitty
Move database creation into role There is no record for why we implement the database creation outside of the role in the playbook, when we could do it inside the role. Implementing it inside the role allows us to reduce the quantity of group_vars duplicated from the role, and allows us to better document the required variables in the role. The delegation can still be done as it is done in the playbook too. In this patch we implement a new variable called 'cloudkitty_db_setup_host' which is used in the role to allow delegation of the database setup task to any host, but defaults to the first member of the galera_all host group. We also document the variable cloudkitty_galera_address which has been used for a long time, but never documented. Change-Id: I7bb3f38556558ef14723361d3672a1d06f839b52
2018年06月12日 20:39:26 +01:00
cloudkitty_database_connection:>-
mysql+pymysql://{{ cloudkitty_galera_user }}:{{ cloudkitty_container_mysql_password }}@{{ cloudkitty_galera_address }}/{{ cloudkitty_galera_database }}?charset=utf8
## Service Type and Data
cloudkitty_service_region:RegionOne
cloudkitty_service_name:cloudkitty
cloudkitty_service_port:8089
cloudkitty_service_proto:http
cloudkitty_service_publicuri_proto:"{{ openstack_service_publicuri_proto | default(cloudkitty_service_proto) }}"
cloudkitty_service_adminuri_proto:"{{ openstack_service_adminuri_proto | default(cloudkitty_service_proto) }}"
cloudkitty_service_internaluri_proto:"{{ openstack_service_internaluri_proto | default(cloudkitty_service_proto) }}"
cloudkitty_service_publicuri:"{{ cloudkitty_service_publicuri_proto }}://{{ external_lb_vip_address }}:{{ cloudkitty_service_port }}"
cloudkitty_service_publicurl:"{{ cloudkitty_service_publicuri }}/"
cloudkitty_service_adminuri:"{{ cloudkitty_service_adminuri_proto }}://{{ internal_lb_vip_address }}:{{ cloudkitty_service_port }}"
cloudkitty_service_adminurl:"{{ cloudkitty_service_adminuri }}/"
cloudkitty_service_internaluri:"{{ cloudkitty_service_internaluri_proto }}://{{ internal_lb_vip_address }}:{{ cloudkitty_service_port }}"
cloudkitty_service_internalurl:"{{ cloudkitty_service_internaluri }}/"
cloudkitty_cloudkitty_conf_overrides:{}
cloudkitty_policy_overrides:{}
cloudkitty_api_paste_ini_overrides:{}
Ensure the components are isolated from the system This creates a specific slice which all OpenStack services will operate from. By creating an independent slice these components will be governed away from the system slice allowing us to better optimise resource consumption. See the following for more information on slices: * https://www.freedesktop.org/software/systemd/man/systemd.slice.html See for following for more information on resource controls: * https://www.freedesktop.org/software/systemd/man/systemd.resource-control.html Tools like ``systemd-cgtop`` and ``systemd-cgls`` will now give us insight into specific processes, process groups, and resouce consumption in ways that we've not had access to before. To enable some of this reporting the accounting options have been added to the [Service] section of the unit file. Change-Id: Idac3056145b92adcd0b5b328296c59b71bf28441 Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
2017年03月28日 23:33:28 -05:00
cloudkitty_api_init_overrides:{}
cloudkitty_processor_init_overrides:{}
Use dictionary for service group mappings Change the 'cloudkitty_service_names' from a list to a dictionary mapping of services, groups that install those services. This brings the method into line with that used in the os_neutron role in order to implement a more standardised method. The init tasks have been updated to run once and loop through this mapping rather than being included multiple times and re-run against each host. This may potentially reduce role run times. Currently the reload of upstart/systemd scripts may not happen if only one script changes as the task uses a loop with only one result register. This patch implements handlers to reload upstart/systemd scripts to ensure that this happens when any one of the scripts change. The handler to reload the services now only tries to restart the service if the host is in the group for the service according to the service group mapping. This allows us to ensure that handler failures are no longer ignored and that no execution time is wasted trying to restart services which do not exist on the host. Finally: - Common variables shared by each service's template files have been updated to use the service namespaced variables. - Unused handlers have been removed. - Unused variables have been removed. Change-Id: Ieb96fac62906ac9eb387edb450df0c0ca9c0ccb2
2016年09月28日 17:35:34 +01:00
## Service Name-Group Mapping
cloudkitty_services:
cloudkitty-api:
group:cloudkitty_api
service_name:cloudkitty-api
Ensure the components are isolated from the system This creates a specific slice which all OpenStack services will operate from. By creating an independent slice these components will be governed away from the system slice allowing us to better optimise resource consumption. See the following for more information on slices: * https://www.freedesktop.org/software/systemd/man/systemd.slice.html See for following for more information on resource controls: * https://www.freedesktop.org/software/systemd/man/systemd.resource-control.html Tools like ``systemd-cgtop`` and ``systemd-cgls`` will now give us insight into specific processes, process groups, and resouce consumption in ways that we've not had access to before. To enable some of this reporting the accounting options have been added to the [Service] section of the unit file. Change-Id: Idac3056145b92adcd0b5b328296c59b71bf28441 Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
2017年03月28日 23:33:28 -05:00
init_config_overrides:"{{ cloudkitty_api_init_overrides }}"
Use dictionary for service group mappings Change the 'cloudkitty_service_names' from a list to a dictionary mapping of services, groups that install those services. This brings the method into line with that used in the os_neutron role in order to implement a more standardised method. The init tasks have been updated to run once and loop through this mapping rather than being included multiple times and re-run against each host. This may potentially reduce role run times. Currently the reload of upstart/systemd scripts may not happen if only one script changes as the task uses a loop with only one result register. This patch implements handlers to reload upstart/systemd scripts to ensure that this happens when any one of the scripts change. The handler to reload the services now only tries to restart the service if the host is in the group for the service according to the service group mapping. This allows us to ensure that handler failures are no longer ignored and that no execution time is wasted trying to restart services which do not exist on the host. Finally: - Common variables shared by each service's template files have been updated to use the service namespaced variables. - Unused handlers have been removed. - Unused variables have been removed. Change-Id: Ieb96fac62906ac9eb387edb450df0c0ca9c0ccb2
2016年09月28日 17:35:34 +01:00
cloudkitty-processor:
group:cloudkitty_api
service_name:cloudkitty-processor
Ensure the components are isolated from the system This creates a specific slice which all OpenStack services will operate from. By creating an independent slice these components will be governed away from the system slice allowing us to better optimise resource consumption. See the following for more information on slices: * https://www.freedesktop.org/software/systemd/man/systemd.slice.html See for following for more information on resource controls: * https://www.freedesktop.org/software/systemd/man/systemd.resource-control.html Tools like ``systemd-cgtop`` and ``systemd-cgls`` will now give us insight into specific processes, process groups, and resouce consumption in ways that we've not had access to before. To enable some of this reporting the accounting options have been added to the [Service] section of the unit file. Change-Id: Idac3056145b92adcd0b5b328296c59b71bf28441 Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
2017年03月28日 23:33:28 -05:00
init_config_overrides:"{{ cloudkitty_processor_init_overrides }}"
cloudkitty_pip_packages:
- cloudkitty
- cryptography
- msgpack-python
- osprofiler
- PyMySQL
- python-memcached
- SQLAlchemy>=1.0.10
- tooz
2016年05月08日 12:03:41 -05:00
# This variable is used by the repo_build process to determine
# which host group to check for members of before building the
# pip packages required by this role. The value is picked up
# by the py_pkgs lookup.
cloudkitty_role_project_group:cloudkitty_all