|
3 | 3 |
|
4 | 4 | 0. Starting from http://bit.ly/simplifymicroservices
|
5 | 5 |
|
6 |
| -1. Do `Lab 1: Setup` |
7 |
| - - This will clone the workshop src from https://github.com/oracle/microservices-datadriven |
8 |
| - and provision and configure the following |
| 6 | +1. Do `Lab 1: Setup` (takes ~20 to 25 minutes) |
| 7 | + - This will clone the workshop src from https://github.com/oracle/microservices-datadriven, |
| 8 | + provision and configure the following, and build and push the workshop microservice docker images |
9 | 9 | - OKE cluster
|
10 | 10 | - 2 ATP databases (with secrets, AQ propagation, etc.)
|
11 | 11 | - OCIR
|
12 | 12 | - Object Storage
|
| 13 | + - Jaeger |
13 | 14 |
|
14 |
| -2. Run `./setup-multicloud.sh` (step 1 will have put you in the appropriate `.../microservices-datadriven/grabdish` dir) |
15 |
| - - This will install verrazzano and provide URLs for |
| 15 | +2. Run `./setup-multicloud.sh` (takes ~20 minutes) |
| 16 | + - Step 1 will have put you in the appropriate `.../microservices-datadriven/grabdish` dir. |
| 17 | + - This will install verrazzano, deploy workshop microservices, and provide URLs for |
16 | 18 | - Grafana
|
17 | 19 | - Prometheus
|
18 | 20 | - Kibana
|
19 | 21 | - Elasticsearch
|
20 | 22 | - Rancher
|
21 | 23 | - KeyCloak
|
22 |
| - - For example... |
23 |
| - NAMESPACE NAME CLASS HOSTS ADDRESS PORTS AGE |
24 |
| - cattle-system rancher <none> rancher.default.158.101.26.244.nip.io 158.101.26.244 80, 443 37h |
25 |
| - keycloak keycloak <none> keycloak.default.158.101.26.244.nip.io 158.101.26.244 80, 443 37h |
26 |
| - verrazzano-system verrazzano-ingress <none> verrazzano.default.158.101.26.244.nip.io 158.101.26.244 80, 443 37h |
27 |
| - verrazzano-system vmi-system-es-ingest <none> elasticsearch.vmi.system.default.158.101.26.244.nip.io 158.101.26.244 80, 443 37h |
28 |
| - verrazzano-system vmi-system-grafana <none> grafana.vmi.system.default.158.101.26.244.nip.io 158.101.26.244 80, 443 37h |
29 |
| - verrazzano-system vmi-system-kibana <none> kibana.vmi.system.default.158.101.26.244.nip.io 158.101.26.244 80, 443 37h |
30 |
| - verrazzano-system vmi-system-prometheus <none> prometheus.vmi.system.default.158.101.26.244.nip.io 158.101.26.244 80, 443 37h |
31 |
| - verrazzano-system vmi-system-prometheus-gw <none> prometheus-gw.vmi.system.default.158.101.26.244.nip.io 158.101.26.244 80, 443 37h |
| 24 | + - Example output... |
| 25 | + |
| 26 | + ` NAMESPACE NAME CLASS HOSTS ADDRESS PORTS AGE` |
| 27 | + |
| 28 | + cattle-system rancher <none> rancher.default.158.101.26.111.nip.io 158.101.26.111 80, 443 37h |
| 29 | + keycloak keycloak <none> keycloak.default.158.101.26.111.nip.io 158.101.26.111 80, 443 37h |
| 30 | + verrazzano-system verrazzano-ingress <none> verrazzano.default.158.101.26.111.nip.io 158.101.26.111 80, 443 37h |
| 31 | + verrazzano-system vmi-system-es-ingest <none> elasticsearch.vmi.system.default.158.101.26.111.nip.io 158.101.26.111 80, 443 37h |
| 32 | + verrazzano-system vmi-system-grafana <none> grafana.vmi.system.default.158.101.26.111.nip.io 158.101.26.111 80, 443 37h |
| 33 | + verrazzano-system vmi-system-kibana <none> kibana.vmi.system.default.158.101.26.111.nip.io 158.101.26.111 80, 443 37h |
| 34 | + verrazzano-system vmi-system-prometheus <none> prometheus.vmi.system.default.158.101.26.111.nip.io 158.101.26.111 80, 443 37h |
| 35 | + verrazzano-system vmi-system-prometheus-gw <none> prometheus-gw.vmi.system.default.158.101.26.111.nip.io 158.101.26.111 80, 443 37h |
| 36 | + |
32 | 37 |
|
33 | 38 | 3. Do `Lab 2: Data-centric microservices walkthrough with Helidon MP` to test the app, etc.
|
34 | 39 | - REPLACE STEP 1 INSTRUCTION IN LAB
|
|
37 | 42 |
|
38 | 43 | 4. Optionally, do labs 3, 4, and 5
|
39 | 44 | - Optionally do `Lab 3: Polyglot Microservices` to test with other languages such as Python, JS, .NET, and Go
|
40 |
| - - Instead of running `cd $GRABDISH_HOME;./deploy.sh` run `cd $GRABDISH_HOME;./deploy-multicloud.sh` |
| 45 | + - Again, instead of running `cd $GRABDISH_HOME;./deploy.sh` run `cd $GRABDISH_HOME;./deploy-multicloud.sh` |
41 | 46 | - Optionally do `Lab 4: Scaling` to show how the application can be scaled at the application and database tiers to maintain optimal performance.
|
42 |
| - - Can be run without modification |
| 47 | + - The creation of the LB in Step 1 is not necessary as the gateway can be used. |
| 48 | + - Instead of running `export LB=[LB_IPADDRESS]` run `export LB=$(kubectl get gateway msdataworkshop-order-helidon-appconf-gw -n msdataworkshop -o jsonpath='{.spec.servers[0].hosts[0]}'` |
43 | 49 | - Optionally do `Lab 5: Tracing Using Jaeger` to show microservice activity using OpenTracing and Jaeger.
|
44 | 50 | - Can be run without modification
|
45 | 51 |
|
46 |
| -4. Use https URLs and login from output in step 2 to view various dashboards. |
| 52 | +4. Use https URLs and login from output in step 2 to view various dashboards deployed by Verrazzano and Jaeger. |
| 53 | + |
| 54 | +5. Teardown by running |
| 55 | + - `./undeploy-multicloud.sh` (to remove workshop microservices, etc.) |
| 56 | + - `./destroy-multicloud.sh` (to remove Verrazzano) |
| 57 | + |
| 58 | +TODOs |
| 59 | + - one open issue: RBAC source access (currently this done by manually changing the authorizationpolicy after the fact) |
| 60 | + and the appropriate way is (if all ms are not in the same app) is to use a project. Doc refs... |
| 61 | + - https://verrazzano.io/docs/concepts/verrazzanomulticluster/#the-verrazzanoproject-resource |
| 62 | + - https://verrazzano.io/docs/reference/api/multicluster/verrazzanoproject/ |
| 63 | + - ./setup-multicloud.sh should take a password to override those auto-generated and password(s) should not be displayed |
| 64 | + - add walkthrough of consoles... |
| 65 | + - reduce the number of required LBs while also keeping the current workshop and multi-cloud workshop independent |
| 66 | + - the workshop uses 2 LBs (one for the app and one for Jaeger) |
| 67 | + - the scaling lab uses an additional 1 LB for requests as they go directly to the order service. |
| 68 | + - Verrazzano uses 2 LBs (one for consoles and one for apps) |
| 69 | + - possibly add Kiali |
47 | 70 |
|
48 |
| -TODO add walkthrough of consoles... |
49 | 71 |
|
50 | 72 | Future: Running on other clouds starting with Azure (using interconnect, etc.)...
|
0 commit comments