By Ashley Lipman Many people have heard of Kubernetes, but don’t know when or where to use it or even what it’s functionality is. Docker users may be more familiar with the program, but still unsure how to make that transition into using Kubernetes. In this article, we’ll take a beginner’s approach to what Kubernetes is and how to start using it. This information will give you a high-level overview of the program and highlight some key considerations.
Almost nothing inspires a spirited discussion among the open source faithful as much as introducing a new open source license, or a major change in an existing license’s terms. In the case of version 3 of the GPL, the update process took years and involved dozens of lawyers in addition to community members. So, it’s no surprise that the pot is already boiling over something called the “Commons Clause.” How energetically? Well, one blog entry posted yesterday was titled The Commons Clause Will Destroy Open Source. The spark that turned up the heat was the announcement the same day by RedisLabs that it was adopting the license language.
The wire services lit up yesterday with news that six of the largest tech companies in the world had issued a statement in support of interoperability in healthcare at a developer conference. It’s a righteous goal, to be sure. In an interoperable healthcare world, anyone’s entire, life-long health record could be accessed anywhere, anytime, by anyone who was giving you care, from your primary physician to an emergency responder. Such a virtuous goal, in fact, that everyone, including the US government, has been trying to achieve it – without success – for over a decade. Will yesterday’s news bring us any closer to that goal?
First, the good news: last week, Google, Microsoft, Twitter and Facebook announced the Data Transfer Project, inviting other data custodians to join as well. DTP is an initiative that will create the open source software necessary to allow your personal information, pictures, email, etc. to be transferred directly from one vendor’s platform to another, and in encrypted form at that. This would be a dramatic improvement from the current situation where, at best, a user can download data from one platform and then try and figure out how to upload it to another, assuming that’s possible at all.
So what’s the bad news, and what does a hammer have to do with it?
As old readers will know and new ones can tell from the left column, one of the things I do besides lawyering is writing satirical, political cybersecurity thrillers - four to date, with a fifth out within a couple of months. Recently, Tantor Media offered me a contract to bring out the first three titles in audio. Tantor is an imprint of the largest publisher of audiobooks in the world, and I was delighted to say yes. Now the first title, The Alexandria Project, a Tale of Treachery and Technology, is available at Audible, Amazon, and everywhere else audiobooks are sold.
My, my, what a difference a decade makes. Or for some, maybe not. Ten years ago, Microsoft was led by Steve Ballmer, who very much viewed open source as the barbarian at the software giant’s gates. The feeling was emphatically reciprocated by most in the free and open source (FOSS) community, which viewed Microsoft as a threat to the very existence of FOSS. And if Ballmer had been able to have his way back then, they would probably have been right.
Ask any journalist to pick an adjective to use in connection with standards development and the answer will invariably be "boring." But according to a recent New York Times article (yes, it also used that word - as well as "wonky"), the process of creating standards just became a whole lot more interesting - at least when it comes to the blockchain. The reason? A standards working group may have been infiltrated by state actors bent on embedding security flaws into the very standards being created for the purpose of preventing attacks.
There’s a belief in some open source circles that standards can be consigned to the ash heap of history now that OSS development has become so central to information technology. While it’s true that today many use cases can be addressed with OSS where open standards would have been used in the past, that approach can’t solve all problems. Most obviously, while resolving interoperation issues through real-time collaboration among up and downstream projects may meet the need within the same stack, it doesn’t help that stack communicate with other software.
Blockchain technology is an architecture where collaboration on software alone will often not suffice to meet the challenge at hand.
When it comes to the blockchain, most people fall into one of two camps: the hand-wavers that think the blockchain will disrupt and benefit the world as profoundly as the Internet, and those who are scratching their heads and just can't see how that could be possible. I confess that I fall more into the second camp than the first, but I do recognize that blockchain technology can provide a far superior tool to tackle some challenges than any that we've had to work with before.
I identified just such a challenge many years ago when the Internet was really taking off, and suggested that individuals needed to seize control of their personal information before commercial interests ran off with it instead, locking it away inside proprietary databases. The date of that article? February 2004, the same month that a little Web site called Facebook went live. Back then the problem was (and it still is) that the critical keys to avoiding data lock in are standards, and the process that develops those standards wasn't (and still isn't) controlled by end users.
Here's how I posed the challenge in that article:
Have you ever wondered what it would be like to read a book as its written? Or better yet, be able to make suggestions as the book develops and see your ideas help shape the result? Well, here’s your chance. If you’re already a Friend of Frank at my author site, or want to become one, that’s what you’re invited to do. As the book evolves, I'll ask for your advice, and answer any questions you may have. I’ll also give you the inside scoop about how and why each chapter is written as it is. Sound interesting? Great, because I’ve just posted the Prologue and First Chapter below. To read the future chapters for free as they’re posted, all you have to do is become a Friend of Frank.