Skip to content

Commit ede6277

Browse files
JeffreyDallasJeffreyDallas
committed
change fst full stacking to solo
Signed-off-by: Jeffrey Tang <[email protected]>
1 parent 5b9d19d commit ede6277

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

43 files changed

+175
-175
lines changed

‎.github/ISSUE_TEMPLATE/feature_enhancement.yml

+1-1
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ body:
2222
placeholder: |
2323
_A clear and concise description of what you want to happen._
2424
25-
Note: Feature enhancements to integrate vendor specific cloud tools (e.g. awscli, gcloud-sdk, azure-cli) will likely be rejected as the Full Stack Testing (FST) Suite aims to be vendor agnostic.
25+
Note: Feature enhancements to integrate vendor specific cloud tools (e.g. awscli, gcloud-sdk, azure-cli) will likely be rejected as the Full Stack Testing (Solo) Suite aims to be vendor agnostic.
2626
validations:
2727
required: true
2828
- type: textarea

‎.github/ISSUE_TEMPLATE/feature_request.yml

+1-1
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ body:
1212
placeholder: |
1313
_A clear and concise description of what you want to happen._
1414
15-
Note: Feature requests to integrate vendor specific cloud tools (e.g. awscli, gcloud-sdk, azure-cli) will likely be rejected as the Full Stack Testing (FST) Suite aims to be vendor agnostic.
15+
Note: Feature requests to integrate vendor specific cloud tools (e.g. awscli, gcloud-sdk, azure-cli) will likely be rejected as the Full Stack Testing (Solo) Suite aims to be vendor agnostic.
1616
validations:
1717
required: true
1818
- type: textarea

‎.github/workflows/script/relay_smoke_test.sh

+1-1
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ solo mirror-node deploy
1212
solo relay deploy -i node1
1313
kubectl port-forward svc/relay-node1-hedera-json-rpc-relay -n solo-e2e 7546:7546 &
1414
kubectl port-forward svc/haproxy-node1-svc -n solo-e2e 50211:50211 &
15-
kubectl port-forward svc/fullstack-deployment-hedera-explorer -n solo-e2e 8080:80 &
15+
kubectl port-forward svc/solo-deployment-hedera-explorer -n solo-e2e 8080:80 &
1616

1717
echo "Clone hedera local node"
1818

‎README.md

+15-15
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ An opinionated CLI tool to deploy and manage standalone test networks.
2626

2727
## Requirements
2828

