FIGURE 1: PLATFORM ISF USER FLOWS
FIGURE 1: PLATFORM ISF USER FLOWS
Figure 1 shows how Platform ISF works. End users (at the top) are presented with a self-service portal from which they can request different offerings from the service catalog. Once the request is approved and within the user’s allocation limits, a reservation is created for those resources. When it’s time to start the request, the allocation engine locates the appropriate resources to run the service and creates the service on those resources. These resources can be obtained from either an internal or a public cloud, or both. Performance metrics are gathered and fed to the reporting and monitoring tools. The data is available to both users and administration staff. A policy engine allows the service to be scaled up or down automatically. The self-service portal allows the user to see the application and monitor the machines in the application. The user can access the services once they are created. The whole process, from the user requesting a service to delivery, can be completed in a few minutes with no need for administrators to get involved.

Cloud administrators can view and manage the cloud resources from a single pane. Different views in the user interface allow the administrator to quickly isolate fault locations. Along with remote log file viewing, remote command execution, and remote consoles, the administrator has all the tools to manage the cloud resources. The cloud administrator is responsible for defining the accounts that will use the cloud and for creating the initial service offerings. The accounts are hierarchical, so once they are defined their management can be delegated to account owners (at the top level, this could be a business unit). The account owners can create other accounts (such as departments), subject to the limits imposed on their account, and add users to the accounts. They also have access to the billing and chargeback reports. Account owners can also create service offerings. These, in turn, can be offered to different sub-accounts (such as projects within departments within business units).

FIGURE 2. ADMINISTRATOR COCKPIT
FIGURE 2. ADMINISTRATOR COCKPIT
Figure 2 shows the cloud administrator’s view, with an interface optimized for managing a large-scale
cloud without introducing unnecessary management complexity. The left frame shows a variety of virtualization and physical provisioning systems supported by Platform ISF. The top-middle frame summarizes the entire cloud including metrics organized by each data center. The middle frame connects the applications (services) in the cloud to the physical hosts. The bottom frame shows the VMs running on that physical host or as part of that application. This ties together the multiple layers of the stack in one easy-to-browse management view. The right frame shows the performance metrics gathered on the physical or virtual hosts, including any events and alarms.

FIGURE 3. PLATFORM ISF SOFTWARE ARCHITECTURE 600
FIGURE 3. PLATFORM ISF SOFTWARE ARCHITECTURE

PLATFORM ISF SOFTWARE ARCHITECTURE


Platform ISF integrates with major hypervisor technologies including VMware vSphere, Citrix Xen, Red Hat Xen*, and Red Hat KVM*. Where a hypervisor presents a central management interface, such as VMware vCenter* or Citrix XenCenter*, Platform ISF executes, controls, and monitors status through that interface. In cases where the hypervisor technology has no central manager, Platform ISF provides its own agent, which is deployed to each hypervisor node.

Platform ISF can manage and provision physical machines from bare metal using its adapter technology (Resource Interface Adapter*) with adapters to best-in-class provisioning tools such as those from Altiris, TPM, BladeLogic, and xCAT.

Platform ISF also provides its own provisioning tool, Platform Cluster Manager* (PCM*), which integrates with Platform ISF and can perform image- and packaged-based installs of the operating system and applications. PCM has also been adapted to provision hypervisor hosts to support demand-based shrink and grow of VM capacity by, say, switching nodes between VMware and Red Hat KVM. Finally, Platform ISF can also manipulate storage and network configuration to suit a particular workload.

Once integrated, Platform ISF can deploy a workload across any resources available (virtual or physical) through its Allocation Engine*, which can create and execute complex policies governing how a workload needs to be initially deployed and how it will behave over the lifecycle of an application. The Allocation Engine also lets the user make current and future reservations on a given request. All requests for a workload are submitted through a Web portal, where users are given a service catalog, published by the cloud administrator, from which to choose. The Service Manager (ICM) manages the application lifecycle (application definitions and instances) as well as users and accounts.

Platform ISF tracks the applications’ duration and produces chargeback and billing reports based on the price set for each resource (e.g., CPU, MEM) and the time for which the application ran. It also produces capacity and allocation reports to manage the overall system.


FIGURE 4. PLATFORM ATTESTATION AND SAFER VMM LAUNCH
FIGURE 4. PLATFORM ATTESTATION AND SAFER VMM LAUNCH

PLATFORM ISF WITH INTEL® TRUSTED EXECUTION TECHNOLOGY


Without a doubt, cloud security is a hot topic and a major concern for enterprises. Cloud security covers a number of important areas including identity management, access control, data protection, data loss prevention, and hypervisor security. Although cloud access and data protection have been at the center of the security discussion, cloud infrastructure security and, specifically, hypervisor security have been getting special attention from enterprise IT. Pervasive use of virtualization technology among enterprises and cloud service providers, with the ability to move virtual machines between internal or external data centers to cloud service providers, raises the question of how enterprises ensure the security of their
cloud infrastructures.

