IBM SmartCloud Orchestrator Content Pack for Opscode Chef

IBM Cloud OrchestratorContent Pack for Opscode ChefVersion 2.0

Content Pack for Opscode Chef

��

IBM Cloud OrchestratorContent Pack for Opscode ChefVersion 2.0

Content Pack for Opscode Chef

��

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

Contents

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

Chapter 1. IBM Cloud OrchestratorContent Pack for Opscode Chef . . . . 1Supported versions . . . . . . . . . . . . 1

Chapter 2. Installing and configuring . . 3Upgrading . . . . . . . . . . . . . . . 3Importing Chef Host certificate . . . . . . . . 3Setting the time difference between Endpoint virtualmachine and Chef server . . . . . . . . . . 4Adding a property in WebSphere Application Server 4

Chapter 3. Toolkit scenarios . . . . . . 5Registering the Chef host . . . . . . . . . . 5Unregistering the Chef host . . . . . . . . . 6Deploy Cookbook . . . . . . . . . . . . 6Installing software modules . . . . . . . . . 7

Chapter 4. Toolkit developer's reference 9Business processes . . . . . . . . . . . . 9

Register Chef Host . . . . . . . . . . . 9Unregister Chef Host . . . . . . . . . . 9Install Software Modules . . . . . . . . . 9Deploy Cookbook . . . . . . . . . . . 9

Human services . . . . . . . . . . . . . 9Register Chef Host . . . . . . . . . . . 9

Unregister Chef Host . . . . . . . . . . 9Deploy Cookbook . . . . . . . . . . . 10Install Software Modules . . . . . . . . . 10

Coach views . . . . . . . . . . . . . . 10Integration services . . . . . . . . . . . . 10

ListChefHosts . . . . . . . . . . . . 10getcookbooks . . . . . . . . . . . . . 10ListSoftwareModules . . . . . . . . . . 10GetSoftwareModuleAttributes . . . . . . . 10

General system services . . . . . . . . . . 10ConvertChefParamsToPlainList . . . . . . . 10ConvertPlainListParamsToChefParams . . . . 10

Chapter 5. Samples about how to usethe available services and views. . . . 11

Chapter 6. Importing XML into IBMCloud Orchestrator . . . . . . . . . 13

Chapter 7. Troubleshooting . . . . . . 15Known problems . . . . . . . . . . . . 15Error codes . . . . . . . . . . . . . . 16

Notices . . . . . . . . . . . . . . 17

Trademarks and Service Marks . . . . 19

© Copyright IBM Corp. 2013, 2014 iii

iv IBM Cloud Orchestrator: Content Pack for Opscode Chef

Preface

This publication documents how to use the IBM Cloud Orchestrator Content Packfor Opscode Chef.

AudienceThis information is intended for content developers of IBM Cloud Orchestratorwho must use or customize the IBM Cloud Orchestrator Content Pack for OpscodeChef.

© Copyright IBM Corp. 2013, 2014 v

vi IBM Cloud Orchestrator: Content Pack for Opscode Chef

Chapter 1. IBM Cloud Orchestrator Content Pack for OpscodeChef

Opscode Chef is an open-source systems integration framework built forautomating the cloud.

Opscode Chef translates your infrastructure into code and you can easily build,rebuild, and configure infrastructure solutions. Using theSCOrchestrator_OpscodeChef_Toolkit content pack you can install software onLinux Virtual Machines by means of applying Chef roles or cookbook.

For more information, see http://www.opscode.com/chef/.

Supported versionsv IBM Cloud Orchestrator version 2.4v Open Source Chef Server version 11.0

© Copyright IBM Corp. 2013, 2014 1

http://www.opscode.com/chef/

2 IBM Cloud Orchestrator: Content Pack for Opscode Chef

Chapter 2. Installing and configuring

Install and configure the IBM Cloud Orchestrator Content Pack for Opscode Chef.

The content pack contains the following items:v The Cloud Orchestrator Opscode Chef toolkit:

SCOrchestrator_OpscodeChef_Toolkit_YYYYMMDD.twx

