Tuesday 25 August 2015

Week 13 Updates

Hello Everyone,

Now I'm able to run the basic longevity test on the VMs development environment and currently working on the improvement features to the basic Longevity test suite. I have pushed two changes to the upstream, one of which has been merged.

I have also made a wiki page on this project "Longevity test for OpenDaylight". Please see the link to the wikipage here.

Though the internship period has ended, I'll still be working on this project as an active contributor of the OpenDaylight community.

Cheers,
Nitika


Sunday 16 August 2015

Week 11 and 12 Upates

Hello Everyone,

As I got the resources increased on one of the VMs (on which ODL controller is installed), I tried to run the longevity test suite, one of which finally passed. Firstly, I tried to run the test suite with two switches and one node link.

Also, I have been having a hard time last week due to which I was not able to concentrate on the project work. I had a discussion with the mentor on the further task and currently working on the improvement of the longevity test suite.

Please see the below mentioned things on which I'm currently working to improve the longevity test suite:

- Add a check for NullPointer exceptions.
- Check that the threads are not leaking.


Cheers,
Nitika Agarwal


Monday 3 August 2015

Week 10 @Opendaylight Summit 2015

Hello Everyone,

Last week, I have been attending the OpenDaylight summit 2015. Thanks for providing the interns with an opportunity to meet the community and developers in person.

It was really a nice experience to meet my mentors and other developers. It was a great learning overall and learnt a lot after attending the Application Development tutorial sessions and other user tutorial sessions. In the Developer forum sessions, I learnt about other ODL projects as well and looking forward to work on other integration projects as well.

During the summit, we had two reception parties which provided us with an opportunity to meet with the community members. We also had an Intern / Mentor meeting in which we discuss our experience while working on the project. Overall, it was a great experience for me to attend the ODL summit.

Cheers,
Nitika Agarwal

Sunday 26 July 2015

Week 9 Updates

Hello Everyone,

I'm still awaiting for the response from the Spirent Labs to get the resources increased on one of the VMs (on which ODL controller is installed).

While working on resolving the issues and discussion with the mentor, I learnt many things like how to keep the controller running even after logout and how to start a clean controller. We can keep the controller running by executing the "bin/start" command instead of executing "bin/karaf" command. It will then go in the background and features can be installed either by doing "ssh -p 8101 karaf@localhost" to get a karaf console or by automatically loading through boot config file.

Last week, I was travelling to attend the OpenDaylight summit this week. Finally during the weekend, I got the response from the Spirent labs that the resources has been increased on one of the VMs (on which ODL controller is installed).

Cheers,
Nitika Agarwal



Sunday 19 July 2015

Week 8 Updates

Hello Everyone,

Moving ahead with the project work, I synced the longevity tests in my repository. As mentioned in my previous blog post. I'm still facing some issues while running the tests using pybot.

The next step was to see robot log files. For this, instead of making use of the remote desktop solution VNC, my mentor Jamo provided me with a good easy solution to view the robot logs via browser.
python -m simpleHTTPServer 80
The above command command just starts a simple web server through the directory you enter this command and then you can access the files in that folder via browser.

I digged deep into the logs to see the reason for the test failure. I also checked various ports on the controller VM. After going through the logs, I figured that the controller was not in the healthy state and mininet was not able to connect to the controller.

Moreover, there was a shortage of resources on the VM on which I have installed the ODL controller. So, I had requested for more resources on the particular VM (on which ODL controller is installed) need to be increased to 8 GB RAM and 4 cores VCPU.

Stay tuned for more updates..!!

Cheers,
Nitika Agarwal

Sunday 12 July 2015

Week 7 Updates

Hello Everyone,

Now I had my development environment setup on the VMs with the stable lithium version of the ODL controller installed.
  • ODL controller (Lithium version) on Ubuntu VM
  • Robot framework, RIDE, code pushing and pulling from upstream setup on another Ubuntu VM.
  • Mininet installed on another Ubuntu VM
Since now the VMs are on public IP address, I can ssh to these VMs directly as well as through jumpbox server.

As I learnt how to run the test suite using pybot and the various flags / options used with pybot command for running the Longevity test suite, I started running the test to see if the test is passing on my development environment. 

But while running the test suite, I faced some issues and had discussion with the mentor on this. We tried to check various things on the above three VMs and ensured that the controller is running, mininet is connected to the controller, ports are open on the controller VM. 

Still working on to resolve the issue and run the test suite.

Cheers, 
Nitika Agarwal


Sunday 5 July 2015

Week 6 Updates

Hello Everyone, 

Finally, I got the VMs recreated now on public IP address. Glad about this. 

I again began setting up the development environment on the VM, started with the installation of helium version of the ODL controller on one of the VMs. 

Though, the resources on this VM is small, only 2GB RAM and 1 core VCPU, so we decided to install only one feature set ie. odl-openflowplugin-flow-services-ui. 

Now I'm able to access the URL http://199.188.118.102:8181/dlux/index.html for the DLUX service via the browser and able to login successfully with admin/admin. I could see the topology. I was even able to watch the CPU on this VM while the modules / features were getting loaded using top command.

On the other VMs, I have installed mininet and Robot framework separately. 

After that, I tested the installation of mininet. One issue faced on the VM in which I have installed Robot framework, I was not able to launch RIDE using terminal. Since, this is not important, as we'll be running our test suite using pybot, hence we ignored this thing.

The below command was used to run the Longevity test suite :

pybot -N 010__longevity.txt -c critical -e exclude -v BUNDLEFOLDER:distribution-karaf-0.2.3-Helium-SR3 -v WORKSPACE:/tmp -v NEXUSURL_PREFIX:http://nexus01.dfw.opendaylight.org:8081/nexus -v CONTROLLER:199.188.118.102 -v CONTROLLER_USER:root -v MININET:199.188.118.103 -v MININET1: -v MININET2: -v MININET_USER:root -v USER_HOME:/root /root/integration/test/csit/suites/openflowplugin/Longevity

After setting up the development environment, I tried to run the basic Longevity test suite but facing some issues due to which the test is failing. I'll have a discussion on this with Jamo this week.

Cheers,
Nitika