Cisco UCS Director Integration

Solution Guide
September 2015

SimpliVity Confidential & Proprietary

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
SimpliVity Confidential & Proprietary 2
This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
1 Introduction: SimpliVity OmniStack
Hyperconverged Infrastructure radically simplifies IT by consolidating all infrastructure and data services below the hypervisor
into a single unified stack running on x86 building blocks. SimpliVity hyperconverged infrastructure is delivered at a fraction of
cost and with extreme reduction in complexity over legacy IT stacks.

SimpliVity partners with Cisco to create hyperconverged infrastructure leveraging Cisco UCSthe industrys fastest growing
x86 server platform. SimpliVitys OmniStack Integrated Solution with Cisco UCS assimilates eight to twelve core data center
functions on Cisco UCS C240 rack-mount servers, including the hypervisor, compute, storage, network switching, backup,
replication, cloud gateway, caching, WAN optimization, real-time deduplication and more. SimpliVitys OmniStack Integrated
Solution with Cisco UCS includes three fundamental elements:

1. OmniStack, the foundational software, delivers the critical enterprise capabilities: performance, data efficiency,
data protection, and global unified management.
2. The OmniStack Accelerator Card: a PCIe card with an FPGA and NVRAM, protected with super capacitors. It
provides data processing at near-wire speeds, delivering enterprise-class performance and reduced latency by
deduplicating, compressing and optimizing all data inline, at inception, once and forever.
3. Cisco UCS C240 rack-mount servers.

The OmniStack Data Virtualization Platform is SimpliVitys critical enabling technology that ultimately produces the
Hyperconvergence solution delivered to customers in the form of the OmniStack-powered Cisco UCS.

OmniStack Accelerator Card

The core technology that performs inline data deduplication, compression, and optimization on all data, at inception, across all
phases of the data lifecycle (primary, backup, WAN, archive, and on the cloud), across all tiers within a system (DRAM,
Flash/SSD, and HDD).

SimpliVity is able to provide all of the benefits of deduplication, without sacrificing performance. In order to deduplicate,
compress and optimize data before it ever hits the disk, SimpliVity developed the OmniStack Accelerator Card, a PCIe
card with an FPGA and NVRAM, protected with super capacitors. This architecture allows data processing at near-wire
speeds, delivering enterprise-class performance and reducing latency. Not only does this save capacity and prevent
administrators from over-provisioning hardware, it also increases performance.

SimpliVity Confidential & Proprietary

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
As duplicate writes come into the system, they never touch a hard disk. The Accelerator Card deduplicates the writes,
acknowledges the writes in real time back to the application, and updates the metadata table. The hard disk is never
touched.
There is no longer a need to have separate devices for WAN optimization, backup deduplication, or cloud gateways.

Integration with UCS Director

SimpliVity is developing a module for UCS Director that will provide Cisco customers the ability to manage their data
centers hosted on SimpliVity Hyperconverged Infrastructure. Leveraging this integration, customer virtual machines, Cisco
UCS server infrastructure and SimpliVity OmniStack Data Virtualization Platform features can all be managed through a
single interface. The main focus areas for the integration are highlighted below:

1) Providing a single tool to manage entire Virtual Data center hosted on Cisco and SimpliVity infrastructure.

2) Exposing SimpliVitys unique Data Virtualization platform management through UCS Director to provide VM-
centric operations including data mobility available through UCS Director.

3) Implementing SimpliVity automation tasks that can be combined with others available within UCS Director for
Virtual Machine level automated IT workflows.

4) Demonstration of Self-Service portal showing multi-tenancy and creation of an application level workflow.

5) Showcasing the power of SimpliVity with UCS Director for orchestration with example workflows for test and
development (test/dev) and remote office / branch office (ROBO) management that also incorporates the self-
service and multi- tenancy capabilities.

Solution Components Hardware and Software

The following hardware and software was tested with the SimpliVity UCS Director Module.

