Do you remember the days of deploying an N-tier application to on-premises servers? The planning that went into determining the right amount of hardware to use so that you weren’t under or significantly over-provisioned. Deployments were often problematic because what ran well on the developer’s computer didn’t always work outside of their environment. Deployments also were assumed to cause downtime, and scheduled during non-peak hours.
In the event of a hardware failure, your app might have been unavailable depending on how much hardware you had access to, and how the application was designed. Failovers may or may not have been automatic, and frankly, it was all a lot of work.
Well, if you thought that was difficult, imagine trying to do all of this at the scale of Google, Facebook, Twitter, Netflix, or similar companies.
All of the companies I just mentioned found that hyperscale computing required a new way to look at things. And regardless of the actual tools that they used, they all had the same solution, which was to treat their entire data center as a single entity.
And that’s what DC/OS does: it’s a central OS for your data center, and it’s the topic of this course.
- You should understand how DC/OS is used
- You should have a high-level understanding of DC/OS
- You should be familiar with the UI
- You should be familiar with the CLI
- You should be able to install services from the catalog
- DevOps Engineers
- Site Reliability Engineers
- Familiarity with containers
- Comfort with the command line
|Lecture||What you'll learn|
|Intro||What to expect from this course|
|A Brief History||The history of DC/OS|
|Overview||An overview of DC/OS|
|Components||About the components of DC/OS|
|Exploring the UI||How to navigate the UI|
|Installing WordPress (UI)||How to install WordPress from the Catalog|
|Installing WordPress (CLI)||How to install WordPress from the Catalog|
|Summary||How to keep learning|
If you have thoughts or suggestions for this course, please contact Cloud Academy at email@example.com.
Welcome back! I want to wrap up this course with a summary of what was covered, as well as talk about what’s coming up next.
Review of Course Content
Let’s review what we’ve covered in each of the lessons. In the first real lesson we talked about the history of DC/OS. Understanding the history is important, because DC/OS isn’t just some new product that popped up. DC/OS is the combination of well tested, production ready tools, centered around Apache Mesos. Recall that Mesos is used at companies such as Twitter and Netflix where high availability is crucial to their business.
In the overview lesson we talked about how DC/OS lives up to its name as a data center operating system. Having an OS for your data center allows you to abstract all of the individual servers and treat that as one unit. Companies such as Autodesk used this to improve their operations and reduce costs.
After that we looked at the user interface and went through some of the functionality. Finally we installed Wordpress and MySQL with both the CLI and UI.
At the start of the course I listed off some learning objectives. Having made it this far you should now understand the history of DC/OS and its value. You should have a high level understanding of how DC/OS is used and its components. And you should also be familiar with how to use the Catalog to install packages.
So, what’s next? Now that you have the fundamentals down you’re ready to start diving in more. I recommend checking out the course DC/OS container orchestration. This is where you’ll learn how to start managing containers. I also recommend giving the official docs a read. They have a lot of great info as well as tutorials.
As I mentioned at the start, I enjoy hearing from you. If you don’t give feedback about what you like and dislike about the content, I can’t improve it. So if you want to reach out you can reach me via firstname.lastname@example.org, or on Twitter via @sowhelmed.
That’s going to do it for this course, thanks for watching and I’ll see you in the next course!
Ben Lambert is a software engineer and was previously the lead author for DevOps and Microsoft Azure training content at Cloud Academy. His courses and learning paths covered Cloud Ecosystem technologies such as DC/OS, configuration management tools, and containers. As a software engineer, Ben’s experience includes building highly available web and mobile apps. When he’s not building software, he’s hiking, camping, or creating video games.