OpenStack Mitaka Dashboard

OpenStack Mitaka Dashboard One, write in front

This article mainly describes the OpenStack Mitaka Horizon Components feature, the Mitaka version of Horizon has added a lot of new features, here specifically to organize, the process of writing documents, I am familiar with the process, organized into notes to follow their own review. At present, there is no in-depth functional understanding, for the time being simply through the interface function and the previous version slightly contrast, follow-up will gradually improve.
If reproduced, please retain the author's information.
Email address: [Email protected]

Second, identity certification

1), Login

All components of the Mitaka version already support Keystone's V3 API interface,
Login supports domain selection, default is defaults, currently horizon does not support creating and adding domain on the interface.

2), Project

1, now as if the default administrator login, is transferred to the Administrator->project interface. For OpenStack, Project equals tenant.

2. Create a project Add a user this block increases the project group (that is, the user group) as long as members within this group have access to the project group.

3), user group

is to make a group of users, a user can belong to more than one group. This makes it easy to manage permissions. Created group, also cannot set permissions on the interface, just can add users to group.

4), role

Roles can be created on the interface, but the actual roles permissions are required to be configured Joson files in the system. System built-in admin and member two kinds of roles, generally, the user who created the project, the assigned permissions are member roles.

Third, the project

1. Cloud Host

Create a cloud host the whole process is more process, the user Help information is more complete, the experience is better than the previous version, the Virtual machine creation form in the L version has entered the development, but the functionality is not merged into the previous version.

Abandoned cloud Host: The personal feel should be in the delete above, the discarded virtual machine will not be deleted, should be in a shutdown state, only the disk resources, but can not be turned off unless "obsolete". Adds a layer of action on top of the delete virtual machine.
Connection interface: Select the network to connect to the interface, the internal network can add interface connection
Detach interface: Unbind the network to which the interface is to be connected

2. Cloud Drive

Disk Consistency group: I don't know yet.
Create Transfer/Accept transfer: The previous version is available, and the ownership of the drive can be transferred from one project to another. Once a volume transfer is created in the transferor project, it can be "accepted" in the receiving project. This is equivalent to the Cinder transfer-create command.

3. Network routing

Adding a routing table through the interface

Iv. Administrator

1. Virtual Machine Manager

Compute Host can disable the service of the node. Let the node enter maintenance mode.

Five, the developer

1, provide developers a quick view of the Bootstrap style sheet page

2. OpenStack Mitaka provides two theme templates (default, Material), which are set by the upper right corner

OpenStack Mitaka Dashboard