Software Version
Cisco UCS Director 5.3.0.0
Cisco UCS Manager v2.2(4b)
SimpliVity OmniStack 2.1.11.806
VMware vSphere 5.5 U2
Hardware
(4) Cisco UCS C240 M4SX
(4) SimpliVity OmniStack Accelerator Card

SimpliVity Confidential & Proprietary 4

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
Sample Solution Environment

2 The SimpliVity UCS Director Plugin

The SimpliVity Cisco UCS Director Plugin allows you to perform the same management tasks as the OmniCube CLI
interface from within the Converged Infrastructure and Physical Accounts modules within Cisco UCS Director. It also
allows you to orchestrate workflows and create self-service portal catalog items for privileged accounts to execute within
UCS Director.

For more information about the installation and initial configuration of UCS Director please see the Cisco UCS Director
Install and Upgrade Guides found here (http://www.cisco.com/c/en/us/support/servers-unified-computing/ucs-
director/products-installation-guides-list.html).

This section goes through the steps for deploying the SimpliVity UCS Director plugin.

Prerequisites for installing the SimpliVity UCS Director Plugin:

OmniCube Virtual Controller for each OmniCube deployed and to be managed via Cisco UCS Director
Cisco UCS Director version 5.3.0.0 deployed in the production environment
The SimpliVity OmniStack UCS Director plugin downloaded and available to deploy into Cisco UCS Director

Installing the SimpliVity UCS Director Plugin

1. Launch Cisco UCS Director and login as the admin user default username and password is admin/admin
2. Navigate to the Administration, Open Automation and click Add Module.
3. Select a file for upload and select the SimpliVity UCS Director plugin
4. Click Upload and then Click Submit
5. The SimpliVity OmniStack module will appear in the list of active modules (Figure 1)

SimpliVity Confidential & Proprietary

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
Figure 1 Cisco UCS Director Administration Open Automation SimpliVity Module Installed

SimpliVity Confidential & Proprietary 6

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
Adding OmniStack Accounts to Cisco UCS Director
1. Navigate to Administration, Physical Accounts and click Add
2. Choose the Pod you which to deploy the OmniStack (DefaultPod is preselected)
3. Choose Category Storage
4. Choose Account Type SimpliVity OmniStack and click Submit
5. Enter your Federation Name in the Account Name field
6. Add OmniStack Credentials to the Add Account form and click Submit
7. The SimpliVity OmniStack will appear in the Physical Accounts list and Connection Status should have a green
dot with Success if all credentials were entered correctly and UCS Director is connected. (Figure 2)

Figure 2 Cisco UCS Director Administration Physical Accounts OmniStack Registered

SimpliVity Confidential & Proprietary

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
3 Using the SimpliVity UCS Director Plugin
Once enabled, the SimpliVity UCS Director Plugin allows you to execute and review SimpliVity management tasks (Figure
3). The Physical accounts storage module provides more details on the OmniStack infrastructure configuration (Figure 4).

Figure 3 Cisco UCS Director Converged Infrastructure SimpliVity OmniStack Summary

Figure 4 Cisco UCS Director Physical SimpliVity Summary Tabs

SimpliVity Confidential & Proprietary 8

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
Managing Hyperconverged Infrastructure with UCS Director
UCS Director provides access to the Virtual, Compute, Network, and Storage resources from a single pane of glass
interface. The SimpliVity OmniStack plugin enables the Omnistack Federation under the Converged Storage tab (Figure
5).

Figure 5 Cisco UCS Director Converged - Storage SimpliVity

Clicking on the SimpliVity Logo opens the OmniStack View and allows you to manage the OmniStack Systems,
Datastores, Virtual Machines, Backups, and Backup Policies (Figure 6). You can also capture support information from
the OmniStack to send to SimpliVity Customer Support. The OmniStack Summary tab shows widgets with info about the
SimpliVity Nodes, Virtual Machines, Datastores, etc.

Figure 6 Cisco UCS Director Converged - Storage SimpliVity OmniStack Summary

