Shulou(Shulou.com)06/01 Report--

OpenStack graphical Dashboard [7] OpenStack graphical Dashboard [7]

Openstack

Time: November 28, 2016

Deploy openstack Management Services

Dashboard (horizon) is a web interface that enables cloud platform administrators and users to manage different Openstack resources and services.

Dashboard

Provide a web interface to operate openstack system, use Django framework based on openstack API development, support session storage in DB memcached support cluster

Install the package:

[root@linux-node1 ~] # yum install openstack-dashboard-y

Virtual machine creation process

The first step is to enter the user name and password into the keyston for authentication. After the authentication is passed, a token is assigned, and then the token can be used to access other services. The second step is to convert the request for creating a virtual machine to REST API and send it to NOVA API, and then it takes the token to keyston to query whether it is legal. The fourth step is NOV api and database interaction, the virtual machine information to be created is written to the database, and the fifth step is to send the message big rabbitMQ. The message will be sent to nova scheduler, the sixth step is nova scheduler algorithm to confirm the physical machine on which the virtual machine will be created, the seventh step is nova scheduler to interact with the database and write the information generated by the virtual machine to the database, the eighth step is nova computer to receive the message to create the virtual machine, the ninth step is nova computer to the database to query the information to be created by the virtual machine, and the tenth step is to communicate with the database. The new version of openstack uses nova conductor instead of step 9, step 11 nova conductor updates the database information, then nova computer obtains the creation information of the virtual machine from the database and then carries on the next step of creating the virtual machine, step 12 contacts glance to obtain the image, step 13 glace contacts keyston for authentication, step 14 contacts neutron to obtain network, step 15 neutron contacts keyston for authentication, step 16 nova computer contacts cinder to obtain disk 17 do not cinder to keyston for authentication, step 18 mova computer calls KVM to create a virtual machine.

View roles

[root@linux-node1 ~] # openstack role list+--+-+ | ID | Name | +-- +-+ | 4161dec8714f468f832a55a6ec2abb9e | user | | c934dad680e142d09c434e2301b2a9bf | admin | +-- +-

Edit file / etc/openstack-dashboard/local_settings

[root@linux-node1 ~] # vim / etc/openstack-dashboard/local_settings

Allow all hosts to access the dashboard

30 ALLOWED_HOSTS = ['*',]

Configure the API version

