Content Pack for OpenStack Cinder StorageVolumes · IBM Cloud Orchestrator Content Pack for...

IBM Cloud OrchestratorContent Pack for OpenStack Cinder Storage VolumesVersion 2.4

Content Pack for OpenStack CinderStorage Volumes

��

NoteBefore using this information and the product it supports, read the information in “Notices” on page 13.

Contents

Preface . . . . . . . . . . . . . . . vAudience . . . . . . . . . . . . . . . v

IBM Cloud Orchestrator Content Packfor OpenStack Cinder Storage Volumes . 1Installing and configuring . . . . . . . . . . 1

Upgrading . . . . . . . . . . . . . . 1Toolkit scenarios . . . . . . . . . . . . . 2

Creating new volumes . . . . . . . . . . 2Attaching volumes . . . . . . . . . . . 3Detaching volumes . . . . . . . . . . . 4Deleting volumes . . . . . . . . . . . . 4Managing volumes related to a virtual systeminstance . . . . . . . . . . . . . . . 5

Toolkit developer's reference . . . . . . . . . 6Environmental variables . . . . . . . . . 6

ATTACH_TIMEOUT. . . . . . . . . . 6Business objects . . . . . . . . . . . . 6

AttachVolumesToInstanceRequestData . . . . 6CinderBreadcrumbsObject . . . . . . . . 7VMCredentials. . . . . . . . . . . . 7Volume . . . . . . . . . . . . . . 7Volume_Attachment . . . . . . . . . . 7VolumeManager . . . . . . . . . . . 7Volume type . . . . . . . . . . . . 7

Human services . . . . . . . . . . . . 7Attach Volumes . . . . . . . . . . . 7Detach Volumes . . . . . . . . . . . 7Create Volumes . . . . . . . . . . . 7Manage Volumes . . . . . . . . . . . 7

Coach views . . . . . . . . . . . . . 7Breadcrumbs . . . . . . . . . . . . 7Generic Listener . . . . . . . . . . . 7Password . . . . . . . . . . . . . 7Server Selected Listener. . . . . . . . . 7Vertical Two RadioButtons . . . . . . . . 8Volume Selected Listener . . . . . . . . 8

Business processes . . . . . . . . . . . 8Attach Volume. . . . . . . . . . . . 8Attach Volume Utility . . . . . . . . . 8Create Volume . . . . . . . . . . . . 8Create Volume Utility . . . . . . . . . 8Create Volumes . . . . . . . . . . . 8Detach Volumes . . . . . . . . . . . 8Delete Volume . . . . . . . . . . . . 8Manage Volumes . . . . . . . . . . . 8

Integration services . . . . . . . . . . . 8Attach Volume Service . . . . . . . . . 8Create Volume Service . . . . . . . . . 8Delete Volume . . . . . . . . . . . . 8Detach Volume . . . . . . . . . . . 9Format Volume on Linux . . . . . . . . 9Format Volume on Windows . . . . . . . 9Get Message . . . . . . . . . . . . 9Get Volume. . . . . . . . . . . . . 9Get Volume Attachment MetaData . . . . . 9List Volume Types . . . . . . . . . . 9List Volumes . . . . . . . . . . . . 9Load Message Bundle . . . . . . . . . 9Set Volume Attachment Metadata . . . . . 9Set Volume Metadata . . . . . . . . . 9Umount Attached Volume Partition. . . . . 9Unset Volume Metadata . . . . . . . . 9

Samples about how to use the available services andviews . . . . . . . . . . . . . . . . 10Importing XML into IBM Cloud Orchestrator . . . 10Troubleshooting . . . . . . . . . . . . . 12

Logs and traces . . . . . . . . . . . . 12Error codes . . . . . . . . . . . . . 12

Notices . . . . . . . . . . . . . . 13

Trademarks and Service Marks . . . . 15

© Copyright IBM Corp. 2013, 2014 iii

iv IBM Cloud Orchestrator V2.4: Content Pack for OpenStack Cinder Storage Volumes

Preface

This publication documents how to use the IBM Cloud Orchestrator Content Packfor OpenStack Cinder Storage Volumes.

AudienceThis information is intended for content developers of IBM Cloud Orchestratorwho implement or customize the content pack for OpenStack Cinder StorageVolumes.

© Copyright IBM Corp. 2013, 2014 v

