os-odl-nofeature-ha overview and description

This document provides scenario level details for Euphrates 1.0 of deployment with the OpenDaylight SDN controller and no extra features enabled.

1. Introduction

This scenario is used primarily to validate and deploy a Newton OpenStack deployment with OpenDaylight, and without any NFV features enabled.

1.1. Scenario components and composition

This scenario is composed of common OpenStack services enabled by default, including Nova, Neutron, Glance, Cinder, Keystone, Horizon. Optionally and by default, Tacker and Congress services are also enabled. Ceph is used as the backend storage to Cinder on all deployed nodes.

All services are in HA, meaning that there are multiple cloned instances of each service, and they are balanced by HA Proxy using a Virtual IP Address per service.

OpenDaylight is also enabled in HA, and forms a cluster. Neutron communicates with a Virtual IP Address for OpenDaylight which is load balanced across the OpenDaylight cluster. Every Open vSwitch node is connected to every OpenDaylight for High Availability.

1.2. Scenario usage overview

Simply deploy this scenario by using the os-odl-nofeature-ha.yaml deploy settings file.

1.3. Limitations, Issues and Workarounds

• APEX-112:

  ODL routes local subnet traffic to GW

• APEX-149:

  OpenFlow rules are populated very slowly

• APEX-268:

  VMs with multiple floating IPs can only access via first NIC

• APEX-384:

  Not including odl_version in deploy settings causes error

• APEX-422:

  First nova instance DHCP request fails

1.4. References

For more information on the OPNFV Euphrates release, please visit http://www.opnfv.org/euphrates