Kubernetes : Application Cluster Management

Magnum : INFRASTRUCTURE CLUSTER MANAGEMENT (container as a service)

-create container clusters (easily , rapid; in 2 min) —> kubernetes : run clusters
-allow developers to iterate more quickly and easily than to do it by hand
- magnum cluster is an API resource in openstack ;
composed of nova instances , neutron networks, security groups and others resources
combined using a heat stack
-openstack users can use their credentials (keystone) in order to create magnum
clusters
-clusters may be scaled up or down by adding or removing nodes from them
→ heat facilitates setup and scaling (orchestration )

cluster template
-model for creating cluster resource.
- a way for operators to make it easy for end users to make magnum clusters

Native client : if deploying docker swarm cluster then our native client is docker
→ magnum is designed to that the end users interact with the native client rather
then with openstack tools

—-----

Features:

-multi-tenant Control and data planes

-offers Choice of COE (Container orchestration Engine) : Docker swarm , Kuberetes…
→ choose different COE depending on what kind of workload you’re running
→ avoid locking into a single container orchestration tool

OpenStack Orchestration (heat)

OpenStack Orchestration provides templates to create and manage cloud

resources such as storage, networking, instances, or applications. Templates
are used to create stacks, which are collections of resources.

For example, you can create templates for instances, floating IPs, volumes,
security groups, or users. Orchestration offers access to all OpenStack core
services with a single modular template, as well as capabilities such as auto-
scaling and basic high availability.

OpenStack Orchestration advantages include:

• A single template provides access to all underlying service APIs.

• Templates are modular and resource-oriented.
• Templates can be recursively defined and reusable, such as nested
stacks. The cloud infrastructure can then be defined and reused in a
modular way.
• Resource implementation is pluggable, which allows for custom
resources.
• Resources can be auto-scaled, and therefore added or removed from
the cluster based on usage.
• Basic high availability functionality is available.

Orchestration components

The following diagram shows the main interfaces that the Orchestration
service uses to create a new stack of two new instances and a local network.