vi IBM Cloud Orchestrator V2.4: Content Pack for OpenStack Cinder Storage Volumes

IBM Cloud Orchestrator Content Pack for OpenStack CinderStorage Volumes

Using the IBM Cloud Orchestrator Content Pack for OpenStack Cinder StorageVolumes, you can manage the lifecycle of block storage volumes through theOpenStack Cinder service. You can manage the block storage volumes to IBMCloud Orchestrator deployed instances.

Supported versionsv IBM Cloud Orchestrator version 2.4

Installing and configuringA good knowledge of IBM Cloud Orchestrator and of the Business ProcessManager programming model is required for using the toolkit as a softwaredevelopment kit (SDK) for building new content.

The content pack contains the following items:v The IBM Cloud Orchestrator for OpenStack Cinder Storage Volumes toolkit:

SCOrchestrator_OpenstackBlockStorage_Toolkit.twx. This toolkit depends onthe SCOrchestrator_Toolkit.twx (SCOTLKT toolkit), theSCOrchestrator_Support_IaaS_Toolkit.twx (SCOIAAS toolkit), SCOrchestratorNova Support Toolkit (SCONOVA toolkit), and theSCOrchestrator_Scripting_Utilities.twx (SCOSUKT toolkit) from which itleverages many base services.

v The XML definition file for the Offerings and Actions to be automaticallycreated, through the Cloud Orchestrator Self-Service Catalog Population Tool, forthe software distribution specific operations provided by this toolkit:cinder-offerings.xml.

v User documentation.

Before starting to use this content pack, you must:v Install the SCOrchestartor_OpenstackBlockStorage_Toolkit_*.twx into Business

Process Manager.v Create Offerings, Categories, and Instance Actions for the volume management

operations exposed by the toolkit.v On the region server that manages the region that you are working on, ensure

that you have:– The OpenStack Cinder service up and running.– At least one storage backend configured on Cinder and a volume type that

maps this backend. For instructions about how to configure a backend onCinder and how to create volume types, see the OpenStack documentation.

UpgradingIf you already have the toolkit installed and are upgrading from SmartCloudOrchestrator V2.3 to IBM Cloud Orchestrator V2.4, the toolkit is automaticallyupgraded. However, because of changes in the structure of the self-service catalogand new version 2.4 architecture, you must make some adjustments manually toclean up the environment so that the toolkits can run.

© Copyright IBM Corp. 2013, 2014 1

http://docs.openstack.org/

Make the following adjustments:v Remove the "Manage Volumes" user actionv Remove all the offerings under the category "Volume (Block Storage)

Management"

For information about removing user actions, see IBM Cloud Orchestrator >Managing orchestration workflows > Orchestration workflows > User actions inthe IBM Knowledge Center.

Toolkit scenariosThere are a number of scenarios that are immediately available from the toolkit.

First, you register the required Self-Service Offerings and Instance Actions, basedon the configuration parameters specified in each of the scenarios.

The following scenarios are available:v “Creating new volumes”v “Attaching volumes” on page 3v “Detaching volumes” on page 4v “Deleting volumes” on page 4v “Managing volumes related to a virtual system instance” on page 5

For more information about operation registration, see the following topics in theIBM Cloud Orchestrator section of the IBM Knowledge Center:v IBM Cloud Orchestrator > Managing orchestration workflows > IBM Cloud

Orchestrator content development > Automating the creation of categories,offerings, and user actions

v IBM Cloud Orchestrator > Managing orchestration workflows > Orchestrationworkflows > Self-service offerings

v IBM Cloud Orchestrator > Managing orchestration workflows > Orchestrationworkflows > User actions

v IBM Cloud Orchestrator > Managing orchestration workflows > Orchestrationworkflows > Event-triggered actions

v IBM Cloud Orchestrator > Working with self-service > Managing self-serviceofferings

v IBM Cloud Orchestrator > Working with self-service > Using self-servicev IBM Cloud Orchestrator > Managing orchestration workflows > Working with

Business Process Manager > Making a process available as an orchestrationaction

Alternatively, you can use the Self-Service Catalog Population Tool to automaticallyregister all of them at once.

Creating new volumesYou can create new volumes in your instance.

This use case is available as a self-service offering.

To run this scenario, perform the following steps:1. Go to the Self-Service Catalog and open the Create resources for cloud service

