Releases: TheNewNormal/corectl
Releases · TheNewNormal/corectl
v0.7.5
- polish etcd and skydns integration
- we now make sure that there isn't another etcd running already on startup
- we now also properly wait for our etcd to be fully initalized before starting
consuming it - the macOS host is now exposed to the guests as corectld(.coreos.local)
- force VM names to be always rendered internally as lower case
- until now it was perfectly legitimate to have a VM named "FOO" and yet another
one named "foo". Now that we have proper name resolution builtin both would had been
rendered the exact same way due to DNS' case insensitiveness.
- until now it was perfectly legitimate to have a VM named "FOO" and yet another
v0.7.4
- etcd and skydns are now bundled into corectld.
- name based resolution of and across VMs now works
- together with the feature above embedded etcd can now be used for discovery and provisioning of VMs as it's data is persistent.
v0.7.3
- etcd and skydns are now bundled into corectld.
- name based resolution of and across VMs now works
- together with the feature above embedded etcd can now be used for discovery and provisioning of VMs as it's data is persistent.
v0.7.2
- etcd and skydns are now bundled into corectld.
- name based resolution of and across VMs now works
- together with the feature above embedded etcd can now be used for discovery and provisioning of VMs as it's data is persistent.
v0.7.1
- etcd and skydns are now bundled into corectld.
- name based resolution of and across VMs now works
- together with the feature above embedded etcd can now be used for discovery and provisioning of VMs as it's data is persistent.
v0.7.0
major refactoring based in users reporting and usage feedback …
major topics are:
- moved to a client (corectl) / server (corectld) with a fully refactored
network backend & api tooling - CoreOS VMs initial VM setup is now done through ignition
- plain pristine CoreOS images are now consumed
- VM initialization a now a little bit less noisy, and faster
- Docker's hyperkit is now used under the skin
- VM boot logs are now stored
- UUIDs are now stored in a consistent way (always in upper caps now)
- mounting host's homedir inside VMs via NFS is now optional and more
deterministic /etc/export
manipulation failures are now more verbose- as showing what was there before should be enough to understand
the root cause in most cases
- as showing what was there before should be enough to understand
- on halt we now actually wait for the VM(s) to be fully down
- improved tooling options
- to report if a running VM has connectivity to the outter world or not.
- to gracefully tell if a VM is running or not
- to report a VM's uuid
- we now block attemps to consume, on aggregate, more than 66% of
total system physical memory - sanitized source
- refactored Makefile for better resiliency
- refactored source structure in an hopefully more logical way
- all known data races (as reported by
go build -race
) handled - added a turn key etcd cluster template to the examples
v0.7.0-rc3
major refactoring based in users reporting and usage feedback …
major topics are:
- moved to a client (corectl) / server (corectld) with a fully refactored
network backend & api tooling - CoreOS VMs initial VM setup is now done through ignition
- plain pristine CoreOS images are now consumed
- VM initialization a now a little bit less noisy, and faster
- Docker's hyperkit is now used under the skin
- VM boot logs are now stored
- UUIDs are now stored in a consistent way (always in upper caps now)
- mounting host's homedir inside VMs via NFS is now optional and more
deterministic /etc/export
manipulation failures are now more verbose- as showing what was there before should be enough to understand
the root cause in most cases
- as showing what was there before should be enough to understand
- on halt we now actually wait for the VM(s) to be fully down
- improved tooling options
- to report if a running VM has connectivity to the outter world or not.
- to gracefully tell if a VM is running or not
- to report a VM's uuid
- we now block attemps to consume, on aggregate, more than 66% of
total system physical memory - sanitized source
- refactored Makefile for better resiliency
- refactored source structure in an hopefully more logical way
- all known data races (as reported by
go build -race
) handled - added a turn key etcd cluster template to the examples
v0.7.0-rc2
major refactoring based in users reporting and usage feedback …
major topics are:
- moved to a client (corectl) / server (corectld) with a fully refactored
network backend & api tooling - CoreOS VMs initial VM setup is now done through ignition
- plain pristine CoreOS images are now consumed
- VM initialization a now a little bit less noisy, and faster
- Docker's hyperkit is now used under the skin
- VM boot logs are now stored
- UUIDs are now stored in a consistent way (always in upper caps now)
- mounting host's homedir inside VMs via NFS is now optional and more
deterministic /etc/export
manipulation failures are now more verbose- as showing what was there before should be enough to understand
the root cause in most cases
- as showing what was there before should be enough to understand
- on halt we now actually wait for the VM(s) to be fully down
- improved tooling options
- to report if a running VM has connectivity to the outter world or not.
- to gracefully tell if a VM is running or not
- to report a VM's uuid
- we now block attemps to consume, on aggregate, more than 66% of
total system physical memory - sanitized source
- refactored Makefile for better resiliency
- refactored source structure in an hopefully more logical way
- all known data races (as reported by
go build -race
) handled - added a turn key etcd cluster template to the examples
v0.5.10
v0.5.9
- this release handles a corner case spotted by @jacobat and reported in IRC under which in certain conditions
running VMs weren't being correctly identified as such by switching to a better behaved/mantained go-ps library