further rebranding from fst --> solo

Signed-off-by: instamenta <[email protected]>

.github/workflows/script/relay_smoke_test.sh

@@ -12,7 +12,7 @@ solo mirror-node deploy
 solo relay deploy -i node1
 kubectl port-forward svc/relay-node1-hedera-json-rpc-relay -n solo-e2e 7546:7546 &
 kubectl port-forward svc/haproxy-node1-svc -n solo-e2e 50211:50211 &
-kubectl port-forward svc/fullstack-deployment-hedera-explorer -n solo-e2e 8080:80 &
+kubectl port-forward svc/solo-deployment-hedera-explorer -n solo-e2e 8080:80 &
 
 echo "Clone hedera local node"
 

README.md

@@ -107,8 +107,8 @@ You may now view pods in your cluster using `k9s -A` as below:
  MEM: n/a
 ┌───────────────────────────────────────────────── Pods(all)[11] ─────────────────────────────────────────────────┐
 │ NAMESPACE↑ NAME PF READY STATUS RESTARTS IP NODE │
-│ fullstack-setup console-557956d575-4r5xm ● 1/1 Running 0 10.244.0.5 solo-con │
-│ fullstack-setup minio-operator-7d575c5f84-8shc9 ● 1/1 Running 0 10.244.0.6 solo-con │
+│ solo-setup console-557956d575-4r5xm ● 1/1 Running 0 10.244.0.5 solo-con │
+│ solo-setup minio-operator-7d575c5f84-8shc9 ● 1/1 Running 0 10.244.0.6 solo-con │
 │ kube-system coredns-5d78c9869d-6cfbg ● 1/1 Running 0 10.244.0.4 solo-con │
 │ kube-system coredns-5d78c9869d-gxcjz ● 1/1 Running 0 10.244.0.3 solo-con │
 │ kube-system etcd-solo-control-plane ● 1/1 Running 0 172.18.0.2 solo-con │
@@ -212,7 +212,7 @@ Kubernetes Namespace : solo
 **********************************************************************************
 ✔ Initialize
 ✔ Prepare chart values
-✔ Install 'fullstack-cluster-setup' chart
+✔ Install 'solo-cluster-setup' chart
 ```
 
 In a separate terminal, you may run `k9s` to view the pod status.
@@ -247,7 +247,7 @@ Kubernetes Namespace : solo
 ✔ Copy Gossip keys
 ✔ Node: node3
 ✔ Copy node keys to secrets
-✔ Install chart 'fullstack-deployment'
+✔ Install chart 'solo-deployment'
 ✔ Check Node: node1
 ✔ Check Node: node2
 ✔ Check Node: node3
@@ -411,15 +411,15 @@ Context: kind-solo <0> all <a> Attach
 │ solo envoy-proxy-node1-65f8879dcc-rwg97 ● 1/1 Running 0 1 │
 │ solo envoy-proxy-node2-667f848689-628cx ● 1/1 Running 0 1 │
 │ solo envoy-proxy-node3-6bb4b4cbdf-dmwtr ● 1/1 Running 0 1 │
-│ solo fullstack-deployment-grpc-75bb9c6c55-l7kvt ● 1/1 Running 0 1 │
-│ solo fullstack-deployment-hedera-explorer-6565ccb4cb-9dbw2 ● 1/1 Running 0 1 │
-│ solo fullstack-deployment-importer-dd74fd466-vs4mb ● 1/1 Running 0 1 │
-│ solo fullstack-deployment-monitor-54b8f57db9-fn5qq ● 1/1 Running 0 1 │
-│ solo fullstack-deployment-postgres-postgresql-0 ● 1/1 Running 0 1 │
-│ solo fullstack-deployment-redis-node-0 ● 2/2 Running 0 1 │
-│ solo fullstack-deployment-rest-6d48f8dbfc-plbp2 ● 1/1 Running 0 1 │
-│ solo fullstack-deployment-restjava-5d6c4cb648-r597f ● 1/1 Running 0 1 │
-│ solo fullstack-deployment-web3-55fdfbc7f7-lzhfl ● 1/1 Running 0 1 │
+│ solo solo-deployment-grpc-75bb9c6c55-l7kvt ● 1/1 Running 0 1 │
+│ solo solo-deployment-hedera-explorer-6565ccb4cb-9dbw2 ● 1/1 Running 0 1 │
+│ solo solo-deployment-importer-dd74fd466-vs4mb ● 1/1 Running 0 1 │
+│ solo solo-deployment-monitor-54b8f57db9-fn5qq ● 1/1 Running 0 1 │
+│ solo solo-deployment-postgres-postgresql-0 ● 1/1 Running 0 1 │
+│ solo solo-deployment-redis-node-0 ● 2/2 Running 0 1 │
+│ solo solo-deployment-rest-6d48f8dbfc-plbp2 ● 1/1 Running 0 1 │
+│ solo solo-deployment-restjava-5d6c4cb648-r597f ● 1/1 Running 0 1 │
+│ solo solo-deployment-web3-55fdfbc7f7-lzhfl ● 1/1 Running 0 1 │
 │ solo haproxy-node1-785b9b6f9b-676mr ● 1/1 Running 1 1 │
 │ solo haproxy-node2-644b8c76d-v9mg6 ● 1/1 Running 1 1 │
 │ 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
 * Node services: `network-<node ID>-svc`
 * HAProxy: `haproxy-<node ID>-svc`
 * Envoy Proxy: `envoy-proxy-<node ID>-svc`
-* Hedera explorer: `fullstack-deployment-hedera-explorer`
+* Hedera explorer: `solo-deployment-hedera-explorer`
 * JSON Rpc Relays
  * You can deploy JSON RPC relays for one or more nodes as below:
  ```

