|
15 | 15 | 2. Run `./setup-multicloud.sh` (takes ~20 minutes)
|
16 | 16 | - Step 1 will have put you in the appropriate `.../microservices-datadriven/grabdish` dir.
|
17 | 17 | - Takes CLUSTER_NAME as an argument
|
18 |
| - - This will install verrazzano, deploy workshop microservices, and provide URLs for |
| 18 | + - This will install verrazzano, deploy workshop microservices, and provide URLs for the Frontend microservice and the consoles... |
19 | 19 | - Grafana
|
20 | 20 | - Prometheus
|
21 | 21 | - Kibana
|
|
24 | 24 | - KeyCloak
|
25 | 25 | - Example output...
|
26 | 26 |
|
27 |
| - ` NAMESPACE NAME CLASS HOSTS ADDRESS PORTS AGE` |
28 |
| - |
29 |
| - cattle-system rancher <none> rancher.default.158.101.26.111.nip.io 158.101.26.111 80, 443 37h |
30 |
| - keycloak keycloak <none> keycloak.default.158.101.26.111.nip.io 158.101.26.111 80, 443 37h |
31 |
| - verrazzano-system verrazzano-ingress <none> verrazzano.default.158.101.26.111.nip.io 158.101.26.111 80, 443 37h |
32 |
| - verrazzano-system vmi-system-es-ingest <none> elasticsearch.vmi.system.default.158.101.26.111.nip.io 158.101.26.111 80, 443 37h |
33 |
| - verrazzano-system vmi-system-grafana <none> grafana.vmi.system.default.158.101.26.111.nip.io 158.101.26.111 80, 443 37h |
34 |
| - verrazzano-system vmi-system-kibana <none> kibana.vmi.system.default.158.101.26.111.nip.io 158.101.26.111 80, 443 37h |
35 |
| - verrazzano-system vmi-system-prometheus <none> prometheus.vmi.system.default.158.101.26.111.nip.io 158.101.26.111 80, 443 37h |
36 |
| - 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 |
| 27 | + `FrontEnd HOST is frontend-helidon-appconf.msdataworkshop.129.146.227.229.nip.io` |
| 28 | + |
| 29 | + ` NAMESPACE NAME CLASS HOSTS ADDRESS PORTS AGE` |
| 30 | + |
| 31 | + cattle-system rancher <none> rancher.default.158.101.26.111.nip.io 158.101.26.111 80, 443 37h |
| 32 | + keycloak keycloak <none> keycloak.default.158.101.26.111.nip.io 158.101.26.111 80, 443 37h |
| 33 | + verrazzano-system verrazzano-ingress <none> verrazzano.default.158.101.26.111.nip.io 158.101.26.111 80, 443 37h |
| 34 | + verrazzano-system vmi-system-es-ingest <none> elasticsearch.vmi.system.default.158.101.26.111.nip.io 158.101.26.111 80, 443 37h |
| 35 | + verrazzano-system vmi-system-grafana <none> grafana.vmi.system.default.158.101.26.111.nip.io 158.101.26.111 80, 443 37h |
| 36 | + verrazzano-system vmi-system-kibana <none> kibana.vmi.system.default.158.101.26.111.nip.io 158.101.26.111 80, 443 37h |
| 37 | + verrazzano-system vmi-system-prometheus <none> prometheus.vmi.system.default.158.101.26.111.nip.io 158.101.26.111 80, 443 37h |
| 38 | + 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 |
37 | 39 |
|
38 | 40 |
|
39 | 41 | 3. Do `Lab 2: Data-centric microservices walkthrough with Helidon MP` to test the app, etc.
|
40 |
| - - REPLACE STEP 1 INSTRUCTION IN LAB |
41 |
| - - Instead of running `cd $GRABDISH_HOME;./deploy.sh` run `cd $GRABDISH_HOME;./deploy-multicloud.sh` |
| 42 | + - SKIP STEP 1 INSTRUCTION IN THE LAB |
| 43 | + - Step 2 (`./setup-multicloud.sh`) in this readme will have made the `./deploy-multicloud.sh` call which in turn |
| 44 | + deploys the GrabDish microservices in the Verrazzano/OAM framework and so there is no need to explicitly deploy. |
42 | 45 | - Proceed with all other steps. Step 1 is the only difference.
|
43 | 46 |
|
44 | 47 | 4. Optionally, do labs 3, 4, and 5
|
45 | 48 | - Optionally do `Lab 3: Polyglot Microservices` to test with other languages such as Python, JS, .NET, and Go
|
46 |
| - - Again, instead of running `cd $GRABDISH_HOME;./deploy.sh` run `cd $GRABDISH_HOME;./deploy-multicloud.sh` |
| 49 | + - Instead of running `cd $GRABDISH_HOME;./deploy.sh` run `cd $GRABDISH_HOME;./deploy-multicloud.sh` |
47 | 50 | - Optionally do `Lab 4: Scaling` to show how the application can be scaled at the application and database tiers to maintain optimal performance.
|
48 | 51 | - The creation of the LB in Step 1 is not necessary as the gateway can be used.
|
49 | 52 | - 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]}'`
|
|
0 commit comments