Bump version

VERSION

@@ -1 +1 @@
-v1.0.33
+v1.0.34

api/v1alpha1/admission_cluster.go

@@ -51,6 +51,11 @@ func (in *Cluster) Default() {
 			schedule.StartingDeadlineSeconds = &DefaultStartingDeadlineSeconds
 		}
 	}
+
+	if in.Spec.DefaultDistributionSpec != nil {
+		in.Spec.DefaultDistributionSpec = &DistributionSpec{Name: DistributionUniform}
+	}
+
 	// TODO(user): fill in your defaulting logic.
 }
 

api/v1alpha1/type_labels.go

@@ -193,7 +193,7 @@ const (
 	PrometheusDiscoverablePort = "tel-"
 
 	// MainContainerName  is the main application that run the service. A service can be either "Main" or "Sidecar".
-	MainContainerName = "app"
+	MainContainerName = "main"
 )
 
 // ///////////////////////////////////////////

charts/databases/cockroachdb/examples/10.bitrot.yml

@@ -51,6 +51,6 @@ spec:
     # Teardown
     - action: Delete
       name: teardown
-      depends: { running: [ masters ], success: [ run-workload] }
+      depends: { running: [ masters ], success: [ run-workload ] }
       delete:
         jobs: [ masters ]

charts/databases/cockroachdb/examples/11.network.yml

@@ -62,6 +62,6 @@ spec:
     # Teardown
     - action: Delete
       name: teardown
-      depends: { running: [ masters ], success: [ partition0, run-workload] }
+      depends: { running: [ masters ], success: [ partition0, run-workload ] }
       delete:
         jobs: [ masters ]

charts/databases/cockroachdb/examples/12.bitrot-logs.yml

@@ -75,6 +75,6 @@ spec:
     # Teardown
     - action: Delete
       name: teardown
-      depends: { running: [ masters, dataviewer ], success: [ run-workload], after: 10m }
+      depends: { running: [ masters, dataviewer ], success: [ run-workload ], after: 10m }
       delete:
         jobs: [ masters, dataviewer ]

charts/databases/cockroachdb/examples/8.scaledown-stop.yml

@@ -64,6 +64,6 @@ spec:
     # Teardown
     - action: Delete
       name: teardown
-      depends: { success: [loader, stop-servers ] }
+      depends: { success: [ loader, stop-servers ] }
       delete:
         jobs: [ masters, more-servers ]

charts/databases/cockroachdb/examples/9.scaledown-kill.yml

@@ -64,6 +64,6 @@ spec:
     # Teardown
     - action: Delete
       name: teardown
-      depends: { success: [loader, killer ], running: [more-servers] }
+      depends: { success: [ loader, killer ], running: [ more-servers ] }
       delete:
         jobs: [ masters, more-servers ]

charts/databases/cockroachdb/templates/cluster.yml

@@ -15,7 +15,7 @@ spec:
         - cockroach.telemetry.server
 
     containers:
-      - name: app
+      - name: main
         image: cockroachdb/cockroach:v22.1.2
         ports:
           - name: grpc

charts/databases/cockroachdb/templates/single.yml

@@ -20,7 +20,7 @@ spec:
             cockroach node drain --insecure --host $(hostname)
 
     containers:
-      - name: app
+      - name: main
         image: cockroachdb/cockroach:v21.2.4
         ports:
           - name: grpc

charts/databases/cockroachdb/templates/telemetry.yml

@@ -16,9 +16,9 @@ spec:
           - name: tel-cock
             containerPort: 9443
         command:
-          - /bin/sh # Run shell
-          - -c # Read from string
-          - |  # Multi-line str
+          - /bin/sh   # Run shell
+          - -c        # Read from string
+          - |         # Multi-line str
             set -eum
 
             # Read metrics from one or many prometheus clients.

charts/databases/cockroachdb/templates/withlogger.yml

@@ -30,7 +30,7 @@ spec:
         command: [ "ls", "/logs" ]
 
     containers:
-      - name: app
+      - name: main
         image: cockroachdb/cockroach:latest
         volumeMounts: # Mount the log volume
           - name: logs

charts/databases/mongodb/examples/plan.baseline.replicated.yml

@@ -111,6 +111,6 @@ spec:
     # Teardown
     - action: Delete
       name: teardown
-      depends: { running: [ master, slaves], success: [ workload-e ] }
+      depends: { running: [ master, slaves ], success: [ workload-e ] }
       delete:
         jobs: [ master, slaves ]

charts/databases/mongodb/templates/cluster.yml

