Types of Netwrok interfaces Virtual box

Believe it or not but your guest virtual box has more ways to connect to network than your host machine ! In virtual box you can connect to network in 7 different ways.
So if you want to just use internet NAT will be more than enough for you. But if you want to communicate with the host machine as well use internal networking. BTW you can add more than one network adapter to your VM so mix and match and have fun ! Read down to get more info on adapters type.

1. Not attached :
In this mode, VirtualBox reports to the guest that a network card is present, but that there is no connection -- as if no Ethernet cable was plugged into the card. This way it is possible to "pull" the virtual Ethernet cable and disrupt the connection, which can be useful to inform a guest operating system that no network connection is available and enforce a reconfiguration.

2. NAT
If all you want is to browse the Web, download files and view e-mail inside the guest, then this default mode should be sufficient for you, and you can safely skip the rest of this section. Please note that there are certain limitations when using Windows file sharing

3. Bridged networking
This is for more advanced networking needs such as network simulations and running servers in a guest. When enabled, VirtualBox connects to one of your installed network cards and exchanges network packets directly, circumventing your host operating system's network stack.

4.Internal networking
This can be used to create a different kind of software-based network which is visible to selected virtual machines, but not to applications running on the host or to the outside world.

5.Host-only networking
This can be used to create a network containing the host and a set of virtual machines, without the need for the host's physical network interface. Instead, a virtual network interface (similar to a loopback interface) is created on the host, providing connectivity among virtual machines and the host.

6.Generic networking

    Rarely used modes share the same generic network interface, by allowing the user to select a driver which can be included with VirtualBox or be distributed in an extension pack.

    At the moment there are potentially two available sub-modes:

    UDP Tunnel
    VDE (Virtual Distributed Ethernet) networking

7. NAT Network :The NAT network is a new NAT flavour introduced in VirtualBox 4.3

Creating a simple application in Open Daylight Controller

In this post I am going to make a simple application in ODL. Main aim of this application will be just to say "I have started" at the time of loading and "Over and out", when it stops.
To program for ODL you need to know java language and Maven, OSGi. Dont panic if you don't know about the last two its fairly easy and I will go step-by-step on that.
When you start developing your folder structure should be as below;

ubuntu@ubuntu:userinfo$ ls
META-INF pom.xml src target 

Here src is where you will have code; target is where you will have binaries META-INF has information related to OSGi (Explained later). You need not to worry about it right now Maven will take care of it.

To understand about OSGi and create a simple java code click here
To understand and create a simple pom file in ODL click here

Once you have build successfully go to your target directory. you will find samples.userinfo-0.4.0-SNAPSHOT.jar over there. Thats your bundle !

Now follow the steps at running a custom bundle and see your sample app running in controller.
If you have any queries feel free to post it :)

OSGi framework and Open DayLight