environment category.

2 IBM Cloud Orchestrator V2.4: Content Pack for OpenStack Cinder Storage Volumes

2. Start the Create volumes offering.3. Select the region and availability zone in which you want to create your

volume.4. Select a storage service level (volume type) from among the ones defined in the

region that you have selected and click Next.5. Insert the base name of your volume, choose the number of volumes that you

want to create, provide an optional description, and enter the volume size inGB.

Note: If you create more than one volume, from the first volume, an increasingindex is added as a suffix to the volume base name.

6. Click Submit.

Table 1. Configuration

Name Create volumes

Category Create resources for cloud service environment

Process Create Volumes (SCOrchestrator_OpenstackBlockStorage_Toolkit)

User interface Create Volumes (SCOrchestrator_OpenstackBlockStorage_Toolkit)

Attaching volumesYou can attach a volume in your project to a virtual machine and optionally formatit as a single partition and mount it to a given mount point.

This use case is available as instance action applicable to a volume resourceinstance. The volume instance must be in available status.

To run this scenario, perform the following steps:1. Go to the volume resource view by clicking the tab Assigned Resources and

then clicking the Volumes icon.2. Select an available volume.3. Click the Attach volumes action.4. Select a virtual machine from the list and click Next.5. Select Format volume if you want to format and mount the volume. If so:

a. Select the virtual machine operating system: Windows or Linux.b. Select the filesystem type.c. Enter the mount point.d. Decide if you want to connect to the machine by providing credentials, or

by an SSH key stored in the keystore or by your own SSH key. ForWindows operating systems, connection using the SSH key is disabled.Click Next.

Note: You cannot enable this option for machines that are powered off.6. Check the summary and click Submit.

Note: For Linux operating systems, if you chose to mount the file system on whichyou have formatted the volume, no record in the /etc/fstab file is added. Whenyou reboot the machine, the file system is no longer mounted and you must mountit manually.

IBM Cloud Orchestrator Content Pack for OpenStack Cinder Storage Volumes 3

After having attached the volume, its format and mount options (if there are any)are stored in the volume metadata. Volume metadata also contains the filesystemlabel and UUID.


Name Attach volume

Instance type volumes

Process Attach Volumes (SCOrchestrator_OpenstackBlockStorage_Toolkit)

User interface Attach Volumes (SCOrchestrator_OpenstackBlockStorage_Toolkit)

Detaching volumesIf necessary, you can umount and detach a volume.

This use case is available as an instance action applicable to a volume resourceinstance. The volume instance must be in in-use status.

If the volume has been previously formatted, its filesystem persistent data, such astype, label, and UUID are not deleted from the metadata.


then clicking the Volumes icon.2. Select an in-use volume.3. Click the Detach volume action.4. If your volume is mounted, specify how you want to connect to the machine.

See the options in “Attaching volumes” on page 3.5. Check the summary and click Submit.


Name Detach volume


Process Detach Volumes (SCOrchestrator_OpenstackBlockStorage_Toolkit)

User interface Detach Volumes (SCOrchestrator_OpenstackBlockStorage_Toolkit)

Deleting volumesYou can delete one or more volumes that are in available status.

This use case is available as an instance action applicable to a volume resourceinstance. The volume instance must be in available status.


then clicking the Volumes icon.2. Select one or more available volumes.3. Click the Delete volume action.4. Confirm the action.


Name Delete volume


Table 4. Configuration (continued)


Process Delete Volumes (SCOrchestrator_OpenstackBlockStorage_Toolkit)

Managing volumes related to a virtual system instanceYou can attach or delete all the available volumes defined in the project that youare currently logged on to. You can detach the volumes in the same project that arein use by the selected virtual system instance.

This use case is available as instance action applicable to an openstackvms resourceinstance.

To run this scenario, perform the following steps:1. Go to the Assigned Resources tab and click the VMs icon.2. Select a virtual machine.3. Click the Manage volume action.4. Select a volume from the ones created in the project that you are currently

logged onto and in the region where your instance is hosted. When you select avolume, the action buttons are enabled or disabled depending on the status ofthe selected volume. If the volume is available, you can attach it to a virtualmachine or delete it. If the volume is in use, you can detach it from its virtualmachine.

5. Click the management action that you want to perform on the selected volume:

Attach