@@ -15,7 +15,7 @@ spec:
         - mongo.telemetry.server
 
     containers: # Container
-      - name: app
+      - name: main
         image: bitnami/mongodb
         ports:
           - name: to-clients
@@ -86,7 +86,7 @@ spec:
       telemetry: [ system.telemetry.agent, mongo.telemetry.server/telegraf ]
 
     containers: # Container
-      - name: app
+      - name: main
         image: bitnami/mongodb
         ports:
           - name: to-clients

charts/databases/redis/examples/10.availability-failover-single.yml

@@ -62,6 +62,6 @@ spec:
     # Teardown
     - action: Delete
       name: teardown
-      depends: { running: [master, slave, sentinel], success: [loaders, partition-b] }
+      depends: { running: [ master, slave, sentinel ], success: [ loaders, partition-b ] }
       delete:
-        jobs: [ master, slave, sentinel]
+        jobs: [ master, slave, sentinel ]

charts/databases/redis/examples/5.scaleup-scheduled.yml

@@ -48,6 +48,6 @@ spec:
     # Teardown
     - action: Delete
       name: teardown
-      depends: { running: [ masters, more-servers], success: [loader] }
+      depends: { running: [ masters, more-servers ], success: [ loader ] }
       delete:
         jobs: [ masters, more-servers ]

charts/databases/redis/examples/6.scaleup-conditional.yml

@@ -51,6 +51,6 @@ spec:
     # Teardown
     - action: Delete
       name: teardown
-      depends: { running: [ masters, more-servers], success: [loaders] }
+      depends: { running: [ masters, more-servers ], success: [ loaders ] }
       delete:
         jobs: [ masters, more-servers ]

charts/databases/redis/examples/8.scaledown-stop.yml

@@ -61,6 +61,6 @@ spec:
     # Teardown
     - action: Delete
       name: teardown
-      depends: { success: [loader, stop-servers ] }
+      depends: { success: [ loader, stop-servers ] }
       delete:
         jobs: [ masters, more-servers ]

charts/databases/redis/examples/9.scaledown-kill.yml

@@ -58,6 +58,6 @@ spec:
     # Teardown
     - action: Delete
       name: teardown
-      depends: { success: [loader, killer ], running: [more-servers] }
+      depends: { success: [ loader, killer ], running: [ more-servers ] }
       delete:
         jobs: [ masters, more-servers ]

charts/databases/redis/examples/README.md

@@ -77,7 +77,7 @@
 3) Run workload A sending traffic to a random node
 4) Scale-up the topology by adding new nodes
 5) Scale-down the topology by periodically **stopping** some nodes (run command within target container to drain the
-   node)
+node)
 
 #### **Observations**
 

charts/databases/redis/templates/cluster.yml

@@ -29,7 +29,7 @@ spec:
         - redis.telemetry.server
 
     containers: # Container
-      - name: app
+      - name: main
         image: redis
         ports:
           - name: to-clients
@@ -112,7 +112,7 @@ spec:
       delay: "0"
   service:
     containers:
-      - name: app
+      - name: main
         image: redis
         command:
           - /bin/bash   # Run shell

charts/databases/redis/templates/single.yml

@@ -9,7 +9,7 @@ spec:
       telemetry: [ system.telemetry.agent, redis.telemetry.server ]
 
     containers:
-      - name: app
+      - name: main
         image: redis
         ports:
           - name: to-clients
@@ -60,7 +60,7 @@ spec:
     decorators:
       telemetry: [ system.telemetry.agent, redis.telemetry.server ]
     containers:
-      - name: app
+      - name: main
         image: redis
         ports:
           - name: to-clients
@@ -111,7 +111,7 @@ spec:
       master: localhost
   service:
     containers:
-      - name: app
+      - name: main
         image: redis
         ports:
           - name: sentinel

charts/databases/tebis/README.md

@@ -4,7 +4,6 @@ This document focuses on setting up a development environment for the
 distributed of Tebis on a local machine.
 
 
-
 ## Build Tebis Containers
 
 
@@ -21,15 +20,13 @@ docker build -t icsforth/tebis-node . -f tebis.Dockerfile
 ```
 
 
-
 ## Set up Execution Environment
 
 Tebis uses RDMA for all network communication, which requires support from the
 network interface to run. A software implementation (soft-RoCE) exists and can
 run on all network interfaces.
 
 
-
 ### Install dependencies
 
 The `ibverbs-utils` and `rdma-core` packages are required to enable soft-RoCE.
@@ -39,7 +36,7 @@ These packages should be in most distirbutions' repositories.
 apt install ibverbs-utils rdma-core perftest
 ```
 
