What is a container?

Linux containers are self-contained execution environments with their own, isolated CPU, memory, block I/O, and network resources that share the kernel of the host operating system. The result is something that feels like a virtual machine, but sheds all the weight and startup overhead of a guest operating system. You can link containers together, set security policies, limit resource utilisation and more.

The Container Orchestration Engine

Container Orchestration refers to the automated arrangement, coordination, and management of software containers.

The process of deploying multiple containers to implement an application can be optimized through automation. This becomes more and more valuable as the number of containers and hosts grow. This type of automation is referred to as orchestration. Orchestration can include a number of features, including:

  • Provisioning cluster hosts.
  • Instantiating a set of containers.
  • Rescheduling failed containers.
  • Linking containers together through agreed interfaces.
  • Exposing services outside of the cluster.
  • Scaling the cluster by adding or removing containers.

Catalyst Cloud currently only offers Kubernetes so we will focus on that as our default container orchestration engine (COE).

Providing feedback

Our goal with this alpha release is to establish a feedback loop and collaborate with early adopters of the technology, to ensure it meets the unique needs of our customers in NZ.

At this stage, the service is expected to have some rough edges and bugs. If you encounter an issue or have a suggestion on how we can improve it, please raise a ticket via the Support Centre.

Where possible, when creating support tickets, please include the output of the following command to assist our support team in helping you to resolve it.

$ openstack coe cluster show <cluster_name>

Known Issues

This is an overview of the issues encountered in the process of testing this Technical Preview release.

Cluster takes a long time to deploy

Description: Currently the time taken to deploy a cluster from commandline or dashboard is in the vicinity of 15-25 minutes.

Status: The cause of the problem is known and a fix is being investigated.

Workaround: None.