55 OPENSTACK_API_VERSIONS = {56 # "data-processing": 1.1,57 "identity": 3,58 "volume": 2,59 "compute": 2,60}

Configure the dashboard on the controller node to use the OpenStack service: 158 OPENSTACK_HOST = "192.168.56.11"

Enable version 3 authentication API

159OPENSTACK_KEYSTONE_URL = "http://%s:5000/v3"% OPENSTACK_HOST

The default user role created through the dashboard is configured as user

160 OPENSTACK_KEYSTONE_DEFAULT_ROLE = "user"

Enable support for domain

64 OPENSTACK_KEYSTONE_MULTIDOMAIN_SUPPORT = True

The default domain configuration when creating a user through the dashboard is default

72 OPENSTACK_KEYSTONE_DEFAULT_DOMAIN = 'default'

If you select network parameter 1, disable the support for layer 3 network services:

Tip: if you don't disable it, an error may occur later.

260 OPENSTACK_NEUTRON_NETWORK = {261 'enable_router': False,262' enable_quotas': False,263 'enable_ipv6': False,264' enable_distributed_router': False,265 'enable_ha_router': False,266' enable_lb': False,267 'enable_firewall': False,268' enable_***': False,269 'enable_fip_topology_check': False

Modify time zone

TIME_ZONE = "Asia/Shanghai" changed to Asia and Shanghai

Save restart

[root@linux-node1 ~] # systemctl restart httpd

Landing page

Default domain: default

User name: demo

Password: demo

Tip: we can also log in using admin users.

Login address: http://192.168.56.11/dashboard

Management interface

Admin users need to be controlled in the administrator window

Introduction to CVM

Admin users can manage all CVMs created by all users, and can manage them

Introduction to host aggregation

You can create a host group and put them together.

CVM

Except that it is impossible to modify the name of the CVM, all other modifications are possible.

CVM type

We can add and delete.

The Internet and so on.

User authentication

We demonstrate deleting a CVM.

We switch to the demo user, ready to delete the CVM, and add a new one

Build a CVM

Click the + sign below to join.

Mirrors, power snapshots, volumes, volume snapshots, and so on can be used here

We can add it in management.

Add Network

Add a security group

Add key pair

Then we can just start the instance.

We just created two, and now it's starting.

Our virtual machine is started with kvm, so booting with kvm will generate two processes on the compute node.

View compute node processes

To listen on the port of vnc, the default port of vnc starts from 5900

In the openstack environment, the bridge cards have the same name.

Metro Bridge Street to the local network card eth0

The virtual machine is saved in / var/lib/nova/instances

[root@linux-node2] # tree / var/lib/nova/instances//var/lib/nova/instances/ ├── 10ea5ada-150a-42fb-bebf-dd99936f08a2 │ ├── console.log │ ├── disk │ disk.info │ └── libvirt.xml ├── 3bb362fb-464b-40ad-b564-628387944c4a │ ├── console.log │ ├── disk │ ├── disk.info │ └── libvirt. Xml ├── _ base │ └── e24c82eb013841010cf48ebfe8281d09ed4b251a ├── cc7f38cd-29e4-492f-b72b-e60bb3f4bed2 │ ├── console.log │ ├── disk │ disk.info │ └── libvirt.xml ├── compute_nodes └── locks ├── nova-e24c82eb013841010cf48ebfe8281d09ed4b251a └── nova-storage-registry-lock5 directories 16 files [root@linux-node2 ~] #

Console.log console log disk virtual disk disk.info virtual disk information libvirt.xml KVM generated a file base image path e24c82 image ID

Tip: although our virtual machine is assigned a 1G hard disk, it does not reach 1G, because it can save space and increase the startup speed. Really, the space is all in the mirror image.

[root@linux-node2] # ll / var/lib/nova/instances/10ea5ada-150a-42fb-bebf-dd99936f08a2/total 1824 disk.info-rw-r--r-- 1 qemu qemu 19760 Nov 23 23:31 console.log-rw-r--r-- 1 qemu qemu 1835008 Nov 23 23:41 disk-rw-r--r-- 1 nova nova 79 Nov 23 23:27 disk.info-rw-r--r-- 1 nova nova 2653 Nov 23 23:27 libvirt.xml [root@linux -node2 ~] # file / var/lib/nova/instances/10ea5ada-150a-42fb-bebf-dd99936f08a2/disk/var/lib/nova/instances/10ea5ada-150a-42fb-bebf-dd99936f08a2/disk: QEMU QCOW Image (v3) Has backing file (path / var/lib/nova/instances/_base/e24c82eb013841010cf48ebfe8281d09e), 1073741824 bytes

We can also use the qemu command to view it in detail

[root@linux-node2 ~] # qemu-img info / var/lib/nova/instances/10ea5ada-150a-42fb-bebf-dd99936f08a2/diskp_w_picpath: / var/lib/nova/instances/10ea5ada-150a-42fb-bebf-dd99936f08a2/diskfile format: qcow2virtual size: 1.0G (1073741824 bytes) disk size: 1.8Mcluster_size: 65536backing file: / var/lib/nova/instances/_base/e24c82eb013841010cf48ebfe8281d09ed4b251aFormat specific information: compat: 1.1lazy refcounts: false refcount bits: 16corrupt: false

Tip: the file disk.info is a path

KVM of Cloud Computing and Virtualization tools

Http://www.abcdocker.com/abcdocker/1627

Console.log, what we show when we log in to the CVM.

Libvirt.xml is dynamically generated and cannot be modified

To be updated

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.