Slashdot Mirror

← Back to Stories (view on slashdot.org)

Microsoft Acquires Container Platform Deis From Engine Yard (techcrunch.com)

Posted by BeauHD on from the jump-ship dept.

According to an announcement made earlier today, Microsoft has acquired Deis, "the company behind some of the most popular tools for building and managing applications on top of the Google-incubated Kubernetes container orchestration service," writes Frederic Lardinois via TechCrunch. From the report: "At Microsoft, we've seen explosive growth in both interest and deployment of containerized workloads on Azure, and we're committed to ensuring Azure is the best place to run them," Microsoft's executive VP for its cloud and enterprise group Scott Guthrie writes today. "To support this vision, we're pleased to announce that Microsoft has signed an agreement to acquire Deis -- a company that has been at the center of the container transformation." Deis provides three core open-source tools for managing Kubernetes deployments: Workflow, a platform for developers and operations teams to easily deploy and manage containerized apps; the Kubernetes package manager Helm; and Steward, a Kubernetes-native service broker (which basically allows applications to talk to each other). Like similar companies, its business model relies on providing paid support and training for these applications. The team will continue to work on these open-source tools, which are currently in use by the likes of Mozilla, CloudMine and SocialRadar.

31 comments

  1. What the hell do containers even do? by Anonymous Coward · · Score: 1

    Other than to give you an excuse to talk about your nice dockers like you have a python in your pants?

    Sure it's great that physical servers have tons of memory and storage so physical servers can virtualize smaller virtual servers. And if I need a virtual server for something, I spin up a virtual server and I run software on it. But virtualization is enough of a pain in the ass when it doesn't work right. Why would I want containers to add yet another level of abstraction getting in my way.

    1. Re:What the hell do containers even do? by jopsen · · Score: 1

      Because you can avoid virtualization... You only have worry about the bits inside your container... Which unlike a VM you can build locally.. building VMs is a hassle..

    2. Re:What the hell do containers even do? by Anonymous Coward · · Score: 0

      "Do not look at that VM behind the curtain, er, container!"

    3. Re:What the hell do containers even do? by Ungrounded+Lightning · · Score: 4, Informative

      ... if I need a virtual server for something, I spin up a virtual server and I run software on it. But virtualization is enough of a pain in the ass when it doesn't work right. Why would I want containers to add yet another level of abstraction getting in my way.

      Because containers are lighter weight than virtual servers but still get what you want done. You still have only one "extra level of abstraction" but it's less of a pain.

      A virtual server is a whole virtual machine, with its own copy of the OS, its own file system with all the libraries and utilities, etc.

      A container is a package containing your application and designating how much of which version of the OS, libraries, file system, utilities, etc. it gets to see. It looks to the app like it's running on its own little machine, just like in a VM. But it's actually running (along with everything else) under the native Linux kernel, which is using several compartmentalization mechanisms to give the app its own, limited and tuned, view of task numbers, file system, tables, etc.

      It's a sandbox, something like a chroot jail, except instead of just compartmentalizing the file system (to show a version that limits the app's view and shows it its own versions of libraries and such) it does the same thing to stuff like the processor, task environment, available devices, etc.

      --
      Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
    4. Re:What the hell do containers even do? by Anonymous Coward · · Score: 1

      Additionally, Containers are especially important to Continuous Integration platforms such as "Travis CI" when do programming/development;

      Via containers, we can test our code base against multiple versions at the same time - without requiring a different VM for each version;
      i.e: Running a separate container for each of: PHP 5.4, PHP 5.5, PHP 5.6 & PHP 7 - all these running on the same VM instance, and testing code against them.

      Additionally for Sys Admins for example, they may want to run IIS & Apache in containers, so they're sandboxed from each other.

      Personally, I see containers as the next evolution beyond Virtual Machines, and they're tremendously useful.

    5. Re:What the hell do containers even do? by swb · · Score: 1

      A container is a package containing your application and designating how much of which version of the OS, libraries, file system, utilities, etc. it gets to see. It looks to the app like it's running on its own little machine, just like in a VM. But it's actually running (along with everything else) under the native Linux kernel, which is using several compartmentalization mechanisms to give the app its own, limited and tuned, view of task numbers, file system, tables, etc.

      This is where I get lost with containers vs. virtualization. How does a container choose what version of the OS it gets to use if it runs under a given OS? The library aspects I think I get, assuming you're able to install multiple copies of the libraries or apps in question in the OS.

      Or is that the part I don't get -- it's more like an app build process, where you essentially compile the app and install its binaries and linked libraries, including system libraries into the container? I guess this makes sense, but then I don't get how you're able to obtain OS portability for containers without essentially throwing every bit of the OS into the container it might need. Or do they not have OS portability, and the container is more or less locked to the OS it was built under?

      At some point I'm curious how containers aren't just basically a method of obtaining what amounts to a statically linked binary with FS jails and networking baked into the container host.

    6. Re:What the hell do containers even do? by Anonymous Coward · · Score: 0

      Containers are pre-configured, self-contained, run anywhere the container engine does, don't require a hypervisor, can usually spin up and tear down in fractions of a second, and don't require all of the bloat and crap that ends up getting installed in a VM - vm guest tools, services you don't use, individual copies of the same kernel, etc. They can also be built and configuration-managed in version control easily, and are invariably smaller than the equivalent virtual machine.

      Containers are an *alternative* layer of abstraction - if you're running containers inside a VM, you're probably doing it wrong.

    7. Re:What the hell do containers even do? by Anonymous Coward · · Score: 0

      How does a container choose what version of the OS it gets to use if it runs under a given OS?

      Shared kernel space, separate user space.

    8. Re:What the hell do containers even do? by Anonymous Coward · · Score: 0

      if you're running containers inside a VM, you're probably doing it wrong.

      Not always, if you have a powerful physical server, VMs with different OS for very different contexts, you may actually want containers inside those VMs.

    9. Re:What the hell do containers even do? by UnknownSoldier · · Score: 2

      Here, literally, is the big picture

      Or working around /.'s shitty lameness filter, some ASCII art:

      | Application. . |
      | DLLs . . . . . | | Application. |
      | Operating Sys. | | DLLs . . . . |
      | Virtual Machine| | Container . .|
      | Operating Sys .| | Operating Sys|

      --
      Slashdot's lameness filter is lame. When the fuck are tables and markdown going to be supported???

    10. Re:What the hell do containers even do? by Anonymous Coward · · Score: 0

      Think of it this way...

      VMs have to create an entire fake machine and then you run another copy of a kernel on top of the fake machine. So you have "real HW" -> kernel -> hypervisor -> "fake HW" -> kernel -> app (someone else can argue about the kernel -> hypervisor and bare metal, blah blah)

      Containers use the kernel in the host, but load whatever supporting libraries/environments are needed and not use the hosts. So it looks like
      "real HW" -> kernel -> app, basically like running on real hardware minus a few games to limit/expose mounts to the container.

    11. Re: What the hell do containers even do? by Anonymous Coward · · Score: 0

      The only thing I have to say is... Have you ever tried it?

    12. Re:What the hell do containers even do? by trybywrench · · Score: 1

      A container is a package containing your application and designating how much of which version of the OS, libraries, file system, utilities, etc. it gets to see. It looks to the app like it's running on its own little machine, just like in a VM. But it's actually running (along with everything else) under the native Linux kernel, which is using several compartmentalization mechanisms to give the app its own, limited and tuned, view of task numbers, file system, tables, etc.

      This is where I get lost with containers vs. virtualization. How does a container choose what version of the OS it gets to use if it runs under a given OS? The library aspects I think I get, assuming you're able to install multiple copies of the libraries or apps in question in the OS.

      Or is that the part I don't get -- it's more like an app build process, where you essentially compile the app and install its binaries and linked libraries, including system libraries into the container? I guess this makes sense, but then I don't get how you're able to obtain OS portability for containers without essentially throwing every bit of the OS into the container it might need. Or do they not have OS portability, and the container is more or less locked to the OS it was built under?

      At some point I'm curious how containers aren't just basically a method of obtaining what amounts to a statically linked binary with FS jails and networking baked into the container host.

      It all pretty much started here

      https://en.wikipedia.org/wiki/...

      --
      I came to the datacenter drunk with a fake ID, don't you want to be just like me?
    13. Re:What the hell do containers even do? by Anonymous Coward · · Score: 0

      For production purposes, the resource overhead of individual virtual machines can be a dealbreaker if you're running many microservices. Each VM must have an entire full OS, along with all accompanying services (sshd, initd/systemd, file system, etc.). Even if you bother to strip the VM down to the bare essentials, it's extremely cumbersome for microservices. So you end up having to install multiple microservices per VM. That means you have to install and configure each microservice, and something is certain to break somewhere along the way (which you'll probably have to figure out on your own). You also lose some of the flexibility offered by cloud services like Amazon's elastic suite.

      Instead, you can build a container for each microservice. Because the container's "OS" is already pared down to (relatively) barebones and partially shared with the host, there's much less overhead. You can reasonably fire up each microservice as its own container instance. The container has the entire microservice already installed and configured (ideally in a way that allows you to override some settings and make it much more usable).

      There's a reason our government customer is shifting toward containerization. They've been doing virtualization for quite a while and still have significant maintenance issues with installing, configuring, and updating software inside VMs. Moving to Docker (and a couple somewhat similar technologies) brings in its own set of woes, but if initially configured well these are much simpler to manage.

    14. Re:What the hell do containers even do? by kwerle · · Score: 1

      You ought to spend a couple of hours with docker.

      Dockerfile
      ---
      # base system is Ubuntu 16.04
      FROM ubuntu:16.04

      # use /my/app to build
      WORKDIR /my/app

      # copy this directory (and all subs)
      COPY . .

      # Build my project (inside the container)
      RUN ./configure
      RUN make
      RUN ...

      # Run my app on container start
      CMD "./bin/my_app"
      ---

      docker built -t my_app_container .
      docker run my_app_container

      What you will end up with is a container that has ubuntu 16.04 running your built application. And it will ONLY be running your application. Nothing else. If you
      docker exec -it {running_container} bash
      you will get a bash shell in your running container. It will be running two processes - your app and the bash shell.

      So, yeah, it's kinda locked to the OS you specify - but you can change it up (https://www.brianchristner.io/docker-image-base-os-size-comparison/).

      At some point I'm curious how containers aren't just basically a method of obtaining what amounts to a statically linked binary with FS jails and networking baked into the container host.

      I can run a container on any OS that hosts docker.

      By dockerifying my project, I can tell any developer that they need to follow 4 steps to be up and developing:
      1. Install docker
      2. Check out the project
      3. Build the container (docker command)
      4. Run the container (docker command)

      And that's it. They can use whatever editor they want on their system. They can use whatever OS they want that hosts docker. And when it's time to deploy we use the same container they are using to do development. It removes all the tricky shit about getting environments right and mysteries about deployment. And it tosses developer's favorite OS question out the window. It's kind of magical.

    15. Re:What the hell do containers even do? by jopsen · · Score: 1

      Bare metal on-demand is becoming a thing checkout packet.net or scaleway.com
      Sure, they don't have the infrastructure or services to complete with AWS yet, but they are both adding block storage options.. scaleway even seems to adding blob storage similar to S3.

      With containers and qubernetes I can see virtualization on it's way out... Well, at-least in the cases where you want to squeeze out the last bit of performance.

  2. How do all of these layers fit together? by Anonymous Coward · · Score: 0

    How do all of these layers fit together? So I have to use an OS like Linux in my containers? And the containers are deployed to VMs and managed by Kubernetes using Workflow? And then I manage all of this container management infrastructure by using Helm to install Steward and Deis? And somehow all of this complexity will simplify my life?!

    1. Re: How do all of these layers fit together? by Anonymous Coward · · Score: 0

      No need for an OS. You can just use a kernel, like Linux and then compile your own stack.

    2. Re:How do all of these layers fit together? by ArchieBunker · · Score: 0

      Just more Linux zealots going off the deep end. We already have systemd controlling much of the OS and now binary log files. Just wait until the systemd config is a giant binary database like the windows registry. Yeah that's totally the right path...

      --
      Only the State obtains its revenue by coercion. - Murray Rothbard
  3. Re:Wow! Mozilla, CloudMine and SocialRadar! by Anonymous Coward · · Score: 0

    I agree with everything I just said, because I've definitely heard of me. I am Anonymous Coward, and I approve this message.

  4. That headline though by TWX · · Score: 3, Funny

    "Microsoft Acquires Container Platform Deis From Engine Yard"

    This literally sounds like a piece of rusty railroad rolling stock was bought from an old railyard and dragged away.

    --
    Do not look into laser with remaining eye.
    1. Re:That headline though by freeze128 · · Score: 1

      I was sure Microsoft was getting into the shipping business.

    2. Re:That headline though by Anonymous Coward · · Score: 0

      Containers are so last year. Serverless framework in the cloud.

    3. Re:That headline though by Godwin+O'Hitler · · Score: 1

      I read the summary and it still sounds like that.

      --
      No, your children are not the special ones. Nor are your pets.
    4. Re:That headline though by Anonymous Coward · · Score: 0

      I have a beef with All Leading Caps Headlines. Especially since companies (proper nouns) now call themselves after common words...

      So is the words Engine Yard a company name, or merely capitalized in the headline as all the words are?
      How about Deis?

      Leading Caps headlines were good for print, (so the text would stand out against 30 other headlines on the same page), but c'mon internet authors... we can move to "Regular sentences now with Proper Nouns capitalized and nothing else". K thx

  5. Re:First M$ Bash by Anonymous Coward · · Score: 0

    I don't like Windoze. I love linux and command line stuff. In fact I do not like GUIs at all, just text.

    I also love old timey computers like the PDP and I know how to program in assembley and cobol. all other languages are cheating and for retards.

  6. I was wondering why by Anonymous Coward · · Score: 0

    Yehuda Katz switched to Windows few months ago, now I know

  7. Well, so long to the open source versions. by Anonymous Coward · · Score: 0

    MS will kill them off and try to pigeonhole everyone into their crappy versions. God, I hate MS. Assholes ruined computing for a decade until Linux got its shit together.