RedHat OpenStack 官方安装文档

【实例简介】
RedHat OpenStack 官方安装文档
Comments and feedback In the spirit of open source, we invite anyone to provide feedback and comments on any reference architectures. Although we review our papers internally, sometimes issues or typographical errors are encountered. Feedback allows us to not only improve the quality of the papers we produce, but allows the reader to provide their thoughts on potential improvements and topic expansion to the papers Feedbackonthepaperscanbeprovidedbyemailingrefarch-feedback@redhat.com.Pleasereferto the title within the email Staying In Touch Join us on some of the popular social media sites where we keep our audience informed on new reference architectures as well as offer related information on things we find interesting Like us on facebook: https://www.facebookcom/rhrefarch Folllow us on twitter: https://twitter.com/redhatrefarCh Plus us on Google+: https:/plus.googlecom/u/0/b/114152126783830728030/ refarch-feedback@redhat.com www.redhat.com Table of contents 1 EXecutive Summary 2 Component Overview 2.1 Red Hat Open stack 重1 2.2 Open Stack Services 12223 2.2.1 Identity 2.2.2 Image 2.2.3 Compute.… 4 2.2.4 Block Storage 4 2.2.5 Dashboard 2.2.6 Services not covered in this reference architecture ..m,.m..... 6 2. 3 Red Hat Enterprise Linux 6 2.4 Supporting Technologies 7 24.1 MySQL… 24.2QP|D 1日1日1面1量B面面面B面自m面B 8 2.4.3KVM. 8 2.4 4 Packsack 2. 4.5 Supporting Technologies Not Included in this Reference Architecture......8 3 Reference Architecture Configuration Details 3.1 Environment 3.1.1 Network Topology 3.1.2 P Addresses. .w.WIGOWNIWWNW 10 3.2 Software and security Reference.,…,…………10 3.2.1 Software Versions 11 3.2.2 Security: iptables 3.2.3 Security SELinux 12 3.2. 4 Required channels 11 量量1面1B 12 3.3 Server Hardware Configuration 13 3.4 Open Stack Service Placement aaaa:aaBaaa 14 4 Deploy Cloud Controller, Compute Node, and Client via Packstack 15 4.1 Architectural overview 15 41.1 Cloud controller 16 4.1.2 Compute Node 116 4.1.3 Client 16 www.redhat.com refarch-feedback@redhat.com 4.2 Prepare the Hosts. 16 4.2.1 nstall the operating System...….…… :.:aaaaa:a::.aa:.aa::aa::aa: 日面 4.2.2 Register with Red Hat Network .17 4.2.3 Configure Name resolution.….…....17 4.2.4 Create an SSH Key on the Cloud Controller 17 4. 3 Deploy Cloud Controller and Compute Node via Packstack 18 4.3. 1 Prepare the cloud controller for Packstack 18 4.3.2 Run packsack on the cloud controller 19 4.3.3 Verify the configuration 22 4.3.4 Verify Packstack installation Completes Successfully.……………23 4. 4 Verity the Packstack Deployment 23 4.4.1 nitial deployment Overview.…………………………23 4.4.2 Examine Deployment as Keystone Admin .24 4. 4. 3 Prepare to Boot an Instance 26 4.4 4 Boot an instance 27 4.45 Connect to the instance via ssh ■ 30 4.4.6 Connect to the instance via noVNc console wwwwwww 31 4.4.7 View Instance from horizon dashboard, wwwwwwwwwwwwwwwww 32 5 Expand the compute Infrastructure 36 5. 1 Re-run Packstack to Add compute nodes 36 5.1.1 Modify the Packstack Answer File 36 5.1.2 Re-run packstack with the new answer file …,37 5. 1. 3 Verify the New Compute nodes 38 5.2 Create the tenant. Users and roles 38 5.2.1 Create a Tenant 38 5.2.2Adda∪ser. 39 5.2.3 Add a role :aa:aa“a:aa:aaa:a:::a日:::::::日:日日:a日道 39 5.2, 4 Associate the user role and tenant 40 5. 3 Configure Nova Networking for Multi-host Mode 40 5.3.1 Disable default virtua| Networks∴………40 5.3.2 Install Networking Services on the Compute Nodes................. 41 5.3.3 Modify Nova Configuration 42 5.3.4 Customize each Compute node 43 5. 4 Boot an Instance in the tenant 45 5.4.1 Add a network to the tenant 45 5.4.2 Boot a New instance as the tenant user 46 5.4.3 Assign a Floating iP Address to the Instance 47 refarch-feedback@redhat.com www.redhatcom 5. 4. 4 Connect to the instance via ssh 5.5 Test Nova Service Availability………………… 8 5.5.1 Disable Nova Services on the Original Compute Node 49 5.5.2 Boot a Test Instance 49 5.5.3 Re-enable Nova services on the Original Compute Node 50 5.6 Deploy cinder NFS Server B道画 51 5.6.1 Build a nes server.w.wwwww 51 5.6.2 Add the nes server to cinder 52 5. 6. 3 Create a persistent volume 3 5. 6. 4 Attach the volume to an instance 55 5.6.5 Attach the volume to the second instance 57 5.6.6 Complete Open Stack Deployment 重m 58 6 Deploy a multi-tier Web Application.……,……………………59 6.1 Overview 59 6.2 Deploy the Database Server 59 6.2.1 Create the User Data Script .60 6.2.2 Create the Registration Script 60 6.2. 3 Create the database volume 60 6.2.4 Boot the instance 60 6.2.5 Verify the Database Server 61 6. 3 Deploy the Web server 62 63.1 Create the User Data Script.........,…………62 6.3.2 Launch the web server .:““·“ 63 6. 3. 3 Associate a public ip address with the web server instance ww. 64 6.34 Verify the Web Server Installation………… 65 6. 4 Test the Web server from a client 66 6.5 Complete Multi-tier Application ∴67 7 Conclusion .68 Appendix a: Revision History………,………,……,…………69 Appendix B: Contributors 70 www.redhat.com refarch-feedback@redhat.com 1 Executive Summary Open Stack is a free and open source Infrastructure-as-a-Service(laas) cloud computing project released under the Apache License. It enables enterprises and service providers to offer on-demand computing resources by provisioning and managing large networks of virtual machines. Open stack boasts a massively scalable architecture that can control compute storage, and networking resources through a unified web interface. The Open Stack development community operates on a six-month release cycle with frequent milestones Their code base is composed of many loosely coupled projects supporting storage, compute image management, identity, and networking services. Open Stack's rapid development cycle and architectural complexity create unique challenges for enterprise customers hoping to add Open Stack to their traditional IT portfolios Red Hat Open Stack(RHOS)2.1 addresses these challenges. Red Hat Open Stack 2.1 delivers a stable code base for production Open stack deployments backed by red hat's open source software expertise. Red Hat open Stack adopters enjoy immediate access to bug fixes and critical security patches, tight integration with Red Hat's enterprise security features including selinux, and a steady release cadence between Open stack versions. This allows Red Hat customers to adopt OpenStack with confidence, at their own pace, and on their own terms This reference architecture introduces Red Hat Open Stack 2. 1 through three detailed use cases Installing an evaluation Red Hat Open Stack deployment consisting of a cloud controller and a single compute node Expanding the evaluation deployment to four compute nodes, multi-host networking and nfs backed persistent storage Deploying a multi-tier web application to the red Hat open stack infrastructure complete with post-boot customization This paper contains step by step instructions for expanding an evaluation Red Hat Open Stack 2.1 deployment to a basic cloud architecture suitable for a small production environment Every step was tested in red hat's engineering lab with production code refarch-feedback@redhat.com www.redhat.com 2 Component Overview This section describes the software components used to develop this reference architecture 2.1 Red Hat Open stack Red Hat open Stack provides a foundation for organizations to build private or public Infrastructure-as-a-Service (laaS) for cloud-enabled workloads. It allows organizations to leverage OpenStack, the largest and fastest growing open source cloud infrastructure project, while maintaining the security, stability, and enterprise readiness of a platform built on Red Hat Enterprise Linux Red Hat Open Stack gives organizations a truly open framework for hosting cloud workloads delivered by red Hat subscription for maximum flexibility and cost effectiveness. In conjunction with other Red Hat technologies, Red Hat Openstack allows organizations to move from traditional workloads to cloud-enabled workloads on their own terms and timelines s their applications require. Red hat frees organizations from proprietary lock-in, and allows them to move to open technologies while maintaining their existing infrastructure investments Unlike other Open Stack distributions, Red Hat Open Stack provides a certified ecosystem of hardware, software, and services, an enterprise lifecycle that extends the community Open Stack release cycle, and award-winning Red Hat support on both the OpenStack nodules and their underlying Linux dependencies. Red Hat delivers long-term commitment and value from a proven enterprise software partner so organizations can take advantage of the fast pace of openStack development without risking the stability and supportability of their production environments 2.2 Open Stack Services Red hat open stack 2.1 is based on the upstream open stack release code named" Folsom This is the sixth open stack release and the first deemed sufficiently hardened for production use. Folsom was the first release to include extensible block and volume storage capabilities It also includes a dedicated advanced network automation platform with Layer 2 networking control, IP address management, and extensions for Layer 3 forwarding Open Stack services are modular. Some provide optional capabilities. Figure 2.2.1: Used Services depicts the Open Stack services used in this reference architecture. The Networking and object Storage services are not used in this reference architecture. They are grayed-out in the diagram. These services are optional in the Folsom release and not necessary for the small production deployment described in this reference architecture. The diagram illustrates where they would fit into the overall infrastructure had they been included The following sections define the core Open Stack components utilized in this reference architecture. They include Identity(code-named Keystone) Image(code-named Glance) Compute(code-named Nova www.redhat.com refarch-feedback@redhat.com Block Storage(code-named Cinder) Dashboard(code-named Horizon) User Interface Dashboard Horizon persistent storage Networking Volume Service Compute Image Object Storage (Quantum) (Cinder Nova (Glance) (Swift) network connectivity stores images stores disk files Identity (Keystone) Authentication Figure 2.2.1: Used Services 2.2.1 Identity The open Stack Identity service is a central directory that maps users to the Open Stack services they can access. It acts as a common authentication system for all OpenStack users and services. The Open Stack Identity service can integrate with existing directory services such as LDAP. It also supports multiple forms of authentication including standard username and password credentials, token-based systems and Aws-style logins that use public/private key pairs The Open stack Identity service catalog provides a way to query and list of all of the services deployed in an Open Stack cloud. Administrators can programmatically determine which resources users and third-party tools can access The Identity service authenticates users based on their access credentials. After the user is authenticated the user is issued a token this token can be used to demonstrate that the user's identity has been authenticated when making subsequent requests. the token includes a list of roles the user may assume when performing a set of operations. This method of access control is commonly referred to as role based Access Control (rbac). Administrators associate grant-or-deny access privileges with each role through either the horizon dashboard interface or the Keystone command line interface The Identity service also manages authentication for Open Stack services through ENDPOINTS An Endpoint is a network-accessible address where a service may be accessed the Identity refarch-feedback@redhat.com 3 www.redhatcom service provides each Open Stack service -- such as Image, Compute, or block Storage with one or more endpoints through which is can be accessed to perform useful operations The Identity service uses tenants to group or isolate resources. User accounts in one tenant may not be able to access resources in another tenant even if they reside within the same Open Stack cloud deployment or physical host. Keystone enforces tenants by issuing tokens to authenticated users. the endpoint service validates the token before allowing user access 2.2.2 Image The Open Stack Image Service discovers, registers, and delivers disk and server images. The images can be copied via snapshot and immediately stored as the basis for new instance deployments. Stored images allow Open Stack users and administrators to provision multiple servers quickly and consistently. The Image service also stores and catalogs snap shots. The Image Service API provides a standard rEst interface for querying information about the Images. The Image Service can store images in a variety of back-ends including Open Stack Object Storage. By default Glance stores images in the Image server's local filesystem in the supports several backend storage technologies including Swift(the Open Stack ober ce /var/lib/glance/images directory the image store location is a configurable option glance Storage service), Amazon S3, and RBD. the Glance aPI can also be configured to cache images locally on the hosts that use them in order to reduce image staging time 2.2.3 Compute Open stack Compute is used to provision and manage large networks of virtual machines. It controls the computing fabric which is the backbone of OpenStack,'s laas functionality Compute resources are accessible via APls for developers and via web interfaces and command line tools for administrators and users. Openstack compute scales horizontally on standard hardware enabling the favorable economics of cloud computing Key features of Open Stack Compute include Distributed and asynchronous architecture, allowing scale out fault tolerance for virtual machine instance management hardware profiles for guests can be assigned to new instances at launch virtual Management of commoditized virtual server resources where predefined virtual Virtual Local Area Networking(LAN) management including VLANS, IP address assignment, and floating iP addresses Security groups to flexibly assign instances to resource pools and control access to them VNC access to instances via web browsers 2.2.4 Block Storage The open stack Compute service provisions ephemeral storage for deployed instances based www.redhat.com refarch-feedback@redhat.com 【实例截图】
【核心代码】