openstack deployment tools

Operating Interface (Horizon) OpenStack Identity Certification (Keystone) OpenStack Network Service (neutron) OpenStack Block Storage (Cinder), providing block data access OpenStack Telemetry (ceilometer), providing metering and monitoring functions OpenStack Orchestration

= eth1Config_cinder_volumes_create = N#########Config_lbaas_install = yConfig_ceilometer_install = yConfig_heat_cloudwatch_install = yConfig_heat_cfn_install = yConfig_heat_install = y Configure the NIC DEVICE=eth0HWADDR=44:33:E7:D1:D4:C4TYPE=EthernetUUID=180283345-0a6f-478c-6f51-d87a128c5ab8ONBOOT=yesBOOTPROTO=staticIPADDR=192.168.40.248NETMASK=255.255.255.0GATEWAY=192.168.40.1DNS1=8.8.8.8 Configure/etc/hosts #127.0.0.1 localhost localhost.localdomain localhost4localhost4.localdomain4127.0.

-py2.6.egg-info ', '/usr ' /share/openstack-dashboard/openstack_dashboard ']The above error by canceling the endpoint interface in the $\ (tend_id) S $, no more such an error, but there is another errorKeyerror at/admin/' Tenant_usages ' Request Method: GET Request URL: http://10.50.20.75/dashboard/admin/ Django Version: 1.4.8

special:Controller1:/etc/init.d/mysql bootstrapController2:/etc/init.d/MySQL StartController3 :/etc/init.d/mysql StartLog on to any node for verification:# mysql-p123456mariadb [(none)]'wsrep_cluster_size';MariaDB [(none)] ' ws% ';Comments:The Wsrep_cluster_status is primary, which indicates that the node is the primary node and reads normally.Wsrep_ready is on to indicate that the cluster is functioning properly.The wsrep_cluster_size is 3, which indicates that the cluster has three nodes.To c

, so you can repeat each time. Correct use of the automatic configuration management tool not only simplifies the automatic deployment release of deployment and configuration changes, but also ensures that each component of the cloud system is in a specific State. These tools also make it possible to test and roll back changes, as they are fully repeatable. con

Tags: centos openstack error local IPProblem description When using rdo for multi-node deployment and testing, the models of several dilapidated machines are different (some hp PCs and some Dell PCs ), the following error occurs: Applying 192.168.40.107_neutron.pp192.168.40.107_neutron.pp: [ DONE ] 192.168.40.248_neutron.pp: [ DONE ] 192.168

OpenStack deployment and O M practicesIntroduction to OpenStack OpenStack is an open-source IaaS implementation. It consists of several associated sub-projects, including computing, storage, and networks. Since its launch as an Apache protocol, more than 2010 companies have joined the

installation Dashboard[email protected] ~]# Yum install-y openstack-dashboardConfiguration Dashboard[Email protected] ~]# vim/etc/openstack-dashboard/local_settingsallowed_hosts = [' * ']108 CACHES = {109 ' default ': {' Backend ': ' Django.core.cache.backends.memcached.MemcachedCache ',111 ' Location ': ' 192.168.1.11:11211 ',112}113}138 Openstack_host = "192.168.1.11"Openstack_keystone_default_role = "U

/89/ED/wKiom1ghlBzznoSiAACf83JFiQU397.jpg-wh_500x0-wm_3 -wmp_4-s_2977389735.jpg "title=" qq20161108165829.jpg "alt=" Wkiom1ghlbzznosiaacf83jfiqu397.jpg-wh_50 "/>Reference http://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/nova.html,The following subsections will organize the OpenStack Network Service deployment, and moreThis article is from the "Zhong blog" blog, make sure to keep this source http://c

Openstack deployment Summary: "Error: Local ip for ovs agent must be set when tunneling is enabled" during deployment, ovsagentProblem description When using RDO for multi-node deployment and testing, the models of several dilapidated machines are different (some HP PCs and some DELL PCs ), the following error occurs:

openstack-nova-consoleauth on# chkconfig Openstack-nova-scheduler on# chkconfig openstack-nova-conductor on# chkconfig openstack-nova-novncproxy on4.1.10 See if the Nova service is installed properly# Nova Image-list+--------------------------------------+---------------------+--------+--------+|ID |Name |Status |Serv

Openstack deployment Summary: "Error: Localipforovsagentmustbesetwhentunnelingisenabled" during deploymentProblem description When using RDO for multi-node deployment and testing, the models of several dilapidated machines are different (some HP PCs and some DELL PCs ), the following error occurs: Applying 192.168.40.107_neutron.pp192.168.40.107_neutron.pp:

=192.168.11.8config_keystone_ldap_url=ldap://192.168.11.8Config_nova_network_fixedrange=192.168.32.0/22config_mongodb_host=192.168.11.8config_redis_master_host=192.168.11.8Don't change anything else.Start deployment:# Yum Install screen# screen Packstack--answer-file=hcloud.txtThis only needs to be performed at the control nodeWelcome to the Packstack setup utilityThe installation log file is available At:/var/tmp/packstack/20160508-231645-zxtev9/

--region RegionOne volumev2 admin http://192.168.56.11:8776/v2/%\(tenant_id\)s+--------------+--------------------------------------------+| Field | Value |+--------------+--------------------------------------------+| enabled | True || id | c7c6845176214a64ab9abefb7cc7acf8 || interface | admin || region | RegionOne

-file=hcloud.txtWelcome to thepackstack Setup utilityThe Installationlog file is available At:/var/tmp/packstack/20160509-032847-sm4dwt/openstack-setup.logInstalling:Clean up [done]Discovering Ipprotocol version [done]Here you need to manually enter the four-node password[Email protected] ' Spassword:[Email protected] ' Spassword:[Email protected] ' Spassword:[Email protected] ' Spassword:Setting up Sshkeys [done]Then wait for the installation to comp

Maas and JuJu are Ubuntu products, recently want to play OpenStack, see if you can deploy an experimental environment, although finally found that Maas and juju pattern is very useful but the official documents to the thing is too little, here I do not list the specific installation steps, I can only say that the installation steps are simply too simple and do not require very complicated documentation at all. The combination of Maas and juju with Con

Shortly after I first came into contact with openstack, I encountered some problems when implementing 3-node deployment by referring to the official documentation, mainly focusing on the compute node. Fortunately, I had more than a decade of O M experience to help me solve the problem one by one. The solution is marked in red. System Environment: centos 6.5 64-bit IP addresses of each node: configured acc

Still in the basic learning process, writing this article is also strong courage to write, because a lot of basic knowledge is not quite clear (bird Brother's that the private food has not yet learned it), just in time to catch up with colleagues need to take an environment on the development, since there is a need to try it, below the deployment process encountered problems recorded, For the future may also encounter the same problem know how to solv

Deployment of FUEL OpenStack on VirtualBox Deployment process of FUEL OpenStack on VirtualBox: The 6.1 version of Fuel. iso was installed several times according to the domestic and foreign tutorials, but the network verification never passed. I am not very familiar with the network. Later, I saw on the Internet that v

Glance Mirroring Service:Glance consists of three main components: Glance-api, glance-registry, and image storeGLANCE-API: Accepts the creation, deletion, and read requests of the system image.Glance-registry: Mirrored registration Service for cloud systemsGlance installation:[[emailprotected] ~]# yum -y install openstack-glance python-glance python-glanceclient[[emailprotected] ~]# vim /etc/glance/glance-api.conf [database]connection=mysql://glance:[