v The XML definition file for the Offerings and Categories to be automaticallycreated through the IBM Cloud Orchestrator Self-Service Catalog PopulationTool: chef-offerings.xml

v User documentation.

Before starting to use this content pack, you must:v Import the Chef Host certificate.v Make sure that the Chef server is reachable with its valid host name by all

clients. This verification is required because of the limitation that exists in usingthe IP address for registering a Chef client.

v Make sure that the time difference between the Endpoint virtual machine andthe Chef server is not more than 15 minutes.

v Connect the Endpoint clients to the internet to automatically install the Chefclient by the toolkit. If this is not possible, install the Chef client manually to allEndpoints.

v Add the com.ibm.crypto.provider.DoRSATypeChecking property in WebSphereApplication Server and set the value as false.

UpgradingIf you already have the toolkit installed and are upgrading from SmartCloudOrchestrator V2.3 to IBM Cloud Orchestrator V2.4, because of changes in thestructure of the self-service catalog and new version 2.4 architecture, you mustmake some adjustments manually to clean up the environment so that the toolkitscan run.

Make the following adjustments:v Remove the "Install Software Modules" and "Deploy Cookbook" user actionsv Remove all the offerings under the category "Chef".v For information about removing user actions, see IBM Cloud Orchestrator >

Managing orchestration workflows > Orchestration workflows > User actions inthe IBM Knowledge Center.

Importing Chef Host certificateYou can import the Chef Host certificate.

About this task

The signer must be added to the local truststore. You can use the Retrieve fromport option in the administrative console to retrieve the certificate and resolve theproblem. If you determine that the request is trusted, complete the following steps:


Procedure1. Log in to the administrative console - https://<Business Process Manager IP

address>:<Port number>/ibm/console/logon.jsp.2. Expand Security and click SSL certificate and key management.3. Under Configuration settings, click Manage endpoint security

configurations.4. Expand the appropriate Outbound configuration, navigate to and select the

following node: Outbound : xxxxCell1 (CellDefaultSSLSettings) :nodes : Node1(NodeDefaultSSLSettings) : servers :SingleClusterMember1.

5. In Related Items, click Key stores and certificates.6. Click CellDefaultTrustStore.7. In Additional Properties, click Signer certificates and Retrieve From Port.8. Enter your appstore host name in the host name field. Normally, this is the

host name of your Chef server.9. Enter 443 in the Port field.

10. Enter <Chef Server host name> in the Alias field.11. Click Retrieve Signer Information.12. Verify that the certificate information is for a certificate that you can trust.13. Click Apply and Save.Related information:http://publib.boulder.ibm.com/infocenter/javasdk/v1r4m2/index.jsp?topic=Information about keytool

Setting the time difference between Endpoint virtual machine and Chefserver

Procedure1. Update Timezone on Linux - ln -sf /usr/share/zoneinfo/Asia/Kolkata/etc/

localtime.2. Change Time on Linux date - --set = <current time in given format>. For

example, Sun Feb 28 14:05:15 IST 2014.

Adding a property in WebSphere Application ServerProcedure1. Open the console window.2. Click WebSphere Application Server 8.0.0.6.3. Go to Servers > Server types and click WebSphere Application Server.4. Go to the Application Server and click the Business Process Manager server.5. Go to Process Definition > Java Virtual Machine > Custom Properties.6. Click New and add the com.ibm.crypto.provider.DoRSATypeChecking property

and set value to false.7. 7. Click Save.


http://publib.boulder.ibm.com/infocenter/javasdk/v1r4m2/index.jsp?topic=

Chapter 3. Toolkit scenarios

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

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

The following scenarios are available:v “Registering the Chef host”v “Unregistering the Chef host” on page 6v “Deploy Cookbook” on page 6v “Installing software modules” on page 7

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

workflows > Self-service offeringsv IBM Cloud Orchestrator > Working with self-service > Managing self-service

offeringsv 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 IBM Cloud Orchestrator Self-Service CatalogPopulation Tool, available with IBM Cloud Orchestrator to automatically create allof them at once by providing the chef-offerings.xml configuration file that comeswith this content pack. For more information about how to use the tool, see thefollowing topic in 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

