native hybrid cloud, openstack edition with vxrack system ... · solution guide . native hybrid...

Solution Guide

NATIVE HYBRID CLOUD, OPENSTACK EDITION WITH VXRACK SYSTEM WITH NEUTRINO Solution Guide 1.1

• Provides a cloud-based application production environment • Enables faster time to market for software applications

• Improves application quality and update schedules

EMC Solutions

Abstract

This solution guide describes Native Hybrid Cloud, a production environment for cloud native applications. It is integrated with VxRack System with Neutrino, a cloud computing environment based on OpenStack. This document introduces the main features and functionality of the solution and the solution architecture.

September 2016

Copyright

2 Native Hybrid Cloud, OpenStack Edition with VxRack System with Neutrino Solution Guide 1.1

Copyright © 2016 EMC Corporation. All rights reserved. Published in the USA.

Published September 2016

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

EMC2, EMC, EMC2, Native Hybrid Cloud, ScaleIO, ViPR, VxRack, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

Native Hybrid Cloud, OpenStack Edition with VxRack System with Neutrino Solution Guide 1.1

Part Number H14939.2

http://www.emc.com/legal/emc-corporation-trademarks.htm

Contents


Contents

Chapter 1 Introduction 5 Business case ............................................................................................................ 6 Solution overview ....................................................................................................... 7 Key benefits ............................................................................................................... 8 Document purpose ..................................................................................................... 9 Audience .................................................................................................................... 9 We value your feedback! ............................................................................................. 9

Chapter 2 Native Hybrid Cloud Architecture 10 Solution architecture ................................................................................................ 11 Key components ....................................................................................................... 12 Hardware resources .................................................................................................. 15 Software resources ................................................................................................... 15

Chapter 3 Before You Begin 17 Introduction ............................................................................................................. 18 Customer pre-deployment tasks ............................................................................... 18 EMC Professional Services pre-deployment tasks ..................................................... 20 Integration with existing IT infrastructure .................................................................. 21 Accessing Pivotal Operations Manager ..................................................................... 21 Accessing Native Hybrid Cloud Monitoring and Reporting ......................................... 22

Chapter 4 Scaling Hardware and Software 24 Scaling compute and storage resources ................................................................... 25 Requesting additional resources for Native Hybrid Cloud .......................................... 25 Modifying OpenStack project quotas for Native Hybrid Cloud ................................... 26 Scaling Pivotal Cloud Foundry .................................................................................. 28

Chapter 5 Native Hybrid Cloud Monitoring and Reporting 31 Introduction ............................................................................................................. 32 Monitoring and reporting architecture ...................................................................... 33 SolutionPacks and Collectors ................................................................................... 34 Dashboards .............................................................................................................. 36 Reports ..................................................................................................................... 37 Thresholds ............................................................................................................... 43 Alerts ........................................................................................................................ 43

Contents


Active Directory and LDAP server integration for reporting ......................................... 44

Chapter 6 Logging 46 Introduction ............................................................................................................. 47 Loggregator .............................................................................................................. 47 Native Hybrid Cloud logging ..................................................................................... 47

Chapter 7 Data Protection 49 Introduction ............................................................................................................. 50 Pivotal Cloud Foundry data protection ...................................................................... 50 Native Hybrid Cloud data protection ......................................................................... 51 Native Hybrid Cloud Installer virtual machine restoration ......................................... 51 Native Hybrid Cloud Blobstore restoration ................................................................ 59 Native Hybrid Cloud Monitoring and Reporting virtual machine restoration ............... 61

Chapter 8 User administration 62 Introduction ............................................................................................................. 63 VxRack Neutrino accounts and users ........................................................................ 63 Pivotal Cloud Foundry identity providers ................................................................... 63 Native Hybrid Cloud Monitoring and Reporting users ................................................ 65

Chapter 9 Support and troubleshooting 66 Customer support ..................................................................................................... 67

Chapter 10 Conclusion 68 Conclusion ............................................................................................................... 69

Chapter 11 Reference documentation 70 Native Hybrid Cloud documentation ......................................................................... 71 VxRack Neutrino documentation ............................................................................... 71 Pivotal Cloud Foundry documentation ...................................................................... 71 Native Hybrid Cloud Monitoring and Reporting documentation ................................. 71

Appendix A Open source license and copyright information 72 Software packages ................................................................................................... 73 GNU General Public License version 3 ...................................................................... 74

Chapter 1: Introduction


Chapter 1 Introduction

This chapter presents the following topics:

Business case .......................................................................................................... 6

Solution overview .................................................................................................... 7

Key benefits ............................................................................................................ 8

Document purpose ................................................................................................... 9

Audience ................................................................................................................. 9

We value your feedback! .......................................................................................... 9



Business case

Businesses are embracing hyper-converged infrastructure and cloud-native frameworks to disrupt conventional business models, differentiate themselves from competitors, and explore new business opportunities. A requirement for growing a business is the ability to analyze consumer data and rapidly and continuously deliver new, innovative, and unique content to consumers. Consumers have come to expect applications to always be available, secure, and updated.

This trend is driving a shift in application-development platforms and processes. Application developers are moving to new practices and technologies like development and operations (DevOps), continuous delivery, agile methodology, twelve-factor application frameworks, microservices, and API-based collaboration. These technologies and practices speed application development and quickly deploy features into production. However, most businesses encounter challenges when transitioning to new practices and technologies.

Application development groups wrestle with decisions about the best system to manage growing application development needs. Short-term revenue goals can displace proper planning for an integrated application development environment. Consequently, disparate applications are installed at different times in various functional areas, resulting in process inefficiencies and software and hardware integration challenges.

Many challenges arise when high-growth application development groups have several applications in silos. These include wasted effort, lack of realtime visibility, and increased integration complexity and cost. IT departments are also under pressure to provide enterprise-quality development environments with a shrinking budget.

The performance and convenience offered by an integrated development environment based on cloud computing and storage addresses these challenges. An integrated development environment can also help application developers decrease the time to market, increase operational agility, and facilitate automated deployment of applications.

The variety and complexity of proprietary and public cloud offerings increases the difficulty of choosing an integrated cloud solution. Several new open source technologies are also available to help create a cloud solution for application development, testing, and deployment. However, IT departments must know how to best use these technologies to drive standardization, integrate open source and proprietary systems, minimize cost, and support service-level agreements.

The availability of the public cloud and the ease with which it can be accessed creates the perception that it is easy for IT to duplicate the same level of service in-house. Planning, designing, and building a private cloud to support cloud native applications can be a complex project that takes too long if you need to roll out a solution to address immediate business needs. IT also needs to maintain and manage the infrastructure supporting these new applications to ensure the environment is reliable, secure, and upgradeable.



As a result, IT departments must make difficult decisions when implementing or creating a cost-effective and cloud-based application development environment. EMC has solved these challenges with Native Hybrid Cloud.

Solution overview

Native Hybrid Cloud is an engineered solution that uses an elastic infrastructure and monitoring tools to support an application production environment. IT professionals can easily monitor, manage, and scale the environment to ensure its fitness for current and future application production needs.

Native Hybrid Cloud provides a predictable, accurate, and protected deployment that is sized correctly and installed on a VxRack System with Neutrino, a hyperconverged infrastructure that is powered by OpenStack cloud compute and ScaleIO storage software. VxRack Neutrino hardware sizing configurations are based on expected Pivotal Cloud Foundry usage and system testing. The virtual infrastructure is sized based on Pivotal Cloud Foundry usage. The Native Hybrid Cloud Monitoring and Reporting dashboard monitors and reports consumption and billing information transparently.

Data protection, including backup and restoration, is provided by OpenStack, Pivotal Cloud Foundry, and EMC ScaleIO®, which provides data replication and redundancy beyond normal OpenStack and Pivotal Cloud Foundry capabilities.

Pivotal Cloud Foundry is a cloud native platform (CNP) on which developers can create, test, deploy, update, and scale applications on public and private clouds. Pivotal Cloud Foundry enables developers to code in multiple languages and frameworks.

Pivotal Cloud Foundry provides developers with a ready-to-use cloud computing environment and application development services, all hosted by virtualized servers on your VxRack Neutrino infrastructure. The services include:

• Pivotal Operations Manager is a web application used to deploy and manage Pivotal Cloud Foundry and associated services such as SSO and Pivotal Cloud Foundry Metrics. It is the industry’s first turnkey enterprise CNP management platform with infrastructure as a service (IaaS) integration.

• Pivotal Cloud Foundry Metrics is a suite of products designed to help operators and developers better understand the health and performance of the Pivotal Cloud Foundry platform and all applications running on it. It includes Java Management Extensions (JMX) bridge for Elastic Runtime. Pivotal Cloud Foundry Metrics collects and exposes system data from Pivotal Cloud Foundry components with a JMX endpoint to help you monitor your installation and assist in troubleshooting.

• Elastic Runtime is the framework that hosts running applications, manages system health, and provides client access to the runtime environment, including running applications through the cloud controller API endpoint.

• Buildpacks provide framework and runtime support for your applications. Buildpacks typically examine user-provided artifacts to determine what

Pivotal Cloud Foundry



dependencies to download and provide instructions on how to configure applications to communicate with bound services.

• Pivotal Marketplace provides developers with a robust self-service user experience that boosts productivity with on-demand access to a large marketplace of mobile and data services, an intuitive console, and open APIs. The Marketplace's managed and user-provided services can be used without the need for IT action.

Native Hybrid Cloud Monitoring and Reporting is resource management software that provides detailed relationship and topology views for virtual or physical hosts, including the underlying infrastructure, to help you visualize infrastructure relationships, analyze and report on its capacity and health, and optimize resources in traditional and software-defined environments.

This software also provides performance and usage views across the layers of the physical and virtual infrastructure to help you understand the impact that infrastructure has on enterprise applications.

