Sunday, February 22, 2015

OpenDaylight Developer Spotlight: Jamie Goodyear [feedly]

OpenDaylight Developer Spotlight: Jamie Goodyear
// OpenDaylight blogs

The OpenDaylight community is comprised of leading technologists from around the globe who are working together to transform networking with open source. This blog series highlights the developers, users and researchers collaborating within OpenDaylight to build an open, common platform for SDN and NFV.

About Jamie Goodyear

Jamie Goodyear is a Computer Systems Analyst with Savoir Technologies, an Apache Software Foundation Member, and an open source evangelist. He has designed, critiqued, and supported architectures for large organizations worldwide.

Jamie has worked in systems administration, software quality assurance, and senior software developer roles for businesses ranging from small start-ups to international corporations. He has attained committer status on Apache Karaf, Servicemix, and Felix, and is a Project Management Committee member on Apache Karaf. He is co-author of Instant OSGi Starter (Packt Publishing, 2013), co-author of Learning Apache Karaf (Packt Publishing, 2013), and co-author of Apache Karaf Cookbook (Packt Publishing, 2014).

Currently he divides his time between providing high-level reviews of architectures,mentoring developers and administrators with MicroService deployments, and helping to grow the Apache community.

What project in OpenDaylight are you working on? Any new developments to share?

I am a lead computer system analyst at Savoir Technologies where I develop and support Apache Karaf - the micro services platform OpenDaylight (ODL) is built upon. My favorite project with ODL was, of course, helping in its refactoring to run on Apache Karaf! Since then, I've been getting the distribution to run on small platforms such as the Intel Edison or Raspberry Pi. Thanks to Karaf's feature mechanism, ODL can now easily be tailored to run on these small systems. I've also enjoyed developing custom Karaf commands to help simplify monitoring the controller's state via the console (see our MD-SAL Status command on github:

OpenDaylight's Lithium release is due out this year. What do you think is most important for the project to focus on for the next release?

The refactor from a near plain OSGi core to Apache Karaf really helped bring structure to the project. Now that the initial work has been completed, it's time for the ODL community to fully take advantage of Karaf features, commands, and ecosystem of tooling to help make the user and developer experience better. At Savoir, we commonly help our clients projects enter this phase after an initial port to Karaf. Leveraging Karaf's micro-services architecture will help differentiate OpenDaylight distributions in the marketplace.

How would you describe the OpenDaylight developer community? What are the community's biggest strengths?

The OpenDaylight community is very welcoming (and big!). You'll meet world-class developers from leading corporate, academic, and other organizations. The global scale of development can be felt each day. Large scale aside, the community has gone out of its way to make accessing planning meetings and notes easy. Among IRC, ask.opendaylight, webex and wiki pages, you'll be able to quickly get up to speed on current developments, and more complex parts of the projects.

What is the best piece of developer advice you've ever received?

Read something in your area every day. It doesn't matter if you already 'know it', there tends to be some little gem or use case about an API, Library, or Language feature that you've yet to think about.

What technology could you not live without?

IRC and email. A lot of open source communities collaborate each day over IRC and email. They may be old tech but I'd be lost without them. Jenkins is also high on my list - I maintain a small build farm, automating my build testing on Windows Server, SUSE, and Ubuntu LTS. For building micro-services for integration platforms, Aetos is my number one toolkit (




Shared via my feedly reader

Sent from my iPhone

No comments:

Post a Comment