this solution guide provides an introduction to release ... · artifactory deployed as an ... the...

This Solution Guide provides an introduction to release automation and

continuous delivery to enable frequent, reliable software releases into the

Federation Enterprise Hybrid Cloud solution.

February 2016

2

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

Published February 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, Avamar, Data Domain, Data Protection Advisor, Enginuity, GeoSynchrony,

Hybrid Cloud, PowerPath/VE, RecoverPoint, SMI-S Provider, Solutions Enabler, VMAX,

Syncplicity, Unisphere, ViPR, EMC ViPR Storage Resource Management, Virtual Storage

Integrator, VNX, VPLEX, VPLEX, Geo, VPLEX Metro, 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.

Federation Enterprise Hybrid Cloud 3.5: VMware vRealize Code Stream Guide Solution Guide

Part Number H14826

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

Contents

3

Chapter 1 Executive Summary ............................................................. 5

Federation solutions ............................................................................................ 6

Document purpose .............................................................................................. 6

Audience ............................................................................................................ 6

Solution purpose ................................................................................................. 6

Business challenge .............................................................................................. 7

Technology solution............................................................................................. 7

Essential reading ................................................................................................ 7

We value your feedback! ...................................................................................... 8

Chapter 2 vRealize Code Stream Deployment ......................................... 9

Introduction ...................................................................................................... 10

Supported versions ........................................................................................ 10

Scope .......................................................................................................... 10

Important notes ............................................................................................ 10

System architecture ........................................................................................... 11

vRealize Automation and vRealize Code Stream compatibility .............................. 11

Deployment in Federation Enterprise Hybrid Cloud ................................................. 11

Deployment topology ..................................................................................... 11

Artifactory deployed as an external entity ......................................................... 13

vRealize Code Stream component locations ...................................................... 14

Sizing considerations for vRealize Code Stream ................................................. 15

Sizing considerations for an external Artifactory server ...................................... 16

Performance parameter tuning details .............................................................. 16

Chapter 3 Release Automation ........................................................... 18

Release automation ............................................................................................ 19

Overview ...................................................................................................... 19

Software development lifecycle ....................................................................... 19

Release pipelines ........................................................................................... 19

Release Dashboard ........................................................................................ 20

Roles ........................................................................................................... 21

Chapter 4 Integration ........................................................................ 22

Overview .......................................................................................................... 23

List of plug-ins ................................................................................................... 23

Chapter 5 Management Packs ............................................................ 24

vRealize Code Stream Management Pack .............................................................. 25

Introduction .................................................................................................. 25

Components ................................................................................................. 25

IT DevOps .................................................................................................... 26

Contents

4

Chapter 6 Conclusion ........................................................................ 27

Summary .......................................................................................................... 28

Findings ............................................................................................................ 28

Chapter 7 References ........................................................................ 29

Federation documentation ................................................................................... 30

Other documentation .......................................................................................... 30

Chapter 1: Executive Summary

5

This chapter presents the following topics:

Federation solutions ............................................................................................ 6

Document purpose .............................................................................................. 6

Audience ............................................................................................................ 6

Solution purpose ................................................................................................. 6

Business challenge .............................................................................................. 7

Technology solution............................................................................................. 7

Essential reading ................................................................................................ 7

We value your feedback! ...................................................................................... 8


6

EMC II, Pivotal, RSA, VCE, Virtustream, and VMware form a unique Federation of

strategically aligned businesses that are free to run individually or together. The EMC

Federation businesses collaborate to research, develop, and validate superior, integrated

solutions and deliver a seamless experience to their collective customers. The Federation

provides customer solutions and choice for the software-defined enterprise and the

emerging third platform of mobile, cloud, Big Data, and social networking.

The Federation Enterprise Hybrid Cloud 3.5 solution is a completely virtualized data center,

fully automated by software. The solution delivers IT as a service (ITaaS), with options for

high availability, backup and recovery, and disaster recovery. It also provides a framework

and foundation for add-on module such as application services, database as a service,

platform as a service, cloud brokering, and continuous delivery for rapid application

deployment.

This Solution Guide serves as a reference for planning and designing a continuous delivery

solution with VMware vRealize® Code Stream™ and third-party continuous integration (CI)

