69f95cc5bb
This adds the optional `create_in_regions` and `create_in_all_regions` parameters to the `NewDefaultNetworkAction` and the `NewProjectDefaultNetworkAction` actions. When `create_in_regions` is set, the action will ignore the default region set when creating a project, and instead create default networks and routers for each region set in the `create_in_regions` list. When `create_in_regions` is unset (or set to an empty list), the actions will default to the behaviour dictated by `create_in_all_regions`. When `create_in_all_regions` is set to `False` (the default), a default network is created in the default region only, as it always has. When it is set to `True`, it will instead create default networks in *all* active cloud regions, as discovered by Adjutant. Improve error handling in `NewDefaultNetworkAction` to give more detail in the task log when resource creation fails. Fix bugs in the fake Neutron client in the unit tests where created resources were hard-coded to be added to the `RegionOne` region. Change-Id: I0e0885dda449b22788bd4c9ae72b874d8ce661b5
Team and repository tags
Adjutant
A basic workflow framework built using Django and Django-Rest-Framework to help automate basic Admin tasks within an OpenStack cluster.
Primarily built as user registration service that fits into the OpenStack ecosystem alongside Keystone, its purpose to fill functionality missing from Keystone. Ultimately it is just a framework with actions that are tied to an endpoint and can require certain data fields and perform actions via the OpenStack clients as well as talk to external systems as needed.
Useful for automating generic admin tasks that users might request but otherwise can't do without the admin role. Also allows automating the signup and creation of new users, and allows such requests to require approval first if wanted. Due to issuing of uri+tokens for final steps of some actions, allows for a password submit/reset system as well.
Documentation
Documentation can be found at: https://docs.openstack.org/adjutant/latest
Documentation is stored in doc/, a sphinx build of the documentation can be generated with the command tox -e docs.
An API Reference is stored in api-ref. This is also a sphinx build and can be generated with tox -e api-ref.