77 lines
2.7 KiB
Markdown
77 lines
2.7 KiB
Markdown
|
# Remote Dashboard Deployment Summary
|
||
|
|
|
||
|
|
## Overview
|
||
|
|
Successfully deployed the Calejo Control Adapter dashboard to the remote server at `95.111.206.155` on port 8081.
|
||
|
|
|
||
|
|
## Deployment Status
|
||
|
|
|
||
|
|
### ✅ SUCCESSFULLY DEPLOYED
|
||
|
|
- **Remote Dashboard**: Running on `http://95.111.206.155:8081`
|
||
|
|
- **Health Check**: Accessible at `/health` endpoint
|
||
|
|
- **Service Status**: Healthy and running
|
||
|
|
- **SSH Access**: Working correctly
|
||
|
|
|
||
|
|
### 🔄 CURRENT SETUP
|
||
|
|
- **Existing Production**: Port 8080 (original Calejo Control Adapter)
|
||
|
|
- **Test Deployment**: Port 8081 (new dashboard deployment)
|
||
|
|
- **Mock Services**:
|
||
|
|
- Mock SCADA: `http://95.111.206.155:8083`
|
||
|
|
- Mock Optimizer: `http://95.111.206.155:8084`
|
||
|
|
|
||
|
|
## Key Achievements
|
||
|
|
|
||
|
|
1. **SSH Deployment**: Successfully deployed via SSH to remote server
|
||
|
|
2. **Container Configuration**: Fixed Docker command to use `python -m src.main`
|
||
|
|
3. **Port Configuration**: Test deployment running on port 8081 (mapped to container port 8080)
|
||
|
|
4. **Health Monitoring**: Health check endpoint working correctly
|
||
|
|
|
||
|
|
## Deployment Details
|
||
|
|
|
||
|
|
### Remote Server Information
|
||
|
|
- **Host**: `95.111.206.155`
|
||
|
|
- **SSH User**: `root`
|
||
|
|
- **SSH Key**: `deploy/keys/production_key`
|
||
|
|
- **Deployment Directory**: `/opt/calejo-control-adapter-test`
|
||
|
|
|
||
|
|
### Service Configuration
|
||
|
|
- **Container Name**: `calejo-control-adapter-test-app-1`
|
||
|
|
- **Port Mapping**: `8081:8080`
|
||
|
|
- **Health Check**: `curl -f http://localhost:8080/health`
|
||
|
|
- **Command**: `python -m src.main`
|
||
|
|
|
||
|
|
## Access URLs
|
||
|
|
|
||
|
|
- **Dashboard**: http://95.111.206.155:8081
|
||
|
|
- **Health Check**: http://95.111.206.155:8081/health
|
||
|
|
- **Existing Production**: http://95.111.206.155:8080
|
||
|
|
|
||
|
|
## Verification
|
||
|
|
|
||
|
|
All deployment checks passed:
|
||
|
|
- ✅ SSH connection established
|
||
|
|
- ✅ Docker container built and running
|
||
|
|
- ✅ Health endpoint accessible
|
||
|
|
- ✅ Service logs showing normal operation
|
||
|
|
- ✅ Port 8081 accessible from external
|
||
|
|
|
||
|
|
## Next Steps
|
||
|
|
|
||
|
|
1. **Test Discovery**: Verify the dashboard can discover remote services
|
||
|
|
2. **Protocol Mapping**: Test protocol mapping functionality
|
||
|
|
3. **Integration Testing**: Test end-to-end integration with mock services
|
||
|
|
4. **Production Deployment**: Consider deploying to production environment
|
||
|
|
|
||
|
|
## Files Modified
|
||
|
|
|
||
|
|
- `docker-compose.test.yml` - Fixed command and port configuration
|
||
|
|
|
||
|
|
## Deployment Scripts Used
|
||
|
|
|
||
|
|
- `deploy/ssh/deploy-remote.sh -e test` - Main deployment script
|
||
|
|
- Manual fixes for Docker command configuration
|
||
|
|
|
||
|
|
## Notes
|
||
|
|
|
||
|
|
- The deployment successfully resolved the issue where the container was trying to run `start_dashboard.py` instead of the correct `python -m src.main`
|
||
|
|
- The test deployment runs alongside the existing production instance without conflicts
|
||
|
|
- SSH deployment is now working correctly after the initial connection issues were resolved
|