Status and status_description fields of HealthMonitor
model are never changed during lifetime of the object
and doesn't represent the status of it's pysical
implementation. Instead, status and status_description
of PoolMonitorAssociation is used. Another reason for
removing those fields is that HealthMonitor acts as
template which is instantiated on device. Status field
for template makes no sense.
Roman Podolyaka [Fri, 2 Aug 2013 15:12:42 +0000 (18:12 +0300)]
Fix typo in FK name in VPNaaS DB schema migration
Applying of migration 52ff27f7567a fails due to the typo
in a table name referenced by a FK ('ipsecsiteonnections'
instead of 'ipsec_site_connections').
zhhuabj [Fri, 2 Aug 2013 16:44:34 +0000 (00:44 +0800)]
Fix the alphabetical order in requirement files
Fix the alphabetical order in requirement files,
Bring into correspondence with other project,like
https://github.com/openstack/requirements/blob/ \
master/requirements.txt
Luis A. Garcia [Mon, 29 Jul 2013 21:43:11 +0000 (21:43 +0000)]
Sync gettextutils from oslo
The oslo changes necessary for delayed translation were refactored in
oslo. This patch set brings in the refactored changes, implemented
under the same change-id mentioned below.
Currently the migration is skipped in all cases.
Added * to run migration for all plugins until we have
proper handling for service plugins in migration framework
Removes peer port creation from add_router_interface.
Also fixes port_drivers dict which had a duplicate key.
In addition clears attachment on the NVP logical switch part
being paired with the logical router port before plugging
the patch attachment.
Add a relationship performing eager load in Port and Network
models, thus preventing the 'extend' function from performing
an extra database query.
Also fixes a comment in securitygroups_db.py
Yang Yu [Mon, 22 Jul 2013 06:14:36 +0000 (14:14 +0800)]
Prompted error message is not correct for PortNotFound
When deleting a non-existing port, the error message would be
"Port XXXX could not be found on network None" for some plugins.
"network None" is not correct enough here.
NEC Plugin used to ignore OFC errors while deleting resources from OFC,
and it could leave some unused resources on OFC. If OFC generates id
which is in remained resources when creating new resource, it will fail.
This commit makes NEC Plugin keep logical resource when it failed to
delete resource from OFC not to leave orphan resource on OFC, and raise
exception to tell the user that the resouce status is Error.
NOTE: The user can retry deletion. If the resouce was successfully
deleted from OFC in retries, the logical resource will be deleted.
This patch removes the NVP call for creating a logical port from
the SQL transaction context used for creating the Neutron port.
It also ensures orphaned data are properly removed from both
the Neutron DB and the NVP backend.
snaiksat [Fri, 10 May 2013 04:31:17 +0000 (21:31 -0700)]
Firewall as a Service (FWaaS) APIs and DB Model
Implements: blueprint quantum-fwaas
blueprint: quantum-fwaas-plugin
This is the first iteration of the FWaaS implementation and
is geared towards implementing the model that will be
required to at least address the reference implementation.
This iteration will not include implementation of the following
features:
* grouping or dynamic objects
* application/service objects
Update Neutron rootwrap to the latest from oslo-incubator. This allows
to get rid of the DnsMasqFilter (which was already replaced by
EnvFilter) in preparation for the havana release, as well as get a few
bugfixes.
All the changes are coming directly from the Oslo "rootwrap" module
sync.
In the iptables firewall driver, each port method (update_port_filter,
prepare_port_filter, remove_port_filter) makes O(N) calls, where
N=len(firewall.ports), to IptablesManager methods that update dozens
of data structures. When the firewall methods are called in sequence,
e.g., by SecurityGroupAgentRpcMixin, the calls to IptablesManager's
methods start to add up.
This patch changes IptablesFirewallDriver to defer and coalesce calls
to IptablesManager. Now a sequence of M port method calls results in
O(N) calls to IptablesManager methods instead of O(N*M) as before.
Tom Fifield [Sun, 28 Jul 2013 18:35:01 +0000 (11:35 -0700)]
Update references with new Mailing List location
Yesterday, openstack@lists.launchpad.org was migrated with
all users to openstack@list.openstack.org.
This patch updates references to the old mailing list with the
new, to ensure that people encountering them don't accidentally
try and join the old list!
Fix creation of trusted queues for the NVP plugin.
Currently if an admin tries to create a trusted queue, Neutron will
fail with MissingDSCPForTrusted exception. However, the NVP semantic
is exactly the opposite, namely the DSCP field must be specified for
untrusted queues and omitted trusted ones.
Deal with intermittent OverflowError in gate-neutron-python26
This occurence looks like is related to a failure in
utils.execute. This patch attempts to deal with the error
by mocking out Popen.communicate altogether.
Gary Kotton [Thu, 20 Jun 2013 11:04:59 +0000 (11:04 +0000)]
Ensure that L3 managed port have status ACTIVE
Some plugins may set the port status as DOWN when it is created. This was not
updated when the port was actually up. This patch ensures that gateway and
router ports that are created will be set as ACTIVE when they are actually
up and running.
Ports that are attached to additional bridges in the OVS will only update the
port status as ACTIVE. There will be no tags set on the specific ports as this
will break the existing functionality.
* Defines logic and API for ServiceProvider - read-only entity
that admins provide in configuration and which is stored in memory
* ServiceType entity which maps to ServiceOfferings in new terms
is removed for now.
* Routed service insertion fixed to not to refer to service providers.
* In case configuration changes and some service providers are removed
then the resources must be cleanup in a special way (undeploy logical
resources). This is a matter of future work
* Add migration.
Jiajun Liu [Wed, 17 Jul 2013 03:00:23 +0000 (03:00 +0000)]
do not raise exception on ip address recycle operation
Currenty a exception will raise on ip address recycle operation if the ip
address doesn't belong to any allocation pool which will make user unable
to update port, even worse it will make user unable to create new port.
So do not raise exception if the ip address to be recycled doesn't belong
to any allocation, just delete it from the ip allocation table.
Code Review / openstack-build / neutron-build.git / log