Archivo de la etiqueta: cloud

CIO Focus Interview: Stuart Appley, Shorenstein

octubre 15, 2014 GreenPages Blog

We’re starting a new CIO Focus Interview Series on the blog to get insights from some of the top thought leaders in the industry. For our first interview, I spoke with Stuart Appley, CIO at San Francisco based Shorenstein, to pick his brain about the current and future IT landscape. You can hear more from Stuart on Twitter.

CIO Focus Interview: Main Challenges

Ben: Could you give me a little background on your company as well as your role as CIO within the organization?

Stuart: Shorenstein is a real estate investment firm and owner and operators of commercial properties. Essentially, we act like a private equity firm by raising money from high net worth individuals. Instead of buying a company, we buy commercial buildings. We buy them and own and operate them for 10-15 years before selling them off and closing the fund. When we buy a building we typically manage it, so the other part of the business is being a property manager, investing in the property, doing redevelopment, etc. As CIO, I’m responsible for running the IT shop and IT’s long term strategic vision

Ben: What sort of unique challenges do you face as the CIO at your organization?

Stuart: A main challenge we face is that the company culture is a little older. This is something we are actively trying to change. We also have a diverse set of workers and a very distributed, mobile workforce. We have leasing agents out in the field, engineers checking equipment on the go, etc. Supporting the needs of this workforce is a challenge. I would say some of our users may not be as tech savvy as they are in other industries. We tend to hire a lot of senior level people, so our age base is a little higher than other companies. This makes it more difficult to get people to adopt technologies and bring them up to speed.

CIO Focus Interview: A look back at 2014

Ben: What was your main accomplishment in 2014 from an IT perspective?

Stuart: We just completed a large cloud ERP project. Doing this has allowed us to reduce a lot of application sets. This was a huge accomplishment because of the large amount of data and apps we have been moving in the cloud. Overall, the project, which lasted a little over a year, went smoothly.

Ben: How long have you been utilizing the cloud?

Stuart: 4-5 years, maybe even a little longer. Right now, we have 70% of our applications in the cloud. This includes LOBs apps that are standard, like Salesforce, and industry specific ones like Intralinks.

Ben: Did you have any pushback from the CEO, CFO or board of directors when you made the pitch to go cloud?

Stuart: No, it really wasn’t an issue with them. I was able to make the case that we should outsource things that we do not have a core competency in, and they were completely on board. Buy vs. Build.

CIO Focus Interview: Looking Ahead

Ben: What are you looking to accomplish in 2015?

Stuart: A main focus of ours is to rationalize cloud storage. We have a lot of content management systems right now – about 5-6. It’s time to rationalize that and get it down to 1-2. Another big focus we have is leveraging the beginning of a digital strategy we have been creating. For example, there are a lot of documents that need to be manually signed. We want to automate the signing of documents to save time and increase efficiency.

Ben: Anything else?

Stuart: We’re also going to review our data center and determine whether we want to move things to public clouds or private. We have listed out apps and services and plan to determine where each one would be the best fit. Finally, I want to continue to focus on mobility and try to push ease of access anywhere, anytime.

Ben: Throughout your career, what concept or technology would you say has had the most drastic impact on IT?

Stuart: I would say the idea of the consumerization of IT. This concept has transformed the whole industry. Users go home and use consumer apps and then carry those same expectations into the work place. In their mind, that ease of access should be available anywhere and everywhere across the board. To me, it’s a great thing for IT because it is forcing us to deliver. We have higher expectations and have a high bar to match.

Ben: How do you view IT?

Stuart: IT needs to be an advisor to the business. There is a lot of innovation that is happening with cloud vendors and we shouldn’t try to match that. The challenge is helping users understand that we support them going out and looking at other options. At the same time, we want them to come to us so we can let them know if there are any security concerns or if it will need to integrate with other apps that already exist in the environment. We need to be a consultant to the business and not a centralized just-say-no organization.

Are you a CIO/CTO interested in participating in our CIO Focus Interview series? Email me at bstephenson@greenpages.com

