SDN Controller Programming Guide

7
2 Setting Environment
The suggested development environment is split into two: Test Environment and Development
Environment. And it is recommended to use different machines. The Test Environment is where the
HP VAN SDN Controller and all the dependency systems will be installed; it will be very similar to
a real deployment, however virtual machines [14] are useful during development phase. The
Development Environment will be formed by the tools needed to create, build and package the
application. Once the application is ready for deployment, the test environment wil be used to
install it.
One reason to keep these environments separated is because distributed applications may need a
team set up to test the application (Cluster of controllers). Another reason is that some unit test
and/or integration tests (RESTful Web Services [1] [2] for example) may open ports that are
reserved for services offered or consumed by the controller.
Test Environment
Installing HP VAN SDN Controller
To install the SDN controller follow the instructions from the HP VAN SDN Controller Installation
Guide [15].
Authentication Configuration
The HP VAN SDN Controller uses Keystone [9] for identity management. When it is installed, two
users are created, "sdn" and "rsdoc", both with a default password of "skyline". This password
can be changed using the keystone command-line interface from a shell on the system where the
controller was installed: Follow the instructions from the HP VAN SDN Controller Installation Guide
[15].
Development Environment
Pre-requisites
The build environment requirements are relatively minimal. They comprise of the following:
Operating System
Supported operating systems include:
 Windows 7or later with MKS 9.4p1
 Ubuntu 10.10 or later
 OSX Snow Leopard or later.