IBM SmartCloud Orchestrator Content Pack For Opscode Chef

IBM Cloud Orchestrator
Content Pack for Opscode Chef

Version 2.0
IBM Cloud Orchestrator

Version 2.0
Note
Before using this information and the product it supports, read the information in Notices on page 17.
Contents
Preface . . . . . . . . . . . . . . . v
Audience
. v
Chapter 1. IBM Cloud Orchestrator

Content Pack for Opscode Chef . . . . 1
Supported versions .
. 1
Chapter 2. Installing and configuring . . 3

Upgrading . . . . . . . . . . . . . . . 3
Importing Chef Host certificate . . . . . . . . 3
Setting the time difference between Endpoint virtual
machine and Chef server . . . . . . . . . . 4
Adding a property in WebSphere Application Server 4
Chapter 3. Toolkit scenarios . . . . . . 5

Registering the Chef host .
Unregistering the Chef host
Deploy Cookbook . . .
Installing software modules
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 4. Toolkit developer's reference

Business processes . . .
Register Chef Host . .
Unregister Chef Host .
Install Software Modules
Deploy Cookbook . .
Human services . . . .
Register Chef Host . .
.
.
.
.
.
.
.
Copyright IBM Corp. 2013, 2014
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Unregister Chef Host . . . . . .

Deploy Cookbook . . . . . . .
Install Software Modules . . . . .
Coach views . . . . . . . . . .
Integration services . . . . . . . .
ListChefHosts . . . . . . . .
getcookbooks . . . . . . . . .
ListSoftwareModules . . . . . .
GetSoftwareModuleAttributes . . .
General system services . . . . . .
ConvertChefParamsToPlainList . . .
ConvertPlainListParamsToChefParams
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 9
10
10
10
10
10
10
10
10
10
10
10
Chapter 5. Samples about how to use

the available services and views. . . . 11
5
6
6
7
Chapter 6. Importing XML into IBM

Cloud Orchestrator . . . . . . . . . 13
Known problems
Error codes . .
9
9
9
9
9
9
9
Chapter 7. Troubleshooting . . . . . . 15
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 15
. 16
Notices . . . . . . . . . . . . . . 17
Trademarks and Service Marks . . . . 19
iii
iv
IBM Cloud Orchestrator: Content Pack for Opscode Chef
Preface
This publication documents how to use the IBM Cloud Orchestrator Content Pack
for Opscode Chef.
Audience
This information is intended for content developers of IBM Cloud Orchestrator
who must use or customize the IBM Cloud Orchestrator Content Pack for Opscode
Chef.
vi
Chapter 1. IBM Cloud Orchestrator Content Pack for Opscode

Chef
Opscode Chef is an open-source systems integration framework built for
automating the cloud.
Opscode Chef translates your infrastructure into code and you can easily build,
rebuild, and configure infrastructure solutions. Using the
SCOrchestrator_OpscodeChef_Toolkit content pack you can install software on
Linux Virtual Machines by means of applying Chef roles or cookbook.
For more information, see http://www.opscode.com/chef/.
Supported versions
v IBM Cloud Orchestrator version 2.4
v Open Source Chef Server version 11.0
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 automatically
created through the IBM Cloud Orchestrator Self-Service Catalog Population
Tool: 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 using
the IP address for registering a Chef client.
v Make sure that the time difference between the Endpoint virtual machine and
the Chef server is not more than 15 minutes.
v Connect the Endpoint clients to the internet to automatically install the Chef
client by the toolkit. If this is not possible, install the Chef client manually to all
Endpoints.
v Add the com.ibm.crypto.provider.DoRSATypeChecking property in WebSphere
Application Server and set the value as false.
Upgrading
If you already have the toolkit installed and are upgrading from SmartCloud
Orchestrator V2.3 to IBM Cloud Orchestrator V2.4, because of changes in the
structure of the self-service catalog and new version 2.4 architecture, you must
make some adjustments manually to clean up the environment so that the toolkits
can run.
Make the following adjustments:
v Remove the "Install Software Modules" and "Deploy Cookbook" user actions
v 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 in
the IBM Knowledge Center.
Importing Chef Host certificate