By Ben Stephenson, Emerging Media Specialist

Cloud computing, Featured

So You Want to Be a Cloud Architect? Part II

octubre 8, 2014 John Dixon

In Part I of this cloud architect series, we highlighted that business skills are at least as important as technical skills for the cloud architect. Here in Part II, we’ll propose three levels of cloud architect, describe the specific skills needed for each level, and make a suggestion on how to obtain these skills.

Levels of the Cloud Architect

At GreenPages, we think of three different levels of cloud architect. Through many client conversations, it has become clear that there are common perspectives on cloud:

Moving to cloud or “cloud as a bucket”
Cloud as a DevOps enabler, to take advantage of cutting edge development concepts
Cloud as a management paradigm, particularly to enable self-service and request management
A service rationalization strategy

So, the three levels of the cloud architect include the Integration, Developer, and Principal.

The Integration Architect has the ability to capture requirements, develop a bill of materials, and help an organization migrate their services to cloud providers. I’d want an integration Architect on staff to help me with a datacenter consolidation/modernization/rationalization project.
The Developer Architect builds on the skills of the Integration Architect and focuses on the ability to transform an organization’s development community to use cloud services efficiently. I’d want a Developer Architect on staff to take on a DevOps transformation project.
The Principal Architect builds on the Integration and Developer levels by focusing on improving the business’s ability to compete, through the use of cloud services (IaaS, PaaS, SaaS, XaaS) as well as the capabilities of cloud and DevOps. IT Service Portfolio skills are important here to understand an IT organization and what it does for the business as a consumer. Analysis and measurement of the business’s activities/processes/revenues/expenses is also important in this role. An individual in this role might lead a team of cloud architects to transform or build an entire business – perhaps a business that provides cloud services. Further, the individual in this role focuses on possibilities more than analysis of requirements.

{Download John’s eBook “The Evolution of Your Corporate IT Department“}

Training and Certification

So, which specific skills or certifications are needed for each level?

In a quick look at Coursera, I came across two courses, offered free of charge, that would be helpful for the cloud architect.

On a sidenote, I think Massive Open Online Courses (MOOCs) are a great thing and a nice use of cloud technology (the “flexible capacity” characteristic). Looking ahead, I expect that one would be able to obtain, from a MOOC, all of the training they need to become a cloud architect (amongst other things).

Available from a MOOC for $0.00

Microeconomics Principles, 8 Weeks
Programming for Everybody, 10 weeks

GreenPages certifies these levels of cloud architects by validating past certifications and industry experience. We also provide a training course to bring together the skills from various certifications and make them relevant for the cloud architect. Instead of needing to know the complete details of every aspect of these certifications, I think there are some core concepts that are highly applicable to the work of a cloud architect. Consider ITIL v3 in particular. While it is helpful to know how Incident and Problem Management processes work, the cloud architect absolutely needs to know the details of Service Strategy for one. Why? Not to understand which cloud services are available, but to help their organization develop their portfolio of IT services – some of which may be great candidates to source to a cloud service. On a related note, why are we hammering the idea that a cloud architect needs to have all of this business expertise? Well, once IT is defined in terms of the services it delivers, the cloud architect can then analyze that portfolio to identify which services provide the business with a competitive edge, and which services do not (I like to call the latter “commodity” services). The cloud architect may make sourcing recommendations based on this analysis. The table below lists the concepts from various certifications that are important for the cloud architect.

In Part III I’ll go into more depth on two things:

The training course that we provide to tie all of this together
The roles and responsibilities of a cloud architect

I’d love to hear your feedback on the role of the cloud architect, especially anything additional that you think the role needs to have. Leave comments below!

Cloud computing, Featured, Virtualization

So You Want to be a Cloud Architect? Part I

octubre 1, 2014 John Dixon

Lately, I’ve been taking a look at the role of a cloud architect. What does that role look like? How does one acquire the necessary skills? Where do aspiring cloud architects turn for training? Is it possible to acquire the skills to be an effective cloud architect by taking a course or two? Rick Blaisdell wrote a great blog about a month ago called “Top Cloud Skills Employers are Looking For” that I would highly recommend reading.