tools within the Federation Enterprise Hybrid Cloud solution.

This Solution Guide is intended for anyone who plans to deploy this solution and configure

the environment to automate the release of applications in various development

environments. The information is written for experienced developers and operation teams

who are familiar with release automation and with the Federation Enterprise Hybrid Cloud.

Readers should also be familiar with the infrastructure and security policies of the customer

installation.

The Federation Enterprise Hybrid Cloud solution enables Federation customers to build an

enterprise-class, scalable, multitenant infrastructure that will accelerates application

releases for business agility. It extends the agility provided by continuous integration into

continuous delivery to enable frequent, reliable software releases, while reducing operational

risks. It integrates out-of-the-box with continuous integration tools through Jfrog

Artifactory, delivers visibility across releases and provides a framework for application

provisioning. Key capabilities include:

Complete management of the infrastructure and application service lifecycle

On-demand access to and control of network bandwidth, servers, storage, and security

Automation and governance of the entire release process

A dashboard for end-to-end visibility of the release process across Dev and Ops

organizations

Artifact management and tracking

This solution provides the reference architecture and the best practice guidance necessary

to integrate the key components and functionality of enterprise continuous delivery into an

underlying Federation Enterprise Hybrid Cloud infrastructure.


7

Today’s enterprise demands an agile development platform that can enable the continuous

delivery, updating, and horizontal scalability of applications. Applications are the engine that

enables the business to deliver services and capture new market opportunities. Increasing

demand for new and updated applications means shorter release cycles and higher risk. In

response, the enterprise must accelerate the entire IT service lifecycle and associated

ecosystem components; not only infrastructure services, but also application deployment

and the downstream release processes. This requires a fundamental change in application

authoring and automated delivery. Current processes require IT to author individual

machines and configure them together as working applications with all dependencies, micro-

services, networking, storage, and security. At most companies this still takes multiple

weeks or months, even those that are heavily leveraging virtualization and associated

management tools.

While an infrastructure as a service (IaaS) strategy is critical for delivering infrastructure, it

only solves a fraction of your business agility problem:

Manual configurations that lead to inconsistencies and errors, resulting in additional

rework, not to mention across environments (dev/test/production/private/public

cloud), where the deployment process must be repeated.

Changes to databases, middleware, and application components, which can further

compound the risk of human errors.

Traditional operating models that include coordination between multiple teams,

including the hand-off of tasks, which consumes “time.” As the organization grows,

you must simultaneously process an explosive growth of requests, which can escalate

quickly.

This Federation Enterprise Hybrid Cloud solution integrates the best of EMC and VMware

products and services. It empowers IT organizations to accelerate the implementation and

adoption of a hybrid cloud infrastructure while still enabling customer choice for the compute

and networking infrastructure within the data center.

The key solution components include:

EMC Avamar® and/or EMC Data Domain® backup and recovery solutions

EMC and VMware integrated workflows

VMware vCloud Suite®

VMware vRealize Code Stream

VMware NSX® software-defined networking

VMware vSphere® virtualization platform

The vRealize Code Stream solution is a modular add-on to the Federation Enterprise Hybrid

Cloud solution. The following documents describe the architecture, features, and

functionality:

Federation Enterprise Hybrid Cloud 3.5: Reference Architecture Guide

Federation Enterprise Hybrid Cloud 3.5: Concepts and Architecture Guide

Federation Enterprise Hybrid Cloud 3.5: Administration Guide

Federation Enterprise Hybrid Cloud 3.5: Infrastructure and Operations Guide


8

The following guides provide further information about various aspects of the Federation

Enterprise Hybrid Cloud solution:

Federation Enterprise Hybrid Cloud 3.5: VMware Integrated OpenStack (VIO) on FEHC

Solution Guide

Federation Enterprise Hybrid Cloud 3.5: Security Management Guide

The following guide also provides guidance on deploying business-critical applications on the

Federation Enterprise Hybrid Cloud solution:

Federation Enterprise Hybrid Cloud 3.5: Microsoft Applications Foundation Solution

Guide

EMC and the authors of this document welcome your feedback on the solution and the

solution documentation. Contact [email protected] with your comments.

Authors: Bruce George, Fiona O’Neill

