Orchestrate JBoss Middleware with Ansible Tower Red Hat Summit San Francisco

Transcription

1 Orchestrate JBoss Middleware with Ansible Tower Red Hat Summit San Francisco Marc Zottner Architect, Red Hat mzottner@redhat.com 29/06/2016 Roeland van de Pol Architect, Red Hat rvandepol@redhat.com

2 Agenda Middleware Orchestration Instruments Performance Image source:

3 MIDDLEWARE ORCHESTRATION

4 Our typical talk with an old school sysadmin... Can you please install a server for me? Today? Please?

5 Our typical talk with an old school sysadmin... Really? A week to install my server? Imagine scaling up for your marketing campaign going viral...

6 Our typical talk with an old school sysadmin... Really? Are you sure you installed this server in the same way as the other server? Imagine how your cluster would behave with different configuration on each node...

7 Our typical talk with an old school sysadmin... Really? What do you mean with reinstall the server? You can you just re-run your installation script, can t you? Imagine rolling back a change that went wrong...

8 Our typical talk with an old school sysadmin... Really? You used that old version of our installation document? Didn t you get the update? Imagine explaining to your CSO you missed a few critical security fixes that were introduced later...

9 Here is the holy grail. Image source: & &

10 Here is the holy grail. One Button Simple and powerful. Image source: & &

11 Here is the holy grail. One Button Some Orchestration Simple and powerful. Our conductor is a robot. We sometimes call it magic. Image source: & &

12 Here is the holy grail. One Button Some Orchestration The Perfect IT Landscape Simple and powerful. Our conductor is a robot. Everything is just as it should be. We sometimes call it magic. Image source: & &

13 Benefits Lower time to market Roll out your changes quicker Smooth end user experience Happy internal customers Less Risk Deterministic, so testable Self Service Have users do your work for you!

14 Vocabulary Topology Representation of the arrangement and grouping of computer systems.

15 Vocabulary Topology Representation of the arrangement and grouping of computer systems. Middleware platform Server runtime environment for web, Java or Java EE applications.

16 Vocabulary Topology Representation of the arrangement and grouping of computer systems. Middleware platform Server runtime environment for web, Java or Java EE applications. Golden image Customized corporate version of a vanilla middleware platform.

17 Vocabulary Topology Representation of the arrangement and grouping of computer systems. Middleware platform Server runtime environment for web, Java or Java EE applications. Golden image Customized corporate version of a vanilla middleware platform. Standard Operating Environment (SOE) How we used to name the holy grail before...

18 Obstacles to find the holy grail Image source: &

19 Obstacles to find the holy grail Over-engineered, monolithic, complex. Image source: &

20 Obstacles to find the holy grail Over-engineered, monolithic, complex. One tool to rule them all. Image source: &

21 Obstacles to find the holy grail (cont d) Swivel chair interface. Image source: &

22 Obstacles to find the holy grail (cont d) Swivel chair interface. Keeping your whole system topology in an Excel sheet or a wiki page. Image source: &

23 The core goals Simple

24 The core goals Simple Determinist Same input Same output

25 The core goals Simple Determinist Same input Same output Idempotent Execute as often as you want.

26 The core goals Simple Determinist Same input Same output Idempotent Execute as often as you want. As-Code Fully versioned and reproducible. No manual step.

27 Our inventory of repositories

28 Our inventory of repositories Java deployments = Java binary + Configuration

29 Our inventory of repositories Java deployments = Java binary Middleware platform binaries RH 1.0 Red Hat installation binaries Corporate middleware golden images + Configuration GI 1.0

30 Our inventory of repositories Java deployments = Java binary Middleware platform binaries RH 1.0 Red Hat installation binaries Corporate middleware golden images + Configuration GI 1.0 Infrastructure topology and environment Topology and mapping information (hosts, instances, deployments, platforms) Environment specific variables and secrets

31 Our inventory of repositories Java deployments = Java binary Middleware platform binaries RH 1.0 Red Hat installation binaries Corporate middleware golden images + Configuration GI 1.0 Infrastructure topology and environment Topology and mapping information (hosts, instances, deployments, platforms) Environment specific variables and secrets Identity Access Management ( User + Groups + Roles + Rights )

32 Our inventory of repositories Java deployments = Java binary Middleware platform binaries RH 1.0 Red Hat installation binaries Corporate middleware golden images + Configuration GI 1.0 Infrastructure topology and environment Topology and mapping information (hosts, instances, deployments, platforms) Environment specific variables and secrets Identity Access Management Automation code (Glue) ( User + Groups + Roles + Rights )

33 Orchestration processes Build the golden images Roll-out your application deployment Orchestrate your deployments

