Following the rhythm, we held the 8th Swiss SDN workshop/meetup in mid-June this year. It was a great a pleasure and experience to get the networkers together for a full-day event hosted at ETH Zurich. We learnt about new solutions and implementations from the talks/demos given by our colleagues from the academia and the private sector.
After the latest work on Heat support for Netfloc service chaining, the SDN team used the summer’s quiet month of August to update some of the features in Netfloc and Netflogi.
A new extension to the API set is the functionality to retrieve the current service chains created in Netfloc. This has been made possible with the improvement of the Netfloc service yang definition and the persistent data record from Netfloc into the MD-SAL repository. Using this APIs the providers of a Netfloc service can now issue RPC requests to the datastore inventory and retrieve the current data and state of the service. This improves the resilience by keeping the network state and the chain aligned and consistent in case of Netfloc restart.
The Service Engineering (SE, blog.zhaw.ch/icclab) group at the Zurich University of Applied Sciences (ZHAW) / Institute of Applied Information Technology (InIT) in Switzerland is seeking applications for a full-time position at its Winterthur facility.
The successful candidate will work in the InIT Cloud Computing Lab (ICCLab) and will contribute to the research initiative on software defined networking for clouds.
Last week in Athens we integrated the SDK4SDN aka Netfloc in the T-Nova Pilot testbed in order to showcase service function chaining using two endpoints and two VNFs (Virtual Network Functions).
NETwork FLOws for Clouds (Netfloc) is an open source SDK for datacenter network programming developed in the ICCLab SDN initiative. It is comprised of set of tools and libraries that interoperate with the OpenDaylight controller. Netfloc exposes REST API abstractions and Java interfaces for network programmers to enable optimal integration in cloud datacenters and fully SDN-enabled end-to-end management of OpenFlow enabled switches.
Inside the Software Defined Networking initiative we are developing a Software Development Kit for SDN, called Netfloc.
NETwork FLOws for Clouds (Netfloc) is a programmable framework solution for software defined datacenter networks. It leverages network management by offering to the network developers a set of libraries packed as Java bundles for the OpenDaylight controller. Netfloc also exposes REST API abstractions and Java interfaces to enable optimal integration in cloud datacenters and customized end-to-end management of OpenFlow equipment. For references and current status, please feel free to visit the Github repository. We will come back with a detailed post on the SDK very soon, so stay tuned.
And yes being the networking guys, we are mainly dealing with command line management in the whole process of development and testing. But only until to date, when we realized that it is time to think as well of the UX side and start a design process for a graphical user interface (GUI) for Netfloc.
Last Friday, 13th November the 5th SDN workshop took place at the SWITCH premises in Zurich. With 9 presentations covering different aspects of Software Defined Networking and around 40 attendees, we are happy to bring together the academia and industry partners on the same table in order to provide to the community a complete overview of the most recent results, products and open source SDN solutions.
Compared with the previous workshops, talks from the industry were prevalent this time, which brought variety but most importantly an intent to close the gap between SDN research projects and grand-scale solutions based on customer use cases.
Yesterday for the 4th time the ICCLab organized the SDN workshop at the University of Bern in cooperation with SWITCH. We had around 25 participants and 7 talks that tackled SDN in the world of cloud computing, NFV, IXP, video content delivery, high performance cloud, authentication request routing and access control etc. All these solutions coming from different projects from the academia and the industry.
We at ICCLab are embarking upon an exciting project to make a software development kit to enable SDN researchers develop exciting products and innovative protocols overcoming the challenges and drawbacks of decades old network protocols in use today. We had a huge debate internally to decide which programming language to use for this development. Since, internally we had quite strong and vocal supporters of both Java and Python, it led to stalemate. So how did we resolve it?