EMC has developed a set of manual and automated tools to simplify the deployment of Native Hybrid Cloud on VxRack Neutrino. EMC Professional Services deploys the Native Hybrid Cloud installer as an OpenStack virtual machine instance and it is used to run automated tasks that validate previously collected customer site-related data (network, DNS, SSO, and so on) and run automated scripts that deploy Native Hybrid Cloud components.

Key benefits

Native Hybrid Cloud is an engineered solution from EMC that provides an optimized and pre-tuned application production platform. The solution stack is based on Pivotal Cloud Foundry and integrated with VxRack Neutrino, an OpenStack-based private cloud. Native Hybrid Cloud accelerates the development cycle of cloud-native applications, and allows businesses to deliver new and unique capabilities to market as quickly as possible.

Native Hybrid Cloud enables developers to create cloud native applications in multiple programming languages and track application quality. The platform is based on an integrated infrastructure, which enables IT operators to easily monitor, manage, and scale the development environment.

Integration with Microsoft Active Directory and Lightweight Directory Access Protocol (LDAP) servers makes it easier to manage users, roles, and permissions. OpenStack Horizon dashboard, Native Hybrid Cloud Monitoring and Reporting, Pivotal Operations Manager, and Pivotal Cloud Foundry Metrics give you the tools you need to monitor Native Hybrid Cloud. With Native Hybrid Cloud, customers will benefit from:

• An engineered solution that integrates the industry’s top open source technologies, professional services, and single call support into a cloud-native application development platform that is easy to deploy, use, and grow

Native Hybrid Cloud Monitoring and Reporting

Native Hybrid Cloud automated deployment



• A turn-key, private cloud and infrastructure service that eliminates the time IT spends on complex deployments and updates

• A fully tested and integrated application development, testing, deployment, updating, and management solution

• A virtual infrastructure that can be deployed quickly to reduce the time from planning to coding

• A single platform to write and store code in multiple languages

Document purpose

This document describes an engineered solution for managing a cloud native application production environment with Native Hybrid Cloud. The solution uses VxRack Neutrino, a private cloud-hosting rack-scale hyperconverged appliance that uses OpenStack cloud computing software.

This document introduces the main features and functionality of the engineered solution, describes the individual components, and lists the validated hardware and software environments. This document also describes how the components and functionality of Native Hybrid Cloud and VxRack Neutrino are integrated.

Audience

This document is for DevOps cloud architects, DevOps cloud operators, or application development managers who want to design, manage, and deploy cloud native applications with Native Hybrid Cloud on VxRack Neutrino. Readers should be aware of OpenStack, Pivotal Cloud Foundry, virtualization, networking, and storage technologies, and general IT functions.

We value your feedback!

EMC and the authors of this document welcome your feedback on the solution and the solution documentation. Contact [email protected] with your comments.

Authors: Sergey Schindler, Eoghan Kelleher, Brian Coe.

mailto:[email protected]?subject=Feedback:%20Native%20Hybrid%20Cloud%201.0.1%20Engineered%20Solution%20(H14939.1)

Chapter 2: Native Hybrid Cloud Architecture


Chapter 2 Native Hybrid Cloud Architecture


Solution architecture ............................................................................................. 11

Key components .................................................................................................... 12

Hardware resources ............................................................................................... 15

Software resources ................................................................................................ 15



Solution architecture

This chapter provides an overview of the architectural components and concepts of Native Hybrid Cloud. The diagrams in this section depict the layout of major components that comprise Native Hybrid Cloud. Figure 1 depicts a high-level overview of the components in the Native Hybrid Cloud architecture, which includes:

• Pivotal Cloud Foundry, an industry standard, open source-based, and cloud native application platform, which developers can use to build, deploy, run, and scale applications on public and private clouds.

• Native Hybrid Cloud Monitoring and Reporting and resource management software. IT can use this software to visualize usage relationships; analyze and report on capacity, performance, and health; and optimize resource consumption.

• VxRack Neutrino can concurrently host multiple services with its elastic, scale-out, and hyper-converged design.



Figure 1. Native Hybrid Cloud architecture

Key components

Native Hybrid Cloud uses the following key components in addition to Pivotal Cloud Foundry and VxRack Neutrino.



Native Hybrid Cloud Monitoring and Reporting and Pivotal Cloud Foundry Metrics analyze health, configurations, and capacity growth. You can quickly spot service level agreement (SLA) problems through custom dashboards and reports that meet the needs of a wide range of users and roles. With Native Hybrid Cloud Monitoring and Reporting you can also see capacity consumption across your Pivotal Cloud Foundry deployment with built-in views to help you understand who is using capacity, how much they are using, and when more will be required.

Organizations can take advantage of Native Hybrid Cloud Monitoring and Reporting SolutionPacks and Collectors, which are plug-ins, extensions, and management packs that add functionality to management tools already deployed in data centers. For example, the Generic Host SolutionPack provides custom component monitoring. The JMX Collector delivered with Native Hybrid Cloud enables administrators to get a complete and in-depth picture of Pivotal Cloud Foundry’s health, capacity, and resource availability.

Pivotal recommends using an external Blobstore for Pivotal Cloud Foundry production deployments. The external Blobstore must be compatible with the Amazon Simple Storage Service (Amazon S3) API, which provides developers and IT teams with secure, durable, and highly-scalable object storage. The Blobstore holds application code, Buildpacks, and applications.

In Native Hybrid Cloud, the Blobstore is deployed on the VxRack Neutrino compute service as a cluster of OpenStack virtual machine instances in a high availability configuration. OpenStack Cinder volumes created in VxRack Neutrino provide the backend storage for this Blobstore cluster. A built-in HAProxy load balancer is combined with multiple storage and proxy nodes to ensure the service’s high availability.

Figure 2 shows the data storage architecture of the solution.


SolutionPacks and Collectors for Native Hybrid Cloud Monitoring and Reporting

Blobstore for Pivotal Cloud Foundry



Figure 2. Data storage for Pivotal Cloud Foundry

Pivotal Cloud Foundry, OpenStack, and ScaleIO provide data protection capabilities for Native Hybrid Cloud. Pivotal Operations Manager offers the ability to export Pivotal Cloud Foundry installation settings and assets. When you export an installation, the exported file contains the base virtual machine images, necessary packages, and references to the installation IP addresses.

ScaleIO distributed storage protects Native Hybrid Cloud data by creating multiple redundant copies. An S3-compatible Blobstore uses Cinder volumes protected by ScaleIO replication, and it is used to protect all Pivotal Cloud Foundry applications and metadata. The Blobstore is backed up at a customer-specified interval, which is typically once daily.

Native Hybrid Cloud integration with external identity providers (IDP) such as Active Directory or LDAP servers provides the separate built-in capabilities of VxRack Neutrino, Pivotal Cloud Foundry, and Native Hybrid Cloud Monitoring and Reporting. EMC Professional Services performs IDP integration services for customers.

Data protection

Integration with external identity providers

Logging



Loggregator, the Pivotal Cloud Foundry component responsible for logging, provides a stream of log output from your applications and from Pivotal Cloud Foundry system components that interact with your applications during updates and execution.

Hardware resources

VxRack Neutrino comes in two brick types: high performance and high capacity. Table 1 lists the maximum hardware resources for both brick types. The high performance brick has a 2U chassis with four nodes. The high capacity brick has a 1U chassis with one node.

Table 1. Hardware details

Hardware High performance, each node High capacity, one node

CPU Dual Intel Xeon E5-2600 v3 sockets Dual Intel Xeon E5-2600 v3 sockets

Memory 512 GB 512 GB

Network Dual Port GbE Dual Port GbE

Storage 800 GB SSD One 400 GB SSD (OS)

One 800 GB SSD (caching)

Twenty-two 1.8 TB HDD (data)

Software resources

Table 2 lists the software used in Native Hybrid Cloud.

Table 2. Solution software

Software Version Notes

VxRack Neutrino 1.1 Provides the physical and virtual infrastructure to use Native Hybrid Cloud

Pivotal Cloud Foundry

1.7 Facilitates application production

Pivotal Operations Manager

1.7.10 Provides a graphical interface to manage Pivotal Cloud Foundry components

Pivotal JMX Bridge (Operations Metrics)

1.7.2 Used to help you monitor your installation and assist in troubleshooting

Pivotal Elastic Runtime

1.7.14 build 5 Provides a scalable runtime environment to deploy applications

Ansible 2.3 Used to deploy Native Hybrid Cloud


1.1 Used to monitor Native Hybrid Cloud



Software Version Notes

EMC ViPR® SRM 3.7 SP2 Used to monitor Native Hybrid Cloud

Elasticsearch 2.1.1 Used for log collection and analysis

Logstash 2.1.0 Used for log collection and analysis

Kibana 4.3.1 Used for log collection and analysis

Chapter 3: Before You Begin


Chapter 3 Before You Begin


Introduction ........................................................................................................... 18

Customer pre-deployment tasks ............................................................................ 18

EMC Professional Services pre-deployment tasks .................................................. 20

Integration with existing IT infrastructure .............................................................. 21

Accessing Pivotal Operations Manager .................................................................. 21

Accessing Native Hybrid Cloud Monitoring and Reporting ...................................... 22



Introduction

This chapter provides an overview of the Native Hybrid Cloud installation process, including the work EMC Professional Services performs to install Native Hybrid Cloud and information you will provide to EMC Professional Services. EMC Professional Services performs the site survey, sizes your solution, allocates resources, and integrates existing IT infrastructure.

Customer pre-deployment tasks

The customer must perform these tasks before EMC Professional Services arrive on-site.

Pivotal Cloud Foundry best practices for network isolation require separate virtual networks: a Management network for management functions and floating IPs, and a Developer network for development functions and access to the Pivotal Cloud Foundry Router virtual machines. Native Hybrid Cloud and Pivotal Cloud Foundry components are deployed by EMC Professional Services in a single private virtual network.

The Developer network may be isolated, and access from the Developer network to the Pivotal Cloud Foundry Router virtual machines is enabled by routing from an external customer router or Layer 3 switch. If you want to isolate traffic, you can create a separate virtual network apart from the OpenStack virtual network.

