Cisco Intelligent Automation for Cloud
User Guide
Release 4.0
Published: January 25, 2014
Cisco Systems, Inc.
www.cisco.com
Cisco has more than 200 offices worldwide.
Addresses, phone numbers, and fax numbers
are listed on the Cisco website at
www.cisco.com/go/offices.
Text Part Number: OL-29974-01
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public
domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this
URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display
output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in
illustrative content is unintentional and coincidental.
Cisco Intelligent Automation for Cloud 4.0 User Guide
© 2014 Cisco Systems, Inc. All rights reserved.
CONTENTS
Preface
vii
Audience
vii
Related Documentation
vii
Obtaining Documentation and Submitting a Service Request
CHAPTER
1
Introduction
vii
1-1
Understanding the Cisco IAC 4.0 User Interface (UI) 1-1
Modules 1-1
Accessing Modules 1-1
Cisco IAC Service Portal Menu Bar 1-1
Portals, Portal Pages, and Portlets 1-2
Working with Portals and Portlets 1-2
Portal Purpose and Location 1-3
Portal Pages List with Descriptions 1-3
Understanding the System Settings Tabs and Their Contents
Accessing the Order Services Portal 1-8
1-5
Managing Your Site Homepage 1-9
Changing Your Default Home Page 1-10
Activating or Inactivating a Portal Page 1-10
Enabling Reserved Portlet Buttons 1-10
Removing a Reserved Portlet 1-11
Re-Enabling Reserved Portlet 1-12
Service Manager 1-12
Organization Designer 1-12
Service Item Manager 1-12
Administration 1-13
Profile Settings and Preferences 1-13
Customizing Table Views 1-13
Re-sorting Table Rows by Column 1-13
Adding or Removing Columns 1-13
CHAPTER
2
Network Services Overview
2-1
Understanding Network Services
Bundled Technologies 2-1
2-1
Cisco Intelligent Automation for Cloud 4.0 User Guide
OL-29974-01
i
Contents
Network Architecture 2-2
Supported Virtual Appliances
2-2
Network Discovery Flow 2-3
Platform Elements and POD Relationships
2-4
Use Case by Persona 2-4
Cloud Provider Technical Administrator (CPTA) 2-4
Connections and Discovery 2-4
System Settings and Behavior 2-5
Greenfield/Brownfield Support 2-5
Tenant Management 2-5
Ongoing Management 2-5
Cloud Provider Business Administrator (CPBA) 2-5
Service Management 2-5
Tenant Management 2-5
Tenant Technical Administrator (TTA) 2-6
Organization Technical Administrator (OTA) 2-6
Server Owner / Application Architect 2-6
Understanding Server and Service Groups 2-7
Server Groups 2-7
Service Groups 2-7
Load Balancer Service Groups 2-8
Firewall Service Groups 2-9
Network Topologies 2-9
Cisco IAC 4.0 / VSA 1.0 2-9
Cisco IAC 4.0 / VMDC 2.3 2-10
VDC Topology 2-10
Points of Delivery (PODs) 2-10
Compute POD 2-10
Network POD 2-11
Network and Compute POD
CHAPTER
3
Managing PODs
2-12
3-1
Working with Network PODs 3-1
Creating One or More PODs 3-1
Modifying Network POD Properties
Removing a Network POD 3-2
3-2
Working with Compute PODs 3-3
Registering a Compute POD 3-3
Modifying a Compute POD’s Properties
3-3
Cisco Intelligent Automation for Cloud 4.0 User Guide
ii
OL-29974-01
Contents
Removing a Compute POD
3-4
Working with Resource Containers 3-4
Creating a Service Resource Container 3-4
Modifying Service Resource Container Properties
Deleting a Service Resource Container 3-6
CHAPTER
4
Managing Services
3-5
4-1
Viewing Service Requisitions
4-1
Configuring and Enabling Approvals 4-2
Managing Approval Requests 4-3
Using the Approvals Portlet 4-3
Approval Queues 4-3
Managing Server Leases 4-3
Notifying a User of Approaching Lease Expiration
Viewing Server Lease Information 4-4
Extending or Removing a Server Lease 4-4
4-4
Managing Infrastructure 4-5
Maintaining Your Servers 4-5
Infrastructure Ownership Reassignment 4-6
Using the Manage Infrastructure Portal 4-7
Checking System Health 4-8
Turning Automatic Health Check On or Off (Global) 4-8
Viewing System Health 4-8
Handling Infrastructure Errors 4-12
Assigning the Remediation Task for Repair 4-12
Remediating a Service 4-13
Checking the Status of an Order 4-15
Cancelling the Order if Remediation Attempt is Unsuccessful
CHAPTER
5
Managing Resources Using Discovery
4-15
5-1
Discovering Network Devices 5-1
Running Discovery 5-2
Connecting or Updating Cloud Infrastructure 5-5
Assigning Registered Devices to a Network POD 5-6
Managing Resources 5-7
Viewing System Resource Capacity
5-7
Managing Cloud Infrastructure Discovery 5-8
Discovering Objects in the Cloud Infrastructure 5-8
Viewing Discovered Objects in the Infrastructure 5-9
Cisco Intelligent Automation for Cloud 4.0 User Guide
OL-29974-01
iii
Contents
Validating Platform Configuration 5-10
Validating Cloud Infrastructure 5-10
Validating an Individual Platform Element 5-10
Validating All of the Platform Elements Together
5-11
Validating Cisco Process Orchestrator and Share Location Settings
Validating the E-mail Server Connection 5-12
Managing Authorization and Review Escalation
Enabling an Authorization or Review 5-12
Setting Up Escalation Sequences 5-13
CHAPTER
6
5-11
5-12
Managing Physical Servers, Virtual Machines, and Virtual Device Centers
Working with Physical Servers 6-1
Commissioning a Physical Server
6-1
6-1
Managing Power Settings for Physical Servers
Powering Down a Physical Server 6-2
Power-cycling a Physical Server 6-3
Powering Up a Physical Server 6-3
Decommissioning a Physical Server 6-4
6-2
Working With Virtual Machines 6-4
Commissioning a Virtual Machine 6-4
Using EC2 Windows VMs Without Keypairs 6-6
Decommissioning a Virtual Machine 6-7
Installing an Operating System 6-8
Viewing Server Status and Properties 6-9
Changing the Server Size of a Virtual Machine 6-11
Powering Down a Virtual Machine 6-11
Powering Up a Virtual Machine 6-11
Power-Cycling a Virtual Machine 6-12
Taking a Snapshot of a Virtual Machine 6-12
Reverting a Virtual Machine Settings to Snapshot 6-12
Viewing Snapshots 6-13
Deleting a Snapshot 6-13
Working with Virtual Data Centers 6-13
Creating a Virtual Data Center 6-14
Obtaining Approvals for Creating a Virtual Data Center
Decommissioning a Virtual Data Center 6-16
Calculating Virtual Data Center Size Requirements 6-16
Modifying Virtual Data Center Size 6-17
Viewing Virtual Data Center Details 6-18
6-15
Cisco Intelligent Automation for Cloud 4.0 User Guide
iv
OL-29974-01
Contents
Viewing Virtual Data Center Capacity Charts
CHAPTER
7
Managing Templates
6-19
7-1
Managing Operating System Templates 7-1
Registering an Operating System Template 7-1
Maintaining an Operating System Template 7-1
Ignoring an Operating System Template 7-2
Managing Server Templates 7-2
Registering a Virtual Machine Template 7-2
Registering an Operating System Template 7-3
Registering a UCS Service Profile Template 7-3
Ignoring a UCS Service Profile Template 7-4
Managing E-mail Templates 7-4
Configuring E-mail Notification Templates 7-4
Assigning From Address for E-mail Templates 7-5
Assigning Mail Addresses for Queue Notifications 7-6
Modifying E-mail Notification Templates 7-7
Setting Return E-mail Address 7-8
APPENDIX
A
Glossary of Terms
A-1
INDEX
Cisco Intelligent Automation for Cloud 4.0 User Guide
OL-29974-01
v
Contents
Cisco Intelligent Automation for Cloud 4.0 User Guide
vi
OL-29974-01
Preface
This guide describes how to administer Cisco Intelligent Automation for Cloud.
Audience
This guide is for administrators who are responsible for setting up, maintaining, and configuring
Intelligent Automation for Cloud. The tasks in this guide are typically performed by administrators only.
Related Documentation
See the Cisco Intelligent Automation for Cloud Documentation Overview for a list of all Intelligent
Automation for Cloud guides.
Note
We sometimes update the documentation after original publication. Therefore, you should also review
the documentation on Cisco.com for any updates.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional
information, see What’s New in Cisco Product Documentation at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.
Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco
technical documentation, as an RSS feed and deliver content directly to your desktop using a reader
application. The RSS feeds are a free service.
Cisco Intelligent Automation for Cloud 4.0 User Guide
OL-29974-01
vii
Cisco Intelligent Automation for Cloud 4.0 User Guide
viii
OL-29974-01
CH A P T E R
1
Introduction
Cisco Intelligent Automation for Cloud 4.0 (Cisco IAC) is a self-service provisioning and orchestration
software solution for cloud computing and data center automation. Cisco IAC users access services and
tasks using Prime Service Catalog, a browser-based interface that provides links to services and status,
such as ordering servers, viewing requisitions, monitoring system resources. Prime Service Catalog is a
browser-based set of applications where organizations and service teams log in to order and manage
services.
Understanding the Cisco IAC 4.0 User Interface (UI)
Modules
Modules are role-based containers of Prime Service Catalog services grouped by purpose. This section
describes Prime Service Catalog modules containing services that are covered in this guide.
Accessing Modules
The module drop-down list is located in the upper-right corner of the window. You use it to open any
module to which you have access.
Figure 1-1
The Module Drop-down List
Cisco IAC Service Portal Menu Bar
The Service Portal menu bar is reachable by selecting Service Portal from the modules drop down menu.
The chart below lists each portal along with its associated portal pages.
Cisco Intelligent Automation for Cloud 4.0 User Guide
OL-29974-01
1-1
Chapter 1
Introduction
Understanding the Cisco IAC 4.0 User Interface (UI)
Figure 1-2
Table 1-1
1
3
Service Portal Menu Bar
Service Portal Menu Items and Sub-Items
2
My Cloud
Setup
•
Home Page
•
Configuration Wizard
•
My Orders
•
System Settings
•
My Run Rate
•
Management Infrastructure
•
My Servers
•
VDC Calculator
•
My VDCs
•
Order Services
User Management
4
Operations
•
Tenant Management
•
Approvals
•
Price Rates
•
Error Remediation
•
Management Infrastructure
•
Network Management
•
System Health
•
System Resource Capacity
Portals, Portal Pages, and Portlets
Portal pages and portlets (subsets of certain portals) contain links to the order forms for services.
Working with Portals and Portlets
To add, modify, or remove portals or portlets, follow these steps.
Step 1
From the modules drop-down, select Portal Designer.
Step 2
You will see the Portal Designer Portal, shown in Figure 1-3 on page 1-3.
Cisco Intelligent Automation for Cloud 4.0 User Guide
1-2
OL-29974-01
Chapter 1
Introduction
Understanding the Cisco IAC 4.0 User Interface (UI)
Figure 1-3
Portal Designer Portal
Note
For complete information on how to use the functionality available on this portal, please see the Cisco
Service Portal Designer Guide.
Portal Purpose and Location
Each portal page is located within a module according to its purpose. Portals can serve three purposes:
•
Provide information—For example, the System Resources portal displays capacity information
about your cloud resources, including UCS blades and virtual data centers.
•
Link to forms—For example, the Tenant Management portal provides links to forms for adding or
removing users, viewing and modifying organization properties, removing organization networks,
and so on.
•
Provide both—For example, the My Servers portal displays tables with specifications and editable
properties of the servers under your control. It also allows you to perform several services on a
server, such as powering up or down, decommissioning, and reverting to snapshots (VMs only).
Portal Pages List with Descriptions
Cisco IAC provides the following portal pages. Access depends upon your role.
My Cloud
•
Home Page—Your customizable home page. See Managing Your Site Homepage, page 1-9.
•
My Orders—Displays the status of all your orders, whether ordered for yourself or on behalf of
another user. Depending on your user role, you may also be able to see orders for all the users in the
business units (Organizations) of which you are a member.
•
My Run Rate—View and perform actions related to your run rate.
•
My Servers—View and perform actions on your deployed servers, including powering up or down,
decommissioning, and snapshots. All users can access the My Servers portal page.
Cisco Intelligent Automation for Cloud 4.0 User Guide
OL-29974-01
1-3
Chapter 1
Introduction
Understanding the Cisco IAC 4.0 User Interface (UI)
•
Note
•
Note
My VDCs—Access to the list of VDCs, which contains the service links to Modify VDC Size,
Decommission VDC, Add a Network to VDC, Remove Network from VDC, Order a VM from
Template, Order a VM and Install an OS and Order a Physical Server.
It is not possible to add a VDC if the datacenter does not have a cluster. Cisco IAC does not
support data centers with 1 host (no cluster).
Order Services—View and perform actions related to ordering services.
Cisco IAC supports an individual’s membership to a single organizational unit or membership (not
multiple).
Setup
•
Configuration Wizard—Step-by-step Cisco IAC configuration tool for the configuration of Agent
Properties Configuration, Cloud Administration, Connect Cloud Infrastructure, POD Management,
Set System-wide Services and Provisioning Settings, and Create Shared Zone.
•
System Settings—Manage a variety of cloud resources, including data connections, server
templates, networks, UCS blades and blade pools. Only Cloud Provider Technical Administrators
can access the System Setup portal page.
•
Manage Infrastructure—Access to Discovery and Manage Cloud Infrastructures.
•
VDC Calculator—Calculate the Planned VM Distribution, Planned VM Configuration and
Suggested VDC Package from Planned VDC VM Limit.
•
Tenant Management—Onboard, offboard, and modify, or remove tenants in an organization.
•
Price Rates—View and perform actions related to price rates.
•
Approvals—Displays approvals assigned to you directly or to your queues, and enables you to see
approvals that precede or follow yours. Depending on your role, you may also be able to see
approvals for orders placed by user in your business units.
•
Error Remediation—Access to the Cloud Service Errors, which contains the service links to Error
Remediation services such as Cancel, Restart, Retry, Ignore and Rollback.
•
Manage Infrastructure—Access to Discovery and Manage Cloud Infrastructures.
•
Network Management—View and perform actions related to network management.
•
System Health—Access to the System Health details, which contains the service links to validate
the Platform Elements, validate Cisco Process Orchestrator and Validate E-mail Server.
•
System Resource Capacity—View capacity information for virtual clusters, UCS blades, and
chassis. Only Cloud Provider Technical Administrators can access the System Resources portal
page.
•
System Resource Usage—Displays the status of UCS Physical Blade Pool Management.
Management
Operations
Cisco Intelligent Automation for Cloud 4.0 User Guide
1-4
OL-29974-01
Chapter 1
Introduction
Understanding the Cisco IAC 4.0 User Interface (UI)
Understanding the System Settings Tabs and Their Contents
From Setup on the Service Portal menu, you can access a variety of key functionality via the System
Settings menu option. This section provides a brief overview of that area of Cisco Intelligent
Automation for Cloud 4.0.
•
Choose Service Portal > Setup > System Settings.
Figure 1-4
Note
System Setup at the Administrators Tab
Only Cloud Provider Technical Administrators can access these portlets.
Cisco Intelligent Automation for Cloud 4.0 User Guide
OL-29974-01
1-5
Chapter 1
Introduction
Understanding the Cisco IAC 4.0 User Interface (UI)
System Setup contains the following tabs and links:
Table 1-2
System Setup Tabs and Links
Portlet Name and Image
Available Tasks
Administrators
Modify Cloud Administration Organization
Add Cloud Administrator
Remove Cloud Administrator
Add Cloud Business Administrator
Remove Cloud Business Administrator
Connections
Connect Cloud Infrastructure
Update Cloud Infrastructure
View Cloud Connections
Manage Directory Server Connection
PODs
Register a Network POD
Modify Network POD Properties
Remove a Network POD
Register a Compute POD
Modify Compute POD Properties
Remove a Compute POD
Create a Service Resource Container
Modify Service Resource Container Properties
Delete a Service Resource Container
Cisco Intelligent Automation for Cloud 4.0 User Guide
1-6
OL-29974-01
Chapter 1
Introduction
Understanding the Cisco IAC 4.0 User Interface (UI)
Table 1-2
System Setup Tabs and Links (continued)
Portlet Name and Image
Available Tasks
System Settings
Set REX Agent Configuration
Set HTTP Agent Configuration
Set System-wide Service Options
Set Provisioning Settings
Set System E-mail Account
Modify E-mail Templates
Networks
Add a Network
Add Public Subnet to Network POD
Modify Network Properties
Remove a Network
Manage IP Address Exclusions
Standards
Define Order Standards
Use the Define Order Standards tables to modify
the sets of standard options users choose from
when ordering their cloud servers, virtual data
center network topologies, etc. This includes
virtual machine sizes (CPU, memory and storage),
lease term lengths, VDC sizes, network topologies
and more.
Cisco Intelligent Automation for Cloud 4.0 User Guide
OL-29974-01
1-7
Chapter 1
Introduction
Understanding the Cisco IAC 4.0 User Interface (UI)
Table 1-2
System Setup Tabs and Links (continued)
Portlet Name and Image
Available Tasks
Approvals
Configure Approvals
Use the Configure Approvals service to manage
which services require approvals by administrators
before being delivered.
About
Displays license data, copyright date, and other
information.
Accessing the Order Services Portal
Access the Order Services portal by selecting Service Portal > My Cloud > Order Services.
Figure 1-5
Order Services Portal
Cisco Intelligent Automation for Cloud 4.0 User Guide
1-8
OL-29974-01
Chapter 1
Introduction
Managing Your Site Homepage
Managing Your Site Homepage
The Site Homepage is by default your Cisco IAC login landing page. Also known as Service Portal, it
provides easy access to the portal pages and portlets, where you can perform the most common tasks,
including ordering servers and configuring networks.
Figure 1-6
The Service Portal Site Homepage
Figure 1-7
My Services: An Alternative Way to Access Cisco IAC Tools and Services for Some Users
Cisco Intelligent Automation for Cloud 4.0 User Guide
OL-29974-01
1-9
Chapter 1
Introduction
Managing Your Site Homepage
Changing Your Default Home Page
Follow these steps to change your Home Page from the default, as needed.
Step 1
Navigate to the page you want to use as your home page.
Step 2
Click My Home button next to the module drop-down list in the upper-right corner of the window.
Figure 1-8
Main UI Buttons
Step 3
Click Set As Homepage.
Step 4
Click OK to commit, then click OK again to acknowledge the change.
Activating or Inactivating a Portal Page
Step 1
Choose Portal Designer from the module drop-down list.
Step 2
On the Portal Designer page, select the page you want to add a reserved portlet to.
Step 3
Click the General tab (it should be displaying by default).
Step 4
In the Portal Page Information area, click either the Inactive or Active radio button, as needed.
Figure 1-9
Step 5
Portal Page Activation Buttons
Exit this screen.
Enabling Reserved Portlet Buttons
Reserved portlets are out-of-the-box portlets that ship with Cisco Prime Service Catalog. Reserved
portlets can be added to any page at any time using the Portal Designer.
Cisco Intelligent Automation for Cloud 4.0 User Guide
1-10
OL-29974-01
Chapter 1
Introduction
Managing Your Site Homepage
Table 1-3
Reserved Portlet Buttons
Reserved Portlet Button Description
Account
Adds an Account control to the selected page to display a list of accounts.
Approval
Adds an Approvals control to the selected page to display a list of tasks
needing approvals
Billing Rates
Adds a Billing Rates control to the selected page to display Billing Rates.
Order Status
Adds an Order Status control to the selected page to display order status.
Search
Adds a Search control to selected page to search for services by name.
Step 1
Choose Portal Designer from the module drop-down list.
Step 2
On the Portal Designer page, select the page you want to add a reserved portlet to.
Step 3
Click the Portals tab.
Step 4
Click the Add Portlets to Page button at the bottom of the screen.
Step 5
Expand the Content Portlets folder, and then the Reserved Portlets folder in the left pane.
Figure 1-10
Add Portlets to Page Dialog Box
Step 6
Click the check box for any of the portlets in the folder and then click Add.
Step 7
You will now see the reserved portlet(s) you activated listed in the Portals tab page for that portal.
Removing a Reserved Portlet
Step 1
Choose Portal Designer from the module drop-down list.
Step 2
On the Portal Designer page, select the page you want to remove a reserved portlet from.
Cisco Intelligent Automation for Cloud 4.0 User Guide
OL-29974-01
1-11
Chapter 1
Introduction
Managing Your Site Homepage
Step 3
Click the Portals tab.
Step 4
Click to highlight the line for the reserved portlet you want to remove.
Step 5
Click the Add Portlets to Page button at the bottom of the screen.
Re-Enabling Reserved Portlet
To re-enable reserved portlet buttons that you’ve deleted, follow the steps found in the “Enabling
Reserved Portlet Buttons” procedure on page 1-10.
Tip
For much more information on how to use the Portal Designer, please see the Portal Designer Help
System, accessible by clicking the small red [?] in the upper right of the Portal Designer page.
Service Manager
Service Manager enables Cloud Provider Technical Administrators (CPTAs) to manage, assign, and
track progress on tasks for Service Team members. The Cloud Provider Technical Administrator uses
ERS and Approvals portlets to try and remediate Cloud services.
Note
Cloud Provider Technical Administrators, Organization Technical Administrators, and site
administrators have permissions to access the Service Manager module.
Organization Designer
Cloud Provider Technical Administrators use Organization Designer to create, modify, and remove
users. Cloud Provider Technical Administrators and site administrators have permissions to access the
Organization Designer module.
Note
Organizations can only be modified in the Organization Management portal. See Managing Your Site
Homepage, page 1-9 for how to access portal pages; see Chapter 4, “Managing Organizations and Users”
in the Cisco Intelligent Automation for Cloud 4.0 Administrator Guide for information on modifying an
organization.
Service Item Manager
The Service Item Manager module provides tools for managing service items and ordering standards.
Ordering standards are defined options that users can choose when ordering servers. For example, you
can define the server sizes users can order; these options appear in drop-down lists on server order forms.
Only Cloud Provider Technical Administrators and site administrators have permissions to access the
Service Item Manager module.
Cisco Intelligent Automation for Cloud 4.0 User Guide
1-12
OL-29974-01
Chapter 1
Introduction
Profile Settings and Preferences
Administration
Access the Administration module to perform administrative tasks, such as editing system-wide settings
and configuring authorizations and reviews. Note that as with Service Item Manager, only Cloud
Provider Technical Administrators have permissions to access the Administration module.
Profile Settings and Preferences
You can add or update personal settings and preferences in your Prime Service Catalog user account.
From the Profile portal, you can perform the following:
•
Change your Prime Service Catalog password
•
Add, update, or delete contact and location information
•
Add, update, or delete calendar information, such as your working hours and scheduled time off
•
Change personal preferences for date and time format, login module
Changes to your personal settings, such as password and time zone, automatically update your Prime
Service Catalog user account. To access your profile settings, click Profile at the top of any page in Prime
Service Catalog.
Customizing Table Views
In Prime Service Catalog, most table views are customizable per user. You can sort rows in ascending or
descending order by column. In some cases, you can also choose which columns to show or hide. When
you change the table view, your personal settings are retained unless or until you change them again, of
if you have cookies disabled in your browser settings.
Re-sorting Table Rows by Column
By default, table rows are sorted by ascending order of the first column. To re-sort the rows by another
column, click the column title. To re-sort the rows in ascending or descending order by column, hover
the mouse pointer over the far right side of the column title until an arrow appears, click the arrow, then
choose Sort Ascending or Sort Descending.
Adding or Removing Columns
Hover the mouse pointer over the far right side of the column title until an arrow appears. Next, click the
arrow and choose Columns. Then, check or uncheck boxes for any of the available columns.
Cisco Intelligent Automation for Cloud 4.0 User Guide
OL-29974-01
1-13
Chapter 1
Introduction
Profile Settings and Preferences
Cisco Intelligent Automation for Cloud 4.0 User Guide
1-14
OL-29974-01
CH A P T E R
2
Network Services Overview
Understanding Network Services
Bundled Technologies
Cisco Intelligent Automation for Cloud 4.0 ships with the following components.
Bundled Suite Components
•
Cisco Prime Service Catalog
•
Cisco Process Orchestrator
•
Cisco Server Provisioner
•
Cisco Prime Network Services Controller
Suite Components / New Integrations
Tip
•
Cisco UCS Director
•
VMware vCloud Director
•
OpenStack Essex (Nova)
•
Amazon AWS (EC2)
•
Cisco UCS Manager
•
Cisco Nexus 1000v
•
Cisco Cloud Services Router
•
Cisco ASA 1000v Limited Support
•
Cisco Virtual Security Gateway
•
Cisco Prime IPAM
•
Citrix Netscaler VPX
For for the full list of interoperable components, please see the Cisco Intelligent Automation for Cloud
4.0 Cisco Intelligent Automation for Cloud Compatibility & Requirements Matrix.
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
2-1
Chapter 2
Network Services Overview
Understanding Network Services
Network Architecture
The network architecture for Cisco Intelligent Automation for Cloud 4.0 is outlined below.
Network Architecture
Compute POD A
Compute POD B
Network POD A
Compute POD C
Network POD B
361880
Figure 2-1
VMDC
•
Orchestration of VMDC:
– Nexus 1000v
– CSR 1000v
– VSG
– NetScaler VPX
– ASA 1000v
VMDC 2.3
•
Extendable to support VMDC:
– ASR 1000
– Cisco 7600
– Nexus 2000/5000/7000
– ASA-SM
– FWSM
– Extensible to additional devices and architectures
Supported Virtual Appliances
CIAC 4.0 Virtual Appliances and their functions are listed below.
Table 2-1
Virtual Appliances
Appliance
Function
ASA 1000v
Virtual firewall and VPN secures tenant edge
Citrix Netscaler
Virtualized tenant load balancing
Cisco Intelligent Automation for Cloud User Guide
2-2
OL-29974-01
Chapter 2
Network Services Overview
Network Discovery Flow
Table 2-1
Tip
Virtual Appliances (continued)
Appliance
Function
CSR 1000v
Virtual routing instance Hypervisor-isolated, Virtual
enterprise-class virtual Cisco IOS-XE router per tenant
Nexus 1000v
Distributed vSwitch
Prime NSC
Security Policy Management
Virtual Security Gateway (VSG)
Virtual zone based firewall to secure intra-tenant traffic
For for the full list of supported Virtual Appliances, please see the Cisco Intelligent Automation for
Cloud 4.0 Cisco Intelligent Automation for Cloud Compatibility & Requirements Matrix.
Network Discovery Flow
Figure 2-2 illustrates the network discovery flow used in Cisco Intelligent Automation for Cloud 4.0.
Figure 2-2
User
Seed Device &
Credentials
Network Discovery Flow
Portal
Orchestrator
Management
Appliance
Discovery
Service
Inventory
Service
Topology
Service
Session Information
Requisition Complete
Async REST Call-Write
Session Config
Start Discovery
Collect Device Inventory
Record Device
Inventory
Record Device
Inventory
Collect Topology
Record Device Topology
Update
Interconnections
Record Device
Topology
361849
Register Device
Record Device &
Credential
Network POD
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
2-3
Chapter 2
Network Services Overview
Use Case by Persona
Platform Elements and POD Relationships
The table below shows the relationship information between specific platform elements and PODs.
Table 2-2
Elements and PODs
Platform Element
POD Information
One Cisco Prime Service Catalog
One or more in the web tier and database tier; one in
SL tier
One or more Cisco Process Orchestrators
Zero or more VMware vCenter Servers (not
Linked mode)
Zero or more Cisco Server Provisioners
One may be associated to a POD or multiple PODs
(not multiple within a POD)
Zero or more UCS Managers
Only one may be associated to a Compute POD
Zero or one Cisco Prime IPAMs
Zero or one Cisco UCS Directors
One may service multiple Network PODs
Zero or more Cisco Virtual Security Gateways Two VSGs per Nexus 1000v per Tenant Organization
Zero or more Cisco Nexus 1000vs
Networks must be pre-provisioned if no Nexus 1000v
is registered
Zero or more Cisco Prime Network Service
Controllers
Only one may be associated to a Service Resource
Container
Zero or more Cloud Service Router 1000vs
(CSR)
One CSR per Nexus 1000v per Tenant Organization
Zero or more Cisco ASA 1000vs
One vASA per Nexus 1000v per Tenant Organization
Zero or more Citrix NetScaler VPXs
One VPX per Nexus 1000v per Tenant Organization
Use Case by Persona
Cloud Provider Technical Administrator (CPTA)
Connections and Discovery
•
Connect to managers and devices
•
Discover and inventory virtual and physical network devices
•
Discover and define network topology (device interconnects)
•
Perform network device connectivity checks
•
Manage network device credentials
•
Define, update and remove Network PODs
•
Associate to Compute PODs
Cisco Intelligent Automation for Cloud User Guide
2-4
OL-29974-01
Chapter 2
Network Services Overview
Use Case by Persona
System Settings and Behavior
•
Define Internet and Enterprise routing behavior
•
Define IPAM authority for network provisioning
•
Identify virtual network appliance images
Greenfield/Brownfield Support
•
Support Greenfield Network PODs
•
Coexist with Brownfield networks and services for existing tenants (enabling migration)
•
Perform discovery of existing networks by discovering available and used IP addresses
Tenant Management
•
On-board new tenants and organizations and set up initial network services
•
Off-board existing tenants and organizations and remove all network resources
Ongoing Management
•
Network inventory synchronization (manual invocation)
•
Display utilization of system network resources (networks, policies, and so on)
•
Views for capacity management of VDCs
•
Views for capacity management of tenant network resources (private cloud case)
•
View ordered networks and network services by tenant
Cloud Provider Business Administrator (CPBA)
Service Management
•
Set master pricing of cloud services and cloud resources
•
Virtual Machines (and resources)
•
Physical Servers (and resources)
•
Virtual Data Centers (sizes)
•
View all or tenant-specific prices and run rates
Tenant Management
•
Onboard new tenant with or without tenant-specific discount
•
Set tenant-specific service offering elections
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
2-5
Chapter 2
Network Services Overview
Use Case by Persona
Tenant Technical Administrator (TTA)
View
Available network services offered by the cloud provider
Select
•
Select network services to be offered to tenant users.
Order
•
Order tenant-level resources (shared network zone, public IP pool, etc.)
Manage
•
Access to different organizations
•
Access to the same VDC (share private VDCs)
•
Define network tenant firewall and load balancer service groups
•
Define tenant network security policy
•
View VDC, network, and tenant services ordered by tenant users
•
Monitor resource utilization of tenant network resources
Organization Technical Administrator (OTA)
View
•
Available tenant VDCs and other resources
Order
•
A VDC, selecting size, zones, and networks
Manage Lifecycle
•
Modify VDC zones and networks
•
Add, modify, or remove NAT, server firewall, server load-balancing
•
Manage server and service groups
•
Decommission VDCs
Server Owner / Application Architect
•
View accessible VDCs and shared zones and their resources
•
Use static or dynamic IP addressing
•
Manage individual server firewall and load-balancer service policy
•
Manage individual server membership to server and service groups
•
Single or bulk server deployment: Deploy multiple virtual servers of the same type
Cisco Intelligent Automation for Cloud User Guide
2-6
OL-29974-01
Chapter 2
Network Services Overview
Understanding Server and Service Groups
Understanding Server and Service Groups
Server Groups
A server group is a collection of servers (see Figure 2-3), which may be used as source or destination
endpoints. Server Groups are logical collections of related servers on the same network. Server Groups
are used to apply and define firewall services and policies.
Server Groups are based on IP addresses, which are applicable to:
•
Both physical and virtual servers
•
CSR 1000v, ASA 1000V or VSG levels
In addition, servers can be added and removed from Server Groups without having to
create/modify/delete any firewall or load balancer rules. Firewall rules that target Server Groups use the
source or destination qualifier. When a server is added to the Server Group, the server immediately
inherits all of the firewall rules applied to the Server Group.
Figure 2-3
Server Group Layout
VDC
Networks
Management
Network
User
Network
IP Address
Physical Server
Physical Server
361850
Server Group
Service Groups
Service Groups are a collection of port, protocol, and monitor combinations that can be used as a single
manageable entity for firewall and load balancing purposes (see Figure 2-4). Service Groups offer
application and management of policy broadly across associated servers and server groups. There are
two types of Service Groups: Firewall Service Groups and Load Balancer Service Groups.
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
2-7
Chapter 2
Network Services Overview
Understanding Server and Service Groups
Figure 2-4
Service Group Layout
VDC
Server Group
Firewall
Service Group
Load Balancer
Service Group
361851
Physical or
Virtual Server
Load Balancer Service Groups
Cisco IAC 4.0 ships with a default set of Load Balancer service groups for HTTP and HTTPS.
Lifecycle of Load-Balancer Service Group
Provider may modify this global set at any time. New tenants receive this default set upon onboarding.
In addition, an Organization inherits from the service groups defined by the TTA when onboarded. Note
that new service group additions are not propagated to existing Organizations. Also, when onboarding
an organization, a default set of service groups is inherited from a Provider-defined global set.
Figure 2-5
Organizations, Service Groups, and Load Balancers
Virtual Servers and Service Groups
Organizational
Units
Tenant
VPX
VIP
Organization
Service Group
Server
361883
End User
Cisco Intelligent Automation for Cloud User Guide
2-8
OL-29974-01
Chapter 2
Network Services Overview
Network Topologies
Firewall Service Groups
Cisco IAC 4.0 ships with a default set of Firewall service groups: Web, Remote Access, and Database
(four different types).
Lifecycle of Firewall Service Group
Provider may modify this global set at any time. An Organization receives this default set upon
onboarding. Again, as with Load Balancer service groups, new service group additions are not
propagated to existing Organizations
When an organization is onboarded, a default set of service groups are inherited from a Provider-defined
global set.
Firewall Rules
Firewall rules metadata is captured in a fashion that is technology-agnostic. Rules are applicable to VSG,
CSR, ASA 1000v, and physical network devices, and are stored in designated Firewall Policy Rules.
Network Topologies
Cisco IAC 4.0 includes a base set of sixteen (16) VDC zone-based topologies. Additional permutations
are possible based on the number of networks per zone.
Cisco IAC 4.0 / VSA 1.0
The table below outlines the topologies for VSA 1.0.
Table 2-3
VMDC 4 Topologies
Topology
Description
4-Zone Gold
Four security zones: a public, a protected public, a private and a
protected private zone (CSR, VSG, LB)
2-Zone Gold
Two security zones: a protected public and protected private zone
(CSR, VSG, LB)
Gold
One security zone: a protected public or a protected private zone
(CSR, VSG, LB)
Silver
One security zone, public or private (CSR [routing], VSG, LB)
Bronze
One zone, public or private (CSR [routing], VSG)
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
2-9
Chapter 2
Network Services Overview
Points of Delivery (PODs)
Cisco IAC 4.0 / VMDC 2.3
The table below outlines the topologies for VMDC 2.3.
Table 2-4
VMDC 2.3 Topologies
Topology
Description
4-Zone Gold
Four zones: one public, one protected public, one private, and one
protected private zone (ASA, VSG, LB)
2-Zone Gold
Two zones: one protected public and one protected private zone (ASA,
VSG, LB)
Gold
One zone: a protected public or a protected private zone (ASA, VSG, LB)
Silver
One zone, public or private (VSG, LB)
Bronze
One zone, public or private (VSG)
Copper
One zone, public or private (FW, VSG)
VDC Topology
The table below shows the VDC topology by zone type.
Table 2-5
VDC Topology, Addressing, and Service Matrix
Public IP
Space
Private IP
Space
Inter-Zone
Firewall
Intra-Zone
Firewall
Outbound
NAT
Unprotected Internet
Yes
Yes
No
No
No
Unprotected Enterprise
Yes
Yes
No
No
No
Protected Internet
Yes
Yes
Yes
Yes
Yes
Protected Enterprise
Yes
Yes
Yes
Yes
No
Zone Type
Points of Delivery (PODs)
There are three POD (Point of Delivery) types in Cisco IAC 4.0:
•
Compute POD
•
Network POD
•
Network and Compute POD
Compute POD
Cisco IAC 4.0 models these Compute PODs so it understands how it is that various infrastructure is
associated to other infrastructure, so it can empower the cloud administrator with common tools of
capacity management of that infrastructure by way of the logical construct of these Compute PODs.
Cisco Intelligent Automation for Cloud User Guide
2-10
OL-29974-01
Chapter 2
Network Services Overview
Points of Delivery (PODs)
Figure 2-6
Compute POD Flow
Service
Catalog
POD A
POD B
POD C
vCenter Server
Datacenter
vCenter Server Datacenter
UCS Director
V & P Account
UCS Director Virtual & Physical Account
UCS Manager
UCS Manager
Process
Orchestrator
UCS
Director
POD D
POD E
POD F
POD G
UCS
Director
vCloud
Director
OpenStack
EC2
UCS Manager
UCS Manager
UCS Manager
UCS Manager
361848
Server
Provisioner
UCS Manager
Network POD
Cisco IAC 4.0 can interact with instances of the Cisco Prime Network Services Controller (as shown in
Figure 2-7) that were previously deployed; or, Cisco IAC can provision new instances. Also shown in
the illustration are various network POD types.
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
2-11
Chapter 2
Network Services Overview
Points of Delivery (PODs)
Figure 2-7
Network POD Flow
Service
Catalog
Prime NSC
Process
Orchestrator
Network POD A
Network POD B
PE Network
Equipment
Network POD C
Nexus 7000
ASR 1000
Nexus 7000
ASR 9000
Nexus 7000
ASR 9000
Nexus 5000
Nexus 1000v
Nexus 5000
Nexus 1000v
Nexus 5000
UCS 6000 FI
ASA 5500 or
FWSM
UCS FI
ASA 5500 or
FWSM
NetScalar SDX
361881
UCS 6000 FI
Network and Compute POD
Figure 2-8 shows how Compute PODs relate to Network PODs. Due to scalability, one Network POD
may service multiple Compute PODs.
Compute POD A
Network and Compute POD Flow
Compute POD B
Compute POD C
Compute POD D
Network POD A
Nexus 7000
Nexus 5000
ASA or FWSM
UCS FI
Compute POD E
Network POD B
ASR 1000
Nexus 1000v
Nexus 7000
Nexus 5000
ASR 9000
Nexus 1000v
Cisco Intelligent Automation for Cloud User Guide
2-12
OL-29974-01
361882
Figure 2-8
CH A P T E R
3
Managing PODs
A POD is a Point of Delivery unit. There are two types of PODS: Network PODs and Compute PODs.
There are also SRCs: Service Request Containers. In Cisco Intelligent Automation for Cloud 4.0, you
can create as many PODs as your organization requires.
Working with Network PODs
A POD is a module or group of network, compute, storage, and application components that work
together to deliver a network service. The POD is a repeatable pattern, and its components increase the
modularity, scalability, and manageability of data centers. You must be logged in as a Cloud Provider
Technical Administrator to create a Network POD.
Creating One or More PODs
Use the Register a POD service to register an installed POD and select the instances that manage its
resources, so that you can start using it in the cloud.
Step 1
Choose Service Portal from the module drop-down list to display the text menu bar.
Step 2
Click System to display the nested menu.
Step 3
On the System Settings portal, click the PODs tab to open the portlet.
Step 4
On the PODs portlet, click:
– Register a Network POD
Step 5
On the Create Network POD form, define the cloud infrastructure:
•
Assign a name and description.
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
3-1
Chapter 3
Managing PODs
Working with Network PODs
•
This field is not editable; only one vCenter is allowed.
•
Select the datacenter that is to serve this POD. There is a 1-to-1 mapping between data centers and
PODs.
•
If the drop-down list is empty, all available data centers have been associated with a POD.
•
Optional. Select the UCS Manager that is to serve this POD. There is a 1-to-1 mapping between UCS
Managers and PODs.
•
If the drop-down list is empty, all available UCS Managers have been associated with a POD.
•
Optional. Select the Server Provisioner instance that is to serve this POD. A CSP can be associated
with multiple PODs. This option requires:
– vCenter Port Group for OS Provisioning - The port group inside the vCenter that will be used
for the provisioning VLAN for bare metal installations.
– UCS VLAN for OS Provisioning - The VLAN associated with UCS that is used by the Server
Provisioner for bare metal installations.
Step 6
Click Submit Order.
Modifying Network POD Properties
Step 1
Choose Service Portal > System Setup > System Settings.
Step 2
On the System Settings portal, click the PODs tab to open the portlet.
Step 3
On the PODs portlet, click:
– Modify a Network POD
Step 4
Step 5
On the Modify Network POD form, complete the fields, as needed.
•
Network POD Name and Description
•
VLANPool
•
Edge Router
•
Layer3 Aggregation Switch
•
Layer3 Service Node
•
Layer2 Access Switch:
•
UCS Manager Interconnect
•
Virtual Access Switch
Click Submit Order.
Removing a Network POD
Step 1
Choose Service Portal > System Setup > System Settings.
Step 2
On the System Settings portal, click the PODs tab to open the portlet.
Cisco Intelligent Automation for Cloud User Guide
3-2
OL-29974-01
Chapter 3
Managing PODs
Working with Compute PODs
Step 3
On the PODs portlet, click:
– Remove a Network POD
Step 4
On the Remove Network POD form, select the POD from the dropdown list.
Step 5
Check the YES check box next to Confirm Action.
Step 6
Click Submit Order.
Working with Compute PODs
Step 1
Choose Service Portal > System Setup > System Settings.
Step 2
On the System Settings portal, click the PODs tab to open the portlet.
Step 3
On the PODs portlet, click:
– Create a Compute POD
Step 4
On the Create Compute POD form, select the POD from the dropdown list.
Step 5
Check the YES check box next to Confirm Action.
Step 6
Click Submit Order.
Registering a Compute POD
Step 1
Choose Service Portal > System Setup > System Settings.
Step 2
On the System Settings portal, click the PODs tab to open the portlet.
Step 3
On the PODs portlet, click:
– Register a Compute POD
Step 4
On the Create Compute POD form, select the POD from the dropdown list.
Step 5
Check the YES check box next to Confirm Action.
Step 6
Click Submit Order.
Modifying a Compute POD’s Properties
Step 1
Choose Service Portal > System Setup > System Settings.
Step 2
On the System Settings portal, click the PODs tab to open the portlet.
Step 3
On the PODs portlet, click:
– Modify a Compute POD
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
3-3
Chapter 3
Managing PODs
Working with Resource Containers
Step 4
On the Remove Compute POD form, select the POD from the dropdown list.
Step 5
Check the YES check box next to Confirm Action.
Step 6
Click Submit Order.
Removing a Compute POD
Step 1
Choose Service Portal > System Setup > System Settings.
Step 2
On the System Settings portal, click the PODs tab to open the portlet.
Step 3
On the PODs portlet, click:
– Remove a Compute POD
Step 4
On the Remove Compute POD form, select the POD from the dropdown list.
Step 5
Check the YES check box next to Confirm Action.
Step 6
Click Submit Order.
Working with Resource Containers
Creating a Service Resource Container
Register a Service Resource Container to dedicated cloud infrastructure for purposes of providing
network services to tenants.
Step 1
Choose Service Portal > System Setup > System Settings.
Step 2
On the System Settings portal, click the PODs tab to open the portlet.
Step 3
On the PODs portlet, click:
– Create a Service Resource Container
Step 4
On the Create Service Resource Container form, complete the required fields.
•
Give a friendly name to easily identify the set of resources allocated for network services.
•
Select a Compute POD, Datacenter Name, Cluster Name, and Datastore Name
•
Management Network: Select a network to which management interface of the Network Service
Virtual Machines will be connected.
•
Service Network: Select a network to which service interface of the network service virtual
machines will be connected.
•
Internet Transit Network: Select a network to which Internet interface of the Virtual Network
Service nodes will be connected.
•
For the Resource Pool, enter the Resource Pool Name and Description
– CPU Shares:Select CPU shares for the Network Service Virtual Machines.
Cisco Intelligent Automation for Cloud User Guide
3-4
OL-29974-01
Chapter 3
Managing PODs
Working with Resource Containers
– CPU Limit (MHz): Enter the CPU Limit in MHz for the resource pool. Enter -1 for unlimited.
– Memory Limit (GB): Enter the MemoryLimit for the resource pool. Enter -1 for unlimited.
– CPU Reservation (MHz): Enter the amount of CPU reservation in MHz to exclusively set aside
for this resource pool.
– Memory Reservation (GB): Enter the amount of memory to exclusively set aside for this
resource pool.
Step 5
Click Submit Order.
Modifying Service Resource Container Properties
Modify assigned resources for a registered Service Resource Container.
Step 1
Choose Service Portal > System Setup > System Settings.
Step 2
On the System Settings portal, click the PODs tab to open the portlet.
Step 3
On the PODs portlet, click:
– Modify Service Resource Container Properties
Step 4
On the Modify Service Resource Container form, complete the following.
•
Select a Resource Name and enter the ClusterName
•
Modify as needed:
– POD Name
– Datacenter Name
– Cluster Name
– Datastore Name
– Management Network
– Service Network
– CSR Organization
– VSG Organization
– VPX Organization
•
For the Resource Pool, modify any or all:
– Resource Pool Name and Description
– CPU Limit (MHz): Enter the CPU Limit in MHz for the resource pool. Enter -1 for unlimited.
– Memory Limit (GB): Enter the MemoryLimit for the resource pool. Enter -1 for unlimited.
– CPU Reservation (MHz): Enter the amount of CPU reservation in MHz to exclusively set aside
for this resource pool.
– Memory Reservation (GB): Enter the amount of memory to exclusively set aside for this
resource pool.
Step 5
Click Submit Order.
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
3-5
Chapter 3
Managing PODs
Working with Resource Containers
Deleting a Service Resource Container
Remove a Service Resource Container and disconnect all infrastructure resources associated to the
container.
Step 1
Choose Service Portal > System Setup > System Settings.
Step 2
On the System Settings portal, click the PODs tab to open the portlet.
Step 3
On the PODs portlet, click:
– Delete a Service Resource Container
Step 4
On the Delete a Service Resource Container form, select the POD from the dropdown list.
Step 5
Check the YES check box next to Confirm Action.
Step 6
Click Submit Order.
Cisco Intelligent Automation for Cloud User Guide
3-6
OL-29974-01
CH A P T E R
4
Managing Services
Cloud Provider Technical Administrators use Prime Service Catalog to configure standards for service
items, manage server leases, and monitor service process flows to ensure they operate smoothly and
quickly fix any problems that might arise.
Viewing Service Requisitions
View service requisitions that you ordered for yourself and for others, status of each request, see error
details, and track how close it is to completion. See also Order Status Portlet documentation in the Cisco
Service Portal Designer Guide.
Step 1
Choose Service Portal from the module drop-down list. The text menu displays.
Step 2
Click My Cloud to display its nested menu.
Step 3
Select My Orders from the menu.
You will see the Order Status portal displaying your order information, such as Requisition ID,
Description, Order Date, and so on.
Figure 4-1
Step 4
Order Status Portal Displaying Orders
Select the orders that you want to view. You can choose to view all orders or select based on the status
of the service requests. You can also choose to view the requisitions ordered for yourself or for others.
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
4-1
Chapter 4
Managing Services
Configuring and Enabling Approvals
Step 5
Expand the arrow (from this  to this ) to view the details of the service and percentage of completion.
Step 6
Click on the order number to view the requisition form that contains the details of the services and the
delivery process.
Step 7
Click on the service name to view the order form that contains the service and the server management
information.
Step 8
Click Cancel Service to cancel the selected service.
Configuring and Enabling Approvals
Authorizations are any approvals required in conjunction with completing fulfillment of a service
request. Authorizations give the approver the opportunity to determine if the person requesting the
service is eligible to receive it. If an authorization is rejected, the requisition will be canceled and the
service will not be delivered. A requisition that needs authorization will be placed in a queue specifically
created for approvals. A queue for approvals is created whenever a new organization is created. The TTA,
TBA, OTA, and CPTA have permissions to perform approve or reject actions on a service requisition that
needs approval.
Every requisition that needs approval waits in the queue until it is either approved or rejected. Approver
will be notified whenever a requisition that needs approval enters the approval queue. When a requisition
is rejected, e-mail notification will be sent out to the requester of the service. No notification will be sent
out when a requisition is approved.
Approvals needed by the Cloud Provider Technical Administrator will go into the queue created by
default for the Cloud Provider Organization. Approvals needed by TTA, TBA, and OTA will go into
organization-specific queues. These are example naming convention for the queues:
Organization
Queue
Cloud Provider Organization
Cloud Service Approval Administration
Other
Approvals for <Organization Name>
Approvals are mandatory for the following services and are automatically enabled:
Service
Cloud Provider Administrator Organization Administrator
Approval is Required
Approval is Required
Create Virtual Data Center
Yes
No
Add Network to VDC
Yes
No
Step 1
Choose Service Portal from the module drop-down list to display the text menu bar.
Step 2
Click System Setup to display the nested menu.
Step 3
Click System Settings.
Step 4
On the System Settings portal, click the Approvals tab to open the portlet.
Step 5
On the Approvals portlet, click:
– Configure Approvals
The Configure Approvals form displays.
Cisco Intelligent Automation for Cloud User Guide
4-2
OL-29974-01
Chapter 4
Managing Services
Managing Server Leases
Step 6
For each service, indicate whether approval is required from the TTA, TBA, OTA, or the CPTA.
Step 7
Click Submit Order.
Managing Approval Requests
Using the Approvals Portlet
Use the Approvals portlet to track and view authorizations for service requisitions—and thereby control
expensive or resource-intensive services. The Approvals portlet displays a list of authorizations filtered
by authorization type and authorization status.
Both the Organization Technical Administrator and the Cloud Provider Technical Administrator can use
the Approvals portlet to approve, cancel, or reject a service requisition; a service requisition that needs
approval waits in the queue until it is either approved or rejected. The service requester will be notified
through e-mail when the service waits for approval and gets the notification when a service is rejected.
For information about using the Approvals portlet to track and view authorizations, see the “Approvals
Portlet” section in the Cisco Prime Service Catalog 10.0 Designer Guide. You can also access the
Approvals portlet from the module drop-down list; choose Service Portal > Operations > Approvals.
Note
The Service Manager module can also be used to manage approvals. For more information about the
Service Manager, see the Cisco Prime Service Catalog 10.0 Configuration Guide.
Approval Queues
Services that need approvals will be placed in the corresponding queues:
•
Approval needed by the Cloud Provider Technical Administrator will be placed in the Cloud Service
Approval Administration queue.
•
Approval needed by Organization Technical Administrator will be placed in the queue with the
naming convention Approvals for <Organization name>.
Managing Server Leases
A server lease is a time period after which an active server is automatically decommissioned. Leases are
optional and can be set when you order a server. This is a CTPA-controlled setting. It may be updated
from System Setup > Standards tab, then by going to the Lease Term table. The default storage lease
expiration is 10 days. At the end of the lease term, the server is decommissioned automatically. There
are two successive expiration dates:
•
Lease Expiration—The server is powered down—but not deleted. Any stored data is preserved but
cannot be accessed by users unless the lease is extended.
•
Storage Lease Expiration—The server is permanently deleted and any stored data is lost.
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
4-3
Chapter 4
Managing Services
Managing Server Leases
Notifying a User of Approaching Lease Expiration
Cisco IAC provides two customizable e-mail notification templates for notifying a user of an
approaching expiration date:
•
Lease Expiration - First Warning
•
Lease Expiration - Section Warning
You can choose when each e-mail notification is automatically sent. To view and modify the Lease
Expiration - First Warning template for a user’s organization, see Managing E-mail Templates, page 7-4.
Viewing Server Lease Information
View the expiration and storage expiration dates of a lease on a server from the My Servers portal page.
Step 1
Choose Service Portal from the module drop-down list, then click My Servers.
Step 2
On the My Servers portal, locate and click the server in the table.
Step 3
Lease information is shown in the Details section for the selected server.
Extending or Removing a Server Lease
You may extend the expiration date on which a server is decommissioned but is not deleted. You can
extend a lease during the lease term or after lease expiration but before storage expiration. You can also
remove an existing lease from a server without deleting or decommissioning it. By removing a lease, you
are simply stopping the automatic decommission service.
Step 1
Choose Service Portal from the module drop-down list and then click My Servers.
Step 2
On the My Servers portal, locate and click the server in the table. Details about the server and icons for
actions appear in the Take Action area.
Step 3
Click the Extend Lease icon to open the Extend Managed Lease Instance form. The name of the server
and its expiration date appear on the form.
Step 4
From the Term drop-down list on the Extend Managed Lease Instance form, choose the number of days
you want to add to the end of your lease term, or choose No Lease to remove the lease from the server.
Step 5
No Lease
6 months
30 days
9 months
90 days
1 year
Click Submit Order.
Cisco Intelligent Automation for Cloud User Guide
4-4
OL-29974-01
Chapter 4
Managing Services
Managing Infrastructure
Managing Infrastructure
Cisco Intelligent Automation for Cloud 4.0 includes a number of ways to manage your infrastructure.
Maintaining Your Servers
You can view your servers as well as act on them at any time. To do so:
Figure 4-2
Step 1
From the modules dropdown menu, select My Cloud.
Step 2
From the text menu bar, select My Servers.
The “My Servers” Portal
1
Displays the details of the selected server
5
List of servers under your management
2
Available Actions button
6
Detail pane the drops open when you click button indicated by #1
3
Server Action button palette
7
Filter button and list of filters
4
Indicates the power state of the server
8
Refresh button
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
4-5
Chapter 4
Managing Services
Managing Infrastructure
Infrastructure Ownership Reassignment
There will be times when you need to change ownership of a virtual server to another user. Typical
scenarios include changing ownership to a support person for repairs and upgrades, and then switching
ownership back to the original owner. Another example would be if an employee assigned to a VM is no
longer available, you can reassign that VM to a different employee.
Note
In virtually all cases, you can only reassign ownership to another user within the same organization.
However, the behavior of this service is dependent upon your user role. For example, TTAs can reassign
ownership within the constituents of their tenant account, OTAs within their organization, and CPTAs
across tenants.
Warning
Cisco does not recommend reassigning ownership across tenant accounts, despite the fact that
CPTA-level users do have the ability to do this. It can cause accounting, billing, and other problems.
To reassign ownership (typically the task of an OTA, the Organization Technical Administrator), start at
the module drop-down menu.
Step 1
Choose Service Portal > My Cloud > My Servers.
Step 2
Select the device for which you want to change ownership.
Step 3
Click the Action button by the server name.
Step 4
In the pop up icon band, click the “person” icon.
Note
Step 5
For an illustrated view, see Figure 4-2: “The “My Servers” Portal” above.
When you hover your mouse over the icon, you’ll see a tooltip saying, “Modify server ownership.”
Figure 4-3
Modify Server Ownership Icon
Step 6
Click the icon and the Modify Server Ownership form displays.
Step 7
Click Select to open the Select Person form.
Step 8
Search for the person you want to reassign this server to (wildcards such as ? and * are acceptable; for
example DE*).
Step 9
From the list that then displays, click the radio button for the person you want to use, then click OK.
Step 10
Click Submit.
Step 11
Close the information form showing you that the request has been completed.
Step 12
Close the menu.
Cisco Intelligent Automation for Cloud User Guide
4-6
OL-29974-01
Chapter 4
Managing Services
Managing Infrastructure
Using the Manage Infrastructure Portal
To access this portal, select Service Portal > Operations > Manage Infrastructure. You will see the
Manage Infrastructure portal display (Figure 4-4).
Tip
Figure 4-4
The first visible charts upon the portal load act as a kind of “overview dashboard” for all platform
element types.
The Manage Infrastructure Portal
Here, you select any of the buttons on the left side to access information on:
•
Amazon EC2
•
Cisco IAC Management Appliance
•
Cisco Prime IPAM
•
Cisco Server Provisioner
•
Cisco USC Director
•
Cisco USC Manager
•
Cisco Prime Network Services Controller
•
Network Elements
Note
As you click on any of the above, the area beneath that button expands, displaying a clickable
list of items for you to choose from. In addition, the graphs and tables to the right change.
This page is the interface wherein the CPTA manipulates cloud infrastructure discovered by CloudSync.
Some example tasks are:
•
Registering discovered infrastructure for use within and management by Cisco IAC
•
Assigning price to a server template
•
Updating credentials associated with a cloud resource
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
4-7
Chapter 4
Managing Services
Managing Infrastructure
Checking System Health
You can check system health at anytime. You can also opt to turn on or off automatic health check or
change the scheduled frequency of health checks by (cloud) platform element type.
Turning Automatic Health Check On or Off (Global)
Access the Set Provisioning Settings Form starting at the modules selection drop down.
Note
This is the global setting. Individual intervals for different cloud platforms is manipulated in System
Health.
Step 1
Service Portal > Setup > System Settings > System Settings.
Step 2
On the System Settings portlet, click:
Set Provisioning Settings
Note
Step 3
On the Set Provisioning Settings Form, find the System Health Check option.
Step 4
From the drop down, choose the state you want Health Check to be in:
Step 5
•
Off
•
On
•
Default (---), which is On
Click Submit Order.
Viewing System Health
To view the current status of your systems’ health, use the System Health page this way (starting at the
modules selection menu in the upper right):
Step 1
Service Portal > Operations> System Health.
Step 2
On the System Health Status portlet (Figure 4-5), view and manage your systems’ health.
Note
Cisco IAC only displays cloud infrastructure that have been registered for use within your Cisco
IAC deployment.
Cisco Intelligent Automation for Cloud User Guide
4-8
OL-29974-01
Chapter 4
Managing Services
Managing Infrastructure
Figure 4-5
Tip
Step 3
System Health Status Portlet
Notice the Summary ribbon across the top of the portal. Here you see a quick view your cloud
platforms along with highlighted numbers showing current status information.
Switch between Cloud Infrastructure and Tenant Infrastructure, as needed.
•
Tenant Infrastructure is infrastructure assigned to and used by a tenant. (dedicated for a tenant's use)
•
Cloud Infrastructure is infrastructure used for purposed of running Cisco IAC.
Note
This infrastructure is owned by and assigned to the Provider/CPTA.
Managing System-Wide (Global) Health Settings
Step 4
Use the Check Health and Manage Intervals buttons as needed for system-wide purposes.
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
4-9
Chapter 4
Managing Services
Managing Infrastructure
Step 5
For each cloud platform element type, use that element’s Manage Intervals button to open the Update
System Health Check Intervals form.
Step 6
Select a new interval as needed:
Figure 4-6
System Health Intervals options
Managing Health at the Device-Type Level
Viewing Historical Health Data
Step 7
To view Historical health information on a cloud platform device, click the small gear icon next to any
device listed on the Health Check page.
A pop-up displays.
Figure 4-7
Step 8
Device-Type Historical Health Data
This popup is populated with historical data showing all health conditions on this device. You can scroll
back (use the scroll bar on the rightside of the popup) on this popup as far as you need to analyze the
health information.
Running a New Health Check
Step 9
To run a new health check, click the Check Health button.
Cisco Intelligent Automation for Cloud User Guide
4-10
OL-29974-01
Chapter 4
Managing Services
Managing Infrastructure
On the message box that pops up subsequently, click OK.
Remediating Health-Related Errors
Step 10
For any element displaying an error message or number, click on the info button:
Step 11
You will see a popup displaying additional information about the problem.
Scroll through to see find your device type and the associated error number.
Figure 4-8
Device-Type Health Errors - Error Code Lookup Popup
Step 12
Remediate the issue as instructed in the help box.
Step 13
Repeat as necessary for as many platform element types as you need to adjust.
Note
Step 14
To adjust all types at once to the same interval, use the Manage Intervals button at the top right
of the screen.
Close this portal when you are finished.
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
4-11
Chapter 4
Managing Services
Managing Infrastructure
Handling Infrastructure Errors
As a Cloud Provider Technical Administrator, you are entrusted with maintaining the cloud system and
ensuring maximal uptime. If problems arise with fulfillment of a customer’s requisition (for example, a
new virtual machine), you receive an e-mail notification error with error code, description, automation
summary link, and the link to the Error Remediations portal.
Conditions
Service problems can arise in any of the following conditions (among many others):
Note
•
Blade error has disabled all VMs running on it
•
Blade error has occurred on a physical blade
•
Cisco UCS Manager, VMware vCenter, LDAP server, or blades in the physical pool have failed
•
Connection is lost
•
Capacity has reached the maximum limit
Please refer to the Cisco Intelligent Automation for Cloud 4.0 Error Messages page, online at
http://www.cisco.com/en/US/products/ps11869/products_tech_note09186a0080bf9d4c.shtml.
The notification will identify the failing service and provide any or all of the following information:
•
Automation summary
•
Steps you must take to fix the problem, such as:
– Performing a roll-back and clean-up of the service to free up and reset associated resources,
cancel the requisition, and re-order the service from Prime Service Catalog
– Taking manual actions outside the system
– Restarting the process from Prime Service Catalog
– Cancelling certain actions in-flight if necessary
•
Referral to a knowledge base article that provides tips and best practices that you can use to
determine the actions to take to recover the process
After the correction, Process Orchestrator automatically makes a second attempt to run the service. If
the second attempt fails, you must cancel the order, then notify the requester to resubmit the order.
Four Steps
There are four sequential steps involved in remediating an infrastructure error:
•
Assigning the Remediation Task for Repair, page 4-12
•
Remediating a Service, page 4-13
•
Checking the Status of an Order, page 4-15
•
Cancelling the Order if Remediation Attempt is Unsuccessful, page 4-15
Assigning the Remediation Task for Repair
When a service requires remediation, it is automatically added to the Cloud Service Remediation queue
in Service Manager. You receive the notification of failure, then assign yourself or another Cloud
Provider Technical Administrator to address the issue.
Cisco Intelligent Automation for Cloud User Guide
4-12
OL-29974-01
Chapter 4
Managing Services
Managing Infrastructure
View the Cloud Service Remediation queue and assign a task using the following steps:
Step 1
Choose Service Manager from the module drop-down list.
Step 2
In the left navigation panel on the Service Manager Home page, expand All Queues in the tree on the
left-hand side, then click the name Cloud Service Remediation. Unassigned tasks appear in a list.
Tip
You can change the view of the tables in Service Manager using buttons located on the right-hand side
under the module drop-down list. Click
to show or hide the tree. Click
to hide the tree, preview
panels, and show only the list. Click
(default view) to show a split view list and preview panels,
without the tree. Click
to show the preview panels only. Service Manager does not save your views.
Step 3
In the Cloud Service Remediation queue list, click the requisition number. Display-only summaries of
the task and requisition appear below the Cloud Service Remediation queue.
Step 4
Assign the task:
•
To assign the task to yourself, choose Check Out from the More Actions drop-down list. The task
is moved to the My Work view in the left navigation panel.
•
To assign the task to someone else, expand Service Teams in the tree on the left-hand side, then the
team to which the user belongs, click the radio button by the user’s name, then click Assign. The
task is moved to the selected person’s My Work view; the person is notified of the assignment.
After the task is assigned, the assignee must first check out the task from the Cloud Service Remediation
queue before fixing the failure.
Remediating a Service
After you have checked out the task (see Assigning the Remediation Task for Repair) from the Cloud
Service Remediation queue, remediate the issue and initiate continuation of the fulfillment process.
Note
Step 1
To free up the reserved resources, attempt to remediate the issue, even if you know or suspect the attempt
will fail. You should not cancel the order unless your attempt to remediate the issue is unsuccessful.
Choose Service Portal from the modules menu, then click Operations > Error Remediation.
The table displays information such as requisition ID, the name of the service with errors, severity of the
error, date when the service was ordered, and last action taken on the service.
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
4-13
Chapter 4
Managing Services
Managing Infrastructure
Figure 4-9
Error Remediation Page
Step 2
Select the service that is assigned to you and needs action.
Step 3
Click the “gear” icon.
Step 4
Choose one of the following options from the Remediate Error panel to remediate the service.
Figure 4-10
Remediation Error Popup
•
Cancel. If your attempts to remediate the issue fail to complete, you can terminate the service to
release the resources that may be tied up by the stalled process by using Cancel.
•
Restart. Restart is basically a combo operation, a Cancel followed by a new service request. This
action will undo any changes to the service and attempts to start over from the beginning of the order.
For example, a service “Commission Physical Server” fails because the server provisioner TFTP
service is not functioning. You could do a complete rollback and start the process again.
•
Retry. Retry will repeat the failed step. The service execution will be resumed from a start point set
in the service orchestration.
•
Ignore. Attempts to ignore the step that just failed and continues with the next step in the process.
For example, a service “Server Provisioning” fails at customize VM activity and server is partially
provisioned at this step. You could choose to correct the error manually to ignore the step.
•
Rollback. Available for every appropriate service. This option reverses all infrastructure and service
item changes. For example, a service “Commission VM Template” service fails because the
datastore is full or you want to change the form data. You could rollback to reverse any or all the
changes that you made to the service and then cancel the order. Therefore the service could be at its
starting point after a Rollback and you could continue to create a new order.
Cisco Intelligent Automation for Cloud User Guide
4-14
OL-29974-01
Chapter 4
Managing Services
Managing Infrastructure
Step 5
Perform the necessary steps to remediate the issue.
Step 6
After remediating the issue, click Submit Order.This action changes the status of the task to In
Progress, and initiates continuation of the fulfillment process.
If the delivery process is successful, proceed to the next section, Checking the Status of an Order.
If the delivery process is not successful, the requisition will appear in the Cloud Service Cancellation
queue. Skip to Cancelling the Order if Remediation Attempt is Unsuccessful, page 4-15.
Checking the Status of an Order
If the delivery process is successful, then the ordered service will be fulfilled and the requisition status
changed to Complete, and no further action is needed. To check the status:
Step 1
Return to the Service Manager Home page and click Cloud Service Delivery Management under All
Queues in the left-hand panel.
Step 2
Locate the requisition in the queue, then click the requisition number to open the Task Data page.
The status is listed in the Service Information panel.
Cancelling the Order if Remediation Attempt is Unsuccessful
To free up the reserved resources, attempt to remediate the issue before cancelling the order, as instructed
in Remediating a Service, even if you know or suspect the attempt will fail. Cancel the order only if your
remediation attempt is unsuccessful. If your attempt to remediate the issue fails to complete the service,
you must terminate the service to release the resources that may be tied up by the stalled process.
Step 1
On the Service Manager Home page, click Cloud Service Cancellation under All Queues in the
left-hand panel.
Step 2
Locate the requisition in the queue, then click the requisition number to open the Task Data page.
Step 3
Click Cancel. This action terminates the order and change service status to Cancel.
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
4-15
Chapter 4
Managing Services
Managing Infrastructure
Cisco Intelligent Automation for Cloud User Guide
4-16
OL-29974-01
CH A P T E R
5
Managing Resources Using Discovery
After the initial set up of your cloud system, there are tasks you must perform the keep the system
running smoothly. This page provides information on managing the resources in your cloud system.
Note
To perform many of the procedures covered in this guide, you must have access to the “Manage
Infrastructure” page in the Service Portal module. CPTAs are granted access by default.
Discovering Network Devices
Network device discovery in Cisco Intelligent Automation for Cloud consists of choosing what type of
device you want Cisco IAC to go out and look for (discover) and return information on, and then
registering the devices you want to use. The workflow the user is straightforward, as shown in
Figure 5-1.
Figure 5-1
User Workflow For Discovery
Step 1
Enter Credentials
and Seed Device
Information
Step 3
Step 4
Step 5
Initate the
Discovery
Process
Register
Discovered
Device(s)
Assign Registered
Devices to a
Network POD
370871
Select the Object
Network Type
Step 2
Tip
Subnet data (an IP address and subnet mask) is required to discover devices using Ping sweep. Ping
Sweep is another method used to discover network devices. Note that Ping sweep expects the subnet
mask to be in the format of 255.255.255.x.
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
5-1
Chapter 5
Managing Resources Using Discovery
Discovering Network Devices
Tip
SNMP includes not just a username/password. Other parameters may be required depending on the
security level.
After discovery has been initiated, CloudSync takes over and runs the full discovery process, as shown
in Figure 5-2 on page 5-2.
Figure 5-2
The Network Discovery Portion of CloudSync.
Collected device, credentials,
inventory, and topology data 5
is returned and all discovered
devices are displayed on the
Cisco IAC screen
END
1 After the user intiates
T
AR
ST
Cloud
discovery, Cisco Prime
Service Catalog sends
session data to Cisco
Process Orchestrator
Topology 4
(device interconnection)
information is collected)
Sync
Note
2 PO then calls
the Management
Appliance
370870
Appliance 3
then starts discovery
and inventory services
Credentials are not returned for discovered network devices. Collected information about
devices and topology depends on the availability and correctness of credentials, and whether the
type of a device is fully supported. In general, network discovery is not guaranteed, but is rather
a best effort. This is unlike other types of discovery that query a device directly to discover
infrastructure.
Running Discovery
Step 1
Choose Service Portal from the module drop-down list.
The text menu bar displays.
Step 2
Click Setup to display the nested menu and click Manage Infrastructure.
Step 3
From the menu that appears next along the left of the screen, choose Network Elements.
Step 4
From the icons that display in the Network Elements dropdown list, select Network Devices:
Cisco Intelligent Automation for Cloud User Guide
5-2
OL-29974-01
Chapter 5
Managing Resources Using Discovery
Discovering Network Devices
Figure 5-3
Step 5
Network Devices in the List
Next, click Discover Network Devices just below the Network Devices label towards the top of the
screen:
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
5-3
Chapter 5
Managing Resources Using Discovery
Discovering Network Devices
Figure 5-4
Discover Network Devices Button
Off State
On State
The CloudSync Infrastructure Discovery (Discover Network Devices) screen displays.
Step 6
Step 7
From the Discovery Type drop down, selected a Discovery Type:
•
Neighbor Discovery
•
Ping Sweep
•
Neighbor & Ping Sweep
Enter required information:
•
For a Neighbor Discovery, enter an IP address in the Seed Device field.
•
For Ping Sweep, enter a Network Name and a Subnet Mask.
•
For a Neighbor & Ping Sweep, enter a Network Name, Subnet Mask, and an IP address in the Seed
Device field.
Note
Step 8
Cisco Intelligent Automation for Cloud 4.0 uses Cisco Device Protocol (CDP) and Link Layer
Discovery Protocol (LLDP) for discovery.
Next, enter information for either Simple Network Management Protocol (SNMP) for version 2 or
version 3, depending on how you have your devices configured.
Cisco Intelligent Automation for Cloud User Guide
5-4
OL-29974-01
Chapter 5
Managing Resources Using Discovery
Discovering Network Devices
Step 9
•
For SNMP v3, enter a username and password.
•
For SNMP v2, enter one or more community strings.
Enter Secure Shell (SSH) credentials.
•
Enter a username and password, then the password again in the Enable SSH Password field.
•
Enter any additional usernames and passwords, as needed.
Note
Step 10
You can enter one or more credentials, as needed, for both SNMP versions as well as for
SSH. CloudSync will determine which credentials should be used for which device.
Click Submit Order.
While the discovery is in process, you will see a screen letting you know that the order has been
submitted. Close this screen (using the X in the upper right).
Step 11
To see the new list of discovered network devices, click the Refresh icon (at the upper right corner of the
table), or refresh the entire page.
Connecting or Updating Cloud Infrastructure
When you connect or update a device in the Cloud Infrastructure after it has been discovered, you will
be presented with options on the available inter-connects. Inter-connects are shown for a device to be
registered. They are a list of discovered topological links with the device as one of the termination points.
To update or connect:
Step 1
Select Service Portal from the module drop-down list.
Step 2
Click Setup to display the nested menu.
Step 3
Click Manage Infrastructure.
Step 4
From the menu that appears next along the left of the screen, choose Network Elements.
Step 5
From the icons that display in the Network Elements dropdown list, select Network Devices.
Step 6
Next to any device that you want to connect (register), click on the small grey gear icon. You will see
information appear in a popup that looks something like this:
Figure 5-5
Connect Device Information
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
5-5
Chapter 5
Managing Resources Using Discovery
Discovering Network Devices
Step 7
:Click the Connect Cloud Infrastructure button.
The Connect Cloud Infrastructure form opens.
Step 8
Step 9
Complete the form as suits your needs. Be sure to complete the following required fields:
•
Administrator Username
•
Administrator Password
•
Re-Enter Password
Click Submit.
Assigning Registered Devices to a Network POD
To assign a registered device to a network POD:
Step 1
Choose Service Portal from the module drop-down list.
Step 2
Click Setup to display the nested men.
Step 3
Click Manage Infrastructure.
Step 4
From the menu that appears next along the left of the screen, choose Network Elements.
Step 5
From the icons that display in the Network Elements dropdown list, select Network Devices.
Step 6
Next to any device that you want to assign to a network POD, click on the small grey gear icon.
You will see a popup appear.
Step 7
:Click the Update Cloud Infrastructure button.
Figure 5-6
Update Cloud Infrastructure button
The Update Cloud Infrastructure form opens.
Step 8
Step 9
Complete the form as suits your needs. Be sure to complete the following required fields:
•
Administrator Username
•
Administrator Password
•
Re-Enter Password
Click Submit.
Cisco Intelligent Automation for Cloud User Guide
5-6
OL-29974-01
Chapter 5
Managing Resources Using Discovery
Managing Resources
Managing Resources
This section describes how to use My Servers, System Resources, and CloudSync to view specifications
and status, and discover new virtual and physical servers, blades, blade chassis, and data centers.
Viewing System Resource Capacity
On the System Resources page, view the following information for your infrastructure resources:
Step 1
•
Capacity statistics for virtual clusters and virtual data centers
•
Proportions of blades in the virtual, physical, and maintenance pools
•
Statuses of physical blades in the pool
•
Number of unoccupied slots in the physical blade chassis
Choose Service Portal from the module drop-down list and then click the System Resources tab.
The System Resources portal displays following information
Resource
Description
Virtual Cluster Capacity
Indicates CPU and memory resource capacity and allocation for each
vCenter cluster.
•
Cluster Name
•
CPU Reserved (MHz)
•
CPU Limit (MHz)
•
Memory Reserved (GB)
•
Memory Limit (GB)
•
Last Collected
Data center
Bar graphs illustrating the CPU and memory resource capacity and
allocation of all resources in the vCenter data center.
UCS Blade Pool
Management
Pie chart showing the proportions of Cisco UCS blades in the physical,
virtual, and management pools.
UCS Blade Pool
Management Physical
Pie chart showing the proportions of physical blades in the management
pool that are in of the following states:
•
Available—The blade is not commissioned or in use by end-users
and is available to be commissioned.
•
In Use—The blade is commissioned and in use by end-users.
•
Pending—The blade is in transition between blade pools.
Note
Physical Blade Chassis
Occupancy
For information on Cisco UCS blades and blade pools, see
Managing Blade Pools, page 4-6.
Identifies the number of unoccupied slots in the Cisco UCS chassis.
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
5-7
Chapter 5
Managing Resources Using Discovery
Managing Cloud Infrastructure Discovery
Managing Cloud Infrastructure Discovery
The CloudSync Infrastructure Discovery service provides Cloud Provider Technical Administrators a
means for monitoring cloud infrastructure. The CloudSync service can be used to discover existing and
new instances of the following types of objects:
•
VMware vCenter Datacenter—Clusters, hosts, datastores, Resource pools, portgroups, and VM
templates
•
Cisco Server Provisioner—Operating system templates
•
Cisco UCS Manager—Service profile templates, UCS blades, and UCS VLANs
After discovery, objects are placed into a Discovered state, where some are auto-registered (data centers,
clusters, hosts, resource pools, port groups, and UCS VLANs), and others wait to be managed into
service or rejected. In this transitional state, you can define how the object will be presented to end users
for consumption by providing metadata such as friendly names, descriptions, and some object-specific
elements.
You can take one of the following actions on an object:
•
Register the object so that it is available for use in the cloud system.
•
Put the object on “hold” by placing it into maintenance mode; it is not available for use until it is
registered.
•
Ignore the object if you do not intend it to be used.
These actions place the object into one of three states: Registered, Maintenance, or Ignored. These states
may be changed at a later time. After an object has been registered, an edit action can be performed to
change the display name and the description. After an object has been put in maintenance mode, it can
be reregistered using the Activate action.
The Discovery portal is located on the Manage Cloud Infrastructure tab in the Service Portal module.
The total number of instances of each object, new and existing, appears above the object icon; the
number of new instances, if any, appears in red.
Discovering Objects in the Cloud Infrastructure
On the CloudSync Infrastructure Discovery portal, you have the following options for performing
discoveries:
Step 1
•
Discover all instances of an object (for example, OS Templates)
•
Discover all new and existing instances in a platform element type, that is, VMware vCenter, Cisco
Server Provisioner, or Cisco UCS Manager.
•
Discover all new and existing instances of all objects.
On the CloudSync Infrastructure Discovery portal, click the icon for the object.
A Discover link for the object (for example, Discover OS Templates) appears in the upper right corner
beside Discover All.
Step 2
Click the Discover link to open the Discover Infrastructure form.
Step 3
Click Submit Order.
Cisco Intelligent Automation for Cloud User Guide
5-8
OL-29974-01
Chapter 5
Managing Resources Using Discovery
Managing Cloud Infrastructure Discovery
To discover all instances of a platform element type:
Step 1
Click inside the gray frame for the platform element.
A Discover link for the group (for example, Discover vCenter Cloud Resources) appears in the upper
right corner beside Discover All.
Step 2
Click the Discover link to open the Discover Infrastructure form.
Step 3
Click Submit Order.
To discover all new instances of all objects:
Step 1
Click Discover All in the upper right corner of the portal to open the Discover Infrastructure form.
Step 2
Click Submit Order.
Viewing Discovered Objects in the Infrastructure
View instances of all objects that were added to the system or detected during the last discovery (if any).
To view all instances of an object, click the icon of the object—for example, Clusters. The “Take
Action” grid, listing all of the clusters, and three action buttons (Register, Maintenance, Ignore) appear.
Those buttons that appear in color are active, indicating that their respective services are available; those
in gray are inactive, indicating that their respective services are not available. To customize the columns
that display in the grid, see Customizing Table Views, page 1-13.
Note
The statuses that appear in the grid were detected in the previous discovery (if any) and are not
up-to-date. To obtain current statuses, you must perform discoveries.
An object instance exists in one of the following five statuses:
•
Discovered—The object was detected in the previous discovery, but no action has been taken upon
it yet.
•
Registered—The object has already been registered, but still needs to be processed to add
user-defined fields, such as a friendly name or description. If the object was discovered and
automatically set by the system to Registered state, no action is required.
•
Maintenance—The object is in maintenance mode.
•
Ignored—The object was rejected for use.
•
Not Found—The object, which was previously discovered, was not detected in the latest discovery,
for whatever reason.
Table 5-1
Allowed Transitions
State Name
To:
From:
Discovered
Registered, Ignored, Not Found
Not Found (only when re-discovered)
Registered
Maintenance, Not Found
Discovered, Ignored, Maintenance
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
5-9
Chapter 5
Managing Resources Using Discovery
Validating Platform Configuration
Table 5-1
Allowed Transitions (continued)
State Name
To:
From:
Ignored
Registered, Not Found
Discovered, Registered, Maintenance
Maintenance
Registered, Ignored, Not Found
Registered
Not Found
Discovered (only when re-discovered)
Discovered, Registered, Ignored,
Maintenance
Validating Platform Configuration
If you need to troubleshoot infrastructure or connection settings, you can test the configurations for the
cloud infrastructure (VMware vCenter, Cisco UCS Manager, Cisco Server Provisioner), Cisco Process
Orchestrator, e-mail server, and share (dropbox) location.
Validating Cloud Infrastructure
On the Connection Status portal, the Platform Elements frame displays icons for all three platform
element types. If there are multiple instances of UCS Manager, Cisco Server Provisioner, or both, the
number of instances appears below the icon. For the platform elements, you have two options: Validating
an Individual Platform Element, or Validating All of the Platform Elements Together.
Validating an Individual Platform Element
Perform the following procedure to validate any of the platform element types individually.
Step 1
In Service Portal, click the Connection Status tab to open the Connection Status portal.
Step 2
Click the icon for the platform element that you want to validate.
The Take Action grid and details about the platform appear. The grid displays results of the last
validation (if any).
Step 3
Click the platform element listing in the grid, then click the icon beside Validate to open the Validate
Platform Element form.
Step 4
If multiple instances of the platform element exist, choose the one that you want to validate from the
Name drop-down list.
Step 5
Click Submit Order to send the order and display the order confirmation form.
Step 6
Close the order confirmation form.
After the order is submitted, the system performs the validation.
Step 7
Repeat Step 2 through Step 6 for other platform elements as needed.
Step 8
To view the results when the validation process is complete, return to the Connection Status portal and
click the icon for the platform element. The results display in the grid with the proper time stamp. If the
results do not appear, wait ten minutes, then return or refresh the screen.
Cisco Intelligent Automation for Cloud User Guide
5-10
OL-29974-01
Chapter 5
Managing Resources Using Discovery
Validating Cisco Process Orchestrator and Share Location Settings
Validating All of the Platform Elements Together
Perform the following procedure to validate all of the cloud infrastructure—VMware vCenter Server,
Cisco UCS Manager, and Cisco Server Provisioner—together. To view the results when the validation
process is complete, return to the Connection Status portal and click the icon for the platform element.
The results display in the grid with the proper time stamp. If the results do not appear, wait ten minutes,
then return or refresh the screen.
Step 1
In Service Portal, click the Connection Status tab to open the portal.
Step 2
Click inside the Platform Elements frame.
Step 3
Click the icon beside Validate All Platform Elements to open the form.
Step 4
On the Validate Platform Element form, click Submit Order to send the order and display the order
confirmation form.
Step 5
Close the order confirmation form.
After the order is submitted, the system performs the validations.
Step 6
To view the results when the validation is complete, return to the Validate Platform Configuration portal
and click the icon for the platform element. The results display in the grid with the proper time stamp.
If the results do not appear, wait ten minutes, then return or refresh the screen.
Validating Cisco Process Orchestrator and Share Location
Settings
Step 1
On the Connection Status portal, click the Cisco Process Orchestrator icon.
The Take Action grid and details about Process Orchestrator appear.
Step 2
Click the icon beside Validate Cisco Process Orchestrator to open the form.
Step 3
Click the Cisco Process Orchestrator listing in the grid, then click the icon beside Validate Cisco
Process Orchestrator to open the form.
Step 4
Click Submit Order to send the order and display the order confirmation form.
After the order is submitted, the system performs the validation.
Step 5
Repeat Step 1 through Step 4 for Share Location.
Step 6
To view the results when the validations are complete, return to or refresh the Connection Status portal
and click the icon for the object.
Step 7
The results display in the grid with the proper time stamp.
Note
If the results do not appear, wait ten minutes, then return or refresh the screen.
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
5-11
Chapter 5
Managing Resources Using Discovery
Validating the E-mail Server Connection
Validating the E-mail Server Connection
Perform the following steps to validate the e-mail server connection.
Step 1
On the Connection Status portal, click the E-mail Configuration icon.
The grid and details about e-mail server appear. The grid displays results of the last validation (if any).
Step 2
Click the e-mail server listing in the grid, then click the icon beside Validate E-mail Configuration to
open the form.
Step 3
Enter your valid e-mail address in the Recipient E-mail Address field, then click Submit Order to send
the order and close the form. If the e-mail server connection is valid, you will receive a system e-mail
confirming the validation. If you do not receive the validation confirmation e-mail, check the
configuration of the SMTP server.
Managing Authorization and Review Escalation
Only a Cloud Provider Technical Administrator has the authority to set up and modify authorizations.
Use the instructions in this section to manage authorization and review escalation. An escalation is a
sequence of tasks requiring action from an assigned person.
The tasks are listed in Service Manager for the person to view and take action.
An authorization task requires the assigned authorizer to reject or approve a service request.
Authorization sequences are configurable for:
•
Finance
•
Departments
•
Service Groups
A review task requires an assigned reviewer to sign off on a step in the delivery process. Review
sequences are configurable for:
•
Departments
•
Service Groups
Enabling an Authorization or Review
Step 1
Choose Administration from the module drop-down list and then click Set Up Authorization Process.
Step 2
Click Edit button next to Service Group Authorization.
Step 3
Choose Enabled from the Status drop-down list.
Step 4
Repeat steps 2 and 3 if you need to enable any other Authorizations.
Cisco Intelligent Automation for Cloud User Guide
5-12
OL-29974-01
Chapter 5
Managing Resources Using Discovery
Validating the E-mail Server Connection
Setting Up Escalation Sequences
An escalation sequence is a series notifications triggered when a task remains incomplete within
specified time limits. When a task has not been completed within the specified time, the cloud system
sends an e-mail notification to the assigned person, supervisor, and/or customer for resolution.
If the task remains incomplete after the first notification, the process is repeated for the next tier.
•
For authorizations, you can specify different notification recipients for each tier in the escalation.
•
For reviews, all identified recipients receive notifications for each tier. You can configure one or
more tiers.
Step 1
Follow the steps outlined in Enabling an Authorization or Review, page 5-12.
Step 2
Click Edit beside an authorization group in the list.
Step 3
In the Escalations panel, click Add, then provide the following information:
Field Name
Action
After (hours)
Enter the number of hours to elapse between escalations. For example, if this
value is 8, then a notification will be sent every 8 hours until the task is resolved.
Note
First Recipient
Second Recipient
Third Recipient
This value does not represent the number of hours after the due date that
the first tier in the escalation is executed.
Enter up to three valid e-mail addresses, separated by commas, of the persons
who will receive notifications during escalation. You can also use namespace
variables. For information on using namespaces, see the Cisco Service Portal
Namespace Users Guide.
You can configure as many tiers as needed. To add more tiers, click Add, and
repeat this step for adding recipients and templates.
E-mail notification
template
For each recipient, choose an e-mail template to use for the notification from the
drop-down list.
To modify an e-mail notification template, see Modifying E-mail Notification
Templates, page 7-7.
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
5-13
Chapter 5
Managing Resources Using Discovery
Validating the E-mail Server Connection
Cisco Intelligent Automation for Cloud User Guide
5-14
OL-29974-01
CH A P T E R
6
Managing Physical Servers, Virtual Machines,
and Virtual Device Centers
Cisco Prime Service Catalog hosts the customer-facing element of Cisco IAC 4.0, where users log in and
order services. This module provides information and steps for commissioning and decommissioning
servers, and describes management tasks on deployed virtual machines (VMs), as well as virtual device
centers (VDCs).
Working with Physical Servers
Commissioning a Physical Server
Deploy a physical server with Windows or Linux operating system installed.
Note
Virtual Server Owners do not have permissions to order physical servers.
Step 1
Choose Service Portal from the module drop-down.
Step 2
Select My Cloud > My Servers.
Step 3
On the Order Cloud Services portal, click Order a Physical Server.
Step 4
On the Order a Physical Server form, choose or enter the information shown in the following table.
Field
Action
VDC
Choose a VDC to deploy the server into. Your selection
populates the display only fields such as:
•
Current Number of Virtual Servers Available
•
Current vCPUs Available
•
Current Storage Available (GB)
•
Current Memory Available (GB)
Operating system family
Choose Windows or Linux
Operating system
Choose platform and version number of the operating system
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
6-1
Chapter 6
Managing Physical Servers, Virtual Machines, and Virtual Device Centers
Managing Power Settings for Physical Servers
Operating System Template
Choose the template that you want to use to create the new
physical server. (The selections in this drop-down depend on
the operating system that you select.) Only Operating System
Templates that are registered for the Cisco Server Provisioner
as the VDC POD are shown.
Cisco UCS Service Profile Template
Choose the UCS server profile template that you want to use to
create the new physical server. (The selections in this
drop-down depend on the operating system that you select.)
To register a UCS service profile template, see Modifying
E-mail Notification Templates, page 7-7.
Computer Name (Host)
Enter a name for the new server. The name must be unique. I
Computer time zone
Choose the time zone of the physical location of the new server.
Deploy to Network
Choose a network whose static IP address will be assigned to
the new virtual machine.
Term
Choose a lease term: 1 month, 3 months, 6 months, 9 months,
or 12 months. Your selection populates the display-only fields
# of Days For Lease, Lease Expiration Date, Storage
Expiration Date.
For more information server lease terms and expiration dates,
see Managing Server Leases, page 4-3.
Enter password
Re-enter password
Enter and re-enter a password that you will need to configure
the new server on fulfillment.
The password must conform to company and domain policy or
the provisioning may fail during configuration.
Step 5
Click Submit Order.
Managing Power Settings for Physical Servers
Powering Down a Physical Server
Power down an active physical server, regardless of its operating system state. (For information on
removing a physical server from use, see Decommissioning a Physical Server, page 1-5.)
Step 1
Choose Service Portal from the module drop-down list.
Step 2
Click My Cloud > My Servers.
Step 3
On the My Servers portal, locate and click the physical server that you want to power down.
Step 4
In the Take Action panel, click the Power Down icon.
Cisco Intelligent Automation for Cloud User Guide
6-2
OL-29974-01
Chapter 6
Managing Physical Servers, Virtual Machines, and Virtual Device Centers
Managing Power Settings for Physical Servers
The Power Down Physical Machine form displays the name of the server.
Step 5
In the Confirm Action area, check the check box if you are sure the selected server is the one that you
want to power down.
Step 6
Click Submit Order.
Power-cycling a Physical Server
Step 1
Choose Service Portal > My Cloud > My Servers.
Step 2
On the My Servers portal, locate and click the physical server that you want to power cycle.
Step 3
In the Take Action panel, click the Power Cycle icon.
The Power Cycle Physical Machine form displays the name of the server.
Step 4
In the Confirm Action area, check the check box if you are sure the selected server is the one that you
want to power cycle.
Step 5
Click Submit Order.
Powering Up a Physical Server
Power up a physical server and start the boot process.
Step 1
Choose Service Portal > My Cloud > My Servers.
Step 2
On the My Servers portal, locate and click the physical server that you want to power up.
Step 3
In the Take Action panel, click the Power Up icon.
Step 4
Click Submit Order.
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
6-3
Chapter 6
Managing Physical Servers, Virtual Machines, and Virtual Device Centers
Working With Virtual Machines
Decommissioning a Physical Server
Power down and permanently remove an existing physical server, including power off, from the Cloud
resource pool, and release all associated resources for re-use.
Step 1
Choose Service Portal from the module drop-down and click the My Servers tab.
Step 2
On the My Servers portal, locate and click the name of the physical server that you want to
decommission.
Detailed information about the server and icons for performing actions appear in the Take Action panel.
Step 3
Click the Decommission icon.
The Decommission Physical Server form displays the computer name, time zone, and operating system.
Step 4
Check the Yes radio button to confirm the decommission.
Step 5
Click Submit Order.
Working With Virtual Machines
Commissioning a Virtual Machine
Deploying a virtual machine using a template with preconfigured settings.
Note
For more information on templates in Cisco IAC 4.0, see Chapter 7, “Managing Templates.”
Step 1
Choose Service Portal from the module drop-down.
Step 2
Click My Cloud > Order Services. The Order Services portal displays:
Cisco Intelligent Automation for Cloud User Guide
6-4
OL-29974-01
Chapter 6
Managing Physical Servers, Virtual Machines, and Virtual Device Centers
Working With Virtual Machines
Figure 6-1
•
Order Services Portal
On the Order Services portal, there are four choices:
– Order a Virtual Machine from a Template. Order a new virtual machine from a template you
select.
– Order a Virtual Machine and Install an OS. Order a new virtual machine running either the
Windows or Linux operating system.
– Order a Physical Server. Order a physical server in the cloud, running either the Windows or
Linux operating system.
– Order a Virtual Data Center. Order a dedicated deployment environment with compute,
network and storage resources.
Step 3
Click Order a Virtual Machine From Template.
Step 4
On the Order a Virtual Machine From Template form, choose or enter the information shown in the
following table.
Field
Action
VDC
Choose the VDC to deploy the server into. Your selection populates the
display only fields such as:
•
Current Number of Virtual Servers Available
•
Current vCPUs Available
•
Current Storage Available (GB)
•
Current Memory Available (GB)
Operating system family
Choose Windows or Linux
Operating system
Choose platform and version number of the operating system
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
6-5
Chapter 6
Managing Physical Servers, Virtual Machines, and Virtual Device Centers
Working With Virtual Machines
VM template
Choose the template that you want to use to create the new virtual
machine. (The selections in this drop-down depend on the operating
system that you select.)
Only VM Templates that are registered and in the same data center as
the VDC POD are shown.
To register an VM template, see Registering a Virtual Machine
Template, page 7-2.
Computer Name (Host)
Enter a name for the new virtual machine. The name must be unique.
Virtual Machine Size
Choose a server size form the drop-down list. Your selection populates
the display-only fields vCPUs and vRAM (GB).
Note
The vCPU and vRAM values are set for each server size option
and cannot be changed individually. To view the vCPUs and
vRAM (GB) values for an option, select the option from the
drop-down list. The values automatically populate the
display-only fields immediately under the drop-down list.
Deploy to Network
Choose a network whose static IP address will be assigned to the new
virtual machine.
Term
Choose a lease term: 1 month, 3 months, 6 months, 9 months, or 12
months. Your selection populates the display-only fields # of Days For
Lease, Lease Expiration Date, and Storage Expiration Date.
For more information server lease terms and expiration dates, see
Managing Server Leases, page 4-3.
Enter password
Re-enter password
Enter and then re-enter a password that you will need to configure the
new server on fulfillment.
The password must conform to company and domain policy or the
provisioning may fail during configuration.
Step 5
When you are finished, click Submit Order.
Using EC2 Windows VMs Without Keypairs
This section details the steps required to create a Windows AMI with a known Administrator password.
The password needs to be known so that when you order an EC2 VM without a keypair, you will still
have valid login credentials. To order and use the EC2 Windows VMs without keypairs, follow the steps
below.
Step 1
Launch an Instance of Windows AMI provided by AWS.
Step 2
Navigate to Launch Instance in the Amazon Web Services (AWS) console.
Step 3
Select the Quick Start tab, then select a Windows AMI.
Step 4
Follow the prompt to order the VM. Make sure that you get a keypair for this VM.
Step 5
Once the VM is operational, RDP to the VM.
•
Use the Keypair to get the Windows Password.
Cisco Intelligent Automation for Cloud User Guide
6-6
OL-29974-01
Chapter 6
Managing Physical Servers, Virtual Machines, and Virtual Device Centers
Working With Virtual Machines
Step 6
Once you are logged into the VM, navigate to EC2ConfigService Settings (found via the Windows Start
Menu).
•
Select the Image tab.
•
In the Administrator Password section, click the Specify (Stores in Sysprep answer file as clear
text) radio button.
•
Enter a password in the text box directly to the right of the field.
Note
•
Step 7
Step 8
Click OK to save the changes
Navigate to the AWS console again.
•
Select the Instances tab.
•
Right-click on the Windows Instance that you were RDP’ed into.
•
Click Create Image and follow the prompts.
After the image is created, order an EC2 Instance using that image.
Note
Step 9
This will be the password used later in this procedure as the Windows Administrator password.
Make sure you order the VM with Elastic IP. Do not associate a keypair with that VM.
Once the VM is operational, RDP in using the login credentials as follows:
•
Login: Administrator
•
Password: the one you specified in Step 6.
Note
You can use this Image to order VMs. The Windows password will always be the one you
specified in Step 6.
Decommissioning a Virtual Machine
Power-off and permanently remove an existing virtual machine from the Cloud resource pool, and
release all associated resources for re-use.
Step 1
Choose Service Portal from the module drop-down. Then click My Cloud > My VDCs.
Step 2
On the My Servers portal, locate and click the name of the virtual machine that you want to
decommission.
Detailed information about the virtual machine and icons for performing actions appear in the Take
Action panel.
Step 3
Click the Decommission VDC icon.
The Decommission Virtual Machine form displays the computer name, full path, and operating system.
Step 4
Click the Yes check box to confirm the decommission.
Step 5
Click Submit Order.
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
6-7
Chapter 6
Managing Physical Servers, Virtual Machines, and Virtual Device Centers
Working With Virtual Machines
Installing an Operating System
Adding an operating system to your VM.
Step 1
Choose Service Portal from the module drop-down list.
Step 2
Select My Cloud > My VDCs.
Figure 6-2
Step 3
On the My VDCs portal, click Install OS.
Figure 6-3
Step 4
My VDCs: Sample View
VDC Buttons: Image Changes and Help Text Appears When You Mouse Over
On the Order a Virtual Machine and Install an OS form, specify the following information.
Field
Action
VDC Name
Choose the VDC to deploy the server into. Your selection populates the
display only fields such as:
•
Current Number of Virtual Servers Available
•
Current vCPUs Available
•
Current Storage Available (GB)
•
Current Memory Available (GB)
Guest Operating System
Family
Choose Windows or Linux.
Operating System
Choose platform and version number of the operating system.
Operating System Template Choose the template that you want to use to create the new virtual
machine. (The selections in this drop-down depend on the operating
system that you select.) Only Operating Systems Templates that are
registered for the Cisco Server Provisioner as the VDC POD are shown.
Computer Name (Host)
Enter a unique name for the new virtual machine.
Cisco Intelligent Automation for Cloud User Guide
6-8
OL-29974-01
Chapter 6
Managing Physical Servers, Virtual Machines, and Virtual Device Centers
Working With Virtual Machines
Field
Action
Virtual Machine Size
Choose a server size form the drop-down list. Your selection populates
the display-only fields vCPUs and vRAM (GB).
Note
The vCPU and vRAM values are set for each server size option
and cannot be changed individually. To view the vCPUs and
vRAM (GB) values for an option, select the option from the
drop-down list. The values automatically populate the
display-only fields immediately under the drop-down list.
Deploy to Network
Choose a network whose static IP address will be assigned to the new
virtual machine. Your selection populates display-only fields for
Network Selection, Routing Prefix, Subnet Mask, Address, Broadcast
Address, vCenter Network Path, and UCS Network Description.
Lease Term
Optional. Choose a lease term from the drop-down list. Your selection
populates the display-only fields # of Days For Lease, Lease Expiration
Date, and Storage Expiration Date.
For more information server lease terms and expiration dates, see
Managing Server Leases, page 4-3.
Enter password
Re-enter password
Step 5
Enter and then re-enter a password that you will need to configure the
new server on fulfillment. The password must conform to company and
domain policy or the provisioning may fail during configuration.
Click Submit Order.
Viewing Server Status and Properties
The My Servers portal provides information about all of your active servers. You can monitor status,
manage snapshots, verify that a server you that ordered has been delivered, and manage power, modify
configuration, take snapshots, decommission, and extend an existing lease.
Step 1
Choose Service Portal from the module drop-down list. Then select My Cloud > My Servers.
The My Servers portal displays active servers in a table with information about each server, including
type (virtual or physical), operating system, organization, and Server Owner. Additional columns are
available. To add columns to the table, and to re-sort the rows, see Customizing Table Views, page 1-13.
Step 2
To display more details about a server or take action (see list of actions below), click the server name in
the My Servers table to display the Take Action panel.
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
6-9
Chapter 6
Managing Physical Servers, Virtual Machines, and Virtual Device Centers
Working With Virtual Machines
Figure 6-4
Take Action Panel for VMs
To take action on a server, click its name, then click one of the following icons in the Take Action pane:
Server Operations
•
Power Down Virtual Machine—See Powering Down a Virtual Machine, page 6-11
•
Power Cycle Virtual Machine—See Power-Cycling a Virtual Machine, page 6-12
•
Power Up—See Powering Up a Virtual Machine, page 6-11
•
Modify Configuration (Virtual machines only)—See Changing the Server Size of a Virtual Machine,
page 6-11
•
Decommission Virtual Machine—See Decommissioning a Virtual Machine, page 1-3 or
Decommissioning a Physical Server, page 1-5
•
Modify Server Ownership—See Extending or Removing a Server Lease, page 4-4
Lifecycle Management
•
Take Snapshot, Revert to Snapshot, or Delete Snapshot (Virtual machines only)—See Taking a
Snapshot of a Virtual Machine, page 6-12, Viewing Snapshots, page 6-13, and Deleting a Snapshot,
page 6-13
Network Services
Note
•
Create VM Firewall Rule, Delete Server Firewall Rule
•
Manage Load Balancer
•
Add to Server Group, Remove from Server Group
If a server is in the process of being provisioned, all of the icons are disabled.
Cisco Intelligent Automation for Cloud User Guide
6-10
OL-29974-01
Chapter 6
Managing Physical Servers, Virtual Machines, and Virtual Device Centers
Working With Virtual Machines
Changing the Server Size of a Virtual Machine
Change the vCPU and vRAM (GB) sizes of a virtual machine. To commission a virtual machine, see
Commissioning a Virtual Machine and Installing an Operating System, page 1-1 and Commissioning a
Virtual Machine from a Template, page 1-2. The vCPU and vRAM values are set for each server size
option and cannot be changed individually. Available server size options are customizable by
Administrators, and so may vary from the default options that ship with Cisco IAC. To view the vCPU
and vRAM values for a server size option, choose the option from the drop-down list. The vCPU and
vRAM values automatically populate the display-only fields below the drop-down list.
Step 1
Choose Service Portal > My Cloud > My Servers.
Step 2
On the My Servers portal, locate and click the server in the My Servers panel.
Step 3
In the Take Action panel, click the Modify Configuration icon.
Step 4
On the Modify Configuration form, choose a size from the Virtual Machine Size drop-down list.
Step 5
Click Submit Order.
Powering Down a Virtual Machine
Power down an active virtual machine, regardless of its operating system state. To remove a server from
use, see Decommissioning a Virtual Machine, page 1-3.
Step 1
Choose Service Portal > My Cloud > My Servers.
Step 2
On the My Servers portal page, click the name of the virtual machine to display the Take Action panel.
Step 3
Click the Power Down icon to open the Power Down Virtual Machine form.
Step 4
In the Confirm Action area, click the Confirm This Action radio button if you are sure the selected server
is the one that you want to power down.
Step 5
Click Submit Order.
Powering Up a Virtual Machine
Power up a virtual machine that has been powered-down, and start the boot process.
Step 1
Choose Service Portal > My Cloud > My Servers.
Step 2
On the My Servers portal page, click the name of the virtual machine to display the Take Action panel.
Step 3
Click the Power Up icon to open the Power Up Virtual Machine form.
Step 4
If you are sure the selected server is the one that you want to power up, click Submit Order.
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
6-11
Chapter 6
Managing Physical Servers, Virtual Machines, and Virtual Device Centers
Working With Virtual Machines
Power-Cycling a Virtual Machine
Use the power-cycle service to power-down a virtual machine, regardless of its operating system state,
then power it up and start the boot process.
Step 1
Choose Service Portal > My Cloud > My Servers.
Step 2
On the My Servers portal page, click the name of the virtual machine to display the Take Action panel.
Step 3
Click the Power Cycle icon to open the Power Cycle Virtual Machine form.
Step 4
In the Confirm Action area, check the check box if you are sure the selected server is the one that you
want to power cycle.
Step 5
Click Submit Order.
Taking a Snapshot of a Virtual Machine
Create, name, and store an image of the state of a virtual machine.
Step 1
Choose Service Portal > My Cloud > My Servers.
Step 2
On the My Servers portal page, click the name of the virtual machine to display the Take Action panel.
Step 3
Click the Take Snapshot icon to open the Take Snapshot form.
Step 4
In the snapshot name field, enter a unique and descriptive name for the snapshot.
Step 5
Enter a description of the snapshot.
Step 6
Click Submit Order.
Reverting a Virtual Machine Settings to Snapshot
Revert a virtual machine to a previous state using the snapshot of your choice.
Step 1
Choose Service Portal > My Cloud > My Servers.
Step 2
On the My Servers portal page, click the name of the virtual machine to display the Take Action panel.
Step 3
Click the Revert Snapshot icon to open the Revert to Snapshot form.
Step 4
From the Snapshot name drop-down list, choose the snapshot to which you want to revert the selected
virtual machine.
Step 5
Check the Confirm This Action check box if you are sure that you want to revert the virtual machine to
the snapshot, then click Submit Order.
Cisco Intelligent Automation for Cloud User Guide
6-12
OL-29974-01
Chapter 6
Managing Physical Servers, Virtual Machines, and Virtual Device Centers
Working with Virtual Data Centers
Viewing Snapshots
View the history of snapshots taken of virtual machines within an organization. From the list, you can
view history and related services of a snapshot.
Step 1
Choose Service Portal > My Cloud > My Servers.
Step 2
On the My Servers portal page, click the name of the virtual machine to display the Take Action panel.
Step 3
Click the View Snapshots icon to open the View Snapshot form
Deleting a Snapshot
Step 1
Choose Service Portal > My Cloud > My Servers.
Step 2
On the My Servers portal page, click the name of the virtual machine to display the Take Action panel.
Step 3
Click the Delete Snapshot icon to open the Delete Snapshot form.
Step 4
From the Snapshot name drop-down list, choose the snapshot to which you want to revert the selected
virtual machine.
Step 5
Click Submit Order
You will receive an e-mail on the snapshot of the virtual machine that is now deleted.
Working with Virtual Data Centers
A virtual data center (VDC) can be used by server owners in an organization to provision virtual and
physical servers. Virtual data centers live in a POD and has datastores, resource pools, and community
networks as resources associated to them. Multiple virtual data centers can be ordered by an organization
for server owners to provision servers in.
Note
The POD type you choose can be any of these POD types: VMware vCenter, UCSD, Amazon EC2, or
OpenStack.
Figure 6-5
The VDC Manage Popup
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
6-13
Chapter 6
Managing Physical Servers, Virtual Machines, and Virtual Device Centers
Working with Virtual Data Centers
A virtual data center has an associated size that determines limits for the number of virtual servers,
physical servers, vCPUs, CPU MHz, storage, and memory. Limits are enforced by comparing the sum
of the number of provisioned virtual and physical servers and the vCPUs, memory, and storage for a
server size against the limits defined for the virtual data center size.
A VMware resource pool is created for each virtual data center. This allows further control of resource
utilization by defining CPU and memory limits, as well as CPU and memory reservations in the VMware
resource pool.
You must be either an Organization Technical Administrator or Cloud Provider Technical Administrator
to create a virtual data center. Create Virtual Data Center ordered by an Organization Technical
Administrator or a Tenant Technical Administrator requires authorization by the Cloud Provider
Technical Administrator.
Warning
Note
You can only add a VDC if the datacenter has a cluster. Cisco IAC does not support data centers with
1 host (no cluster). Therefore, when you register a compute POD with connection to Vcenter
datacenter, that datacenter must have one or more clusters.
Cisco IAC supports an individual’s membership to a single organizational unit or membership (not
multiple).
Creating a Virtual Data Center
The following procedure shows an Organization Technical Administrator ordering a virtual data center.
If the Cloud Provider Technical Administrator orders the Create a Virtual Data Center service, all the
fields that are available during authorization moment will be visible during the ordering moment and the
requisition will not wait for the authorization.
Step 1
Choose Service Portal from the module drop-down list, the My Cloud > My VDCs.
Step 2
Click the Create Virtual Data Center link:
Figure 6-6
Create Virtual Data Center Link
Step 3
On the Create Virtual Data Center form, select the Tenant Name.
Step 4
Select the Organization Name.
Step 5
Then specify the following information:
Field
Action
VDC Name
Enter a descriptive name for the virtual data center. This name will be
displayed when the server owners select the virtual data center.
Description
Enter a description for the virtual data center.
Cisco Intelligent Automation for Cloud User Guide
6-14
OL-29974-01
Chapter 6
Managing Physical Servers, Virtual Machines, and Virtual Device Centers
Working with Virtual Data Centers
Field
Action
Size
Select the size of the virtual data center. The size determines the maximum
limits for the number of virtual servers, maximum number
Compute Pod
Select the POD in which to place the virtual data center.
Select a Network Service Choose the type of network service from the drop-down list.
Number of Networks
Radio button
Step 6
Read-only
•
Provision New Networks
•
Select from existing Networks
Number of Networks
A virtual data center can contain multiple networks. Select the number of
networks for this virtual data center. If more than one network is selected,
additional Add Network sections will be displayed on the form.
Max Hosts
Select the number of hosts needed per network. This is used to determine
the size of the network that will be assigned to the virtual data center.
Click Submit Order.
The requisition will go to the Cloud Provider Technical Administrator for approval.
Obtaining Approvals for Creating a Virtual Data Center
When an Organization Technical Administrator submits a requisition for Order a Virtual Data Center, it
goes the CPTA’s Cloud Service Approval Administrator queue for approval. The Cloud Provider
Technical Administrator must assign a POD, cluster, datastore, and networks for the virtual data center,
as part of the approval process.
Step 1
Choose Service Portal from the module drop-down list; then click Cloud Operations > Approvals.
Step 2
Click the order number in the Order # column to create a virtual data center requisition that requires
approval. This brings up the requisition form.
Step 3
Select the POD that this virtual data center should be created on. The POD selection should be based on
the virtual data center size selected and available capacity in the POD.
Step 4
Select the cluster that this virtual data center should be created on. The cluster selection should be based
on the virtual data center size selected and available capacity in the cluster. A single cluster can host
multiple virtual data centers.
Step 5
Select the datastore that this virtual data center will use. The datastore selection should be based on the
virtual data center size selected and available capacity of the datastore. A single datastore can be
associated with multiple virtual data centers.
Step 6
You can also change the CPU reservation in MHz for the virtual data center resource pool. The default
value is based on the VDC Size selected. This corresponds directly to the VMware resource pool CPU
reservation.
Step 7
You can also change the memory reservation in GB for the virtual data center resource pool. The default
value is based on the VDC Size selected. This corresponds directly to the VMware resource pool
memory reservation.
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
6-15
Chapter 6
Managing Physical Servers, Virtual Machines, and Virtual Device Centers
Working with Virtual Data Centers
Step 8
Select the network name that should be assigned to the virtual data center. The networks that are shown
in the list are non-community, user networks. The network selection should be based on the Hosts per
Network specified in the requisition.
Step 9
Optionally, a management network can be associated with a virtual data center. If desired, select a
management network for the virtual data center. The management network subnet size should be the
same as the user network size.
Step 10
If the virtual data center has more than one network, repeat steps 8-9 for each network.
Step 11
Click Update to update the requisition with the VDC resource assignment information.
Step 12
Click Approve.
Decommissioning a Virtual Data Center
You must be an Organization Technical Administrator (OTA) or a Cloud Provider Technical
Administrator (CPTA) to perform this action. Note that all networks, virtual machines, and physical
machines must be removed from the virtual data center prior to decommissioning.
Step 1
Choose Service Portal from the module drop-down list, the My Cloud > My VDCs.
Step 2
Locate the virtual data center in the grid, then click the name.
Step 3
In the Manage Virtual Data Center collapsible panel, click on Decommission VDC. In the modal
window that follows, the VDC Name field will be prepopulated with the selected virtual data center
name.
Step 4
Click the radio button to confirm action.
Step 5
Click Submit Order.
Calculating Virtual Data Center Size Requirements
Step 1
Choose Service Portal from the module drop-down list, the System Setup> VDC Calculator.
Step 2
Complete all four steps on the VDC Calculator (see Figure 6-7 on page 6-17):
•
Step 1. Planned VDC VM Limit: Enter the total number of virtual machines in the Planned VDC
VM Limit field.
•
Step 2. Planned VM Distribution: Enter names for each VM size as well as the respective virtual
machine percentages for the planned VDC VM Limit, such as “Small,” “Medium,” and “Large.”
•
Step 3. Planned VM Configuration: Enter respective virtual machine configuration attributes for
each size you entered in Step 3.
– VM Quantity
– CPU Count
– Memory (GB)
– Storage (GB)
– MHz allocated per vCPU
Cisco Intelligent Automation for Cloud User Guide
6-16
OL-29974-01
Chapter 6
Managing Physical Servers, Virtual Machines, and Virtual Device Centers
Working with Virtual Data Centers
– Snapshots per VM
•
Step 4. Suggested VDC Package: Here, CIAC returns the recommended configuration, which
includes:
– Total vCPUs
– Total Memory (GB)
– Total Storage (GB)
– Total MHz
Figure 6-7
The VDC Calculator
This calculator does
nothing; it is only here
as a design element.
Step 3
Close the VDC Calculator when you are done.
Modifying Virtual Data Center Size
Modify VDC size allows the virtual data center size to be increased. The VDC size can only be increased
not decreased. Changing the VDC size changes the corresponding memory and CPU limits and
reservations in the VMware resource pool.
To change the resource pool size of a deployed virtual data center, complete the following steps:
Step 1
Choose Service Portal from the module drop-down list, the My Cloud > My VDCs.
Step 2
Locate the Virtual Data Center in the grid, then use the Take Action panel (click the “gear” icon) to take
action as needed on the selected server(s).
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
6-17
Chapter 6
Managing Physical Servers, Virtual Machines, and Virtual Device Centers
Working with Virtual Data Centers
Figure 6-8
Step 3
The Take Action Panel for Managing VMs and VDCs
In the Manage Virtual Data Center collapsible panel, click on Modify VDC Size.
In the modal window that follows the Name field will be prepopulated with the selected virtual data
center name. The current size and size settings populate the remaining fields.
Step 4
Choose a new size from the VDC Size drop-down list.
Step 5
If needed, change the Maximum Snapshots per VM, CPU Reservation (MHz), Memory Reservation
(GB).
Step 6
Click Submit Order.
Viewing Virtual Data Center Details
Step 1
Choose Service Portal from the module drop-down list, the My Cloud > My VDCs.
Step 2
Locate the Virtual Date Center in the grid, then click the name.
There is a tab panel at the bottom of the page. When you select a virtual data center, the Virtual Data
Center Details tab is displayed. There are three sections in this tab:
•
Virtual Data Center Details shows the following details for the selected virtual data center:
– Name of the virtual data center
– The POD associated to the selected virtual data center
– The Cluster associated to the selected virtual data center (NOTE: Only visible to the Cloud
Provider Technical Administrator)
– The Datastore associated to the selected virtual data center (NOTE: Only visible to the Cloud
Provider Technical Administrator)
– The Resource Pool associated to the selected virtual data center (NOTE: Only visible to the
Cloud Provider Technical Administrator)
– The amount of CPU (MHz) Reservation associated to the Resource Pool in which the virtual
data center is located (Only visible to the Cloud Provider Technical Administrator)
– The amount of Memory (GB) Reservation associated to the Resource Pool in which the virtual
data center is located (Only visible to the Cloud Provider Technical Administrator)
– The CPU limit (MHz) associated to the selected virtual data center
– The total number of allocated Physical Servers versus the total number of available Physical
Servers within the selected virtual data center.
– The total number of allocated Virtual Machines versus the total number of available Virtual
Machines within the selected virtual data center.
– The total number of allocated Virtual CPUs (MHz) versus the total number of available Virtual
CPUs (MHz) within the selected virtual data center.
Cisco Intelligent Automation for Cloud User Guide
6-18
OL-29974-01
Chapter 6
Managing Physical Servers, Virtual Machines, and Virtual Device Centers
Working with Virtual Data Centers
– The total number of allocated Memory (GB) versus the total number of available Memory (GB)
within the selected virtual data center.
– The total number of allocated Storage (GB) versus the total number of available Storage (GB)
within the selected virtual data center.
– The maximum number of snapshots allowed within the selected virtual data center.
If any of the above fields are blank, no data to display will be shown.
Note
•
Network
– Lists the total number of networks associated to the selected virtual data center.
– Lists the name of each individual network when there are networks associated to the selected
virtual data center.
•
Network IP Address Utilization
– A pie chart displaying the total number of all the IP addresses assigned and all the IP addresses
that are unassigned. (
Note
If the values of both assigned and unassigned are zero, then no pie chart will be displayed.
In its place, you will see the text, “No data to display.”
Viewing Virtual Data Center Capacity Charts
To view charts depicting allocated resources versus total available for allocation:
Step 1
Choose Service Portal from the module drop-down list, then click My Cloud > My VDCs.
Step 2
Locate the Virtual Data Center in the grid, then click the name.
Figure 6-9
Step 3
Utilization Chart
In the tab panel located at the bottom of the page, click the Virtual Data Center Capacity tab.
The following charts will populate:
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
6-19
Chapter 6
Managing Physical Servers, Virtual Machines, and Virtual Device Centers
Working with Virtual Data Centers
•
A pie chart showing the total number of virtual machines ordered versus the total number of physical
servers ordered within the selected virtual data center.
•
A bar chart showing the total number of physical servers allocated with a circular point indicating
the limit (maximum number of) allowed within the virtual data center.
•
A bar chart showing the total number of virtual machines allocated with a circular point indicating
the limit (maximum number of) allowed within the virtual data center.
•
A bar chart showing the total number of virtual machine CPUs (MHz) allocated with a circular point
indicating the limit allowed within the virtual data center.
•
A bar chart showing the total number of virtual machine Memory (GB) allocated with a circular
point indicating the limit (maximum number of) allowed within the virtual data center.
•
A bar chart showing the total number of virtual machine Storage (GB) allocated with a circular point
indicating the limit (maximum number of physical servers) allowed within the virtual data center.
Cisco Intelligent Automation for Cloud User Guide
6-20
OL-29974-01
CH A P T E R
7
Managing Templates
Cisco Intelligent Automation for Cloud 4.0 provides the following types of server templates that users
can select when they order servers.
•
Virtual machine (VM) template (see Managing Operating System Templates, page 7-1)
•
Operating system from Cisco Server Provisioner (see Managing Operating System Templates,
page 7-1)
•
UCS service profile template (see Managing Server Templates, page 7-2)
•
E-mail notification templates (see Managing E-mail Templates, page 7-4)
•
Authorization and review escalation (see Managing Authorization and Review Escalation,
page 5-12
Virtual machine, operating system, and UCS service profile templates are discovered and registered
using the CloudSync Infrastructure Discovery portal. See Managing Cloud Infrastructure Discovery,
page 5-8. After registering, the templates are then uniformly available to all users.
Managing Operating System Templates
Use the instructions in this section to manage your operating system templates.
Registering an Operating System Template
For information about registering operating system templates, see Registering an Operating System
Template, page 7-3.
Maintaining an Operating System Template
The Cloud Provider Technical Administrator can change the state of an operating system template to
Maintenance to keep the template ready, but not be used for new servers within the Cisco IAC system.
The template must be in Registered state to set it to Maintenance. To set the operating system template
to Maintenance when already Registered:
Step 1
Choose Service Portal from the module drop-down list.
Step 2
Select System Setup.
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
7-1
Chapter 7
Managing Templates
Managing Server Templates
Step 3
Select Manage Infrastructure.
Step 4
Click the OS Templates icon.
Step 5
Select the line item you wish to set to Maintenance in the grid, and select the Maintenance button.
Step 6
Click Submit Order.
Ignoring an Operating System Template
The Cloud Provider Technical Administrator can change the state of an operating system template to
Ignored to administratively ignore a template.
The template may be in Discovered, Registered, or Maintenance states to set it to Ignored. If the record
was previously in Registered or Maintenance states, metadata on that record will be saved.
To set the operating system template to Ignored:
Step 1
Choose Service Portal from the module drop-down list and then click Manage Cloud Infrastructure.
Step 2
Click the OS Templates icon.
Step 3
Select the line item you wish to set to Ignored in the grid, and select the Ignore button.
Step 4
Click Submit Order.
Managing Server Templates
Cisco IAC provides the following types of server templates that users can select when they order servers.
•
Virtual machine (VM) template
•
Operating system (from Cisco Server Provisioner)
•
UCS service profile template
All three types of server templates are discovered and registered using the CloudSync Infrastructure
Discovery portal. After registering, the template is then uniformly available to all users.
Registering a Virtual Machine Template
The Cloud Provider Technical Administrator (CPTA) can Register an existing virtual machine (VM)
template in the cloud system for users to select when ordering virtual machines.
The template may be in Discovered, Maintenance, or Ignored states to be changed to Registered.Register
an existing virtual machine template in the cloud system for users to select when ordering virtual
machines. Before you can register a VM template, it must first be defined in vCenter and discovered
using the CloudSync Infrastructure Discovery portal.
Step 1
Choose Service Portal from the module drop-down list and then click Manage Cloud Infrastructure.
Step 2
Click the VM Templates icon.
Cisco Intelligent Automation for Cloud User Guide
7-2
OL-29974-01
Chapter 7
Managing Templates
Managing Server Templates
Step 3
Select the line item you wish to register in the grid, then select the Register button.
Step 4
In Register VM Template, select the Operating System Family, then the Operating System.
Step 5
Enter a friendly name in Display Name.
Step 6
Enter a description in Description.
Step 7
Click Submit Order.
Registering an Operating System Template
The Cloud Provider Technical Administrator (CPTA) can Register an existing operating system template
in the cloud system for users to select when ordering servers. The template may be in Discovered,
Maintenance, or Ignored states to change it to Registered.
Note that before you can register an operating system template, it must first be defined on the CSP server
and discovered using the CloudSync Infrastructure Discovery portal.
Step 1
Choose Service Portal from the module drop-down list and then click Manage Cloud Infrastructure.
Step 2
Click the OS Templates icon.
Step 3
Select the line item you wish to register in the grid, and select the Register button.
Step 4
In Register Operating System Template, select the Operating System.
Step 5
Enter a friendly name in Display Name.
Step 6
Enter a description in Description.
Step 7
Click Submit Order.
Registering a UCS Service Profile Template
The Cloud Provider Technical Administrator (CPTA) can Register an existing UCS service profile
template in the cloud system for users to select when ordering servers. The template may be in
Discovered, Maintenance, or Ignored states to change it to Registered. Before you can register a UCS
Service Profile Template, it must first be defined on the UCS Manager and discovered using the
CloudSync Infrastructure Discovery portal.
Step 1
Choose Service Portal from the module drop-down list and then click Manage Cloud Infrastructure.
Step 2
Click the Service Profile Templates icon.
Step 3
Select the line item you wish to register in the grid, and select the Register button.
Step 4
In Register Operating System Template, select whether this is a Hypervisor Template. If yes, select the
vCenter Cluster.
Step 5
Enter a friendly name in Display Name and Description.
Step 6
Click Submit Order.
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
7-3
Chapter 7
Managing Templates
Managing E-mail Templates
Ignoring a UCS Service Profile Template
The Cloud Provider Technical Administrator can change the state of a UCS service profile template to
Ignored to administratively ignore a template. The template may be in Discovered, Registered, or
Maintenance states to set it to Ignored. If the record was previously in Registered or Maintenance states,
metadata on that record will be saved.
Step 1
Choose Service Portal from the module drop-down list and then click Manage Cloud Infrastructure.
Step 2
Click the Service Profile Templates icon.
Step 3
Select the line item you wish to set to Ignored in the grid, and select the Ignore button.
Step 4
Click Submit Order.
Step 5
Review the information to confirm that the selected operating system template is the one that you want
to remove, then click Submit Order.
Managing E-mail Templates
Use the instructions in this section to manage your e-mail templates.
Configuring E-mail Notification Templates
Cisco IAC includes a set of default (delivered as part of Prime Service Catalog) e-mail notification
templates that you customize for an organization. The cloud system sends the e-mail notifications in
response to events such as orders and system errors. Before users can start ordering cloud services, you
must configure the e-mail notification templates with the relevant sender and recipient addresses.
Step 1
Choose Service Portal from the module drop-down list.
The text menu displays.
Step 2
Click System Setup to display the nested menu.
Step 3
Click System Settings.
Step 4
On the System Settings portal, click the System Settings tab to open the portlet.
Step 5
On the System Settings portlet, click:
– Modify E-mail Templates
Step 6
On the Request Center tab in the E-mail Templates panel, update the following templates (the others are
programmed using a service):
•
Ad-Hoc Task Started
•
Default Late Activity
•
My Services Departmental Reviews
•
My Services Financial and Departmental Authorizations
•
My Services Service Group Authorizations
•
My Services Service Group Reviews
Cisco Intelligent Automation for Cloud User Guide
7-4
OL-29974-01
Chapter 7
Managing Templates
Managing E-mail Templates
Note
Step 7
•
Process Escalation
•
Service Link Error on External Task
Use the page controls at the bottom of the Request Center tab to find each template you want to
configure. In addition to the default templates listed above, you may modify any of the templates listed
on either the Request Center or the Demand Center tabs.
In the General pane, modify any or all of the following attributes:
•
Enter the name of the template.
•
Enter the subject of the notification.
•
Enter a valid address to use as the sender.
•
Enter one or more valid recipient e-mail addresses. For multiple recipients, separate e-mail
addresses using semi-colons.
Note
Step 8
You can use namespace variables in this field. For information on using namespaces, see the
Cisco Service Portal 9.1 Namespace Users Guide.
•
Leave the Language field as is. In the current release, only US English is supported; any language
selection you make will be ignored.
•
Leave the Request Center radio button selected by the Type field.
For the editing window, click one of the following radio buttons to choose an editor.
•
HTML Part
•
Text Part
Step 9
In the editing panel, modify the default content and add optional content as needed.
Step 10
Click Update.
Step 11
Repeat Step 4 through Step 8 above for the e-mail templates on the Request Center tab.
Assigning From Address for E-mail Templates
In addition to configuring the templates, you must also assign the From address for the default templates
to use for outgoing notification e-mail messages. E-mail cannot be sent without a fully-qualified e-mail
address.
Step 1
Choose Service Portal from the module drop-down list.
The text menu displays.
Step 2
Click System Setup to display the nested menu.
Step 3
Click System Settings.
Step 4
On the System Settings portal, click the System Settings tab to open the portlet.
Step 5
On the System Settings portlet, click:
– Set System E-mail Account
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
7-5
Chapter 7
Managing Templates
Managing E-mail Templates
Step 6
Enter the e-mail address you would like to use as the default from address for outgoing notification
e-mail messages in the Sender E-mail Address field.
Step 7
Click Submit Order.
Assigning Mail Addresses for Queue Notifications
You must update the queue configuration settings with e-mail addresses that will receive e-mail
notifications for changes in service queues.
A queue is a repository for administrative tasks that need to be performed, such as monitoring service
delivery, lease instances, and failed service remediation. Tasks are automatically added to the queue by
the Cloud system. Users with permissions can see the queues, assign tasks, and take action on the tasks
in Service Manager.
Cisco IAC ships with the following preconfigured queues:
•
Default Service Delivery—Tasks that are currently unassigned.
•
Cloud Service Cancellation—Tasks related to services that have been cancelled.
•
Cloud Service Delivery Management—Tasks related to services that fail after they are first ordered,
and resubmission of failed services after they are remediated.
•
Cloud Service Lease Administration—Tasks related to server leases.
•
Cloud Service Remediation—Tasks related to services that failed and need remediation action.
•
Cloud Service Approval Administration – Tasks that are waiting for an approval.
Cloud Provider Technical Administrators and Organization Technical Administrator monitor, assign, or
address tasks added to the queues. Those users with access to the queues can perform the tasks added
the queues. When a task is added to a queue or is assigned or reassigned to a user, the designated users
receive e-mail notifications.
For information about working with queues, see the Cisco Intelligent Automation for Cloud User Guide.
To prepare the queues for use, you must specify the e-mail addresses of the users who receive e-mail
notifications when a task is added to a queue. If you skip this task, no one will receive notifications of
changes to the queues.
Tip
Remember to us mailing lists (aliases), not specific user e-mail addresses. Also, be sure to configure
e-mail addresses for each queue.
Step 1
Log in to Cisco IAC as an administrator.
Step 2
Choose Organization Designer from the module drop-down list,.
Step 3
Click the Queues tab.
Figure 7-1
Organization Designer Tabs Bar
Cisco Intelligent Automation for Cloud User Guide
7-6
OL-29974-01
Chapter 7
Managing Templates
Managing E-mail Templates
Step 4
In the Queues pane, click Default Service Delivery.
Step 5
From the menu on the right side of the window, click Contact to display the Contact pane.
Before configuration, the Contacts panel lists one test e-mail address (typically,
[email protected]).
Step 6
Click in the Value field and edit the e-mail address.
Step 7
Select E-mail from the Type drop down.
Step 8
Click Update.
Step 9
Repeat Step 1 through Step 8 above to add additional e-mail addresses to the queue.
Step 10
Repeat Step 4 through Step 8 above for the remaining queues.
Modifying E-mail Notification Templates
Cisco Intelligent Automation for Cloud 4.0 (Cisco IAC) includes a set of default e-mail notification
templates that you customize for an organization. The cloud system sends the e-mail notifications in
response to events such as orders and system errors.
The e-mail templates must be customized with the sender and recipient addresses. You can also
optionally customize the subject and message.
To modify the default e-mail notification templates, perform the following steps.
Step 1
Choose Service Portal from the module drop-down list, then click the System Setup tab.
Step 2
On the System Setup portal page, click the System Settings tab to open the portlet.
Step 3
On the System Settings portlet, click Modify E-mail Templates to open the form.
Figure 7-2
E-mail Templates Form
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
7-7
Chapter 7
Managing Templates
Managing E-mail Templates
Step 4
On the Request Center tab in the E-mail Templates panel, click Add Role Completion Notification in
the list.
Step 5
In the General pane, modify any or all of the following attributes:
Step 6
Field
Action
Name
Enter the name of the template.
Subject
Enter the subject of the notification.
From
Enter a valid address to use as the sender.
To(s)
Enter one or more valid recipient e-mail addresses. For multiple recipients, separate
e-mail addresses using semi-colons.
Note
You can use namespace variables in this field. For information on using
namespaces, see the Cisco Service Portal Namespace Users Guide.
Note
If this field is not set, these e-mail templates will not be sent. The requisition
history might say they did, but the e-mail will not be sent if an SMTP
formatted e-mail address is not entered. The e-mail does not have to be a real
address, but it must be properly formatted ([email protected]).
Language
Leave as is. In the current release, only US English is supported; any language
selection you make will be ignored.
Type
Click the Request Center radio button.
For the editing window, click one of the following radio buttons to choose an editor.
•
HTML Part
•
Text Part
Step 7
In the editing panel, modify default content and add optional content as needed.
Step 8
Click Update.
Step 9
Repeat Step 4 through Step 8 for the e-mail templates on the Request Center tab.
For a complete list of the e-mail templates, see the E-mail Notification Template Modification Checklist
in the Cisco Intelligent Automation for Cloud Configuration Guide.
Setting Return E-mail Address
To set a return e-mail address, perform the following steps.
Step 1
Choose Service Portal from the module drop-down list and then click System Setup tab.
Step 2
In the System Set up portal page, click the System Settings tab to open the portlet.
Step 3
In the System Settings portlet, click Set System E-mail Account.
Step 4
Enter an actual, active e-mail account with a valid SMTP format
Step 5
Click Submit Order.
Cisco Intelligent Automation for Cloud User Guide
7-8
OL-29974-01
A P P E N D I X
A
Glossary of Terms
The following contains a list of acronyms important for understanding the installation, configuration,
and day-to-day use of Cisco Intelligent Automation for Cloud 4.0.
A
AD
Active Directory (AD) is a directory service implemented by Microsoft for Windows
domain networks
Amazon EC2
See EC2
AS
Advanced Services – Team of professional services engineers with Cisco, same as
Cisco Services
Autonomous System– In a routing context
ASA
Adaptive Security Appliance
AWS
Amazon Web Services
B
BaseDN
Base-distinguished name; used in LDAP authentication. See DN
BindDN
Bind-distinguished name; used in LDAP authentication. See DN
C
CaaS
Compute as a Service. See also IaaS and SaaS
CDP
Cisco Device Protocol
CIAC
Cisco Intelligent Automation for Cloud
CP
Cloud Portal. This name is no longer in use (but you may still find it in older
documents.) The new name for this product is Cisco Prime Service Catalog.
CPBA
Cloud Provider Business Administrator
CPTA
Cloud Provider Technical Administrator
CSR
Cloud Services Router
CUIC
Cisco Unified Infrastructure Controller
Cisco Intelligent Automation for Cloud 4.0
Glossary
A-1
Appendix A
Glossary of Terms
D
DBA
Database Administrator
DHCP
Dynamic Host Configuration Protocol
DN
Name that uniquely identifies an entry in an LDAP directory. A DN is made up of
“attribute=value” pairs separated by commas
DNS
Domain Name System
DRS
Distributed Resource Scheduler. Part of VMware vSphere
E
EC2
Amazon Elastic Compute Cloud
EFT
Early Field Testing [release of beta software to select internal and external
stakeholders for a trial period]
ELMI
Enhanced Local Management Interface
ESXi
ESXi is a bare-metal hypervisor from VMware
F-H
FCS
Field Customer Ship
FHRP
First Hop Redundancy Protocol
HSRP
Hot Standby Router Protocol
HTML
HyperText Markup Language. A language for displaying information in a web
browser
I
IaaS
Infrastructure as a Service. See also Saas and CaaS
IAC
Cisco Intelligent Automation for Cloud
IIS
Internet Information Services, an extensible web server created by Microsoft
ILMI
Interim Local Management Interface
IPAM
IP Address Management
JKL
JBoss
Open Source Java Application Server from JBoss, a division of Red Hat Inc.
JQuery
Cross-browser JavaScript library
KDE
“K Desktop Environment;” A network-transparent desktop environment used on
UNIX workstations
LAN
Local Area Network
LDAP
Lightweight Directory Access Protocol. A protocol for accessing and maintaining
distributed directory information services over an Internet
LLDP
Link Layer Discovery Protocol
LUN
Logical Unit Number
Cisco Intelligent Automation for Cloud 4.0
A-2
Glossary
Appendix A
Glossary of Terms
M-N
MAC
Media Access Control
Mapping
Refers to mapping within Active Directory
NFS
Network File System
NSC
Network Service Controller
NMTG
Network Management Technology Group
nsAPI
Cisco offers a set of standard REST (Representational State Transfer) APIs and Java
stubs for accessing entities defined in Service Portal. They are collectively known
as nsAPI.
O
OpenStack
Initiative developed jointly by Rackspace Hosting and NASA. See:
http://www.openstack.org/
OTA
Organization Technical Administrator
OU
Organizational Unit
P
PNC
PowerVu Network Center
PNSC
Cisco Prime Network Services Controller (formerly known as VNMC)
PO
Cisco Process Orchestrator
POC
Proof Of Concept – Hands-on engagement of select customers with beta product
install in their environment at customer site
POD
Point of Delivery or Point of Distribution
PSC
Cisco Prime Service Catalog
Q
Queue
A first-in/first-out (FIFO) list of elements, where the first element added to the
queue will be the first one to be removed.
Query
A request for information from a database. See JQuery
R
RabbitMQ
Open source message broker software (middleware) for Advanced Message
Queuing
RDP
Remote Desktop Protocol
S
SAN
Storage Area Network
SaaS
Software as a Service; See also CaaS and IaaS
SC
Service Catalog
SDP
Service Delivery Platform
Cisco Intelligent Automation for Cloud 4.0
Glossary
A-3
Appendix A
Glossary of Terms
SDU
Systems Development Unit
SSL
A cryptographic protocol used to provide secure communication over the Internet
SNMP
Simple Network Management Protocol
SP
Cisco Server Provisioner
SSH
Secure Shell
T
TAC
Technical Assistance Center
TBA
Tenant Business Administrator
Tenant
Member of a multi-tenancy server/zone; another word for “customer”
TTA
Tenant Technical Administrator
U
UCS
Cisco Unified Computing System
UCSD
Cisco Unified Computing System Director (USCD)
UUID
Universal Unique Identifier. A 128-bit number used to uniquely identify an object
or entity
V
vASA
Virtual Adaptive Security Appliance
VDC
VMware Virtual Cloud Director
VDC
Virtual Data Center
VIP
Virtual IP
VNMC
Virtual Network Management Center (same as NSC). This name is no longer used.
This product is now known as Cisco Prime Network Services Controller.
VLAN
Virtual LAN
VMDC
Virtualized MultiService Data Center
VRRP
Virtual Router Redundancy Protocol
VSG
Virtual Security Gateway
VSO
Virtual Server Owner
V/PSO
Virtual and Physical Server Owner
WXYZ
Week 0
Marker to denote AS’s successful, autonomous deployment of IAC and successful
testing of flagship services.
WWNN
World Wide Node Name
WWPN
World Wide Port Names
Cisco Intelligent Automation for Cloud 4.0
A-4
Glossary
INDEX
Center, Decommissioning a Virtual Data
A
Accessing Modules
6-16
Center, Obtaining Approvals for Creating a Virtual
Data 6-15
1-1
Action Panel for Managing VMs and VDCs, The
Take 6-18
Center Capacity Charts, Viewing Virtual Data
Adding
Center Link, Create Virtual Data
Columns
Center Details, Viewing Virtual Data
1-13
Administration
Approval Queues
6-6, 6-7
1-10
7-5
Chart, Utilization
7-6
4-12
6-19
Charts, Viewing Virtual Data Center Capacity
6-19
Checking
Authorization
Status of an Order
5-12
System Health
4-15
4-8
Cisco IAC Service Portal Menu Bar
Cisco IAC Site Homepage
B
1-1
1-9
Cisco Unified Computing System
Buttons
5-7, 5-8, 5-10, 5-11, 6-2, 6-9,
7-1, 7-2, 7-3, 7-4
Cloud Infrastructure
1-10
Connecting or Updating
Cloud Operations
C
5-5
1-4
Columns
Calculating Virtual Data Center Size Requirements
Calculator, The VDC
Capacity Charts, Viewing Virtual Data Center
5-4
Center, Creating a Virtual Data
6-16
adding or removing
1-13
Commissioning a Physical Server
6-17
Commissioning a Virtual Machine
Cancelling the Order if Remediation Attempt is
Unsuccessful 4-15
CDP
6-11
Changing Your Landing Page from My Services to Service
Portal 1-10
Assigning Mail Addresses for Queue Notifications
Assigning the Remediation Task for Repair
6-16
Changing
Changing the Server Size of a Virtual Machine
Assigning From Address for Email Templates
UI main
6-17
Center Size Requirements, Calculating Virtual Data
your landing page
4-3
Approvals for Creating a Virtual Data Center,
Obtaining 6-15
managing
6-13
Center Size, Modifying Virtual Data
Advanced Services 5-2, 5-5, 5-8, 5-9, 5-10, 5-13, 6-1, 6-2, 6-5, 6-6,
6-7, 6-8, 6-13, 6-14, 6-15, 6-16, 6-17, 7-4, 7-5, 7-6, 7-7, 7-8
Amazon Web Services
6-18
6-14
Centers, Working with Virtual Data
1-13
6-19
6-4
Compute POD
6-19
registering
removing
6-14
6-1
3-3
3-4
working with
3-3
Cisco Intelligent Automation for Cloud User Guide
OL-29974-01
IN-1
Index
Compute POD properties
modifying
Designer
for Organizations
3-3
Computing System, Cisco Unified
portal
6-2, 6-9
Configuring and Enabling Approvals
1-12
1-3
Desktop Protocol, Remote
4-2
Configuring Email Notification Templates
Details, Viewing Virtual Data Center
7-4
Connecting or Updating Cloud Infrastructure
6-6, 6-7
6-18
Device-Type Level
5-5
Health of
Container
managing
Service Resource
creating
3-4
deleting
3-6
modifying
4-10
Discovery
Instances of a platform element type
Network Devices
3-5
Containers
5-1
New instances of all objects
Resource containers
working with
5-9
Objects in the Cloud Infrastructure
running
3-4
Create Virtual Data Center Link
Creating a Service Resource Container
Creating a Virtual Data Center
Down a Virtual Machine, Powering
6-14
Creating a Virtual Data Center, Obtaining Approvals
for 6-15
Creating One or More PODs
Customizing Table Views
5-1
Down a Physical Server, Powering
3-4
5-8
5-2
User workflow
6-14
5-9
6-2
6-11
Dropdown List
Network Elements
5-3
3-1
1-13
E
EC2 Windows VMs Without Keypairs, Using
D
6-6
E-mail notifications
Data Center, Creating a Virtual
6-14
configuring templates
Data Center, Decommissioning a Virtual
6-16
Data Center, Obtaining Approvals for Creating a
Virtual 6-15
Data Center Capacity Charts, Viewing Virtual
Data Center Details, Viewing Virtual
Data Center Link, Create Virtual
Deleting a Snapshot
Error Remediation Page
6-16
6-4
6-16
6-7
3-6
6-13
1-10
4-14
Escalation
managing
Decommissioning a Virtual Data Center
5-12
Enabling Reserved Portlet Buttons
6-17
Deleting a Service Resource Container
7-7
enabling
6-13
Decommissioning a Virtual Machine
Email Templates Form
Authorization
Data Center Size Requirements, Calculating Virtual
Decommissioning a Physical Server
7-6
an Authorization or Review
6-18
Data Center Size, Modifying Virtual
for service queues
Enabling
6-19
6-14
Data Centers, Working with Virtual
7-4
5-12
setting up sequences for
5-13
Escalation Sequences
setting up
5-13
Extending or Removing a Server Lease
4-4
Cisco Intelligent Automation for Cloud 4.0 User Guide
IN-2
OL-29974-01
Index
H
M
Handling Infrastructure Errors
Machine, Changing the Server Size of a Virtual
4-12
Health at the Device-Type Level, Managing
Health Check
4-10
6-4
Machine, Decommissioning a Virtual
4-10
Health Check, running new
Machine, Power-cycling a Virtual
4-10
Health Data, historical
viewing
Machine, Commissioning a Virtual
Machine, Powering Up a Virtual
Health Settings
6-7
6-12
Machine, Powering Down a Virtual
4-10
6-11
6-11
Machine, Taking a Snapshot of a Virtual
System-Wide
6-11
6-12
Machine Settings to Snapshot, Reverting a Virtual
Managing
Maintaining
4-9
Historical Health Data, viewing
6-12
Servers
4-10
4-5
Maintaining an Operating System Template
Main UI Buttons
I
7-1
1-10
Manage Infrastructure Portal
4-7
Manager
Icon
for Service Items
Server Ownership
modifying
Service
4-6
Ignoring an Operating System Template
Ignoring a UCS Service Profile Template
Approval Requests
7-4
Cisco UCS Blades and Blade Pools
Infrastructure Ownership Reassignment
Cloud Infrastructure Discovery
4-6
Infrastructure
6-8
Resources
Instances of a platform element type
Discovery of
4-3
Authorization and Review Escalation
5-10
Installing an Operating System
1-12
Managing
7-2
Individual Platform Element
validating
1-12
4-5
5-8
4-5
5-7
Server Leases
5-9
5-12
4-3
Managing Email Templates
7-4
Managing Health at the Device-Type Level
K
4-10
Managing Infrastructure Portal
Keypairs, Using EC2 Windows VMs Without
6-6
using
4-7
Managing Operating System Templates
7-1
Managing Power Settings for Physical Servers
6-2
L
Managing Server Templates
Landing page
Managing System-Wide (Global) Health Settings
changing
LLDP
5-4
4-9
Managing VMs and VDCs, The Take Action Panel
for 6-18
1-10
Link, Create Virtual Data Center
7-2
6-14
Menu Bar
for Service Portal
Service Portal
1-1
1-1, 1-2
Cisco Intelligent Automation for Cloud 4.0 User Guide
OL-29974-01
IN-3
Index
Modifying
O
Compute POD Properties
3-3
Network POD Properties
3-2
Server Ownership Icon
Discover of
4-6
Service Resource Container
Shared Server Zone
Objects in the Cloud Infrastructure
Obtaining Approvals for Creating a Virtual Data
Center 6-15
3-5
5-12
Modifying Email Notification Templates
Modifying Virtual Data Center Size
Module Drop-down List
Modules
7-7
One or more PODs
creating
6-17
templates
7-2
Operating System, Installing an
1-1
Modules, accessing
My Cloud
3-1
operating system
1-1
1-1
Accessing
5-8
Operations
1-1
Cloud
1-3
My Servers Portal
1-4
Order Status Portal Displaying Orders
4-5
Organization Designer
My Services
Changing Landing page
6-8
1-12
Organization Designer Tabs Bar
1-10
4-1
7-6
My VCDs
Sample View
6-8
P
Panel for Managing VMs and VDCs, The Take
Action 6-18
N
Physical Server, Commissioning a
Network Device
Physical Server, Decommissioning a
Registering
Physical Server, Power-cycling a
see Connecting or Updating Cloud
Infrastructure 5-5
Physical Server, Powering Up a
Discovery of
Physical Servers, Working with
Network Elements
6-3
6-2
6-1
POD
5-3
Compute
Network POD
removing
6-2
Physical Servers, Managing Power Settings for
5-1
Dropdown List
6-4
6-3
Physical Server, Powering Down a
Network devices
modifying
6-1
registering
3-2
removing
3-2
working with
New Health Check, running
3-1
Network
4-10
modifying
removing
5-9
3-2
3-2
working with
Notifying
User of Approaching Lease Expiration
3-3
creating one or more
3-1
New instances of all objects
Discovery of
3-4
working with
3-1
Network with Compute PODs
3-3
4-4
3-1
POD properties
Cisco Intelligent Automation for Cloud 4.0 User Guide
IN-4
OL-29974-01
Index
Compute POD
Remote Desktop Protocol
modifying
Removing
3-3
Portal Designer Portal
6-6, 6-7
Columns
1-3
Portal Pages List with Descriptions
Portal Purpose and Location
1-3
1-3
Portals, Portal Pages, and Portlets
1-13
Compute POD
3-4
Network POD
3-2
Requirements, Calculating Virtual Data Center Size
1-2
power
6-16
Reserved Portlet Buttons
powering-off
6-2, 6-11
powering-on
6-3, 6-11
resetting
Enabling
1-10
resetting servers. See power-cycling a server
Re-sorting
6-3, 6-12
Power-cycling a Physical Server
Table Rows by Column
6-3
Power-cycling a Virtual Machine
6-12
Resource Containers
Powering Down a Physical Server
6-2
working with
Powering Down a Virtual Machine
Powering Up a Physical Server
managing
5-7
Reverting a Virtual Machine Settings to Snapshot
6-11
Power Settings for Physical Servers, Managing
6-2
6-12
Review
enabling
Profile
Settings and Preferences
3-4
Resources
6-11
6-3
Powering Up a Virtual Machine
1-13
5-12
Review Escalation
1-13
managing
Properties
modifying
5-12
Running
Compute POD
Discovery
3-3
Properties, Viewing Server Status and
Protocol, Remote Desktop
5-2
New Health Check
6-9
4-10
6-6, 6-7
S
R
Server, Commissioning a Physical
Re-enabling
Server, Decommissioning a Physical
1-12
Registering
Server, Power-cycling a Physical
Network Device
Registering a Compute POD
Server, Powering Up a Physical
modifying
Registering an Operating System Template
7-1, 7-3
Registering a UCS Service Profile Template
7-3
Remediating
4-13
Remediation Error Panel
7-2
6-3
4-6
servers
power-cycling
6-3, 6-12
powering-off
6-2, 6-11
powering-on
6-3, 6-11
properties
4-14
6-2
Server Ownership Icon
3-3
Registering a Virtual Machine Template
6-4
6-3
Server, Powering Down a Physical
see Connecting or Updating Cloud
Infrastructure 5-5
a Service
6-1
status
6-9
6-9
Cisco Intelligent Automation for Cloud 4.0 User Guide
OL-29974-01
IN-5
Index
Servers, Managing Power Settings for Physical
Servers, Working with Physical
System, Cisco Unified Computing
6-1
Server Size of a Virtual Machine, Changing the
Server Status and Properties, Viewing
server templates
Status and Properties, Viewing Server
6-2
System, Installing an Operating
6-11
Service Manager
Intervals options
Status Portlet
1-12
6-8
4-10
4-9
System Setup portal page showing the Administrators
portlet. 1-5
1-12
Service Portal
changing landing page to
menu bar for
6-2, 6-9
System Health
6-9
7-2
Service Item Manager
6-9
System-Wide Health Settings, Managing
1-10
4-9
1-1
Service Portal Menu Bar
1-1, 1-2
T
service queues
assigning e-mail addresses for notifications
Table Rows by Column
7-6
re-sorting
Service Resource Container
creating
3-4
deleting
3-6
modifying
Table views
customizing
6-1, 6-2, 6-5, 6-6, 6-7, 6-8, 6-13, 6-14, 6-15,
6-16, 6-17
Services, Amazon Web
Taking a Snapshot of a Virtual Machine
templates
6-6, 6-7
Setting Return Email Address
6-12
7-2
for e-mail notifications
7-8
7-4
The Take Action Panel for Managing VMs and
VDCs 6-18
Settings and Preferences
profile
1-13
Take Action Panel for Managing VMs and VDCs,
The 6-18
3-5
Services, Advanced
1-13
1-13
Settings for Physical Servers, Managing Power
The VDC Calculator
6-2
Settings to Snapshot, Reverting a Virtual Machine
6-17
Turning Automatic Health Check On or Off
4-8
6-12
Setting Up
Escalation Sequences
U
5-13
Shared Server Zone
Modifying
UCS service profile templates
5-12
Site Homepage/Service Portal
UI Buttons
1-9
Size, Modifying Virtual Data Center
main
6-17
Size of a Virtual Machine, Changing the Server
Snapshot of a Virtual Machine, Taking a
Snapshots, Viewing
SNMP
SSH
6-16
Unified Computing System, Cisco
Up a Physical Server, Powering
6-13
Snapshot, Reverting a Virtual Machine Settings to
1-10
Understanding the Cisco IAC 4.0 User Interface (UI)
6-11
Size Requirements, Calculating Virtual Data Center
Snapshot, Deleting a
7-2
6-12
6-12
6-13
5-5
Up a Virtual Machine, Powering
1-1
6-2, 6-9
6-3
6-11
User Workflow
Discovery
5-1
Using
Approvals Portlet
5-5
Cisco Intelligent Automation for Cloud 4.0 User Guide
IN-6
OL-29974-01
Index
Approvals Portlet
using
Virtual Data Center, Obtaining Approvals for Creating
a 6-15
4-3
Managing Infrastructure Portal
Virtual Data Center Capacity Charts, Viewing
4-7
Using EC2 Windows VMs Without Keypairs
Utilization Chart
6-6
Virtual Data Center Details, Viewing
Virtual Data Center Link, Create
6-19
6-19
6-18
6-14
Virtual Data Centers, Working with
6-13
Virtual Data Center Size, Modifying
6-17
V
Virtual Data Center Size Requirements, Calculating
Validating
Virtual Machine, Changing the Server Size of a
Cisco Process Orchestrator and Share Location
Settings 5-11
Virtual Machine, Commissioning a
Cloud Infrastructure
Virtual Machine, Power-cycling a
5-10
Email Server Connection
5-12
Individual Platform Element
Platform Configuration
5-10
5-11
6-8, 6-16
6-11
6-11
6-12
6-12
virtual servers
changing server size
Image Changes and Help Text Appears When You
Mouse Over 6-8
6-1, 6-2, 6-5, 6-6, 6-7, 6-8, 6-13, 6-14, 6-15, 6-16, 6-17, 6-18
VDC Calculator, The
6-12
Virtual Machine Settings to Snapshot, Reverting a
VCD Buttons
VDC
6-7
Virtual Machine, Taking a Snapshot of a
Platform Elements Together
vCD
Virtual Machine, Decommissioning a
Virtual Machine, Powering Up a
6-11
6-4
Virtual Machine, Powering Down a
5-10
6-16
6-17
templates
6-11
7-2
VMs and VDCs, The Take Action Panel for
Managing 6-18
VMs Without Keypairs, Using EC2 Windows
VDCs, The Take Action Panel for Managing VMs
and 6-18
VMware
6-6
5-8, 5-10, 5-11, 6-14, 6-15, 6-17
Viewing
Discovered Objects in the Infrastructure
Historical Health Data
4-10
Server Lease Information
Service Requisitions
System Health
4-8
6-6, 6-7
Windows VMs Without Keypairs, Using EC2
6-6
Without Keypairs, Using EC2 Windows VMs
6-6
Workflow
5-7
Viewing Server Status and Properties
Discovery
6-9
user
6-13
Viewing Virtual Data Center Capacity Charts
Viewing Virtual Data Center Details
6-18
5-1
Working with
6-19
Compute PODs
3-3
Portals and Portlets
Views
Resource Containers
Table
customizing
W
Web Services, Amazon
4-4
4-1
System Resource Capacity
Viewing Snapshots
5-9
1-2
3-4
Working with Physical Servers
1-13
Virtual Data Center, Creating a
6-1
Working with Virtual Data Centers
6-13
6-14
Virtual Data Center, Decommissioning a
6-16
Cisco Intelligent Automation for Cloud 4.0 User Guide
OL-29974-01
IN-7
Index
Y
Your landing page
changing
1-10
Cisco Intelligent Automation for Cloud 4.0 User Guide
IN-8
OL-29974-01