Cloud Architect Training, Today

I recently wrote a blog about a Forbes article I read by Jason Bloomberg about the concept of cloudwashing. I think this idea applies very well to the cloud training offerings out there today. If you take a look, many of the cloud training courses that currently exist from established vendors are simply rebranded with “Cloud” as a highlight.

The Valuable Cloud Architect

The cloud architect should possess a healthy combination of the following skills:

Technical –especially virtualization with a splash of programming and automation
IT operations – in particular the concept of IT services and an IT services portfolio
Understanding of your business, its initiatives, its challenges, etc.

Technical Skills of the Cloud Architect

Technically speaking, cloud architects need to bring their past experience to bear, validated by the following certifications:

Current VCP
ITIL v3 Foundations
At least one vendor certification (e.g., AWS Certified Solution Architect)
Basic knowledge of programming and automation(2)

Technical competence is more of a pre-requisite for a cloud architect. It should be assumed that a cloud architect has some hands-on experience with these items. As they say, these technical skills are necessary but not sufficient for the complete cloud architect. Having acquired these certifications, an architect would probably be hip to the recent progression of IT that occurred since virtualization became mainstream. If you’ve read this far, you’d probably agree that virtualization alone does not mean cloud computing. However, many of the fundamental characteristics of cloud borrow from virtualization and are practical due to virtualization.

Other Core Skills of the Cloud Architect

Maybe the role of the cloud architect is less technical than we think. Business and market knowledge is absolutely critical for the cloud architect, for several reasons:

Products, features, and prices are changing day to day in the market for cloud services – why is this happening and what will happen tomorrow?
The traditional corporate IT market is, effectively, now a competitor in this market for IT services
Using cloud concepts, new companies are being formed and are growing rapidly – some of these companies may challenge your own business – how can the cloud architect understand them and improve their company’s competitive advantage, recognize partnership opportunities, bring products to market more rapidly using cloud and other emerging technology?

The third point is a bit of a departure from what we’ve seen as a cloud architect. This says that a cloud architect should really be a specialist in business issues. More than that, we think that Corporate IT should look to transform to specialize in the business rather than specialize in providing IT services. IT departments should be an Innovation Center for the business. More on that in a future post.

The market for cloud computing is changing every day. Established providers like Amazon Web Services introduce new features and products while also dropping prices. Established companies like Microsoft up their game quickly. New companies form to carve out a niche or challenge an established provider. Barriers to entry are low. Economists call this an active competitive marketplace. What does this mean for consumers? Consumers enjoy significant downward pressure on prices for cloud services (especially for commodity IaaS). This also means many new products from which to choose. For this reason, we think the modern cloud architect also needs to have some knowledge of the following:

Consulting Experience (particularly, how to assess an organization)
Relationships Between the Customer and Provider(1)
Essentials of Behavior in a Competitive Market(1) – specialization, substitutes, complements, network effects

I’ve seen a few posts lately suggesting that individuals in corporate IT need to retool. Here is one of those posts. I definitely agree with the author that IT administrators need to shift focus to services rather than servers. What this post leaves out is a recommendation of which new skills are needed. Which skills or certifications should an IT administrator or architect acquire? How do they get them? Later in this series, I’ll propose a training path for the new role of Cloud Architect, why certain skills are important, and how to acquire them.

For Part II, I’ll propose three different types of cloud architect, outline the responsibilities that individuals in this role might have, and describe a path to obtain the skills needed to deliver in this new role. Leave a comment below with your thoughts & stay tuned for part II.

By John Dixon, Consulting Architect

Photo credit = http://www.patheos.com/blogs/deaconsbench/2011/10/what-they-didnt-ask/

Cloud computing, cloudwashing, Featured

Forbes Cloudwashing Article: A Few Key Points

septiembre 12, 2014 John Dixon

By John Dixon, Consulting Architect