Figure 3. Native Hybrid Cloud and Pivotal Cloud Foundry virtual networks

Pivotal Cloud Foundry supports a deployment environment that is protected by a customer-provided firewall. For instructions on how to configure your firewall for Pivotal Cloud Foundry, and how to verify that Pivotal Cloud Foundry can resolve DNS

Network isolation considerations

Configure your firewall for Pivotal Cloud Foundry



entries behind your firewall, refer to Preparing Your Firewall for Deploying Pivotal Cloud Foundry.

Note: EMC recommends that customers prepare their firewall before EMC Professional Services arrive on-site.

Pivotal Cloud Foundry has specific access requirements for deployments that reside behind a firewall. For more information on how to configure your firewall to allow the required access, refer to Preparing Your Firewall for Deploying Pivotal Cloud Foundry.

Pivotal Cloud Foundry relies on accessing external websites to download components required in Buildpacks, which are used to compile applications that are pushed to Pivotal Cloud Foundry. In cases where external access is not possible from the Pivotal Cloud Foundry network to external websites, use offline or custom Buildpacks. For more information, refer to Custom Buildpacks.

Native Hybrid Cloud relies on an external DNS service for its application name resolution. The DNS service must be provided through an existing customer DNS. An existing customer DNS server must be configured with at least one wildcard DNS domain, such as *.nhc.example.com, to facilitate the publishing to and access of applications hosted by Native Hybrid Cloud. For more information, refer to the General Requirements section of Prerequisites to Deploying Operations Manager and Elastic Runtime.

Note: For production deployments, EMC recommends using two wildcard domains if the system and applications need to be separated.

The typical Pivotal Cloud Foundry deployment for lab and test environments uses a single internal instance of HAProxy. Production environments should use a highly-available and customer-provided load balancing solution for forwarding application traffic to the Pivotal Cloud Foundry Elastic Runtime router IP addresses.

The customer-provided external load balancer must be capable of:

• Providing load balancing to each of the Pivotal Cloud Foundry router IP addresses

• Supporting SSL termination with a wildcard DNS location

• Inserting appropriate X-Forwarded-For and X-Forwarded-Proto HTTP headers to incoming requests

• Optionally supporting WebSockets for application logging with Pivotal Cloud Foundry Loggregator

SNAT is enabled for the VxRack Neutrino software-defined networking service. However, all Pivotal virtual machines must be assigned floating IP addresses to communicate with external targets.

The impact on Pivotal Cloud Foundry deployment on VxRack Neutrino is minimal. Designated Pivotal Cloud Foundry virtual machine instances, such as Pivotal

Firewall and Internet Proxy considerations

DNS considerations

Configure your load balancer

Configure source network address translation

https://docs.pivotal.io/pivotalcf/customizing/config_firewall.html

https://docs.pivotal.io/pivotalcf/customizing/config_firewall.html

http://docs.pivotal.io/pivotalcf/1-7/customizing/config_firewall.html

http://docs.pivotal.io/pivotalcf/1-7/buildpacks/custom.html

https://docs.pivotal.io/pivotalcf/customizing/requirements.html#general

https://docs.pivotal.io/pivotalcf/customizing/requirements.html#general

https://docs.pivotal.io/pivotalcf/devguide/services/log-management.html#loggregator



Operations Manager, HAProxy, or Router require a floating IP assignment. For more information, refer to Network address translation .

EMC Professional Services pre-deployment tasks

Pre-deployment tasks include procedures that do not directly relate to installation and configuration, however, you do need the results from these tasks at the time of installation. Examples of pre-deployment tasks are collection of host names, IP addresses, VLAN IDs, license keys, and installation media. These tasks are performed before the Native Hybrid Cloud is installed and configured. EMC Online Support can provide more information on these prerequisites. See Customer support for customer support contact information.

EMC Professional Services collects customer-specific configuration data for networking, arrays, accounts, and so on. This information must be entered into the Customer Configuration Worksheet during the deployment process. The following tasks must be performed and information must be obtained prior to deploying the Native Hybrid Cloud:

• Pivotal Operations Manager Director administrator username and password

• Pivotal Cloud Foundry DNS A record

• DNS wildcard entry or entries for Pivotal Cloud Foundry

• HAProxy SSL certificate and SSL ciphers (if used) for Pivotal Cloud Foundry

• System and application domain names for Pivotal Elastic Runtime

• Desired Pivotal Cloud Foundry Application Instance (AI) size

• SSO and LDAP servers and SMTP endpoints and credentials

• Customer DNS server and NTP server IP addresses

Prior to deploying Native Hybrid Cloud on VxRack Neutrino, EMC Professional Services ensure that the following components are available in the VxRack Neutrino infrastructure:

• Root password for SSH access to VxRack Neutrino infrastructure servers

• Access to a dedicated OpenStack project in the default domain

• Native Hybrid Cloud user in the dedicated project with full OpenStack administrative rights

• OpenStack private and public networks for the Native Hybrid Cloud tenant, including DNS name server addresses for external virtual machine access to customer DNS and NTP

The Native Hybrid Cloud private network must only contain a single subnet

The Native Hybrid Cloud private network must be a full /24 subnet with no existing IP addresses in use

Required customer data

Native Hybrid Cloud deployment readiness list

http://docs.openstack.org/liberty/networking-guide/intro_network_address_translation.html



• Ability to assign a minimum of 75 floating IP addresses in the Native Hybrid Cloud OpenStack tenant namespace

• Sufficient OpenStack resource quotas are assigned for Native Hybrid Cloud deployment in the OpenStack tenant namespace

Sizing prerequisites

Table 3 provides a list of the minimum OpenStack resource quotas needed for a Native Hybrid Cloud installation on VxRack Neutrino. This table assumes a deployment of three Pivotal Cloud Foundry Diego Cell instances of size m1.xlarge. Additional OpenStack resources are required for larger deployments.

Table 3. Minimum OpenStack resource quotas

OpenStack resource name Minimum quota requirement

vCPU 120

Instances 70

Volumes 30

RAM (MB) 262144

Total size of volumes and snapshots (GiB) 6656

Volume snapshots 50

Floating IP addresses 75

Neutron ports 100

Use the PCF Sizing & Cost Estimation Tool to estimate the necessary resources to deploy Native Hybrid Cloud on OpenStack.

Integration with existing IT infrastructure

EMC Professional Services performs the integration with both VxRack Neutrino and existing IT infrastructure. This includes integrating or installing the following services:

• SSO and LDAP servers

• DNS and NTP servers

• Customer’s load balancer

• Customer’s SSL certificates and SSL ciphers

• MySQL database, if a customer is only using external databases for Pivotal Cloud Foundry

• Customer’s log aggregators

• SMTP endpoints

Accessing Pivotal Operations Manager

https://pcfsizer.cfapps.io/



Use a web browser to access Pivotal Operations Manager when it is successfully deployed.

Steps 1. In your web browser, type the IP address assigned to the Pivotal Operations

Manager virtual machine:

https://opsmgr-address, where opsmgr-address is the Pivotal Operations Manager IP address.

2. On the Pivotal Operations Manager login page, type your Pivotal Operations Manager administrator username and password, as shown in Figure 4.

Figure 4. Pivotal Operations Manager login page

Accessing Native Hybrid Cloud Monitoring and Reporting

By default, the Native Hybrid Cloud Monitoring and Reporting server address is specified as an IP address. Use a web browser to access Native Hybrid Cloud Monitoring and Reporting.

Steps 1. In your web browser, type the Native Hybrid Cloud Monitoring and Reporting

URL:

https://nhc-mnr-address:58080/APG, where nhcmnr-address is the Native Hybrid Cloud Monitoring and Reporting virtual machine instance floating IP address.

2. On the Native Hybrid Cloud home page, type a user name and password, as shown in Figure 5.



Figure 5. Native Hybrid Cloud Monitoring and Reporting login page

Chapter 4: Scaling Hardware and Software


Chapter 4 Scaling Hardware and Software


Scaling compute and storage resources ................................................................. 25

Requesting additional resources for Native Hybrid Cloud ....................................... 25

Modifying OpenStack project quotas for Native Hybrid Cloud ................................. 26

Scaling Pivotal Cloud Foundry ................................................................................ 28



Scaling compute and storage resources

Native Hybrid Cloud does not have direct control over scaling the VxRack Neutrino infrastructure and is dependent on the VxRack Neutrino scale-out capabilities. Native Hybrid Cloud gains access to additional resources when compute and storage resources are scaled out for VxRack Neutrino.

When additional nodes are added to the VxRack Neutrino hardware rack, these nodes must be configured by VxRack Neutrino and provisioned for the compute service. Compute and storage capacity are added as part of every node added to VxRack Neutrino, and disks immediately become part of the ScaleIO disk pool. After new disks are added to ScaleIO, they can be used by Native Hybrid Cloud.

Native Hybrid Cloud has no native discovery mechanism for additional resources. Native Hybrid Cloud is scaled by requesting additional resources. The request is denied if there are no additional resources and fulfilled if the resources are present in VxRack Neutrino.

OpenStack project quotas can be increased so users can gain access to additional resources. Adding hardware capacity in Native Hybrid Cloud does not change OpenStack project quotas.

When the additional compute and storage nodes are added to VxRack Neutrino, Pivotal Operations Manager Director uses an API call to add additional virtual machines. When the request is granted, the Nova scheduler service, which determines how to dispatch compute requests, places the virtual machines on new or existing nodes.

Note: VxRack Neutrino 1.1 and Native Hybrid Cloud 1.1 do not support external storage.

Requesting additional resources for Native Hybrid Cloud

A Cloud Administrator, which is a user with the administrator role in the default VxRack Neutrino account, can add nodes to the Cloud Compute Service. Adding nodes to the Cloud Compute Service provides the virtual compute and storage capacity required for the creation and management of virtual machines and volumes in OpenStack.

