This commit is part of a series to retire the Packaging Deb
project. Step 2 is to remove all content from the project
repos, replacing it with a README notification where to find
ongoing work, and how to recover the repo if needed at some
future point (as in
https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project).
Change-Id: I161dc093726c3c8cce5a7057282743ca4908eb57
To make multiple process or threads to execute periodic
tasks parallely, locks are being applied per tasks basis rather
than on the table.
This patch makes sure that a single periodic thread in a process
exist. All the tasks are managed by a single instance
of PeriodicTask class.
If a task is just executed then other tasks can not acquire lock
in time less then periodic time interval. Therefor this prevent
periodic task to be executed by process on the same host or
different host back to back.
Change-Id: Id9054515721ce28a84b3a42d4cece7e3e096ad0c
Partially-Implements: blueprint v2driver-activities-in-pike
When port binding fails, log device_owner and device_id in addition
to the existing ones. They are helpful to determine what port is for.
e.g. vm, dhcp, router etc when diagnosing failure of port binding.
There is a race condition between dhcp port creation and network
deletion because notification to dhcp agent can be delayed.
If dhcp port is to be bound after network is deleted, the binding
fails. It's safe to ignore such a case.
Change-Id: I26e235fa3e0bdab5e3d568a9a0f60a380642c760
There are intermittent failures with journal db. e.g. there is should
corresponding journal entry, but it didn't.
One of the possible causes is, there can be one or more journal threads
running unintentionally. In principle JournalThread is prevented from
creating thread by mocking methods that spawns such threads.
Make it sure that do mock.patch or useFixture which calls mock.patch
before calling super.setUp
Change-Id: I884c6ca5c07f330c2c416226d95304ac618bfc66
Member APIs contains /pool/<pool-id>/member/<member-id> which
increased thse size of the column. And current implementation
is not the clean way of implementing member operation. Because
wrong information related to object type is stored in database.
Customied URL builder for lbaas member resource is used to
the discussed issues.
Change-Id: Ic61aaeb8d8d47c75d3d6834c581fb40968145ba2
Port status update worker wasn't loaded, causing VM launch to fail when
using pseudo agent binding which is the default.
Change-Id: I39c971899e6133f31b05adebcd30398f8d93b11f
This change moves dependency calculations to happen when creating a
journal entry. This way, each journal entry only depends on the known
information at that time reducing the possibility or errors dues to
dependency calculations taking into account later journal entries.
Also journal entries won't be attempted unless they have no
dependencies, reducing the need to lock & unlock journal entries that
aren't free of dependencies yet.
More info can be found in the spec [1].
[1] https://docs.openstack.org/developer/networking-odl/specs/dep-validations-on-create.html
Implements: blueprint dep-validations-on-create
Change-Id: I7c9ba3b42017749ce871735942926849ee09228e
The table will keep dependencies of journal entries upon one another,
and will be utilized later on.
Partially-Implements: blueprint dep-validations-on-create
Change-Id: Ie39fde548016ecd20ae0f68d158c7e82b9dd3e8c
Introduce fixture to mock start_odl_sync_thread.
and mock _start_sync_timer. It's also needs to be mocked
to avoid running timer unintentionally.
Change-Id: I8298189fcbe56028fa08b96cb50f50d5163a58f0
Currently ml2 and l3 resources are recovered other resources are
not being recovered. This patch adds lbaas, l2gw, trunk, sfc for
recovery.
Resources are registered at the time of initialization of driver
and registered resources are used for recovery.
Closes-bug: #1701207
Change-Id: Ib3d219953e73cb6aad4fd09637e996b61d4a32d6
1. Add OpenDaylight Ceilometer driver to collect network statistics from ODL
through its REST APIs.
2. Set project_id of the meters as:
a. Admin tenant id for all switch.* meters
b. Tenant id who created the neutron port for port.* meters.
Change-Id: Id1fc02eb413366b87b2f28799a1d38ed120acb7d
Implements: blueprint network-statistics-from-opendaylight
Depend-On: I0e65d25e71d2d258ff0db76f020924170f380ec2
Recently a change [1] was merged which forced new netvirt
to be used for all gate jobs, but intention was to use it
for fullstack carbon and nitrogen job. This is followup to
revert [2] of [1]
[1]. https://review.openstack.org/#/c/482281/
[2]. https://review.openstack.org/#/c/482814/
Change-Id: I495c2fa61d233cea74a5fd7c2f0145f7821700e5
This reverts commit eaa9ab1d39.
The mentioned commit causes the gate tempest jobs to run with the new
netvirt, even though some of them are defined to run with the old one.
Change-Id: I4ce69e60ef700739e9e5652cc1fa22cd5b7bc491
The way test have been done in the past was passing
in any generated uuid for instance and fake tap device
for ovs vif plugging and checks if mac address of plugged
port exists in flow, this may not work with new netvirt.
this patch update the test to list ports on bridge and checks
if tap device exists in results.
Change-Id: Ica0004bfd69e3e29c4d528191c42ff8d3f4485a6