The following is a description of how to go from Packstack with traditional nova networking to Quantum. In the example below the OpenvSwitch plugin is used:
1. Terminate nova networking
service openstack-nova-network stop chkconfig openstack-nova-network off
2. Install quantum service and the Open vSwitch plugin
yum install openstack-quantum openstack-quantum-openvswitch
3. The Quantum installation scripts make use of keystone environment variables. Make sure that the administrator environment variables are set.
source /root/keystonerc_admin
4. Configure quantum service to use Open vSwitch (you can get the MySQL password from the Packstack answer file, see CONFIG_MYSQL_PW)
quantum-server-setup
5.1. The above script will ask if the nova parameters need to be updated. Restart the nova compute service. The script will configure Quantum as the networking module for Nova.
service openstack-nova-compute restart
5.2 Start the openvswitch service
service openvswitch start chkconfig openvswitch on
5.3 Create the integration bridge (for the private network)
ovs-vsctl add-br br-int
5.4 Create the external bridge (for the layer 3 agent)
ovs-vsctl add-br br-ex
5.5 Ensure that the interfaces are persistant after reboot. This is done by creating interface files, for example for br-int:
DEVICE=br-int DEVICETYPE=ovs TYPE=OVSBridge ONBOOT=yes
6. Start quantum service
service quantum-server start chkconfig quantum-server on
6.1 Start quantum agent
service quantum-openvswitch-agent start chkconfig quantum-openvswitch-agent on
7. In order for the IPAM to take place one needs to invoke the DHCP agent. Use the DHCP setup tool
quantum-dhcp-setup
7.1. Start DHCP agent
service quantum-dhcp-agent start chkconfig quantum-dhcp-agent on
8. In order to support floating IP's one need to invoke the Layer 3 agent. Use the L3 agent setup tool
quantum-l3-setup
8.1. Start the L3 agent
service quantum-l3-agent start chkconfig quantum-l3-agent on
9. Ensure that the openvswitch cleanup utility is enabled (this is used after reboot to ensure that device management of the quantum agents is not affected by the fact that the openvswitch creates the interfaces at boot)
chkconfig quantum-ovs-cleanup on
10. Create a Quantum endpoint with keystone
keystone service-create --name=quantum --type=network --description="Quantum Service" keystone endpoint-create --region RegionOne --service-id<ID> --publicurl "http://127.0.0.1:9696" --adminurl "http://127.0.0.1:9696" --internalurl "http://127.0.0.1:9696"
11. Create a keystone tenant and user.
11.1 Create the keystone tenant
keystone tenant-list # Record 'services' tenant ID keystone user-create --name=quantum --email=quantum@example.com --tenant-id <services_ID>
11.2 Add the quantum user to the admin role
keystone role-list # Record 'admin' role keystone user-list # Record 'quantum' user ID keystone user-role-add --user_id <quantum_ID> --role_id <admin_ID> --tenant_id <services_ID>
12. Now one is able to start to use the Quantum CLI
12.1 Create a private network
quantum net-create private
12.2 Create a subnet
quantum subnet-create private 10.0.0.0/24
13. Validate that a port has been created by the DHCP agent (quantum port-list). This port will have IP address 10.0.0.2. The gateway will 10.0.0.1.
14. At this stage VM's can be deployed and they will receive IP addresses from the DHCP service.