pot/using-swift-for-secondary-storage.pot - cloudstack-docs - Git at Google

 #Licensed to the Apache Software Foundation (ASF) under one
 #or more contributor license agreements.  See the NOTICE file
 #distributed with this work for additional information
 #regarding copyright ownership.  The ASF licenses this file
 #to you under the Apache License, Version 2.0 (the
 #"License"); you may not use this file except in compliance
 #with the License.  You may obtain a copy of the License at
 #http://www.apache.org/licenses/LICENSE-2.0
 #Unless required by applicable law or agreed to in writing,
 #software distributed under the License is distributed on an
 #"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
 #KIND, either express or implied.  See the License for the
 #specific language governing permissions and limitations
 #under the License.
 msgid ""
 msgstr ""
 "Project-Id-Version: 0\n"
 "POT-Creation-Date: 2013-02-02T20:12:00\n"
 "PO-Revision-Date: 2013-02-02T20:12:00\n"
 "Last-Translator: Automatically generated\n"
 "Language-Team: None\n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-publican; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"

 #. Tag: title
 #, no-c-format
 msgid "Using Swift for Secondary Storage"
 msgstr ""

 #. Tag: para
 #, no-c-format
 msgid "&PRODUCT; supports OpenStack Object Storage (<ulink url=\"http://swift.openstack.org/\"> Swift</ulink>) for secondary storage. When using Swift, you configure Swift storage for the entire &PRODUCT;, then set up NFS secondary storage for each zone as usual. The NFS storage in each zone acts as a staging area through which all templates and other secondary storage data pass before being forwarded to Swift. The Swift storage acts as a cloud-wide resource, making templates and other data available to any zone in the cloud. There is no hierarchy in the Swift storage, just one Swift container per storage object. Any secondary storage in the whole cloud can pull a container from Swift at need. It is not necessary to copy templates and snapshots from one zone to another, as would be required when using zone NFS alone. Everything is available everywhere"
 msgstr ""

 #. Tag: para
 #, no-c-format
 msgid "Swift storage must be set up before you add NFS secondary storage to zones. This is accomplished through some additional configuration steps on a fresh Management Server installation, before you add the first zone. The procedure is described in Adding a Zone in the Advanced Installation Guide."
 msgstr ""
	#Licensed to the Apache Software Foundation (ASF) under one
	#or more contributor license agreements. See the NOTICE file
	#distributed with this work for additional information
	#regarding copyright ownership. The ASF licenses this file
	#to you under the Apache License, Version 2.0 (the
	#"License"); you may not use this file except in compliance
	#with the License. You may obtain a copy of the License at
	#http://www.apache.org/licenses/LICENSE-2.0
	#Unless required by applicable law or agreed to in writing,
	#software distributed under the License is distributed on an
	#"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
	#KIND, either express or implied. See the License for the
	#specific language governing permissions and limitations
	#under the License.
	msgid ""
	msgstr ""
	"Project-Id-Version: 0\n"
	"POT-Creation-Date: 2013-02-02T20:12:00\n"
	"PO-Revision-Date: 2013-02-02T20:12:00\n"
	"Last-Translator: Automatically generated\n"
	"Language-Team: None\n"
	"MIME-Version: 1.0\n"
	"Content-Type: application/x-publican; charset=UTF-8\n"
	"Content-Transfer-Encoding: 8bit\n"

	#. Tag: title
	#, no-c-format
	msgid "Using Swift for Secondary Storage"
	msgstr ""

	#. Tag: para
	#, no-c-format
	msgid "&PRODUCT; supports OpenStack Object Storage (<ulink url=\"http://swift.openstack.org/\"> Swift</ulink>) for secondary storage. When using Swift, you configure Swift storage for the entire &PRODUCT;, then set up NFS secondary storage for each zone as usual. The NFS storage in each zone acts as a staging area through which all templates and other secondary storage data pass before being forwarded to Swift. The Swift storage acts as a cloud-wide resource, making templates and other data available to any zone in the cloud. There is no hierarchy in the Swift storage, just one Swift container per storage object. Any secondary storage in the whole cloud can pull a container from Swift at need. It is not necessary to copy templates and snapshots from one zone to another, as would be required when using zone NFS alone. Everything is available everywhere"
	msgstr ""

	#. Tag: para
	#, no-c-format
	msgid "Swift storage must be set up before you add NFS secondary storage to zones. This is accomplished through some additional configuration steps on a fresh Management Server installation, before you add the first zone. The procedure is described in Adding a Zone in the Advanced Installation Guide."
	msgstr ""