Registering the Chef hostTo use a configured chef server in the IBM Cloud Orchestrator, you must firstregister the host. This is a preliminary step for the “Install Software Scenario”.

Note: The Chef host must be registered only by an administrator.

To run this scenario, perform the following steps:1. Log in to the IBM Cloud Orchestrator UI.2. Go to the Self-Service Catalog and open the Chef category.3. Click Register Chef Host.4. Enter the following Chef Host details:

Host nameHost name of the Chef server

Port Port on which the connection is established


Private KeyFile that contains the private key of the client specified in the Clientfield.

Chef-validator keyFile that contains the chef-validator key

Client Name of the client with the admin role used to access the Chef ServerAPI.

5. Click Create. The details of the Chef host are stored in the database.

Both the private and validator key can be generated by the Chef server. For moreinformation, see http://docs.opscode.com/chef_private_keys.html.

Table 1. Configuration of the offering

Name Register Chef Host

Category Chef

Process Register Chef Host (SCOrchestrator_OpscodeChef)

User interface Register Chef Host (SCOrchestrator_OpscodeChef)

Unregistering the Chef hostUnregister the configuration of a Chef server registered in IBM Cloud Orchestrator.

Note: The Chef host must be unregistered only by an administrator.

To run this scenario, perform the following steps:1. Log in to the IBM Cloud Orchestrator UI.2. Go to the Self-Service Catalog and open the Chef category.3. Click Unregister Chef Host.4. Select the server from the list.5. Click Unregister Chef Host. The details of the Chef Host are removed from the

database.

Table 2. Configuration of the offering

Name Unregister Chef Host

Category Chef

Process Unregister Chef Host (SCOrchestrator_OpscodeChef)

User interface Unregister Chef Host (SCOrchestrator_OpscodeChef)

Deploy CookbookIn Chef, a cookbook is an essential component for configuration.

For more information about Opscode Chef, see http://docs.opscode.com/essentials_cookbooks.html. This content pack provides an easy-to-use interface todeploy the cookbook on a virtual machine.

Before being able to install software modules to the deployed virtual images, youmust:v Register a Chef host


http://docs.opscode.com/chef_private_keys.html

http://docs.opscode.com/essentials_cookbooks.html

http://docs.opscode.com/essentials_cookbooks.html

v Create cookbooks on Chef Server

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 Deploy Cookbook action.4. Select the Chef Server from the list and click Next.5. Select the Cookbook that you want to deploy6. Click Install.7. 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. Click Next. Note:You cannot enable this option for machines that are powered off.

8. Click Finish.

Table 3. Configuration of the user action

Name Deploy Cookbook

Category Chef

Process Deploy cookbook (SCOrchestrator_OpscodeChef)

User interface Deploy cookbook (SCOrchestrator_OpscodeChef)

Installing software modulesInstall selected software modules on all the Virtual Machines.

A software module corresponds to a role created in the selected Chef server. Theaction of installing a software module on virtual image is the same as applying arole to a node. As a result, before being able to install software modules to thedeployed virtual images, you must:v Register a Chef hostv Create the roles definitions in the registered Chef host

If a role definition contains default attributes, the attributes can be customized inthe IBM Cloud Orchestrator UI. The attributes are applied during the installationof the software unless overridden by the Chef cookbooks, recipes, roles, orenvironment attributes. For more information, see http://docs.opscode.com/essentials_roles.html.

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 Install Software Modules action.4. Select the Chef Server from the list and click Next.5. Select the Software Module. If the Software Module contains parameters and

you want to change the default values, provide the values and click Apply tosave them.

6. Click Install.7. 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. Click Next. Note:You cannot enable this option for machines that are powered off.

8. Click Finish.

Chapter 3. Toolkit scenarios 7

http://docs.opscode.com/essentials_roles.html

http://docs.opscode.com/essentials_roles.html

Table 4. Configuration of the User Action

Name Install Software Modules

