Changes to the OpenStack installation
by James Denton
Learning OpenStack Networking (Neutron) - Second Edition
- Learning OpenStack Networking (Neutron) Second Edition
- Table of Contents
- Learning OpenStack Networking (Neutron) Second Edition
- Credits
- About the Author
- About the Reviewers
- www.PacktPub.com
- Preface
- 1. Preparing the Network for OpenStack
- 2. Installing OpenStack
- System requirements
- Initial network configuration
- Initial steps
- Installing OpenStack
- Summary
- 3. Installing Neutron
- 4. Building a Virtual Switching Infrastructure
- Virtual network devices
- Network types supported by Neutron
- Choosing a plugin and driver
- Visualizing traffic flow when using LinuxBridge
- Visualizing the traffic flow when using Open vSwitch
- Configuring the ML2 networking plugin
- Configuring the LinuxBridge driver and agent
- Configuring the Open vSwitch driver and agent
- Summary
- 5. Creating Networks with Neutron
- Network management
- Neutron ports
- Attaching instances to networks
- Exploring how instances get their addresses
- Exploring how instances retrieve their metadata
- Summary
- 6. Managing Security Groups
- Security groups in OpenStack
- An introduction to iptables
- Working with security groups
- Managing security groups in the CLI
- Creating security groups in the CLI
- Deleting security groups in the CLI
- Listing security groups in the CLI
- Showing the details of a security group in the CLI
- Updating security groups in the CLI
- Creating security group rules in the CLI
- Deleting security group rules in the CLI
- Listing security group rules in the CLI
- Showing the details of a security group rule in the CLI
- Applying security groups to instances and ports in the CLI
- Removing security groups from instances and ports in the CLI
- Managing security groups in the CLI
- Implementing security group rules
- Working with security groups in the dashboard
- Disabling port security
- Summary
- 7. Creating Standalone Routers with Neutron
- Routing traffic in a cloud
- Installing and configuring the Neutron L3 agent
- Router management in the CLI
- Creating routers in the CLI
- Working with router interfaces in the CLI
- Listing the interfaces attached to routers
- Deleting internal interfaces
- Clearing the gateway interface
- Listing routers in the CLI
- Displaying router attributes in the CLI
- Updating router attributes in the CLI
- Deleting routers in the CLI
- Network address translation
- Floating IP management
- Demonstrating traffic flow from an instance to the Internet
- Setting the foundation
- Creating an external provider network
- Creating a Neutron router
- Attaching the router to the external network
- Testing gateway connectivity
- Creating an internal network
- Attaching the router to the internal network
- Creating instances
- Verifying instance connectivity
- Observing default NAT behavior
- Assigning floating IPs
- Reassigning floating IPs
- Router management in the dashboard
- Summary
- 8. Router Redundancy Using VRRP
- 9. Distributed Virtual Routers
- Distributing routers across the cloud
- Installing and configuring Neutron components
- Routing east-west traffic between instances
- Centralized SNAT
- Floating IPs through distributed virtual routers
- Summary
- 10. Load Balancing Traffic to Instances
- Fundamentals of load balancing
- Integrating load balancers into the network
- Installing LBaaS
- Load balancer management in the CLI
- Building a load balancer
- Load balancer management in the dashboard
- Summary
- 11. Firewall as a Service
- Enabling FWaaS
- Firewall Management in the CLI
- Managing firewall rules
- Managing firewall policies
- Creating a firewall policy in the CLI
- Deleting a firewall policy in the CLI
- Listing firewall policies in the CLI
- Showing the details of a firewall policy in the CLI
- Updating a firewall policy in the CLI
- Inserting rules into firewall policies in the CLI
- Removing rules from firewall policies in the CLI
- Managing firewalls
- Creating a firewall rule
- Creating a firewall policy
- Creating a firewall
- Demonstrating traffic flow through a firewall
- Summary
- 12. Virtual Private Network as a Service
- A. Additional Neutron Commands
- B. Virtualizing the Environment
- Index
OpenStack can run in a virtualized environment, but various components must be tuned accordingly. The configuration is not optimal but should provide an experience that is acceptable for demonstration purposes.
After the OpenStack installation is complete, a change must be made to the Nova configuration on the virtual machines running the nova-compute service before instances can be booted. Software-based virtualization must be enabled in place of the faster, hardware-based KVM hypervisor.
On the compute node virtual machines, edit the auxiliary Nova configuration file at /etc/nova/nova-compute.conf and set virt_type to qemu from kvm:
[libvirt] ... virt_type=qemu
Restart the nova-compute service on both the compute nodes with the following command:
# service nova-compute restart
Due to the lack of flexibility in configuring tagged networks with VirtualBox, the external GATEWAY_NET provider network that was configured in Chapter 7, Creating Standalone Routers with Neutron, must be configured as a flat network. To enable the use of flat networks, the flat_networks configuration option in the ML2 configuration file must be updated.
Using a text editor, update the flat_networks configuration option within the [ml2_type_flat] section of the ML2 configuration file on all hosts with the following:
[ml2_type_flat] ... flat_networks = physnet2
For reference, the ML2 plugin configuration file can be found at /etc/neutron/plugins/ml2/ml2_conf.ini.
Restart the neutron-server service on the controller node for the changes to take effect.
# service neutron-server restart
Note
When creating the GATEWAY_NET network, be sure to use the --provider:network_type=flat and --provider:physical_network=physnet2 options rather than vlan. Your workstation should be able to access floating IPs thanks to the VirtualBox host-only network configuration implemented earlier in this appendix.
-
No Comment