I came across an article from a couple of months ago by Jason Bloomberg in Forbes entitled, “Why Implement Cloud When Cloudwashing Will Suffice?” The article briefly describes adoption of cloud computing and the term “cloudwashing” – what vendors and customers are tending to do in order to get started with cloud computing. The article makes a lot of good points. Below, I highlighted a few of the points that stood out the most to me and added in some of my own thoughts.

“Cloudwashing typically refers to vendors’ and service providers’ exaggerated marketing, where they label a product as “Cloud” even when such designation is either completely false or at best, jumping the gun on a future capability … But it’s not just vendors and service providers who Cloudwash – executives often exaggerate the truth as well … some CIOs are only too happy to put OpenStack or CloudFoundry on their Cloud roadmaps, secure in the knowledge that they will now be able to present themselves as forward-looking and Cloud savvy…”

I’ve seen this firsthand in various conversations. And I don’t think it’s malicious or wrong – I think it represents a limited understanding of cloud computing. I like to point back to recent history and the days of datacenter consolidation. The whole thing was pretty straightforward…we installed some software on servers (vSphere, Hyper-V, or similar) and went to work virtualizing servers. From that, I derived benefits that were easy to understand – fewer servers to administer, less power consumed, vastly improved time to provision new servers, etc. We didn’t have to do much measurement of those things either. Who needs measurement when you consolidate, say, at least ten servers onto one. The whole thing was very comfortable. I think “cloudwashing” is a good term, and it feels like an attempt to replay datacenter consolidation in terms of cloud computing. And…It’ll be BETTER! After all, it is cloud, so the benefits must be greater!

Not so fast though. Mr. Bloomberg makes a key point later in the article, and I agree 100%.

“The underlying story [of cloud computing] is one of business transformation. Cloud Computing does not simply represent new ways of procuring IT assets or software. It represents new ways of doing business. Cloud, along with other Digital Transformation trends in IT including the rise of mobile technologies, the Internet of Things, and the Agile Architecture that facilitates the entire mess, are in the process of revolutionizing how businesses – and people – leverage technology. And as with any revolution, the change is both difficult to implement and impossible to understand while it’s happening.”

I think the author is absolutely correct here. Cloud Computing is a new capability for the business. One of the most exciting prospects of the whole cloud computing scene is this: it allows a business to take on more risk, fail fast, learn, and begin again. Call that the Deming Cycle or P-D-C-A, or whatever you like. Cloud computing has made real the fantastic growth of companies like Uber (valuation greater than Hertz and Avis combined) and Airbnb (in 2014, estimated to book more “hotel stays” than Hilton). Two crazy ideas that were no doubt implemented in “the cloud.”

Cloud is difficult to implement – if you think of it like any other technology project. Where do you start? How do you know when you’re done? Maybe it is not an implementation project at all.

“The choices facing today’s executives are far more complex than is it Cloud or isn’t it, or should we do Cloud or not. Instead, the question is how to keep your eye on your business goals as technology change transforms the entire business landscape.”

I couldn’t agree more with this. I think that IT organizations should specialize in its company’s core business, rather than administering systems that do not provide competitive advantages. At GreenPages, we’re currently bringing to market a set of Professional and Cloud services that will help organizations take advantage of cloud computing that I’m pretty excited about. To learn more about the evolution of the corporate IT department and what it means for IT decision makers, check out my ebook.

What do you think of Jason’s take on cloudwashing?

Cloud computing, Featured, XaaS

X as a Service (XaaS): What the Future of Cloud Computing Will Bring

agosto 15, 2014 John Dixon

By John Dixon, Consulting Architect

Last week, Chris Ward and I hosted a breakout session at Cloudscape 2014, GreenPages’ annual customer Summit. We spoke about cloud service models today (IaaS, PaaS, and SaaS), as well as tomorrow’s models — loosely defined as XaaS, or Anything-as-a-Service. In this post, I’ll discuss XaaS: what it is and why you might want to consider using it.