The Omnistack Systems tab allows you to view more detailed information about the nodes; the datacenters,
Host/Mgmt/Federation/Storage IP addresses, version and status information (Figure 7).

SimpliVity Confidential & Proprietary

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
Figure 7 Cisco UCS Director Converged - Storage SimpliVity OmniStack Systems

The OmniStack Systems tab also provides a Support Capture task. This uses the svt-support-capture command to create
a support capture. If you do not specify any arguments, the command creates a complete support capture which might
take several minutes to complete and might be hundreds of megabytes to several gigabytes in size. Options include
Bzip2 compression and include vCenter information. Warning: Run this command under guidance of your technical
support provider.

The Datastores tab lists all existing VMware datastores, the datacenter, SimpliVity backup policy, size, created timestamp,
and access nodes (Figure 8). Before clicking any datastores, the Create task is available to add a new datastore to the
OmniStack.

Figure 8 Cisco UCS Director Converged - Storage SimpliVity Datastores

Clicking on a datastore in the list opens up all relevant tasks including Create, Delete, Set Policy, Resize, Share, and
Unshare.

SimpliVity Confidential & Proprietary 10

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
Creating Datastores on OmniStack
The Create task leverages the svt-datastore-create command from the SimpliVity CLI. The svt-datastore-create
command creates a datastore in the Federation and sets the backup policy for new VMs that you create in the datastore.
The example CLI command is svt-datastore-create --name name --policy name --size [nGB|nTB] --datacenter datacenter
[common-options]. The UCS Director plugin also passes the options via the GUI window form (Figure 9).

Figure 9 Cisco UCS Director Converged - Storage SimpliVity Create Datastore

Deleting Datastores on OmniStack

The Delete task leverages the svt-datastore-delete command from the SimpliVity CLI. The svt-datastore-delete command
deletes a datastore from the Federation. Note: You cannot delete a datastore if it contains active VMs or backups of
deleted VMs. The example CLI command is svt-datastore-delete --name name [common-options]. The UCS Director
plugin verifies that you want to permanently delete the datastore before continuing (Figure 10).

11

SimpliVity Confidential & Proprietary

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
Figure 10 Cisco UCS Director Converged - Storage SimpliVity Delete Datastore

Setting Backup Policy on Datastores in OmniStack

The Set Policy task leverages the svt-datastore-policy-set command from the SimpliVity CLI. The svt-datastore-policy-
set command changes the default backup policy for a datastore. The new default policy applies only to any new VMs that
you create after the policy change. Existing VMs continue to use the policy that was in force at their time of creation or the
policy that you subsequently assigned to that VM. The example CLI command is svt-datastore-policy-set --datastore
name --policy name [common-options]. The UCS Director plugin shows a dropdown box with the available backup
policies for selection (Figure 11).

Figure 11 Cisco UCS Director Converged - Storage SimpliVity Set Policy to Datastore

Resize Datastores on OmniStack

The Resize Datastore task leverages the svt-datastore-resize command from the SimpliVity CLI. The svt-datastore-resize
command enables you to increase or decrease the capacity of a datastore by specifying a new size in GB, TB or PB.
When decreasing the size of a datastore, you cannot specify a size that is smaller than the space currently allocated to
VMs in the datastore. The minimum size is 1GB. The UCS Director plugin shows a form box to enter the new datastore
size (Figure 12).

SimpliVity Confidential & Proprietary 12

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
Figure 12 Cisco UCS Director Storage SimpliVity Resize Datastore

Share/Unshare Datastores on OmniStack

The Share and Unshare Datastore tasks leverage the svt-datastore-resize command from the SimpliVity CLI. The svt-
datastore-share command enables you to allow access to Federation datastores from Non-SimpliVity ESXi hosts. This
TM TM
enables you to use vMotion and Storage vMotion and to enable VMs running on an ESXi host to access a datastore in
a Federation, with no disruption to users. The VM remains running on the original ESXi host. Before sharing a datastore,
you must configure the NFS and network settings in the Non-SimpliVity ESXi host and configure the /etc/hosts file on
Non-SimpliVity ESXi hosts. See the OmniCube for vSphere Client Help for information about the required settings. The
example CLI command is svt-datastore-share --host non-simplivity-name|IP --datastore datastore-name [common-
options]. The svt-datastore-unshare command stops sharing Federation datastores with a Non-SimpliVity ESXi host. The
example CLI command is svt-datastore-unshare --host non-simplivity-name|IP --datastore datastore-name [common-
options]

