As we’ve talked about before, a few of us in Dell’s CTO group have recently been working with our friends at Joyent. This effort is a part of the consideration of platforms capable of intelligently deploying workloads to all major infrastructure flavors – bare-metal, virtual machine, and container.
Today’s post on this topic comes to us complements of Glen Campbell — no, not that one, this one:
Glen has recently come from the field to join our merry band in the Office of the CTO. He will be a part of the Open Source Cloud team looking at viable upstream OSS technologies across infrastructure, OS, applications, and operations.
Cloud, allows customers to take advantage of the technologies and scale Joyent leverages in their Public Cloud.
On the Triton Elastic Container Infrastructure (which I’ll call “Triton” from now on) bare-metal workloads are intelligently sequestered via the use of the “Zones” capabilities of SmartOS. Virtual machines are deployed via the leveraged KVM hypervisor in SmartOS, and Docker containers are deployed via the Docker Remote API Implementation for Triton and the use of the Docker or Docker Compose CLIs.
What’s the Dell/Joyent team doing?
As part of interacting with Triton we are working to deploy a Dell application, our Active System Manager (ASM), as a series of connected containers.
The work with Triton will encompass both Administrative and Operative efforts:
Investigate user password-based authentication via LDAP/Active Directory
in conjunction with SSH key-based authentication for CLI work
Newer Triton node client to see next-gen of “sdc-X” tools
build a multi-tier Docker application via Docker Compose, deploy on Triton via its Docker Remote API endpoint
deploy a 3-tier application composed of:
Zone-controlled bare-metal tier (db – MySQL)
Docker-controlled container tier (app – Tomcat)
VM-based tier (presentation – nginx)
Dell Active System Manager — a work in progress
aligning with Dell’s internal development and product group to establish a container architecture for the application
Our test environment has been created and the Triton platform has been deployed. Follow-on blog posts will cover basic architecture of the environment and the work to accomplish the Admin and Ops tasks above. Stay tuned!
Instructions: Installing Triton Elastic Container Infrastructure (updated to reflect learnings from setting up Triton in the Dell CTO lab)
Here is our third and final post walking through the setting up of the Joyent Triton platform in the Dell CTO lab. In the first post, Don Walker of the CTO office gave an overview of what we were doing and why. The second laid out the actual components and configuration of the platform.
Today’s video is a walk-through of the installation process where Don shares his experience in setting up the Triton Platform.
When we pick this series up again it will focus on containerizing Dell’s Active System Manager and then loading it on Triton. Not sure how long this work will take so stay tuned!
Some of the ground Don covers:
Before installing Triton, you need networking set up and working. Don double clicks on the network configuration and what we did to make sure it was working.
Step one in installing Triton, is to create a bootable USB key and install the head node. There is a scripted set up which is dead simple. Lays down SmartOS and Triton services
Compute node install is also scripted which contains a lot of the info you entered during the head node configuration. After this you run acceptance tests
Great support from Joyent with a couple of small issues we had
Unacceptable character in pswd. This info was fed back to the devs and is now fixed.
We forgot to disable the SATA port and kept getting error messages. Once we disabled it, it worked.
Continuing from the previous post, here is a more detailed explanation of the Joyent Triton platform we set up in the CTO lab. Triton is Joyent’s elastic container infrastructure that runs on their cloud, a private cloud or both.
The idea behind setting up this instance is, working with Joyent, to learn about the platform. The next step is to work with the Dell Active System Manager (ASM) team to decompose ASM into microservices and then run it on the Triton platform.
Take a listen as Don walks through the actual layout of the instance.
Some of the ground Don covers
Our minimalist set-up featuring two Dell R730 servers (the schematic only shows one for simplicity. An R730 contains two 520s). Don explains how they are configured and how ZFS affects the set up.
The two Dell Force 10 S6000 switches.
A double-click on the networking set up
The roles the compute and head nodes (the head node acts as the admin into the system).
A while back I tweeted how we had begun setting up a mini-instance of Joyent’s Triton in our Dell CTO lab. Triton is Joyent’s elastic container infrastructure that runs on their cloud, a private cloud or both. This cloud platform includes OS and machine virtualization (e.g. Docker with regards to the former and typical VMs under KVM for the latter).
About a week ago we got the platform set up about and I grabbed sometime with Don Walker of Dell’s enterprise CTO office to tell us about it.
In this first of three videos, Don gives an overview of the work Dell is doing with Joyent. He describes what we’ve set up in the lab and talks about where we hope to take it.
Some of the ground Don covers
Don’s focus on Open Source Cloud eg Open Stack, containers, cloud networking and storage solutions
What the enterprise CTO office does
What we’re doing with Joyent: evaluating Triton and the process of taking existing products and put them into microservices and containers.
Looking at Dell’s ASM (Active System Manager) and what it means to refactor for microservices and containers
Overview of what was set up in the lab: a minimalist 2 node instance consisting of head and compute nodes.
While I was in San Francisco back in November, I stopped by Joyent’s headquarters. The main purpose was to talk about the Docker/Triton platform we are setting up in the CTO lab.
While I was there I chatted with Joyent’s Casey Bisson, director of product management. Casey took me through a couple of white board sessions around containers and VMs. This first session talks about how containers and VMs work together, how they’re different and where Joyent’s elastic container infrastructure, Triton, fits.
Some of the ground Casey covers
Linux allows you to build containers on your laptop and push them, as is, to the cloud. For other OS’s you need to use VMs
Containers in the cloud within VMs and the affect on efficiency
Running containers on bare metal, security concerns and how Joyent addresses these concerns
How Triton virtualizes the network into the container
KubeCon: Learning about Joyent and Triton, the elastic container infrastructure – Barton’s blog
Here’s another interview from KubeCon back in November. This one’s a twofer. Joyent’s CEO and CTO, Scott Hammond and Bryan Cantrill respectively, talk about taking their learnings from Solaris zones and applying them to the world of modern apps and containers.
Some of the ground Scott and Bryan cover
Joyent, a software company focused on delivering a container native software infrastructure platform
They had been doing containers for 6 years and when Docker came along they focused on that
How Solaris zones came about, how Joyent picked it up and ran with it, and how it acted as a foundation for today’s containerized world – How they were in the right place at the wrong time
Whats in store for Joyent going forward – supporting the movement to modern app dev and the intersection of containers – taking this new tech and productizing and simplifying them to allow enterprises to roll them out