redhat-gpe/rhte_lab_00_common

:scrollbar: :data-uri: :toc2: :linkattrs: :cna_labs_overview_old: link:https://docs.google.com/document/d/1hhvRPN0H48zUs4IxJh4CwS3T9V3r_lAmM46m8cWuyBs/edit#heading=h.5ovkhgyfbmm1[GPTE Cloud Native Apps Labs Overview] :cna_labs_overview_folder: link:https://drive.google.com/drive/folders/1qDFMyyr4idNOT8hh0HoTE81HRLXiqy5a[GPTE Cloud Native Apps Lab Overview] :rhte_session_planning: link:https://docs.google.com/spreadsheets/d/1BcWPAxo9GHR8Z1yHwxRCVA5tNpN8FNsNkXA6WB0yb6Q/edit#gid=1572036407[2018 Global RHTE - General Session Planning] :rht_planner_folder: link:https://drive.google.com/drive/folders/1HfQuQ_Ywwtv2t8-8jhKZ2ZGEkwRCpqYk[RHTE 2018 Planning Folder in Google Drive] :automation_labs_overview: link:https://drive.google.com/open?id=1SOCL49P87GeEcAbXF7L8Dq4b3_YMkoxkusq8tiPKfy8[GPTE Automation and Management Labs Overview] :cloud_infrastructure_overview: link:https://drive.google.com/open?id=1o60IGJGS2Je4ydTBk_c_LT8HgIcGVsovke6bdX8QXB8[GPTE Hybrid Cloud Infrastructure labs Overview]

= Multi Product Labs : Instructor Guide

:numbered:

== Overview

Red Hat Solution Architects and consultants have requested multi-product labs that they can:

. Learn from . Leverage as the basis for labs that they utilize in the field

Red Hat GPTE has been directed to create and manage these multi-product labs.

These labs will be utilized at the 3 Red Hat Tech Exchanges in 2018.

== Comparison with GPTE course labs

GPTE middleware course lab instructions tend to be step by step in nature. This is particularly the case at the experienced and advanced levels. Lab assets are typically a skeleton of the final solution. GPTE middleware courses tend to be focused on functionality provided by a single Red Hat product.

These multi-product labs are different:

. lab assets should consist of the final solution. . The multi-product labs should be reproducible out of the box in Red Hat Partner lab System (RHPDS). . Lab instructions should highlight how to order and use the lab.

== Planning Documents:

. {cna_labs_overview_folder} (Middleware team labs) . {rhte_session_planning} . link:https://docs.google.com/spreadsheets/d/1kkjsKEdsJ7ikAoLa6GvziFm4iFHCV9gWK23R1oHXIyg/edit#gid=652240199[2018 RHTE - Global Lab Planning Doc] . link:https://docs.google.com/spreadsheets/d/1bCTUzTNTjUu9rG9DPGo68H4lyLCg6p9rMjuC2eM1Obk/edit#gid=396704806[EMEA Tech Exchange Session Planning]

== Red Hat Tech Exchange 2018 Dates and Locations

. Sept 10-14, 2018 : Taiwan .. link:https://bluejeans.com/s/rq7st[APAC RHTE Speaker Briefing: Bluejeans Recording] .. link:https://docs.google.com/presentation/d/1h2-WUhGEH0mhdbOhx7hDN964841P0UxwRqL1Y9OT5bs/edit#slide=id.g3a3c020939_0_72[APAC RHTE Speaker Briefing Deck]

. Sept 24-28, 2018 : Prague . Oct 8-12, 2018 : Orlando, Florida, US

Please check the Roadmunk FY19 ILT schedule to determine if/when you will be attending

== GUID Grabber

. REGION will be pulled from GUID Grabber. Please review

.. https://docs.google.com/document/d/1GoZjPpfqnian49OWAZ3vlp2TL5aKOhyfvf7jaBH0WFA/edit#heading=h.2xnkj1268hry .. https://mojo.redhat.com/docs/DOC-1172529

== Presentation Tips

. link:https://github.com/vmbrasseur/Public_Speaking#presenting-talks[Presenting Talks]

== Project Management

=== Contributors:

=== Project plans

. Planning will occur in each multi-product lab's link:https://github.com/redhat-gpe?utf8=%E2%9C%93&q=rhte_&type=&language=[git repo]. . Each project git repo has a prefix called: rhte. . All issues should be assigned the following: .. Assignee .. Project (rhte) .. Milestone . [red]#Please make commits fine grained and specific to a github issue# . [red]#Please reference the github issue for each commit in the commit message# +

$ git commit -m https://github.com/redhat-gpe/rhte_lab_04_api_mgmt_and_service_mesh/issues/15

== Slides

There will be one slide deck per multi-product lab. Please create slide decks in: redhat.slides.com.

. link:https://redhat.slides.com/jbride/01_apis_as_a_business?token=KH_uUwDl[rhte_lab_01_apis_as_a_business] . link:https://redhat.slides.com/jbride/02_brownfield_migration?token=gV0HpHBS[rhte_lab_02_brownfield_migration] . link:https://redhat.slides.com/jbride/03_msa_and_service_mesh?token=ckNXJ1yU[rhte_lab_03_msa_and_service_mesh] . link:https://redhat.slides.com/jbride/04_api_mgmt_service_mesh?token=YpfrvfsG[rhte_lab_04_api_mgmt_and_service_mesh] . link:https://redhat.slides.com/jbride/05_msa_orchestration?token=ReMbgqHO[rhte_lab_05_msa_orchestration] . link:https://redhat.slides.com/jbride/06_operational_intelligence?token=jf9evKi3[rhte_lab_06_operational_intelligence]

== OCP Infrastructure

All labs will be executed in OpenShift.

. Development environment: Please use https://master.dev39.openshift.opentlc.com . ILTs : + For each ILT, an appropriately sized OCP Workshop environment will be provisioned for each multi-product lab. ie: 6 MW multi-product labs = 6 dedicated OCP workshop environments.

== CI / CD

=== Version Control

All aspects of each multi-product lab is to be version controlled.

NOTE: These multi-product labs are not a GPTE course. Therefore, there is not a need for assessment questions nor audio recording of slides.

. link:https://github.com/redhat-gpe?utf8=%E2%9C%93&q=rhte_&type=&language=[project git repo] .. Slides + NOTE: Please implement slides in: redhat.slides.com and then version control in this git project repo. .. Lab Instructions .. Project Management .. Issue tracking

. link:https://github.com/gpe-mw-training[Lab assets] + .. ansible role .. OCP templates .. Jenkins pipeline .. code solution .. mock data set .. unit and integration tests

=== Binary Repositories

Each OCP cluster comes provisioned with a Nexus in the default project.

Please utilize this nexus for the following:

. Proxy maven repository . Repository for generated binary artifacts from your Jenkins pipelines . Linux container image Repository

=== Code Analysis

=== Jenkins

We'll share a link:https://jenkins-rhte-jenkins.apps.dev39.openshift.opentlc.com[common multi-tenant Jenkins server] that will be provisioned and maintained by Hong.

Please develop your Jenkins pipelines using the groovy based workflow plugin.

The pipeline itself should be written in a file and version controlled as part of your lab assets.

redhat-gpe / rhte_lab_00_common

readme

$ git commit -m https://github.com/redhat-gpe/rhte_lab_04_api_mgmt_and_service_mesh/issues/15