The UCS Director plugin shows a form box to enter the IP address of the host to share/unshare the selected datastore
(Figure 13 & Figure 14).

Figure 13 Cisco UCS Director Converged - Storage SimpliVity Share Datastore

13

SimpliVity Confidential & Proprietary

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
Figure 14 Cisco UCS Director Converged - Storage SimpliVity Unshare Datastore

Virtual Machines Tab on OmniStack UCS Director Plugin

Selecting a virtual machine opens up the available tasks on the menu bar in the UCS Director Virtual Machine tab. The
available tasks are Backup, Clone, Move, Restore and Set Policy (Figure 15).

Figure 15 Cisco UCS Director Converged - Storage SimpliVity Virtual Machines Tab

Backup Virtual Machine

The Backup Virtual Machine task leverages the svt-vm-backup command from the SimpliVity CLI. The svt-vm-backup
command creates a manual backup of a virtual machine (VM) at the current time. A backup saves the state of the VM at
the time you created the backup.

Unlike a policy backup, a manual backup is not deleted during the automatic cleanup performed by a backup policy. You
must manually delete these backups to make sure that they do not consume excessive system resources.

SimpliVity Confidential & Proprietary 14

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
The default operation is to take an instantaneous copy without using VMware operations. Manual backup options include:

Application consistentInclude a VMware application consistent snapshot in the backup. This type of backup brings
guest VM applications to a consistent state before taking a backup. Using application consistency increases the time
required to complete a backup, and you should not use it for guest VMs that have high I/O.

Remote datacenterSpecify a remote destination for the backup.

NameBy default, the command creates a unique name for the backup by appending a timestamp to the VM name.
You can override the default by specifying a unique name for the backup. You can also rename backups at any time.

The example CLI command is svt-vm-backup --datastore datastore-name --vm vm-name --name backup-name --
appconsistent --destination datacenter-name [common-options]

Once a virtual machine is selected and the Backup task clicked, the UCS Director plugin shows a form box to enter the
optional backup name, option to select application consistency and the destination datacenter (Figure 16).

Figure 16 Cisco UCS Director Converged - Storage SimpliVity Virtual Machines Backup

Clone Virtual Machine

The Clone Virtual Machine task leverages the svt-vm-backup command from the SimpliVity CLI. The svt-vm-clone
command creates a new virtual machine (VM) that contains the same contents as an existing VM. The new VM has a
different name, but resides in the same datastore as the original VM. Characteristics of the cloned VM are:

Clone nameBy default, the command appends the string -clone-<timestamp> to the original VM name. You can
override this by specifying the --name option.

The example CLI command is svt-vm-clone --datastore datastore --vm vm --name new-name --appconsistent [common-
options]

Once a virtual machine is selected and the Clone task clicked, the UCS Director plugin shows a form box to enter the
clone name and option to select application consistency (Figure 17).

15

SimpliVity Confidential & Proprietary

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
Figure 17 Cisco UCS Director Converged - Storage SimpliVity Virtual Machines Clone

Move Virtual Machine

The Move Virtual Machine task leverages the svt-vm-move command from the SimpliVity CLI. The svt-vm-move
command enables you to relocate a VM to a Federation datastore in a different datacenter or a different datastore
contained in the same datacenter. By default, the command uses the original VM name as the name for the moved VM
(Figure 18). You can override the default by specifying a unique name for the moved VM. You can move a VM to and from
a remote datacenter. The example CLI command is svt-vm-move --source datastore --vm vm --datacenter datacenter --
destination datastore --name vm-name [common-options]

