Lab Registration Request - MEDOS_LAVA (GE Healthcare)

# KernelCI Lab Registration Request

## Lab Information
- **Lab Name:** MEDOS_LAVA
- **Organization:** GE Healthcare
- **Contact:** HarshaR.Gowda@gehealthcare.com
- **Lab Type:** LAVA 2019.12

## Connection Details
- **URL:** http://10.184.192.249:8080 (local network)
- **RPC Endpoint:** http://10.184.192.249:8080/RPC2/
- **Username:** kernelci-prod
Authentication:
A dedicated RPC token for the 'kernelci-prod' user will be shared privately upon request.

## Infrastructure
- **Device Type:** Atlanta
- **Architecture:** arm64
- **Quantity:** 1
- **Status:** Operational and tested

## Test Capabilities
- ✅ **kselftests** - Full suite available at http://10.184.192.249:8080/static/k.tgz
- ✅ **Boot tests** - Basic kernel boot validation
- ✅ **24/7 availability**
- ✅ **Estimated capacity:** 50-100 jobs/day

## Network Configuration
**Current Status:** Local network (behind NAT)

**Public Access Options:**
1. Working on direct public IP with port forwarding
2. Can provide VPN/SSH tunnel access for integration
3. Investigating ngrok/Cloudflare tunnel solutions

**Timeline:** Public access expected within 1-2 weeks

**Alternative:** Can provide secure VPN or SSH tunnel access to KernelCI team for immediate integration testing.

## Technical Details
- Successfully executed full kselftests suite (~22 minutes)
- All test results captured in TAP format
- Device configured with auto-login
- Result callbacks ready to be configured

## Integration Readiness
- ✅ LAVA server operational
- ✅ Device configured and tested
- ✅ Test resources deployed
- ✅ Authentication configured
- ⏳ Public URL setup in progress

## Next Steps
1. Complete public access configuration
2. Receive KernelCI API credentials
3. Configure result callbacks
4. Begin integration testing

## Contact
- **Email:** HarshaR.Gowda@gehealthcare.com
- **Timezone:** Asia/Kolkata (UTC+5:30)
- **Available for:** Setup calls, integration testing, troubleshooting

---

**Submitted:** $(date)
**Status:** Ready for integration (pending public access)

Start with the lab registration details in this issue, especially the LAVA RPC endpoint, device type, kselftests capability, and network-access status. Confirm public or secure access, then follow the listed integration steps for API credentials, result callbacks, and integration testing; done means the lab is reachable and submitting results.

Written by the indexing model from the issue text.