Before you begin: Only a Cloud Administrator can perform this operation. There must be three platform service nodes in the VxRack Neutrino system. These nodes are different from the nodes that run the Cloud Compute Service. For more information, refer to the VxRack™ System 1000 with Neutrino 1.1 Administrator Guide.

Steps 1. Select Infrastructure > Nodes.

2. Select Manage > Add to Service.

3. Select Select a Service > Cloud Compute.



4. Click Select next to each node in the Actions column. These are the nodes that you want to add to the Cloud Compute Service. You must select a minimum of three nodes.

5. Click Deploy Service.

A progress banner at the top of the page shows the deployment progress of the various VxRack Neutrino containers and processes that comprise the Cloud Compute Service. The Cloud Compute Service deployment takes approximately 30 minutes. The time depends on the number of nodes selected.

Results When the Cloud Compute Service deployment completes on the nodes, Cloud Compute displays in the Service column next to each node in the Node Management page, verifying that these are now Cloud Compute nodes. Native Hybrid Cloud gains access to the node when the VxRack Neutrino node is added.

Modifying OpenStack project quotas for Native Hybrid Cloud

You can increase OpenStack project quotas after additional nodes are added. The minimum OpenStack project quotas for Native Hybrid Cloud represent a full Native Hybrid Cloud installation with a minimal Pivotal Cloud Foundry installation of Pivotal Operations Manager, Pivotal Elastic Runtime, Pivotal Operations Metrics, and three Pivotal Cloud Foundry Diego cells. The project quotas must be adjusted if you need to scale out or add additional Marketplace services to your Pivotal Cloud Foundry deployment.

Before you begin: Only a Cloud Administrator can perform this operation.

Steps Follow these steps to modify the OpenStack project quotas:

1. Log in to the OpenStack dashboard as the admin user in the default domain.

2. Select Identity > Projects in the OpenStack Dashboard.

3. Select the Native Hybrid Cloud project name in the list of projects.

4. Select Modify Quotas Project in the Actions list box.

5. On the Quota tab, shown in Figure 6, modify quotas for vCPUs and memory to match your desired Pivotal Cloud Foundry sizing increase.



Figure 6. Modifying OpenStack project quotas

6. Click Save when the quotas are modified.



Scaling Pivotal Cloud Foundry

Pivotal Cloud Foundry offers several scaling strategies. These strategies increase the capacity and availability of the Pivotal Cloud Foundry platform and the applications deployed on the platform, and decrease the chances of downtime. The strategies include:

• Scaling out or scaling up the Pivotal Cloud Foundry platform and its components

• Scaling out applications

• Scaling out services

For more information, refer to Zero Downtime Deployment and Scaling in CF.

You can scale out the Pivotal Cloud Foundry platform to deploy multiple instances of platform components to achieve redundancy. For more information, refer to Scaling Instances in Elastic Runtime.

Factors such as user workload can change the amount of disk space and memory an application uses. For many applications, increasing the available disk space or memory can improve overall performance. Similarly, running additional instances of an application can allow the application to handle increased user workload and concurrent requests.

Applications deployed on Pivotal Cloud Foundry can be scaled up or vertically in size by increasing CPU, memory, and storage. Pivotal Cloud Foundry also allows you to horizontally scale an application by creating multiple instances of an application. This is called scaling out.

When an application is scaled out, incoming requests to an application are automatically load balanced across all instances, and each instance handles tasks in parallel with every other instance. Adding more instances allows an application to handle increased usage and network traffic.

You can scale out applications deployed on Pivotal Cloud Foundry by using the Pivotal Applications Manager Console, as shown in Figure 7, or the Pivotal Cloud Foundry command line interface by using the cf scale command.

Scaling Pivotal Cloud Foundry platform components

Scaling Pivotal Cloud Foundry applications

https://docs.cloudfoundry.org/concepts/high-availability.html

https://docs.pivotal.io/pivotalcf/opsguide/scaling-ert-components.html

https://docs.pivotal.io/pivotalcf/opsguide/scaling-ert-components.html



Figure 7. Scaling an application

For more information, refer to Scaling an Application Using cf scale.

Managed services are integrated with Cloud Foundry using APIs, and enable users to provision reserved resources and credentials on demand. Pivotal Cloud Foundry offers managed services that enable users to provision on-demand reserved resources, as shown in Figure 8. Examples of reserved resources include databases on a shared or dedicated server, or accounts on a software as a service (SaaS) application. These resources are called Service Instances and the systems that deliver and operate these resources are called Services.

Service Instances are bound to applications using service brokers. A service broker can provide additional instances of a service to serve multiple application instances. For more information, refer to Custom Services .

Scale Pivotal Cloud Foundry managed services

https://cf-p1-docs-prod.cfapps.io/pivotalcf/devguide/deploy-apps/cf-scale.html

https://docs.pivotal.io/pivotalcf/services/



Figure 8. Pivotal Cloud Foundry managed services

Chapter 5: Native Hybrid Cloud Monitoring and Reporting


Chapter 5 Native Hybrid Cloud Monitoring and Reporting


Introduction ........................................................................................................... 32

Monitoring and reporting architecture ................................................................... 33

SolutionPacks and Collectors ................................................................................ 34

Dashboards ........................................................................................................... 36

Reports .................................................................................................................. 37

Thresholds ............................................................................................................ 43

Alerts .................................................................................................................... 43

Active Directory and LDAP server integration for reporting ..................................... 44



Introduction

Native Hybrid Cloud Monitoring and Reporting resource management software provides comprehensive monitoring, reporting, and analysis for heterogeneous physical and virtual environments. Native Hybrid Cloud Monitoring and Reporting enables IT personnel to visualize relationships, analyze and report on capacity, performance, and health, and optimize resources in traditional and software-defined environments.

The Native Hybrid Cloud Monitoring and Reporting platform provides the core of an out-of-the-box monitoring and reporting solution that you can customize and scale based on your environment and performance requirements. The platform is enhanced and customized with SolutionPacks that support a wide variety of EMC and third-party devices, hosts, and networks.

Native Hybrid Cloud Monitoring and Reporting is an embedded software technology that is common across EMC ViPR®, ViPR SRM, and EMC Service Assurance Suite. By using common technology, EMC provides customers with a consistent look, feel, and experience as they use these products together to manage their data center. The common technology also simplifies deployment, ongoing maintenance, and resource utilization.

As shown in Figure 9, Native Hybrid Cloud Monitoring and Reporting and Pivotal Cloud Foundry Metrics provide monitoring and reporting services and help you analyze health, configurations and capacity growth. You can quickly spot SLA problems through custom dashboards and reports that meet the needs of a wide range of users and roles. With Native Hybrid Cloud Monitoring and Reporting, you can also view capacity consumption across your Pivotal Cloud Foundry deployment with built-in views to help you understand who is using capacity, how much they are using, and when more will be required.

Monitoring and reporting services



Figure 9. Pivotal Cloud Foundry metrics collection for Native Hybrid Cloud Monitoring and Reporting

Monitoring and reporting architecture

All Native Hybrid Cloud Monitoring and Reporting components for Native Hybrid Cloud, including the frontend, primary backend, and collector, are located on a single virtual machine. The components use built-in SolutionPacks and Collectors, including:

• Generic Host SolutionPack for monitoring all Native Hybrid Cloud virtual machines

• JMX Collector for data collection from Pivotal Cloud Foundry Metrics

• Stream Collector for data collection from Pivotal Operations Manager REST API

• Native Hybrid Cloud Monitoring and Reporting Health Collector

Figure 10 shows the Native Hybrid Cloud Monitoring and Reporting architecture.



Figure 10. Native Hybrid Cloud Monitoring and Reporting architecture

SolutionPacks and Collectors

A SolutionPack is an installable application that provides data collection and reporting capabilities for specific entities in your infrastructure. SolutionPacks provide a list of reports, pre-configured alerts, and automation required for Native Hybrid Cloud Monitoring and Reporting dependencies to monitor the managed infrastructure’s performance.

The SolutionPack Center makes updating a SolutionPack or changing a configuration, such as device credentials, as simple as picking applications from an application store. SolutionPacks support server, application, and virtualization systems along with many common third-party infrastructure components.

Collectors retrieve raw data from multiple sources. Collectors can easily be scaled and deployed as business needs grow.



Generic Host SolutionPack

This SolutionPack discovers and monitors physical and virtual servers and provides a global view of hosts in a data center. The Generic Host SolutionPack provides the ability to report, alert, and examine host, capacity usage, and performance measurements. The Host Enterprise Dashboard provides the following Generic Host reports:

• Host information and details

• Performance metrics such as CPU, memory, and disks for host devices

• File systems summary report

• Local and remote disk capacity reports

Native Hybrid Cloud Monitoring and Reporting Health Monitor SolutionPack

Native Hybrid Cloud Monitoring and Reporting Health Monitor SolutionPack monitors the health of your Native Hybrid Cloud Monitoring and Reporting infrastructure to keep the Native Hybrid Cloud Monitoring and Reporting services at optimal performance levels. It provides instant access to performance data, reports, and alerts.

Native Hybrid Cloud Monitoring and Reporting Health main reports include:

• Modules performance

• Collecting level performance

• Backend and database events and utilization

• Server summary

Native Hybrid Cloud Monitoring and Reporting Health metrics include:

• Collectors

• Event processing manager

• Backends

• Tomcat and frontend

• Databases

JMX Collector

The JMX Collector is designed to collect raw values from JMX enabled applications, such as Pivotal Cloud Foundry Metrics. The JMX Collector generates raw values and properties from MBean attribute values and uses regular expressions to transform values obtained from attributes and operations. You can apply multiple transformations on the same value.

Stream Collector

The Stream Collector is a collector module that imports data from various text-based sources using text streaming APIs. Unlike other text-based collectors such as Text Collector, XML Collector, and Remote Shell Collector, this collector parses data as it is received, instead of storing all the data in memory prior to parsing it.