README.md.template

@@ -95,8 +95,8 @@ You may now view pods in your cluster using `k9s -A` as below:
  MEM: n/a
 ┌───────────────────────────────────────────────── Pods(all)[11] ─────────────────────────────────────────────────┐
 │ NAMESPACE↑ NAME PF READY STATUS RESTARTS IP NODE │
-│ fullstack-setup console-557956d575-4r5xm ● 1/1 Running 0 10.244.0.5 solo-con │
-│ fullstack-setup minio-operator-7d575c5f84-8shc9 ● 1/1 Running 0 10.244.0.6 solo-con │
+│ solo-setup console-557956d575-4r5xm ● 1/1 Running 0 10.244.0.5 solo-con │
+│ solo-setup minio-operator-7d575c5f84-8shc9 ● 1/1 Running 0 10.244.0.6 solo-con │
 │ kube-system coredns-5d78c9869d-6cfbg ● 1/1 Running 0 10.244.0.4 solo-con │
 │ kube-system coredns-5d78c9869d-gxcjz ● 1/1 Running 0 10.244.0.3 solo-con │
 │ 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
 │ solo envoy-proxy-node1-65f8879dcc-rwg97 ● 1/1 Running 0 1 │
 │ solo envoy-proxy-node2-667f848689-628cx ● 1/1 Running 0 1 │
 │ solo envoy-proxy-node3-6bb4b4cbdf-dmwtr ● 1/1 Running 0 1 │
-│ solo fullstack-deployment-grpc-75bb9c6c55-l7kvt ● 1/1 Running 0 1 │
-│ solo fullstack-deployment-hedera-explorer-6565ccb4cb-9dbw2 ● 1/1 Running 0 1 │
-│ solo fullstack-deployment-importer-dd74fd466-vs4mb ● 1/1 Running 0 1 │
-│ solo fullstack-deployment-monitor-54b8f57db9-fn5qq ● 1/1 Running 0 1 │
-│ solo fullstack-deployment-postgres-postgresql-0 ● 1/1 Running 0 1 │
-│ solo fullstack-deployment-redis-node-0 ● 2/2 Running 0 1 │
-│ solo fullstack-deployment-rest-6d48f8dbfc-plbp2 ● 1/1 Running 0 1 │
-│ solo fullstack-deployment-restjava-5d6c4cb648-r597f ● 1/1 Running 0 1 │
-│ solo fullstack-deployment-web3-55fdfbc7f7-lzhfl ● 1/1 Running 0 1 │
+│ solo solo-deployment-grpc-75bb9c6c55-l7kvt ● 1/1 Running 0 1 │
+│ solo solo-deployment-hedera-explorer-6565ccb4cb-9dbw2 ● 1/1 Running 0 1 │
+│ solo solo-deployment-importer-dd74fd466-vs4mb ● 1/1 Running 0 1 │
+│ solo solo-deployment-monitor-54b8f57db9-fn5qq ● 1/1 Running 0 1 │
+│ solo solo-deployment-postgres-postgresql-0 ● 1/1 Running 0 1 │
+│ solo solo-deployment-redis-node-0 ● 2/2 Running 0 1 │
+│ solo solo-deployment-rest-6d48f8dbfc-plbp2 ● 1/1 Running 0 1 │
+│ solo solo-deployment-restjava-5d6c4cb648-r597f ● 1/1 Running 0 1 │
+│ solo solo-deployment-web3-55fdfbc7f7-lzhfl ● 1/1 Running 0 1 │
 │ solo haproxy-node1-785b9b6f9b-676mr ● 1/1 Running 1 1 │
 │ solo haproxy-node2-644b8c76d-v9mg6 ● 1/1 Running 1 1 │
 │ 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
  kubectl port-forward svc/envoy-proxy-node2-svc -n "${SOLO_NAMESPACE}" 8281:8080 &
  kubectl port-forward svc/envoy-proxy-node3-svc -n "${SOLO_NAMESPACE}" 8381:8080 &
  ```
-* Hedera explorer: `fullstack-deployment-hedera-explorer`
+* Hedera explorer: `solo-deployment-hedera-explorer`
  ```bash
  #enable portforwarding for hedera explorer, can be access at http://localhost:8080/
