[RPKI] Krill release 0.9.5-RC7 'Have You considered these Upgrades?'

[Tim Bruijnzeels]

Dear list, 

One month ago, we announced the RC2 release candidate of the coming Krill 
release 0.9.5 'Have You considered these Upgrades?'. 

The main focus of RC2 was to improve upgrades and facilitate clean roll-back in 
case an upgrade fails. We introduced a separate command line tool `krillup` 
which can be used to prepare and test a data migration while krill is running - 
reducing possible risk and downtime especially for installations with a lot of 
data. 

Despite our silence on this list, we have been busy testing and subsequently 
refining this code. We primarily focused on scalability for organisations that 
use Krill with more than 1000 co-hosted or remote delegated CAs. 

The current RC7 release candidate includes a number of additional improvements 
resulting from this effort: 

- Let CAs connect to local parent directly #791
- Decrease CA update frequency and use jitter to spread load #802
- Use a priority queue instead of a cronlike scheduler (PR #803) 

You can read the full release notes here:https:
//github.com/NLnetLabs/krill/releases/tag/v0.9.5-rc7 

We have upgraded our own production environments to this release candidate 
version. While we do not expect any further issues, we will leave it running 
for a full week before finalising 0.9.5 on Monday 4 April. 

If you should want to do further testing of your own then you can find binary 
packages for Debian and Ubuntu via the -proposed'distributions' (i.e., using 
bullseye-proposed rather than just bullseye) and via the proposed channel for 
RHEL 7 and 8 and compatible distributions. 

Please let us know if you find any issues, or if you have any questions or 
concerns. 

On behalf of the NLnet Labs RPKI Team, 


Tim