For those of you building out private cloud service stacks, one of the big questions is – how do I deal with release management? What happens when we retire an old version of the OS?
Here’s how Azure appears to be doing it. As of date X, you will no longer be able to deploy retired OS or manage existing versions. This makes sense, in a way. If you advertise the End of Support date in advance, it shouldn’t be a surprise when you are required to migrate away from the platform.
Ensure accountability for application currency resides with the business, but offer assistance with those migrations. Too often I think as infrastructure folks we stop at the message that the underlying infrastructure will be end of support, the application must be migrated. In the new IT economy where you need powerful differentiators to convince business executives to keep workloads internal, this could be powerful. Public cloud providers will not guide you in your migration to new Operating Systems/platforms. They will end support for the platform and move on.
Categories: private cloud
Infrastructure nerd learning to code and be a better human