The newest SDN controller OpenDayLight is made on OSGi architecture. It gives you flexibility to load various plugins without stopping complete controller, which is cool actually as you can upgrade your existing plugin without any restart. So service is not affected. OSGi has three variations, OpenDayLight is made on equinox. (FYI eclipse is also made on equinox). OSGi bundles are essentially jar files. its the META-INF file which differentiates them. It has all information about the project. Whenever a project is loaded firstly an Activator class is called. (Note: That's why we give its address in tag bundle-activator in pom.xml). When bundle is loaded Activator first calls init method, and when you remove the bundle destroy method is called. the Now lets build a basic java code for ODL.


package org.opendaylight.controller.samples.userinfo.internal;


import org.slf4j.Logger;
import org.slf4j.LoggerFactory;


import org.opendaylight.controller.sal.core.ComponentActivatorAbstractBase;


public class Activator extends ComponentActivatorAbstractBase {
    protected static final Logger logger = LoggerFactory
            .getLogger(Activator.class);

    /**
     * Function called when the activator starts just after some
     * initializations are done by the
     * ComponentActivatorAbstractBase.
     *
     */
    public void init() {
       logger.info("I have started !!");
    }

    /**
     * Function called when the activator stops just before the
     * cleanup done by ComponentActivatorAbstractBase
     *
     */
    public void destroy() {
              logger.info("Over and out !!");
    }

 }


For more info on pom file click here.
To create a sample application click here

Basic pom.xml file for building a bundle in Open DayLight

Maven is something like makefile in linux. Maven helps in compilation. when you say 'mvn install' it reads the pom.xml file. pom.xml have various tags essential tags for creating basic pom.xml are as below. Please note i have put comments between <!-- --> which is standard xml comment tag.
pom.xml

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>

<!-- Do not change above lines. They provide xml version and maven version info -->

    <parent>

<!-- Everything inside this tab is your parents, i.e on top of which you will make your application   --> 

    <groupId>org.opendaylight.controller</groupId>

    <!-- its the project where your parent is located-->

    <artifactId>commons.opendaylight</artifactId>

    <!-- Parent application name-->

    <version>1.4.0-SNAPSHOT</version>

    <!-- Parents version-->

    <relativePath>../../commons/opendaylight</relativePath>

    <!-- Path where parent pom file is located-->

  </parent>

  <scm>

    <connection>scm:git:ssh://git.opendaylight.org:29418/controller.git</connection>

    <developerConnection>scm:git:ssh://git.opendaylight.org:29418/controller.git</developerConnection>

    <url>https://wiki.opendaylight.org/view/OpenDaylight_Controller:Main</url>

  </scm>

    <!-- Everything inside scm tag is for version controlling you can delete this tag if you want-->

  <artifactId>samples.userinfo</artifactId>

  <!-- this is your application name.  -->

  <version>0.0.1-SNAPSHOT</version>

  <!-- Your application version.  -->

  <packaging>bundle</packaging>

  <!-- Tells maven you want to create OSGi bundle.   -->

  <build>

  <!-- Information on how to build the code-->

    <plugins>

      <plugin>

      <!-- Info on which plugin to use from maven   -->

        <groupId>org.apache.felix</groupId>

        <!-- Project name for that plugin-->

        <artifactId>maven-bundle-plugin</artifactId>

        <!-- Kind of obvious we are making an OSGi bundle-->

        <version>2.3.6</version>

        <!-- Plugins option-->

        <extensions>true</extensions>

        <!-- Use extension for this project-->

        <configuration>

          <instructions>

            <Import-Package>

              org.opendaylight.controller.sal.core,

              org.slf4j,

            </Import-Package>

            <!-- Which package to import for building the code-->

            <Export-Package>

              org.opendaylight.controller.samples.userinfo

            </Export-Package>

          <!-- Name of the package, which will be exported-->

            <Bundle-Activator>

              org.opendaylight.controller.samples.userinfo.internal.Activator

            </Bundle-Activator>

           <!-- Address where OSGi activator is located -->

          </instructions>

          <manifestLocation>${project.basedir}/META-INF</manifestLocation>

           <!-- Address of OSGi META file -->

        </configuration>

      </plugin>

    </plugins>

  </build>

  <dependencies>
  <!-- Dependencies on exiting code>
    <dependency>
      <groupId>org.opendaylight.controller</groupId>
      <artifactId>sal</artifactId>
      <version>0.5.0-SNAPSHOT</version>
    </dependency>
  </dependencies>

</project>

For more information on how to make a simple application in open daylight controller click here

Running a custom bundle in Open Day light controller

I have copied one of the sample application int the opendaylight controller and named it as userinfo by changing artifact id in pom file. In this post i will show you how can i add my application while controller is running.

First of all build the bundle by command "mvn install". If everything is well go to command line of controller. But before that let me shed some light on how OSGi works. Life cycle of any app is 1. install 2. resolve 3.uninstall. First and last is self explanatory. A bundle will be in resolved state when all the dependencies are resolved and that's when you can start a service. 

osgi> install file:/home/ubuntu/workspace/controller/opendaylight/samples/userinfo

Bundle id is 150

< output omitted>

Version              0.0.1.SNAPSHOT

BundleDescription    org.opendaylight.controller.samples.userinfo_0.0.1.SNAPSHOT

Framework            org.eclipse.osgi.framework.internal.core.Framework@164e955

ResolutionFailureException org.osgi.framework.BundleException: The state indicates the bundle is resolved

Revisions            [org.opendaylight.controller.samples.userinfo_0.0.1.SNAPSHOT]

BundleContext        null

BundleId             150

StartLevel           1

SymbolicName         org.opendaylight.controller.samples.userinfo

BundleData           org.opendaylight.controller.samples.userinfo_0.0.1.SNAPSHOT

KeyHashCode          150

StateChanging        null

as you can see once installed osgi gives you a bundle id. now you can start or stop this bundle with this id.

To check currently installed bundle and its id/state say 'ss'

osgi> ss

"Framework is launched."

id      State       Bundle

0       ACTIVE      org.eclipse.osgi_3.8.1.v20120830-144521

<OUTPUT ommited>

150     RESOLVED    org.opendaylight.controller.samples.userinfo_0.0.1.SNAPSHOT

As you can see state is resolved. Good now let you can start the bundle by giving command 'start 150'. But it will give you error as the controller don't have binaries. For that you need to copy your binary (i.e. jar) to
/home/ubuntu/workspace/controller/opendaylight/distribution/opendaylight/target/distribution.opendaylight-0.1.0-SNAPSHOT-osgipackage/opendaylight/plugins

ok. Now say start 150 and njoy your code !

To create a simple application click here

User levels in OpenDayLight controller

I have been playing around Open Daylight Controller from a while now. OD controller divides user in 6 types mainly

1. SYSTEMADMIN - This user is the GOD of OD. He has no restrictions.
2.  NETWORKADMIN - It can do everything but setting a system admin user profile. Still he has lots of power.
3. NETWORKOPERATOR - It can only see what is configured anywhere;
4. CONTAINERUSER - container context user

5. APPUSER - application context user

 6. NOUSER - Get out ! He is not authorized.

I am yet to figure out what user level 4 and 5 can do. Please let me know if you figure it out :)

Definition of these are in UserLevel.java file.

    SYSTEMADMIN(0, "System-Admin", "System Administrator"),
    NETWORKADMIN(1, "Network-Admin", "Network Administrator"),
    NETWORKOPERATOR(2, "Network-Operator", "Network Operator"),
    CONTAINERUSER(4, "Container-User", "Container User"),  
    APPUSER(5, "App-User", "Application User"),
    NOUSER(255, "Not Authorized", "Not Authorized");

Next I will show how to set up an AAA server for OD controller.