During the installation process, a source problem was encountered and the Web page for the package could not be found: reopen the preloaded source address, open the Epel-openstack-havana.repo file, and display the following:# Place this file in Your/etc/yum.repos.d/directory[openstack-havana]name=openstack Havana Repository for EPEL 6baseurl= http://repos.fedorap
that the state of the virtual machine remains in the building state, you can manually modify the database records to become active.Update instances set vm_state= ' active ' where uuid= ' 9ff3776b-6835-4a4e-8b11-b440591ca9b9 '; 6. Impressions1. Learning OpenStack, Devstack is not enough to start with the environment.2. One of the great benefits of open source products is that you can modify the code as needed3. Set debug=true in config file, you can g
number.) ）After that, Dashboard's page found that it was deleted.Restart Nova-compute, create the virtual machine again, and the status is active.Problem thinking Direction: The operation of virtual machine (create, delete, etc.) must be related to Nova-compute.----------------------------------------------------------------------------------------------------March 25, 2014 update after following the above actions, and found that although the instance has been deleted, such as: If you want to m
First, preface1.RDO is an open source project in Red Hat, the full name of RPM distribution of OpenStack, that can help us deploy OpenStack projects quickly.Official Deployment Documentation: https://www.rdoproject.org/install/packstack/2. This installation is basically in accordance with the official documentation of the steps to operate, in addition to the seco
Tags: technology sharing deploy other chmod his ace dashboard edit imgFirst, the basic introductionThis experiment was to deploy OpenStack (Juno version) on virtual machine ubuntu14.04 (64bit,desktop) on VMware Workstation. The tool used is openshit.Openshit is a project on GitHub, see website:Https://github.com/windworst/openshit.Precautions:1. The environment i
Address of this document (http://blog.sina.com.cn/s/blog_68d0c6c30102v8c4.html)
For beginners, OpenStack manual deployment is cumbersome and takes more time to learn. But we can use deployment scripts to install OpenStack.
Online there is a known as the most stupid OpenStack deployment tool called Devstack. I used to think it was quite a fool. The component is pu
Statement:I read the notes, the translation of the article is only for paraphrase. If anything is wrong, please state.Need more understanding of the source, please read English by yourself.This blog welcome forwarding, but please keep the original author information!Blog Address: Http://blog.csdn.net/halcyonbabySina Weibo: Looking for MiraclesThe content of my study, research and summary, if there is similar, it is honored!Deploy
For beginners, OpenStack manual deployment is cumbersome and takes more time to learn. But we can use deployment scripts to install OpenStack.Online there is a known as the most stupid OpenStack deployment tool called Devstack. I used to think it was quite a fool. The component is pulled straight down from GitHub, not only slow not to say, Even version compatibility may be problematic. It took 4 hours to in
Every time you mention deploying OpenStack is a very complex thing, and of course many people will mention the use of devstack to quickly deploy OpenStack, generally we use devstack to deploy the development environment, It can be implemented on a machine to deploy a
storage and computing nodes. Therefore, an enterprise must first build a private cloud and then add large data. Therefore, in this case, SWIFT, Nova, and rabbitmq are used and the controller node is used to manage and maintain the environment. However, the question is whether an enterprise needs to divide the environment into several parts for different systems and business departments (for example, non-Big Data virtual machines or customer server instances ). If you want to use the private clo
, enter the ip address of the computing node.
SQL _connection: Enter the connection value in nova. conf.
Id set by node number
[kanyun]log: /var/log/kanyun/kanyun.log[DEFAULT]sql_connection: mysql://nova:novamysqlpassword@controller/nova[worker]id: worker1worker_timeout: 60dataserver_host: 172.19.9.1dataserver_port: 5551log: /var/log/kanyun/kanyun-worker.log[client]api_host: 172.19.9.1api_port: 5552log: /var/log/kanyun/kanyun-client.logStart the service
Today, when debugging OpenStack, restart Apache with the following error:[[Email protected] log]# service httpd restart stop httpd:[OK] starting httpd:httpd:Could not reliably determine the server ' s ful Ly qualified domain name, using 127.0.0.1 for servername[OK] on the/etc/hosts toss a while, no fruit. Later on Google and Baidu search found that need to modify a place in the HTTP configuration file1) Enter Apache installation directory: (depending
-1482841779121004386.jpg "/>The network structure of the current host is as follows:650) this.width=650; "Src=" http://7xo6kd.com1.z0.glb.clouddn.com/ Upload-ueditor-image-20161227-1482841779322035224.jpg "/>Two instance are hung on the br-int and can communicate with each other.Create a second local networkTo analyze the connectivity of the local network, we create a "second_local_net".Most properties of second_local_net are the same as first_local_net, except that the IP pool range is 172.16.1
The previous section deployed CIRROS-VM1 to First_local_net, and today we will deploy CIRROS-VM2 to the same network and create second_local_net.connecting a second instance to first_local_netIn the same way launch instance "CIRROS-VM2", the assigned IP is 172.16.1.4.The CIRROS-VM2 is also schedule to the control node, and the output of Ovs-vsctl show is as follows:CIRROS-VM2 for the TAP device is tapddbbb728-93.From CIRROS-VM2 can Ping the IP address
cirros-vm2 in the same way, assigning the IP to 172.16.100.4.650) this.width=650; "Src=" http://7xo6kd.com1.z0.glb.clouddn.com/ Upload-ueditor-image-20161113-1479026489473056264.jpg "/>The CIRROS-VM2 is schedule to the compute node, the corresponding tap device is TAP457CC048-AA, and connected to bridge brq1762d312-d4.650) this.width=650; "Src=" http://7xo6kd.com1.z0.glb.clouddn.com/ Upload-ueditor-image-20161113-1479026489603043136.jpg "/>Because there is no HDCP service on the compute nodes,
.glb.clouddn.com/ Upload-ueditor-image-20170117-1484631963570088105.jpg "/>The IP assigned to the CIRROS-VM3 is 172.16.101.103.650) this.width=650; "Src=" http://7xo6kd.com1.z0.glb.clouddn.com/ Upload-ueditor-image-20170117-1484632053655003094.png "alt=" Image615.png "/>The CIRROS-VM3 is schedule to the compute node and the virtual network card is connected to the Br-int.650) this.width=650; "Src=" http://7xo6kd.com1.z0.glb.clouddn.com/ Upload-ueditor-image-20170117-1484631963692015111.jpg "/>65
This section deploys the Devstack lab environment, including control nodes and compute nodes, as follows:Create a virtual machineCreate Devstack-controller and Devstak-compute virtual machines according to physical resource requirementsInstalling the operating systemInstall Ubuntu 14.04, and configure eth0 IP devstack-controller 192.168.104.10 devstak-compute 192.168.104.11download CodeDownload the Devstack code and switch to the Stable/liberty branch
Apt-get Install Git-ygit clone http
In general, OpenStack requires at least two physical machines, or two nodes, the control nodes and compute nodes mentioned earlier. In general, the control node does not require excessive hardware resources, compute nodes need a relatively high hardware resources, but often the user's two nodes of the hardware information is the same, so we will also install Nova on the control node, to use the Control node hardware resource information.
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
and provide relevant evidence. A staff member will contact you within 5 working days.