The Stream Collector retrieves absolute values for Pivotal Cloud Foundry virtual machine memory, virtual CPUs, and ephemeral and persistent disks. It also retrieves the Pivotal Cloud Foundry application chargeback information

Dashboards

The Native Hybrid Cloud Monitoring and Reporting user interface provides end-to-end visibility into the performance, health, availability, and configuration of infrastructure; this visibility includes hosts, storage, adapters, and switches, as shown in Figure 11. You can also view virtual storage, storage chargeback, and capacity for object and file storage.

Figure 11. Native Hybrid Cloud Monitoring and Reporting dashboard

Figure 12 shows the Native Hybrid Cloud Monitoring and Reporting Health dashboard, which displays a summary of component health. Green, yellow, and red are used to indicate good health, potential problems, and components that need immediate attention.



Figure 12. Native Hybrid Cloud Monitoring and Reporting Health dashboard

Reports

The Native Hybrid Cloud report library includes reports for logs, reports for Pivotal Cloud Foundry runtime resources and operations, chargeback reports, and Pivotal Cloud Foundry health reports. Table 4, Table 5, Table 6, Table 7, and Table 8 show the available Native Hybrid Cloud Monitoring and Reporting reports.

Table 4. Alerts, chargeback, and log reports

Alerts Chargeback Logs (Kibana)

Alerts Summary Chargeback by Organization Dashboard

All Alerts Chargeback by Space Filters

Top Components with Critical Alerts

Chargeback by Service Plan



Alerts Chargeback Logs (Kibana)

Unacknowledged Alerts Chargeback by Application

Unassigned Alerts

Alerts for Watched Components

High Impact Alerts

Table 5. Hosts and Native Hybrid Cloud Monitoring and Reporting health reports

Native Hybrid Cloud hosts Native Hybrid Cloud Monitoring and Reporting health

Host Inventory Native Hybrid Cloud Monitoring and Reporting server stress

Host Information CPU Usage

File System Usage Memory Usage

Host Situations to Watch File System Usage

Collection Health

Database Health

Server Critical Logs

Table 6. Blobstore and situations to watch reports

S3-compatible Blobstore Situations to watch

Blobstore Health Reports Application Staging Issues

Blobstore Health Alerts CloudController Health Issues

Logging Health Issues

etcd Key-Value Store Health Issues

Table 7. Applications and dashboard overview reports

Applications Dashboard overview

Organizations

• Org Summary with Spaces, Services, Apps, and Users

• Org Summary with Spaces and Quotas

Alerts

• Alerts Summary (Link to summary)

• Alert Summary History (Link to history)



Applications Dashboard overview

Spaces

• Spaces Summary with Services, Service Plans, and Apps

• Spaces Details

Capacity

• Pivotal Cloud Foundry Total Resource Consumption vs. Free (Bar Chart)

• Pivotal Cloud Foundry Spaces by Quota Consumption (Bar Chart)

• Pivotal Cloud Foundry Orgs by Total Used Capacity (Stacked Chart with Trend)

• S3-compatible Blobstore Capacity Utilization (Bar Chart)

Applications

• Apps Summary with Users, Services, and Resources Consumption

• Applications Details

Performance

• Top-5 Apps by Resource Consumption (vCPU, RAM, Disk Hours) (Bar Chart)

• Top-5 Orgs by Resources Consumption (vCPU, RAM, Disk Hours) (Bar Chart)

Services

• Service Summary with Service Plans and Apps

Service Plans

Buildpacks

Droplets

Users

Table 8. Pivotal Cloud Foundry operations and runtime resources reports

Pivotal Cloud Foundry operations Pivotal Cloud Foundry runtime resources

Global Status

• Stress

Heatmap of Pivotal Cloud Foundry Components by Health and Alerts

Pivotal Cloud Foundry virtual machine inventory runtime resources (vCPU, RAM, Disk Table)

CloudController

• CC Health (Table)

DEA (Diego)

• DEA (Diego) Health (Table)

• DEA (Diego) Performance (Table)

• DEA (Diego) Droplet Status (Table)

DopplerServer

• DopplerServer Health (Table)



Pivotal Cloud Foundry operations Pivotal Cloud Foundry runtime resources

HealthManager

• HealthManager Health (Table)

• Applications Health (Table)

LoggregatorTrafficController

• Loggregator Health (Table)

Router

• Router Health (Table)

• Router Performance (Table)

Collector

• Collector Performance (Table)

etcd Key-Value Store

• etcd Key-Value Store Health (Table)

UAA

• UAA Health (Table)

Figure 13 shows the Native Hybrid Cloud Reports dashboard.



Figure 13. Native Hybrid Cloud Reports dashboard

Custom reports

Native Hybrid Cloud Monitoring and Reporting reports enable operators to combine information from various existing reports into a customized report specific to your enterprise. You can edit report definitions, including timespans and sampling types, and make customizations visible to other users.

The pinned reports feature lets you create new reports that suit your needs by reusing existing tables and graphs and combining them onto a single customized report. Each pinned report becomes an element on the customized report. You can rearrange those elements in the “My Reports” node.

This node is a workspace for creating customized reports and testing changes before making the reports available to other users. In a fresh installation, this node might not be available until you create a new report. When the customized report is ready, you can make it visible to other users by placing it in a new location in the report tree.

Additional report customization features are available in Edit mode. This mode lets you change items such as the style of the report graphs, the frequency of samples shown, and the range of data to include. Changes that you make are saved in the



original report and are visible to all users immediately after you apply them. The changes apply to all views of the report, whether the report is viewed from its original location in the report tree or pinned as an element in a customized report.

Edit mode also permits more advanced operations, such as applying filters and expansions, creating formulas for new statistics, and defining new reports. You can export and schedule customized reports the same as you would for existing reports.

Create custom Native Hybrid Cloud Monitoring and Reporting reports

Administrators can develop and deploy custom reports in the Native Hybrid Cloud Monitoring and Reporting server, which can then be viewed in the Native Hybrid Cloud Monitoring and Reporting front-end server.

Steps 1. Log in to an instance of Native Hybrid Cloud Monitoring and Reporting where

the JMX collector is configured.

For example, https://< Native Hybrid Cloud Monitoring and Reporting URL>:58080/APG/admin/, using the credentials admin/changeme.

2. Click Report Pack and create a new report pack.

3. Type the required fields and upload the XML file to add the new template. The XML is also available under Reports.

4. Browse to https://< Native Hybrid Cloud Monitoring and Reporting URL>:58080/APG/ and view the reports under PCF Operations.

Scheduled Reports

Scheduled Reports are like the Stored Reports feature but with more options and features. Scheduled Reports are generated based on a schedule. Using Scheduled Reports allows you execute or run a report on a regular basis, according to your specification (for example, off-load, off-hours, sent by mail, stored, and so on).

You can choose and adjust the report so it displays the information you need and set various parameters of a scheduled report.

Exporting reports

From the Export tab, you have access to a full set of options for exporting the current report. You can export a report in these formats:

• PDF format—generates the report in a PDF format you can save or print

• CSV format—exports the report in a comma separated values file

• XLS format—exports the report to Microsoft Excel

• XLS 1 column—exports the report to Microsoft Excel, but all values are in one column

• PNG image—exports the graphic to an image

• JPEG image—exports the graphic to an image

• SVG image—exports the graphic to an image



• XML format—dependent upon current mode

Browse Mode—exports the report’s data to an XML file, which can then be used, for example, by a third party tool

Edit Mode—exports the report’s template, which can be re-imported in Watch4net

Sharing Native Hybrid Cloud Monitoring and Reporting reports

You can share reports using:

• Email—if a report is sent by email, the fields in this tab can be used to configure the report format and destination. This allows the report to be sent by email. The report format can be specified, as well as a subject and a short message. HTML tags are allowed in report emails.

• Web—additionally, Native Hybrid Cloud Monitoring and Reporting reports can be shared through the web by embedding the report URL into a custom portal.

Thresholds

Native Hybrid Cloud Monitoring and Reporting uses threshold settings to apply visual cues to values that fall within defined ranges. When a value’s threshold is breached or it falls outside of the defined range, an alert is generated. The visual cues are for informational purposes only. They do not have any other effects in the reporting system. The visual cues can enhance your interpretation of the metrics. For example, they can:

• Help you classify the data

• Draw attention to high or low values

• Provide reassurance that connections or availability are working

• Provide additional information useful in your working environment

Some reports come with predefined thresholds. You can edit existing threshold boundaries and threshold types, add new thresholds, and delete thresholds.

Alerts

Native Hybrid Cloud Monitoring and Reporting generates threshold alerts based on metric data that is consolidated from external sources. You must enable the threshold alert definitions for each source. You can use the default alert definitions available or create a custom definition and then enable it.

Alert reports support these features that allow you to examine data in greater detail:

• From the summary-level bar and pie charts, you can click a bar or a section in a pie chart to open a tabular report that lists the alerts in the summarized category.

• From most of the tabular reports, you can click a row in the table to open a detailed report for a single alert.



Administrators can mark alerts as acknowledged and take ownership of alerts. These actions are convenient, optional ways to track and organize alerts.

When there is a reoccurrence of an alert, the latest alert is shown on a report and the state of the existing alert changes from ACTIVE to INACTIVE. When an alert becomes INACTIVE, it is automatically closed.

• When a MOMENTARY alert is acknowledged, the state of the alert changes from ACTIVE to INACTIVE and the alert is closed. Closed alerts are not available on the All Alerts Report.

• When a DURABLE alert is acknowledged, it remains ACTIVE and remains on the alerts reports with Yes in the ACK column.

Figure 14 shows the Native Hybrid Cloud Alerts dashboard.

Figure 14. Native Hybrid Cloud Alerts dashboard

Active Directory and LDAP server integration for reporting