Figure 18 Cisco UCS Director Converged - Storage SimpliVity Virtual Machines Move

SimpliVity Confidential & Proprietary 16

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
Restore Backup
The Restore Backup task leverages the svt-backup-restore command from the SimpliVity CLI. In the Virtual Machines
tab of Cisco UCS Director, select the backup that you want to restore and click the restore task in the menu bar. A
dialogue box will open with a drop down with backup to select from existing backups (Figure 19). This restores the
backup over the existing virtual machine. The example CLI command is svt-backup-restore --datastore datastore --vm vm
--backup backup --source datacenter --destination datacenter --home datastore --name vm [ common-options].

Figure 19 Cisco UCS Director Converged - Storage SimpliVity Backups Restore Task

17

SimpliVity Confidential & Proprietary

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
Set Virtual Machine Backup Policy
The Set VM Backup Policy task leverages the svt-vm-policy-set command from the SimpliVity CLI. The svt-vm-policy-
set command sets the backup policy for a virtual machine (VM). A backup policy enables you to schedule VM backup
operations and control the frequency and number of backups retained. By default, each VM inherits the backup policy
assigned to the datastore in which the VM resides (Figure 20). If you change the VM's backup policy to a different policy
from the datastore default, any changes to the datastore default policy are ignored by the VM. The example CLI
command is svt-vm-policy-set --datastore datastore_name --vm vm_name --policy policy_name [common-options].

Figure 20 Cisco UCS Director Converged - Storage SimpliVity Virtual Machines Set Policy

Backups Tab on OmniStack UCS Director Plugin

The Backups tab provides a list of all of the virtual machine backups in OmniStack. Once a backup is selected, the tasks
appear for deleting, locking, renaming, restoring, canceling and copying a backup from within UCS Director (Figure 21).

Figure 21 Cisco UCS Director Converged - Storage SimpliVity Backups Tab

SimpliVity Confidential & Proprietary 18

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
Delete Backup
The Delete Backup task leverages the svt-backup-delete command from the SimpliVity CLI. The svt-backup-delete
command deletes one or more backups of a virtual machine (VM). In Cisco UCS Director, select the backup that you
want to delete and click the delete task in the menu bar. A dialogue box will open asking to confirm the deletion of the
backup (Figure 22). The example CLI command is svt-backup-delete --datastore datastore --datacenter datacenter --
datacenter-id datacenter_id --datastore-id datastore_id --vm vm --vm-id vm_id --backup backup [common-options].

Figure 22 Cisco UCS Director Converged - Storage SimpliVity Backups Delete Task

Lock Backup
The Lock Backup task leverages the svt-backup-lock command from the SimpliVity CLI. The svt-backup-lock command
preserves automatic (policy) VM backups, preventing them from deletion. In Cisco UCS Director, select the backup that
you want to lock and click the lock task in the menu bar. A dialogue box will open asking to confirm the lock of the backup
(Figure 23). The example CLI command is svt-backup-lock --datastore datastore --vm vm --backup backup [common-
options].

Figure 23 Cisco UCS Director Converged - Storage SimpliVity Backups Lock Task

19

SimpliVity Confidential & Proprietary

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
Rename Backup
The Rename Backup task leverages the svt-backup-rename command from the SimpliVity CLI. The svt-backup-rename
command renames and existing VM Backup. In Cisco UCS Director, select the backup that you want to rename and click
the rename task in the menu bar. A dialogue box will open asking for the new backup name (Figure 24). The example
CLI command is svt-backup-rename --datastore datastore --vm vm --backup backup --name new-name [common-
options].

Figure 24 Cisco UCS Director Converged - Storage SimpliVity Backups Rename Task

Restore Backup
The Restore Backup task leverages the svt-backup-restore command from the SimpliVity CLI. The svt-backup-restore
command restores a VM backup to a new VM at any accessible datacenter and datastore. You can use this command to
create a new VM, preserving the original VM. In Cisco UCS Director, select the backup that you want to restore and click
the restore task in the menu bar. A dialogue box will open asking for the new VM name and datastore (Figure 25). The
example CLI command is svt-backup-restore --datastore datastore --vm vm --backup backup --source datacenter --
destination datacenter --home datastore --name vm [ common-options].

