Skip to content

Vyomi v2.1.0.1

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 22 Jun 23:47
v2.1.0.1
bdc6053

Windows-install hotfix on top of v2.1.0, from end-to-end validation on a Windows 10 Home / 8 GB / VirtualBox laptop. The appliance ran fully (all containers up), but three rough edges blocked or confused first-run; none touched the EC2/GCP compute 500 (still under investigation).

Fixed

  • Readiness gauge stuck at 52% (core/appliance_readiness.py). A half-finished cloudlearn-→vyomi- rename left five backend services (postgres, vault, elasticmq, pubsub, firestore) named cloudlearn-* in docker-compose.appliance.yml while the readiness prober dialed vyomi-*. Those five weigh exactly enough to peg the weighted gauge at 52%, and — because the progressive-startup gate reads the same probe — falsely blocked gated launches (e.g. RDS create) with "appliance still getting ready." The prober now resolves each backend host from the simulator's own canonical env (CLOUDLEARN_*_URL/_HOST, parsed via urlparse), so it follows real service names and can never drift out of sync again; literal defaults were also corrected.
  • Garbled access URL on VirtualBox-NAT hosts (Get-ApplianceIp). When the VM exposed only in-VM bridge IPs (docker0 172.17.0.1, lxdbr0 10.x.x.1), the fallback returned a bridge gateway, producing a dead netsh portproxy and a banner like http:///. The fallback now skips bridge-gateway addresses and returns empty when only NAT/bridge IPs exist, so the banner falls back to localhost.

Added

  • VirtualBox NAT port-forward for Windows Home (Set-VBoxNatPortForward in scripts/cloud-learn.ps1). On VirtualBox-NAT hosts the VM has no host-routable IP and is owned by the LocalSystem Multipass service, so localhost:9000 never reaches it. The launcher now best-effort adds a 127.0.0.1 NAT forward for 9000/9443; when the VM is SYSTEM-owned (the common case, which needs VBoxManage run as SYSTEM) it prints the exact, proven psexec -s … controlvm … natpf1 commands instead of leaving the user stranded. Non-fatal everywhere; Hyper-V hosts (no VBoxManage) skip it silently.

Artifacts

  • SHA256SUMS
  • cloud-learn-0.1.0.tar.gz
  • cloud-learn-2.1.0.1-1.noarch.rpm
  • cloud-learn-2.1.0.1-x64.msi
  • cloud-learn-2.1.0.1-x64.msi.sha256
  • cloud-learn-2.1.0.1.tar.gz
  • cloud-learn_2.1.0.1_all.deb

Docker image: docker pull vyomi/appliance:2.1.0.1
Install: curl -fsSL https://raw.githubusercontent.com/vyomi-cloud/appliance/main/install.sh | bash
SHA256 checksums: see SHA256SUMS in attached artifacts.

Assets 9
Loading