Select the virtual machine where you want to attach the volume.Choose whether or not to format and mount the volume. You cannotenable this option on machines that are powered off. If you chose toformat and mount the volume, select operating system type, filesystemtype, mount point, and configure the access to the machine. See“Attaching volumes” on page 3. After reviewing the summary, clickSubmit. The volume is attached, formatted, and mounted to theselected machine.

Note: For Linux operating systems, if you chose to mount the filesystem on which you have formatted the volume, no record in the/etc/fstab file is added. When you reboot the machine, the file systemis no longer mounted and you must mount it manually.

Detach

If the volume is mounted, you must configure access to the virtualmachine to unmount it before detachment. Review the summary andclick Submit. The volume is detached from the attached virtualmachine.

Delete

Review the summary and click Submit. The volume is deleted and nolonger appears in the volume list.

Note: Only volumes that are in "available" state or attached to theselected Virtual System instance are listed in the volume table.



Name Manage volume

Instance type openstackvms

Process Manage Volumes (SCOrchestrator_OpenstackBlockStorage_Toolkit)

User interface Manage Volumes (SCOrchestrator_OpenstackBlockStorage_Toolkit)

Toolkit developer's referenceThis section contains reference information about the Business Process Managerartifacts exposed in the toolkit contained in the content pack. It is intended to beused by IBM Cloud Orchestrator content developers to extend the alreadyavailable scenarios or to write new scenarios leveraging the building blocksavailable from the toolkit.

The SCOrchestartor_OpenstackBlockStorage_Toolkit has dependencies against thefollowing toolkits:v SCOrchestrator_Support_vSys_Toolkit

v SCOrchestrator_Support_IaaS_Toolkit

v SCOrchestrator_Scripting_Utilities_Toolkit

v SCOrchestrator_Toolkit

v SCOrchestrator Nova Support Toolkit

The following items are the main building blocks of the toolkit:v “Environmental variables”v “Business objects”v “Human services” on page 7v “Coach views” on page 7v “Business processes” on page 8v “Integration services” on page 8

Environmental variablesSome environment variables are available so you can customize some behaviorswhen you run the use cases.

Environmental variables are defined in the toolkit in Toolkit Settings >Environment.

ATTACH_TIMEOUTThis variable specifies the maximum time, in minutes, to wait for a volumebecoming available after creation changing its status, for example from creating toavailable or from available to in-use.

Business objectsThere are Business Process Manager business objects defined in the toolkit.

AttachVolumesToInstanceRequestDataThis business object is used for storing information about the volume which isbeing attached to a given instance.


CinderBreadcrumbsObjectThis object is used for storing the temporary properties to manage the breadcrumbwidget that appears on the bottom part of some user interfaces.

VMCredentialsThis object stores the virtual machine credentials and in case also public andprivate ssh keys.

VolumeThis is the volume object. It contains info about the volume name, status, volumetype, ID, size, attachment metadata, and the server which it is attached to.

Volume_AttachmentThis object stores the correspondence between the volume and the server it isattached to.

VolumeManagerThis object contains the volume data, the operation which must be carried out onthis volume, the attachment data for this volume, the virtual machine object thevolume must be attached to and the region which the volume is defined on.

Volume typeThis object represents the volume type or Storage Service Level.

Human servicesThere are a number of Human Services artifacts available in the toolkit.

Attach VolumesThis an entry point user interface for the "Attach volume" instance action.

Detach VolumesThis an entry point user interface for the "Detach volume" instance action.

Create VolumesThis an entry point user interface for the "Create volumes" self-service offering.

Manage VolumesThis an entry point user interface for the "Manage volumes" instance action.

Coach viewsThere are a number of coach view artifacts available in the toolkit.

BreadcrumbsIt is the breadcrumb widget that appears on the bottom part of some userinterfaces.

Generic ListenerIt is the panel fragment which show the summary for detaching operation.

PasswordThe Password coach view renders the password as a masked input.

Server Selected ListenerThis is the listener on the servers list. It disables the Next button if no servers areselected.


Vertical Two RadioButtonsA coach view for implementing a choice between two possibilities.

Volume Selected ListenerThis is the listener on the volumes list. It disables the buttons which correspond toaction not compatible with the selected volume status. For example, volumes“in-use” can only be detached.

Business processesThere are a number of the business processes available in the toolkit.

