devopsy.kinsta.cloud

Author: Brian J. Kelly

Taming the Shadow IT Beast and Runaway Spend

Do you know how much IT resources your employees are consuming?

According to research conducted by the Everest Group, shadow IT spending accounts for a whopping 50% or more of the IT budget. Beyond these costs, shadow IT could end up costing you big in terms of a security breach: Gartner estimates that 33% of security attacks will be on shadow IT resources by 2020. Simply put, shadow IT isn’t just an expensive problem to have. It’s a threat to your business.

You Can’t Blame Developers for Going Rogue

DevOps and application teams are a key consumer of IT resources in your organization—they’re agile teams who need to get product releases out the door quickly. They need to get the job done, and will provision any resource that will get them there, even if it means going around IT.

Still, you can’t blame these developers for going rogue: They need the right resources when they need them, and IT, busy responding to multiple tickets while juggling daily fires, can’t always meet those needs in a timely fashion. From a developer’s perspective, though, the fact that IT is firing on all cylinders to do their best doesn’t matter. For them, waiting days for resources may as well be an eternity.

Giving Your DevOps Teams the Goods

In a perfect world, DevOps and application teams would get access to the resources they need without the back and forth of ticketing systems, or the complexity of provisioning resources on systems that are totally unfamiliar systems. The latter is especially risky because it can introduce potential security holes that could be exploited by attackers.

To this end, IT’s ultimate goal should be to enable self-service provisioning for DevOps and application teams. Creating a catalog that only serves up the resources relevant to the requesting team is one option here. Through blueprints, a repeatable way to orchestrate and automate provisioning of resources, this self-service nirvana becomes a reality: IT delivers resources in minutes, not days or weeks, and developers get what they need without putting the organization at financial and operational risk.

Delivering Self-Service, but with a Safety Net

Of course, IT wants to be as efficient and agile as possible, though not at the expense of control over cost and compliance. So, while enabling DevOps, IT also needs to monitor and contain cross-cloud spend.

To accomplish this, IT can set automated quotas and limits, ensuring that user access to AWS resources, memory and more, is tightly controlled. They can also set up controls, such as power scheduling and expiration dates, to further control costs. As a result, VMs can’t be left on gobbling resources over the weekend, and demo environments shut down automatically when no longer used.

From a security and compliance standpoint, IT can prevent teams from going rogue by determining who can do what. For instance, this could be who can orders servers, workloads and XaaS—along with quotas set for spend and resource usage—to who can approve fulfillment of those orders. This way, resources are never overprovisioned, and a real tally is kept as to exactly who is using which resources across the business.

Taming the Shadow IT Beast

With a better handle on cloud spend and resource usage, IT teams can put a dent in the 44% of IaaS compute spend stemming from non-production resources that are accidentally left running, according to ParkMyCloud. At the same time, they can stay on top of security and compliance, while still giving DevOps the tools they need, with orchestration blueprints that automate resource provisioning on a repeated basis. Taming the shadow IT beast, allowing developers to access resources in seconds with a self-service catalog, frees up IT teams to tame all the other beasts they face on a daily basis.

— Brian J. Kelly

April 3, 2020
How Enterprise IT Teams Can Win the Hearts of DevOps

Take your average IT team in a young enterprise in the midst of skyrocketing growth. There’s a good chance the workflows they’ve used since the outset can’t keep up with the ever-increasing volume of requests from the business. In the minds of some DevOps and app development teams in particular, the IT department of the scrappy startup has gradually become the department of slowing things down.

As a result, tasks that once took hours, such as provisioning resources (e.g., virtual machines, workloads, XaaS), can now take days. For agile DevOps teams, this is essentially a showstopper: They need access to resources when they need them–not when you deem them worthy. Anything else feels like a drag on development and the business.

Giving DevOps What They Want

IT needs to make access to resources as seamless as possible for DevOps teams. The ultimate goal is self-service. DevOps should be able to instantly gain the access they need to the resources they need, without the back and forth of ticketing systems, or the complexity of provisioning resources on totally unfamiliar systems. And with a user interface that only serves up the resources relevant to the requesting team, DevOps can easily manage and provision resources on demand.

Maintaining the Controls the Enterprise Needs

Of course, it’s not about just giving DevOps access to whatever they want when they want it. You need real controls in place.

For example, without the right guardrails, DevOps teams can easily spin up more virtual machines than they need and let them run without limit. To give you an example of how bad it can get, Gartner estimates shadow IT accounts for 30-40% of IT spend, from idle resources consuming costs by the minute.

Through blueprints, repeatable ways to orchestrate and automate provisioning of resources, this self-service nirvana to eliminate shadow IT can be a reality for admins. Since blueprints contain set rules and builds sanctioned by IT, they’ll always be able to accurately and securely deliver the right resources, without users going rogue and out of compliance with taking provisioning into their own hands.

For instance, IT can determine who can order servers, workloads and XaaS—along with quotas set for spend and resource usage—to who can approve fulfillment of those orders. This way, resources are never over-provisioned and a real tally is kept as to exactly who is using which resources across the business. By automating routine approval processes and applying the proper conditions to user requests, the errors and time associated with manual provisioning are eliminated and users can get what they need without going at it alone.

