“We see PaaS as a strategic component of our software-defined infrastructure and application platform strategy,” stated SUSE President of Strategy, Alliances and Marketing Michael Miller, in a note to The New Stack, “and Cloud Foundry as the open source project and technology that brings together the best innovation and industry collaboration. We want to leverage that innovation for the benefit of our customers, and we have a vision for the convergence of CaaS technologies [in SUSE’s case, Containers as a service] like Docker and Kubernetes and PaaS technologies like Cloud Foundry that we think will address the real-world needs of our customers and partners. We will now work with the Cloud Foundry community to develop that vision.”
I get asked to talk on DevOps a lot. Here’s my current (late 2016 and 2017) presentation, going over the why’s, the how’s, the technologies, and the meatware that supports including some best and worst practices based on what Pivotal customers do. See the newer slides with big pictures on most slides, and some of the older slides
Also, here’s a more blatantly pro-Pivotal (and longer) version that you might have seen, esp. if the talk title was something like “Digital Transformation in the Streets.”
Much of it draws a lot on my cloud native journey booklets as well.
Like reading about doing agile, DevOps, and “cloud native” in the real world? Check out my little booklet on that topic drawing from failures and success at large organizations that I’ve observed over the past few years.
I have a new, updated version of this book in development. Check out the draft!
Unsurprisingly, I liked both of them, esp. the second:
What I find so helpful, and even thrilling, about Gruver’s book, is that it’s exacting in its instructions and walks through several what-if scenarios for addressing common problems that come up when applying agile and DevOps at scale. Plus, it’s the perfect size for a book of this type: about 90 pages that’ll take you about 90 minutes to read.
“I think significant organic growth going forward will be nonexistent due to the competition from the public cloud providers,” said Tim Feeney, an analyst at Morningstar Inc. “Whitman may look to M&A to augment organic growth.”
A round-up of all sorts of container stacks, and some advice on what to do:
Therefore, the key lessons learned from this event (from developer’s perspective): Do not focus on developing code for the container under the hood. Care instead about the business logic. Implement your microservices in a vendor agnostic way.
Do not make the same fault as we all did with J2EE / Java EE where all vendors used the same standard specifications, but still offered many vendor-dependent features and “added value” in their specific “standard implementation”. Migration, i.e. deployment to another Java EE application server was a lot of efforts (re-development, testing, …); sometimes a complete re-write was easier and faster.
There’s a lot of fragmentation in container land now. This is what Linux must have felt like back in the late 90s.
Our advice at Pivotal, of course, is to focus on using Spring and other services towards the top of the stack for that layer of lock-in protection.
“If he institutes a 35-percent penal tariff on every export from China, then most of what you buy at Walmart is 35 percent more expensive,” said Roger Entner, a wireless analyst at Recon Analytics.
The intention of plans like this is always to re-build the entire system and structure. That takes a long time, one assumes. So, what’s important is to describe how the transition phase works.
Another unstated assumption of such thinking is “corporations make too much profit,” that is, Apple and Wal-Mart should take the hit. I’d rather we be having a debate about that: how much money do individuals deserve versus corporate profits and how do we do anything about it?
From Al’s report on the recent OpenStack Summit:
Based on a 451 Research Advisors survey of midsize and large enterprises, increasing operational efficiency and accelerating innovation/deployment speed are top business drivers for enterprise adoption of OpenStack, at 76% and 75%, respectively. Supporting DevOps is a close second, at 69%. Reducing cost and standardizing on OpenStack APIs were next, at 50% and 45%, respectively. The survey further shows diversity in vertical markets using OpenStack, with 80% of respondents being outside the tech industry.
The latest biannual release of OpenStack is Newton, and the community supporting it also shows diversity among the contributors. As of this 14th release, there are 64,549 community members from 187 countries, up from 50,000 six months ago. There are also 643 supporting companies, up from 578 for the same period. Newton also had a record number of developers contribute to the code: 2,581, versus 15 in the first release.
Lots of charts that show a large percentage of workers leave after a year. Also, as better jobs come about, if wages don’t rise in gig jobs, churn will be even higher:
“It doesn’t look like [gig work] is becoming more lucrative for people,” says Fiona Greig, co-author on the JPMorgan Chase Institute report. “As the labor force strengthens in general, more and more people have better options.”
“[Gartner analyst Arup Roy] said Indian [IT services] companies, for example, should not expect double-digit sales revenue growth in 2017, adding that ‘a sub 10% growth for 2017 is certain.'”
But, the effect is likely to be on all large organizations who have been globalizing IT staffing:
“There is really no such thing as the Indian IT services sector. All companies would be affected. For example, Capgemini employs more people in India that in any other country. Legislation does not differentiate between Infosys, Capgemini or Accenture,” said Schumacher.
In 2013, German car manufacturer Daimler said it planned to achieve savings of €150m a year by bringing IT services in-house and expanding IT operations in India and Turkey. In 2012, General Motors said it would insource around 90% of its heavily outsourced IT operations.
We talked about more “Trump’s possible effects on tech” in last week’s Software Defined Talk, with some extensive links and notes in the show notes if you don’t want to fill your ear-holes.