mailto:[email protected]?subject=Feedback:%20Solution%20Guide%20(H14825)

Chapter 2: vRealize Code Stream Deployment

9


Introduction ...................................................................................................... 10

System architecture ........................................................................................... 11

Deployment in Federation Enterprise Hybrid Cloud ................................................. 11


10

This section describes the recommended deployment topology for vRealize Code Stream.

vRealize Code Stream can use blueprints in a vRealize Automation™ catalog for virtual

machine provisioning.

Currently, vRealize Code Stream does not support connecting to an external vRealize

Orchestrator instance and does not support its own distributed setup (these capabilities are

planned for the first half of 2016), but it can integrate with an external distributed vRealize

Automation, such as Federation Enterprise Hybrid Cloud, and use it for virtual machine

provisioning as well as other Federation Enterprise Hybrid Cloud services, such as data

protection, disaster recovery, encryption, and so on. vRealize Code Stream has a separate

pipeline catalog for developers provided by a dedicated user portal distinct from the

Federation Enterprise Hybrid Cloud primary catalog, as shown in Figure 1.

Figure 1. vRealize Code Stream and Federation Enterprise Hybrid Cloud portals

The deployment recommendation in this section is valid for vRealize Code Stream 1.2 only.

The following scenarios are described in the document:

vRealize Code Stream and vRealize Automation as two separate instances where

vRealize Automation is a distributed environment.

Artifactory deployed as an external entity

The following scenarios are out of the scope for this document:

vRealize Code Stream integrating directly with external vRealize Orchestrator™

instance (this is planned for a future release)

vRealize Code Stream in distributed configuration (this is planned for a future release)

During configuration of the vRealize Code Stream deployment, you should be aware of the

following:

When using an external distributed deployment of vRealize Automation, vRealize Code

Stream should use a shared user account to access vRealize Automation. Configure

the vRealize Automation endpoint using a shared account and not a per user session.

Refer to the vRealize Code Stream endpoint configuration document for more

information.

vRealize Code Stream 1.2 integrates with Advanced Service Designer (ASD) forms. A

new ASD plug-in is shipped with vRealize Code Stream 1.2. This plug-in works only

with the internal vRealize Automation 6.2.3 instance supplied within the vRealize Code

Stream appliance itself. The ASD plug-in does not work directly with an external

vRealize Automation instance, such as the distributed vRealize Automation used by

Federation Enterprise Hybrid Cloud. Instead, the vRealize Code Stream pipeline

Supported

versions

Scope

Important notes


11

catalog may use blueprints from the Federation Enterprise Hybrid Cloud catalog to

deploy virtual machines as required.

Figure 2 shows the vRealize Code Stream architecture, including its components.

Figure 2. vRealize Code Stream architecture

Table 1 shows the versions of vRealize Code Stream that are compatible with an external

vRealize Automation instance. Only vSphere single machine blueprints are supported in the

vRealize Automation provisioning task.

vRealize Automation and vRealize Code Stream compatibility Table 1.

vRealize Code Stream

version

vRealize Automation

1.2 6.2.1, 6.2.2, 6.2.3

Note: Only vRealize Code Stream 1.2 may be used to connect to Federation Enterprise Hybrid

Cloud. Older versions of vRealize Code Stream do not support the version of vRealize

Automation used by Federation Enterprise Hybrid Cloud 3.5 (vRealize Automation 6.2.3).

vRealize Code Stream can integrate with an existing distributed vRealize Automation

deployment for virtual machine provisioning. When using the Federation Enterprise Hybrid

Cloud for virtual machine blueprint deployment, an endpoint needs to be created in vRealize

Code Stream where external vRealize Automation endpoint-related details can be specified.

The load balancer configured for the Federation Enterprise Hybrid Cloud vRealize Automation

instance should be used as the external endpoint in vRealize Code Stream. This endpoint is

listed under the provisioning category while adding a task to a stage. Refer to Registering

Components section of the Installation and Configuration: vRealize Code Stream 1.2

document for more information on vRealize Automation Server endpoint configuration.

Figure 3 depicts the logical configuration when vRealize Code Stream is integrated with

Federation Enterprise Hybrid Cloud.

vRealize

