stopwatch 5 minutes

/compute/api.py by Unshelve.nova-scheduler Execution SchedulingNova-scheduler the message is received, the appropriate compute node is selected for instance. View Log/opt/stack/logs/n-sch.logAfter screening, the final Devstack-controller is selected launch instance.Nova-scheduler sending MessagesNova-scheduler sends a message telling that the selected compute node can launch instance the source code on line 95th of the/opt/stack/nova/nova/scheduler/filter_scheduler.py by Select_destinationsNova-

This section analyzes the instance start operation in detail through a log file.here is the flowchart for start instance Send a request to NOVA-API Nova-api sending messages Nova-compute Performing actions Let's discuss each step in detail below.send a request to Nova-apiThe customer (which can be an OpenStack end-user or other program) sends a request to the API (NOVA-API): "Start this Instance for me"View Log/opt/stack/logs/n-api.logNova-api sending MessagesNova-api sent

Volume via DD.Log analysis no longer repeat, leave a everyone to practice.If a volume exists snapshot, then this volume cannot be deleted.This is because snapshot relies on volume,snapshot not being able to exist independently.In an environment where LVM is a volume provider, snapshot is completely copy from the source volume, so this dependency is not strong.But in other volume provider (such as commercial storage devices or Distributed file systems), snapshot is usually a reference (pointer)

-space:normal;float:none; "/>resume operations is reserved for everyone to practice. Tip: The Resume operation here is actually a unpause operation, which can be used to locate the log through the keyword "unpause". The above is a detailed analysis of Pause/resume, the next section we continue to analyze suspend/resume operations. 650) this.width=650; "title=" "src=" http://7xo6kd.com1.z0.glb.clouddn.com/ Upload-ueditor-image-20160516-1463348250019020727.jpg "style=" Border:0px;vertical-align:mi

-ueditor-image-20160517-1463494945476033387.png "src=" http://7xo6kd.com1.z0.glb.clouddn.com/ Upload-ueditor-image-20160517-1463495356406065102.jpg "style=" border:0px;white-space:normal;float:none; "/>Unrescue's log analysis is reserved for everyone to practice.650) this.width=650; "title=" "src=" http://7xo6kd.com1.z0.glb.clouddn.com/ Upload-ueditor-image-20160517-1463495356512088695.jpg "style=" Border:0px;vertical-align:middle;color:rgb ( 63,63,63); font-family: ' Microsoft Yahei '; Font-siz

In the previous section we discussed the first part of Cinder creating Volume, Cinder-api operation, this section continues the second part, Cinder-scheduler scheduling work.cinder-scheduler Execution SchedulingCinder-scheduler executes the scheduling algorithm and selects the optimal storage node log for/opt/stack/logs/c-sch.log through Filter and Weigher.Cinder-scheduler performs the dispatch work through Flow Volume_create_scheduler.The Flow executes Extractschedulerspectask and schedulecreat

:15px;line-height:21.75px;text-align:justify;white-space:normal;background-color: #f6f6f6; "title=" "src = "Http://7xo6kd.com1.z0.glb.clouddn.com/upload-ueditor-image-20160304-1457044908340089757.jpg"/>650) this.width=650; "Style=" Background:url ("Http://ipaiban.com/js/ueditor/lang/zh-cn/images/localimage.png") No-repeat center;border:1px solid #ddd; "src=" Http://ipaiban.com/js/ueditor/themes/default/images/spacer.gif "/> after Ubuntu starts, use the following command to confirm that the CPU s

/ubuntu/trusty-backports main restricted universe Multiverse then execute the following command to update the installation package index# APT UpdateThe Redhat and CentOS installations are relatively straightforward, and the virtualization and graphics components are selected during installation.tip: Ubuntu default is not allow root via SSH Direct login, you can modify the/etc/ssh/sshd_config, set Permitrootlogin Yes Then restart the SSH service to# service SSH restartssh stop/waitingssh start/r

system in the form of Driver simply by implementing these interfaces. The following is the architecture of the Cinder Driver:We can see in the/opt/stack/cinder/cinder/volume/drivers/directory the Driver of the OpenStack source code that has come with a lot of volume provider:The storage node configures the driver used with the Volume_driver option in the configuration file/etc/cinder/cinder.conf:Here LVM is the volume provider we use.periodically report the status of compute nodes to OpenStackI

complete, we can view the contents of the container directoryThere are three files, according to the previous log we can know: BACKUP-00001, compressed backup file. Backup_metadata,metadata file. Backup_sha256file, encrypt files. You can view the current backup by Cinder Backup-list.In addition we can check the usage of cinder backup-create.Here is the –incremental option, which means you can perform an incremental backup.If you have done normal (full-volume) backups befor