34 Process - Build a corporate golden image

35 Process - Build a corporate golden image RH 1.0 Unpack the official Red Hat installation binaries

36 Process - Build a corporate golden image RH Unpack the official Red Hat installation binaries 1.0 Apply the latest updates and patches.

37 Process - Build a corporate golden image RH Unpack the official Red Hat installation binaries 1.0 Apply the latest updates and patches. Update and cleanup the provided configuration profiles.

38 Process - Build a corporate golden image RH Unpack the official Red Hat installation binaries 1.0 Apply the latest updates and patches. Update and cleanup the provided configuration profiles. Add your own libraries, drivers and adapters.

39 Process - Build a corporate golden image RH Unpack the official Red Hat installation binaries 1.0 Apply the latest updates and patches. Update and cleanup the provided configuration profiles. Add your own libraries, drivers and adapters. Harden the security matching your needs.

40 Process - Build a corporate golden image RH Unpack the official Red Hat installation binaries 1.0 Apply the latest updates and patches. Update and cleanup the provided configuration profiles. Add your own libraries, drivers and adapters. Harden the security matching your needs. GI 1.0 Versioned corporate Golden Image (GI): ready for use by all Devs and Ops

41 Process - Roll-out your application deployment

42 Process - Roll-out your application deployment Up-to-date deployment

43 Process - Roll-out your application deployment Up-to-date deployment No deployment

44 Process - Roll-out your application deployment Repositories Up-to-date deployment No deployment GI 1.0 Golden Image Java deployment Automation code Topology & env. specific Combine the right artifacts. Configure and start. Up-to-date deployment

45 Process - Roll-out your application deployment Repositories Up-to-date deployment No deployment Outdated deployment GI 1.0 Golden Image Java deployment Automation code Topology & env. specific Combine the right artifacts. Configure and start. Up-to-date deployment

46 Process - Roll-out your application deployment Repositories Up-to-date deployment GI 1.0 Golden Image Java deployment Automation code Topology & env. specific No deployment Combine the right artifacts. Configure and start. Outdated deployment Graceful shutdown Remove platform instance No deployment Up-to-date deployment

47 Process - Roll-out your application deployment Repositories Up-to-date deployment GI 1.0 Golden Image Java deployment Automation code Topology & env. specific No deployment Combine the right artifacts. Configure and start. Up-to-date deployment Outdated deployment Graceful shutdown Combine the right artifacts. Up-to-date deployment Remove platform instance Configure and start. No deployment

48 Process - Orchestrate your deployments Repositories Identity & Access Management GI 1.0 Golden Image Continuous Integration / Delivery Users Java deployment Automation code Topology & env. specific Monitoring Log management

49 Process - Orchestrate your deployments Repositories Identity & Access Management GI 1.0 Golden Image Java deployment Automation code Topology & env. specific Managed infrastructure Continuous Integration / Delivery Monitoring Hardware load-balancer Users Software Load-balancers (httpd+mod_cluster) Log management Red Hat JBoss middleware (EAP / JWS)

50 Process - Orchestrate your deployments Repositories Identity & Access Management GI 1.0 Golden Image Java deployment Automation code Topology & env. specific Managed infrastructure Continuous Integration / Delivery Monitoring Hardware load-balancer Users Software Load-balancers (httpd+mod_cluster) Log management Red Hat JBoss middleware (EAP / JWS)

51 INSTRUMENTS

52 Look to the Orchestra Conductor Red Hat Middleware Repositories Infrastructure 6&7 3

53 What is Ansible? Ansible is a radically simple IT automation engine that automates cloud provisioning, configuration management, application deployment, intra-service orchestration, and many other IT needs. ansible.com/how-ansible-works

54 Why Ansible?

55 Why Ansible? SIMPLE Human readable automation No special coding skills needed Tasks executed in order Get productive quickly

56 Why Ansible? SIMPLE POWERFUL Human readable automation App deployment No special coding skills needed Configuration management Tasks executed in order Workflow orchestration Get productive quickly Orchestrate the app lifecycle

57 Why Ansible? SIMPLE POWERFUL AGENTLESS Human readable automation App deployment Agentless architecture No special coding skills needed Configuration management Uses OpenSSH & WinRM Tasks executed in order Workflow orchestration No agents to exploit or update Get productive quickly Orchestrate the app lifecycle More efficient & more secure

58 How Ansible Works Ansible Automation Engine User Inventory API Infrastructure Modules Playbook Plugins

59 How Ansible Works: Inventory Inventory lists and group hosts containsengine all your systems Ansible Automation User Inventory API Infrastructure Modules Playbook Plugins

