After using api_replay to migrate the neutron data from NSX-V to NSX-T
we need to update the VM ports to use OpaqueNetwork instead of
DistributedVirtualPortgroup
Usage: nsxadmin -r ports -o nsx-migrate-v-v3
Output example:
Detaching old interface from VM ad02211d-25a1-4e0b-ab6e-ffee48c77077
Updated VM moref vm-59 spec - detached an interface
Attaching new interface to VM ad02211d-25a1-4e0b-ab6e-ffee48c77077
Updated VM moref vm-59 spec - attached an interface
Change-Id: Ie6b4c929257be9bed9701c9c2073a0e65cab9839
1. Upgrade ports with IPv4 address only
2. Delete previous internal metadata networks
3. Add list function for metadata proxy
4. Add more checking and logs
5. Pass required UUID from command-line
6. Refactor codes
DocImpact
Change-Id: I4e0f05b2dff9394cc6d0d567abf58507efaf6685
The utility: nsxadmin -r edges -o nsx-update --property appliances=True
will now update the requested edge deployment according to its' current availability zone.
It can be used when the availability zone definition or global definition of resource pool,
data stores or edge_ha changes.
Change-Id: I8d28fec3c95c272e581d63a8fd0f2618ffb26cb8
Delete a backend router edge, and move its' router/s to other edges.
Currently this utility does not support distributed routers
usage:
nsxadmin -r routers -o nsx-recreate --property edge-id=edge-307
Change-Id: Ib1ab84120aaae42dba884d4ba964a3bdd82df2fb
This utility can be used to move all the networks from a specific
DHCP edge, to another (new or existing) edge.
This should work also for VDR router DHCP edge.
Usage:
nsxadmin -r dhcp-binding -o nsx-recreate --property edge-id=<edge-Id>
Output example:
==== [NSX] Recreate Dhcp Edge ====
ReCreating NSXv Edge: edge-222
Deleting the old DHCP edge: edge-222
Moving network a7fd0856-923e-43a6-97c7-9980e7fabd08 to a new edge
Moving subnet ae9efc04-a685-497e-aab1-1dff9abacf9c to a new edge
Creating network a7fd0856-923e-43a6-97c7-9980e7fabd08 DHCP address group
Network a7fd0856-923e-43a6-97c7-9980e7fabd08 was moved to edge edge-228
Moving network 7a484242-0261-4888-ba77-41bb7bbd4f9d to a new edge
Moving subnet 412e89ce-7c69-494d-b525-c08c8828cdfd to a new edge
Moving subnet 139f7375-afb9-41dd-bdb7-c25af772a805 to a new edge
Creating network 7a484242-0261-4888-ba77-41bb7bbd4f9d DHCP address group
Network 7a484242-0261-4888-ba77-41bb7bbd4f9d was moved to edge edge-228
Change-Id: I97ba4abfe50d634f5ba5b137a64e021575db1ead
Update the rpc api devref docs to include an example of what a change
that includes a minor version increment looks like. I hope this will
help clarify for people what all is included in an API change that
requires a version bump.
Part of blueprint rpc-docs-and-namespaces.
Change-Id: I9c53d3518b200412701b19958d7cbf1ed03d643e
Replace URLs for workflow documentation to appropriate parts of the
OpenStack Project Infrastructure Manual.
Change-Id: I77aa4152a903a0f1f47de20bb1a006d29f5a1bf2
The devref docs had a placeholder file for rpc API docs. Now that
both a client side and server side interface have been converted from
the rpc compat layer to oslo.messaging APIs, add some docs that give
an overview of what the client and server sides look like.
Also include a section that describes the code layout of where you can
find client and server api implementations in the neutron code base.
It starts by discussing the DHCP agent related APIs.
Part of blueprint drop-rpc-compat.
Change-Id: Ib391958252077365a81bcb881ab27a078f71fdec
Add tests to verify that database migrations produce
the same schema as the database models.
Also for MySQL, check that all tables are configured to use InnoDB
as the storage engine.
These tests make use of the ModelsMigrationsSync test class from
oslo.db and the load_tests protocol from Python unittest.
Closes-bug: #1346444
Change-Id: Ic0e7eb37c30cc5e94cbdbddf07a6dc1ebf377c17
Remove intersphinx from the docs build as it triggers network calls that
occasionally fail, and we don't really use intersphinx (links other
sphinx documents out on the internet)
This also removes the requirement for internet access during docs build.
This can cause docs jobs to fail if the project errors out on
warnings.
Change-Id: I71e941e2a639641a662a163c682eb86d51de42fb
Related-Bug: #1368910
Adds the beginnings of documentation for the Firewall as a Service,
Loadbalancer as a Service, and VPN as a Service.
Part of blueprint developer-documentation
Change-Id: I5e46df2dc4f87f961490ee75791a7e825ea94e1e
* Discuss the WSGI layer of Neutron
* Describe the startup code that creates the WSGI application
* Briefly discuss the URL routing and resource creation
Change-Id: Id82a2a5679d7e29c0a19d1a20942a9249946b011
* Turns TESTING into a rst file, that we include in the developer
documentation, for instructions on how to run the unit tests.
* Link to a Vagrant project that sets up Neutron inside a VM.
* Adds a section for how to debug with Nose
* Add new section for Neutron Internals
* Neutron L2 Agent documentation - currently only OVS
* Make the Security Group API extension an example of how an API
extension is implemented
Implements bp developer-documentation
Change-Id: I9b452abc9da3b1a41ae65cff727967de0eab12fe
Several hyperlinks were incorrectly specified in one page of the docs.
These syntax typos have been fixed.
Change-Id: I1a4fe91ac05f51b71e01c001b76712752664ae74
Closes-Bug: #1268611
There is currently no useful developer-focused documentation in-tree
for Neutron. There are a smattering of useful documents on the
OpenStack wiki, however, there isn't a good organization to this
information, nor is there a condensed developer focus to a lot of it.
Some of the wiki pages are more proposals for features or bug fixes,
and there is a need for architecture, design, and code walk-through
documentation for Neutron to help with new (and existing) contribution.
This patch begins the process of adding developer documentation to Neutron.
It updates the main developer reference index.rst to pull in-line with what
Nova is doing, leaving some todo references for future patches. It also
adds a development.environment tutorial that is up-to-date with current
Neutron development, using tox/testr processes for running unit tests and
including a number of references to external wiki pages that have
instructions for using DevStack for OpenStack contribution/testing.
The next series of patches will add automodule documentation to the
developer reference for some of the major modules in Neutron.
Change-Id: I23aaa11d9a174f24242c49767b92540f5e25b48a
Addresses: blueprint quantum-developer-docs
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!
Change-Id: Id52268cc077bcc89e345a1cd28203ce2fce75db7
This change renames everything to Neutron while providing backwards
compatible adjustments for Grizzly configuration files.
implements blueprint: remove-use-of-quantum
Change-Id: Ie7d07ba7c89857e13d4ddc8f0e9b68de020a3d19
The quantum.quantum_plugin_base_v2 module had some good docstrings,
but there was no corresponding sphinx code that would generate
docs from them. There were also some syntax issues with the
sphinx markup in the docstrings.
This change adds sphinx directives so these docs will be auto-
generated. It also modifies the docstrings in the QuantumPluginBaseV2
methods so they are parsed by the Sphinx documentation generator
without any errors.
If this patch is accepted, a "Plugin API" link to these docs
will appear at
http://docs.openstack.org/developer/quantum/
Fixes bug 1186255
Change-Id: I96eddcc516d109766d7f4c52edd595748696b595
Use commit eaab5fae2502198e9fa57d0d90a7204a2bd83b16:
Merge "sort options to make --help output prettier"
(Wed Feb 13 12:52:14 2013 +0000)
Add processutils to quantum since impl_zmq depends on them.
Drop notifier.list_notifier that is not present in oslo.
Change-Id: I91d9ec05481b8c24da9fbee1ad4706ff56a3b7aa
Fixes: bug #1116290
Updating setup and version require code changes in the code base. This is done
here to support Id9c116a1e10e5c240913fae7a127110b806eff0f
Change-Id: I60b6dd6d684982e33de8fbf051a3dcaf98cb9b87
* Fixes LP1007132
* Adds keystone link
* removes __init__.py since doc/source is not a python module
Change-Id: I6a3234fa760ca23889e352735669547ad9afedf8
Implements the blueprint use-common-cfg
In order for the linuxbridge plugin to use the rpc code soon to be merged into
openstack-common, we need to parse our configuration using cfg. Here we
make the most simple, backwards compatible change in that direction.
The same is relevant for the openvswitch implementation
Fixes after comments.
Change-Id: I70fc1898a802cb4198f72741453283d114added2
bug 995283
Changes after initial comments
Removed spaces
Updates after comments
Remove white spaces
Fix text and remove empty files
Remove config.py
Updated to be similar to the keystone page
Updated afetr comments
Change-Id: If9240114ae31d7120c708cdcf883e8fe4c7d2bb2