Cloud and the Service Catalog

I haven't blogged in quite some time. I was looking around at some of my old blogs and wondered if my account was still active. As you can see, I was able to log in. I figured, what the heck, why not do a blog... here you go!

I've been doing a lot of work around the cloud over the past couple years, both public and private. I've found that the Customers are driving towards a portal that has their Service Catalog presented to end users so they can pick and choose the supported Services that IT provides. Companies tend to have some variations of their Service Catalog, it could be something as simple as provisioning a generic server with an Operating System installed or maybe it is preloaded with some applications like Apache or mySQL, or even a full blown Service Offering like a Project Tracking System, an Email Server, the company approved Intranet Website, etc, etc, etc.

The Customers still have all kinds of rules of what can be provisioned to the Cloud, which instances need to be provisioned to the Private Cloud and which are eligible to go to the Public Cloud. Regardless of what is provisioned or where it is provisioned, IT is still responsible for monitoring and supporting the instances. It still comes down to the same things we have talked about in these blogs over the years, agent, or agent-less, monitor up/down, or real time responses, watch log files, or run synthetic tests against an application. IT still needs real-time visibility and a way to prioritize performance issues, outages or general errors coming from an application.

I still see Customers needing multiple tools to do multiple tasks and all those tools, along with processes, working together to not only provision new services quickly and reliably, but also maintain and monitor the enterprise.

I hope all is well with my readers, feel free to click on my name to send me a message, maybe even request a blog article when I have some free time.

- Tobin


How To-Best Practice
Comment List
Related Discussions