Automation

and vRealize

Code Stream

compatibility

Deployment

topology


12

Figure 3. vRealize Code Stream with Federation Enterprise Hybrid Cloud distributed vRealize Automation

Users require access to the ports, as shown in Table 2.

Server ports for users Table 2.

Server role Port

vRealize Code Stream 443

vRealize Automation appliance 443

EHC Platform Services Controller (PSC) 7444

Administrators require access to the ports shown in Table 3 and Table 4, in addition to those ports

required by users.

Server ports for administrators Table 3.

Server role Port


vRealize Automation Appliance 5480

Inbound and outbound ports Table 4.

Server role Inbound ports Service/system outbound ports


SSH: 22

VAMI: 5480

EHC PSC: 7444

vRA VA: 443

vRealize Automation appliance 443

SSH: 22

VAMI: 5480

5432 ,

5672

EHC PSC: 7444

This is a communication requirement between clustered vRealize Appliances. Refer to the vRealize Automation deployment guide for more details.


13

The vRealize Code Stream appliance includes an embedded Artifactory server, which can be

accessed using the server URL format https://vrcs-<hostname>/artifactory/.

If an organization already has an Artifactory server available then vRealize Code Stream can

be configured to use it transparently. The existing Artifactory repositories can be used as

remote repositories in the embedded vRealize Code Stream Artifactory, as shown in

Figure 4.

Figure 4. vRealize Code Stream using an external Artifactory server

A vRealize Code Stream Appliance can also be used as a standalone Artifactory server. Refer

to the section Install Artifactory on a Separate Artifactory Server in the Installation and

Configuration vRealize Code Stream Guide for details on how to configure remote

repositories. Table 5 details the network ports required for communication between the

Artifactory server and the vRealize Code Stream appliance.

Inbound and outbound ports Table 5.

Server role Inbound ports Service/system outbound ports

Artifactory server 443

vRealize Code Stream appliance 443

SSH: 22

VAMI: 5480

EHC PSC: 7444

Artifactory server: 443

Artifactory

deployed as an

external entity


14

The Automation Pod hosts the virtual machines used for automating and monitoring the

hybrid cloud infrastructure. When used with vRealize Code Stream, this pod should also be

used to host the vRealize Code Stream appliance and the external Artifactory server if used,

as shown in Figure 5. Additional third-party components, such as Jenkins, should also be

placed in the Automation Pod.

Figure 5. Cloud management platform component layout

Note: Currently the Federation Enterprise Hybrid Cloud sizing tool does not include sizing for

the vRealize Code Stream appliance, the external Artifactory server or additional third-party

continuous delivery tools. These requirements and the requirements of any other third party

components should be added on to the sizing tool output to ensure the Automation Pod is

adequately sized. Refer to Table 6 and Table 7 for details on vRealize Code Stream and

Artifactory sizing.

vRealize Code

Stream

component

locations


15

The compute resources required to support different types of vRealize Code Stream

configurations are described in Table 6.

Compute resource requirements for the vRealize Code Stream Appliance Table 6.

Configuration type

Object size Host CPU and memory

Tuning parameters Distribution types/concurrent executions

Medium *Executed pipelines: 50,000

**No of pipelines: 200

Artifact count: 600

6 vCPU

32 GB RAM

JVM memory for vRealize Automation instance 8 GB

JVM memory for vRealize Orchestrator instance 14 GB

vRealize Automation application database pool: 100

connectionTimeout for vRealize Automation

instance: 90 sec

connectionTimeout for vRealize Orchestrator instance: 40 sec

vRealize Orchestrator application thread pool size: 300

postgres max_connections: 200

**100

Large *Executed pipelines:

90,000

**No of pipelines: 200

Artifact count: 600

8 vCPU

64 GB RAM

JVM memory for

vRealize Automation instance 16 GB

JVM memory for vRealize Orchestrator instance 20 GB

vRealize Automation application database pool: 200

vRealize Automation Application thread pool: 600

connectionTimeout for vRealize Orchestrator instance: 40 sec

vRealize Orchestrator application thread pool size: 300

postgres max_connections: 250

**125

Note * The number of pipelines executed continuously without bringing the server down.

Note ** Different pipelines executed, 100 times each.