It isn’t too difficult to imagine that one infected hypervisor or guest VM can spread the infection through virtualized infrastructure when moving from one host to another. While there are solutions to detect infected applications within guest VMs, there are far fewer solutions to detect infected hypervisors today. For this reason, Intel has developed a unique technology called Intel Trusted Execution Technology (Intel TXT).

Intel TXT helps prevent software-based attacks on currently unprotected areas, such as attempts to insert a non-trusted VM manager (VMM, or rootkit hypervisor); reset attacks designed to compromise platform secrets in memory; or BIOS and firmware update attacks. To view it in a different way, Intel TXT enforces control through measurement, memory locking, and sealing secrets. To do this, it also works cooperatively with Intel Virtualization Technology (Intel VT).

An Intel TXT-enabled system requires all of the listed components— processor, chipset, TPM, enabled BIOS, and enabled hypervisor (VMM) or operating system. Without a complete set of these components, a trusted launch is not possible (Figure 4).
FIGURE 5 TRUSTABLE POOLS AND SECURE MIGRATION
FIGURE 5 TRUSTABLE POOLS AND SECURE MIGRATION
Available on Intel Xeon processor 5600 series-based servers, Intel TXT is providing hardware-based protection in the processor, chipset, and third-party trusted platform modules (TPMs) that can better resist software attacks and make platforms more robust (Figure 5).
FIGURE 6. PLATFORM ISF HIGHLY SECUIRE ENVIRONMENT 400
FIGURE 6. PLATFORM ISF HIGHLY SECUIRE ENVIRONMENT
Platform ISF creates a highly secure environment for running applications in VMs through its integration with Intel TXT, which monitors changes to the BIOS and boot processes of a hypervisor host to ensure it has not been tampered with. When a new host is added to the system, the administrator indicates it’s a "trusted" host. Platform ISF then queries Intel TXT for the host's digest value, a cryptographic hash value coded to a number of metrics that measures the unique characteristics of the host's boot sequence. The digest value remains constant as long as the hypervisor installed on the host is not modified. Platform ISF saves this good digest value in its internal database for later comparison (Figure 6).

FIGURE 7. HOST MARKED AS TRUSTED
FIGURE 7. HOST MARKED AS TRUSTED
Each time a host connects to Platform ISF (e.g., after rebooting) the
TXT digest values are retrieved. Platform ISF then compares the values to the known good values. If the values are equal, Platform ISF marks the host as "trusted" (Figure 7).
FIGURE 8. FLAGS INDICATING A PROBLEM
FIGURE 8. FLAGS INDICATING A PROBLEM
With this knowledge of trusted and untrusted hosts, Platform ISF enables a number of important policies. Applications can be easily restricted to running only on trusted hosts by specifying "trusted==1" in the application definition. This controls not only on which hosts are initially chosen to start the application VMs, but also to which hosts VMs are allowed to migrate. Platform ISF ensures only trusted hosts are used. Platform ISF can also notify the administrator when a host becomes untrusted by using the configurable alarm feature of ISF. When digest Values do not match, a red flag next to the host's name indicates a problem (Figure 8). The administrator can then drill down and find the cause of the issue.

It’s important to remember that in building secure cloud services, you need to incorporate multi-layer security architecture from the start. The Platform ISF and Intel TXT solution provides a foundation for building secure infrastructure while relying on other solutions to address requirements for data protection and data loss prevention.

BUILDING A PRIVATE CLOUD


In future articles, we’ll discuss how to build private cloud using Platform ISF.

ADDITIONAL RESOURCES


For more information, visit the Platform Computing Private Cloud website at www.platform.com/privatecloud or contact the authors:

About Jay Muelhoefer

VP Marketing at Platform Computing Inc

Jay drives marketing strategy, lead generation, and product marketing globally for Platform Computing's cloud business. He is a 15+ year veteran helping both small and large companies adopt leading enterprise software for competitive advantage. Jay's experience includes cloud-related ventures spanning virtualization, database monitoring, and data management products and services. Prior to Platform, Jay was the general manager of PTC's (Parametric) SaaS business and has held senior management positions with Lumigent, Bowstreet, Booz Allen Hamilton and Schlumberger.

view the cloudbook profile for Jay Muelhoefer >>

About Platform Computing Inc


Building on its core competency of unifying dynamic resource pools (both in HPC and corporate data centers) and sharing them for production applications, Platform Computing, with its Platform Computing ISF product, has emerged as a major provider of cloud management software. Platform Computing offers a comprehensive set of capabilities spanning virtual, physical, and external clouds with an open architecture to work in very heterogeneous environments.

view the cloudbook profile for Platform Computing Inc >>

Cloudbook Journal
Vol 2 Issue 4, 2011

This article is featured in the
Vol 2 Issue 4, 2011 of the
Cloudbook Journal

Find more Stories from this Issue >>