pinboard August 15, 2015

  • ContainersTeam – OpenStack
    OpenStack Containers Team
    The Containers team is a cross-functional team for OpenStack community stakeholders interested in adding better support in OpenStack for container technology. The team was initially formed in May 2014, and currently has a clear vision for advancing container technology in existing OpenStack services, and new services and tools that evolve OpenStack to track with new technological advances in this area. This team will be considered successful once users of OpenStack can create and manage containers on OpenStack with an experience consistent with what they expect from using the Nova service to get virtual machines.

    This team is actively engaged refining Magnum, a Containers Service for OpenStack.

  • Project Atomic
    Create and Run Applications in Linux Containers
    Create your application using Docker containers. Deploy and manage containerized applications on a proven, trusted platform.

    Project Atomic introduces Atomic App — an implementation of the Nulecule specification, which lets you manage multi-container applications and orchestration metadata as easily as you manage RPMs.

  • Magnum Demo on Vimeo
    starting up k8s and swarm clusters using Heat
  • Magnum – OpenStack
    Magnum is an OpenStack API service developed by the OpenStack Containers Team making container orchestration engines such as Docker and Kubernetes available as first class resources in OpenStack. Magnum uses Heat to orchestrate an OS image which contains Docker and Kubernetes and runs that image in either virtual machines or bare metal in a cluster configuration. Click below for a 5 minute demo of how Magnum works.
  • Open Container Initiative
    In the past two years, there has been rapid growth in both interest in and usage of container-based solutions. Almost all major IT vendors and cloud providers have announced container-based solutions, and there has been a proliferation of start-ups founded in this area as well. While the proliferation of ideas in this space is welcome, the promise of containers as a source of application portability requires the establishment of certain standards around format and runtime. While the rapid growth of the Docker project has served to make the Docker image format a de facto standard for many purposes, there is widespread interest in a more formal, open, industry specification, which is:

    not bound to higher level constructs such as a particular client or orchestration stack
    not tightly associated with any particular commercial vendor or project
    portable across a wide variety of operating systems, hardware, CPU architectures, public clouds, etc.
    The specification will be available at The newly expanded team of maintainers (both original libcontainer maintainers and the appc maintainers) are busy preparing the first draft of the specification, and intend to release it in 2-3 weeks.

    Docker is donating its container format and runtime, runC, to the OCI to serve as the cornerstone of this new effort. It is available now at

    Initiative Sponsors: Apcera, AT&T, AWS, Cisco, ClusterHQ, CoreOS, Datera, Docker, EMC, Fujitsu, Google, Goldman Sachs, HP, Huawei, IBM, Intel, Joyent, Kismatic, Kyup, the Linux Foundation, Mesosphere, Microsoft, Midokura, Nutanix, Oracle, Pivotal, Polyverse, Rancher, Red Hat,, Suse, Sysdig, Twitter, Verizon, VMWare

  • opencontainers/specs
    This project is where the Open Container Initiative Specifications are written. This is a work in progress. We should have a first draft by end of July 2015.

    Table of Contents

    Filesystem Bundle
    Container Configuration
    Linux Specific Configuration
    Runtime and Lifecycle

  • opencontainers/runc

    runc is a CLI tool for spawning and running containers according to the OCF specification.

    State of the project

    Currently runc is an implementation of the OCF specification. We are currently sprinting to have a v1 of the spec out within a quick timeframe of a few weeks, ~July 2015, so the runc config format will be constantly changing until the spec is finalized. However, we encourage you to try out the tool and give feedback.


    How does runc integrate with the Open Container Format? runc depends on the types specified in the specs repository. Whenever the specification is updated and ready to be versioned runc will update it’s dependency on the specs repository and support the update spec.

  • Apache Stratos
  • Deploy in scale with Docker, CoreOS, Kubernetes and Apache Stratos
  • Inside Amazon: Wrestling Big Ideas in a Bruising Workplace –
  • Scott Kelly on Twitter: "#EarthArt Perfectly Patagonia and wall worthy. #YearInSpace"
    RT @StationCDRKelly: #EarthArt Perfectly Patagonia and wall worthy. #YearInSpace
  • Oliver Sacks: Sabbath –
  • on Twitter: "Roadtripping man annoys his sister with seven hours of lip syncing"
    RT @avantgame: I smiled the whole video. Also the end is the best 😀 happy Friday!
  • #ILookLikeAnEngineer is not about looking—it’s about listening
    RT @selenalarson: Last night’s #ILookLikeAnEngineer gathering was an important event. Here’s my story:
  • Juju & Kubernetes: The power of components | Ubuntu Insights
  • mesosphere/kubernetes-mesos
  • Large-scale cluster management at Google with Borg
    EuroSys paper
  • Building on Kubernetes: Bringing Google-Scale Container Orchestration and Management to the Enterprise – OpenShift Blog
  • Red Hat Reimagines OpenShift 3 PaaS With Docker
  • Red Hat and Google Collaborate on Kubernetes to Manage Docker Containers at Scale | Red Hat
  • Get Started Orchestrating Containers with Kubernetes – Red Hat Customer Portal
  • Issues · kubernetes/kubernetes v1.1

Digest powered by RSS Digest


There are no comments yet...Kick things off by filling out the form below.

You must log in to post a comment.