Episode 96: An AWS private cloud strategy, kubernetes aplenty, microservices by yaml, & detailed hot-dog creature analysis

Published: June 2, 2017, 3 p.m.

b'

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.

\\n\\n

Alternate Titles

\\n\\n
    \\n
  • I\'ve seen this hot-dog before.
  • \\n
  • I\\u2019ve been doing this since dickity-4
  • \\n
  • I\\u2019m sticking with the Mary Meeker slides, you nerds go figure it out
  • \\n
\\n\\n

Mid-roll

\\n\\n\\n\\n

Hot-dog guy in Japan

\\n\\n\\n\\n

Internet Trends 2017

\\n\\n
    \\n
  • 300 plus slides of charts
  • \\n
  • Computes!
  • \\n
  • Cot\\xe9\\u2019s notebook, summary of summary:\\n\\n
      \\n
    • Google and Facebook make a lot of ad money.
    • \\n
    • The Kids like using smart phones, the olds like using traditional telephones. One of them will die sooner.
    • \\n
    • Voice, image recognition, etc.
    • \\n
    • China is pretty much a mature market, and it\\u2019s huge.
    • \\n
    • India has potential, but doing business there is hard and you need more Internet in a pocket rollout.
    • \\n
    • The public/private cloud debate is still far from over.
    • \\n
    • But, AWS, Microsoft, and Google have pretty much won.
    • \\n
    • Bonus: there\\u2019s surprisingly little funding and exits this year.
    • \\n
  • \\n
  • Would Amazon sell some private clouds?
  • \\n
\\n\\n

Isotoner and Hephaestus - All the new container orchestration poop

\\n\\n
    \\n
  • Cot\\xe9: Catching up on all this week\'s container poop & as always, my first reaction is \\u201coh, I thought the existing stuff did all that already..so."
  • \\n
  • Managed service for Tectonic as a Service - so, keeping your Kubernates cluster software updated? Presumably enforcing config, etc?\\n\\n
      \\n
    • However, not all done, still working on the complete solution.
    • \\n
    • But, there\\u2019s an etcd thing \\u2018As a first step, Tectonic 1.6.4 will offer the distributed etcd key-value data store as a fully managed cloud service. \\u201cIt\\u2019s the logical one to offer first because it is everything else gets built on it,\\u201d Polvi explained. The data store \\u201cguarantees that data is in a consistent state for very specific operations,\\u201d he said, referring to how etcd can be essential for operations such as database migrations.\\u2019
    • \\n
    • Another etcd description: \\u201cetcd is a clustered database that prizes consistency above partition tolerance\\u2026 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.
    • \\n
    • So, you need locks for - dun-dun-dun! - transactions! Queue JP lecturing me in 2002.
    • \\n
  • \\n
  • Then there\\u2019s Istio: \\n\\n
      \\n
    • Istio?!
    • \\n
    • Whao! Check out the exec-pitch: \\u201c Istio gives CIOs a powerful tool to enforce security, policy and compliance requirements across the enterprise.\\u201d And Google: \\u201cThrough 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.\\u201d\\n\\n
        \\n
      • I love their idea of what a CIO does.
      • \\n
    • \\n
    • \\u201cAn open platform to connect, manage, and secure microservices\\u201c
    • \\n
    • SDN++ overlay for container orchestrators from Google, IBM & Lyft - once you control the network with the \\u201cdata plane,\\u201d you add in the \\u201ccontrol plane\\u201d which allows you to control the flow and shit of the actual microservices.
    • \\n
    • Tackling the \\u201cnew 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.\\u201d
    • \\n
    • And, you know, all the agnostic, multi-cloud, open stuff.
    • \\n
    • Thankfully, they didn\\u2019t use a bunch of garbage, nonsense names for things.
    • \\n
    • Let\\u2019s look at the docs (BTW, can you kids start just putting out PDFs instead of only these auto-generated from markdown web pages?):\\n\\n
        \\n
      • First of all, these are good docs.
      • \\n
      • Monkey-patching for the container era: \\u201cYou 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\\u2019s control plane functionality.\\u201d
      • \\n
      • The future! Where we all shall live! \\u201cIstio currently only supports service deployment on Kubernetes, though other environments will be supported in future versions.\\u201d
      • \\n
      • Problems being solved, aka, \\u201cways you must be this tall to ride the microservices ride\\u201d: \\u201cIts 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.\\u201d
      • \\n
      • Also: Traffic Management, Observability, Policy Enforcement, Service Identity and Security.
      • \\n
      • Does it have the part where it reboots/fixes failed services for you?
      • \\n
      • So: \\n\\n
          \\n
        • you monkey-patch all this shit in (er, sorry, \\u201csidecar\\u201d),
        • \\n
        • which controls the network with SDN shit,
        • \\n
        • Istio-Manager + Envoy does all your load-balancing/circuit breaker/canary/AB shit, service discovery/registry, service versioning (i.e., running n+1 different versions of code - always a pretty cool feature), configuring \\u201croutes,\\u201d what connects to what,
        • \\n
        • I don\\u2019t think it provides a service registry/discover service? Maybe just a waffer thin API (\\u201ca platform-agnostic service discovery interface\\u201d)?
        • \\n
        • Question: what does this look like in your code? \\n\\n
            \\n
          • The thing 12 factor-style passes a configuration into your actual code. Here, you\\u2019re 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?
          • \\n
          • 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 .,
          • \\n
        • \\n
      • \\n
    • \\n
  • \\n
  • So, big questions, aka, Cot\\xe9 mental breakdown that only Matt Ray can cure:\\n\\n
      \\n
    • 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)?
    • \\n
    • So, it\\u2019s just cheaper and more transparent than VMware?
    • \\n
    • What\\u2019s the set of shit one needs? Ubuntu, Moby Engine (?), Moby command line tools, etcd? Actuality kubernetes code? What\\u2019s Swarm do? And then there\\u2019s monitoring, which according to Whiskey Charity, is all shit, right?
    • \\n
    • Where\\u2019 my fucking chart on this shit?
    • \\n
    • Please write two page memo for the BoD by 2pm today.
    • \\n
  • \\n
  • Meanwhile: Oracle\\u2019s cool with it, \\u201cWTF is a microservice\\u201d, compared to SOA/ESB and RESTful, and James Governor tries to explain it all.
  • \\n
