Jargon Dictionary

A

Axsh

Axsh Co. LTD are the authors of Wakame-vdc and OpenVNet. Pronounced: Ah-ku-shu.

B

Backup Storage

Backup storage is a means of storing backup objects. Backup objects can be stored on a local file system, served through http or using Indelible FS (experimental).

Backup Object

A backup object is basically a hard drive image. Backup objects that hold bootable partitions are called machine images.

C

Collector

The collector is one of Wakame-vdc's processes. It's in charge of making scheduling decisions and database access.

D

Dcmgr

Stands for Data Center Manager. In Wakame-vdc, this is just another word for the WebAPI

E

Endpoint

An endpoint is a single part of the WebAPI that the user can call to control Wakame-vdc. For example GET http://<webapi ip>:<webapi port>/api/instances is an endpoint. POST http://<webapi ip>:<webapi port>/api/images is another endpoint and so on.

F

G

GUI

See WebUI.

H

Host/Host Node

See HVA.

HVA

The HVA (HyperVisor Agent) is the part of Wakame-vdc that actually starts instances. On a production environment, you would likely have several dedicated bare metal hosts for this.

Also known as host or host node.

I

Instance

A virtual machine managed by wakame-vdc.

Instances network

An L3 network in which instances are started. This can technically be the same network used for the management line but on production environments, it is probably a good idea to separate them.

J

K

L

M

Machine Image

A backup object that holds a bootable partition. You are able to start instances of machine images.

Management Line / Management Network

This is a network that Wakame-vdc uses for communication between its different nodes.

Meta-data

In Wakame-vdc's context, meta-data usually refers to information that is passed to instances when they start. It includes for example the instance's IP addresses, network host name and thrusted public keys. Meta-data is usually delivered as files on an extra (tiny) hard drive.

N

NATbox

The NATbox is an optional Wakame-vdc node that provides one to one network address translation for instances.

Node

Refers to a server that a Wakame-vdc process runs on. Can be physical or a VM but not an instance.

O

OpenVNet

An full virtual networking implementation using OpenFlow. This project is completely separate from Wakame-vdc but Wakame-vdc can use it to implement virtual networking. http://openvnet.org

P

Q

R

S

Scheduling

The decision making process when starting a new instance. Deciding things like the network to join, the MAC and IP address to be assigned, which HVA to use, etc. are referred to as scheduling. Scheduling takes place in Wakame-vdc's collector.

Security Group

Wakame-vdc's dynamically updating firewall. You can put vnics into groups that determine which network traffic is blocked and which is accepted. These firewalls are updated dynamically as the layout of the virtual data center changes. Read the security groups guide for more details.

T

U

User data

User data is an arbitrary field that users can set when starting an instance. The user data will be delivered along with meta-data and will thus be accessible from inside the instance. For example users can create custom images with scripts in them that react to user data.

V

vdc-manage

A command-line front-end for Wakame-vdc's database. It can be found at /opt/axsh/wakame-vdc/dcmgr/bin/wakame-vdc

Vnic / Vif

Stands for Virtual Network Interface Card or Virtual Interface. In either case, the term refers to an instance's simulated network card.

W

WebAPI

This is Wakame-vdc's user interface. You tell Wakame-vdc to do stuff by making http requests to this API.

WebUI

Wakame-vdc's GUI. It's actually a Rails application that sits in front of the WebAPI.

X

Y

Z