|By Marten Terpstra||
|July 18, 2014 09:00 AM EDT||
Much has been published about the Open Compute Project. Initiated by Facebook, it has become an industry effort focused on standardization of many parts and components in the datacenter. Initially focused on racks, power and server design, it has also added storage and now networking to its fold. Its goal is fairly straightforward: “how can we design the most efficient compute infrastructure possible”, a direct quote from its web site.
The focus of OCP has been mostly around hardware designs and specifications. If you look at the networking arm of OCP, you find several Top of Rack (ToR) ethernet switch hardware designs donated by the likes of Broadcom, Mellanox and Intel. By creating open specifications of hardware designs for fairly standard ethernet switches, the industry can standardize on these designs and economics of scale would drive down the cost to create and maintain this hardware. A noble goal and there are many opinions on both sides of this effort. Mostly referred to as “bare metal” and “commodity”, you can easily spend days reading up on many opinions. Mike Bushong yesterday discussed pricing implications for resellers in this blog post.
An interesting development however is that the network group within OCP has added a few software projects to its scope. Mellanox has initiated an Open Switch API specification, which attempts to standardize the lowest layer of interaction with the actual ethernet switching hardware. As a hardware vendor today, the choice of switching chipset is an important one beyond just the raw capabilities of the chipset. Each chip vendor that has a portfolio of chipsets also has a Software Development Kit or SDK that provides the initial layer of software to instruct the chip what to do. Ultimately every chip is manipulated with a (rather large) set of registers that need to be set, but that complexity is hidden in this SDK. The SDK presents a set of higher level APIs to program against that control the functioning of the chipset. This is what we (Plexxi) and all other hardware vendors write our software against, this is how we glue our software to the ethernet switching hardware.
Different chipset vendors of course have different SDKs, which makes changing chipsets a non-trivial step to take, your software has to adjust to a different SDK with all its functional and sometimes architectural differences. By creating a common switch API, life for us would be better, we would have a single API to develop against and could easily support multiple chipsets since the differences would be hidden behind this API. With so much functional difference between the chipset vendors, even these APIs will have lots of vendor specific extensions in them, but as recipients of such standardization, we can only welcome the effort.
The second software component the networking arm of OCP has taken on is the Open Network Install Environment. ONIE is a boot loader and installer based on a complete, but narrow linux distribution. ONIE was created as an open source, vendor agnostic boot loader with the desire to have these commodity switches leave their factory with only ONIE installed. Driven by Cumulus it creates a convenient and standard method to get software installed and loaded onto bare metal switches from commodity hardware providers. It’s a necessary piece for Cumulus’ business to ensure easy installation of their software onto third party hardware.
ONIE is pretty straight forward and those that use net booting using DHCP, TFTP and a variety of other means will probably say “what’s the big deal”? At a high level, it really provides the same functionality, but with some small, but very relevant differences.
ONIE is built on a full linux distribution. So out of the gate, switches with ONIE installed will boot to a complete linux before they even attempt to find the actual switching software image they ultimately will run. Having a full linux means you have full networking support, you can access the device using telnet, ssh, you name it. Once booted, ONIE will follow a set of search rules to find an image to download and install. There is no pre-conceived notion of what that image is, or what needs to be done to install it, the image itself contains the instructions of how this image needs to be installed, how the internal disk should be formatted,which partition to install into, you name it. ONIE has none of that knowledge, it just has the linux tools to do it. Once a switching software image has been installed, ONIE will reboot the switch again and now boot right through to the software image installed (with of course a chance to interrupt that).
A bit of boot loader, installer and some may even want to call it BIOS, all wrapped together in a linux distribution, ONIE is not magic, it’s not radically innovative. But it is a very convenient and open source way to get switches to boot, find, install and run software all with the safety-net of linux to get into the switch remotely if the software loading, installation or execution really goes bad. I bet most of you have had switches in crash and boot loops before, and they are hard to recover from without physical intervention.
At Plexxi we do not create standard switching hardware, that should be clear. We also don’t create standard switching software for commodity switches. But we are implementing ONIE on our switches and packaging our software to be ONIE installable, available a bit later this year.
For us this is a very convenient and (on its way to being industry) standardized way to implement a boot loading and installation environment that fits well with our open source and linux roots and beliefs. For us this is about providing convenience to our customers and logistics teams. We will have the option to ship our switches with ONIE so that the customer can simply power the switch on, plug in the management ethernet connection, connect our LightRail optical cables and the switch becomes part of a Plexxi ring loaded with the right software, visible to our controller.
It’s not a huge innovative leap, but it’s a significant convenience. And there is lots of value in creating convenience and simplicity, they are significant drivers in our overall solution. Which makes ONIE a nice fit.
The post Open Compute, Open Switch API and Open Network Install Environment appeared first on Plexxi.
From the conception of Docker containers to the unfolding microservices revolution we see today, here is a brief history of what I like to call 'containerology'. In 2013, we were solidly in the monolithic application era. I had noticed that a growing amount of effort was going into deploying and configuring applications. As applications had grown in complexity and interdependency over the years, the effort to install and configure them was becoming significant. But the road did not end with a ...
May. 5, 2016 06:30 PM EDT Reads: 723
The goal of any tech business worth its salt is to provide the best product or service to its clients in the most efficient and cost-effective way possible. This is just as true in the development of software products as it is in other product design services. Microservices, an app architecture style that leans mostly on independent, self-contained programs, are quickly becoming the new norm, so to speak. With this change comes a declining reliance on older SOAs like COBRA, a push toward more s...
May. 5, 2016 05:15 PM EDT Reads: 1,722
Many private cloud projects were built to deliver self-service access to development and test resources. While those clouds delivered faster access to resources, they lacked visibility, control and security needed for production deployments. In their session at 18th Cloud Expo, Steve Anderson, Product Manager at BMC Software, and Rick Lefort, Principal Technical Marketing Consultant at BMC Software, will discuss how a cloud designed for production operations not only helps accelerate developer...
May. 5, 2016 05:00 PM EDT Reads: 1,361
Small teams are more effective. The general agreement is that anything from 5 to 12 is the 'right' small. But of course small teams will also have 'small' throughput - relatively speaking. So if your demand is X and the throughput of a small team is X/10, you probably need 10 teams to meet that demand. But more teams also mean more effort to coordinate and align their efforts in the same direction. So, the challenge is how to harness the power of small teams and yet orchestrate multiples of them...
May. 5, 2016 05:00 PM EDT Reads: 567
In a crowded world of popular computer languages, platforms and ecosystems, Node.js is one of the hottest. According to w3techs.com, Node.js usage has gone up 241 percent in the last year alone. Retailers have taken notice and are implementing it on many levels. I am going to share the basics of Node.js, and discuss why retailers are using it to reduce page load times and improve server efficiency. I’ll talk about similar developments such as Docker and microservices, and look at several compani...
May. 5, 2016 04:00 PM EDT Reads: 881
SYS-CON Events announced today that Peak 10, Inc., a national IT infrastructure and cloud services provider, will exhibit at SYS-CON's 18th International Cloud Expo®, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. Peak 10 provides reliable, tailored data center and network services, cloud and managed services. Its solutions are designed to scale and adapt to customers’ changing business needs, enabling them to lower costs, improve performance and focus inter...
May. 5, 2016 02:30 PM EDT Reads: 1,482
Much of the value of DevOps comes from a (renewed) focus on measurement, sharing, and continuous feedback loops. In increasingly complex DevOps workflows and environments, and especially in larger, regulated, or more crystallized organizations, these core concepts become even more critical. In his session at @DevOpsSummit at 18th Cloud Expo, Andi Mann, Chief Technology Advocate at Splunk, will show how, by focusing on 'metrics that matter,' you can provide objective, transparent, and meaningfu...
May. 5, 2016 02:30 PM EDT Reads: 1,202
In the world of DevOps there are ‘known good practices’ – aka ‘patterns’ – and ‘known bad practices’ – aka ‘anti-patterns.' Many of these patterns and anti-patterns have been developed from real world experience, especially by the early adopters of DevOps theory; but many are more feasible in theory than in practice, especially for more recent entrants to the DevOps scene. In this power panel at @DevOpsSummit at 18th Cloud Expo, moderated by DevOps Conference Chair Andi Mann, panelists will dis...
May. 5, 2016 01:30 PM EDT Reads: 1,135
Last week I had the pleasure of speaking on a panel at Sapphire Ventures Next-Gen Tech Stack Forum in San Francisco. Obviously, I was excited to join the discussion, but as a participant the event crystallized not only where the larger software development market is relative to microservices, container technologies (like Docker), continuous integration and deployment; but also provided insight into where DevOps is heading in the coming years.
May. 5, 2016 09:45 AM EDT Reads: 236
Wow, if you ever wanted to learn about Rugged DevOps (some call it DevSecOps), sit down for a spell with Shannon Lietz, Ian Allison and Scott Kennedy from Intuit. We discussed a number of important topics including internal war games, culture hacking, gamification of Rugged DevOps and starting as a small team. There are 100 gold nuggets in this conversation for novices and experts alike.
May. 5, 2016 05:45 AM EDT Reads: 1,029
The notion of customer journeys, of course, are central to the digital marketer’s playbook. Clearly, enterprises should focus their digital efforts on such journeys, as they represent customer interactions over time. But making customer journeys the centerpiece of the enterprise architecture, however, leaves more questions than answers. The challenge arises when EAs consider the context of the customer journey in the overall architecture as well as the architectural elements that make up each...
May. 5, 2016 04:00 AM EDT Reads: 2,082
Much of the discussion around cloud DevOps focuses on the speed with which companies need to get new code into production. This focus is important – because in an increasingly digital marketplace, new code enables new value propositions. New code is also often essential for maintaining competitive parity with market innovators. But new code doesn’t just have to deliver the functionality the business requires. It also has to behave well because the behavior of code in the cloud affects performan...
May. 5, 2016 03:15 AM EDT Reads: 1,514
Admittedly, two years ago I was a bulk contributor to the DevOps noise with conversations rooted in the movement around culture, principles, and goals. And while all of these elements of DevOps environments are important, I’ve found that the biggest challenge now is a lack of understanding as to why DevOps is beneficial. It’s getting the wheels going, or just taking the next step. The best way to start on the road to change is to take a look at the companies that have already made great headway ...
May. 5, 2016 01:30 AM EDT Reads: 501
In 2006, Martin Fowler posted his now famous essay on Continuous Integration. Looking back, what seemed revolutionary, radical or just plain crazy is now common, pedestrian and "just what you do." I love it. Back then, building and releasing software was a real pain. Integration was something you did at the end, after code complete, and we didn't know how long it would take. Some people may recall how we, as an industry, spent a massive amount of time integrating code from one team with another...
May. 5, 2016 01:15 AM EDT Reads: 1,151
I have an article in the recently released “DZone Guide to Building and Deploying Applications on the Cloud” entitled “Fullstack Engineering in the Age of Hybrid Cloud”. In this article I discuss the need and skills of a Fullstack Engineer with relation to troubleshooting and repairing complex, distributed hybrid cloud applications. My recent experiences with troubleshooting issues with my Docker WordPress container only reinforce the details I wrote about in this piece. Without my comprehensive...
May. 4, 2016 11:45 PM EDT Reads: 1,010
Struggling to keep up with increasing application demand? Learn how Platform as a Service (PaaS) can streamline application development processes and make resource management easy.
May. 4, 2016 09:00 PM EDT Reads: 2,259
As the software delivery industry continues to evolve and mature, the challenge of managing the growing list of the tools and processes becomes more daunting every day. Today, Application Lifecycle Management (ALM) platforms are proving most valuable by providing the governance, management and coordination for every stage of development, deployment and release. Recently, I spoke with Madison Moore at SD Times about the changing market and where ALM is headed.
May. 4, 2016 08:00 PM EDT Reads: 1,634
If there is anything we have learned by now, is that every business paves their own unique path for releasing software- every pipeline, implementation and practices are a bit different, and DevOps comes in all shapes and sizes. Software delivery practices are often comprised of set of several complementing (or even competing) methodologies – such as leveraging Agile, DevOps and even a mix of ITIL, to create the combination that’s most suitable for your organization and that maximize your busines...
May. 3, 2016 07:30 PM EDT Reads: 1,958
Digital means customer preferences and behavior are driving enterprise technology decisions to be sure, but let’s not forget our employees. After all, when we say customer, we mean customer writ large, including partners, supply chain participants, and yes, those salaried denizens whose daily labor forms the cornerstone of the enterprise. While your customers bask in the warm rays of your digital efforts, are your employees toiling away in the dark recesses of your enterprise, pecking data into...
May. 3, 2016 04:45 PM EDT Reads: 1,167
You deployed your app with the Bluemix PaaS and it's gaining some serious traction, so it's time to make some tweaks. Did you design your application in a way that it can scale in the cloud? Were you even thinking about the cloud when you built the app? If not, chances are your app is going to break. Check out this webcast to learn various techniques for designing applications that will scale successfully in Bluemix, for the confidence you need to take your apps to the next level and beyond.
May. 3, 2016 12:15 PM EDT Reads: 1,654