It’s finally out! The Architecture of Open Source Applications, Volume II, is now available in dead tree form (PDFs will be available for sale soon, I’m told).
Additionally, all content from the book will also be freely available on aosabook.org next week sometime (!).
But know this: all royalties from the sales of this book go to Amnesty International. So buy a copy; it’s for a good cause.
Both volumes 1 and 2 are excellent educational material for seeing how other well-known open source applications have been architected. What better way to learn than to see how successful, widely-used open source software packages were designed? Even better, after you read about each package, you can go look at the source code itself to further grok the issues.
Read More »
Tags: HPC, mpi, Open MPI, open source
We’ve held our annual Cisco Open Source event this week, on May 1st in San Jose. I’m very impressed to see the large turnout and the ultra positive feedback after the keynote and 5 tracks on Linux, SDN, Big Data, Emerging Technologies and Community Development. Wonderful to see Irving Wladawsky-Berger from IBM, Jim Zemlin from the Linux Foundation, Simon Crosby from Bromium and the great discussions that ensued. Next time we’ll have to open this event up to more than just one afternoon, there is just so much open collaboration that is taking place. My thanks to our track leads, Michael Hein who helped me put together the Linux track, Jan Medved and Dave Ward on SDN, Mark Voelker and Ed Warnicke on Big Data, Fabio Maino and Flavio Bonomi on Emerging Technologies, and Peter Saint-Andre for the Community Management and Tools — these guys have already left their mark on timeless and enduring open standards, but it’s amazing to see how good they are in open source! We’ll have to post the key takeaways in these next blog entries, for now to all those of you who came, contributed and enjoyed this event, we salute you! Open at Cisco is a vibrant and growing community.
Tags: Big Data, Cisco, Linux, open source, SDN
I have previously written about oVirt on this blog, but today, the official press release went out. You can read it in full here, but I’d like to quote a bit from the release:
The oVirt project today announced that Canonical, Cisco, IBM, Intel, NetApp, Red Hat and SUSE have joined together to help create a new open source community for the development of open virtualization platforms, including virtual management tools to manage the Kernel-based Virtual Machine (KVM) hypervisor. With the oVirt project, the industry gains an open source, openly governed virtualization stack.
The key piece to note above is the community aspect. oVirt as a community will develop and create an ecosystem in which customers, developers, and vendors can all thrive. Since the workshop, the community has been working towards the first release of oVirt for public consumption. Cisco, being on the oVirt board, is proud to be a part of the oVirt community as this community drives towards the initial release of oVirt.
Tags: community, open source, oVirt
Let me tell you a reason why open source and open communities are great: information sharing.
Let me explain…
I am Cisco’s representative to the Open MPI project, a middleware implementation of the Message Passing Interface (MPI) standard that facilitates big number crunching and parallel programming. It’s a fairly large, complex code base: Ohloh says that there are 0ver 674,000 lines of code. Open MPI is portable to a wide variety of platforms and network types.
However, supporting all the things that MPI is suppose to support and providing the same experience on every platform and network can be quite challenging. For example, a user posted a problem to our mailing list the other day about a specific feature not working properly on OS X.
Read More »
Tags: HPC, mpi, MPICH2, Open MPI, open source
In my previous post, I talked about how networking was a large part of the discussion at the oVirt Kickoff Workshop. Increasingly, the network is elevating itself to be a first-class citizen in large open source infrastructure and cloud projects, including open source projects like OpenStack and now oVirt. In OpenStack, the Quantum project is the result of these discussions. Newborn community projects such as oVirt are starting to look at elevating the network to provide advanced functionality as well. It was no surprise a large portion of the last day of the workshop was spent on networking, with an early focus on Quantum.
The last day of the workshop started out the morning with an overview of SDNs and Quantum by Lew Tucker, CTO of Cloud at Cisco. Lew drew a nice overview of cloud networking on the white board, presenting an app-centric view of cloud and virtual networking. In the cloud network model, apps care only about connectivity to the network, not how that connectivity happens, thus the focus on apps as the center of this world.
Lew Tucker Diagraming Quantum Networking
After Lew was done, Dan Wendlandt, project lead for Quantum, presented his Quantum slides. This was helpful to level-set everyone at oVirt with regards to Quantum and OpenStack. One of the main pain points with looking at how Quantum can be shared from OpenStack into oVirt has been the difference in the networking models. OpenStack presents a very cloud-centric view of networking, whereas oVirt wants a more datacenter-centric model. Quantum was designed to generally be agnostic to the deployment model, so using it in oVirt should be a matter of fitting it into the architecture.
Ram Durairaj from Cisco, Chris Wright from Red Hat, and Dan Wendlandt from Nicira
After Dan was done giving a broad Quantum overview, Ram Durairaj from the Cisco OpenStack team presented on Quantum L3 Services. Currently, Quantum is designed to address the L2 abstraction of the network. Quantum L3 Services are meant to expose L3 concepts such as subnets and gateways into Quantum and the plugins. It would also allow for routing between tenant domains.
Ram Durairaj talking L3 Services
Now that the oVirt Kickoff Workshop is over, watching how the networking story with oVirt evolves will be interesting. The success of oVirt will be the result of the community around it, and the ecosystem for third party vendors it creates. With regards to networking in oVirt, the interactions between the Quantum community and the oVirt community have only just begun, and the future looks like a very collaborative affair between the two projects.
Tags: open source, oVirt, quantum, SDN