There are not enough OpenStack experts to go around. At OpenStack Summit, there is literally not a single company here that is not looking for more programmers, architects, and engineers.
But, they're coming. OpenStack is now backed by more than 200 vendors, including Cisco, Dell, HP, IBM, Intel, Oracle, RackSpace Red Hat, and VMware. Is there any enterprise out there which doesn't have a working relationship with at least of one of these companies?
This is making OpenStack deployment easier. If your company doesn't have the talent it needs to do it in-house, Canonical, Red Hat, and Mirantis, to name but three of the leading OpenStack deployment firms, are all ready to jump in and help you get up and running. In short, you can pay cash today and have a working OpenStack cloud tomorrow.
If your next software development project is going to be successful, be it a simple Java EE deployment or a full-scale role out of a private cloud initiative based on OpenStack, a tremendous amount of code has to be written. The sad state of affairs enterprise organizations need to reckon with is that there is no way all that code can be written by the internal development team.
So what's an organization to do? According to Jim Zemlin, executive director of the Linux Foundation, successful organizations reach out to the open source community. "There is too much software to be written for any one organization to write this software on its own," Zemlin said. "Open source allows businesses to focus on only the most important aspects of their technology stacks; only the things that truly differentiate the organization."
Jim Whitehurst recently wrote about the performance management approach we use at Red Hat for the Harvard Business Review. In his article, Whitehurst details one aspect of the performance management process that differentiates Red Hat from other companies—its flexibility.
We have a system for tracking performance (called Compass), and we have expectations for when Compass reviews are performed (at least annually, preferably quarterly). But the details and structure of implementation are up to individual managers or teams. I lead a team of more than 100 people at Red Hat, and I’d like to share how I measure and manage performance the open source way.
So as technology leaders — as the drivers of innovation — we must always be on the lookout for new ways to ready our organizations for agility. One means to that end is open source. Open source is the ultimate platform for flexibility, right? A platform that affords us the agility we need to quickly adapt as technology evolves, business demands expand and markets mature. A platform that allows us to innovate how we want, when we want — rather than innovating on the path and at the pace of our vendors.
Open source is increasingly changing the software industry. We can see open source products gaining market share in almost every category today, and this development is continuing at a fast pace.
Although a lot of business people still intuitively think of Linux when it comes to open source software, content management systems played a pivotal role in changing the mindset within corporations. Why? Because the CMS industry was one of the first to largely adopt open source products. Nowadays, the most corporations use open source content management systems for their web platforms. Some of them may not even realize it.
Cultural heritage management tends to suffer from limited funding and resources, which can make a crisis — whether natural disaster, pipeline construction, or war — that much more catastrophic for assessing what’s in need of protection. An open-source system called Arches is the first online tool designed specifically to inventory heritage sites. It was created through a partnership between the World Monuments Fund (WMF) and the Getty Conservation Institute (GCI), and its third version launched earlier this month.
Ever since NASA and Rackspace first got together in 2010 to create OpenStack, there has been the concept of an integrated OpenStack release. However, at the OpenStack Summit here this week, developers declared the integrated release model to be dead, being replaced with a new "Big Tent" model that redefines what OpenStack includes as a platform.
But backers of the project insist it’s as strong as ever. This week OpenStack is in the midst of its 11th semi-annual Summit in Vancouver. From all accounts it’s got the feel of a real tech show with an estimated 6,000 attendees and more than 500 companies supporting the project.
Working directly with hardware is hard. Each project brings with it mundane questions of which compiler to use, what communications protocols to work with, and how to load code. Developers also need to figure out how to debug the live system without affecting the program being executed.
In the past this has required expensive and proprietary software, but thanks to commodity hardware and projects such as OpenOCD, developing programs that run directly on embedded hardware is easier than ever before.
I've known Fred for about 15 years or so, first as a contributor to OpenEMR and later we accidentally met in person at the University of Texas. It's pretty cool to come face-to-face with folks you've only know online and, mostly, from working with their contributed code! Over the years, Fred has hosted a couple of open source healthcare IT conferences and done some great work in the field for ClearHealth/MirrorMed with Dave Ulhman and now focusing on open data.
I'm Lee Schlesinger, currently managing editor for the Spiceworks Community. Spiceworks provides a free downloadable help desk and network inventory application, and hosts a community for IT pros to discuss both work and off-topic issues. Though we have a pretty popular Linux group in the community, many of the community members, who we call SpiceHeads, work in Microsoft-centric shops.