ONOS is an Opensource SDN controller targeted towards Service providers. I had provided a brief overview of ONOS in 1 of my earlier blog. I tried out ONOS software recently and in this blog, I will share my experiences.
Following picture from ONOS architecture guide shows the different layers of ONOS at high level.
Continue reading ONOS Overview and Hands-on
This is a continuation of my previous blog on Group based policy(GBP). In this blog, I will cover the GBP features in Opendaylight helium release, Use-cases that are published in the Opendaylight wiki as well as different usecase that I tried out.
Group based policy in Opendaylight:
Following diagram is from Opendaylight GBP wiki:
- Openstack here is the orchestration layer and it communicates the policy to ODL through Neutron apis.
- The policy is expressed in high level data language and is translated and programmed into hardware through renderers.
- In ODL helium release, the only available renderer is Openflow and it uses ovsdb overlay design.
- Opflex renderer is being developed currently and it is also based on ovsdb overlay. When Opflex is available, there will be a Opflex agent in the openvswitch that will eventually do the low level translation and programming.
Continue reading Group based policy in Opendaylight
There is lot of work going on in both Openstack and Opendaylight projects on Group based policy and I will try to capture my learnings in the next few blogs.
Group based policy(GBP) is an abstracted way of specifying interactions between the applications rather than using infrastructure specifics. In the networking context, for example, rather than using terms like ip address, vlan, port numbers, the policies are specified in much higher level language in terms of what the application needs. Currently Group based policy is targeted for Networking. Eventually, it will be applicable to Compute and Storage as well. I kind of see GBP as Open source variant of Cisco’s ACI model, multiple vendors are involved in the development of GBP.
In Openstack Neutron context, following are the goals of Group based policy.
Continue reading Group based policy
Opendaylight Helium is the second release after Hydrogen and it was released late September 2014. Earlier, I was using Opendaylight Hydrogen release and recently, I tried out Opendaylight Helium release. In this blog, I have shared some of my experiences with Helium.
Following are some important additions to Helium compared to Hydrogen. For more details, please refer Opendaylight webpage.
- Hardening of the controller, Clustering capability, Security options like AAA.
- Better integration with Openstack which has features like Group based policy, service function chaining.
- Use of Apache karaf container format so that individual features can be installed.
- Better Dlux gui.
Continue reading Opendaylight Helium release
I came across few recent Opensource projects which I found them to be interesting. In this blog, I will cover some details on OPNFV, Openconfig, ONOS. There is no relation between the 3 projects, the common thing is all the 3 projects are focussed on Networking and Cloud and all are relatively new.
OPNFV is an Opensource project under Linux foundation. The goal is to create a Opensource reference platform for developing NFV applications. In 1 of my earlier blogs on NFV, I covered overview of NFV and the ETSI NFV model. The goal of the OPNFV project is to create a reference implementation using the model proposed by ETSI. OPNFV’s plan is to leverage the work done in other Opensource projects like Openstack, Opendaylight, Openvswitch, KVM, Linux kernel, DPDK. Even though OPNFV can work with other Cloud OS and SDN controllers, the goal for the first release is to use the most popular Cloud OS, SDN controller and hypervisor mentioned above. Following picture from OPNFV illustrates the blocks that OPNFV will focus on from ETSI NFV reference model.
Continue reading Recent Networking Opensource projects – OPNFV, Openconfig, ONOS
Recently, I came across this tool called Vagrant that eases the creation and sharing of VM work environment. I played with it and found it very useful. Vagrant integrates with VM hosting providers like Virtualbox, Vmware and AWS. Different devops tools like Chef, Puppet, Ansible are integrated with Vagrant. In this blog, I will cover high level overview and use cases of Vagrant, Vagrant workflow and an application that I created using Vagrant. In the application, I have created a Vagrant Opendaylight(ODL) box using Ubuntu 12.04 as baseline. I will describe the steps that I followed to create the Vagrant ODL box and how it can be used.
Vagrant Use cases:
- Easier to share VM and this allows for better collaboration. Rather than sharing large OVA files, Vagrant configuration files can be shared.
- Same VM base can be used for different applications. For example, Vagrant box can be a Ubuntu OS which contains the OS alone. Vagrant box could also be Ubuntu OS plus LAMP stack, this base box can be used for developers wanting to develop applications on top of LAMP stack.
- VagrantCloud can be used to find base VMs for a lot of different use cases. The same site can be used to host new base VMs. Free VagrantCloud account does not allow hosting.
- Vagrant integrates well with devops tools like Chef, Puppet and Ansible and this makes the recipe installation easier.
Continue reading Vagrant – Overview and Opendaylight Vagrant Image
Cisco’s acquisition of Tail-f prompted me to look deeper into what Tail-f does. That in-turn made me dig deeper into Netconf and Yang. Netconf is a device configuration and management protocol and Yang is a modeling language that’s used by Netconf. Yang modeling can also be used outside Netconf’s context. From looking at the history behind Netconf and Yang, I realized that Network management as a whole was a widely ignored topic for quite sometime. The current Network management techniques used by Operators seems to be very arcane and the recent SDN wave has triggered a renewed interest in simplifying Network management. In this blog, I will cover the following:
- Shortcomings of SNMP.
- Netconf and Yang overview with examples.
- Comparison with Ovsdb and Openflow.
- Opendaylight’s use of Yang model
- Tail-f NCS system’s use of Netconf and Yang.
Continue reading Netconf and Yang