Coté

Try to go beyond hand waving and opinions and find out what really is happening. A good way to start is to ask people to picture what their scenario would look like if everything was perfect. This puts them into a positive frame and helps focus on great outcomes. Once you’re sure you’re working on an improvement opportunity that’s worth your time, try small time-bound experiments that you actually follow through on.

You probably still want to know who actually built a given container and what’s running in it. Source: Google, IBM and others launch an open source API for keeping tabs on software supply chains

I have an extra piece in The Register this month. I was asked to frame the history of software product theory between the Cluetrain, Andrew Clay Shafer’s agile infrastructure talk, DevOps, and the “we’re a software company now” trope.

From an interview with Jeffrey Hammond and Marc Cecere on developer skills gaps. Here, the trend to training with people in person and then (slowly) going back “home”: [Hammond:] One of the things I think you see is it– so many companies have used the words, partnering model, for years, and it’s been more or less lip service. But you do see a little bit more of a partnering and more highly tailored model.

Has everyone gone kubernetes crazy? It seems like most buyers and sellers at least want it as an option and are, if you prefer the word, capitulating to supporting it. In past weeks most all vendors - even Oracle! - have announced support and road-maps for using Google’s container orchestrator in their cloud-native stacks. Also, Chef and Puppet have new suites of tools, Docker sets its sites clearly on reducing VMware costs, and there’s some new momentum stats on the Cloud Foundry ecosystem.

Has everyone gone kubernetes crazy? It seems like most buyers and sellers at least want it as an option and are, if you prefer the word, capitulating to supporting it. In past weeks most all vendors - even Oracle! - have announced support and road-maps for using Google’s container orchestrator in their cloud-native stacks. Also, Chef and Puppet have new suites of tools, Docker sets its sites clearly on reducing VMware costs, and there’s some new momentum stats on the Cloud Foundry ecosystem.

On overview of how Bloomberg is looking at the likes of Pivotal Container Services: "Many Kubernetes distributions are good on day one, when they're first deployed," said Andrey Rybka, technical architect in the office of the CTO at Bloomberg, the global finance, media and tech company based in New York. "But what happens on day two, when something fails? Kubernetes doesn't [automatically] address things like failures at the physical node level.

Paying premium bucks to hire influencers for the big cloud migration wars. Source: What is Microsoft Doing?

Consider the case of the connected cows. The grand unified, cloud/AI/IoT/serverless theory: That was the essence of the Build keynote: The cloud interprets IoT telemetry, in real time, with AI. And that AI can, in turn, instruct other IoT devices to do things based on its interpretation. Source: The Serverless Revolution Will Make Us All Developers

The three new Puppet products based on Distelli's technology are Puppet Pipelines for Apps, which automates key application development and delivery tasks; Puppet Pipelines for Containers, which enables users to build Docker images from a repository and deploy them to Kubernetes clusters; and Puppet Container Registry, which gives developers a comprehensive view of their Docker images across all repositories. Source: Puppet Launches Barrage Of Products To Enable ‘New Age’ Of Software Automation And DevOps