Podcasts Technology Software Defined Talk Episode 105: Kubernetes Rules Everything Around Me, VMworld, Pivotal Container Service

Episode 105: Kubernetes Rules Everything Around Me, VMworld, Pivotal Container Service

Published: Aug. 31, 2017, 7 p.m.

b'

It\\u2019s VMworld this week, so there\\u2019s fresh news from the Dell Technologies universe to sort through. VMware releases it\\u2019s SDDC on AWS scheme and Pivotal announces its container service/stack, Pivotal Container Service (PKS). We discuss both, including a meandering overview of what PKS is and some theory about what enterprises actually want with all that VMware in public cloud. Also, the tragic story of airline and hotel upgrades, like pearls to tired business travelers.

\\n\\n

Misc.

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

Now you can buy kubernetes from Dell

\\n\\n

\\n\\n
    \\n
  • VMware/Pivotal/Google make a kubo distro. Uses BOSH, NSX, and kubo to setup clusters. Will run on vSphere and Google Cloud, promises to work with other Google Cloud services, be continuously updated to be compatible with GCE containers. Also, VMware storage services and comparability with VMware systems management tools.
    • \\n
  • El Reg coverage, and also from The New Stack.
    • \\n
  • TPM: \\u201cThe private PKS stack will use vSAN for storage, vRealize Automation for orchestration and governance, vCloud Director for provisioning, and vRealize Operations for monitoring. (So, in theory, one could run the PKS stack on the AWS cloud slices that VMware has partnered with Amazon to create, effectively creating a clone of GKE to run on AWS bare metal iron. . . .)\\u201d
    • \\n
  • More laundry listing of the parts from Google, that is, Google Cloud services you can use in a PKS environment: BigQuery, Bigtable, Spanner, Storage, SQL, Pub/Sub, Vision API, Speech API, Natural Language API, Translate API.
    • \\n
  • A list of capabilities from Cornelia\\u2019s(?) talk, and what BOSH does (and, thus, does in k8 management).
    • \\n
  • Use it for: \\u201cPKS\\u2122 is ideal for workloads like Spark and ElasticSearch, and when you need access to infrastructure primitives. Further, use PKS for apps that require specific co-location of container instances, and for those that need multiple port binds.\\u201d\\n\\n
      \\n
    • The Pod affinity thing here is for when you want to run multiple things grouped together, like with Spark, Elastic Search, etc. where you the different things go together.
      • \\n
    • \\n
  • More value-props\\u2019ing:\\n\\n
      \\n
    • i.e., kubernetes on it\\u2019s own is hard.
      • \\n
    • As Ramji points out, PKS means you\\u2019ll get a consistent, standardized kubernetes/container technology across the Dell Technologies portfolio.
      • \\n
    • Watters lays it out.
      • \\n
    • \\n
  • Positioning: guidance seems to be that PKS is mostly for large organizations, \\u201centerprises.\\u201d
    • \\n
  • PKS to GA in 2017Q4, pricing then too.
    • \\n
  • Diagram here:.
    • \\n
  • Some vendor exec story-time here, and Pivotal blog post.
    • \\n
  • So, you can run PCF and PKS side-by-side.
    • \\n
  • See longer explanation from Chad Sakac:\\n\\n
      \\n
    • \\u201chistorically, [Dell Technologies\\u2019] point of view on the container/cluster manager abstraction ecosystem wasn\\u2019t clear\\u201d\\n
      • \\n
    • See also this pro\'er diagram.
      • \\n
    • Lots of emphasize on a unified, compatible approach/GTM: \\u201cWe now have a Cloud Native/Digital Transformation stack where there is a SINGLE target we are furiously running towards now as VMware, Pivotal, and Dell EMC \\u2013 no mis-alignment, no differences in PoV. \\u201c
      • \\n
    • \\n
  • Market context: \\n\\n
      \\n
    • You may recall Cot\\xe9\\u2019s summary of the CoreOS commissioned 451 survey, which linked to a 2016(?) Gartner survey where 18% of respondents had containers in production, with 4% being \\u201csignificant production\\u201d
      • \\n
    • That CoreOS/451 survey had a very important footnote: the survey respondents were already running containers already. It was more about which container orchestration platforms they liked.
      • \\n
    • It was hard to do conclusive ranking of container orchestrators since people were using multiple ones. But, if you lump together CoreOS\\u2019s kubernetes distro with generic kubernetes, kubernetes wins out over Docker Swarm, 49% vs. 36%.
      • \\n
    • Meanwhile: \\u201cBy 2020, 50%+ of global enterprises will be running containerized applications in production, up from <20% today.\\u201d
      • \\n
    • \\n
  • RedMonk\\u2019s \\u201cdevelopers are the kingmakers\\u201d theory, more.
    • \\n
