OpenStack 入门概述.ppt

System Components The Ring: Mapping of names to entities (accounts, containers, objects) on disk. Stores data based on zones, devices, partitions, and replicas Weights can be used to balance the distribution of partitions Used by the Proxy Server for many background processes Proxy Server: Request routing, exposes the public API Object Server: Blob storage server, uses xattrs, uses binary format Recommended to run on XFS Object location based on path from name hash timestamp System Components (Cont.) Container Server: Handles listing of objects, stores as SQLite DB Account Server: Handles listing of containers, stores as SQLite DB Replication: Keep the system consistent, handle failures Updaters: Process failed or queued updates Auditors: Verify integrity of objects, containers, and accounts Software Dependencies Object Storage (Swift) development currently targets Ubuntu Server 10.04, but should work on most Linux platforms with the following software: Python 2.6 rsync 3.0 And the following python libraries: Eventlet 0.9.8 WebOb 0.9.8 Setuptools Simplejson Xattr Nose Sphinx Example Network Deployment Evolution of Object Storage Architecture Version 1: Central DB (Rackspace 2008) Version 2: Fully Distributed (OpenStack Object Storage 2010) 5 Zones2 Proxies per 25Storage Nodes10 GigE to Proxies1 GigE to Storage Nodes24 x 2TB Drivesper Storage Node Public Internet Example OpenStack Object Storage Hardware Load Balancers (SW) Example only – many configurations possible Planning an OpenStack DeploymentRequirements Technology Choices Hardware Selection OpenStack is designed to run on industry standard hardware with flexible configurations Compute X86 Server Storage flexible (Local, SAN, NAS) Object Storage X86 Server (other architectures possible) Do not deploy with RAID (can use controller for case) Physical Hardware Remote Management Host Networking Host Seed OS Install Host OS Install Post OS Configuration Rack Cable Dell DRAC HP iLO IPMI DHCP BOOTP