60 How Ansible Works: Inventory Inventory lists and group hosts containsengine all your systems Ansible Automation User [webservers] web1.example.com Inventory API Infrastructure web2.example.com [dbserver] Playbook db1.example.com Modules Plugins

61 How Ansible Works: Playbooks Ansible Automation Engine Playbooks are written in YAML User execute tasks sequentially invoke Ansible modules can be grouped in roles Inventory API Infrastructure Modules Playbook Plugins It s supposed to be fun using them. They aren t workbooks :) docs.ansible.com/ansible/glossary.html

62 How Ansible Works: Playbooks --- name: Install and start Apache HTTPD hosts: webservers vars: Ansible Automation Engine Playbooks are written in YAML User execute tasks sequentially invoke Ansible modules can be grouped in roles Inventory http_port: 80 max_clients: 200 remote_user: root API tasks: Infrastructure - name: Install httpd Modules Playbook yum: pkg=httpd state=latest It s supposed to be fun - name: Write the apache config file Plugins template: using them. They aren t workbooks :) src=/srv/httpd.j2 dest=/etc/httpd.conf - name: Start httpd docs.ansible.com/ansible/glossary.html service: name=httpd state=running

63 How Ansible Works: Playbooks --- name: Install and start Apache HTTPD hosts: webservers vars: Ansible Automation Engine Playbooks are written in YAML User execute tasks sequentially invoke Ansible modules can be grouped in roles Inventory http_port: 80 max_clients: 200 remote_user: root API tasks: Infrastructure - name: Install httpd Modules Playbook yum: pkg=httpd state=latest It s supposed to be fun - name: Write the apache config file Plugins template: using them. They aren t workbooks :) src=/srv/httpd.j2 dest=/etc/httpd.conf - name: Start httpd docs.ansible.com/ansible/glossary.html service: name=httpd state=running

64 How Ansible Works: Playbooks --- name: Install and start Apache HTTPD hosts: webservers vars: Ansible Automation Engine Playbooks are written in YAML User execute tasks sequentially invoke Ansible modules can be grouped in roles Inventory http_port: 80 max_clients: 200 remote_user: root API tasks: Infrastructure - name: Install httpd Modules Playbook yum: pkg=httpd state=latest It s supposed to be fun - name: Write the apache config file Plugins template: using them. They aren t workbooks :) src=/srv/httpd.j2 dest=/etc/httpd.conf - name: Start httpd docs.ansible.com/ansible/glossary.html service: name=httpd state=running

65 How Ansible Works: Playbooks --- name: Install and start Apache HTTPD hosts: webservers vars: Ansible Automation Engine Playbooks are written in YAML User execute tasks sequentially invoke Ansible modules can be grouped in roles Inventory http_port: 80 max_clients: 200 remote_user: root API tasks: Infrastructure - name: Install httpd Modules Playbook yum: pkg=httpd state=latest It s supposed to be fun - name: Write the apache config file Plugins template: using them. They aren t workbooks :) src=/srv/httpd.j2 dest=/etc/httpd.conf - name: Start httpd docs.ansible.com/ansible/glossary.html service: name=httpd state=running

66 How Ansible Works: Playbooks --- name: Install and start Apache HTTPD hosts: webservers vars: Ansible Automation Engine Playbooks are written in YAML User execute tasks sequentially invoke Ansible modules can be grouped in roles Inventory http_port: 80 max_clients: 200 remote_user: root API tasks: Infrastructure - name: Install httpd Modules Playbook yum: pkg=httpd state=latest It s supposed to be fun - name: Write the apache config file Plugins template: using them. They aren t workbooks :) src=/srv/httpd.j2 dest=/etc/httpd.conf - name: Start httpd docs.ansible.com/ansible/glossary.html service: name=httpd state=running

67 How Ansible Works: Modules Ansible Automation Engine User Modules are tools in the toolkit extend Ansible can be written in any language Inventory API Infrastructure Modules Playbook Plugins

68 How Ansible Works: Modules Ansible Automation Engine User Modules are tools in the toolkit extend Ansible can be written in any language Inventory API Infrastructure #!/usr/bin/python date = str(datetime.datetime.now()) Modules Playbook Plugins print json.dumps({ "time" : date })

69 Ansible is complete automation Ansible was written to automate complex multi-tier deployments, including: Configuration management App deployment Provisioning Servers and network devices Cloud management and VMs Zero-downtime rolling upgrades Ad-hoc patches and updates

70 Enterprise framework for controlling, securing and managing your Ansible automation with a graphical UI and restful API.

71 Enterprise framework for controlling, securing and managing your Ansible automation with a graphical UI and restful API. Role-based access control keeps environments secure, and teams efficient. Non-privileged users can safely deploy entire applications with push-button deployment access. All Ansible automations are centrally logged, ensuring complete auditability and compliance.