\\n\\n

SDDC on VMware

\\n\\n
    \\n
  • Run the VMware stack on AWS, out of beta: \\u201cFor the IT and software development sectors, the deal means that VMware mainstays such as all its software-defined data center ware\\u2014vCenter, NSX, vSphere, VSAN and others\\u2014will run on AWS instead of VMware\'s own cloud.\\u201d
    • \\n
  • Pricing?
    • \\n
  • \\u201dThe three-year contract costs $109,366 per host, which would save about 50% compared to the on-demand hourly billing rate, according to VMware. Another program can cut costs by up 25% based on their on-premises VMware product licenses, as long as those on-premises products remain active\\u2026. There are separate charges for IP and data transfers, as the standard AWS egress fees still apply. Each host has 2 CPUs, 36 cores, 72 hyper-threads, 512 GiB RAM and local flash storage.\\u201d - \\u201dthe estimated total cost of ownership for VMware Cloud on AWS is up to $0.09 per VM per hour, according to VMware\\u201d
    • \\n
  • More pricing info from TPM: \\u201cThe base on demand price for this server is $8.3681 per hour, which works out to around $6,109 per month.\\u201d
    • \\n
  • Cloud-context, from Derrick Harris: \\u201cLook at the companies\\u2019 most-recent fiscal years\\u20142016\\u2014during which VMware grew about 9 percent to just over $7 billion in revenue, while AWS grew about 45 percent to more than $12.2 billion in revenue. It\\u2019s on pace for about $16 billion in revenue in 2017.\\u201d
    • \\n
  • And, more from Derrick on public cloud companies ever elusive quest to grab on-premises workloads and revenue: \\u201cThere will continue to be a lot of big workloads running inside company data centers. If AWS and Google really want a shot at owning them, they\\u2019ll probably need to get their hands (and code) a little dirty by going to where those applications live and showing there\\u2019s a better way of doing things.\\u201d
    • \\n
  • It makes you wonder if a strategy for public cloud companies going behind-the-firewall is just wishful projection on the on-premise set\\u2019s part. 451 surveys a predicting that by 2019, 60% of work-loads will run on cloud technologies (across public, hosted, and private), with under 25% on private cloud (hosted/managed and on-premises).
    • \\n
\\n\\n

VMworld, in general

\\n\\n
    \\n
  • Round-up of news from Larry Dignan - lot\\u2019s of security stuff, of which Cot\\xe9 has no clue. And, of course, the VDI/desktop stuff. It\\u2019s like the old Project Octopus era vision of VMware.
    • \\n
  • Delving into VMware financials, and some product portfolio strategy typing.
    • \\n
  • VIO, VMware\\u2019s OpenStack distro has a few production users, but, \\u201cfor the most part customers are deploying it for their development and test environments, where programmers want to embrace OpenStack and the IT managers want to keep everything on a VMware substrate\\u201d
    • \\n
  • VIO pricing: \\u201cThe other thing that is new with VIO 4.0 is that it is no longer free. Starting with this release, VIO will cost $995 per server socket in a Datacenter Edition, but customers who are using VIO in conjunction with the vRealize management suite will be able to get it for $495 per socket. That is just the price of the perpetual license; reckon another 18 percent or so on top of that for annual support.\\u201d
    • \\n
  • Chad Sakac explains all the stacks, how it does hybrid cloud, etc.
    • \\n
\\n\\n

BONUS LINKS! Not covered in show.

\\n\\n

SDN

\\n\\n
    \\n
  • Turns out, SDN is a condiment, not an entr\\xe9e.
    • \\n
  • Also, a good list of adoption challenges any new technology/thought-technology faces.\\n# Meta, follow-up, etc.
    • \\n
  • Patreon - like anyone who starts these things, I have no idea WTF it is, if it\\u2019s a good idea, or if I should be ashamed. Need some product/market fit.
    • \\n
  • Check out the Software Defined Talk Members Only White-Paper Exiguous podcast over there.
    • \\n
  • Join us all in the SDT Slack.
    • \\n
\\n\\n

Mid-roll

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

Recommendations

\\n\\n

Sponsored By:

'