Control Doesn’t Have to Come at the Cost of Delight

In the absence of the right tools and the right processes, IT can start to seem like a slow-moving gatekeeper to DevOps teams, who need resources fast. Consuming resources needs to be easy and quick for agile developers who need to ship products to market fast. In this sense, the self-service IT model plays greatly to agility: By presenting only the resources needed for DevOps teams, and orchestrating automated processes, resources are provisioned in seconds versus the days involved with an IT ticket. Additionally, with built-in, automated permissions and role-based controls, IT teams can still protect the enterprise, as they should, but at the same time delight users.

Take for example an organization as big as Home Depot, with over 385,000 employees: By rolling out a self-service approach to provisioning resources, they were able to completely reign in VM sprawl and at the same time make their developers’ lives easier with a provisioning time decreased from two weeks to just under 20 minutes.

Indeed, IT admins can win the hearts of DevOps and at the same time win back their role as an enabler of enterprise-wide innovation. By empowering users with intuitive self-service to quickly get resources when they need them, IT becomes the heroes that enterprises–and their DevOps teams—need.

— Brian J. Kelly

October 16, 2019
How Not to Sabotage Your Multi-Cloud Strategy

The immense pressure for enterprises to deliver new applications and insights that exploit new business opportunities has been a driving force for digital transformation. This, in turn, has led IT leaders to embrace a multi-cloud strategy—whether that’s deploying a combination of cloud platforms such as AWS, Azure and Google, or extending private data centers to the public cloud—to achieve greater agility, optimized performance and cost savings resulting from deploying workloads across multiple cloud platforms.

However, maintaining multiple cloud platforms and services adds complexity and even confusion to enterprise IT environments already crowded with a range of technologies, applications and processes. While a recent Forrester study shows that enterprises are increasing investments in using multi-cloud strategies for business-critical applications and workloads, the majority of these enterprises also report that they experienced issues with deploying and using multi-cloud environments.

The difficulty in managing IT environments made more complex by multiple cloud services involves three major issues: ignoring the importance of cultural transformation, not addressing the widening skill set gap and implementing a DIY approach to cloud management.

Here are three ways to deal with these challenges, so you don’t end up sabotaging your multi-cloud strategy.

Make Culture Change a Priority

The cultural transformation required to support digital transformation and to fully take advantage of multi-cloud’s power is more than shifting the organizational mindset from capex to opex. It’s also more than picking one or a combination of the big three cloud providers and simply saying, “Let’s do this.” It requires building trust and breaking down the silos of technology knowledge—whether vendor, legacy or emerging technologies—across disparate IT teams to achieve the business goal of speedier application development and faster time to market.

Specifically, this culture change requires better collaboration between teams and arming central IT with up-to-date processes and management platforms that are focused less on managing infrastructures and more on achieving a balance between visibility and resource control, the linchpin for IT, and creativity, the true north for developers. It will have parameters in place for provisioning resources while helping developers get the resources they need—compute, storage, network services and more—as quickly as possible.

Culture change also enables the maturing of DevOps processes toward streamlining and bringing order to the clutter and smooth partnerships with other IT teams, especially security and operations. These include processes to eliminate bottlenecks in workflow, to advance automation and self-service, to consolidate resources and to make security integral to—rather than an afterthought in—the development process.

Invest in Building Expertise in Multi-Cloud and Emerging Technologies

The more cloud environments an organization has, the more skills and tools are needed to be able to deploy and optimize these environments efficiently. Despite increasing commoditization in the industry, there are still differentiators between cloud vendors and their services, and ways to leverage these to align with an organization’s specific needs. To do this, it is crucial to train the internal DevOps team or hire experts in multi-cloud environments and in key technologies for advancing multi-cloud such as containerization, microservices and serverless computing.

Additionally, a cloud management platform that provides self-service IT and enables any user to provision, manage and orchestrate IT resources, will allow both end users and admins more time to focus on getting high-quality work done.

Select a Cloud Management Platform that’s Right for You

Cloud management platforms address the complexity of hybrid and multi-cloud environments by providing a central platform that allows a selection of the clouds and services that best fit an organization’s needs. They also enable IT to connect to any third-party resource, whether that’s VMware on-prem, AWS in the public cloud or container orchestrators such as Kubernetes, to gather the inventory of cloud computing resources and to provision new resources to be used by anyone in the organization from one place. Self-service IT can also be enabled when appropriate.

In addition, by ensuring cloud management platforms are built on a single pane of glass, IT can gain a holistic view of hybrid and multi-cloud environments. It also allows effective monitoring of resource utilization across those environments, thus ensuring that cloud spend is not only reined in but also optimized.

Finally, a cloud management platform should connect both legacy and new technologies within cloud environments. Although the complexity will not go away, it gets easier to manage. Instead of having multiple teams from different departments managing and accessing resources in separate environments, a central team handles complexity with enterprisewide visibility and control.

The way to succeed is to embrace the complexity by configuring it and managing it behind the scenes, so developers and end users consume IT resources from one consistent way, regardless of where it comes from. Leave the complexity to the cloud and IT architects and let your end users and developers get to work.

— Brian J. Kelly

June 14, 2019