\\n\\n

BONUS LINKS! Not covered in episode.

\\n\\n

Rackspace Buys Enterprise Apps Management TriCore

\\n\\n
    \\n
  • Link
  • \\n
  • New CEO and biggest acquisition, I thought they were quieting down with the PE
  • \\n
\\n\\n

Red Hat buys Codenvy

\\n\\n
    \\n
  • Codenvy sets up your developer environments, and has team stuff.
  • \\n
  • Red Hat is really after the developer market.
  • \\n
  • TaskTop has a good chance of being acquired in this climate.
  • \\n
  • Pour one out from BMC/StreamStep.
  • \\n
  • Notes from Carl Lehmann report at 451:\\n\\n
      \\n
    • In-browser IDE and devtool chain(?) for OpenShift.io, based on Eclipse Che
    • \\n
    • \\u201cFounded 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.\\u201d
    • \\n
    • \\u201cThe 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.\\u201d
    • \\n
    • Check out the Dell Sputnik call-out: \\u201cRivals 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.\\u201d
    • \\n
  • \\n
\\n\\n

Uber back in Austin

\\n\\n\\n\\n

Amazon Hiring Old Folks (Like Me)

\\n\\n\\n\\n

More Tech Against Texas\\u2019 Discriminatory Laws

\\n\\n
    \\n
  • Lords of Tech sign a thing
  • \\n
  • \\u201cIn 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.\\u201d
  • \\n
  • \\u201cPeeing is not political\\u201d - recap of the history of the bathroom bill. Still doesn\\u2019t really address \\u201cis there actually a problem here, backed up with citations.\\u201d Without such coverage, it\\u2019s hard to understand (and therefore figure out and react to) the hillbilly\\u2019s side on this beyond: "It\'s just common sense and common decency \\u2014 we don\'t want men in women\'s, ladies\' rooms." It also highlights the huge, social divide between \\u201ccity folk\\u201d and the hillbillies.
  • \\n
  • A lot more from TheNewStack.
  • \\n
\\n\\n

ChefConf Retrospective

\\n\\n\\n\\n

Competing in Public Cloud is Crazy Expensive

\\n\\n
    \\n
  • Link
  • \\n
  • Tracks the CAPEX spend over the years for MS, Google and Amazon
  • \\n
\\n\\n

A Year of Google & Apple Maps

\\n\\n
    \\n
  • Link
  • \\n
  • Comprehensive drill-down into the mapping changes made by Google and the smaller moves by Apple.
  • \\n
  • Probably not content for conversation, but whoa.
  • \\n
\\n\\n

FAA Flight Delay Tracking

\\n\\n\\n\\n

Recommendations

\\n\\n

Sponsored By:

'