Snippets Groups Projects

"...kolla-ansible.git" did not exist on "f1c81365562e2e222dbaf97a1f689298582ca127"

Remove system scope token to access services

Ghanshyam Mann authored 2 years ago

As per the RBAC new direction in Zed cycle, we have dropped the
system scope from API policies and all the policies are hardcoded
to project scoped so that any user accessing APIs using system scope
will get 403 error. It is dropped from all the OpenStack services
except for the Ironic service which will have system scope and to
support ironic only deployment, we are keeping system as well as project
scope in Keystone.

Complete discussion and direction can be found in the below gerrit
change and TC goal direction:

- https://review.opendev.org/c/openstack/governance/+/847418
- https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rbac.html#the-issues-we-are-facing-with-scope-concept

As phase-2 of RBAC goal, services will start enabling the new
defaults and project scope by default. For example: Nova did in
- https://review.opendev.org/c/openstack/nova/+/866218

Kolla who start accessing the services using system scope token
- https://review.opendev.org/c/openstack/kolla-ansible/+/692179

This commit partially revert the above change except keeping
system scope usage for Keystone and Ironic. Rest all services are changed
to use the project scope token.

And enable the scope and new defaults for Nova which was disabled
by https://review.opendev.org/c/openstack/kolla-ansible/+/870804

Change-Id: I0adbe0a6c39e11d7c9542569085fc5d580f26c9d

283fa242

283fa242 2 years ago

Name	Last commit	Last update
ansible
contrib
deploy-guide/source
doc
etc/kolla
kolla_ansible
releasenotes
roles
specs
tests
tools
zuul.d
.ansible-lint
.gitignore
.gitreview
.stestr.conf
.yamllint
CONTRIBUTING.rst
LICENSE
README.rst
lint-requirements.txt
requirements.txt
requirements.yml
setup.cfg
setup.py
test-requirements.txt
tox.ini

Kolla Ansible

The Kolla Ansible is a deliverable project separated from Kolla project.

Kolla Ansible deploys OpenStack services and infrastructure components in Docker containers.

Kolla's mission statement is:

To provide production-ready containers and deployment tools for operating
OpenStack clouds.

Kolla is highly opinionated out of the box, but allows for complete customization. This permits operators with little experience to deploy OpenStack quickly and as experience grows modify the OpenStack configuration to suit the operator's exact requirements.

Getting Started

Learn about Kolla Ansible by reading the documentation online Kolla Ansible.

Get started by reading the Developer Quickstart.

OpenStack services

Kolla Ansible deploys containers for the following OpenStack projects:

Infrastructure components

Kolla Ansible deploys containers for the following infrastructure components:

Collectd, Telegraf, InfluxDB, Prometheus, and Grafana for performance monitoring.
OpenSearch and OpenSearch Dashboards to search, analyze, and visualize log messages.
Etcd a distributed reliable key-value store.
Fluentd as an open source data collector for unified logging layer.
Gnocchi A time-series storage database.
HAProxy and Keepalived for high availability of services and their endpoints.
MariaDB and Galera Cluster for highly available MySQL databases.
Memcached a distributed memory object caching system.
Open vSwitch for use with Neutron.
RabbitMQ as a messaging backend for communication between services.
Redis an in-memory data structure store.

Directories

ansible - Contains Ansible playbooks to deploy OpenStack services and infrastructure components in Docker containers.
contrib - Contains demos scenarios for Heat, Magnum and Tacker and a development environment for Vagrant
doc - Contains documentation.
etc - Contains a reference etc directory structure which requires configuration of a small number of configuration variables to achieve a working All-in-One (AIO) deployment.
kolla_ansible - Contains password generation script.
releasenotes - Contains releasenote of all features added in Kolla Ansible.
specs - Contains the Kolla Ansible communities key arguments about architectural shifts in the code base.
tests - Contains functional testing tools.
tools - Contains tools for interacting with Kolla Ansible.
zuul.d - Contains project gate job definitions.

Getting Involved

Need a feature? Find a bug? Let us know! Contributions are much appreciated and should follow the standard Gerrit workflow.

We communicate using the #openstack-kolla irc channel.
File bugs, blueprints, track releases, etc on Launchpad.
Attend weekly meetings.
Contribute code.

Contributors

Check out who's contributing code and contributing reviews.

Notices

Docker and the Docker logo are trademarks or registered trademarks of Docker, Inc. in the United States and/or other countries. Docker, Inc. and other parties may also have trademark rights in other terms used herein.