You can import the Chef Host certificate.
About this task

The signer must be added to the local truststore. You can use the Retrieve from
port option in the administrative console to retrieve the certificate and resolve the
problem. If you determine that the request is trusted, complete the following steps:
Procedure
1. 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 Chef
server
Procedure
1. 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 Server

Procedure
1.
2.
3.
4.
5.
Open the console window.

Click WebSphere Application Server 8.0.0.6.
Go to Servers > Server types and click WebSphere Application Server.
Go to the Application Server and click the Business Process Manager server.
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.
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 6
v Deploy Cookbook on page 6
v Installing software modules on page 7
For more information about operation registration, see the following topics in the
IBM Knowledge Center:
v IBM Cloud Orchestrator > Managing orchestration workflows > Orchestration
workflows > Self-service offerings
v IBM Cloud Orchestrator > Working with self-service > Managing self-service
offerings
v IBM Cloud Orchestrator > Working with self-service > Using self-service
v IBM Cloud Orchestrator > Managing orchestration workflows > Working with
Business Process Manager > Making a process available as an orchestration
action
Alternatively you can use the IBM Cloud Orchestrator Self-Service Catalog
Population Tool, available with IBM Cloud Orchestrator to automatically create all
of them at once by providing the chef-offerings.xml configuration file that comes
with this content pack. For more information about how to use the tool, see the
following 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 host

To use a configured chef server in the IBM Cloud Orchestrator, you must first
register 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 name
Host name of the Chef server
Port
Port on which the connection is established
Private Key
File that contains the private key of the client specified in the Client
field.
Chef-validator key
File that contains the chef-validator key
Client Name of the client with the admin role used to access the Chef Server
API.
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 more
information, 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 host

Unregister the configuration of a Chef server registered in IBM Cloud Orchestrator.
Note: The Chef host must be unregistered only by an administrator.
To
1.
2.
3.
run this scenario, perform the following steps:

Log in to the IBM Cloud Orchestrator UI.
Go to the Self-Service Catalog and open the Chef category.
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 Cookbook
In 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 to
deploy the cookbook on a virtual machine.
Before being able to install software modules to the deployed virtual images, you
must:
v Register a Chef host
v Create cookbooks on Chef Server

Go to the Assigned Resources tab and click the VMs icon.
Select a virtual machine.
Click the Deploy Cookbook action.
Select the Chef Server from the list and click Next.
Select the Cookbook that you want to deploy
Click Install.
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.
1.
2.
3.
4.
5.
6.
7.
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 modules

Install selected software modules on all the Virtual Machines.
A software module corresponds to a role created in the selected Chef server. The
action of installing a software module on virtual image is the same as applying a
role to a node. As a result, before being able to install software modules to the
deployed virtual images, you must:
v Register a Chef host
v Create the roles definitions in the registered Chef host
If a role definition contains default attributes, the attributes can be customized in
the IBM Cloud Orchestrator UI. The attributes are applied during the installation
of the software unless overridden by the Chef cookbooks, recipes, roles, or
environment attributes. For more information, see http://docs.opscode.com/
essentials_roles.html.
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 to
save 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
Table 4. Configuration of the User Action
Name
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 Manager
artifacts exposed in the toolkit contained in the content pack. It is intended to be
used by IBM Cloud Orchestrator content developers to extend the already
available scenarios or to write new scenarios leveraging the building blocks
available 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 10
v Integration services on page 10
v General system services on page 10
Business processes
There are a number of the business processes available in the toolkit.
Register Chef Host

This business process is responsible for registering the Chef Host configuration in
the repository.

This business process is responsible for unregistering the Chef Host configuration
from the repository.

This business process is responsible for installing software modules on a virtual
machine, applying roles to a node in Chef terminology.
Deploy Cookbook
This business process is responsible for deploying cookbooks on a virtual machine.
Human services
There are a number of Human Services artifacts available in the toolkit.
Register Chef Host

This is the human service for collecting the configuration of the Chef host.

This is the human service for unregistering the configuration of the Chef host.
Deploy Cookbook
This business process is responsible for deploying cookbooks on a virtual machine