-#### 
+####
 
 ### Enabling soft-RoCE
 
@@ -67,7 +64,6 @@ link rxe0/1 state ACTIVE physical_state LINK_UP netdev eno1
 ```
 
 
-
 #### Verify soft-RoCE is working
 To verify that soft-RoCE is working, we can run a simple RDMA Write throuhgput
 benchmark.
@@ -86,15 +82,15 @@ Example output:
 ************************************
 ---------------------------------------------------------------------------------------
 RDMA_Write BW Test
-Dual-port       : OFF		Device         : rxe0
-Number of qps   : 1		Transport type : IB
-Connection type : RC		Using SRQ      : OFF
+Dual-port       : OFF        Device         : rxe0
+Number of qps   : 1        Transport type : IB
+Connection type : RC        Using SRQ      : OFF
 CQ Moderation   : 100
 Mtu             : 1024[B]
 Link type       : Ethernet
 GID index       : 1
 Max inline data : 0[B]
-rdma_cm QPs	 : OFF
+rdma_cm QPs     : OFF
 Data ex. method : Ethernet
 ---------------------------------------------------------------------------------------
 local address: LID 0000 QPN 0x0011 PSN 0x3341fd RKey 0x000204 VAddr 0x007f7e1b8fa000
@@ -103,24 +99,24 @@ remote address: LID 0000 QPN 0x0012 PSN 0xbfbac5 RKey 0x000308 VAddr 0x007f70f58
 GID: 00:00:00:00:00:00:00:00:00:00:255:255:192:168:122:205
 ---------------------------------------------------------------------------------------
 #bytes     #iterations    BW peak[MB/sec]    BW average[MB/sec]   MsgRate[Mpps]
-65536      5000             847.44             827.84 		   0.013245
+65536      5000             847.44             827.84           0.013245
 ---------------------------------------------------------------------------------------
 ```
 
 * Client process:
 ```
 ---------------------------------------------------------------------------------------
 RDMA_Write BW Test
-Dual-port       : OFF		Device         : rxe0
-Number of qps   : 1		Transport type : IB
-Connection type : RC		Using SRQ      : OFF
+Dual-port       : OFF        Device         : rxe0
+Number of qps   : 1        Transport type : IB
+Connection type : RC        Using SRQ      : OFF
 TX depth        : 128
 CQ Moderation   : 100
 Mtu             : 1024[B]
 Link type       : Ethernet
 GID index       : 1
 Max inline data : 0[B]
-rdma_cm QPs	 : OFF
+rdma_cm QPs     : OFF
 Data ex. method : Ethernet
 ---------------------------------------------------------------------------------------
 local address: LID 0000 QPN 0x0012 PSN 0xbfbac5 RKey 0x000308 VAddr 0x007f70f5843000
@@ -129,21 +125,17 @@ remote address: LID 0000 QPN 0x0011 PSN 0x3341fd RKey 0x000204 VAddr 0x007f7e1b8
 GID: 00:00:00:00:00:00:00:00:00:00:255:255:192:168:122:205
 ---------------------------------------------------------------------------------------
 #bytes     #iterations    BW peak[MB/sec]    BW average[MB/sec]   MsgRate[Mpps]
-65536      5000             847.44             827.84 		   0.013245
+65536      5000             847.44             827.84           0.013245
 ---------------------------------------------------------------------------------------
 ```
 
 
-
 ```shell
 server: ibv_rc_pingpong -d rxe0 -g 1
 client: ibv_rc_pingpong -d rxe0 -g 1 10.1.128.51
 ```
 
 
-
-
-
 ### Others
 
 
@@ -176,8 +168,4 @@ https://bbs.archlinux.org/viewtopic.php?id=273059
 https://ask.cyberinfrastructure.org/t/access-to-dev-infiniband-from-user-space/854/2
 
 
-
-
-
-
 ## Parameters

charts/databases/tebis/examples/normal-execution.yml

@@ -24,7 +24,7 @@ spec:
     # Initialize a data node
     - action: Cluster
       name: masters
-      depends: {running: [ zookeeper ], success: [ boot ]}
+      depends: { running: [ zookeeper ], success: [ boot ] }
       cluster:
         templateRef: tebis.cluster.master
         instances: 1
@@ -35,7 +35,7 @@ spec:
     # Initialize a client node
     - action: Service
       name: client
-      depends: { running: [zookeeper, masters], success: [boot] }
+      depends: { running: [ zookeeper, masters ], success: [ boot ] }
       service:
         templateRef: tebis.cluster.client
         inputs: