An AWS private cloud strategy, kubernetes aplenty, microservices by yaml, & detailed hot-dog creature analysis
Software Defined Talk LLC·2017-06-02·via Software Defined Talk
Episode 96
·
June 2nd, 2017
·
1 hr 7 mins
The cat-nip of Mary Meeker's Internet Trends report is out this week so we discuss the highlights which leads to a sudden discussion of what an Amazon private cloud product would look like. Then, with a raft of new container related news we sort out what CoreOS is doing with their Tectonic managed service, what Heptio is (the Mirantis of Kubernetes?), and then a deep dive into the newly announced Istio which seems to be looking to create a yaml-based(!) standard for microservices configuration and policy and, then, the actual code for managing it all. Also, an extensive analysis of a hot-dog display, which is either basting itself or putting on some condiment-hair.
Alternate Titles
I've seen this hot-dog before.
I’ve been doing this since dickity-4
I’m sticking with the Mary Meeker slides, you nerds go figure it out
However, not all done, still working on the complete solution.
But, there’s an etcd thing ‘As a first step, Tectonic 1.6.4 will offer the distributed etcd key-value data store as a fully managed cloud service. “It’s the logical one to offer first because it is everything else gets built on it,” Polvi explained. The data store “guarantees that data is in a consistent state for very specific operations,” he said, referring to how etcd can be essential for operations such as database migrations.’
Another etcd description: “etcd is a clustered database that prizes consistency above partition tolerance… Interestingly, at Google, chubby is most frequently accessed using an abstracted File interface that works across local files, object stores, etc. The highly consistent nature, however, provides for strict ordering of writes and allows clients to do atomic updates of a set of values.
So, you need locks for - dun-dun-dun! - transactions! Queue JP lecturing me in 2002.
Whao! Check out the exec-pitch: “ Istio gives CIOs a powerful tool to enforce security, policy and compliance requirements across the enterprise.” And Google: “Through the Open Service Broker model CIOs can define a catalog of services which may be used within their enterprise and auditing tools to enforce compliance.”
I love their idea of what a CIO does.
“An open platform to connect, manage, and secure microservices“
SDN++ overlay for container orchestrators from Google, IBM & Lyft - once you control the network with the “data plane,” you add in the “control plane” which allows you to control the flow and shit of the actual microservices.
Tackling the “new problems emerge due to the sheer number of services that exist in a larger system. Problems that had to be solved once for a monolith, like security, load balancing, monitoring, and rate limiting need to be handled for each service.”
And, you know, all the agnostic, multi-cloud, open stuff.
Thankfully, they didn’t use a bunch of garbage, nonsense names for things.
Let’s look at the docs (BTW, can you kids start just putting out PDFs instead of only these auto-generated from markdown web pages?):
First of all, these are good docs.
Monkey-patching for the container era: “You add Istio support to services by deploying a special sidecar proxy throughout your environment that intercepts all network communication between microservices, configured and managed using Istio’s control plane functionality.”
The future! Where we all shall live! “Istio currently only supports service deployment on Kubernetes, though other environments will be supported in future versions.”
Problems being solved, aka, “ways you must be this tall to ride the microservices ride”: “Its requirements can include discovery, load balancing, failure recovery, metrics, and monitoring, and often more complex operational requirements such as A/B testing, canary releases, rate limiting, access control, and end-to-end authentication.”
Also: Traffic Management, Observability, Policy Enforcement, Service Identity and Security.
Does it have the part where it reboots/fixes failed services for you?
So:
you monkey-patch all this shit in (er, sorry, “sidecar”),
The thing 12 factor-style passes a configuration into your actual code. Here, you’re adding a bunch of name/value pairs (which can be nested) and also translating them to the name/value pairs that your code is expecting...on an HTTP call? Executing a command in your container? As ENV vars?
And then, I think you finally get ahold of the network to reply back with some HTML, JSON, or some sort of HTTP request by .,
So, big questions, aka, Coté mental breakdown that only Matt Ray can cure:
Er...so this all really is a replacement for the VMware stack, right? And OpenStack? Or do you still need those. What the fuck is all this stuff? It just installs the Docker image on a server? And then handles multi-zone replication, and making sure config drift is handles (bringing up failed nodes, too)?
So, it’s just cheaper and more transparent than VMware?
What’s the set of shit one needs? Ubuntu, Moby Engine (?), Moby command line tools, etcd? Actuality kubernetes code? What’s Swarm do? And then there’s monitoring, which according to Whiskey Charity, is all shit, right?
Where’ my fucking chart on this shit?
Please write two page memo for the BoD by 2pm today.
In-browser IDE and devtool chain(?) for OpenShift.io, based on Eclipse Che
“Founded in 2013, San Francisco-based Codenvy raised $10m in January of that year, and used a portion of its funds to buy its initial codebase from eXo Platform, which had developed the eXo Cloud IDE in-browser coding suite to support its social and collaboration applications.”
“The company's suite works with developer tools like subversion and git, CloudBees, Jenkins, Docker, MongoDB, Cloud Foundry, Maven and ant, as well as PaaS and IaaS offerings such as Heroku, Google AppEngine, Red Hat OpenShift and AWS.”
Check out the Dell Sputnik call-out: “Rivals to Codenvy include cloud-based development suites Eclipse Orion (open source), Cloud9 IDE and Nitrous.IO. There are other 'cloud IDEs,' including Codeanywhere, CodeRun Studio, Neutron Drive and ShiftEdit. On the developer environment configuration front, Pivotal created and open-sourced a developer and OS X laptop configuration tool called Workstation, and now Sprout. Dell's Project Sputnik is seeking to address similar build environment standup productivity challenges.”
“In addition to Facebook founder Mark Zuckerberg and Apple CEO Tim Cook, the letter was signed by Amazon CEO Jeff Wilke, IBM Chairman Ginni Rometty, Microsoft Corp. President Brad Smith and Google CEO Sundar Pichai. The leaders of Dell Technologies, Hewlett Packard Enterprise, Cisco, Silicon Labs, Celanese Corp., GSD&M, Salesforce and Gearbox Software also signed the letter.”
“Peeing is not political” - recap of the history of the bathroom bill. Still doesn’t really address “is there actually a problem here, backed up with citations.” Without such coverage, it’s hard to understand (and therefore figure out and react to) the hillbilly’s side on this beyond: "It's just common sense and common decency — we don't want men in women's, ladies' rooms." It also highlights the huge, social divide between “city folk” and the hillbillies.