Attach VolumeThis process attaches a volume to a given virtual server and can, if necessary,format and mount it after the attachment. It returns the volume object after theattachment.

Attach Volume UtilityA wrapper for the Attach Volume process which provides a more usable interfacefor input parameters.

Create VolumeThis process create a new volume of a given size within a given volume type on aspecified region. The volume is returned as output value if it has been availableafter a given timeout.

Create Volume UtilityA wrapper for the Create Volume process which provides a more usable interfacefor input parameters.

Create VolumesThis process loops over the number of requested volumes calling Create Volumeprocess for creating them.

Detach VolumesThis process detaches a volume and, if it is mounted, unmounts it beforedetachment.

Delete VolumeThis process triggers a volume deletion and wait for it is completed.

Manage VolumesThis process create a new volume or manage an existing volume as stated by anoperationid (1=ATTACH, 2=DETACH, 3=DELETE). It is called by “ManageVolumes Offering” and “Manage Volumes Action” processes.

Integration servicesThere are a number of integration services available in the toolkit.

Attach Volume ServiceThis integration service attaches one or more Cinder Volumes to a given server.

Create Volume ServiceThis integration service creates a volume.

Delete VolumeThis integration service deletes a volume.


Detach VolumeThis integration service detaches a volume from a server.

Format Volume on LinuxThis integration service connects to Linux machine, formats an attached volume,and mounts it to a given mount point. The volume is formatted as a singlepartition and mounted by using the script configure_volume.sh which is containedin the toolkit. It also updates the attachment metadata for the volume. The script isexecuted remotely via SSH by using the management IP address. The SSHconnection is tried for each available machine IP until it is successful. The SSHconnection can be carried out either by providing credentials or by using apre-configured privateKey.

Format Volume on WindowsThis integration service connects to a Windows machine, formats an attachedvolume, and mounts it to a given mount point. The volume is formatted as asingle partition and mounted by using the script configure_volume.ps1 which iscontained in the toolkit. It also updates the attachment metadata for the volume.The script is executed remotely via SMB by using the management IP address. TheSMB connection is tried for each available machine IP until it is successful.

Get MessageThis integration service gets a message from the loaded message bundle.

Get VolumeThis integration service retrieves a volume given its ID.

Get Volume Attachment MetaDataThis integration service returns the volume attachment data (filesystem type,mount point, filesystem label, and file system UUID) by retrieving them fromvolume metadata.

List Volume TypesThis integration service retrieves all volume types defined on a given region.

List VolumesThis integration service gets the list of all volumes defined on a given region.

Load Message BundleThis integration service loads the message bundles.

Set Volume Attachment MetadataThis integration service sets the volume attachment metadata.

Set Volume MetadataThis integration service set a volume metadata.

Umount Attached Volume PartitionThis integration service connects to a Windows or Linux machine and unmountsthe mounted volume. It also updates the attachment metadata for the volume. Thescript is executed remotely via SMB or SSH by using the management IP address.The SMB or SSH connection is tried for each available machine IP until it issuccessful. The SMB or SSH connection can be carried out either by providingcredentials or by using a pre-configured privateKey (only for Linux).

Unset Volume MetadataThis integration service deletes one volume metadata.


Samples about how to use the available services and viewsThe services that are delivered as part of this content pack can be used as startingpoints and as samples for developing new content.

Using samples can give you an idea about how to invoke and combine theIntegration Services delivered in the content pack. You can clone and adapt themto better fit your needs. Once you are familiar with them, you can start creatingyour new offerings and actions.

For information about how to develop new content, see the IBM CloudOrchestrator Content Development Guide available in the IBM Cloud Orchestratorsection of the IBM Knowledge Center:v IBM Cloud Orchestrator > Managing orchestration workflows > IBM Cloud

Orchestrator content development

Importing XML into IBM Cloud OrchestratorRefer to this sample XML file that you can use, with the Self-Service CatalogPopulation Tool, to create all the Offerings and Orchestration Actions required toleverage the capabilities provided by this content pack in IBM Cloud Orchestrator.<?xml version="1.0" encoding="UTF-8"?><catalog version="2.4"><automation-categories><category><name>Deploy cloud services</name><description>A set of offerings to manage the life cycle of

cloud services</description><icon>Storage</icon></category></automation-categories>

<offerings><offering><name>Create volumes</name><description>This offering allows you to create a volume