29-
| Solo Version | Node.js | Kind | FST Chart | Hedera | Kubernetes | Kubectl | Helm | k9s | Docker Resources | Java |
29+
| Solo Version | Node.js | Kind | Solo Chart | Hedera | Kubernetes | Kubectl | Helm | k9s | Docker Resources | Java |
3030
|--------------|---------------------------|------------|-----------|----------|------------|------------|---------|------------|-------------------------|--------------|
3131
| 0.29.0 | >= 20.14.0 (lts/hydrogen) | >= v1.29.1 | v0.30.0 | v0.53.0+ | >= v1.27.3 | >= v1.27.3 | v3.14.2 | >= v0.27.4 | Memory >= 8GB, CPU >= 4 | >= 21.0.1+12 |
3232
| 0.30.0 | >= 20.14.0 (lts/hydrogen) | >= v1.29.1 | v0.30.0 | v0.54.0+ | >= v1.27.3 | >= v1.27.3 | v3.14.2 | >= v0.27.4 | Memory >= 8GB, CPU >= 4 | >= 21.0.1+12 |
@@ -107,8 +107,8 @@ You may now view pods in your cluster using `k9s -A` as below:
107107
MEM: n/a
108108
┌───────────────────────────────────────────────── Pods(all)[11] ─────────────────────────────────────────────────┐
109109
│ NAMESPACE↑ NAME PF READY STATUS RESTARTS IP NODE │
110-
│ fullstack-setup console-557956d575-4r5xm ● 1/1 Running 0 10.244.0.5 solo-con │
111-
│ fullstack-setup minio-operator-7d575c5f84-8shc9 ● 1/1 Running 0 10.244.0.6 solo-con │
110+
│ solo-setup console-557956d575-4r5xm ● 1/1 Running 0 10.244.0.5 solo-con │
111+
│ solo-setup minio-operator-7d575c5f84-8shc9 ● 1/1 Running 0 10.244.0.6 solo-con │
112112
│ kube-system coredns-5d78c9869d-6cfbg ● 1/1 Running 0 10.244.0.4 solo-con │
113113
│ kube-system coredns-5d78c9869d-gxcjz ● 1/1 Running 0 10.244.0.3 solo-con │
114114
│ kube-system etcd-solo-control-plane ● 1/1 Running 0 172.18.0.2 solo-con │
@@ -212,7 +212,7 @@ Kubernetes Namespace : solo
212212
**********************************************************************************
213213
✔ Initialize
214214
✔ Prepare chart values
215-
✔ Install 'fullstack-cluster-setup' chart
215+
✔ Install 'solo-cluster-setup' chart
216216
```
217217

218218
In a separate terminal, you may run `k9s` to view the pod status.
@@ -247,7 +247,7 @@ Kubernetes Namespace : solo
247247
✔ Copy Gossip keys
248248
✔ Node: node3
249249
✔ Copy node keys to secrets
250-
✔ Install chart 'fullstack-deployment'
250+
✔ Install chart 'solo-deployment'
251251
✔ Check Node: node1
252252
✔ Check Node: node2
253253
✔ Check Node: node3
@@ -411,15 +411,15 @@ Context: kind-solo <0> all <a> Attach
411411
│ solo envoy-proxy-node1-65f8879dcc-rwg97 ● 1/1 Running 0 1 │
412412
│ solo envoy-proxy-node2-667f848689-628cx ● 1/1 Running 0 1 │
413413
│ solo envoy-proxy-node3-6bb4b4cbdf-dmwtr ● 1/1 Running 0 1 │
414-
│ solo fullstack-deployment-grpc-75bb9c6c55-l7kvt ● 1/1 Running 0 1 │
415-
│ solo fullstack-deployment-hedera-explorer-6565ccb4cb-9dbw2 ● 1/1 Running 0 1 │
416-
│ solo fullstack-deployment-importer-dd74fd466-vs4mb ● 1/1 Running 0 1 │
417-
│ solo fullstack-deployment-monitor-54b8f57db9-fn5qq ● 1/1 Running 0 1 │
418-
│ solo fullstack-deployment-postgres-postgresql-0 ● 1/1 Running 0 1 │
419-
│ solo fullstack-deployment-redis-node-0 ● 2/2 Running 0 1 │
420-
│ solo fullstack-deployment-rest-6d48f8dbfc-plbp2 ● 1/1 Running 0 1 │
421-
│ solo fullstack-deployment-restjava-5d6c4cb648-r597f ● 1/1 Running 0 1 │
422-
│ solo fullstack-deployment-web3-55fdfbc7f7-lzhfl ● 1/1 Running 0 1 │
414+
│ solo solo-deployment-grpc-75bb9c6c55-l7kvt ● 1/1 Running 0 1 │
415+
│ solo solo-deployment-hedera-explorer-6565ccb4cb-9dbw2 ● 1/1 Running 0 1 │
416+
│ solo solo-deployment-importer-dd74fd466-vs4mb ● 1/1 Running 0 1 │
417+
│ solo solo-deployment-monitor-54b8f57db9-fn5qq ● 1/1 Running 0 1 │
418+
│ solo solo-deployment-postgres-postgresql-0 ● 1/1 Running 0 1 │
419+
│ solo solo-deployment-redis-node-0 ● 2/2 Running 0 1 │
420+
│ solo solo-deployment-rest-6d48f8dbfc-plbp2 ● 1/1 Running 0 1 │
421+
│ solo solo-deployment-restjava-5d6c4cb648-r597f ● 1/1 Running 0 1 │
422+
│ solo solo-deployment-web3-55fdfbc7f7-lzhfl ● 1/1 Running 0 1 │
423423
│ solo haproxy-node1-785b9b6f9b-676mr ● 1/1 Running 1 1 │
424424
│ solo haproxy-node2-644b8c76d-v9mg6 ● 1/1 Running 1 1 │
425425
│ solo haproxy-node3-fbffdb64-272t2 ● 1/1 Running 1 1 │
@@ -442,7 +442,7 @@ Once the nodes are up, you may now expose various services (using `k9s` (shift-f
442442
* Node services: `network-<node ID>-svc`
443443
* HAProxy: `haproxy-<node ID>-svc`
444444
* Envoy Proxy: `envoy-proxy-<node ID>-svc`
445-
* Hedera explorer: `fullstack-deployment-hedera-explorer`
445+
* Hedera explorer: `solo-deployment-hedera-explorer`
446446
* JSON Rpc Relays
447447
* You can deploy JSON RPC relays for one or more nodes as below:
448448
```

‎README.md.template