in its own configuration file/etc/cinder/cinder.conf, which is named for the volume Provider of the storage node.This allows the Capabilitiesfilter to filter out the specified Volume Provider through the "Volume_backend_name" of the Volume Type.Different storage nodes can be configured with the same volume_backend_name in their respective cinder.conf, which is allowed. Because although the storage nodes are different, they may be using a Volume Provider.If multiple storage nodes are selected in

Storage Pool of LVM type Not only can a file be assigned to the client as a virtual disk, but the LV in the VG on the host can also be allocated to the virtual machine for use as a virtual disk.However, LV because there is no MBR boot record of the disk, can not be used as the boot disk of the virtual machine, only as a data disk.In this configuration, the VG on the host is a Storage POOL,VG in the LV is Volume. The advantages of LV are better performance, the lack of management and mobility is

-scheduler and Cinder-volume will then create a blank volume, which, like the create volume, does not repeat.Next, analyze the process of data recovery. First, you can see the relevant information in the CINDER-API log.Note here that the volume_id and backup_id in the log are consistent with the output from the previous Backup-restore command.Let's look at how Cinder-backup recovers data.Cinder-backup performing a restore operationThe log is/opt/stack/logs/c-vol.log. Start the restore operat

here. Volume_backend_name = NFSRestart Cinder-volume,cinder Service-list confirm that the NFS Cinder-volume service is working correctly.Create the NFS volume type.Open the GUI page, Volume Types, Volumes, System, admin, click "Create Volume Type".Name NFS, click "Create Volume Type".Select NFS Volume TYEP, click the drop-down menu "View Extra Specs"Click "Create", Key input volume_backend_name; Value input NFS.NFS Volume provider is ready, the next section we will create volume for NFS backend

features many functions.VMDK is a virtual disk format for VMware, which means that VMware virtual machines can run directly on KVM.The next section describes the Storage Pool for LVM types.650) this.width=650; "title=" "src=" http://7xo6kd.com1.z0.glb.clouddn.com/ Upload-ueditor-image-20160313-1457875040598057697.jpg "style=" Border:0px;vertical-align:middle;color:rgb ( 63,63,63); font-family: ' Microsoft Yahei '; Font-size:15px;line-height:21.75px;text-align:justify;white-space: Normal;backgro

memory, so KVM is responsible for mapping the client's physical memory to the actual machine memory (PA-to-MA). Concrete implementation will not do too much introduction, we are interested to check the information.There is also a point to remind you that memory is also overcommit, that is, all the memory of the virtual machine can exceed the host's physical memory. However, it is also necessary to be fully tested, otherwise performance will be affected.In the next section we discuss how KVM imp

-20161110-1478760595748056384.jpg "/>Visible, vxlan-100 VNI is 100, the corresponding VTEP network interface is eth1.At this point the VXLAN100 structure:650) this.width=650; "Src=" http://7xo6kd.com1.z0.glb.clouddn.com/ Upload-ueditor-image-20161110-1478760595861020045.jpg "/>In the next section we will deploy instance to vxlan100_net and analyze the connectivity of the network.650) this.width=650; "Src=" http://7xo6kd.com1.z0.glb.clouddn.com/ Upload-ueditor-image-20161110-1478760596091013180.j

We discussed the theoretical knowledge of VXLAN and completed the relevant configuration in ML2.Today you will create vxlan100_net through the Web UI and observe the changes in the node network structure.Open Menu Admin--Networks, click the "Create Network" buttonThe Create page is displayed.Provider Network Type Select "VXLAN" Segmentation ID is VNI, set to 100Click "Create Network" to create a successful vxlan100.Click on the vxlan100 link, go to the Network Configuration page, there is no sub

Bridge to open VSwitch, you first need to install the Open VSwitch Agent. To modify the Devstack local.conf:Rerun./stack,devstack will automatically download and install the Open vSwitch.You can then modify the ML2 configuration file/etc/neutron/plugins/ml2/ml2_conf.ini, which is set using Openvswitch mechanism driver.Both the control node and the compute node need to install and configure the Open VSwitch as described above.After the Neutron service restarts, you can see Neutron-openvswitch-ag

In the previous section, we have configured and tested LBaaS, and today we focus on how Neutron uses Haproxy to achieve a balanced balance.Running IP netns on the control node, we found that Neutron created a new namespace qlbaas-xxx.The namespace corresponds to the pool "Web servers" we created. Its naming format is qlbaas-You can view its settings through IP a.The VIP 172.16.100.11 is already configured on the namespace interface. The corresponding configuration of the interface can also be fo