Some standing reservations have immeasurable value. Date night with your spouse. Game day with your kids. If you travel frequently you may have a favorite airplane seat or favorite car rental type that you consistently try to reserve. Maybe even a standing lunch or dinner reservation. These types of reservations are beneficial for family, social and business relationships.
But.
Persistent Reservations in the Cloud Computing context offer limited utility. They go by a handful of names; Reserved Instances, Reserved Pools, Standby Capacity, etc. The names are used to describe a portion of your aggregate resource pool that is in a warm-idle state – essentially, waiting for you to have a defined use. It could be for burst/surge capacity, it could be in the context of COOP/DR , support of a periodic batch job or even as part of a Q/A cycle. We all have these type of workloads but if you are leveraging resource reservations to tackle them – consider the alternative – building your application to scale and workload sizing. Given the austere condition of budgets – resources without a defined purpose need to go.
Supply side Vendors, love, love, this model because it allows them to monetize a portion of their infrastructure that would otherwise be without commitment. The expense line to manage them is some small number over zero and the likelihood of you calling on their use is some other number slightly over zero. I think about it almost like one of those insurance premiums you do not really need but continue buying on a yearly basis because it was always included in your binder even though you never knew what it was.
Consider having an open dialogue with your procurement partners about why you have the resource reservations and how often have they been leveraged in the previous calendar year. My guess is not very often. The inspection – I think will lead you down one of two different paths. Either the application that leverages the persistent reservation was not sized correctly or there was a rouge IT project that claimed use of the resource.
Claim it back. Work on sizing the application properly. Tools to help in this regard are plentiful.
That is Anthony Bourdain saying “No Reservations” … No I do not know why he is covered in mud looking like a zombie. I just happen to like the show and tried to get a reservation at his place in NYC recently…..
Filed under: Uncategorized | Tagged: Acqusition, Anthony Bourdain, cloud, Government cloud, Persistent Reservations, Reserved Instances | Leave a Comment »