This is the human service for collecting the information to install software modules
on a the virtual machines within a virtual system.
Coach views
There are no public coach views currently available.
Integration services
Integration services are used to implement the activities in a business process
definition. It implements the required feature when the Business Process
Definitions and its tasks are started.
ListChefHosts
Returns the list of the Chef Hosts registered in the repository.
getcookbooks
Returns the list of cookbooks defined in the specified Chef Host.
ListSoftwareModules
Returns the list of software modules (roles) defined in the specified Chef Host.
Each software module is described by a name and a description.
GetSoftwareModuleAttributes
Returns the default attributes, in JSON format, of the specified software module
(role) defined in the specified Chef Host.
General system services

There are some general system services available in the toolkit.
ConvertChefParamsToPlainList
Converts 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.
ConvertPlainListParamsToChefParams
Converts 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, to a JSON format.
10
Chapter 5. Samples about how to use the available services

and views
The services that are delivered as part of this content pack can be used as starting
points and as samples for developing new content.
Using samples can give you an idea about how to invoke and combine the
Integration Services delivered in the content pack. You can clone and adapt them
to better fit your needs. Once you are familiar with them, you can start creating
your new offerings and actions.
For information about how to develop new content, see the IBM Cloud
Orchestrator Content Development Guide available in the IBM Knowledge Center:
v IBM Cloud Orchestrator > Managing orchestration workflows > IBM Cloud
Orchestrator content development
11
12
Chapter 6. Importing XML into IBM Cloud Orchestrator