- kubectl port-forward svc/fullstack-deployment-hedera-explorer -n "${SOLO_NAMESPACE}" 8080:80 &
+ kubectl port-forward svc/solo-deployment-hedera-explorer -n "${SOLO_NAMESPACE}" 8080:80 &
  ```
 * JSON Rpc Relays
  * You can deploy JSON RPC relays for one or more nodes as below:

docs/content/getting-started/deploy.md

@@ -104,7 +104,7 @@ Kubernetes Namespace : solo
 **********************************************************************************
 ✔ Initialize
 ✔ Prepare chart values
-✔ Install 'fullstack-cluster-setup' chart
+✔ Install 'solo-cluster-setup' chart
 
 ```
 
@@ -128,7 +128,7 @@ Kubernetes Cluster : kind-solo
 Kubernetes Namespace : solo
 **********************************************************************************
 ✔ Initialize
-✔ Install chart 'fullstack-deployment'
+✔ Install chart 'solo-deployment'
 ✔ Check Node: node0
 ✔ Check Node: node1
 ✔ Check Node: node2
@@ -301,8 +301,8 @@ You may view the list of pods using `k9s` as below:
  MEM: n/a
 ┌─────────────────────────────────────────────────── Pods(all)[27] ────────────────────────────────────────────────────┐
 │ NAMESPACE↑ NAME PF READY RESTARTS STATUS IP │
-│ fullstack-setup console-557956d575-fqctd ● 1/1 0 Running 10.244.0.4 │
-│ fullstack-setup minio-operator-7d575c5f84-j9p6f ● 1/1 0 Running 10.244.0.3 │
+│ solo-setup console-557956d575-fqctd ● 1/1 0 Running 10.244.0.4 │
+│ solo-setup minio-operator-7d575c5f84-j9p6f ● 1/1 0 Running 10.244.0.3 │
 │ kube-system coredns-5d78c9869d-gknqp ● 1/1 0 Running 10.244.0.6 │
 │ kube-system coredns-5d78c9869d-q59pc ● 1/1 0 Running 10.244.0.5 │
 │ 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:
 │ solo envoy-proxy-node0-84947f844f-f28tp ● 1/1 0 Running 10.244.0.215 │
 │ solo envoy-proxy-node1-65f8879dcc-j2lrk ● 1/1 0 Running 10.244.0.216 │
 │ solo envoy-proxy-node2-667f848689-dkmf9 ● 1/1 0 Running 10.244.0.214 │
-│ solo fullstack-deployment-grpc-69f9cc5666-lf6ql ● 1/1 0 Running 10.244.0.227 │
-│ solo fullstack-deployment-hedera-explorer-79f79b7df4-wjdct ● 1/1 0 Running 10.244.0.226 │
-│ solo fullstack-deployment-importer-864489ffb8-6v8tk ● 1/1 0 Running 10.244.0.228 │
-│ solo fullstack-deployment-postgres-postgresql-0 ● 1/1 0 Running 10.244.0.232 │
-│ solo fullstack-deployment-rest-584f5cb6bb-q9vnt ● 1/1 0 Running 10.244.0.230 │
-│ solo fullstack-deployment-web3-69dcdfc4fb-mm5pk ● 1/1 0 Running 10.244.0.229 │
+│ solo solo-deployment-grpc-69f9cc5666-lf6ql ● 1/1 0 Running 10.244.0.227 │
+│ solo solo-deployment-hedera-explorer-79f79b7df4-wjdct ● 1/1 0 Running 10.244.0.226 │
+│ solo solo-deployment-importer-864489ffb8-6v8tk ● 1/1 0 Running 10.244.0.228 │
+│ solo solo-deployment-postgres-postgresql-0 ● 1/1 0 Running 10.244.0.232 │
+│ solo solo-deployment-rest-584f5cb6bb-q9vnt ● 1/1 0 Running 10.244.0.230 │
+│ solo solo-deployment-web3-69dcdfc4fb-mm5pk ● 1/1 0 Running 10.244.0.229 │
 │ solo haproxy-node0-6969f76c77-n5cfl ● 1/1 1 Running 10.244.0.219 │
 │ solo haproxy-node1-59f6976d45-x6xmp ● 1/1 1 Running 10.244.0.217 │
 │ 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
 Node services: `network-<node ID>-svc`\
 HAProxy: `haproxy-<node ID>-svc`\
 Envoy Proxy: `envoy-proxy-<node ID>-svc`\
