taikun.cloud

Taikun Logo

Documentation

Our Lingo

Taikun Terminology #

Access Profile – a profile using HTTP proxy, ssh (we support RSA, ECDSA or Ed25519), DNS or NTP to access your cluster, the condition is that you add it to the project during creation.

Alerting Profile – a profile attached to a Project, provides notifications about alerts in your Project.

Audit Log – summary of changes made in Projects.

Backup credentials – Taikun uses S3-compatible backup. S3 (Simple Storage Service) Backup is a desktop application using Amazon’s infrastructure for remote backups and secure online file storage. It features strong encryption, compression, easy access to your backed-up files, and built-in backup scheduling.

Backup policy – defines the ground rules for planning, executing, and validating backups and includes specific activities to ensure that critical data is backed up to secure storage media located in a secure location.

  • schedules = policies
  • backups = a copy created based on policy
  • restores = a copy from backup data

Billing Rules – rules for Chargeback. Every rule is based on an external source, metrics, and price.

Chargeback – external billing set by Billing Rules, you can see the price for every rule for the selected time period.

Cloud – a global network of servers, each with a unique function. These servers are designed to either store and manage data, run applications, or deliver content or a service such as streaming videos, webmail, office productivity software, or social media. Cloud operates as a single ecosystem.

  • Taikun supports OpenStack, Amazon Web Services (AWM), Microsoft Azure, and Google Cloud Platform (GCP)

Cluster – Taikun Project – a set of computers that work together so that they can be viewed as a single system

  • Kubernetes cluster – a set of nodes that run containerized applications. Containerizing applications package an app with its dependencies and some necessary services. They are more lightweight and flexible than virtual machines. This way, Kubernetes clusters allow applications to be more easily developed, moved and managed.

CNI – Container Network Interface, consists of a specification and libraries for writing plugins to configure network interfaces in Linux containers, along with a number of supported plugins.

Credentials – data confirming the identity of the user or external application (e.g. the user name and password, user name and API key, or authentication token that the identity service provides). In Taikun you can find Cloud Credentials, Backup Credentials, Billing Credentials, and Showback Credentials.

CSM – Customer Success Manager

Endpoint – a remote computing device that communicates back and forth with a network to which it is connected (usually URL address).

Flavor – is an available hardware configuration for a server. Defines the compute, memory, and storage capacity of nova computing instances

Floating IP – a kind of virtual IP address that can be dynamically routed to any server in the same network. Multiple servers can own the same Floating IP address, but it can only be active on one server at any given time.

Import network – use the network already created in the Cloud (works for OpenStack)

Keycloak – an open-source software product to allow single sign-on with Identity and Access Management aimed at modern applications and services. 

Kubeconfig file – a file used to configure access to Kubernetes when used in conjunction with the kubectl command line tool (or other clients).

Kubernetes – a portable, extensible, open-source platform for managing containerized workloads and services, that facilitates both declarative configuration and automation.

Kubernetes Profile – a profile for enabling Kubernetes functions and features (such as Octavia, Load Balancer, or Proxy on bastion)

Load Balancer – refers to the process of distributing a set of tasks over a set of resources (computing units), with the aim of making their overall processing more efficient. Load balancing can optimize the response time and avoid unevenly overloading some compute nodes while other compute nodes are left idle.

Metrics – measure specific characteristics in a countable manner. Metrics are used in monitoring and billing.

Monitoring – is the process to gather metrics about the operations, to ensure everything functions as expected to support applications and services. By enabling monitoring you can see Logs, Alerts or Metrics.

Node – a worker machine in Kubernetes and may be either a virtual or a physical machine, depending on the cluster.

Octavia – exposes the Service externally using the load balancers from OpenStack.

Pod – the smallest execution unit in Kubernetes. A pod encapsulates one or more applications.

Proxy on Bastion – exposes the Service on each Node’s IP at a static port, the NodePort. You’ll be able to contact the NodePort Service, from outside the cluster, by requesting NodeIP:NodePort.

Reboot – to reload the operating system of a computer: to start it up again.

  • HARD – the power to the system is physically turned off and back again causing an initial boot
  • SOFT – system restarts without the need to interrupt the power

Role – defines the rights and permissions granted to user accounts. In Taikun there are Users, Managers (Owner), or Partners. You can take a look at each role in our User Types article.

Showback – internal billing set by Showback Rules, you can see the price for every rule for the selected time period. You can also set an external source for billing.

Showback Rules – rules for Showback. Every rule is based on metrics and price.

Subscription – an amount of money that you pay regularly to use Taikun. Price varies depending on the number of users, projects, or TCU.

Token – an alphanumeric text string that provides access to APIs and resources.

User – digital representation of a person using Taikun. Each user is defined by username (e-mail) and the access is granted by a token. User is an assigned role with its permissions.

Webhook – way web applications can communicate with each other, allows you to send real-time data from one application to another whenever a given event occurs.

Was this article helpful?