Sizing

considerations

for vRealize Code

Stream


16

Additional sizing considerations when deploying a single server external Artifactory are

shown in Table 7.

Compute resource requirements for an external Artifactory server Table 7.

Number of Developers

Processors *Memory (RAM) for JVM Heap

1-20 4 4 GB

20-100 4 8 GB

100-200+ 8 (16 recommended) 12GB

*Memory (RAM) for JVM Heap, This specifies the amount of memory that Artifactory requires

from the JVM heap. The server machine should have enough additional memory to run the

operating system and any other processes running on the machine

You can adjust the available vRealize Application Services server memory, number of thread

connections, and number of database connections based on the requirements of the

environment in question.

Details of the configuration files that can be edited to achieve the required goal are

described in this section.

Heap memory

vcac server

Navigate to /etc/vcac/setenv-server.sh.

For example, to increase the maximum heap size to 8 GB, change the Xmx value to 8192m

in the configuration setup file:

JVM_OPTS="-Xms3584m -Xmx8192m -Xmn1152m -XX:PermSize=512m -

XX:MaxPermSize=1024m -Xss256k"

vco server

Navigate to /var/lib/vco/app-server/bin/setenv.sh.

For example, to increase the max heap size to 20 GB, change the Xmx value to 20480m in

the configuration setup file:

MEM_OPTS="-Xms2560m -Xmx20480m -Xmn864m -XX:PermSize=256m -XX:MaxPermSize=512m

-Xss256k"

Database connections

vcac application db pool

Database connection settings can be edited in the /etc/vcac/server.xml file.

For example, to increase the database connection pool size to 100, change the maxActive

value to 100.

Below is the file snippet of the change:

<Resource name="jdbc/cafe" auth="Container" type="javax.sql.DataSource"

factory="org.apache.tomcat.jdbc.pool.DataSourceFactory"

driverClassName="org.postgresql.Driver"

url="jdbc:postgresql://127.0.0.1:5432/vcac" username="vcac" password="vcac"

validationQuery="select 1" validationInterval="30000" initialSize="10"

maxActive="100" maxWait="120000"

Sizing

considerations

for an external

Artifactory server

Performance

parameter tuning

details


17

To change the connection timeout to 90 seconds change the value of connectionTimeout

to"90000" (in ms).


<Connector address="127.0.0.1" port="8080" acceptCount="100"

protocol="HTTP/1.1" connectionTimeout="90000" packetSize="65000"

redirectPort="8443"/>

vco application db pool

Database connection settings can be edited in the /etc/vco/app-server/server.xml file.

To change the connection timeout to 90 seconds change the value of connectionTimeout

to"90000" (in ms).


<Connector port="${ch.dunes.http-server.port}"

address="${server.bind.address}" protocol="HTTP/1.1" URIEncoding="UTF-8"

connectionTimeout="90000" redirectPort="${ch.dunes.https-server.port}"

maxHttpHeaderSize="163840"/>

Postgres database connections

Postgres database configuration can be edited in the

/storage/db/pgdata/postgresql.conf file.

For example, to increase connection size to 100, change the value of geqo_pool_size to

100.

Thread pool

vco application thread pool

Thread pool size can be edited in the /etc/vco/app-server/server.xml file.

For example, to increase the application thread pool size to 300, change maxThreads =

"300" property within the Connector tag.

Note: To make the configuration changes effective restart the respective services.

Below are the commands to stop, start, and restart the vco and vcac services:

service vco-server <stop/start /restart>

service vcac-server restart <stop/start /restart>

Heap memory size can be configured based on the expected load. The maximum heap size

of an application server should be at least half of the total memory. The rest of the memory

should be left for the Postgres, RabbitMQ, and other system processes.

Note: The Federation recommends not changing the -XX:MaxPermSize value unless you are

troubleshooting permgen errors.

Chapter 3: Release Automation

18


Release automation ............................................................................................ 19


19

vRealize Code Stream is a powerful automation tool designed to enable DevOps teams to

streamline tasks in the software release process. It uses the extensive set of Jfrog

Artifactory plug-ins for popular continuous integration (CI) tools such as source control,

build, integration, and test.