Refer to this sample XML file that you can use, with the Self-Service Catalog
Population Tool, to create all the Offerings and Orchestration Actions required to
leverage 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>
<category-name>Chef</category-name>
<process>
</process>
<user-interface>
</user-interface>
</offering>
<offering>
<name>Unregister Chef Host</name>
<description>Unregister a Chef server configuration.</description>
<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 registered
Chef Servers</description>
<instance-type>openstackvms</instance-type>
<process>
<name>Deploy cookbook</name>
</process>
<user-interface>
<name>Deploy Cookbook</name>
</user-interface>
<tags>
13
<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>
14
Chapter 7. Troubleshooting
There are some known problems and limitations.
Error messages are logged for all failures occurring during the execution of the
triggered operations.
The main locations to check are the BPM SystemOut.log and SystemErr.log files
located 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 user
interface when interacting with the Offerings and when monitoring the outcome of
a queued operation.
The BPM Admin Console (https://<bpm_hostname>:9080/ProessAdmin) can also be
used to inspect a failed process and check its internal status and parameters.
Known problems
There are some known problems you might encounter when using this toolkit.
Install Software Modules UI takes too long to return the list of software
The reason is that the Chef Server is unreachable. Solution: Power on the
machine 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 the
chef-client. Solution: Configure the machine's network or install the
chef-client before running this action.
v The chef-client run process exited unsuccessfully. This might occur for
the 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 you
select multiple virtual machines and a software installation fails on one of
them, the process exits without attempting to install the software on the
remaining selected machines.
15
Error codes
Error messages are logged for all probable errors during deployment. The syntax
of 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
16
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. Verify

DNS settings or install Chef Client manually.
CTJCA1309E
Connection timeout.
CTJCA1311E
Chef Server generic error. Check BPM server logs for more
details.
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 be

used.
CTJCA1315E
Prerequisites not met. See documentation (WebSphere

Application Server upgrade missing or property not added).
CTJCA1316E
Unable to connect either IP address is used or incorrect host

name specified.
CTJCA1317E
Unable to find node on Chef Server for given endpoint.
CTJCA1318E
Prerequisites not met. See documentation (Certificate not added

to truststore).
CTJCA1319E
Prerequisites not met. See documentation (OpenSSL library not

installed).
CTJCA1320E
An error occurred while converting keys. Check logs for more

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

more details.
CTJCA1322E
There is no Chef Server registered.
CTJCA1323E
Unable to contact the specified Chef Server. Check that the Chef
Server is running and that the provided connection data is
correct.
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. Register

at 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 document
in other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte character set (DBCS) information,
contact the IBM Intellectual Property Department in your country or send
inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan Ltd.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.
This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
17
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758
U.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 material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement, or any equivalent agreement
between us.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.
18
Trademarks and Service Marks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corporation in the United States, other countries,
or both. If these and other IBM trademarked terms are marked on their first
occurrence in this information with a trademark symbol ( or ), these symbols
indicate U.S. registered or common law trademarks owned by IBM at the time this
information was published. Such trademarks may also be registered or common
law trademarks in other countries. A current list of IBM trademarks is available on
the Web at http://www.ibm.com/legal/copytrade.shtml.
Adobe, the Adobe logo, PostScript, and the PostScript logo are trademarks or
registered trademarks of Adobe Systems, Incorporated, in the United States and/or
other countries.
Intel, the Intel logo, Intel Inside, the Intel Inside logo, Intel Centrino, the Intel
Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are
trademarks or registered trademarks of Intel Corporation or its subsidiaries in the
United States and other countries.
Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Oracle and/or its affiliates.
Linux is a registered trademark of Linus Torvalds in the United States, other
countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
19
20

Printed in USA

IBM SmartCloud Orchestrator Content Pack For Opscode Chef

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

IBM SmartCloud Orchestrator Content Pack For Opscode Chef

Caricato da

Copyright:

Formati disponibili

IBM Cloud Orchestrator

Content Pack for Opscode Chef

Content Pack for Opscode Chef

IBM Cloud Orchestrator

Content Pack for Opscode Chef

Chapter 1. IBM Cloud Orchestrator

Chapter 2. Installing and configuring . . 3

Chapter 3. Toolkit scenarios . . . . . . 5

Chapter 4. Toolkit developer's reference

Copyright IBM Corp. 2013, 2014

Unregister Chef Host . . . . . .

Chapter 5. Samples about how to use

Chapter 6. Importing XML into IBM

IBM Cloud Orchestrator: Content Pack for Opscode Chef

Copyright IBM Corp. 2013, 2014

IBM Cloud Orchestrator: Content Pack for Opscode Chef

Chapter 1. IBM Cloud Orchestrator Content Pack for Opscode

Copyright IBM Corp. 2013, 2014

IBM Cloud Orchestrator: Content Pack for Opscode Chef

Chapter 2. Installing and configuring

Importing Chef Host certificate

About this task

Copyright IBM Corp. 2013, 2014

Adding a property in WebSphere Application Server

Open the console window.

6. Click New and add the com.ibm.crypto.provider.DoRSATypeChecking property

IBM Cloud Orchestrator: Content Pack for Opscode Chef

Chapter 3. Toolkit scenarios

Registering the Chef host

Port on which the connection is established

Register Chef Host

Register Chef Host (SCOrchestrator_OpscodeChef)

Register Chef Host (SCOrchestrator_OpscodeChef)

Unregistering the Chef host

run this scenario, perform the following steps:

4. Select the server from the list.

Unregister Chef Host

Unregister Chef Host (SCOrchestrator_OpscodeChef)

Unregister Chef Host (SCOrchestrator_OpscodeChef)

IBM Cloud Orchestrator: Content Pack for Opscode Chef

v Create cookbooks on Chef Server

Table 3. Configuration of the user action

Deploy cookbook (SCOrchestrator_OpscodeChef)

Deploy cookbook (SCOrchestrator_OpscodeChef)

Installing software modules

Table 4. Configuration of the User Action

Install Software Modules

Install Software Modules (SCOrchestrator_OpscodeChef)

Install Software Modules (SCOrchestrator_OpscodeChef)

IBM Cloud Orchestrator: Content Pack for Opscode Chef

Chapter 4. Toolkit developer's reference

Register Chef Host

Unregister Chef Host

Install Software Modules

Register Chef Host

Unregister Chef Host

Copyright IBM Corp. 2013, 2014

Install Software Modules

General system services

IBM Cloud Orchestrator: Content Pack for Opscode Chef

Chapter 5. Samples about how to use the available services

Copyright IBM Corp. 2013, 2014

IBM Cloud Orchestrator: Content Pack for Opscode Chef