x/vmware-nsx
Code Issues Proposed changes
edad9f26e0
vmware-nsx/setup.cfg

125 lines
6.0 KiB
INI
Raw Normal View History

Move to pbr. Closes bug 1179007 Change-Id: I3666e373389da6ad9a21a195a42918d4dec50cb5
2013-04-28 21:41:09 -07:00
[metadata]
VMware: fix gitreview Fix the correct repo Change-Id: I1deed42fb003f06bc97634e3908c6d82c8620e85
2014-12-20 23:20:48 -08:00
name = vmware-nsx
summary = VMware NSX library for OpenStack projects
Move to pbr. Closes bug 1179007 Change-Id: I3666e373389da6ad9a21a195a42918d4dec50cb5
2013-04-28 21:41:09 -07:00
description-file =
Rename README to README.rst README.rst seems to be more standard accross OpenStack modules. Also add it to the manifest. Fix a typo in the manifest. Fixes: LP Bug #1186518 Change-Id: Ib04f44a1186d3793f5fca39c0c29d74a78a52faf
2013-05-31 12:00:26 +02:00
README.rst
Move to pbr. Closes bug 1179007 Change-Id: I3666e373389da6ad9a21a195a42918d4dec50cb5
2013-04-28 21:41:09 -07:00
author = OpenStack
Change openstack-dev to openstack-discuss Mailinglists have been updated. Openstack-discuss replaces openstack-dev. Change-Id: I5903e21d4baf9d15b7437c8fbd10337c5b176e8b
2018-12-04 17:18:23 +08:00
author-email = openstack-discuss@lists.openstack.org
Use https for *.openstack.org references The openstack.org pages now support https and our references to the site should by default be one signed by the organization. Change-Id: I0448c7bc0294db867bc1766da7aaf07912575dbe
2017-02-06 13:10:20 -08:00
home-page = https://launchpad.net/vmware-nsx
Move to pbr. Closes bug 1179007 Change-Id: I3666e373389da6ad9a21a195a42918d4dec50cb5
2013-04-28 21:41:09 -07:00
classifier =
Environment :: OpenStack
Intended Audience :: Information Technology
Intended Audience :: System Administrators
License :: OSI Approved :: Apache Software License
Operating System :: POSIX :: Linux
VMware: fix gitreview Fix the correct repo Change-Id: I1deed42fb003f06bc97634e3908c6d82c8620e85
2014-12-20 23:20:48 -08:00
Programming Language :: Python :: 3
Dropping the py35 testing All the integration testing has been moved to Bionic now[1] and py3.5 is not tested runtime for Train or stable/stein [2][3]. As per below ML thread, we are good to drop the py35 testing now: http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005097.html [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004647.html [2] https://governance.openstack.org/tc/reference/runtimes/stein.html [3] https://governance.openstack.org/tc/reference/runtimes/train.html Depends-On: I1b0496d3048f832cd60be70703a23cc712f8693d Change-Id: I071bd473617691ee72e29547e320dd8d9781ee75
2019-04-22 06:33:12 -06:00
Programming Language :: Python :: 3.6
update for python3 train jobs Change-Id: Ic104e1a67e69a2e06fb47db23896a14cacf9ca24
2019-07-10 11:03:47 -06:00
Programming Language :: Python :: 3.7
Move to pbr. Closes bug 1179007 Change-Id: I3666e373389da6ad9a21a195a42918d4dec50cb5
2013-04-28 21:41:09 -07:00
[files]
packages =
VMware: fix gitreview Fix the correct repo Change-Id: I1deed42fb003f06bc97634e3908c6d82c8620e85
2014-12-20 23:20:48 -08:00
vmware_nsx
Exclusive Router Support Exclusive router is the router who exclusivly occupies one edge. You can create an exclusive router with "--router_type exclusive" For distributed router, it would always be exclusive router. Change-Id: Ice8cbc20912bc9becc5a82a646c76b9153418189 DocImapct:
2014-11-03 10:22:46 +08:00
[entry_points]
Add check-nsx-config to console scripts This script is moving from openstack/neutron to stackforge/vmware-nsx, and should therefore be installed with the latter package. Change-Id: If1f1a3b55d5e68658f63a759dbad7e616ed14eca
2015-03-03 12:56:27 -08:00
console_scripts =
Move vmware_nsx/neutron/plugins/vmware to vmware_nsx This is part of new vmware_nsx directory structure proposed in https://goo.gl/GdWXyH. Change-Id: I60d6ef62eb724df71dfda90137e00f107e220971
2015-09-14 18:51:57 -07:00
neutron-check-nsx-config = vmware_nsx.check_nsx_config:main
Move python_nsxadmin out of a top-level namespace It is not a good idea to have a top-level "tools" namespace, this name is too generic and already taken in PyPi (see https://pypi.python.org/pypi/tools). This patch moves python_nsxadmin to the vmware_nsx.tools namespace, adjusting all imports and making sure setup.cfg is adapted accordingly. Change-Id: I75922db2010194fe59db424cc4615c7ba57c1b81
2015-12-17 15:34:45 -07:00
nsxadmin = vmware_nsx.shell.nsxadmin:main
Rename api-replay to nsx-migration Change-Id: I2a8889119b52123427a4ae269cc1fb669375c36e
2017-05-10 18:14:56 +03:00
nsx-migration = vmware_nsx.api_replay.cli:main
Initialize alembic branches for vmware-nsx repo Add alembic migration branch for vmware-nsx repo. Scripts for new tables owned by vmware-nsx must now be added here. Partially-Implements: blueprint online-schema-migrations Change-Id: Ia3b805bb7a4583c96c61f322a45a91db0d67cc9c
2015-08-13 07:52:01 -07:00
neutron.db.alembic_migrations =
Move vmware_nsx/neutron/db to vmware_nsx/db This is part of new vmware_nsx directory structure proposed in https://goo.gl/GdWXyH. Change-Id: I50468e8ecf81a636ac6a0f195c75b4bef25423b4
2015-09-14 16:45:18 -07:00
vmware-nsx = vmware_nsx.db.migration:alembic_migrations
NSX: Move DB models as part of core vendor decomposition As part of core vendor decomposition, this patch moves the models from neutron repository to vmware-nsx repository. Change-Id: I99f358af73fd80246aea0c40ecbeb8ce84f5453d Depends-On: I5d5b0acf34417889c2a449f22b92fd105697d90d Partial-bug: #1483453
2015-08-10 09:45:24 -07:00
neutron.core_plugins =
Add vmware_nsxv entry_point in setup If config neutron.core_plugins values for vmware_nsx.plugin.NsxVPlugin. It throw warning for 'stevedore.named [-] Could not load vmware_nsx.plugin.NsxVPlugin'. So,Add vmware_nsx vmware_nsxv vmware_nsxv3 and vmware_dvs entry_point in neutron.conre_plugins group. Change-Id: Ie2a5a4d00bd15ad838737948e2eb8eec69f3303b
2017-05-05 09:19:56 +08:00
vmware_nsx = vmware_nsx.plugin:NsxPlugin
vmware_nsxv = vmware_nsx.plugin:NsxVPlugin
vmware_nsxv3 = vmware_nsx.plugin:NsxV3Plugin
NSX-Policy: Skeleton for the new NSX Policy plugin Change-Id: Ia3195293270ceb3af1f14fa280de43019ca44b7f
2018-08-30 15:12:04 +03:00
vmware_nsxp = vmware_nsx.plugin:NsxPolicyPlugin
Add vmware_nsxv entry_point in setup If config neutron.core_plugins values for vmware_nsx.plugin.NsxVPlugin. It throw warning for 'stevedore.named [-] Could not load vmware_nsx.plugin.NsxVPlugin'. So,Add vmware_nsx vmware_nsxv vmware_nsxv3 and vmware_dvs entry_point in neutron.conre_plugins group. Change-Id: Ie2a5a4d00bd15ad838737948e2eb8eec69f3303b
2017-05-05 09:19:56 +08:00
vmware_dvs = vmware_nsx.plugin:NsxDvsPlugin
NSX TVD: V, T and simple DVS Coexist in the same plugin Introduce a plugin that can work with all of the VC and NSX offerings under the same umbrella of a single plugin. Co-Authored-By: Adit Sarfaty <asarfaty@vmware.com> Change-Id: I0449d64e3cf79b7a3a846dacba95e8854d53bdf8
2017-11-20 00:28:37 -08:00
vmware_nsxtvd = vmware_nsx.plugin:NsxTVDPlugin
Add firewall_drivers entry_point in setup Add firewall_drivers entry_point for vmware_edge. Change-Id: I25aa8fb2620ccbf6cdc19a711022c82bea70919d
2017-05-13 15:37:25 +08:00
firewall_drivers =
NSX|P FWaaS V2 support Adding FWaaS support for the Policy plugin, implementing hte NSX gateway policy Depends-on: I97bcbd99fcced02592a6e5f10d0d43a3e99efbe6 Change-Id: I486a6f4ab766233942008b5677722fb14b8553d7
2019-01-31 15:51:08 +02:00
vmware_nsxp_edge_v2 = vmware_nsx.services.fwaas.nsx_p.edge_fwaas_driver_v2:EdgeFwaasPDriverV2
NSX|V: FWaaS-V2 driver This patch adds a driver for FWaaS V2 support in the NSX-V plugin. It supports setting firewall rules per router interface port on the router edge firewall. In addition, the FWaaS TVD driver will now support NSX-V as well. The driver code is a combination of the NSX-V3 FWaas-V2 code, and the old NSX-V FWaaS-V1 code that is being deleted. Change-Id: Iacc7eaff0c70b68156516008cf0277c154edd76b
2018-11-26 14:55:49 +02:00
vmware_nsxv_edge_v2 = vmware_nsx.services.fwaas.nsx_v.edge_fwaas_driver_v2:EdgeFwaasVDriverV2
NSX|v3: FWaaS v2 support FWaaS V2 support in NSX-v3. Support different firewall group per router interface port for igress/egress. limitation: cannot support egress rules with source ip, or ingress rules with destination ips. Depends-on: I2a37be5518bfc8124ffca2ab05f684d8c1c3d673 Change-Id: I3ed70fa48d078bed15f30e855b73bdfb11d11c6e
2017-08-21 13:18:20 +03:00
vmware_nsxv3_edge_v2 = vmware_nsx.services.fwaas.nsx_v3.edge_fwaas_driver_v2:EdgeFwaasV3DriverV2
TVD: Update devstack doc with different services Change-Id: Iaf6fb4227df7c919d6bd757a8b47d1c96b289758
2017-12-24 14:26:30 +02:00
vmware_nsxtvd_edge_v2 = vmware_nsx.services.fwaas.nsx_tv.edge_fwaas_driver_v2:EdgeFwaasTVDriverV2
Add support for L2 gateway service plugin This patch adds the service plugin module which integrates the networking-l2gw APIs with NSX. This module is the common framework for the Layer 2 gateway support for NSX-T and NSX-V backends. The corresponding backend drivers will be controlled via the config parameter introduced here. This parameter will be configured with the class path to the backend driver. Backend drivers will be responsible for adding backend-specific logic. The corresponding backend drivers for NSX-T and NSX-V will be addressed in separate follow up patches. Change-Id: If997df17a1379a3775d29c1377f0f4e1ce9be328 Partial-bug: #1481087
2015-08-01 01:13:22 -07:00
neutron.service_plugins =
NSX|V add qos support for networks Add support for the qos service in NSX|V, including: - Attach/Detach qos policy to a new or updated network - Allow qos configuration on a backend network only, and only if use_dvs_features is True - Update the bw limitations on the edge through the dvs - Update the networks bw limitations when a policy or rule changes through the QoS notification driver Change-Id: Icee25b59e8e0f3c1c093077b631250a908e127c1
2016-03-15 11:51:28 +02:00
vmware_nsxv_qos = vmware_nsx.services.qos.nsx_v.plugin:NsxVQosPlugin
TVD: Add service plugins to separate list results Adding service plugins for QoS, VPNaaS and L2Gateway and updating the BGP plugin to prevent users from getting objects belonging to a different plugin Change-Id: I3545c3acefaf50ca6937a0b7a65c131c569317cd
2018-02-20 10:14:43 +02:00
vmware_nsxtvd_l2gw = vmware_nsx.services.l2gateway.nsx_tvd.plugin:L2GatewayPlugin
vmware_nsxtvd_qos = vmware_nsx.services.qos.nsx_tvd.plugin:QoSPlugin
vmware_nsxtvd_vpnaas = vmware_nsx.services.vpnaas.nsx_tvd.plugin:VPNPlugin
NSX|V3: VPN connection status update The VPNaaS plugin expects the driver to update the connection status from a separate process/thread/agent. When the user requests a connection/list, the status is retrived from the VPNaaS DB, without calling the driver. To avoid adding a process to actively query and update all connections statuses, this patch creates a new VPNaaS plugin, to be used instead of hte default one. This plugin (vmware_nsx_vpnaas) will issue a get-statuses call to the driver, update the current statuses in the DB, and call the original plugin. Change-Id: Ib750bfb8f0c8ad12265fa71506182ff5d7e8030a
2018-08-13 09:51:24 +03:00
vmware_nsx_vpnaas = vmware_nsx.services.vpnaas.nsx_plugin:NsxVPNPlugin
NSX|V3 add qos support for ports Add support for the qos service in NSX|V3, including: - Attach/Detach qos policy to a new or updated port - Allow qos configuration on ports with internal networks only - Update the switch profile with the BW limitations and tags through the qos notification driver - Add a new mapping db table to link the policy id and the nsx-v3 switch profile id For this to work, the following configuration should appear under the 'qos' section in the neutron.conf: notification_drivers = vmware_nsxv3_message_queue Change-Id: I4016de756cebe0032e61d3c2a5250527e44b49e4
2016-03-23 11:56:44 +02:00
neutron.qos.notification_drivers =
vmware_nsxv3_message_queue = vmware_nsx.services.qos.nsx_v3.message_queue:NsxV3QosNotificationDriver
Fix IPAM drivers entry point in setup.cfg Change-Id: If45878f800bb669595d77bbb56823f7c2f026036
2017-01-10 09:56:21 +02:00
neutron.ipam_drivers =
NSX|v add IPAM driver to setup.cfg This will allow simpler configuration of the ipam_driver in the neutron.cong Change-Id: Icc81117ab778528b901a9eeaad152a507acad0c2
2016-12-08 14:32:45 +02:00
vmware_nsxv_ipam = vmware_nsx.services.ipam.nsx_v.driver:NsxvIpamDriver
NSX|V3 IPAM support The NSX-V3 plugin will use the NSX-V3 backend IPAM. An IP pool will be created for each subnet, and port IPs will be allocated from this pool. The current backend limitation is that we cannot allocate a specific IP, so port create/update with fixed_ips will fail, unless the requested ip is the subnet gateway ip. To enable this option set 'ipam_driver = vmware_nsxv3_ipam' in the neutron.conf Change-Id: I5263555cbb776018a5d01f19d0997fd2adf6483d
2016-12-11 10:13:21 +02:00
vmware_nsxv3_ipam = vmware_nsx.services.ipam.nsx_v3.driver:Nsxv3IpamDriver
TVD IPAM support Adding an IPAM driver for the TVD plugin which will redirect the requests to the V/T driver. Change-Id: Iea48c7de053b0e7545fdae2a8e38c7b489d61409
2018-02-21 10:06:11 +02:00
vmware_nsxtvd_ipam = vmware_nsx.services.ipam.nsx_tvd.driver:NsxTvdIpamDriver
NSXV+NSXV3: Add support for dns-integration extension One can enable DNS integration for the upstream neutron DNS integration extension by setting: nsx_extension_drivers = vmware_nsxv_dns (for NSXV) nsx_extension_drivers = vmware_nsxv3_dns (for NSXV3) Change-Id: Id100f8034e602d92310d22f900c48d9dfbe59a8d
2017-01-12 10:11:46 -08:00
vmware_nsx.extension_drivers =
vmware_nsxv_dns = vmware_nsx.extension_drivers.dns_integration:DNSExtensionDriverNSXv
vmware_nsxv3_dns = vmware_nsx.extension_drivers.dns_integration:DNSExtensionDriverNSXv3
NSX|P dns integration support based on the v3 integration Change-Id: Ie726525c7b1cd4006b932b280634df27b192db4e
2019-01-13 10:49:26 +02:00
vmware_nsxp_dns = vmware_nsx.extension_drivers.dns_integration:DNSExtensionDriverNSXp
DVS: Add support for dns-integration extension One can enable DNS integration for the upstream neutron DNS integration extension by setting: nsx_extension_drivers = vmware_dvs_dns Closes-Bug: #1727626 Change-Id: If776d21679acfa2abf8018a8f6f19b58be24cb4b
2017-10-26 10:29:41 +02:00
vmware_dvs_dns = vmware_nsx.extension_drivers.dns_integration:DNSExtensionDriverDVS
Exclusive Router Support Exclusive router is the router who exclusivly occupies one edge. You can create an exclusive router with "--router_type exclusive" For distributed router, it would always be exclusive router. Change-Id: Ice8cbc20912bc9becc5a82a646c76b9153418189 DocImapct:
2014-11-03 10:22:46 +08:00
vmware_nsx.neutron.nsxv.router_type_drivers =
Divide vmware_nsx/plugins into plugin-specific subdirectories This patch will create: vmware_nsx/plugins/dvs for DVS specific files vmware_nsx/plugins/nsx_mh for MH specific files vmware_nsx/plugins/nsx_v for nsx_v specific files vmware_nsx/plugins/nsx_v3 for nsx_v3 specific files also move vmware_nsx/vsphere/ to vmware_nsx/plugins/nsx_v/vsphere/. This is part of new vmware_nsx directory structure proposed in https://goo.gl/GdWXyH. Change-Id: I00ee12da2eea0add988bae3d4f3e12940ea829bb
2015-09-16 16:14:47 -07:00
shared = vmware_nsx.plugins.nsx_v.drivers.shared_router_driver:RouterSharedDriver
distributed = vmware_nsx.plugins.nsx_v.drivers.distributed_router_driver:RouterDistributedDriver
exclusive = vmware_nsx.plugins.nsx_v.drivers.exclusive_router_driver:RouterExclusiveDriver
Automatically generate vmware-nsx configuration files This patch adds support to automatically generate config files for vmware-nsx repo using oslo config generator[1] for all VMware plugins. Tox can be used to generate a sample config file using the following command: tox -e genconfig This will generate a config file "nsx.ini.sample" under vmware-nsx/etc/ folder. This patch also modifies devstack scripts to use the auto-generated config files and adds more information to help texts in config modules. [1] http://docs.openstack.org/developer/oslo.config/generator.html Change-Id: Iff4ea37b52616295b262ead53947acb5b0cd9cd7 Partial-Bug: #1568215
2016-04-06 12:02:31 -07:00
oslo.config.opts =
nsx = vmware_nsx.opts:list_opts
Convert policy.json into policy-in-code vmware-nsx specific policies are defined as policy-in-code. - vmware_nsx/policies/lsn.py, qos_queue.py and maclearning.py are moved from the neutron repo. - vmware_nsx/policies/providersecuritygroup.py is based on the difference between etc/policy.json and the old neutron policy.json - vmware_nsx/policies/security_group.py is based on etc/policy.d/security-groups.json - vmware_nsx/policies/network_gateway.py is based on etc/policy.d/network-gateways.json etc/policy.d/dynamic-routing.json and etc/policy.d/neutron-fwaas.json have no policies specific to vmware-nsx, so they can be dropped and we can use policy-in-code definitions in neutron-fwaas and neutron-dynamic-routing. etc/policy.d/routers.json and flow-classifier.json cannot be converted into policy-in-code because the default policies are different from those defined in neutron and networking-sfc. Note that etc/policy.d/routers.json now has policies which are different from the default policies defined in the neutron repo. (Others are clean up by this commit.) This commit depends on the following patches under review: (neutron-fwaas policy-in-code support) Depends-On: https://review.openstack.org/527282 (neutron-dynamic-routing policy-in-code support) Depends-On: https://review.openstack.org/625429 (networking-sfc policy-in-code support) Depends-On: https://review.openstack.org/625431 (Drop 3rd-party plugin specific policies) Depends-On: https://review.openstack.org/625394 Partially Implements: blueprint neutron-policy-in-code Co-Authored-By: Michal Kelner Mishali <mkelnermishal@vmware.com> Co-Authored-By: Adit Sarfaty <asarfaty@vmware.com> Change-Id: I96a9dbd759d54308abbc12ce65c97b06a76453cd
2018-12-17 01:03:57 +09:00
oslo.policy.policies =
vmware-nsx = vmware_nsx.policies:list_rules
neutron.policies =
vmware-nsx = vmware_nsx.policies:list_rules
NSX-V Service insertion support The service insertion feature allows us to redirect some of the NSX traffic to an external security vendor like Palo-Alto or checkpoint for advanced inspection. The implementation contains: Enable the flow classifier plugin, and use it to create redirect rules on NSX When the flow classifier plugin is initialized a new security group is created and added to the configured service profile When a vm port with port security is created/updated, it is added to this security group When the admin user create a flow classifier entry, a backed redirect rule will be created. DocImpact: new NSXV Configuration parameters: service_insertion_profile_id = <service profile id, i.e. serviceprofile-1> DocImpact: The flow classifier methods should be added to the policy.json as admin only Change-Id: I67a132d4b35764c6940516a8365a2749d574aad2
2016-06-09 13:35:53 +03:00
networking_sfc.flowclassifier.drivers =
vmware-nsxv-sfc = vmware_nsx.services.flowclassifier.nsx_v.driver:NsxvFlowClassifierDriver
OCS plugin + initial extensions support Create an openstack client plugin for vmware nsx, and add the some of the extensions suport: router-type, router-size, subnet dhcp-mtu and dns-search-domain and port provider security groups and vnic index Work for future patches: - More unit tests (provider-security-groups) - Add the rest of the extensions Change-Id: I5b335de000b310cbcbb9a2f81483fd28f8d9afea
2016-09-25 11:49:18 +03:00
openstack.cli.extension =
nsxclient = vmware_nsx.osc.plugin
openstack.nsxclient.v2 =
port_create = vmware_nsx.osc.v2.port:NsxCreatePort
port_set = vmware_nsx.osc.v2.port:NsxSetPort
router_create = vmware_nsx.osc.v2.router:NsxCreateRouter
router_set = vmware_nsx.osc.v2.router:NsxSetRouter
Add security group extensions to OSC Change-Id: Ic626c3efed3dfd90ae5045591f6949b2b81915b1
2016-11-03 15:48:35 +02:00
security_group_create = vmware_nsx.osc.v2.security_group:NsxCreateSecurityGroup
security_group_set = vmware_nsx.osc.v2.security_group:NsxSetSecurityGroup
OCS plugin + initial extensions support Create an openstack client plugin for vmware nsx, and add the some of the extensions suport: router-type, router-size, subnet dhcp-mtu and dns-search-domain and port provider security groups and vnic index Work for future patches: - More unit tests (provider-security-groups) - Add the rest of the extensions Change-Id: I5b335de000b310cbcbb9a2f81483fd28f8d9afea
2016-09-25 11:49:18 +03:00
subnet_create = vmware_nsx.osc.v2.subnet:NsxCreateSubnet
subnet_set = vmware_nsx.osc.v2.subnet:NsxSetSubnet
NSX TVD: V, T and simple DVS Coexist in the same plugin Introduce a plugin that can work with all of the VC and NSX offerings under the same umbrella of a single plugin. Co-Authored-By: Adit Sarfaty <asarfaty@vmware.com> Change-Id: I0449d64e3cf79b7a3a846dacba95e8854d53bdf8
2017-11-20 00:28:37 -08:00
project_plugin_create = vmware_nsx.osc.v2.project_plugin_map:CreateProjectPluginMap
project_plugin_show = vmware_nsx.osc.v2.project_plugin_map:ShowProjectPluginMap
project_plugin_list = vmware_nsx.osc.v2.project_plugin_map:ListProjectPluginMap
Plugin housekeeper Implements a generic mechanism to cleanup and fix various breakages and issues between neutron, plugin and backend. Also adds a housekeeping job which detects and handles broken DHCP edge issues. Change-Id: I5324befbe2c7740b8ed47e0a20586f8aca0726f1
2017-03-26 12:39:50 +03:00
vmware_nsx.neutron.nsxv.housekeeper.jobs =
error_dhcp_edge = vmware_nsx.plugins.nsx_v.housekeeper.error_dhcp_edge:ErrorDhcpEdgeJob
NSXv HK: recover broken backup edge appliances When there is a failure during the recycling of an edge appliace to the backup pool, the edge at the backend may still be attached to networks and use IP addresses which are free for reuse by Neutron. Housekeeping job should address such cases. Change-Id: I3a8ba622f742064bdc8906ba745da0a54a4576ac
2017-12-21 16:36:15 +02:00
error_backup_edge = vmware_nsx.plugins.nsx_v.housekeeper.error_backup_edge:ErrorBackupEdgeJob
NSX|V3: Add housekeeping jobs Adding houskeeper for NSX V3 including handling orphaned DHCP server, logical swithces, firewall sections & logical routers, and handling mismatched logical ports. Change-Id: Id5e038a5c713796a83e485343cdc1672d0c1fd24
2018-06-25 12:09:15 +03:00
vmware_nsx.neutron.nsxv3.housekeeper.jobs =
orphaned_dhcp_server = vmware_nsx.plugins.nsx_v3.housekeeper.orphaned_dhcp_server:OrphanedDhcpServerJob
orphaned_logical_switch = vmware_nsx.plugins.nsx_v3.housekeeper.orphaned_logical_switch:OrphanedLogicalSwitchJob
orphaned_logical_router = vmware_nsx.plugins.nsx_v3.housekeeper.orphaned_logical_router:OrphanedLogicalRouterJob
orphaned_firewall_section = vmware_nsx.plugins.nsx_v3.housekeeper.orphaned_firewall_section:OrphanedFirewallSectionJob
mismatch_logical_port = vmware_nsx.plugins.nsx_v3.housekeeper.mismatch_logical_port:MismatchLogicalportJob
NSX|V+V3: Octavia driver Implementing the Octavia support for NSX-V & NSX-T. Follow up patches will handle the TVD plugin, Status updates, and migration. Since Octavia is not (yet?) in the requirements, using a hack to allow unittests to be skipped. Co-Authored-by: Adit Sarfaty <asarfaty@vmware.com> Change-Id: Iadb24e7eadcab658faf3e646cc528c2a8a6976e5
2018-05-24 10:15:26 +03:00
octavia.api.drivers =
vmwareedge = vmware_nsx.services.lbaas.octavia.octavia_driver:NSXOctaviaDriver
Octavia driver: agent implementation The driver is loaded, then terminated whenever a request is issued. This behavior causes termination of the Octavia listener which is responsible to the processing of the driver status updates and statistics processing. The following change implements an agent which will execute the listener. Change-Id: I566aaa65df4ba7455577a539aa9eebb6cc36a099
2019-09-26 19:30:18 +03:00
octavia.driver_agent.provider_agents =
vmwareagent = vmware_nsx.services.lbaas.octavia.octavia_driver:vmware_nsx_provider_agent
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. Change-Id: I672fbd296e2b8f1da1eede74d6f0c7a26345cf74
2012-06-08 14:26:58 -07:00
[build_sphinx]
source-dir = doc/source
VMware: fix gitreview Fix the correct repo Change-Id: I1deed42fb003f06bc97634e3908c6d82c8620e85
2014-12-20 23:20:48 -08:00
build-dir = doc/build
all_files = 1
Remove pbr warnerrors in favor of sphinx check This change removes the now unused "warnerrors" setting, which is replaced by "warning-is-error" in sphinx releases >= 1.5 [1]. [1] http://lists.openstack.org/pipermail/openstack-dev/ 2017-March/113085.html Change-Id: Ie82fce03c73f4a78b557caecc5bcf4ad9c8b7cb1 Closes-Bug:#1693670
2018-02-01 13:46:45 +07:00
# warning-is-error = 1
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. Change-Id: I672fbd296e2b8f1da1eede74d6f0c7a26345cf74
2012-06-08 14:26:58 -07:00
VMware: fix gitreview Fix the correct repo Change-Id: I1deed42fb003f06bc97634e3908c6d82c8620e85
2014-12-20 23:20:48 -08:00
[upload_sphinx]
upload-dir = doc/build/html
Use babel to generate translation file Fixes bug 1103519 Following http://wiki.openstack.org/Translations to integrate transifex translation into quantum We added the empty file quantum/locale/quantum.pot to avoid the failure of the Jenkin's translation-jobs because git doesn't allow empty directory to be added into the repository. After this patch accepted, we need to do as below: 1. Make the transifex quantum project (https://www.transifex.com/projects/p/quantum/) as part of the openstack transifex project hub and give access to the transifex openstack Jenkins account. 2. Add the translation-jobs into openstack/openstack-ci-puppet for ceilometer. Change-Id: I329a8bdc51ed8a0e75399c592d3991b1ec06a855
2013-01-24 00:07:18 +08:00
[compile_catalog]
Update translation setup Follow new infra setup for translations, see spec http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_setup.html for full details. This basically renames vmware-nsx/locale/vmware-nsx.pot to vmware_nsx/locale/vmware_nsx.pot. For this we need to update setup.cfg. Update also domain name in _i18n.py. Let's remove the po and pot files in the outdated paths. The updated scripts work without them. So, we can just delete the files and once the infra script runs, an updated pot file together with translations will be imported automatically. Change-Id: Id4bade9ffd23c57153b415514c82b384fd0977aa
2016-01-29 01:28:08 +09:00
directory = vmware_nsx/locale
domain = vmware_nsx
Use babel to generate translation file Fixes bug 1103519 Following http://wiki.openstack.org/Translations to integrate transifex translation into quantum We added the empty file quantum/locale/quantum.pot to avoid the failure of the Jenkin's translation-jobs because git doesn't allow empty directory to be added into the repository. After this patch accepted, we need to do as below: 1. Make the transifex quantum project (https://www.transifex.com/projects/p/quantum/) as part of the openstack transifex project hub and give access to the transifex openstack Jenkins account. 2. Add the translation-jobs into openstack/openstack-ci-puppet for ceilometer. Change-Id: I329a8bdc51ed8a0e75399c592d3991b1ec06a855
2013-01-24 00:07:18 +08:00
[update_catalog]
Update translation setup Follow new infra setup for translations, see spec http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_setup.html for full details. This basically renames vmware-nsx/locale/vmware-nsx.pot to vmware_nsx/locale/vmware_nsx.pot. For this we need to update setup.cfg. Update also domain name in _i18n.py. Let's remove the po and pot files in the outdated paths. The updated scripts work without them. So, we can just delete the files and once the infra script runs, an updated pot file together with translations will be imported automatically. Change-Id: Id4bade9ffd23c57153b415514c82b384fd0977aa
2016-01-29 01:28:08 +09:00
domain = vmware_nsx
output_dir = vmware_nsx/locale
input_file = vmware_nsx/locale/vmware_nsx.pot
VMware: fix gitreview Fix the correct repo Change-Id: I1deed42fb003f06bc97634e3908c6d82c8620e85
2014-12-20 23:20:48 -08:00
[extract_messages]
keywords = _ gettext ngettext l_ lazy_gettext
mapping_file = babel.cfg
Update translation setup Follow new infra setup for translations, see spec http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_setup.html for full details. This basically renames vmware-nsx/locale/vmware-nsx.pot to vmware_nsx/locale/vmware_nsx.pot. For this we need to update setup.cfg. Update also domain name in _i18n.py. Let's remove the po and pot files in the outdated paths. The updated scripts work without them. So, we can just delete the files and once the infra script runs, an updated pot file together with translations will be imported automatically. Change-Id: Id4bade9ffd23c57153b415514c82b384fd0977aa
2016-01-29 01:28:08 +09:00
output_file = vmware_nsx/locale/vmware_nsx.pot
VMware: fix gitreview Fix the correct repo Change-Id: I1deed42fb003f06bc97634e3908c6d82c8620e85
2014-12-20 23:20:48 -08:00
[pbr]
autodoc_index_modules = 1
Prep for pbr warnerrors As per [1] the next version of pbr will properly support pbr/Sphinx warnerrors during doc builds. We should enable warnerrors upon the next pbr release and verify our doc build completes successfully. [1] http://lists.openstack.org/pipermail/openstack-dev/2016-June/097849.html Change-Id: I20cbbefb9dce05770dafa37a6ee1a59afc29c218
2016-06-24 08:12:39 -06:00
# NOTE(boden): enable and validate once a new version of pbr is released.
# More info can be found on the ML:
# http://lists.openstack.org/pipermail/openstack-dev/2016-June/097849.html
Copy Permalink