Figure 25 Cisco UCS Director Converged - Storage SimpliVity Backups Restore Task

SimpliVity Confidential & Proprietary 20

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
Cancel Backup
The Cancel Backup task leverages the svt-backup-cancel command from the SimpliVity CLI. The svt-backup-cancel
command cancels a virtual machine backup that is in-progress. In Cisco UCS Director, select the backup that you want to
cancel and click the cancel task in the menu bar. A dialogue box will open asking to confirm the cancel backup (Figure
26). The example CLI command is svt-backup-cancel --datastore datastore --vm vm --backup backup --datacenter
datacenter [common-options].

Figure 26 Cisco UCS Director Converged - Storage SimpliVity Backups Cancel Task

Copy Backup
The Copy Backup task leverages the svt-backup-copy command from the SimpliVity CLI. The svt-backup-copy
command copies VM backups to remote datacenters. Use this command to create a copy of a backup. In Cisco UCS
Director, select the backup that you want to copy and click the copy task in the menu bar. A dialogue box will open asking
to select the destination datacenter (Figure 27). The example CLI command is svt-backup-copy --datastore datastore --
vm vm --backup backup --source datacenter --destination datacenter [common-options].

Figure 27 Cisco UCS Director Converged - Storage SimpliVity Backups Copy Task
21

SimpliVity Confidential & Proprietary

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
Policies Tab on OmniStack UCS Director Plugin
The Policies tab provides a list of all of the virtual machine policies in OmniStack. Once a policy is selected, the create,
delete, rename, create and delete rule tasks appear on the menu bar (Figure 28).

Figure 28 Cisco UCS Director Converged - Storage SimpliVity Backup Policies

Create Backup Policy

The Create Backup Policy task leverages the svt-policy-create command from the SimpliVity CLI. The svt-policy-create
command creates a backup policy in a Federation. For each datastore in a Federation, you set a default backup policy
that applies to new virtual machines (VMs) created in the datastore. You can also set a specific backup policy for an
individual Federation VM. In Cisco UCS Director, select the create policy task in the menu bar. A dialogue box will open
asking for the new policy name (Figure 29). The example CLI command is svt-policy-create --name policy_name
[common-options].

Figure 29 Cisco UCS Director Converged - Storage SimpliVity Backup Policies Create Policy Task

SimpliVity Confidential & Proprietary 22

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
Delete Backup Policy
The Delete Backup Policy task leverages the svt-policy-delete command from the SimpliVity CLI. The svt-policy-delete
command deletes a backup policy in a Federation. In Cisco UCS Director, select the policy you wish to delete and then
click the delete policy task in the menu bar. Note: You cannot delete a backup policy if it is assigned to a datastore or a
VM. A dialogue box will open asking to confirm the policy deletion (Figure 30). The example CLI command is svt-policy-
delete --name policy_name [common-options].

Figure 30 Cisco UCS Director Converged - Storage SimpliVity Backup Policies Delete Policy Task

Rename Backup Policy

The Rename Backup Policy task leverages the svt-policy-rename command from the SimpliVity CLI. The svt-policy-
rename command renames an existing backup policy in a Federation. In Cisco UCS Director, select the policy you wish
to rename and then click the rename policy task in the menu bar. A dialogue box will open asking for the new policy
name (Figure 31). The example CLI command is svt-policy-rename --policy original_name --name new_name [common-
options].

Figure 31 Cisco UCS Director Converged - Storage SimpliVity Backup Policies Rename Policy Task
23

