Note:
Reference official:http://docs.openstack.org/mitaka/install-guide-rdo/environment-packages.html
OpenStack is an open source cloud computing platform that supports all types of cloud environments. The purpose of the project is to achieve simple, large scale scalability, and a rich feature set. Cloud computing expert projects from around the world contribute.
OpenStack is an open source cloud computing platform that supports all types of cloud environments. The purpose of the project is to achieve simple, large scale scalability, and a rich feature set. Cloud computing expert projects from around the world contribute.
OpenStack provides a infrastructure-as-a-service (IaaS) solution through a variety of complementary service solutions. Each service provides a application programming Interface (API) that facilitates this consolidation.
650) this.width=650; "Src=" Http://s4.51cto.com/wyfs02/M02/82/9E/wKioL1ddHIOQ2r0kAADzSXbdM8M446.png-wh_500x0-wm_3 -wmp_4-s_211024571.png "title=" 1.png "alt=" Wkiol1ddhioq2r0kaadzsxbdm8m446.png-wh_50 "/>
After you are familiar with the basic installation, configuration, operation, and troubleshooting of these OpenStack services, you should consider the following few steps when using production architecture deployment.
Identify and implement the necessary core and optional services to meet performance and redundancy requirements.
Security is enhanced using methods such as firewalls, encryption, and service policies.
Automate the deployment and management of your production environment with automated tools such as Ansible,chef, Puppet, or salt.
Sample Schemas
In order to start a basic: Term: ' Virtual machines <virtual Machine (VM) > ' or instance, this example architecture requires at least two nodes (hosts). Optional services such as block storage and object storage require additional nodes.
This example schema differs from the minimal production architecture, as follows:
650) this.width=650; "Src=" Http://s4.51cto.com/wyfs02/M01/82/9F/wKioL1ddHrCSpc2TAAFi1J2SEgk031.png-wh_500x0-wm_3 -wmp_4-s_501058575.png "title=" Hwreqs.png "alt=" Wkiol1ddhrcspc2taafi1j2segk031.png-wh_50 "/>
Hardware requirements
Controller
Controller node running Unit service, Image Service, management part of the calculation, management network part, various network agents and dashboards. It also includes support for such services as a SQL database, Message Queuing , National TB control program .
Optionally, part of the Controller node block store runs, object storage, orchestration, and telemetry technical services.
A controller node requires at least two network interfaces.
calculation
running on compute nodes Virtual Machine Monitoring Program part of the compute run instance. By default, the compute uses the KVM hypervisor. The compute node also runs a virtual network connection to the Network Service proxy instance and provides the instance security group through the Firewall service .
You can deploy multiple compute nodes. Each node requires a minimum value of two network interfaces.
block Storage
An optional block storage node contains disk block storage and shared file system services that provide an instance.
For simplicity, the service flows between the compute nodes, which use the management network. A separate storage network should be implemented in the production environment to improve performance and security.
You can deploy multiple block storage nodes. Each node requires at least one network interface.
Object Storage
The optional Object storage node contains the disk object storage service that uses storage accounts, containers, and objects.
For simplicity, the service flows between the compute nodes, which use the management network. A separate storage network should be implemented in the production environment to improve performance and security.
This service requires two nodes. Each node requires a minimum of one network interface. You can deploy more than two object storage nodes.
network
Select one of the following virtual network options.
Network option 1: Vendor network
choosing to deploy an OpenStack network service provider network in the simplest way is primarily a 2-tier (bridging/switching) service and network VLAN partitioning. Essentially, this bridges the virtual network physical network and relies on the physical network infrastructure of the third tier (routing) service. Additionally, a DHCP Service provides the IP address information for the instance.
650) this.width=650; "Src=" Http://s4.51cto.com/wyfs02/M02/82/9F/wKioL1ddHteSIhp_AAKdKqcUCaE035.png-wh_500x0-wm_3 -wmp_4-s_2553194413.png "title=" Rk1-services.png "alt=" Wkiol1ddhtesihp_aakdkqcucae035.png-wh_50 "/>
Network Option 2: Self-service network
the Self-service network option increases the Vendor Network option third tier (routing) enabled services Self-Service The network uses the overlay subdivision method as VXLAN . Essentially, a virtual network of physical network lines uses NAT. In addition, this option provides the basis for advanced services such as Lbaas and Fwaas.
650) this.width=650; "Src=" Http://s3.51cto.com/wyfs02/M00/82/A0/wKiom1ddHeXCfsd-AAKn9Z31zEk871.png-wh_500x0-wm_3 -wmp_4-s_2195619847.png "title=" Rk2-services.png "alt=" Wkiom1ddhexcfsd-aakn9z31zek871.png-wh_50 "/>
This article is from the "Destiny." blog, be sure to keep this provenance http://hypocritical.blog.51cto.com/3388028/1788316
OpenStack Learning Note (i): Introduction to OpenStack Environment