-Hedera explorer: `fullstack-deployment-hedera-explorer`\
+Hedera explorer: `solo-deployment-hedera-explorer`\
 JSON Rpc Relays\
 You can deploy JSON RPC relays for one or more nodes as below:
 

package.json

@@ -35,8 +35,8 @@
  },
  "keywords": [
  "solo",
- "full-stack-testing",
- "fullstack-network-manager"
+ "solo-charts",
+ "solo-network-manager"
  ],
  "author": "Swirlds Labs",
  "license": "Apache2.0",

src/commands/account.mjs

@@ -173,7 +173,7 @@ export class AccountCommand extends BaseCommand {
  {
  title: 'Prepare for account key updates',
  task: async (ctx) => {
- const secrets = await self.k8.getSecretsByLabel(['fullstack.hedera.com/account-id'])
+ const secrets = await self.k8.getSecretsByLabel(['solo.hedera.com/account-id'])
  ctx.updateSecrets = secrets.length > 0
 
  ctx.accountsBatchedSet = self.accountManager.batchAccounts(this.systemAccounts)

src/commands/cluster.mjs

@@ -173,7 +173,7 @@ export class ClusterCommand extends BaseCommand {
  const confirm = await task.prompt(ListrEnquirerPromptAdapter).run({
  type: 'toggle',
  default: false,
- message: 'Are you sure you would like to uninstall fullstack-cluster-setup chart?'
+ message: 'Are you sure you would like to uninstall solo-cluster-setup chart?'
  })
 
  if (!confirm) {
@@ -231,7 +231,7 @@ export class ClusterCommand extends BaseCommand {
  }
  return {
  command: 'cluster',
- desc: 'Manage fullstack testing cluster',
+ desc: 'Manage solo testing cluster',
  builder: yargs => {
  return yargs
  .command({
@@ -335,7 +335,7 @@ export class ClusterCommand extends BaseCommand {
  ) {
  let valuesArg = ''
  if (chartDir) {
- valuesArg = `-f ${path.join(chartDir, 'fullstack-cluster-setup', 'values.yaml')}`
+ valuesArg = `-f ${path.join(chartDir, 'solo-cluster-setup', 'values.yaml')}`
  }
 
  valuesArg += ` --set cloud.prometheusStack.enabled=${prometheusStackEnabled}`
@@ -357,9 +357,9 @@ export class ClusterCommand extends BaseCommand {
  * @returns {Promise<string>}
  */
  async prepareChartPath (chartDir = flags.chartDirectory.definition.default) {
- let chartPath = 'full-stack-testing/fullstack-cluster-setup'
+ let chartPath = 'solo-charts/solo-cluster-setup'
  if (chartDir) {
- chartPath = path.join(chartDir, 'fullstack-cluster-setup')
+ chartPath = path.join(chartDir, 'solo-cluster-setup')
  await this.helm.dependency('update', chartPath)
  }
 

src/commands/flags.mjs

@@ -274,7 +274,7 @@ export const chartDirectory = {
  constName: 'chartDirectory',
  name: 'chart-dir',
  definition: {
- describe: 'Local chart directory path (e.g. ~/full-stack-testing/charts',
+ describe: 'Local chart directory path (e.g. ~/solo-charts/charts',
  defaultValue: '',
  alias: 'd',
  type: 'string'

src/commands/mirror_node.mjs

@@ -417,7 +417,7 @@ export class MirrorNodeCommand extends BaseCommand {
  task: async (ctx, _) => {
  const pvcs = await self.k8.listPvcsByNamespace(ctx.config.namespace, [
  'app.kubernetes.io/component=postgresql',
- 'app.kubernetes.io/instance=fullstack-deployment',
+ 'app.kubernetes.io/instance=solo-deployment',
  'app.kubernetes.io/name=postgres'
  ])