Compass4NFV Scenarios

This document introduces scenario descriptions for Euphrates 1.0 of deployment with no SDN controller and no feature enabled.

os-nosdn-nofeature-ha

This scenario is used to deploy an Ocata OpenStack deployment with Ceph Jewel, and without SDN controller nor any NFV feature enabled.

Scenario components and composition

This scenario includes a set of common OpenStack services which are Nova, Neutron, Glance, Cinder, Keystone, Heat, Ceilometer, Gnocchi, Aodh, Horizon. Ceph is used as the backend of Cinder on deployed hosts. HAproxy is used to balance all the services running on 3 control nodes behind a VIP (Virtual IP address).

Scenario usage overview

To deploy with this scenario, you just need to assign the os-nosdn-nofeature-ha.yaml to DHA file before deployment.

References

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

This document introduces scenario descriptions for Euphrates 1.0 of deployment with the OpenDaylight controller and no feature enabled.

os-odl-nofeature-ha

This scenario is used to deploy an Ocata OpenStack deployment with OpenDaylight Nitrogen, Ceph Jewel, and without any NFV feature enabled.

Scenario components and composition

This scenario includes a set of common OpenStack services which are Nova, Neutron, Glance, Cinder, Keystone, Heat, Ceilometer, Gnocchi, Aodh, Horizon. Ceph is used as the backend of Cinder on deployed hosts. HAproxy is used to balance all the services running on 3 control nodes behind a VIP (Virtual IP address). OpenDaylight will also be deployed in this scenario. ODL is also running in HA. Neutron communicates with ODL through a VIP.

Scenario usage overview

To deploy with this scenario, you just need to assign the os-odl-nofeature-ha.yaml to DHA file before deployment.

References

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

This document introduces scenario descriptions for Euphrates 1.0 of deployment with the OpenDaylight controller and SFC feature enabled.

os-odl-sfc-ha

This scenario is used to deploy an Ocata OpenStack deployment with OpenDaylight Nitrogen, Ceph Jewel, and SFC feature enabled.

Scenario components and composition

This scenario includes a set of common OpenStack services which are Nova, Neutron, Glance, Cinder, Keystone, Heat, Ceilometer, Gnocchi, Aodh, Horizon. Ceph is used as the backend of Cinder on deployed hosts. HAproxy is used to balance all the services running on 3 control nodes behind a VIP (Virtual IP address). OpenDaylight will also be deployed in this scenario. ODL is also running in HA. Neutron communicates with ODL through a VIP. Open vSwitch with NSH patched is used instead of native Open vSwitch to support ODL SFC. Neutron communicates with ODL SFC to create port pair, classifier, port chain and etc.

Scenario usage overview

To deploy with this scenario, you just need to assign the os-odl-nofeature-ha.yaml to DHA file before deployment.

References

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

This document introduces scenario descriptions for Euphrates 1.0 of deployment with no SDN controller and no feature enabled.

k8s-nosdn-nofeature-ha

This scenario is used to deploy an kubernets cluster.

Scenario components and composition

This scenario includes a set of kubernets services which are kubernets API Server, Controller Manager, kube-proxy, kubelet,kube-dns,nginx-proxy,kubernetes-dashboard. Nginx-proxy is used to balance all the services running on 3 control nodes behind a VIP (Virtual IP address).

Scenario usage overview

To deploy with this scenario, you just need to assign the k8s-nosdn-nofeature-ha.yaml to DHA file before deployment.

References

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