Yes, Cisco in partnership with SAP, has delivered a HANAaaS offering that uses IAC (including multi-tenancy). Would you like more details? ... View more

Hi, You'll want to verify that the user you're signed in as has permission to view this portlet. You may do so within Portal Designer. ... View more

Irvin, this discussion board is for the product Prime Network Services Controller. You'll want to use the Prime Network or Prime Infrastructure (or other - I'm not sure which Prime 1.4 product you're referring to) board to get this question addressed. ... View more

Correct, IAC 4.0 is currently undergoing compatibility testing with Grizzly and Havana. Support for these two OpenStack releases will be announced shortly after the IAC 4.0 release. ... View more

Since the release of Network Services Manager (NSM) as part Cisco Intelligent Automation for Cloud (IAC) 3.1 , we have seen a strong alignment of network automation use cases with Tier 1 Service Providers. Capitalizing on this alignment, NSM functionality will evolve from a standalone product to system/solution with greater flexibility and field adaptation. Given this evolution, the TEO 2.3.5 NSM adapter will be obsoleted in the Process Orchestrator 3.0 release (TEO has been renamed to PO). Cisco IAC 4.0 will o ffer network-enhanced application deployment environments in private and public cloud deployments, with self-service network policy control, and virtual network provisioning. Cisco IAC 4.0 will integrate with Cisco Prime Network Services Controller (NSC - formerly known as VNMC), Cisco 1000v series products - CSR, ASA and Nexus, Cisco VSG and Citrix NetScaler VPX. This integration along with other native IAC 4.0 functionality, like n etwork discovery, inventory and topology, network kdevice registration, g reenfield / limited brownfield support, n etwork catalog management, o nboard and off-board tenants, m anage tenant network services and offerings, t enant and organization views to order and manage their virtual data centers and virtual network services, m anage firewall and load-balancer policies for individual VMs. ... View more

Vinay, You've posted this question to the Cisco Prime Service Catalog discussion forum. You may wish to repost in the Cisco Prime Infrastructure forum. ... View more

Hung, once the user has been assigned to an organization in IAC, a subsequent assignment of this same user to another organization should present you (the OTA) with an alert informing you that this user is being relocated from one organization to the next. IAC 4.0 will embed multi-tenancy into all services, including this people picker. IAC 4.0 will introduce two new tenant-level roles - the Tenant Technical Administrator (TTA) and the Tenant Business Administrator (TBA). It's worth noting that the behavior of 4.0 will be such that as a TTA, when selecting an existing user, the division between which users will be shown in this list will be on the order of tenants, not organizations.     ... View more

VM Discovery (or VM Brownfield or VM Import) will be a feature of IAC 4.0. CloudSync will be enhanced to perform discovery of existing VMs within the managed Cloud infrastructure. The following information is provided as tentative details of the forthcoming feature. CloudSync will tentatively include: Discover the existence of the VMs (under data centers or resource pools registered for use with IAC) Discover attributes of those VMs (the same as when a VM is provisioned) CPU configuration Memory configuration Storage reservation as well as actual usage (new) Network configuration Discover snapshots only under data centers registered for use in IAC (new) Discover snapshot attributes Storage usage Parent object (data center or resource pool) Snapshot hierarchy VM Discovery is a special case of vCenter object discovery there are many more VMs than other vCenter objects collecting all fields of a VM is time and CPU intensive Several use cases are defined to limit the amount of time and effort needed to keep records updated. The most intensive use case will be the Day 0 brownfield collection as Data Centers are registered. The engine process, Enumerate VMs, will be used to collect the VMs for all use cases.  This ensures consistent collections, and any changes are applied to all use cases. It'll perform two tiers of data collection: Tier 1 collects a small amount of data very quickly Tier 2 collects the full fingerprint per VM, but is relatively slow Discovery happens: on a schedule - like other CloudSync activities on an event - registration of a parent object (data center or resource pool) on manual invocation by a cloud administrator Discovered State (Holding Area) VMs are discovered, attributes collected, ready for manipulation (tagging/assignment/placement) by Cloud Provider Technical Administrator. Transition to Registered State (VM Registration) VMs are registered into service using the Manage Cloud Infrastructure portlet. This portlet needs to contain a new object type for vCenter. The CPTA needs to assign: ownership By identifying the Server Owner, other aspects of ownership become known (tenant, org) placement - a VDC or Shared Zone ensure the assigned IP address is reflected in IPAddress SI tables. ... View more

Hung, as you become familiar with IAC from an IaaS perspective (or other), you'll want to ensure you're considering the entirety of the solution as resides in both the orchestrator (Cisco Process Orchestrator) and the portal (Cisco Cloud Portal - being renamed to Cisco Prime Service Catalog). In IAC, user notifications, for example, are sent from the portal, not the orchestrator. Hope this helps. ... View more