The software development lifecycle (SDLC) contains various stages and actors. Developers

commit code to a source code management system such as Git, Apache Subversion (svn),

or Perforce. The code changes are built using a CI tool such as Jenkins or Microsoft TFS. As

part of the CI process, various tests are run through tools such as Selenium or Jmeter. If

the build process completes successfully, then the result is that one or more artifacts are

copied into a repository. Some of the popular repositories are Artifactory, yum, and Nexus.

Periodically, these artifacts are bundled together into a release and deployed onto servers,

for example Tomcat or Database. There are various provision and deployment tools

available to stand up the application stack. vRealize Automation, Docker, Puppet, and Chef

are some of the common ones.

As shown in Figure 6, any of several tools could be used at various steps in the SDLC. In

addition, different teams or different locations often use tools they are most comfortable

with. As open source tools increase in popularity, new ones replace the existing tools.

Therefore, any solution for continuous delivery must be able to integrate with the SDLC

toolset and consume data.

Figure 6. Software development lifecycle tools

You can model simple and complex release pipelines by specifying the configuration and

various tasks such as provision, deploy, and test in each stage, as shown in Figure 7. Gating

rules are a set of criteria that each stage must pass to continue to the subsequent stage.

You can configure gating rules based on your requirement for a pipeline.

Overview

Software

development

lifecycle

Release pipelines


20

Figure 7. Software development lifecycle tasks

The vRealize Code Stream Release Dashboard, as shown in Figure 8, provides end-to-end

visibility to the DevOps team showing the state of each release pipeline and which artifact

versions are deployed at any stage. As a Release Dashboard user you can view artifacts,

machines, and pipelines, and track the cross dependencies between these resource types to

help troubleshoot when deployments fail or exceed the expected deployment time threshold.

Figure 8. vRealize Code Stream Release Dashboard

Release

Dashboard


21

There are three primary roles included in the vRealize Code Stream application. These roles

can be configured by selecting Administration > Users & Groups > Identity Store

Users & Groups.

vRealize Code Stream roles Table 8.

Roles name Authorities

Release Dashboard User View Release Dashboard

Release Engineer Execute Release Pipeline

View Release Dashboard

View Release Pipeline Details


Release Manager View Release Dashboard

Execute Release Pipeline



Delete Release Pipeline

Update Release Pipeline

Create Release Pipeline

Advanced services configurations

Roles

Chapter 4: Integration

22


Overview .......................................................................................................... 23

List of plug-ins ................................................................................................... 23

Chapter 4: Integration

23

vRealize Code Stream provides a framework to use industry standard tools for provisioning

application environments. It integrates with vRealize Automation, the infrastructure

automation and provisioning tool for VMware customers. In addition, it provides out-of-the-

box integration with other tools such as Puppet, Chef, and SaltStack. This integration is

provided through vRealize Orchestrator plug-ins.

Plug-ins for vRealize Code Stream are listed in Table 9.

vRealize Code Stream plug-ins Table 9.

Build and continuous integration

Jenkins Available today

Microsoft TFS Available today

Artifact and source control repository

JFrog Artifactory JFrog Artifactory

Sonatype Nexus Sonatype Nexus

Yum Yum

Testing frameworks

JMeter JMeter

JUnit JUnit

Selenium Selenium

SoapUI SoapUI

Provisioning and configuration

Amazon EC2 Available today

Chef Available today

Puppet Available today

Scripts (BASH & PowerShell) Available today

vRealize Automation, vCenter, and vCloud Director Available today

Other applications

Atlassian JIRA Atlassian JIRA

BMC Remedy ITSM BMC Remedy ITSM

HP Service Manager HP Service Manager

ServiceNow ServiceNow

Chapter 5: Management Packs

24


vRealize Code Stream Management Pack .............................................................. 25


25

vRealize Code Stream Management Pack for IT DevOps is an extensible framework that

automates the management of software-defined content such as workflows, blueprints, or

templates. This management pack makes it possible to avoid the time-consuming and error-

prone manual processes currently required to manage software-defined content.

This solution is based on the VMware concept of the software-defined data center (SDDC).

The SDDC abstracts every service in the data center from its underlying hardware and

redefines these services as software. By treating software-defined content as code, you can

