This patch adds the ability to configure devstack to use catalog zones
when using the BIND9 backend.
It also adds a test job "designate-bind9-catalog-zones" that uses catalog zones
with a BIND9 backend.
Change-Id: Ib618d7850b0a86a8eb10eaa52b0e330cf908883a
Signed-off-by: Jan Hartkopf <jhartkopf@inovex.de>
This reverts commit 185d92d230.
Reason for revert: Lets try to move back to uwsgi, as logging is a lot cleaner in the CI with uwsgi. Switches uwsgi from using uwsgi over socket to over localhost HTTP.
This patch also bumps the API_WORKERS setting for devstack from 2 to 4.
This will bump the uwsgi processes and threads from two to four.
Change-Id: I126133564e2ada32448ad36e0d021790939425d4
"localhost" can also point to ::1, but the memcached service is only
listening on 127.0.0.1, so be explicit about that in the URL that
we give to tooz.
Depends-On: https://review.opendev.org/759831
Change-Id: I2a2ec20b7645034a23337380005add2e953f9185
There is an issue with the unauthed tests
and uwsgi causing the CI to frequently fail.
Lets move back to mod_wsgi until we can figure
that out.
Change-Id: I9fd558cec85da87c8daea36f7a9e2666948e72f1
This patch switches to Apache and mod_wsgi by default
for devstack.
Also, use memcached as the coordinatior for single node deployments.
Change-Id: I8798c04f2bc386aca32bda8961efd29298899890
That directory was only needed when using PKI tokens, which have been
removed from keystone for some cycles now. Also replace the deprecated
devstack function configure_auth_token_middleware with the current
version.
Change-Id: I7d10a21ed90dc9ea762dc3ea28fb22f55acf413d
The pool-manager has been deprecated since Newton and
is now being removed with the Train release.
Change-Id: Ib258043d492bb25e1c061d765b40885317c73804
Currently when devstack runs, the following
error message is always displayed.
> WARNING stevedore.named [-] Could not load
This is because no notification driver is set. We
fix this by setting messagingv2 to default.
Change-Id: Id8c293cfab828b568b6cb2654530e8fe657fb69a
we need to test with default values to ensure validity of
designate-tempest-plugin for deployments with default config values.
Change-Id: Ifbcf8614fdcab5a97139234025ed0decf2e91f8e
Depends-On: https://review.openstack.org/638412/
TEMPEST_SERVICES global variable is not supported
by devstack since long back.
- I380dd20e5ed716a0bdf92aa02c3730359b8136e4
- I9c24705e494689f09a885eb0a640efd50db33fcf
Service availability of tempest known services will be
set by devstack with local check.
- I02be777bf93143d946ccbb8e9eff637bfd1928d4
This commit removes the unused TEMPEST_SERVICES setting
Related-Bug: #1743688
Change-Id: I596e45d0922686ce916fe4342d3d6357b57b91bb
In devstack settings we have pool-manager and zone-manager
enabled by default. This causes conflict if a user wants to run
designate plugin with worker and producer.
This change replaces pool-manager and zone-manager with worker
and producer in devstack settings.
Closes-Bug: #1733992
Change-Id: Id96f1430d1091f2485099523fae499bde377e7e6
In [1] the definition of start_tls_proxy was changed, we need to have a
service name as the first parameter now.
Also set the correct protocol when tls-proxy is enabled.
[1] Ifcba410f5969521e8b3d30f02795541c1661f83a
Change-Id: I64e6f9aefcc8da5b9988fb7bff894d9a4205f871
- More information about the actual worker code can be found
in `designate/worker/README.md` and in the inline docstrings
- Stand up a `designate-worker` process with an rpcapi, all
the usual jazz
- Implement a base `Task` class that defines the behavior of
a task and exposes resources to the task.
- Implement CUD Zone tasks, which includes Tasks that poll for zones,
send Notifies, and update status. These are all done in parallel
with threads using a shared threadpool, rather than iteratively.
- Implement a `recover_shard` task that serves the function
of a periodic recovery, but only for a shard. Call that
task with various shards from the zone manager.
- Put some shims in central and mdns so that the worker can
be switched on/off with a few config values.
- Changes Zone Manager -> Producer
- Removes zm rpcapi
- Adds startable designate-producer service
- Makes zone-manager an alias for producer service with a warning log
- Lots of renaming
- Moves zone export to worker
- API now uses central_api.export_zone to get zonefiles
- Central uses worker_api.start_zone_export to init exports
- Now including unit tests
- Temporary workarounds for upgrade/migration move the logic
into central if worker isn't available.
- Deprecates Pool manager polling options and adds warning msg on
starting designate-pool-manager
- Get some devstack going
- Changes powerdns backend to get new sqlalchemy sessions for each
action
- Sets the default number of threads in a worker process to 200,
this is pretty much a shot in the dark, but 1000 seemed like
too many, and 20 wasn't enough.
- Grenade upgrade testing
- Deprecation warnings for zone/pool mgr
The way to run this is simple, just stop `designate-pool-manager`
and `designate-zone-manager`, toggle the config settings in the
`service:worker` section: enabled = true, notify = true
and start `designate-worker` and `designate-producer` and you
should be good to go.
Change-Id: I259e9825d3a4eea58e082303ba3bdbdb7bf8c363
As tempest is creating and deleting zones, it does not wait
for all zones to be deleted before moving onto the next test.
This can lead to having a large number of pending delete zones
which consume all/most of the default quotas, and tests begin
failing.
By setting the default quotas higher in DevStack, we allow the
tests to proceed.
Change-Id: I3652bb06724fb8b89bb341c9d9f61b1dde056119
This updates our devstack plugin to use the current clone+install
method for the client (missing vars) and dashboard (replaced with
the new method).
Designate itself is still using old vars, but I suspect this is
a leftover and there's really no need for Designate to try
clone itself since the plugin is inline now...
Change-Id: I2189abc196d74520fa3fae0da215a1c6dd891387
In order to fully remove the V1 API, we need to be able to
deploy DevStack entirely without the API. As a step towards
removing the API, we'll (at a date to be chosen later) disable
API v1 by default in both the codebase and DevStack plugin.
Change-Id: If1f27eb43f014959551c298f10c6c5fcb95e2fe8
* Add a new backend for DevStack allowing the Agent
backend to be configured.
* Change the agent to choose a sane port by default, it's extremely
unlikely anyone is exposing the agent on port 53 intentionally.
* The agent itself is not yet configured, this will come later as it
involves refactoring most of the BIND non-agent backend into a lib.
* Fail when the user asks for the agent backend, without also enabling
the agent service.
Change-Id: Iedde58f4f5a2ea89cb9da78aaec1853208af8fc9
This change adds the tooling to use the DB Tables created for pool
config data and the tooling to migrate the config info itself.
Change-Id: If99dbf527ef1ac0f05f15fe77f68f64e357fe0a5
This patch will not remove the existing Devstack integration
in contrib/devstack.
Change-Id: I23ef00bb136e92abc5e69a9bbe1093cad9d2a362
Closes-bug: #1504214