to be used in a domain--> project.</description><icon>Storage</icon><category-name>Deploy cloud services</category-name><process><name>Create Volumes</name></process><user-interface><name>Create Volumes</name></user-interface></offering></offerings>

<instance-actions>

<instance-action selection-type="multiple"><name>Delete volumes</name><description>This action applies to available volumes in the project.

Selected volumes are to be deleted.</description><icon>Storage</icon><instance-type>volumes</instance-type><process><name>Delete Volume</name></process><tags><tag>cinder</tag><tag>available</tag>


</tags></instance-action>

<instance-action selection-type="single"><name>Detach volume</name><description>This action applies to volumes attached to virtual

servers and enables you to detach the volumes from thevirtual servers they are attached to.</description>

<icon>Detach</icon><instance-type>volumes</instance-type><process><name>Detach Volumes</name></process><user-interface><name>Detach Volumes</name></user-interface><tags><tag>cinder</tag><tag>in-use</tag></tags></instance-action>

<instance-action selection-type="single"><name>Attach volume</name><description>This action applies to volumes not attached to virtual

servers and enables you to attach the volumes to a virtual serverdefined in the same project.</description>

<icon>Storage</icon><instance-type>volumes</instance-type><process><name>Attach Volume</name></process><user-interface><name>Attach Volume</name></user-interface><tags><tag>cinder</tag><tag>available</tag></tags></instance-action>

<instance-action selection-type="single"><name>Manage volume</name><description>This action enables you to manage the volumes of a virtual server.

It provides a single view of the status of the volumes attached to thevirtual server and enables you to manage existing volumes and createnew ones on behalf of the virtual server.</description>

<icon>Storage</icon><instance-type>openstackvms</instance-type><process><name>Manage Volumes</name></process><user-interface><name>Manage Volumes</name></user-interface><tags><tag>nova</tag></tags></instance-action>

</instance-actions>

</catalog>


TroubleshootingThere are some known problems and limitations.

Logs and tracesIf you receive an error, you can check the Business Process Manager log filesSystemOut.log and SystemErr.log at /opt/ibm/BPM/v8.5/profiles/Node1Profile/logs/SingleClusterMember1/.

You can find additional logs on the region server at /var/log/cinder and/var/log/nova. For errors regarding format and mount operation, a log fileformatFileSystem.log is present in the /tmp directory of the virtual machine. Errormessages are logged for all probable errors during deployment.

Error codesTable 6. Error codes

Error code Cause

CTJCA2000E The volume was not available within the defined timeout. SeeATTACH_TIMEOUT variable. Its status might be creating or error.

CTJCA2001E A problem occurred while attempting to format and mount the attachedvolume. This is usually due to a connection problem.

CTJCA2002E A problem occurred while attempting to unmount the attached volume.This is usually due to a connection problem.

CTJCA2006E A problem occurred in updating metadata of the volume.


Notices

This information was developed for products and services offered in the U.S.A.

IBM® may not offer the products, services, or features discussed in this documentin other countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte character set (DBCS) information,contact the IBM Intellectual Property Department in your country or sendinquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.


IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this information and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.


Trademarks and Service Marks

IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks ofInternational Business Machines Corporation in the United States, other countries,or both. If these and other IBM trademarked terms are marked on their firstoccurrence in this information with a trademark symbol (® or ™), these symbolsindicate U.S. registered or common law trademarks owned by IBM at the time thisinformation was published. Such trademarks may also be registered or commonlaw trademarks in other countries. A current list of IBM trademarks is available onthe Web at http://www.ibm.com/legal/copytrade.shtml.

Adobe, the Adobe logo, PostScript, and the PostScript logo are trademarks orregistered trademarks of Adobe Systems, Incorporated, in the United States and/orother countries.

Intel, the Intel logo, Intel Inside, the Intel Inside logo, Intel Centrino, the IntelCentrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium aretrademarks or registered trademarks of Intel Corporation or its subsidiaries in theUnited States and other countries.

Java™ and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.


http://www.ibm.com/legal/copytrade.shtml

��

Printed in USA

Content Pack for OpenStack Cinder StorageVolumes · IBM Cloud Orchestrator Content Pack for...

Documents

Transcript of Content Pack for OpenStack Cinder StorageVolumes · IBM Cloud Orchestrator Content Pack for...