Bug 911101
Summary: | Going from packstack to Quantum | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Gary Kotton <gkotton> |
Component: | doc-Getting_Started_Guide | Assignee: | Stephen Gordon <sgordon> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ecs-bugs |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 2.0 (Folsom) | CC: | alyoung, bloch, breeler, rkukura, sgordon |
Target Milestone: | --- | Keywords: | Documentation, Triaged |
Target Release: | 2.1 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-04-11 06:58:14 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 896197 |
Description
Gary Kotton
2013-02-14 11:18:43 UTC
Please see - https://fedoraproject.org/wiki/Packstack_to_Quantum Which steps need to be run on every compute node versus only the networking node (I assume this concept only applies in the "destination state")? We also seem to assume that the desired plugin is openvswitch, I thought we supported at least one of the others too? There are number of issues: 1. Steps on compute node: i. if nova networking is running then stop the service (step 1) ii. install and start ovs agent (step 3) iii. run quantum-node-setup (step 4 needs to be done before running this script - this sets the correct environment variables) iv. restart nova compute v. ensure that nova compute can communicate with quantum service (ensure that traffic to port 9696 passes) 2. All of the plugins that are part of the packaging are supported. We have tested linuxbridge and openvswitch Sorry Gary, few more questions. For the most part this is basically the same as setting up Quantum for the first time except that we stop/disable nova-network right? I notice it includes both of these steps: ovs-vsctl add-br br-int ovs-vsctl add-br br-ex As we don't have namespaces working right am I correct in believing this would be on differing machines (we do have both in the instructions in the guide but in separate sections, one for L3 and one for DHCP)? Is 6.5 actually necessary? On my system when I rebooted the bridges still appeared to be there (though I'm not sure if they should have had an IP or not?) as well as a tap device? Thanks in advance, as you can probably tell I'm considering whether this should be a separate section or intertwined with the normal setup for Quantum (probably as a prerequisite). Packstack adds iptables rules to accept connections to the services' APIs. We need to do this for quantum-server as well: iptables -t filter -I INPUT -p tcp -m tcp --dport 9696 -j ACCEPT iptables-save > /etc/sysconfig/iptables > As we don't have namespaces working right am I correct in believing this would > be on differing machines (we do have both in the instructions in the guide but > in separate sections, one for L3 and one for DHCP)? The Host that is running the L3 agent requires: ovs-vsctl add-br br-int ovs-vsctl add-br br-ex The Host that has the DHCP agent running requires: ovs-vsctl add-br br-int The "br-int" is used to maintain all of the Quantum ports that are created. > Is 6.5 actually necessary? No. This is also relevant for 6.3 and 6.4. > On my system when I rebooted the bridges still appeared to be there (though I'm > not sure if they should have had an IP or not?) as well as a tap device? The ovs-vsctl add-br <name> only needs to be done once. The OVS has an internal database that maintains all of the devices that have been attached and created on the OVS. (If you recall we added in the OVS cleanup utility to purge these devices at reboot) commit 9bc517b3b7799870f712c1b67e4195b4ce578fba Author: Stephen Gordon <sgordon> Date: Wed Mar 13 10:49:30 2013 -0400 BZ#911101 - Added inline steps for switching to Quantum. Added steps for disabling Nova Networking (in preparation for switch to OpenStack Networking) inline with instructions for deploying OpenStack Networking. Also expanded on description of how/why to use ovs-vsctl to create the br-int and br-ex bridges. Change-Id: I9ff7c231ee4943514ce74e70a61a4717a9e6e2af |