apply current software development methodologies such as agile or DevOps to the

configurations and content within the SDDC.

The management pack uses vRealize Code Stream to facilitate "DevOps for Infrastructure."

The management pack is intended for organizations that have an enterprise deployment of

vRealize Automation, which includes multiple environments such as development, testing,

staging, and FEHC Production, as shown in Figure 9. The management pack provides an

alternative to the time-intensive manual processes currently used to move content and

configurations from one environment to another.

Figure 9. vRealize Code Stream for multiple environments

vRealize Code Stream Management Pack for IT DevOps is supplied as a vRealize

Orchestrator package. The release must be installed on a vRealize Automation standalone

deployment with the following components on a single host machine:

vRealize Automation

vRealize Orchestrator

vRealize Code Stream

JFrog Artifactory

These components are pre-installed on the vRealize Automation 6.2.3 appliance.

The management pack requires an additional component, the Content Transfer Server

(CTS). For this release, the CTS are hosted on a separate, modified vRealize appliance that

has all non-essential services disabled. The CTS exports and imports software-defined

content in the form of binary files between external systems and the JFrog Artifactory

artifact repository.

Introduction

Components


26

The vRealize Code Stream Management Pack for IT DevOps enables you to provide

continuous integration (CI) and delivery of software-defined content for the content package

types listed in Table 10.

Content package types Table 10.

Content package type Description

ASD-Action Captures a vRealize Automation Advanced Service Designer resource action.

ASD-Blueprint Captures a vRealize Automation Advanced Service Designer

service blueprint.

IAAS-Blueprint (vSphere endpoints only) Captures a vRealize Automation

infrastructure blueprint as well as referenced global profiles.

Linux-Files Captures files from Linux operating systems.

Orchestrator-Package Captures a vRealize Orchestrator package containing software files and related information.

Orchestrator-Workflow Captures a vRealize Orchestrator workflow containing system tasks and dependent actions.

Orchestrator-Action Captures a vRealize Orchestrator Advanced Service Designer resource action.

Orchestrator-Configuration Element

Captures a vRealize Orchestrator Advanced Service Designer configuration element

IT DevOps

Chapter 6: Conclusion

27


Summary .......................................................................................................... 28

Findings ............................................................................................................ 28

Chapter 6: Conclusion

28

Federation Enterprise Hybrid Cloud enables customers to build an enterprise-class, scalable,

multitenant platform for complete infrastructure service lifecycle management.

The solution uses the best of EMC and VMware products and services to deliver on the

following principles:

Self-service and automation

Multitenancy and secure separation

Workload-optimized storage

Security and compliance

Monitoring and service assurance

vRealize Code Stream is an application release automation solution that empowers

development and operations teams to become more efficient and effective at releasing

software. vRealize Code Stream:

Automates the different tasks needed to provision, deploy, test, monitor, and

decommission the software targeted for a specific release.

Assures standardized configurations, by coordinating the artifacts and process across

each release delivery stage.

Provides governance and control across the end-to-end process ensuring process

consistency at each phase in the delivery pipeline.

Leverages existing tools and processes to minimize disruption and leverage prior

investments.

Provides reporting and release dashboards that allow all groups to monitor the status

and foster greater collaboration between teams.

Chapter 7: References

29


Federation documentation ................................................................................... 30

Other documentation .......................................................................................... 30

Chapter 7: References

30

The following documents provide additional and relevant information:

Federation Enterprise Hybrid Cloud Solution documentation (refer to Essential reading)

EMC ViPR documentation

EMC VNX and VMAX documentation

EMC Unisphere and Enginuity documentation

EMC Solutions Enabler and EMC SMI-S Provider documentation

EMC PowerPath/VE documentation

EMC Avamar documentation

EMC Data Domain documentation

VMware vRealize Automation documentation

VMware vRealize Operations Manager documentation

VMware vRealize Application Services documentation

VMware vRealize Code Stream documentation

VMware vRealize Code Stream Management Pack for IT DevOps

Refer to the following document: Continuous Delivery: Reliable Software Releases Through

Build, Test, and Deployment Automation by Jez Humble and David Farley.

this solution guide provides an introduction to release ... · artifactory deployed as an ... the...

Documents