General Host Aggregates — nova 2012.2 documentation
General Host Aggregates¶ Host aggregates can be regarded as a mechanism to further partition an availability zone; while availability zones are visible to users, host aggregates are only visible to administrators. Host aggregates started out as a way to use Xen hypervisor resource pools, but has been generalized to provide a mechanism to allow administrators to assign key-value pairs to groups of
Welcome to Swift’s documentation! — Swift 2.34.0.dev83 documentation
Welcome to Swift’s documentation!¶ Swift is a highly available, distributed, eventually consistent object/blob store. Organizations can use Swift to store lots of data efficiently, safely, and cheaply. This documentation is generated by the Sphinx toolkit and lives in the source tree. Additional documentation on Swift and other components of OpenStack can be found on the OpenStack wiki and at http
Getting virtual machine images - OpenStack Compute Administration Manual - Essex (2012.1)
Scott Moser maintains a set of small virtual machine images that are designed for testing. These images use cirros as the login user. They are hosted under the CirrOS project on Launchpad andare available for download. If your deployment uses QEMU or KVM, we recommend using the images in QCOW2 format. The most recent 64-bit QCOW2 image as of this writing is cirros-0.3.0-x86_64-disk.img Canonical m
Installing from Source - OpenStack Quantum Administration Guide - Essex (2012.1)
The Quantum server code currently depends on code in python-quantumclient, so the client code must always be downloaded and installed. First, install python setup tools. For example, on Ubuntu: sudo apt-get install python-setuptools python-dev libxslt1-dev Then install the client and server packages using setup tools. For example, on Ubuntu:tar xzf python-quantumclient-<version>.tar.gz tar xzf qu
Compute schedulers — nova 29.1.0.dev80 documentation
Compute schedulers¶ Compute uses the nova-scheduler service to determine how to dispatch compute requests. For example, the nova-scheduler service determines on which host or node a VM should launch. You can configure the scheduler through a variety of options. In the default configuration, this scheduler considers hosts that meet all the following criteria: Are in the requested Availability Zone
Quantum Manager Limitations - Quantum Admin Guide - Quantum 2012.1 (Essex) Administrator Guide
During Essex, Quantum has added many capabilities toward achieving "nova-network parity". The following limitations exist: Multi-host nova-network HA is not supported (i.e., running nova-network on each compute node for HA purposes). CloudPipe VPNs do not work when using Quantum Manager. Nova is developing an alternative to CloudPipe for Essex that should be compatible with Quantum Manager.
Multi-Node Lab — DevStack documentation
Multi-Node Lab¶ Here is OpenStack in a realistic test configuration with multiple physical servers. Prerequisites Linux & Network¶ Minimal Install¶ You need to have a system with a fresh install of Linux. You can download the Minimal CD for Ubuntu releases since DevStack will download & install all the additional dependencies. The netinstall ISO is available for Fedora and CentOS/RHEL. Install a c
Chapter 3. Installing and Configuring OpenStack Object Storage
Chapter 3. Installing and Configuring OpenStack Object Storage
Admin Documentation — nova 29.1.0.dev82 documentation
Admin Documentation¶ The OpenStack Compute service allows you to control an Infrastructure-as-a-Service (IaaS) cloud computing platform. It gives you control over instances and networks, and allows you to manage access to the cloud through users and projects. Compute does not include virtualization software. Instead, it defines drivers that interact with underlying virtualization mechanisms that r
Keystone, the OpenStack Identity Service — keystone 25.1.0.dev17 documentation
Keystone, the OpenStack Identity Service¶ Keystone is an OpenStack service that provides API client authentication, service discovery, and distributed multi-tenant authorization by implementing OpenStack’s Identity API. This documentation is useful for contributors looking to get involved in our community, developers writing applications on top of OpenStack, and operators administering their own O
DevStack — DevStack documentation
DevStack¶ DevStack is a series of extensible scripts used to quickly bring up a complete OpenStack environment based on the latest versions of everything from git master. It is used interactively as a development environment and as the basis for much of the OpenStack project’s functional testing. The source is available at https://opendev.org/openstack/devstack. Warning DevStack will make substant
Welcome to Swift’s documentation! — Swift 2.34.0.dev31 documentation
Welcome to Swift’s documentation!¶ Swift is a highly available, distributed, eventually consistent object/blob store. Organizations can use Swift to store lots of data efficiently, safely, and cheaply. This documentation is generated by the Sphinx toolkit and lives in the source tree. Additional documentation on Swift and other components of OpenStack can be found on the OpenStack wiki and at http
Deployment Options
The swift services run completely autonomously, which provides for a lot of flexibility when designing the hardware deployment for swift. The 4 main services are: The Proxy Services are more CPU and network I/O intensive. If you are using 10g networking to the proxy, or are terminating SSL traffic at the proxy, greater CPU power will be required. The Object, Container, and Account Services (Storag
SAIO (Swift All In One) — Swift 2.34.0.dev54 documentation
Note This guide assumes an existing Linux server. A physical machine or VM will work. We recommend configuring it with at least 2GB of memory and 40GB of storage space. We recommend using a VM in order to isolate Swift and its dependencies from other projects you may be working on. Instructions for setting up a development VM¶ This section documents setting up a virtual machine for doing Swift dev
System Requirements
Hardware: OpenStack Object Storage specifically is designed to run on commodity hardware. At Rackspace, our storage servers are currently running fairly generic 4U servers with 24 2T SATA drives and 8 cores of processing power. RAID on the storage drives is not required and not recommended. Swift's disk usage pattern is the worst case possible for RAID, and performance degrades very quickly using
Operations
Operations are the actions you perform within an OpenStack Object Storage system such as creating or deleting containers, uploading or downloading objects, and so on. The full list of operations is documented in the Developer Guide. Operations may be performed via the ReST web service API or a language-specific API; currently, we support Python, PHP, Java, Ruby, and C#/.NET. Important All operatio
Containers and Objects
A container is a storage compartment for your data and provides a way for you to organize your data. You can think of a container as a folder in Windows® or a directory in UNIX®. The primary difference between a container and these other file system concepts is that containers cannot be nested. You can, however, create an unlimited number of containers within your account. Data must be stored in a
Chapter 6. OpenStack Interfaces
You can use a dashboard interface with an OpenStack Compute installation with a web-based console provided by the Openstack-Dashboard and Django-Nova projects. Together they provide a reference implementation of a Django site that provides web-based interactions with the OpenStack Compute cloud controller. For more information about the Django-Nova project, please visit: http://launchpad.net/djang
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Object Server Configuration - OpenStack Object Storage Administration Manual - trunk
Reference for Flags in nova.conf