First, what is XaaS? Is this just more marketing fluff? Why do we need to define yet another model to fully describe cloud services? I contest that XaaS is a legitimate term, and that it is useful to describe a new type of cloud services — those that make use of IaaS, PaaS, and SaaS all neatly delivered in one package. Such packages are intended to fully displace the delivery of a commodity IT service. My favorite example of XaaS is desktop as a service, or DaaS. In a DaaS product, a service provider might assemble it with the following:

Servers to run Virtual Desktop Infrastructure from a provider such as Terremark (IaaS)
An office suite such as Microsoft Office365 (SaaS)
Patching and maintenance services
A physical endpoint such as a Chromebook or thin client device

The organization providing DaaS would design, assemble, and manage the product out of best-of-breed offerings in this case. The customer would pay one fee for the use of the product and have the all-important “one throat to choke” for the delivery of the product. At GreenPages, we see the emergence of XaaS (such as DaaS) as a natural evolution of the market for cloud services. This sort of market behavior is nothing new for other industries in a competitive market. Take a look at the auto industry (another one of my favorite examples). When you purchase a car, you are buying a single product from one manufacturer. That product is assembled from pieces provided by many other companies — from the paint, to the brake system, to the interior, to the tires, to the navigation system, to name a few. GM or Ford, for example, doesn’t manufacture any of those items themselves (they did in days past). They source those parts to specialist providers. The brakes come from Brembo. The interior is provided by Lear Corp. The Tires are from Goodyear. The navigation system is produced by Harman. The auto manufacturer specializes in the design, marketing, assembly, and maintenance of the end product, just as a service provider does in the case of XaaS. When you buy an XaaS product from a provider, you are purchasing a single product, with guaranteed performance, and one price. You have one bill to pay. And you often purchase XaaS on a subscription basis, sometimes with $0 of capital investment.

You can download John’s “The Evolution of Your Corporate IT Department” eBook here

So, secondly, why would you want to use XaaS? Let’s go back to our DaaS example. At GreenPages, we think of XaaS as one of those products that can completely displace a commodity service that is delivered by corporate IT today. What are commodity services? I like to think of them as the set of services that every IT department delivers to its internal customers. In my mind, commodity IT services deliver little or no value to the top line (revenue) or bottom line (profit) of the business. Desktops and email are my favorite commodity services. Increased investment in email or the desktop environment does not translate into increases in top-line revenue or bottom-line profit for the business. Consider that investment includes financial and time investments. So, why have an employee spend time maintaining an email system if it doesn’t provide any value to the business? Two key questions:

Does investment in the service return measurable value to the business?
In the market for cloud services, can your IT department compete with a specialist in delivering the service?

When looking at a particular service, if you answer is “No” to both questions, then you are likely dealing with a commodity service. Email and desktops are two of my favorite examples. Coming back to the original question… you may want to source commodity services to specialist providers in order to increase investment (time and money) on services that do return value to the business.

We’ll expand this discussion into the role of corporate IT in a future post. For now though, what do you think of XaaS? Would you use it to replace one of your commodity services? Maybe you already do. I’m interested to hear from you about which services you have chosen to source to specialist providers.

Featured, Miscellaneous IT

Moving to the Cloud: Lessons from Jason Segel & Cameron Diaz

julio 24, 2014 Journey to the Cloud

By Ben Stephenson, Journey to the Cloud

As you probably know, Jason Segal and Cameron Diaz recently came out with a new movie called “Sex Tape.” In the movie, Segel and Diaz play a couple who decide to make an adult home movie, and it accidently gets released online.

I saw the trailer a couple of weeks ago and one clip from it grabbed my attention. After Jason and Cameron realize the tape has been released, they start to panic. The clip shows the two driving in a frenzy talking about how the tape got released (you can watch the clip here).

Cameron: “How do you forget to delete your sex tape?”

Jason: “It kept slipping my mind, and then the next thing I knew it went up…it went up to the cloud.”

Cameron: “And you can’t get it down from the cloud?”

Jason: “Nobody understands the cloud. It’s a mystery”