72 Red Hat JBoss Middleware

73 Red Hat JBoss Middleware Full featured Java EE platform Modular and extensible architecture Fast and lightweight Single configuration file Flexible management

74 Red Hat JBoss Middleware Full featured Java EE platform Modular and extensible architecture Fast and lightweight Single configuration file Flexible management Servlet container HTTP web server mod_cluster providing Service Discovery Service Registry

75 Red Hat JBoss EAP - Operation good practices Keep it simple, standalone.

76 Red Hat JBoss EAP - Operation good practices Keep it simple, standalone. Stop gracefully, delete and rebuild when updating.

77 Red Hat JBoss EAP - Operation good practices Keep it simple, standalone. Stop gracefully, delete and rebuild when updating. Use the Command Line Interface (CLI) instead of your favorite XML editor.

78 Red Hat JBoss EAP - Operation good practices Keep it simple, standalone. Stop gracefully, delete and rebuild when updating. Use the Command Line Interface (CLI) instead of your favorite XML editor. Configure EAP to start when your system boots.

79 Red Hat JBoss EAP - Operation good practices Keep it simple, standalone. Stop gracefully, delete and rebuild when updating. Use the Command Line Interface (CLI) instead of your favorite XML editor. Configure EAP to start when your system boots. Prepare troubleshooting procedures and analysis tools.

80 PERFORMANCE

81 Project Blueprint Get it now!

82 Project Blueprint Ansible Roles rh_jboss_core: rh_jboss_eap: Prerequisites for Red Hat JBoss middleware. Manage Red Hat JBoss EAP 6 and 7 instances. multiple parallel versions and profiles support multiple EAP instances per host graceful orchestration application deployment using nexus or local files configuration option using the CLI rh_jboss_web_server apache: rh_jboss_web_server tomcat: mod_cluster integration Application deployment Get it now!

83 Project Blueprint Ansible Roles rh_jboss_core: rh_jboss_eap: Prerequisites for Red Hat JBoss middleware. Manage Red Hat JBoss EAP 6 and 7 instances. multiple parallel versions and profiles support multiple EAP instances per host graceful orchestration application deployment using nexus or local files configuration option using the CLI rh_jboss_web_server apache: rh_jboss_web_server tomcat: Provisioned virtual machines Managed hosts Nexus Customized Ansible Tower mod_cluster integration Application deployment Get it now!

84 Topology = inventory + groups... inventory/hosts-dev Definition of the managed hosts (VM) host-dev-01 host-dev-02 host-dev-03 ansible_host= ansible_host= ansible_host= [dev:children] dev-eap-group dev-jws-group Assigned groups [dev-jws-group] host-dev-01 [dev-eap-group] host-dev-02 host-dev-03

85 Topology = inventory + groups... inventory/hosts-dev Definition of the managed hosts (VM) host-dev-01 host-dev-02 host-dev-03 ansible_host= ansible_host= ansible_host= [dev:children] dev-eap-group dev-jws-group Assigned groups [dev-jws-group] host-dev-01 [dev-eap-group] host-dev-02 host-dev-03 dev dev-jws-group host-dev-01 dev-eap-group host-dev-02 host-dev-03

86 Topology = + roles + variables site.yml --- hosts: "dev-jws-group" roles: # - {role: "rh_jboss_web_server tomcat", app_list: { "tomcat-sample.war" }} - {role: "rh_jboss_web_server apache"} - hosts: "dev-eap-group" roles: -{ -{ role: "rh_jboss_eap", role: "rh_jboss_eap", jboss_eap_instance_name: "petclinic", jboss_eap_instance_name: "ticket_monster", jboss_eap_golden_image_name: "jboss-eap-7.0.0_gi", jboss_eap_golden_image_name: "jboss-eap-6.4.8_gi", jboss_eap_instance_standalone_file: "standalone-full-ha.xml", jboss_eap_instance_standalone_file: "standalone.xml", jboss_eap_instance_port_offset: "1000", jboss_eap_instance_port_offset: 0, app_list: { "petclinic.war" }, app_list: { "ticket-monster.war" }, #app_mvn_list: [ { g: "com.redhat.jboss", a: "petclinic.war", v: "1.0", e: "war" } ], cli_list: { "add_datasource.cli" }, } }

87 Overview Orchestrated middleware Application Platform host-dev-02 Load Balancer host-dev Application Platform host-dev-03 Nexus

88 Demo time!

89 Thank you! Marc Zottner Architect, Red Hat Roeland van de Pol Architect, Red Hat

90