Native Hybrid Cloud Monitoring and Reporting uses a Java interface contained within Apache Tomcat to connect to an external managed security server such as Active Directory or LDAP servers. This interface consists of multiple plug-ins that support connections to different types of user access databases. JNDIRealm is the plug-in used for LDAP server integration.

Realm is a database that Tomcat uses to identify authorized web application users. The default realm in ViPR SRM is a local realm. In a local realm, the user accounts and roles are stored in the local master database.

LDAP authentication mechanisms rely on the JNDI Directory Realm. Java Naming and Directory Interface (JNDI) is a set of APIs used to interact with naming services and directory services. When connecting with a LDAP user, Native Hybrid Cloud Monitoring and Reporting creates a user entry in the local database and classifies the user as an external user so that the administrator can add access rights.

Chapter 6: Logging


Chapter 6 Logging


Introduction ........................................................................................................... 47

Loggregator ........................................................................................................... 47

Native Hybrid Cloud logging .................................................................................. 47

Chapter 6: Logging


Introduction

Native Hybrid Cloud logging capabilities are an integral part of the existing customer logging technologies and process. In addition to the existing Pivotal Cloud Foundry log aggregation features, Native Hybrid Cloud also makes use of the open source tools, such as Elasticsearch, Logstash and Kibana. Native Hybrid Cloud also includes preconfigured log filters and dashboards to simplify the analysis of event logs and log-based troubleshooting.

Loggregator

Loggregator, the Pivotal Cloud Foundry component responsible for logging, provides a stream of log output from your application and from Pivotal Cloud Foundry system components that interact with your application during updates and execution.

By default, Loggregator streams logs to your terminal. To retain more than the limited amount of logging information that Loggregator can buffer, this solution uses the ELK Stack to collect, analyze and display logs for management and operational analysis. The logs visualized in Kibana are presented to the user by a Native Hybrid Cloud Monitoring and Reporting report configured as an “external” report type.

Native Hybrid Cloud logging

Native Hybrid Cloud logging uses the Elastic platform of open source projects designed to search, analyze, and visualize your data, allowing you to get actionable insight in real time.

Elasticsearch is a distributed open source search and analytics engine, designed for horizontal scalability, reliability, and easy management. It combines search capabilities and powerful analytics with a sophisticated, developer-friendly query language covering structured, unstructured, and time-series data.

Elasticsearch is based on Apache Lucene. It provides a distributed, multitenant-capable full-text search engine with a RESTful web interface and schema-free JSON documents. Based on a Performance and Scale (P&S) evaluation of Elasticsearch, EMC Professional Services may require fewer or more Elasticsearch server nodes. These server nodes house the search service and its indexes and databases.

Logstash is a flexible, open source data collection, enrichment, and transportation pipeline. With connectors to common infrastructure for easy integration, Logstash receives, processes, and outputs logs, and presents a powerful pipeline for log storage, query and analysis. Logstash is designed to efficiently process a growing list of log, event, and unstructured data sources for distribution into a variety of outputs, including Elasticsearch.

Logstash runs a Native Hybrid Cloud Monitoring and Reporting node inside a container. It must be dynamically configured to communicate to a corresponding elastic search service and Native Hybrid Cloud Monitoring and Reporting service.

Elasticsearch

Logstash

https://www.elastic.co/products/elasticsearch

https://www.elastic.co/products/logstash

https://www.elastic.co/products/kibana

https://docs.pivotal.io/pivotalcf/loggregator/architecture.html

https://www.elastic.co/

Chapter 6: Logging


Kibana is an open source data visualization platform that allows you to graphically interact with your data. It is a data visualization plug-in for Elasticsearch that provides visualization capabilities in addition to the log content indexed on an Elasticsearch cluster. Users can create bar charts, line and scatter plots, or pie charts and maps from large volumes of logs. Kibana’s browser-based interface enables you to quickly create and share dynamic dashboards that display changes to Elasticsearch queries in real time.

You can construct search result visualizations in the Visualization page. Each visualization is associated with a search. For more information on configuring log visualization with Kibana, refer to the Kibana User Guide .

Kibana

https://www.elastic.co/guide/en/kibana/current/index.html

Chapter 7: Data Protection


Chapter 7 Data Protection


Introduction ........................................................................................................... 50

Pivotal Cloud Foundry data protection .................................................................... 50

Native Hybrid Cloud data protection ....................................................................... 51

Native Hybrid Cloud Installer virtual machine restoration ....................................... 51

Native Hybrid Cloud Blobstore restoration ............................................................. 59

Native Hybrid Cloud Monitoring and Reporting virtual machine restoration ............ 61



Introduction

The built-in capabilities of Pivotal Cloud Foundry, Native Hybrid Cloud, and VxRack Neutrino provide the data protection and recovery capabilities for this solution.

Pivotal Cloud Foundry data protection

Pivotal Operations Manager lets you export the current Pivotal Cloud Foundry installation settings and assets. When you export an installation, the exported file contains the base virtual machine images, necessary packages, and references to the installation IP addresses.

The Pivotal data protection procedure includes steps to create copies of critical databases, such as the Cloud Controller, User Account and Authentication (UAA) database, MySQL databases, and Applications Manager databases. EMC Professional Services or an expert administrator can perform the data protection procedure. For more information, refer to Backing Up Pivotal Cloud Foundry.

The complete state of a Pivotal Elastic Runtime deployment is protected by capturing the following:

• Pivotal Cloud Foundry installation settings

• Critical databases:

Pivotal MySQL server database

Cloud Controller database

UAA database

Applications Manager database

S3-compatible Blobstore

Note: Native Hybrid cloud replaces the Network File System (NFS) server storage used by Pivotal Cloud Foundry with a S3-compatible Blobstore.

To create a backup copy of an Elastic Runtime deployment, you must temporarily stop the Cloud Controller virtual machines (cloud_controller_partition and cloud_controller_worker) and save all of the above and your database encryption credentials to restoration files. To restore a deployment, you must temporarily stop the Cloud Controller virtual machines and restore the state of each component from the restoration files.

For instruction on protecting Elastic Runtime, refer to Backing Up Pivotal Cloud Foundry. For instructions on restoring Elastic Runtime, refer to Restoring Pivotal Cloud Foundry from Backup.

Pivotal recommends that you frequently export your installation settings. Always export an installation before importing a new one. Import an installation to restore your settings or to share your settings with another user.

Export installation settings

http://docs.pivotal.io/pivotalcf/customizing/backup-settings.html

https://docs.pivotal.io/pivotalcf/customizing/backup-restore/backup-pcf.html

https://docs.pivotal.io/pivotalcf/customizing/backup-restore/backup-pcf.html

https://docs.pivotal.io/pivotalcf/customizing/backup-restore/restore-pcf.html

https://docs.pivotal.io/pivotalcf/customizing/backup-restore/restore-pcf.html



Pivotal Operations Manager enables you to export the current Pivotal Cloud Foundry installation settings and assets. When you export an installation, the exported file contains the base virtual machine images, necessary packages, and references to the installation IP addresses.

Native Hybrid Cloud data protection

The Native Hybrid Cloud Installer virtual machine is protected by taking snapshots at a customer-specified interval, which is typically once daily. These virtual machine snapshot images are stored in the Glance image repository.

The S3-compatible Blobstore is backed up at a customer-specified interval, which is typically once daily. The automated process involves quiescing I/O, flushing all data down to disk, taking a snapshot of the storage volumes, and then un-quiescing the I/O. A golden copy volume is then created from each snapshot, and can be used immediately. The snapshots and old backup volumes are deleted on successful creation of the new backup volumes.

The Native Hybrid Cloud Monitoring and Reporting solution is an OpenStack virtual machine and an associated OpenStack Cinder volume. Daily backups of Native Hybrid Cloud Monitoring and Reporting include backups of the virtual machine and its associated volume.

Native Hybrid Cloud creates a backup schedule for the Native Hybrid Cloud Monitoring and Reporting virtual machine. The typical backup interval, which an administrator can modify, is 24 hours. This preserves the historical data collected by Native Hybrid Cloud Monitoring and Reporting.

Note: Only the last Native Hybrid Cloud Installer, Native Hybrid Cloud Monitoring and Reporting, and Blobstore backups are retained.

Native Hybrid Cloud Installer virtual machine restoration

The Native Hybrid Cloud Installer virtual machine can be restored in case of failure. Before you restore it you must verify that a valid backup of the Native Hybrid Cloud Installer virtual machine exists in OpenStack. Then you can delete the failed Native Hybrid Cloud Installer virtual machine.

Steps 1. In the OpenStack dashboard, go to Project > Compute > Images.

2. Verify that the OpenStack images contain a snapshot image of the Native Hybrid Cloud Installer virtual machine. Valid snapshots are named in the following format:

NHC-InstallerDD-MM-YYYY

Native Hybrid Cloud Installer virtual machine protection

Native Hybrid Cloud virtual Blobstore protection

Native Hybrid Cloud Monitoring and Reporting virtual machine protection



3. In the OpenStack dashboard, go to Project > Compute > Instances to remove the Native Hybrid Cloud Installer virtual machine.

4. Type nhc-installer in the Instance Name field and click Filter to filter on the Native Hybrid Cloud Installer virtual machine instance, as shown in Figure 15.

Figure 15. Native Hybrid Cloud Installer virtual machine instance

5. If the Native Hybrid Cloud Installer virtual machine is not deleted and is in an Error state, click the Action list box and select Terminate Instance, as shown in Figure 16.



Figure 16. Select terminate instance

Follow the steps below to restore the Native Hybrid Cloud Installer virtual machine when the instance is terminated.

Note: Contact EMC Online Support for assistance if you cannot delete the Native Hybrid Cloud Installer virtual machine.

Steps 1. Retrieve the private IP address that was assigned to the Native Hybrid Cloud

Installer virtual machine. This was recorded by EMC Professional Services in the Native Hybrid Cloud Configuration Workbook.



2. In a web browser, open a connection to the Neutrino OpenStack dashboard.

3. Log in to the OpenStack dashboard as the Native Hybrid Cloud tenant.