This got me thinking about some companies’ abruptness to go to the cloud without fully understanding the consequences. IT decision makers are under increasing pressure from CEOs & CFOs to utilize the benefits of cloud. If your IT department doesn’t have a well thought out strategy, however, chances are you’re not going to be successful. You don’t want to move to the cloud for the sake of moving to the cloud and then be in a frenzy if something goes wrong. I spoke with one of our bloggers, and cloud expert, John Dixon to get his take on what organizations need to consider before deciding to move to the cloud. Here’s what John had to say:

Not everything is a great fit for cloud

Have some high-end CAD desktops? Not a great fit for cloud (at least right now). Just setup a new ERP system on new hardware? Not a great fit for cloud at the moment. Testing some new functionality on your website or a new brand entirely? Now we’re talking — setup the infrastructure, test the market, scale up if needed, take everything down if needed.

Benefits of cloud are potentially huge, but hard to measure

Back in the datacenter consolidation days, the ROI of doing a virtualization project was dead easy. Consolidate at least 10 physical servers down to 1, and you have instant savings in power, cooling, floor space, administrative burden, etc. Some nice features came from having virtualized infrastructure, like the ability to provision servers from templates, easier DR, etc. Infrastructure teams were the big winners. In short, you could easily calculate the financial benefit of virtualizing servers. With cloud, this is not the case. If you look closely, there is limited benefit in just “moving” servers to the cloud. In fact, it may cost you more to host servers in the cloud than it does in your physical datacenter. However, IaaS clouds allow you to do things that you couldn’t do on your own. A pharmaceutical company can “rent” 10,000 servers to run a 2 day simulation; an online school can build infrastructure in a cloud datacenter in Australia to test a new market in APAC; a startup can use cloud to run ALL of its technical services (with no capital investment). In short, you’ve got to understand your existing costs, your use cases, and the benefits you are seeking. Jumping in to cloud without this mindset may comprise the benefits of doing so.

Portability or optimization? Especially in Amazon Web Services

As of now, you can’t have both. Choose wisely. Optimizing your application for cloud (for example, in AWS) by making use of RDS, SNS, SQS, Cloudformation, Autoscaling, Cloudwatch, etc. can deliver some amazing benefits in terms of scalability, supportability, and reliability. However, doing so destroys portability and any hope of brining that application back in house. On the flip side, VMware vCHS offers awesome portability, but the opportunities for optimization are fewer.

So, lessons for the kids out there? Don’t upload certain home videos online and have a well thought out cloud strategy before jumping into anything you may regret.

Oh, and Jason…borderline offensive when you say “no one gets the cloud”…because GreenPages gets it…

If you would like to hear more from John, download his ebook on the evolution of the corporate IT department.

Cloud computing, Featured, hybrid cloud, Public Cloud, Shadow IT

Have You Met My Friend, Cloud Sprawl?

mayo 15, 2014 John Dixon

By John Dixon, Consulting Architect

With the acceptance of cloud computing gaining steam, more specific issues related to adoption are emerging. Beyond the big-show topics of self-service, security, and automation, cloud sprawl is one of the specific problems that organizations face when implementing cloud computing. In this post, I’ll take a deep dive into this topic, what it means, how it’s caused, and some options for dealing with it now and in the future.

Cloud Sprawl and VM Sprawl

First, what is cloud sprawl? Simply put, cloud sprawl is the proliferation of IT resources – that provide little or no value – in the cloud. For the purposes of this discussion, we’ll consider cloud to be IaaS, and the resources to be individual server VMs. VM sprawl is a similar concept that happens when a virtual environment goes unchecked. In that case, it was common for an administrator, or someone with access to vCenter, to spin up a VM for testing, perform some test or development activity, and then forget about it. The VM stayed running, consuming resources, until someone or something identified it, determined that it was no longer being used, and shut it down. It was a good thing that most midsize organizations limited vCenter or console access to perhaps 10 individuals. So, we solved VM sprawl by limiting access to vCenter, and by maybe installing some tools to identify little-used VMs.

So, what are the top causes of cloud sprawl? In IT operations terms, we have the following:

