Shared services workloads in IBM pureapplication system

In this article, the author describes some of the basic concepts of shared services, describing the sample shared services plug-in in the plug-in Development Kit (PDK), which provides a good starting point for creating a new shared service. The author will also describe how to convert the sample shared services to functional general media sharing services, a generic service repository in which client deployments can obtain common files.

Shared Services is a predefined pattern that is deployed in the cloud and deployed by multiple client applications in the cloud, such as virtual applications, http://www.aliyun.com/zixun/aggregation/12423.html > Virtual systems and virtual devices) sharing. Shared Services provides some run-time services to multiple applications or services to end users on behalf of multiple applications.

You typically only find a shared service reference in each cloud group (a typical hardware grouping that defines the cloud), and shared services are available to all applications deployed in the cloud group. This means that shared services must provide multiple tenant access capabilities.

Figure 1. Shared Services is a predefined pattern that is deployed and shared by multiple application deployments

For the purposes of this article, we define shared services as a deployment that can be used by other virtual applications (client deployments). One or more client deployments can connect to a single shared services deployment to access a common data repository.

This article describes the steps for importing and customizing a sample shared service from the plug-in Development Kit (PDK), which is known as a sample shared service or a media service.

The concept of media sharing service

A virtual application deployment often requires the installation of some form of preparatory binary, such as a binary file or an ISO DVD image on a build server. There may be reasons for not using Application Mode or component Plug-ins to encapsulate these binaries, such as licensing, code distribution issues, or binaries that may need to be updated independently of application mode.

In a cloud environment, multiple application deployments may need to refer to the same media file. Downloading files to each deployed virtual application may take a long time if the required files are located on a slower (perhaps remote) network outside the cloud.

To address these issues, we recommend creating a new media sharing service that has a binary file repository for any virtual applications in the Cloud group. The media service can deploy and load the preliminary files independently of the virtual applications and plug-ins.

Instead of copying files from somewhere outside the cloud every time you start deploying new applications, you can copy files to the Media service virtual machine (VM) once and place them locally in the cloud. This allows administrators to manage this service in a more centralized design, rather than through independent VMs that do not share any common framework.

Files can be replicated much faster from media services to virtual applications because this is done entirely within the rack (representing Pureapplication System) and the cloud group, enabling multiple deployments to quickly access data.

The following example is a typical stream of media services:

deployment of Shared services/media services. The media service VM launches and loads the binaries to be shared through NFS on the cloud group. Deploy a virtual application that uses the media service (component tags or policies in the pattern). The virtual application requests binary file location and/or connection information to the media service. Virtual applications can mount file repositories from media service VMS through NFS. Repeat the process for multiple virtual application deployments. Each deployment will gain the ability to access shared files through the media service.

We will first look at the sample shared services provided in the plug-in development kit, work with you to analyze the provided elements, and then import the shared services into the IBM Pureapplication System or IBM Workload Deployer products that will be deployed to the cloud. This provides you with general information for adding general shared services.

Then we'll show you how to modify the sample shared services plug-in to make it a media sharing service that shows you how you can easily add new shared services. After this section is the steps and code snippets for completing this task, you can easily use the resources provided to create your own media share services and future custom shared services.

Building and installing PDK, services, and client virtual applications

The sample shared services provided in PDK v1.0.0.4 can serve as a good custom framework. It sets the desired file structure and defines code scripts for the following:

a sample shared service with the REST API management interface. A client virtual application component that uses the sample shared services that invoke the REST API management interface.

First import the sample code, and then continue to add custom functionality.

Download PDK v1.0.0.4. The minimum requirements for deploying Plug-ins are IBM workload Deployer 3.1.0.2 or IBM pureapplication System v1.0.

Some things to keep in mind:

Ensure that you import all projects that contain shared services and shared services clients. Go to the Plug-in.depends project and run Build.xml with ANT. Perform cleanup and publishing targets in this order. This builds all plug-in projects that contain shared services and shared services clients. Go to Patterntype.hello and run Build.patterntype.xml with ANT. Perform cleanup and publish targets in that order. This encapsulates the output from plug-in.depends into a pattern to be imported.

Now let's install the mode type in workload Deployer or Pureapplication System.