Category Chef

Process Install Software Modules (SCOrchestrator_OpscodeChef)

User interface Install Software Modules (SCOrchestrator_OpscodeChef)


Chapter 4. Toolkit developer's reference

This 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 SCOrchestrator_Opscode has dependencies against the following toolkits:v SCOrchestrator_Scripting_Utilities_Toolkit

v SCOrchestrator_Toolkit

The following items are the main building blocks of the toolkit:v “Business processes”v “Human services”v “Coach views” on page 10v “Integration services” on page 10v “General system services” on page 10

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

Register Chef HostThis business process is responsible for registering the Chef Host configuration inthe repository.

Unregister Chef HostThis business process is responsible for unregistering the Chef Host configurationfrom the repository.

Install Software ModulesThis business process is responsible for installing software modules on a virtualmachine, applying roles to a node in Chef terminology.

Deploy CookbookThis business process is responsible for deploying cookbooks on a virtual machine.

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

Register Chef HostThis is the human service for collecting the configuration of the Chef host.

Unregister Chef HostThis is the human service for unregistering the configuration of the Chef host.


Deploy CookbookThis business process is responsible for deploying cookbooks on a virtual machine

Install Software ModulesThis is the human service for collecting the information to install software moduleson a the virtual machines within a virtual system.

Coach viewsThere are no public coach views currently available.

Integration servicesIntegration services are used to implement the activities in a business processdefinition. It implements the required feature when the Business ProcessDefinitions and its tasks are started.

ListChefHostsReturns the list of the Chef Hosts registered in the repository.

getcookbooksReturns the list of cookbooks defined in the specified Chef Host.

ListSoftwareModulesReturns the list of software modules (roles) defined in the specified Chef Host.Each software module is described by a name and a description.

GetSoftwareModuleAttributesReturns the default attributes, in JSON format, of the specified software module(role) defined in the specified Chef Host.

General system servicesThere are some general system services available in the toolkit.

ConvertChefParamsToPlainListConverts the Chef attributes in JSON format to a list of NameValuePair objects,where the name is the attribute name in plain format, for example,apache.default_ports, and the value is the attribute value in string format.

ConvertPlainListParamsToChefParamsConverts a list of NameValuePair objects, where the name is the attribute name inplain format, for example, apache.default_ports, and the value is the attributevalue in string format, to a JSON format.


Chapter 5. Samples about how to use the available servicesand views

The 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 Knowledge Center:v IBM Cloud Orchestrator > Managing orchestration workflows > IBM Cloud

Orchestrator content development



Chapter 6. Importing XML into IBM Cloud Orchestrator

Refer 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"?>

<catalog version="2.4">

<automation-categories>

<category><name>Chef</name><description>Service offerings that allow to handle software

management operations through a Chef server</description><icon>Application</icon>

</category>

</automation-categories>

<offerings><offering>

<name>Register Chef Host</name><description>Register a Chef server configuration.</description><icon>Application</icon><category-name>Chef</category-name><process>

<name>Register Chef Host</name></process><user-interface>

<name>Register Chef Host</name></user-interface>

</offering>

<offering><name>Unregister Chef Host</name><description>Unregister a Chef server configuration.</description><icon>Application</icon><category-name>Chef</category-name><process>

<name>Unregister Chef Host</name></process><user-interface>

<name>Unregister Chef Server</name></user-interface>

</offering>

</offerings>

<instance-actions><instance-action selection-type="single"><name>Deploy Cookbook</name><description>This action applies to virtual servers and enables

you to deploy cookbooks defined on the registeredChef Servers</description>

<instance-type>openstackvms</instance-type><process><name>Deploy cookbook</name></process>

<user-interface><name>Deploy Cookbook</name></user-interface><tags>


<tag>active</tag></tags></instance-action>

<instance-action selection-type="single"><name>Install Software Modules using Chef</name><description>This action applies to virtual servers and enables

you to apply Roles defined on the registered Chef Servers</description><instance-type>openstackvms</instance-type><process><name>Install Software Modules</name></process><user-interface><name>Install Software Modules</name></user-interface><tags>

