Repository navigation
v0.2.1: Cluster mode on AWS
Features in v0.2.1
Highlights
- Cluster mode. Sandbox specs replicate, and a dead owner's sandboxes can be recovered by another node.
- AWS deploy. Terraform builds the cluster. Ansible installs sandboxd and joins a node.
- Leader election is fixed.
Cluster (#58, #79)
- sandboxd starts in a server, worker, or ingress role. On boot it replays the sandboxes it owns.
- Spec replication is what a non-owner needs to forward and to recover.
- A leader-election bug is fixed.
Deploy (#85, #86)
- Terraform for an AerolVM cluster on AWS: network, nodes, and the wiring those nodes boot with.
- Ansible for install, inventory, and node lifecycle.
- Scripts accept a node name so a host is not identified only by its address.
What's Changed
- feat(cluster): Distributed sandbox orchestration with spec replication and owner recovery by @sumansaurabh in #79
- feat(cluster): Distributed sandbox orchestration with spec replication and owner recovery by @sumansaurabh in #58
- feat: Add Terraform configuration for AerolVM cluster deployment on AWS by @sumansaurabh in #85
- Enhance AerolVM cluster management with Ansible, Terraform, and documentation by @sumansaurabh in #86
- feat: Enhance node identification with node-name support in scripts by @sumansaurabh in #87
- feat: fix the leader election bug by @sumansaurabh in #88
Full Changelog: v0.1.7...v0.2.1