4. Go to Project > Compute > Images.

5. Locate the Native Hybrid Cloud Installer virtual machine snapshot image, as shown in Figure 17.

Figure 17. Native Hybrid Cloud snapshot images

6. Select the image name to view the image details.

7. Record the Image ID in the Image Overview screen, as shown in Figure 18.

Figure 18. Snapshot image details

8. Go to Project > Compute > Instances.

9. Locate a running Native Hybrid Cloud virtual machine in the Instances screen, as shown in Figure 19.



Figure 19. Instances screen

10. Select one of the running instance names to view the instance details.

11. Scroll down to the Metadata section and record the key name, as shown in Figure 20.

Figure 20. Key name

12. Go to Project > Network > Networks in the OpenStack dashboard.

13. Select the network name for Native Hybrid Cloud, as shown in Figure 21.

Figure 21. Networks screen

14. Record the ID of the private network in the Network Details screen, as shown in Figure 22.



Figure 22. Network details

15. Select one of the running Native Hybrid Cloud virtual machines.

16. Select Associate Floating IP in the list box, as shown in Figure 23.

Figure 23. Associate a floating IP address

17. Select a floating IP address in the IP Address menu, as shown in Figure 24.

Figure 24. Manage floating IP address associations

a. If there are no floating IP addresses available, click the + icon to associate a new floating IP to the Native Hybrid Cloud tenant, as shown in Figure 25.



Figure 25. Associate a new floating IP address

b. In the Allocate Floating IP screen, click Allocate IP to allocate a new floating IP address, as shown in Figure 26.

Figure 26. Allocate a floating IP address

18. When the floating IP address is selected, click Associate to associate the floating IP address with the selected virtual machine, as shown in Figure 27.



Figure 27. Manage floating address associations

19. Open an SSH session to the floating IP address you have just assigned, using your Native Hybrid Cloud key pair file and the root account.

20. Download the OpenStack RC file to authenticate against the OpenStack command line from the following location in Horizon: Project > Compute > Access & Security-> API Access.

21. Click Download OpenStack RC File v2.0.

22. In the SSH session create a new file using a text editor and paste the contents of the RC file into the new file.

23. Change the OS_AUTH_URL version from v3 to v2.0 as shown below and save your changes.

export OS_AUTH_URL=https://desert.neutrino.lab.com:6100/v2.0

Figure 28. OS_AUTH_URL version

24. Source the RC file using the following command: source <rc_filename>

25. Run the command below to restore the Native Hybrid Cloud Installer virtual machine from the snapshot image, using the retrieved image ID, NHCSecurityGroup, key pair name , network ID, and private IP address from the Native Hybrid Cloud Configuration Workbook:

nova boot NHC-Installer --image IMAGE --flavor 2 \ --security-groups SECURITYGROUP --key-name KEYNAME \ -nic net-id=NEUTRON_NETWORK_ID,v4-fixed-ip=IP_ADDRESS

26. Return to the OpenStack Dashboard when the Nova boot command is complete.



27. When the Native Hybrid Cloud Installer virtual machine has successfully booted, follow the steps outlined above to re-assign a floating IP address to the virtual machine.

28. Remove the floating IP from the Native Hybrid Cloud Installer virtual machine that was temporarily used to issue the Nova command to create the Native Hybrid Cloud Installer virtual machine.

When the Native Hybrid Cloud virtual machine is restored, subsequent backup cycles create backup copies of the restored running instance.

Native Hybrid Cloud Blobstore restoration

If a proxy or storage node is lost, there is no impact due to the high availability design of the Blobstore. Customers can create a new node. For a storage node, customers can create a new storage volume and synchronize data to it from the remaining nodes. It is not restored from a copy. Customers must initiate all restores.

Native Hybrid Cloud provides support for three restore scenarios:

• Restore from complete failure

• Restore a single proxy node

• Restore a single storage node and associated volume

The sections below outline the processes for restoring from each of these failure scenarios.

Note: Contact EMC Online Support if you cannot restore the storage node or proxy node to their original private IP addresses.

All Blobstore restores must be initiated from the Native Hybrid Cloud Installer virtual machine. Access the Native Hybrid Cloud Installer virtual machine using these steps.

Steps 1. Open the Neutrino OpenStack user interface in a web browser.

2. Log in using Native Hybrid Cloud tenant credentials.

3. Go to Project > Compute > Instances.

4. Use your OpenStack Native Hybrid Cloud SSH key pair to open an SSH session to the Native Hybrid Cloud Installer virtual machine’s floating IP address.

ssh -i emcnhc.pem [email protected]

Note: The OpenStack Native Hybrid Cloud key pair is provided by EMC Professional Services on completion of the installation and configuration of this solution.



Follow this restore from a complete failure of the Native Hybrid Cloud Blobstore, where all storage nodes, proxy nodes, and storage volumes have failed or have been deleted.

Steps 1. Verify that all three storage nodes, both proxy nodes, and the three storage

volumes have failed.

2. Terminate the storage node and proxy node instances if they are not already deleted. Storage nodes are named “nhc-swift-storage-#” and proxy nodes are named “nhc-swift-proxy-#”.

3. Delete the storage node volumes if they are not already deleted. Storage volumes are named “swift-<storage_node_ip>”.

4. Run the nhc-blobstore redeploy command to create new storage node and proxy node instances and attach the backup volumes. Refer to the /opt/emc/nhc/config/nhc-fixed-ip.yml file for the proxy node and storage node IP addresses.

nhc-blobstore redeploy --proxy-nodes <proxy_node_1_IP>,<proxy_node_2_IP> --storage-nodes <storage_node_1_IP>,<storage_node_2_IP>,<storage_node_3_IP>

5. Verify that the storage nodes, proxy nodes, and storage volumes are created.

6. Verify that applications can be successfully pushed.

7. Perform a fresh backup using the swift-backup command.

Follow the steps outlined below to restore a single proxy node in the Native Hybrid Cloud Blobstore.

Steps 1. Verify that the proxy node has failed.

2. Terminate the proxy node instances if they are not already deleted. Proxy nodes are named “nhc-swift-proxy-#”.

3. Run the nhc-blobstore redeploy command to create new proxy node instances. Refer to the /opt/emc/nhc/config/nhc-fixed-ip.yml file for proxy node IP addresses.

nhc-blobstore redeploy --proxy-nodes <proxy_node_IP>

4. Verify that the proxy node is created.



Restore from complete failure

Restore a single proxy node

Restore a single storage node and associated volume



Follow the steps outlined below to restore a single Storage node and its volume in the Native Hybrid Cloud Blobstore.

Steps 1. Verify that the storage node and its volume have failed.

2. Terminate the storage node instance if it is not already deleted. Storage nodes are names “nhc-swift-storage-#”.

3. Delete the associated storage node volume if it is not already deleted. Storage volumes are named “swift-<storage_node_ip>”.

4. From an SSH session to NHC Installer-VM, run the nhc-blobstore redeploy command to create new storage node instances and attach the backup volume. Refer to the /opt/emc/nhc/config/nhc-fixed-ip.yml file for proxy node and storage node IP addresses.

nhc-blobstore redeploy --storage-nodes <storage_node_IP> --from-backup

5. Verify that the storage node and storage volume are created.



Note: During redeployment of the Swift node, if you see one of the following messages, rerun the redeploy command: "mount /dev/vdb on /srv/node/vdb failed: Structure needs cleaning" or "mkfs.xfs: /dev/vdb appears to contain a partition table (DOS)."

Native Hybrid Cloud Monitoring and Reporting virtual machine restoration

Contact EMC Online Support if you need to restore the Native Hybrid Cloud Monitoring and Reporting virtual machine.

Chapter 8: User administration


Chapter 8 User administration


Introduction ........................................................................................................... 63

VxRack Neutrino accounts and users ...................................................................... 63

Pivotal Cloud Foundry identity providers ................................................................ 63

Native Hybrid Cloud Monitoring and Reporting users ............................................. 65



Introduction

This section provides information about configuring Native Hybrid Cloud users so authenticated users can log in and use Native Hybrid Cloud services and applications associated with their projects.

VxRack Neutrino accounts and users

In addition to built-in account services, VxRack Neutrino supports the addition of external identity providers, such as Active Directory or LDAP servers. New accounts, projects, and users can be created in the VxRack Neutrino local database using Accounts menu, as shown in Figure 29.

Figure 29. VxRack Neutrino Account Management page

Refer to the VxRack™ System 1000 with Neutrino 1.1 Administrator Guide for instructions on adding identity providers, accounts, projects, and users.

Pivotal Cloud Foundry identity providers

Pivotal Cloud Foundry enables you to create local users, and integrate them with external identity providers, as shown Figure 30. Local users are able to create organizations and spaces, as well as push new applications to the Pivotal Cloud Foundry platform.



Figure 30. Pivotal Elastic Runtime Administration page

Refer to the following Pivotal Cloud Foundry documents for additional details:

• Creating New Elastic Runtime User Accounts

• Configuring LDAP

• Adding Existing LDAP Users to a Pivotal Cloud Foundry Deployment

• Orgs, Spaces, Roles, and Permissions

https://docs.pivotal.io/pivotalcf/customizing/creating-account.html

https://docs.pivotal.io/pivotalcf/opsguide/ldap-uaa.html

https://docs.pivotal.io/pivotalcf/customizing/ldap-user-management.html

https://docs.pivotal.io/pivotalcf/concepts/roles.html



Native Hybrid Cloud Monitoring and Reporting users

Native Hybrid Cloud Monitoring and Reporting enables you to add local user accounts directly using the Administration page, as shown in Figure 31.

Figure 31. Native Hybrid Cloud Monitoring and Reporting user management

Refer to the EMC ViPR SRM Administrator's Guide for additional information on adding local user accounts, as well as integrating them with external identity providers.

Chapter 9: Support and troubleshooting


Chapter 9 Support and troubleshooting


