Ensures that each attribute which is used by the policy engine is not
removed by the plugin when the 'fields' query parameter is specified.
This could be better achieved by not having the plugin perform this
selection, but as it is part of the plugin interface, it's probably better
not to introduce changes which alter it.
Because the openstack common project does not stick to latest pep8 rules,
I have to exclude some bad-ruled files in the tox.ini and run_tests.sh.
However pep8 does not support exclude option in the format quantum/openstack/common,
so I have to exclude some of openstack common files one by one.
Also, I have changed the Qunatum Context to base on the common context.
I does not update the setup.py in our openstack common dir and the one
under quantum top dir, since it should be maintained in a consistent way
across all of openstack projects.
After this introduction, we are ready for notification feature.
The router will simply use the QuantumManager which stores the instance
of the plugin being used by the Quantum server. Changes to unit tests
are for ensuring plugin instances are recycled across tests.
Gary Kotton [Sun, 8 Jul 2012 12:05:46 +0000 (08:05 -0400)]
Enable quantum agents to work with global cfg.CONF
This implements blueprint global-config-support
A common configuration parse function is used by the service and the agent.
In the case of the service, when loading the plugin, the configuration file
will be appended to the existing cfg.CONF (this was originally created when
quantum.conf was loaded).
In the case of the agent a global cfg.CONF will be created.
This task is a prerequisite for the RPC integration into Quantum.
Dan Wendlandt [Sun, 8 Jul 2012 19:34:22 +0000 (12:34 -0700)]
Fix v2 API policy checks when keystone is in use.
bug 1022032. There were significant errors in how
the policy framework was being invoked, but existing
tests did now show them, since they always invoked the
API with no keystone context. This patch fixes those
issues and add a significant amount of test coverage
simulating API calls with keystone enabled.
As part of this patch, we also needed to add a tenant-id
attribute to the subnet object. Furthermore, we
changed the API validation code to prevent tenant-id from
being changed with a PUT, since changing it after creation
could invalidate some of the create checks we're planning
on adding (e.g., that a port is being created on a network
owned by the same tenant).
This changeset adds a new parameter, 'allocation_pools' to the 'subnet'
resource of the Quantum v2 API.
Allows for creating and validation of subnets with multiple allocation pools.
This commit only deals with POST verb (subnet creation).
PUT verb (subnet update) will be dealt with in a subsequent commit.
Gary Kotton [Thu, 28 Jun 2012 10:26:10 +0000 (06:26 -0400)]
v2 support for the linux bridge plugin
blueprint lb-api-v2-support
Plugin support for the linuxbridge using the v2 API
1. The core_plugin in quantum.conf must be set to:
quantum.plugins.linuxbridge.LinuxBridgePluginV2.LinuxBridgePluginV2
2. By default the agent is v2. A configuration file entry 'target_v2_api'
in the section 'AGENT' can be set as False to support v1.
Gary Kotton [Sun, 1 Jul 2012 07:06:07 +0000 (03:06 -0400)]
Check if interface exists in bridge prior to adding.
This fixes bug 1019730. The fix for bug 1000406 ensures that return
values of shell commands are checked. The command
utils.execute(['brctl', 'addif', bridge_name, interface],
root_helper=self.root_helper)
would cause an exception if there was more than one attachment
on the network. The reason for this was the interface already existed
on the bridge.
Monty Taylor [Thu, 28 Jun 2012 14:45:35 +0000 (07:45 -0700)]
Use setuptools git plugin for file inclusion.
Fixes bug 1018833. We're looking at this as a possible pan-project
option instead of manual MANIFEST.in inclusion and then looking for
where the tarballs differ.
The allocation is done as follows (according to the value of
port['fixed_ips']):
- api_router.ATTR_NOT_SPECIFIED - Quantum will generate an IP address.
If a v4 subnet is defined then a v4 address will be generated. If
a v6 subnet is defined then a v6 address will be generated. If both are
defined then both v4 and v6 addresses will be generated.
- user configuration which may contain a list of the following:
- ip_address - the specific IP address will be generated
- subnet_id - an IP address from the subnet will be generated
Juliano Martinez [Mon, 18 Jun 2012 22:30:36 +0000 (19:30 -0300)]
Bug #1012418 - quantum agent for OVS does not install properly on Xen XCP
This change added the feature to package and install the ovs-quantum-agent inside XS and XCP,
added an option on Makefile to gen and install using python2.6 ( by default it will use 2.4 )
Jenkins [Thu, 21 Jun 2012 13:27:52 +0000 (13:27 +0000)]
Merge "Added iptables_manager ( based on openstack/linux_net.py ) This module will be the base library to implement security groups and generic firewall. It is an independent iptables module, made to be easy to package if used by agents and also inside quantum"
Juliano Martinez [Mon, 18 Jun 2012 14:00:45 +0000 (11:00 -0300)]
Added iptables_manager ( based on openstack/linux_net.py )
This module will be the base library to implement security
groups and generic firewall.
It is an independent iptables module, made to be easy to package
if used by agents and also inside quantum
Using quantum.agent.linux.utils
Added support to root_helper
Gary Kotton [Sun, 3 Jun 2012 11:55:09 +0000 (07:55 -0400)]
Implements the blueprint use-common-cfg for the quantum service.
More specifically uses global CONF for the quantum.conf file.
Added support for the RYU plugin (similar to ovs and lb,
which use non-global conf for plugins)
patch 27: clean up find_config_file
patch 28: for config file use old paths (plugin unit tests)
this hopefully will be replaced when we move to common
config file
patch 30: rebase and merge (utils.py and policy.py)
Gary Kotton [Tue, 19 Jun 2012 23:32:22 +0000 (16:32 -0700)]
Ensure unique mac address allocation.
This is the first part of bug 1008029
If the port command does not contain a MAC address then Quantum will generate
a random MAC address. The mac address will be saved in the database to ensure
that it is not used by another port on the same network.
Adds the policy openstack-common module and implements policy checks
for the v2 API. Note that this cut only addresses whole objects (i.e.,
a subnet or a network or a port), not specific fields within objects.
(This means that attributes are not filtered out based on policies.)
Implements blueprint authorization-support-for-quantum.
Removed all unused functions and imports from common/utils.py.
Patch set 2: Submitted same code by mistake
Patch set 3: removed commented code but inappropriate commit msg.
Patch set 4: removed commented code with appropriate commit msg. Removed pep8 changes for ucs plugin.
Roman Sokolkov [Fri, 15 Jun 2012 13:13:33 +0000 (17:13 +0400)]
Added vlan range management for OVS plugin
* Added integer config flags: vlan_min, vlan_max
* If vlan_min is larger than vlan_max log warn and use default values
* Changed test_vlan_map.py in favor removed definitions of VlanMap class
Removed use of argument action_prefix for Client. Also, made HOST, PORT and USE_SSL global. Signed-off-by: Harsh Prasad <prasad.tanay@gmail.com>
Change-Id: I93037b34fca89786778a2dcd8a3afc80df5687f8
- rename few attributes:
op_state -> status
additional_routes -> additional_host_routes
prefix -> cidr
- expand request body validation to indicate whether fields can be
specified during create and or update.
- add test cases to validate defaults, and input validation.
- update db_base_plugin_v2 to generate gateway_ip for subnet and mac
for port when unspecified.
- validate that tenant-id is only specified in req by admin users
- automatically set tenant-id based on request.context.tenant_id if needed
Clark Boylan [Fri, 8 Jun 2012 21:26:58 +0000 (14:26 -0700)]
Add build_sphinx options.
To better facilitate the building and publishing of sphinx
documentation by Jenkins we are moving all openstack projects with
sphinx documentation to a common doc tree structure. Documentation
goes in project/doc and build results go in project/doc/build.
Zhongyue Luo [Thu, 7 Jun 2012 02:20:25 +0000 (10:20 +0800)]
Quantum should use openstack.common.jsonutils
Implements blueprint use-common-jsonutils
1. Edit openstack-common.conf and import quantum/openstack/common/jsonutils.py
2. Remove json package imports and replace with jsonutils
3. Remove json related functions in common/utils.py
Dan Wendlandt [Wed, 6 Jun 2012 19:41:13 +0000 (12:41 -0700)]
Remove hardcoded version for pep8 from tools/test-requires
In email discussions we decided that the master branch should always
pull in the lastest version of the pep8 tool, which keeps us closest
to the real pep-8 document. Therefore, I'm removing the hardcoded
version here to match the lack of a pep8 version in tox.ini (which is
what the CI infrastructure uses when running the gating pep8 checks).
Note that your pep8 version will only update when you re-run
pip install --upgrade -r tools/test-requires .
Adds authentication support for Quantum. Generates a context object
and stuffs it into the 'quantum.context' variable in the WSGI environment.
This will be used in conjunction with authZ, later.
Dan Wendlandt [Tue, 5 Jun 2012 05:07:27 +0000 (22:07 -0700)]
Add common dir for shared agent code, add OVS lib.
bp quantum-agent-common
Adds a common directory that can be used for code shared by agents for
different plugins. Also seeds this directory with an OVS library,
removing that code from the openvswitch plugin itself. This code
can then be leveraged by other plugins (e.g., Ryu) who have similar code.
Also add a suite of mox-based tests for OVS lib.
Also add more powerful OVS flow expression builder as suggested by
salv-orlando, plus additional flow expression testing.
Note: the expectation is that this directory will be used for much of the
agent functionality that is similar to what Nova's nova/network/linux_net.py
file included, such as iptables manipulation, dhcp manipulation, etc.
People should be careful about changing code in this directory in a
non-backward compatible way, as other plugins may be using the code as well.
XS should not have the centos repo enabled by quantum this can break the system, also is possible to get the sqlalchemy from epel and avoid unneeded packages on the system.
It's running without any issue with 1.2, the exception problem was caused
by WebTest. We should use at least version 1.3.3 (supplied by Ubuntu 12.04 and Debian Wheezy)
Code Review / openstack-build / neutron-build.git / log