9 results found
-
Apply maintenance in a lower level environment before promoting to production
As a customer, I want the ability to designate non-production systems as the primary target for updates, patches, and upgrades, so I can test them in my process before pushing them to production.
22 votes -
Improve service notifications
As a customer, I want system service notifications to be provided through alternative mechanisms, e.g., webhooks, API, console notifications, etc., as the current system of email notifications often go unnoticed or get caught in spam filters, and we are caught unprepared.
15 votes -
On demand rolling restart of services
As an Aiven customer
I want to be able to trigger a rolling restart of my service
So that I can recover from or troubleshoot potential issues7 votes -
LTS editions
As a product owner of Aiven services
I want to be able to select Long term support versions of the Aiven products
so that I can have the upgrade cycles match those of my other products without having to request exceptions when End of life warnings start appearing
In addition, I'd like to be able to made aware of any maintainence done to my clusters if they are in anyway destructive.6 votesAlthough this sounds reasonable in practice and many Linux distributions follow this, the projects we run at Aiven do not. So we are unable to build secured versions of open-source projects for long-term support. This would require an immense amount of engineering to maintain legacy versions of these 11 open-source projects. We also run Linux infrastructure, which is not part of the LTS model, so this would be yet another issue with the idea of LTS. If you'd like to discuss more, I am happy to speak with you.
-
Improve visibility on maintenance updates
As a user, I would like to have more granular details on what is included in updates and get an estimation on how long the maintenance period would be on my service and what would be the impact, if any temporary scale up of service is required during maintenance update
4 votes -
Allow for greater maintenance schedule flexibility.
Allow for greater maintenance schedule flexibility.
As a customer, I want to schedule maintenance to my services with a fixed calendar schedule rather then a weekly schedule. This is because I am required to only apply maintenance to my systems based on contracted schedules with my end customers. For example, I want to be able to schedule maintenance to occur on the 20th of each month. Or every 3rd Friday of the month between a certain window of time.
3 votes -
Separate Version Hold vs Maintenance Hold
As a customer, I want to ensure that my version of service is not auto-incremented on the Major.Minor release number as I have client code that connects to it. Thus, there needs to be a separate of maintenance and version upgrade that is separate. I still want maintenance to occur on my account (i.e. patching for security), yet I need the service version to remain the same.
2 votes -
Apply Aiven configuration and service updates during scheduled maintenance windows
As a customer, I want the ability to designate non-urgent configuration and service updates to be implemented only during scheduled maintenance windows, so I can limit the risk of updates running outside of these windows, and impacting the availability of production systems.
2 votes -
Links to release notes with version update notices
As an engineer
I want to see links to release notes of updating software when applying maintenance
so that I can quickly find out all the changes that are being applied and understand their relevancy to meSpecifically when using the console I can see links to all release notes, rather than a generic notice that my service is being updated to a specific version.
1 vote
- Don't see your idea?