Stein Series Release Notes¶
Added new tool
zaqar-status upgrade check.
Add an new option named ‘message_delete_with_claim_id’, when it is True, delete messages must need claim_ids and message_ids both in request parameters. This will improve the security of the message.
Currently the email subscription in Zaqar relay on the third part tools, such as “sendmail”. It means that deployer should install it out of Zaqar. If he forgets, Zaqar will raise internal error. This work let Zaqar support email subscription by itself using the
Introduce a new resource called Topic into Zaqar. Topic is a concept from AWS Simple Notification Service (SNS), it will has relevance with subscriptions. User can send message to a topic, and then the subscribers will get the message according to different protocols, like http, email, sms, etc. This feature will help Zaqar to split Messaging Queue Service and Notification Service clearly.
In Queens, we support the old way to use pool_group and the new way without it in Flavor both. In Stein, we will remove the pool_group totally and only keep the new way in Flavor and Pool.
New framework for
zaqar-status upgrade checkcommand is added. This framework allows adding various checks which can be run before a Zaqar upgrade to ensure if the upgrade can be performed safely.
Operator can now use new CLI tool
zaqar-status upgrade checkto check if Zaqar deployment can be safely upgraded from N-1 to N release.