Hi!
Ganeti 3.0.0-rc1 is out! There are little external changes compared to
beta1, but a lot of work has gone into bringing master close to a final
release. You can find more details regarding the release in [1]. We
would like to than the following people for their work on -rc1:
Andre Liebigt (1):
Fix sphinx 'manpage' role
Apollon Oikonomopoulos (9):
Comply with Cabal 3.0 API changes
Use `cabal v1-configure' when supported
cabal: bump library version
CI: perform matrix builds on supported OSs
Perform nightly builds
Only run builds for PRs and pushes to master
htest: use printable unicode ByteStrings
Wrap overlong lines introduced since beta1
Release Ganeti 3.0.0-rc1
Daniel Howard (1):
Document gnt-instance add --tags
David Mohr (1):
Do not override disk_cache settings for RBD disks
Iustin Pop (5):
Update the NEWS entry regarding 2.17 situation
Note GHC 8.0+ is needed
GHC 8.8 + Debian unstable compatibility
Enable codeql security analysis
Update codeql-analysis.yml
Jun Futagawa (1):
Add support for pass *_ARGS to programs under systemd
Klaus Aehlig (3):
Add a constant for a new node-setup paramter
Add a function to extract the hmac key
Also ship the hmac key with the inital data
Kloppi313 (1):
gnt-node.rst typo
Marius Bakke (10):
Fix typos in
configure.ac.
Remove bridge-utils from installation instructions.
cabal: Relax QuickCheck version restriction.
Fix typo in ganeti-luxid man page.
Open vSwitch: Do not fail if the switch or port already exists.
Fix pygments highlighting in design-impext2.rst.
Fix typo in gnt-cluster man page.
Make gnt-cluster.8 manual page generation deterministic.
Expose disk size to OS install scripts.
Document all daemons in administrator guide.
Rudolph Bott (2):
Describe the 3.0 relase in a design document
Ship NEWS section for 3.0.0-rc1
Sascha Lucas (5):
fix typos in hbal man page
don't print double newline
fix various spelling/typos
don't expose RAPI to public w/o password
Fix docs by removing sphinx pre-1.3 support.
Vladimir Ipatov (1):
Fixes for DRBD >= 8.4.
There are only a couple of issues left to be resolved for 3.0 [2], none
of which is critical, so at this point it is important to do as much
real-world testing as possible. Remember that staging or development
cluster lying around? That's a good candidate to upgrade to 3.0 today :-)
Cheers,
Apollon
P.S: If all goes well, 3.0.0rc1 will make it to Debian unstable in the
following days.
[1]
https://github.com/ganeti/ganeti/releases/tag/v3.0.0rc1
[2]
https://github.com/ganeti/ganeti/milestone/25