Learn About Landscape! ODS Keynote

This article was last updated 10 years ago.


In complex computing scenarios, creating a holistic or unified update procedure across multiple clouds and hundreds of separate machines feels like an impossible task. And what do you want to do when your systems estate reaches the thousands, is it possible to automate and simplify cloud management so that thousands of systems can be managed as easily as one?

In this latest of our OpenStack Summit seminars, Dean Henrichsmeyer, Engineering Manager for our Landscape group talks about the challenges facing compute-heavy, cloud-based organisations when trying to manage a growing cloud ecosystem. He explains how Landscape has been designed to scale from the outset; able to manage (with ease) up to 40,000 machines. He also talks about the importance of understanding, and responding to milestones in the life-cycle of each cloud. He digs into the intricacies of working with Autopilot and demonstrates how, by putting your OpenStack cloud on Autopilot you can automate the way your cloud evolves using Canonical’s wealth of experience and tools.

Watch our OpenStack Summit keynote below.

Talk to us today

Interested in running Ubuntu in your organisation?

Newsletter signup

Get the latest Ubuntu news and updates in your inbox.

By submitting this form, I confirm that I have read and agree to Canonical's Privacy Policy.

Related posts

The foundations of software: open source libraries and their maintainers

Open source libraries are repositories of code that developers can use and, depending on the license, contribute to, modify, and redistribute. Open source...

From inspiration to impact: design students from Regent’s University London explore open design for their dissertation projects

Last year, we had the opportunity to speak at Regent’s UX Conference (Regent’s University London’s conference to showcase UX work by staff, students, and...

When an upstream change broke smartcard FIPS authentication – and how we fixed it

This is the story of how Canonical’s Support team provided bug-fix support: we tracked down an upstream change in OpenSC that inadvertently broke FIPS...