SimpliVity Confidential & Proprietary

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
Create Rule in Backup Policy
The Create Rule in Backup Policy task leverages the svt-policy-rule-create command from the SimpliVity CLI. The svt-
policy-rule-create command creates a rule for a backup policy in a Federation. In Cisco UCS Director, select the policy
you wish to create the rule for and then click the create rule task in the menu bar. A dialogue box will open asking for the
backup frequency, the maximum backups to retain, and the destination datacenter (Figure 32). The example CLI
command is svt-policy-rule-create- --policy policy --destination destination --frequency frequency --start_time start-time --
end_time end-time --days days --max_backups max-backups --appconsistent [common-options].

Figure 32 Cisco UCS Director Converged - Storage SimpliVity Backup Policies Create Rule Task

Delete Rule in Backup Policy

The Delete Rule in Backup Policy task leverages the svt-policy-rule-delete command from the SimpliVity CLI. The svt-
policy-rule-delete command deletes a rule for a backup policy in a Federation. In Cisco UCS Director, select the policy
you wish to delete the rule for and then click the delete rule task in the menu bar. A dialogue box will open with a
dropdown box of all available rules for that backup policy (Figure 33). Select the rule and submit to delete the rule. The
example CLI command is svt-policy-rule-delete --policy name --rule n [common-options].

Figure 33 Cisco UCS Director Converged - Storage SimpliVity Backup Policies Delete Rule Task

SimpliVity Confidential & Proprietary 24

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
4 Using the SimpliVity Orchestration Tasks
UCS Director provides an orchestration engine for stringing tasks together in a workflow (Figure 34) that can be executed
by an administrator or made available in a self-service portal as a catalog item for other privileged users to open as a
service request. Each of the SimpliVity tasks from the converged infrastructure module can be orchestrated and are listed
in the UCS Director Task Library (Figure 35). Each task is defined with required and optional inputs and outputs in the
UCS Director Task Library and can be referenced when creating workflows within Workflow Designer (Figure 36).

Figure 34 Cisco UCS Director Policies - Orchestration SimpliVity Test/Dev Example Workflow

Figure 35 Cisco UCS Director Policies - Orchestration SimpliVity Orchestration Tasks

25

SimpliVity Confidential & Proprietary

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
Figure 36 Cisco UCS Director Policies - Orchestration SimpliVity Orchestration Tasks Virtual Machine
Backup Example

Figure 37 Cisco UCS Director Policies - Orchestration SimpliVity ROBO Gold Backup Example

SimpliVity Confidential & Proprietary 26

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
Figure 38 Cisco UCS Director Policies - Orchestration SimpliVity ROBO Restore Example

5 Using the SimpliVity Self Service Portal

UCS Director provides a self service portal for privileged users to execute workflows as catalog items. In this example,
there are several SimpliVity workflows that have been added to the catalog and published for remote branch office users
to create and restore backups of virtual machines (Figure 39). When a service request is executed, the variables required
from the end user will be displayed in a text box and passed as input variables to the UCS Director workflow. The end
user can view the workflow status by opening up the service request in the UCS Director self service portal (Figure 40).

Figure 39 Cisco UCS Director Self Service Portal SimpliVity ROBO Catalog Items

27

SimpliVity Confidential & Proprietary

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.
Figure 40 Cisco UCS Director Self Service Portal SimpliVity Service Request Status

More information regarding the operation of the self service portal can be found on the Cisco Self-Service Portal Guide.
(http://www.cisco.com/c/en/us/support/servers-unified-computing/ucs-director/products-user-guide-list.html)

6 Solution Summary
The SimpliVity OmniStack Integrated Solution with Cisco UCS simplifies IT operations with automation and orchestration
of all IT infrastructure and services below the hypervisor including compute, network, storage, and built-in data protection.
SimpliVitys integration with UCS Director effectively eliminates the complexity around provisioning applications and
speeds time to delivery with automated VM-centric workflows. To learn more, read the OmniStack with Cisco UCS
Reference Architecture and view OmniStack Integrated Solution with Cisco UCS on Cisco Marketplace.

SimpliVity Confidential & Proprietary 28

This document contains proprietary information subject to a non-disclosure agreement and is not to be released without
prior written authorization of SimpliVity Corporation.