Customer support .................................................................................................. 67

Chapter 9: Support and troubleshooting


Customer support

You can get EMC support, product, and licensing information as follows:

Product information

For documentation, release notes, software updates, or information about EMC products, go to EMC Online Support.

Technical support

Go to EMC Online Support and click Service Center to access options for contacting EMC Technical Support. Contact your EMC sales representative for details about obtaining a valid support agreement to open service requests or with questions about your account.

Upgrading Native Hybrid Cloud

EMC Professional Services performs all Native Hybrid Cloud upgrades.

https://support.emc.com/

https://support.emc.com/

Chapter 10: Conclusion


Chapter 10 Conclusion


Conclusion ............................................................................................................ 69

Chapter 10: Conclusion


Conclusion

Reducing IT operational expenditures while simultaneously increasing the reliability and capability of application production environments is a top priority for many companies. Cost, stability, visibility, and ease of use are often key considerations when an enterprise evaluates new technology solutions.

Native Hybrid Cloud provides a flexible application production environment that can economically scale based on your company’s needs. Using Native Hybrid Cloud enables IT organizations to meet or exceed their goals to save money and maintain dependable service with an easily-managed application production system. With Native Hybrid Cloud, customers realize the following benefits:

• Decreased costs associated with environment scalability

• Greater flexibility in cloud migration

• Rapid provisioning and application deployment and management

• Faster time to market for applications

• Improved application quality through cloud-based quality assurance services

• Integrated support for agile application development practices, and integration with developer eco-systems

• Failure detection and health remediation in addition to monitoring, logs, and metrics

• Single point of contact for support issues

Chapter 11: Reference documentation


Chapter 11 Reference documentation


Native Hybrid Cloud documentation ....................................................................... 71

VxRack Neutrino documentation ............................................................................ 71

Pivotal Cloud Foundry documentation .................................................................... 71

Native Hybrid Cloud Monitoring and Reporting documentation ............................... 71



Native Hybrid Cloud documentation

The following document, available at EMC.com, provides additional and relevant information:

• Native Hybrid Cloud, OpenStack Edition with VxRack Neutrino Reference Architecture Guide 1.1

VxRack Neutrino documentation

The following documents, available at EMC.com, provide additional and relevant information:

• VxRack™ System 1000 with Neutrino 1.1 Release Notes

• VxRack™ System 1000 with Neutrino 1.1 Administrator Guide

• VxRack™ System 1000 with Neutrino 1.1 Hardware Guide

• VxRack™ System 1000 with Neutrino 1.1 Security Configuration Guide

Pivotal Cloud Foundry documentation

The following Pivotal Cloud Foundry documents, available at Pivotal.io, provide additional and relevant information:

• Pivotal Cloud Foundry Documentation

• Using Operations Manager

• Operator's Guide

• Administering and Operating Cloud Foundry

• Using the Apps Manager

• Buildpacks

Native Hybrid Cloud Monitoring and Reporting documentation

The following documents, available at EMC.com, provide additional information about the EMC ViPR Storage Resource Management Suite, the basis for Native Hybrid Cloud Monitoring and Reporting:

• EMC ViPR SRM Product Documentation Index

• EMC ViPR SRM 3.7.2 Administrator's Guide

• ViPR SRM 3.7.2 - SolutionPack Metrics and Reports Matrix

• Storage Resource Management Suite

• Storage Resource Management Fundamentals e-Learning

http://www.emc.com/

http://www.emc.com/

http://lglor056/caspiandocs/rel_notes/VxRack_System_1000_w_Neutrino_1.1_RNs.pdf

http://lglor056/caspiandocs/admin/VxRack_System_1000_w_Neutrino_1.1_Administrator_Guide.pdf

http://lglor056/caspiandocs/hw_guide/VxRack_System_1000_w_Neutrino_1.1.0.0_Hardware_Guide.pdf

http://lglor056/caspiandocs/sec_guide/VxRack_System_1000_w_Neutrino_Security_Configuration_Guide.pdf

https://pivotal.io/

https://cf-p1-docs-prod.cfapps.io/pivotalcf/getstarted/pcf-docs.html

http://docs.pivotal.io/pivotalcf/customizing/index.html

http://docs.pivotal.io/pivotalcf/opsguide/index.html

http://docs.pivotal.io/pivotalcf/adminguide/index.html

http://docs.pivotal.io/pivotalcf/console/index.html

http://docs.pivotal.io/pivotalcf/buildpacks/index.html

http://www.emc.com/

https://community.emc.com/docs/DOC-49148

https://support.emc.com/docu78316_ViPR-SRM-3.7.2-Administration-Guide.pdf

https://support.emc.com/docu78316_ViPR-SRM-3.7.2-Administration-Guide.pdf






Appendix A Open source license and copyright information

This appendix presents the following topics:

Software packages ................................................................................................ 73

GNU General Public License version 3 .................................................................... 74



Software packages

Native Hybrid Cloud uses GPLv3 licensed software. This appendix includes information related to the distribution of the GPLv3 licensed software. The license agreements for software packages included with Native Hybrid Cloud are listed in the table below.

Table 9. Native Hybrid Cloud software packages

Open source software title Version

libidn11 1.28

rsyslog 8.4.0

libksba8 1.3.0

diffutils 3.3

binutils 2.24

cloud-init 0.7.6

cpio 2.11

growpart 0.27

autoconf 2.69

bash 4.2

coreutils 8.22

cpp 4.8

cpp48 4.8.3+r212056

dirmngr 1.1.1

findutils 4.5.12

gawk 4.1.0

gcc 4.8

gcc-c++ 4.8

gcc48 4.8.3+r212056

gcc48-c++ 4.8.3+r212056

gpg2 2.0.24

grep 2.16

grub2 2.02~beta2

grub2-i386-pc 2.02~beta2

info 4.13a

libgdbm4 1.1



Open source software title Version

libparted0 3.1

libreadline6 6.2

m4 1.4.16

parted 3.1

rsync 3.1.0

sed 4.2.2

tar 1.27.1

gettext-runtime 0.19.2

libassuan0 2.1.1

libaugeas0 1.2.0

libgmp10 5.1.3

less 458

libatomic1 4.8.3+r212056

libgcc_s1 4.8.3+r212056

libgomp1 4.8.3+r212056

libstdc++48-devel 4.8.3+r212056

libstdc++6 4.8.3+r212056

ansible 1.9.2

libtasn1 3.7

libtasn1-6 3.7

GNU General Public License version 3

Version 3, 29 June 2007

Copyright© 2007 Free Software Foundation, Inc. <http://fsf.org/>

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

Preamble

The GNU General Public License is a free, copyleft license for software and other kinds of works.

The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a

http://fsf.org/



program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.

To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it.

For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions.

Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users.

Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free.

The precise terms and conditions for copying, distribution and modification follow.

TERMS AND CONDITIONS

0. Definitions. “This License” refers to version 3 of the GNU General Public License.



“Copyright” also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.

“The Program” refers to any copyrightable work licensed under this License. Each licensee is addressed as “you”. “Licensees” and “recipients” may be individuals or organizations.

To “modify” a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a “modified version” of the earlier work or a work “based on” the earlier work.

A “covered work” means either the unmodified Program or a work based on the Program.

To “propagate” a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.

To “convey” a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.

An interactive user interface displays “Appropriate Legal Notices” to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.

1. Source Code. The “source code” for a work means the preferred form of the work for making modifications to it. “Object code” means any non-source form of a work.

A “Standard Interface” means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.

The “System Libraries” of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A “Major Component”, in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.



The “Corresponding Source” for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.

The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.

The Corresponding Source for a work in source code form is that same work.

2. Basic Permissions. All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.

You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.

Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.

3. Protecting Users' Legal Rights From Anti-Circumvention Law. No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.

When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.



4. Conveying Verbatim Copies. You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.

You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.

5. Conveying Modified Source Versions. You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:

• a) The work must carry prominent notices stating that you modified it, and giving a relevant date.

• b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to “keep intact all notices”.

• c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.

• d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.

A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.

6. Conveying Non-Source Forms. You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:

• a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.

• b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support



for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.

• c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.

• d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.

• e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.

A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.

A “User Product” is either (1) a “consumer product”, which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, “normally used” refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.

“Installation Information” for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.

If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in



perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).

The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.

Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.

7. Additional Terms. “Additional permissions” are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.

When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.

Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:

• a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or

• b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or

• c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or

• d) Limiting the use for publicity purposes of names of licensors or authors of the material; or

• e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or



• f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.

All other non-permissive additional terms are considered “further restrictions” within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.

If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.

Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.

8. Termination. You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).

However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.

Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.

Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.

9. Acceptance Not Required for Having Copies. You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.



10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License.

An “entity transaction” is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.

You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.

11. Patents. A “contributor” is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's “contributor version”.

A contributor's “essential patent claims” are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, “control” includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.

Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.

In the following three paragraphs, a “patent license” is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To “grant” such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.

If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the



requirements of this License, to extend the patent license to downstream recipients. “Knowingly relying” means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.

If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.

A patent license is “discriminatory” if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.

Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.

12. No Surrender of Others' Freedom. If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.

13. Use with the GNU Affero General Public License. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such.

14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.



Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation.

If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.

Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.

15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each



file should have at least the “copyright” line and a pointer to where the full notice is found.

<one line to give the program's name and a brief idea of what it does.>

Copyright (C) <year> <name of author>

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>.

Also add information on how to contact you by electronic and paper mail.

If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:

<program> Copyright (C) <year> <name of author> This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an “about box”.

You should also get your employer (if you work as a programmer) or school, if any, to sign a “copyright disclaimer” for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, refer to <http://www.gnu.org/licenses/>.

The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. For more information, refer to <http://www.gnu.org/philosophy/why-not-lgpl.html>.

http://www.gnu.org/licenses/

http://www.gnu.org/philosophy/why-not-lgpl.html

native hybrid cloud, openstack edition with vxrack system ... · solution guide . native hybrid...

Documents