<tag>active</tag></tags></instance-action>

</instance-actions></catalog>


Chapter 7. Troubleshooting

There are some known problems and limitations.

Error messages are logged for all failures occurring during the execution of thetriggered operations.

The main locations to check are the BPM SystemOut.log and SystemErr.log fileslocated under the following directory, on the Business Process Manager machine:/opt/ibm/BPM/v8.5/profiles/Node1Profile/logs/SingleClusterMember1/.

Error indications and messages are displayed in the IBM Cloud Orchestrator userinterface when interacting with the Offerings and when monitoring the outcome ofa queued operation.

The BPM Admin Console (https://<bpm_hostname>:9080/ProessAdmin) can also beused to inspect a failed process and check its internal status and parameters.

Known problemsThere are some known problems you might encounter when using this toolkit.

Install Software Modules UI takes too long to return the list of softwareThe reason is that the Chef Server is unreachable. Solution: Power on themachine that hosts the Chef server and start the Chef server.

User action “Install Software Modules” did not completed successfully

The software installation on one of the virtual machine failed. Check the/opt/ibm/BPM/v8.5/profiles/Node1Profile/logs/SingleClusterMember1/SystemOut.log file to see the root causes.

Failure might occur for the following reasons:v The chef-client is not installed on the virtual machine and the virtual

machine cannot connect to the “www.opscode.chef' site to download thechef-client. Solution: Configure the machine's network or install thechef-client before running this action.

v The chef-client run process exited unsuccessfully. This might occur forthe following reasons:– The run list refers to recipes or roles not loaded in the Chef server.

Solution: Upload the missing recipes or roles to the Chef server.– One of the recipes cannot be compiled due to an error. Solution: Fix

the specified error.

The “Install Software on Vms” process stops on error. This means if youselect multiple virtual machines and a software installation fails on one ofthem, the process exits without attempting to install the software on theremaining selected machines.


Error codesError messages are logged for all probable errors during deployment. The syntaxof the error message is as follows: <Base error code>: <Detailed error code>:<Error message>.

The table provides the list of all the error codes and their probable causes.

Table 5. Error codes

Error code Description

CTJCA1301E Enter IP address.

CTJCA1302E Organization type must be private or hosted.

CTJCA1303E Enter client name.

CTJCA1304E Enter organization type.

CTJCA1305E Enter IP address.

CTJCA1306E No cookbook found.

CTJCA1307E System time mismatch.

CTJCA1308E Cannot connect to internet for downloading chef client. VerifyDNS settings or install Chef Client manually.

CTJCA1309E Connection timeout.

CTJCA1311E Chef Server generic error. Check BPM server logs for moredetails.

CTJCA1312E Invalid private key or mismatched private key and client.

CTJCA1313E Incorrect client name specified.

CTJCA1314E Unable to connect to chef server, correct host name must beused.

CTJCA1315E Prerequisites not met. See documentation (WebSphereApplication Server upgrade missing or property not added).

CTJCA1316E Unable to connect either IP address is used or incorrect hostname specified.

CTJCA1317E Unable to find node on Chef Server for given endpoint.

CTJCA1318E Prerequisites not met. See documentation (Certificate not addedto truststore).

CTJCA1319E Prerequisites not met. See documentation (OpenSSL library notinstalled).

CTJCA1320E An error occurred while converting keys. Check logs for moredetails.

CTJCA1321E An error occurred while registering the node. Check logs formore details.

CTJCA1322E There is no Chef Server registered.

CTJCA1323E Unable to contact the specified Chef Server. Check that the ChefServer is running and that the provided connection data iscorrect.

CTJCA1324E Chef run process exited unsuccessfully.

CTJCA1325E Virtual Machine is powered off. Cannot perform operation.

CTJCA1326E Failed to perform Chef Client install/register operation.

CTJCA1327E No Chef Server configured in IBM Cloud Orchestrator. Registerat least one Chef Server before performing this operation.


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

IBM SmartCloud Orchestrator Content Pack for Opscode Chef

Documents