Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -116,6 +116,12 @@ test: ## Run smoke tests
./scripts/helm-deploy.sh test -r $(RELEASE_NAME) -n $(NAMESPACE)
$(call log_success,"Tests completed successfully")

.PHONY: validate-init
validate-init: ## Validate Accumulo initialization with Alluxio
$(call log_info,"Validating Accumulo initialization...")
./scripts/validate-accumulo-init.sh $(RELEASE_NAME) $(NAMESPACE)
$(call log_success,"Validation completed")

.PHONY: status
status: ## Show deployment status
./scripts/helm-deploy.sh status -r $(RELEASE_NAME) -n $(NAMESPACE)
Expand Down
33 changes: 30 additions & 3 deletions charts/accumulo/DEPLOYMENT.md
Original file line number Diff line number Diff line change
Expand Up @@ -122,7 +122,27 @@ helm install accumulo-dev ./charts/accumulo \
kubectl wait --for=condition=Ready pod --all --timeout=600s
```

### 3. Run Smoke Tests
### 3. Validate Initialization

Before running tests, validate that Accumulo initialized correctly with Alluxio:

```bash
# Run the validation script
./scripts/validate-accumulo-init.sh accumulo-dev default

# Or use the Makefile target
make validate-init RELEASE_NAME=accumulo-dev
```

The validation script checks:
- All pods are running (ZooKeeper, Alluxio, Accumulo components)
- Services have endpoints
- Alluxio Master is accessible
- Accumulo instance is properly initialized in ZooKeeper
- Accumulo data directories exist in Alluxio filesystem
- Alluxio client libraries are available

### 4. Run Smoke Tests

```bash
# Run the built-in smoke tests
Expand All @@ -132,7 +152,14 @@ helm test accumulo-dev
kubectl logs accumulo-dev-smoke-test
```

### 4. Access Services
The smoke tests validate:
- All services are accessible (ZooKeeper, Alluxio, Accumulo)
- Accumulo table operations work correctly
- Data can be written and read from Alluxio
- Alluxio filesystem integration is functional
- Monitor web interface is available

### 5. Access Services

```bash
# Access Accumulo Monitor (web UI)
Expand All @@ -148,7 +175,7 @@ kubectl port-forward svc/accumulo-dev-minio 9001:9001 &
echo "MinIO Console: http://localhost:9001 (minioadmin/minioadmin)"
```

### 5. Connect with Accumulo Shell
### 6. Connect with Accumulo Shell

```bash
# Get a shell into the manager pod
Expand Down
24 changes: 22 additions & 2 deletions charts/accumulo/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -231,6 +231,25 @@ curl http://localhost:19999/
kubectl exec -it deployment/accumulo-manager -- /opt/accumulo/bin/accumulo shell -u root
```

### Initialization Validation

Validate that Accumulo initialized correctly with Alluxio:

```bash
# Using the validation script
./scripts/validate-accumulo-init.sh <release-name> <namespace>

# Or using Make
make validate-init RELEASE_NAME=<release-name> NAMESPACE=<namespace>
```

The validation checks:
- All pods and services are running
- Alluxio Master is accessible and serving
- Accumulo instance is initialized in ZooKeeper
- Accumulo data directories exist in Alluxio
- Alluxio client integration is working

### Smoke Tests

Run the built-in smoke tests to validate deployment:
Expand All @@ -241,8 +260,9 @@ helm test <release-name>

The smoke test validates:
- All services are accessible
- Accumulo table operations work
- Alluxio integration is functional
- Accumulo table operations work correctly
- Data persistence through Alluxio
- Alluxio filesystem integration
- Monitor web interface is available

## Upgrade Guide
Expand Down
Loading