PureApplication Meet the Experts The New Virtual Pattern. Location: Raleigh, North Carolina Date: September 24-25, 2014 Speaker(s): Lin Sun

Transcription

1 PureApplication Meet the Experts The New Virtual Pattern Location: Raleigh, North Carolina Date: September 24-25, 2014 Speaker(s): Lin Sun

2 Agenda Overview Demo Pattern Customization Maintenance 2

3 Virtual Pattern Features Prior to 2.0 Virtual System Pattern Virtual Application Pattern Virtual Appliance HTTP Server Software application Metadata Metadata SLA policies Virtual Appliance Application Server Virtual Appliance Application Server Metadata Metadata OS Image vsys Pattern Engine Automated deployment of middleware topologies Traditional administration and management model Application and infrastructure driven elasticity Maestro Deployment Framework Highly automated deployments using expert patterns Business policy driven elasticity Built for the cloud environment Leverages elastic workload management services Customer Control Best TCO 3

4 Customize patterns to meet your IT standards with the new PureApplication Virtual Pattern Dev Topology Pattern SLA policies Software Application SLA policies QA Topology Pattern SLA policies Production Topology Pattern SLA policies CLIENT BENEFITS Support for corporate IT standards Flexible control over middleware topologies for virtual applications Lifecycle management for both topology and virtual application patterns Simplified tooling Existing patterns run unchanged Choice of OS Image IBM Pattern Deployment Framework VM recovery, middleware level resiliency, autoscaling, basic VM monitoring, logging 4

5 New! Virtual System New Contents Split HV Images into Base OS image + Software Packages Content providers build/deliver software packages (plugins) using PDK or web based tooling Software package = content binaries + automation scripts + metadata Content providers do not deliver HV images. 5 Binaries are optional (automation scripts may point to IM repository) Script-pkg and adds-on remain unchanged. Prior script-pkg and adds-on can be used with the new base OS + software package contents.

6 New! Virtual System New Contents (cont.) Customers define patterns using images, software packages, automation Script1 Pkg2 n.n.n.n Pkg1 n.n.n.n Image1 Script2 Script3 Pkg1 n.n.n.n Image1 Script4 Pkg4 n.n.n.n Pkg3 n.n.n.n Image2 Pattern deployment/management is done via Maestro deployment framework used for virtual applications Provides VM/middleware level resiliency, VM level monitoring, auto-scaling based on VM statistics, log collection etc. 6

7 New Virtual System Existing Contents Existing HV images, patterns, deployments in the field are supported. Existing HV images are represented as Image component in vsys.next pattern editor Existing script package and add-on are displayed as script package and add-on component in vsys.next pattern editor. Script package/add-ons remain unchanged for end users, same supported data format, same UI to load a script package/add-on. 7

8 New Virtual System Benefits Advantages to Pattern Creators / Deployers BYOS Bring your OS. Build your OS the way you want and use it in patterns Greatly reduce image sprawl. Common topologies built from with single (or few) OS image(s) and software packages - Parity between management capabilities of virtual systems and virtual applications Scaling, Routing, Maintenance, images/softare packages/scripts parallelism 8

9 Virtual Application Patterns New Additions Allow customers / content providers to define virtual application components and specify virtual system topology that they map to Scripts WAS Node WAS dmgr Scripts WAS Node Export as My WAR Virtual Application Component Inputs Outputs Virtual System Pattern Use pattern components to build patterns My WAR My DB Virtual Application Pattern 9

10 Define Pattern Component Connor Content Developer Connor tests his Trade software package plugin, build a golden pattern and pattern component, and export them out as a signle archive 10

11 New Virtual System Pattern Versioning Key architectural decisions New virtual system only Only elements that are not represented by a plugin Patterns, script packages, add-ons Upgrading existing VSP to VSP.next will allow assigning a version No semantics No assumed format No version management, e.g. History trail Rollback Reuse existing version attribute where possible cbscript.json pattern.json 11

12 IBM Software Pattern Inventory IBM API Management 2.0 IBM Application Pattern for Java 1.0 IBM Business Intelligence 1.0, 2.0 IBM Business Intelligence w/blu Acceleration 1.0 (AIX Only) IBM Business Process Manager 8.0.1, 8.5 (8.5 is vapp and vsys) IBM Connections 4.0 (Intel Only) IBM Content Foundation Pattern 5.2 (Intel Only) IBM Data Mart Pattern (with BLU Acceleration) IBM DB2 9.7 FP5, 10.1, 10.5 with BLU Acceleration IBM Transactional Database Pattern (DB2 vapp) IBM Domino 9.0 (Intel Only) IBM Encryption Pattern for Guardium Encryption Expert IBM Encryption Pattern for SecurityFirst SPxBitFiler IBM Informix 11.7, IBM InfoSphere Information Server 9.1 IBM InfoSphere Master Data Management Standard Edition and Advanced Edition, 11.0 (Intel Only) IBM InfoSphere Optim Performance Manager IBM Integration Bus 9.0 (evolution of Message Broker) IBM Maximo Asset Management 7.5 [prereq DB2 HV] IBM Messaging Extension for Web App Pattern 2.0 IBM Mobile Application Platform 5.0.6, IBM Operational Decision Manager 8.0.1, 8.5 (8.5 is vapp) [prereq DB2 HV] IBM Pattern for SAP Business Suite (Intel Only) IBM SOA Policy 2.0 (Intel Only) IBM SOA Policy Gateway 2.0, 2.5 IBM Software Delivery and LifeCycle Patterns (Intel Only) Collaborative Lifecycle Mgmt Rational Application Developer 8.5 Test Virtualization Server and Workbench IBM Sterling Order Management System IBM Transactional Database Pattern 1.1 (vapp) ITM Shared Service IBM Web Application Pattern 1.0, 2.0 (vapp) IBM Web Content Manager 8.0 IBM WebSphere App Server HV 7.0, 8.0, 8.5, IBM WebSphere Message Broker 8.0 IBM WebSphere Cast Iron 6.4, 7.0 (Intel Only) IBM WebSphere Commerce Pattern 1.0 (for WC Enterprise 7.0) [* prereq DB2 HV] IBM WebSpere Datapower XG45 V5.0, V6.0 (Intel Only) IBM WebSphere Datapower XI52 V5.0, V6.0 (Intel Only) IBM WebSphere MQ 7.5 IBM WebSphere Portal Server 8.0 IBM WebSphere Transformation Extender Launcher 8.4, Microsoft Dynamics v2008 for Intel Microsoft Exchange for Intel Microsoft Sharepoint V2010 for Intel Microsoft SQL Server V2012 for Intel Oracle DB Enterprise Edition v11g, R2 for Intel and AIX 12

13 PureApplication System On-premise & PureApplication on SoftLayer brings cloud economics & hybrid cloud together Private On-Premise Public Off-Premise Patterns: System Create Once Deploy Anywhere on Service Deploying AND managing software quickly and easily across Hybrid Cloud options with proven patterns of expertise 13

15 Demo 1 promotes a classic virtual system pattern 15

16 Demo 2 uses pattern builder to create a new virtual system pattern deploys the pattern 16

17 Demo 3 creates a new software component using PDK creates a pattern component. 17

19 Opportunities for Virtual System Customization 1. Within the Image (Extend/Capture) ABC s own Red Hat 6.5 OS tuning 2. Within the pattern 3. With script packages and parameters Select the component to configure the component attributes 4. Create your own software components 19

20 Best Practices for virtual system customization 1. Always check if there is images in the catalog or PureSystems centre, and explore Bring Your Own Image 2. Start with golden topology pattern if exists 3. Investigate the following customization opportunities: Images Within the pattern Script package Software components 20

21 1. Overview of BYOS Typical use cases Customers have their own company standard operating system specification and/or virtual image Customers want to use a different flavor of Linux distributions besides RHEL BYOS is a process for enabling user onboard their own OS image into PureApp, and transform that image by adding capabilities required for pattern based deployment 21

22 1. Supported OS Platforms in PureApp 2.0 Linux RHEL 6.5+ AIX 6.1/7.1 Windows (via ICCT) Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 22

23 1. How Does It Work PureApplication System Customer s Own OS Image PureApp Enablement Package 1 3 Virtual Appliance 2 Virtual Machine Instance Activation Engine Maestro Bootstrap Prereqs (ibm jdk, etc) New Virtual Image 4 42 U 41 U 40 U 39 U 38 U 37 U 36 U 35 U 34 U 33 U 32 U 31 U 30 U 29 U 28 U 27 U 26 U 25 U 24 U 23 U 22 U 21 U 20 U 19 U 18 U 17 U 16 U 15 U 14 U 13 U 12 U 11 U 10 U 9 U 8 U 7 U 6 U 5 U 4 U 3 U 2 U 1 U PureApp OS Image Metadata Template Provided by customer Provided by IBM 23

24 2. Customization within the pattern 24 The following points of customization are exposed: Middleware version number Scaling Policy Arbitrary script package execution Middleware configuration Script package configuration

25 2. Customization when deploying the pattern 25

26 3. Customization with Script Packages Scenarios: If you need a security agent or database driver or an application to be installed on some or all of the VMs, script package is recommended. Start with a new script package or clone an existing script package. Package your files for the script package into an archive that you can upload to the system. The archive must include the following items: The cbscript.json script definition file in the root directory (recommended). The executable file you created to execute the script Any other artifacts that are required for executing the script The optional extendedattribute.json in the root directory Use a meaningful script package name (recommended) Implement your script package to run on multiple platforms if desired The following archive formats are supported:.zip,.tgz, and.tar.gz. Each script package archive must be less than 2 GB. The script package name must be in ASCII characters. 26

27 3. Sample cbscript.json cbscript.json ensures same script sharing across different pattern engines [ { "name":"application Install", "version":"1.0.0", "description":"this script package installs the specified application", "command":"/bin/sh ${WAS_PROFILE_ROOT}/bin/wsadmin.sh", "log":"${was_profile_root}/logs/wsadmin.traceout", "location":"/opt/tmp/installapp", "timeout":"0", "commandargs":"-lang jython -f /opt/tmp/installapp/install_app.jy $APP_LOCATION $INSTALL_ARGS", "ostype":"linux/unix", "type":"application", "keys":[ { "scriptkey":"app_location", "scriptvalue":"", "scriptdefaultvalue":"" }, { "scriptkey":"install_args", "scriptvalue":"", "scriptdefaultvalue":"" } ] } ] cbscript.json 27

28 3. Sample extendedattribute.json Extendedattribute.json defines additional attributes to extend the script package configuration. Envonly: Specifies whether script package parameter values are set only in the environment, or if they are also written to the virtualimage.properties file before the script package is run. Savevars: Specifies whether changes made to script package parameter values are persisted after deployment, and reapplied to subsequent runs of the script package. [ ] { } "envonly":"true", "savevars":"1", "product_license":{ "productid":"5725a26", "licensetype":"server", "licensecpu":"16", "licensememory":"4" } extendedattribute.json 28

29 3. Sample Script package in the catalog cbscript.json 29

30 3. Sample Script package in the builder Script package parameters allow further customization. Drag and drop script package on the desired VM to customize. cbscript.json 30

31 4. Creating software packages Connor Content developer (Acme) Develops contents for patterns Understands the product technically Has scripting skills Limited Java development skills Scenario: Connor creates contents for software package using PDK No need to worry about base OS Delivery supports multiple OS Easily reuse software Quickly reiterate the dev-test cycle WebSphere Images AIX Image RHEL Image zlinux Image was.tgz fetch binaries IM Repo One set of images for each fix-pack: 10+ images 31 Support for V7, V8, and V8.5

33 ifix and FixPack in App Builder Global ifix Policy Select service level, e.g. FixPack Local VM ifix Policy 33 List ifix list from WCA and IMRepo 33

34 Import ifix and FixPack topology.json ifix FixPack import from Emergency fix Catalog or IM Repository import as package defined in plugin Import from IMRepo Middleware install from IM 34 FixPack defined in config.json 34

35 IM repo configuration Client can configure internal built-in IM repo by adding/removing IM pkgs Client can add external IM repos Fixes in IM repo will be supported similarly as emergency fixes catalog, except the fixes will be fetched from one or more IM repo Fixes Or relationship here

36 Maintenance Role in Operation UI 1. In the grid, it will list all the existing installed ifixes/fixpack, and user can apply more fixes. 2. The installed ifixes/fixpack will not be removed, the new fixes planned to installed could be removed before submission 3. The user can apply more fixes to the deployment. after selection, it will show the target VM template which will be applied 36 36

37 Support Create SnapShot and Restore for Maintenance Operation 37 37

38 Ordering Control for ifixes/fixpack installation If one fixpack applied to more than one vm-template, framework will guarantee the installation order. e.g. install one fix pack on WAS, it will apply to DMGR firstly, then install on Custom Node This ordering control is applied to ifixes too 38 38

39 OS Patch Management solutions IBM Endpoint Manager (IEM) Integration Windows guests AIX guests TEM Pattern type includes IEM Relay Shared service, client plugins Red Hat OS Update Red Hat Satellite Server Integration Red Hat Update Infrastructure (RHUI) deprecated in v2.0 release RHUS Pattern type covers RH Satellite Server, RHUI shared services, client plugins A Pattern type to install RH Satellite Server Pattern types support vsys.classic, vsys.next, vapps Does not support virtual appliances 39 June 3, 2014

40 BACKUP 40