+14-14
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ An opinionated CLI tool to deploy and manage standalone test networks.
2626

2727
## Requirements
2828

29-
| Solo Version | Node.js | Kind | FST Chart | Hedera | Kubernetes | Kubectl | Helm | k9s | Docker Resources | Java |
29+
| Solo Version | Node.js | Kind | Solo Chart | Hedera | Kubernetes | Kubectl | Helm | k9s | Docker Resources | Java |
3030
|--------------|---------------------------|------------|-----------|----------|------------|------------|---------|------------|-------------------------|--------------|
3131
| 0.29.0 | >= 20.14.0 (lts/hydrogen) | >= v1.29.1 | v0.30.0 | v0.53.0+ | >= v1.27.3 | >= v1.27.3 | v3.14.2 | >= v0.27.4 | Memory >= 8GB, CPU >= 4 | >= 21.0.1+12 |
3232
| 0.30.0 | >= 20.14.0 (lts/hydrogen) | >= v1.29.1 | v0.30.0 | v0.54.0+ | >= v1.27.3 | >= v1.27.3 | v3.14.2 | >= v0.27.4 | Memory >= 8GB, CPU >= 4 | >= 21.0.1+12 |
@@ -95,8 +95,8 @@ You may now view pods in your cluster using `k9s -A` as below:
9595
MEM: n/a
9696
┌───────────────────────────────────────────────── Pods(all)[11] ─────────────────────────────────────────────────┐
9797
│ NAMESPACE↑ NAME PF READY STATUS RESTARTS IP NODE │
98-
│ fullstack-setup console-557956d575-4r5xm ● 1/1 Running 0 10.244.0.5 solo-con │
99-
│ fullstack-setup minio-operator-7d575c5f84-8shc9 ● 1/1 Running 0 10.244.0.6 solo-con │
98+
│ solo-setup console-557956d575-4r5xm ● 1/1 Running 0 10.244.0.5 solo-con │
99+
│ solo-setup minio-operator-7d575c5f84-8shc9 ● 1/1 Running 0 10.244.0.6 solo-con │
100100
│ kube-system coredns-5d78c9869d-6cfbg ● 1/1 Running 0 10.244.0.4 solo-con │
101101
│ kube-system coredns-5d78c9869d-gxcjz ● 1/1 Running 0 10.244.0.3 solo-con │
102102
│ kube-system etcd-solo-control-plane ● 1/1 Running 0 172.18.0.2 solo-con │
@@ -249,15 +249,15 @@ Context: kind-solo <0> all <a> Attach
249249
│ solo envoy-proxy-node1-65f8879dcc-rwg97 ● 1/1 Running 0 1 │
250250
│ solo envoy-proxy-node2-667f848689-628cx ● 1/1 Running 0 1 │
251251
│ solo envoy-proxy-node3-6bb4b4cbdf-dmwtr ● 1/1 Running 0 1 │
252-
│ solo fullstack-deployment-grpc-75bb9c6c55-l7kvt ● 1/1 Running 0 1 │
253-
│ solo fullstack-deployment-hedera-explorer-6565ccb4cb-9dbw2 ● 1/1 Running 0 1 │
254-
│ solo fullstack-deployment-importer-dd74fd466-vs4mb ● 1/1 Running 0 1 │
255-
│ solo fullstack-deployment-monitor-54b8f57db9-fn5qq ● 1/1 Running 0 1 │
256-
│ solo fullstack-deployment-postgres-postgresql-0 ● 1/1 Running 0 1 │
257-
│ solo fullstack-deployment-redis-node-0 ● 2/2 Running 0 1 │
258-
│ solo fullstack-deployment-rest-6d48f8dbfc-plbp2 ● 1/1 Running 0 1 │
259-
│ solo fullstack-deployment-restjava-5d6c4cb648-r597f ● 1/1 Running 0 1 │
260-
│ solo fullstack-deployment-web3-55fdfbc7f7-lzhfl ● 1/1 Running 0 1 │
252+
│ solo solo-deployment-grpc-75bb9c6c55-l7kvt ● 1/1 Running 0 1 │
253+
│ solo solo-deployment-hedera-explorer-6565ccb4cb-9dbw2 ● 1/1 Running 0 1 │
254+
│ solo solo-deployment-importer-dd74fd466-vs4mb ● 1/1 Running 0 1 │
255+
│ solo solo-deployment-monitor-54b8f57db9-fn5qq ● 1/1 Running 0 1 │
256+
│ solo solo-deployment-postgres-postgresql-0 ● 1/1 Running 0 1 │
257+
│ solo solo-deployment-redis-node-0 ● 2/2 Running 0 1 │
258+
│ solo solo-deployment-rest-6d48f8dbfc-plbp2 ● 1/1 Running 0 1 │
259+
│ solo solo-deployment-restjava-5d6c4cb648-r597f ● 1/1 Running 0 1 │
260+
│ solo solo-deployment-web3-55fdfbc7f7-lzhfl ● 1/1 Running 0 1 │
261261
│ solo haproxy-node1-785b9b6f9b-676mr ● 1/1 Running 1 1 │
262262
│ solo haproxy-node2-644b8c76d-v9mg6 ● 1/1 Running 1 1 │
263263
│ solo haproxy-node3-fbffdb64-272t2 ● 1/1 Running 1 1 │
@@ -295,10 +295,10 @@ Once the nodes are up, you may now expose various services (using `k9s` (shift-f
295295
kubectl port-forward svc/envoy-proxy-node2-svc -n "${SOLO_NAMESPACE}" 8281:8080 &
296296
kubectl port-forward svc/envoy-proxy-node3-svc -n "${SOLO_NAMESPACE}" 8381:8080 &
297297
```
298-
* Hedera explorer: `fullstack-deployment-hedera-explorer`
298+
* Hedera explorer: `solo-deployment-hedera-explorer`
299299
```bash
300300
#enable portforwarding for hedera explorer, can be access at http://localhost:8080/
301-
kubectl port-forward svc/fullstack-deployment-hedera-explorer -n "${SOLO_NAMESPACE}" 8080:80 &
301+
kubectl port-forward svc/solo-deployment-hedera-explorer -n "${SOLO_NAMESPACE}" 8080:80 &
302302
```
303303
* JSON Rpc Relays
304304
* You can deploy JSON RPC relays for one or more nodes as below:

‎docs/content/getting-started/deploy.md

+11-11
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,7 @@ Kubernetes Namespace : solo
104104
**********************************************************************************
105105
✔ Initialize
106106
✔ Prepare chart values
107-
✔ Install 'fullstack-cluster-setup' chart
107+
✔ Install 'solo-cluster-setup' chart
108108
109109
```
110110

@@ -128,7 +128,7 @@ Kubernetes Cluster : kind-solo
128128
Kubernetes Namespace : solo
129129
**********************************************************************************
130130
✔ Initialize
131-
✔ Install chart 'fullstack-deployment'
131+
✔ Install chart 'solo-deployment'
132132
✔ Check Node: node0
133133
✔ Check Node: node1
134134
✔ Check Node: node2
@@ -301,8 +301,8 @@ You may view the list of pods using `k9s` as below:
301301
MEM: n/a
302302
┌─────────────────────────────────────────────────── Pods(all)[27] ────────────────────────────────────────────────────┐
303303
│ NAMESPACE↑ NAME PF READY RESTARTS STATUS IP │
304-
│ fullstack-setup console-557956d575-fqctd ● 1/1 0 Running 10.244.0.4 │
305-
│ fullstack-setup minio-operator-7d575c5f84-j9p6f ● 1/1 0 Running 10.244.0.3 │
304+
│ solo-setup console-557956d575-fqctd ● 1/1 0 Running 10.244.0.4 │
305+
│ solo-setup minio-operator-7d575c5f84-j9p6f ● 1/1 0 Running 10.244.0.3 │
306306
│ kube-system coredns-5d78c9869d-gknqp ● 1/1 0 Running 10.244.0.6 │
307307
│ kube-system coredns-5d78c9869d-q59pc ● 1/1 0 Running 10.244.0.5 │
308308
│ kube-system etcd-solo-e2e-control-plane ● 1/1 0 Running 172.18.0.2 │
@@ -315,12 +315,12 @@ You may view the list of pods using `k9s` as below:
315315
│ solo envoy-proxy-node0-84947f844f-f28tp ● 1/1 0 Running 10.244.0.215 │
316316
│ solo envoy-proxy-node1-65f8879dcc-j2lrk ● 1/1 0 Running 10.244.0.216 │
317317
│ solo envoy-proxy-node2-667f848689-dkmf9 ● 1/1 0 Running 10.244.0.214 │
318-
│ solo fullstack-deployment-grpc-69f9cc5666-lf6ql ● 1/1 0 Running 10.244.0.227 │
319-
│ solo fullstack-deployment-hedera-explorer-79f79b7df4-wjdct ● 1/1 0 Running 10.244.0.226 │
320-
│ solo fullstack-deployment-importer-864489ffb8-6v8tk ● 1/1 0 Running 10.244.0.228 │
321-
│ solo fullstack-deployment-postgres-postgresql-0 ● 1/1 0 Running 10.244.0.232 │
322-
│ solo fullstack-deployment-rest-584f5cb6bb-q9vnt ● 1/1 0 Running 10.244.0.230 │
323-
│ solo fullstack-deployment-web3-69dcdfc4fb-mm5pk ● 1/1 0 Running 10.244.0.229 │
318+
│ solo solo-deployment-grpc-69f9cc5666-lf6ql ● 1/1 0 Running 10.244.0.227 │
319+
│ solo solo-deployment-hedera-explorer-79f79b7df4-wjdct ● 1/1 0 Running 10.244.0.226 │
320+
│ solo solo-deployment-importer-864489ffb8-6v8tk ● 1/1 0 Running 10.244.0.228 │
321+
│ solo solo-deployment-postgres-postgresql-0 ● 1/1 0 Running 10.244.0.232 │
322+
│ solo solo-deployment-rest-584f5cb6bb-q9vnt ● 1/1 0 Running 10.244.0.230 │
323+
│ solo solo-deployment-web3-69dcdfc4fb-mm5pk ● 1/1 0 Running 10.244.0.229 │
324324
│ solo haproxy-node0-6969f76c77-n5cfl ● 1/1 1 Running 10.244.0.219 │
325325
│ solo haproxy-node1-59f6976d45-x6xmp ● 1/1 1 Running 10.244.0.217 │
326326
│ solo haproxy-node2-6df64d5457-hf9ps ● 1/1 1 Running 10.244.0.218 │
@@ -338,7 +338,7 @@ Once the nodes are up, you may now expose various services (using `k9s` (shift-f
338338
Node services: `network-<node ID>-svc`\
339339
HAProxy: `haproxy-<node ID>-svc`\
340340
Envoy Proxy: `envoy-proxy-<node ID>-svc`\
341-
Hedera explorer: `fullstack-deployment-hedera-explorer`\
341+
Hedera explorer: `solo-deployment-hedera-explorer`\
342342
JSON Rpc Relays\
343343
You can deploy JSON RPC relays for one or more nodes as below:
344344

‎examples/custom-network-config/Taskfile.yml

+3-3
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ env:
88
FST_CHART_VERSION: v0.30.0
99
CONSENSUS_NODE_VERSION: v0.54.1
1010
SOLO_NAMESPACE: solo-{{ env "USER" | replace "." "-" | trunc 63 }}
11-
SOLO_CLUSTER_SETUP_NAMESPACE: fullstack-setup
11+
SOLO_CLUSTER_SETUP_NAMESPACE: solo-setup
1212
SOLO_NETWORK_SIZE: 7
1313

1414
vars:
@@ -104,7 +104,7 @@ tasks:
104104
solo:network:deploy:
105105
internal: true
106106
cmds:
107-
- solo network deploy --release-tag "${CONSENSUS_NODE_VERSION}" --fst-chart-version "${FST_CHART_VERSION}" --values-file {{ .solo_values_file }} --settings-txt {{ .solo_settings_file }}
107+
- solo network deploy --release-tag "${CONSENSUS_NODE_VERSION}" --solo-chart-version "${FST_CHART_VERSION}" --values-file {{ .solo_values_file }} --settings-txt {{ .solo_settings_file }}
108108
- solo node setup --release-tag "${CONSENSUS_NODE_VERSION}"
109109

110110
solo:network:destroy:
@@ -126,7 +126,7 @@ tasks:
126126
solo:node:addresses:
127127
internal: true
128128
cmds:
129-
- kubectl get svc -n "${SOLO_NAMESPACE}" -l "fullstack.hedera.com/type=network-node-svc" --output=go-template-file={{ .ip_list_template_file }}
129+
- kubectl get svc -n "${SOLO_NAMESPACE}" -l "solo.hedera.com/type=network-node-svc" --output=go-template-file={{ .ip_list_template_file }}
130130

131131
solo:cache:remove:
132132
internal: true

‎package.json

+2-2
Original file line numberDiff line numberDiff line change
@@ -36,8 +36,8 @@
3636
},
3737
"keywords": [
3838
"solo",
39-
"full-stack-testing",
40-
"fullstack-network-manager"
39+
"solo-charts",
40+
"solo-network-manager"
4141
],
4242
"author": "Swirlds Labs",
4343
"license": "Apache2.0",

0 commit comments

Comments
 (0)