Self-service is a central advantage of cloud computing, and essentially cloud means opening up a request system to many users
Traditional IT service management (a.k.a. ITIL) is somewhat limited in dealing with cloud, specifically configuration management and change management processes
There remains limited visibility into the costs of IT resources, though cloud improves this since resource consumption ends up as a dollar amount on a bill…somewhere

How is Cloud Sprawl Different?

One of the main ideas behind cloud computing – and a differentiator between plain old virtualization and centralization – is the notion of self-service. In the language of VMware, self-service IaaS might be interpreted as handing out vCenter admin access to everyone in the company. Well, in a sense, cloud computing is kind of like that – anyone who wants to provision IaaS can go out to AWS and do just that. What’s more? They can request all sorts of things, aside from individual VMs. Entire platform stacks can be provisioned with a few clicks of the mouse. In short, users can provision a lot more resources, spend a lot more money, and cause a lot of problems in the cloud.

We have seen one of our clients estimate their cloud usage at a certain amount, only to discover that actual usage was over 10 times their original estimate!

In addition, cloud sprawl can go in different directions than plain old VM sprawl. Since there are different cloud providers out there, the proliferation of processes and automation becomes something to watch out for. A process to deal with your internal private cloud may need to be tweaked to deal with AWS. And it may need to be tweaked again to deal with another cloud provider. In the end, you may end up with a different process to deal with each provider (including your own datacenter). That means more processes to audit and bring under compliance. The same goes for tools – tools that were good for your internal private cloud may be completely worthless for AWS. I’ve already seen some of my clients filling their toolboxes with point solutions that are specific to one cloud provider. So, bottom line is that cloud sprawl has the potential to drag on resources in the following ways:

Orphaned VMs – a lot like traditional VM sprawl, resulting in increased spend that is completely avoidable
Proliferation of processes – increased overhead for IT operations to stay compliant with various regulations
Proliferation of tools – financial and maintenance overhead for IT operations

Download John’s ebook “The Evolution of Your Corporate IT Department” to learn more

How Can You Deal with Cloud Sprawl?

One way to deal with cloud sprawl is to apply the same treatment that worked for VM sprawl: limit access to the console, and install some tools to identify little-used VMs. At GreenPages, we don’t think that’s a very realistic option in this day and age. So, we’ve conceptualized two new approaches:

Adopt request management and funnel all IaaS requests through a central portalThis means using the accepted request-approve-fulfill paradigm that is a familiar concept from IT service management.
Sync and discoverGive users the freedom to obtain resources from the supplier of their choosing, whenever and wherever they want. IT operations then discovers what has been done, and runs their usual governance processes (e.g., chargeback, showback) on the transactions.

Both options have been built in to our Cloud Management and a Service (CMaaS) platform. I see the options less as an “either/or” decision, and more of a progression of maturity within an organization. Begin with Option 2 – Sync and Discover, and move toward Option 1 – Request Management.

As I’ve written before, and I’ll highlight here again, IT service management practices become even more important in cloud. Defining services, using proper configuration management, change management, and financial management is crucial to operating cloud computing in a modern IT environment. The important thing to do now is to automate configuration and change management to prevent impeding the speed and agility that comes with cloud computing. Just how do you automate configuration and change management? I’ll explore that in an upcoming post.

See both options in action in our upcoming webinar on cloud brokerage and governance. Our CTO Chris Ward will cover:

Govern cloud without locking it down: see how AWS transactions can be automatically discovered by IT operations
Influence user behavior: see how showback reports can influence user behavior and conserve resources, regardless of cloud provider
Gain visibility into costs: see how IaaS costs can be estimated before provisioning an entire bill of materials

Register for our upcoming webinar being held on May 22nd @ 11:00 am EST. “The Rise of Unauthorized AWS Use. How to Address Risks Created by Shadow IT.

CIO Focus Interview: Main Challenges

CIO Focus Interview: A look back at 2014

CIO Focus Interview: Looking Ahead

Levels of the Cloud Architect

Training and Certification

Cloud Architect Training, Today

The Valuable Cloud Architect

Technical Skills of the Cloud Architect

Other Core Skills of the Cloud Architect

The cloud news categorized.