June 9, 2016Summer '16 documentation updates by Casey Bisson
We're always updating our documentation, but it's worth calling out some of the big changes, including the following recent updates to ContainerPilot, Triton CNS, CloudAPI, Triton CLI, and Docker.
June 1, 2016Cisco's Mantl on Triton by Casey Bisson
Cisco's Mantl is intended to be a standardized platform for containerized microservices. It packages a number of open source components with a single install process. Joyent Triton, including our public cloud and private data centers world wide, is now an officially documented platform for Mantl.
May 12, 2016The Autopilot Pattern and the rise of app-centric micro-orchestration by Casey Bisson
Container scheduling and orchestration are among the most critical problems to solve in modern applications, but it turns out they're not so tough if you look at them the right way.
May 11, 2016Container-Native Means Big Savings by Bill Fine
Joyent lowers pricing for container-native computing and demonstrates the advantages of running containers securely on bare metal with new instance packages designed for every workload.
May 5, 2016WordPress on Autopilot by Casey Bisson
Joyent and 10up introduce Autopilot Pattern WordPress implementation that makes it a snap to build and operate WordPress websites at any scale.
April 19, 2016Mesosphere open-sources DC/OS container orchestration solution by Casey Bisson
Joyent celebrates open source DC/OS container orchestration.
April 12, 2016Monitoring and scaling applications with ContainerPilot telemetry by Tim Gross
Introducing application telemetry in ContainerPilot to make scaling decisions easy.
April 12, 2016ContainerPilot: the app-centric orchestration solution for modern ops by Casey Bisson
Triton ContainerPilot™ (formerly Containerbuddy) makes automated discovery, configuration, and monitoring simple and straightforward.
April 4, 2016More than just a Drop(box) in the bucket? by Bill Fine
At Joyent, we build open source software to automate data centers. Like Amazon, we operate our own public cloud. Unlike Amazon, we also offer the software that powers our public cloud to enterprises who want to run their own data centers. Simply put, we make it easy for companies to switch from the public cloud to a private data center, or to use both in a hybrid model. And, as I look across our customer base and sales pipeline, I see a clear trend toward a hybrid cloud model emerging among what I call “cloud mature” companies.
March 23, 2016DevOps questions: patterns for multi-data center and multi-cloud applications by Casey Bisson
DevOps expert Casey Bisson answers your DevOps questions. Today's question: how can I successfully run my applications in multiple data centers?
March 18, 2016Production Docker Logs on Triton by Tim Gross
docker logs to get our container logs works in development but in production we need to centralize our logs. Triton has support for the syslog, Graylog, and Fluentd log drivers and we can use them to support production-ready log collection.
March 15, 2016New images to run your favorite applications on Triton bare metal infrastructure containers by Christopher Horrell
Enjoy bare metal performance with Joyent's latest releases of Node.js, MongoDB, PostgreSQL and Percona running container-native on Triton.
March 8, 2016Introducing Triton Container Name Service by Casey Bisson
Triton CNS is a free, automated DNS solution that offers consistent and predictable addresses for changing infrastructure. Use Triton CNS as a free, high-performance alternative to virtual IPs and hosted load balancers.
March 8, 2016Modern application blueprint: Node.js + Docker + NoSQL by Tim Gross
This post demonstrates how you can deploy and scale a Node.js application backed by Couchbase and load balanced with Nginx. All the components are running in multiple Docker containers on Triton, and use ContainerPilot to automate discovery and configuration. We're using Docker Compose to deploy the application and scale it across the data center on Triton.
March 3, 2016Implementing the autopilot pattern by Tim Gross
Deploying containerized applications and connecting them together is a challenge because it forces developers to design for operationalization. Autopiloting applications are a powerful design pattern to solving these problems. By pushing the responsibility for understanding startup, shutdown, scaling, and recovery from failure into the application, we can build intelligent architectures that minimize human intervention in operation. But we can't rewrite all our applications at once, so we need a way to build application containers that can knit together legacy and greenfield applications alike. This project demonstrates the autopilot pattern by applying it to a simple microservices deployment using Nginx and two Node.js applications.