Welcome!

Related Topics: @CloudExpo, Java IoT, Linux Containers, Containers Expo Blog, @BigDataExpo, SDN Journal

@CloudExpo: Article

Top Ten Considerations for a Converged Infrastructure Investment

Ten tips you should consider to maximize the benefits of a Converged Infrastructure investment

Archie Hendryx looks at the benefits and challenges of managing multiple IT components through a single support solution

Many public sector organisations are not changing their ICT legacy systems. As a result, they face increasing number of inefficiencies and challenges. These issues can nevertheless be overcome, and performance increased, by managing these legacy systems within a converged infrastructural environment. This approach can also reduce the risks associated with legacy systems, such as security, missing functionality, increased complexity and operational expenditure.

Converged infrastructure simplifies support as it packages multiple IT components from different vendors into one single, optimised computing solution. So it offers end-to-end support unlike reference architectures, which require organisations to deal with a multitude of disparate vendors to gain support. Converged infrastructure removes the need to manage multiple upgrade cycles, offers pre-tested interoperability and release management resources. It enables organisations to centralize the management of IT resources.

A converged infrastructure has pre-configured and pre-tested configurations while reference architectures follow certain guidelines. Converged infrastructures tend to have defined scalability. Reference architectures are completely flexible but they have no defined performance boundaries, making it less predictable than a converged infrastructure.

The components of a converged infrastructure include servers, data storage devices, networking equipment, software for IT infrastructure management, automation and orchestration. A converged infrastructure can be used as a platform for private, hybrid and public cloud computing services: e.g. infrastructure-as-a-service (IaaS), platform-as-a-service (PaaS) and software-as-a-service (SaaS).

The journey towards operating converged infrastructure should begin by establishing a business case: both technical and commercial goals and objectives such as the ability to deploy new products and services to market much faster than a traditional IT model all so often permits. Reliability, data security and a reduction in infrastructural complexity will no doubt be at the core of your proposition. There may be a number of other factors in play, and many of these could point you towards developing a converged cloud infrastructure because it delivers efficiency, reduces complexity without reducing security.

Tips to improve performance

1. Restructure your complex and disparate IT technology-focused silos to a centralised, streamlined and service-oriented converged infrastructure team that will be able to do a lot more a lot quicker. Traditional designs are based on in house and siloed expertise that inevitably introduce risk as success depends on this expertise being shared and correlated between teams prior to building the infrastructure.

Speed to deployment and agility is a key factor with converged infrastructure where new project rollouts can be reduced from months to days. To enhance this, a model that includes a capacity on demand buffer model should be looked at. This enables the public sector to have additional inventory installed in their converged infrastructure for unplanned growth and projects, where the payment of such inventory is only made once it's consumed. This consequently reduces project delivery times drastically.

Another key factor is the support model, which should provide a single and seamless model. Instead of a dial in number that ultimately sends you to various departments for all the infrastructure components, the support model should be set up to manage and maintain the single product, namely the converged infrastructure. This will consequently reduce the mean time to resolution for the public sector considerably if and when any issues arise.

2. Prepare for simplified operations. Converged infrastructure offers the opportunity to simplify and centrally monitor your workloads and capacity management as well as application performance.

3. Look to fully virtualise your environment. Converged infrastructures can enable you to immediately consolidate and virtualise your workloads. This provides the flexibility to seamlessly move resources from one virtual machine to another and also avoid vendor lock in should you decide to move to another platform at a later date. Legacy systems can often cause headaches, but with a converged cloud infrastructure an opportunity arises to gain a highly virtualised, optimised, secure and a highly available but also stable platform that will improve performance while enhancing existing services.

4. Plan for data protection. Accidental data loss is perceived as the biggest security threat to public sector organisations so a backup and recovery solution that comes pretested and pre-integrated with your converged infrastructure should be a serious consideration.

5. Prepare to streamline your security policies. Converged Infrastructures offer the ability to enhance security controls and increase compliance while still offering the benefits associated with cloud. For example instead of complex and costly deployments of physical security infrastructure, virtualised appliances and enterprise software security suites offer the same features but with the added agility of being virtualised.

6. Implement a disaster recovery solution. Converged infrastructures offer the ability to quickly standardise the platform specifications between two sites as well as shift away from complex, convoluted and manual failover methods. With pretested and pre-integrated disaster recovery and avoidance solutions, failover and failback processes can be automated tasks that mitigate risk and reduce OPEX costs being introduced when protecting against a disaster.

7. Initiate a private cloud strategy. A converged infrastructure removes a lot of the infrastructure challenges associated with deploying a private cloud and offers a standardised and optimised platform that can allow you to focus on designing service catalogues, blueprints, chargeback, billing, approval processes etc. By implementing an integrated self-service provisioning model, the converged infrastructure enables a Private Cloud to be quickly deployed allowing workloads and resources to be provisioned and allocated in minutes.

8. Include a strategy to accommodate a software defined data centre (SDDC) approach. Converged infrastructure offerings are already incorporating solutions that enable a SDDC that consequently help free up even more administration time and resources. SDDC extends the benefits of virtualisation by incorporating orchestration, automation and management to core components enabling IT admin to become proactive and subsequently innovative.

Additionally the load sharing and balancing of resources within converged infrastructures and SDDC models allows for higher efficiency and utilisation as well as streamlined infrastructure scalability enabling the business to meet future and unplanned demands in a seamless manner.

The higher availability and testable disaster recovery solutions also allow the business to safeguard against the unnecessary costs and fines associated with unplanned downtime. Ultimately the streamlining of manual and complex processes into functions that are automated and orchestrated allows the business to focus on new initiatives and application delivery and consequently forget about the infrastructure that supports them.

9. Establish new internal architectural and compliance standards that cater for converged infrastructure. Instead of having to design, document and adhere to standards for every single component within a traditional infrastructure, converged infrastructures are a comprehensive product. This simplifies internal processes considerably as the standardisation, design, integration, security, availability, support and maintenance of converged infrastructures are already catered for by the vendor.

A converged infrastructure should incorporate a release certification matrix that validates all of the patches, maintenance and upgrades of all of the product's components throughout its lifecycle. To ensure this compliance an API that can scan, validate, present and monitor the infrastructure as a whole is a necessity. Unless a converged infrastructure includes this it ultimately remains a well-marketed collection of components that will offer little if any advantage over a traditional infrastructure.

Furthermore the converged infrastructure offering should include quality assurance that fully tests and validates all software updates for security and availability vulnerabilities consequently reducing ongoing risks. This will allow public sector organisations to extend their capabilities by integrating additional security and compliance controls to meet their objectives. The key here is that security and high availability is built in at the outset rather than added as an afterthought, ensuring the confidentiality, integrity and availability of the business infrastructure.

10. Simplify process management. Change management, incident management, asset management etc. are all processes that can be significantly simplified with a converged infrastructure offering and in most cases automated. For example asset management becomes simplified in that the configuration management database input now replaces thousands of complex components with a single entity that has all of its components supported by a single vendor as a single product. Additionally monitoring, alerting, logging, maintenance, patching and upgrading procedures can all be automated with converged infrastructure, mitigating the risk associated with manual tasks.

With traditional deployments you need to keep patches and firmware up to date with multiple vendors, components and devices which requires internal IT to assess the criticality of each patch and relevance to each platform as well as validate firmware compatibility with other components. This requires costly mirrored Production Test Labs and then also having rollback mechanisms if there are any issues.

Coupled with these risks, the multiple vendors needed to support a traditional infrastructure lead to prolonged resolution times when issues occur. Logging a support call for a traditional infrastructure first needs the identification of who is responsible: this might be the storage vendor, the networking company, the hypervisor or the server manufacturer.

Archie Hendryx is Principal vArchitect at converged infrastructure supplier VCE

Original article taken from Public Technology Magazine.

More Stories By Archie Hendryx

SAN, NAS, Back Up / Recovery & Virtualisation Specialist.

Latest Stories
WebRTC has had a real tough three or four years, and so have those working with it. Only a few short years ago, the development world were excited about WebRTC and proclaiming how awesome it was. You might have played with the technology a couple of years ago, only to find the extra infrastructure requirements were painful to implement and poorly documented. This probably left a bitter taste in your mouth, especially when things went wrong.
Up until last year, enterprises that were looking into cloud services usually undertook a long-term pilot with one of the large cloud providers, running test and dev workloads in the cloud. With cloud’s transition to mainstream adoption in 2015, and with enterprises migrating more and more workloads into the cloud and in between public and private environments, the single-provider approach must be revisited. In his session at 18th Cloud Expo, Yoav Mor, multi-cloud solution evangelist at Cloudy...
When you focus on a journey from up-close, you look at your own technical and cultural history and how you changed it for the benefit of the customer. This was our starting point: too many integration issues, 13 SWP days and very long cycles. It was evident that in this fast-paced industry we could no longer afford this reality. We needed something that would take us beyond reducing the development lifecycles, CI and Agile methodologies. We made a fundamental difference, even changed our culture...
The proper isolation of resources is essential for multi-tenant environments. The traditional approach to isolate resources is, however, rather heavyweight. In his session at 18th Cloud Expo, Igor Drobiazko, co-founder of elastic.io, drew upon his own experience with operating a Docker container-based infrastructure on a large scale and present a lightweight solution for resource isolation using microservices. He also discussed the implementation of microservices in data and application integrat...
All organizations that did not originate this moment have a pre-existing culture as well as legacy technology and processes that can be more or less amenable to DevOps implementation. That organizational culture is influenced by the personalities and management styles of Executive Management, the wider culture in which the organization is situated, and the personalities of key team members at all levels of the organization. This culture and entrenched interests usually throw a wrench in the work...
Containers have changed the mind of IT in DevOps. They enable developers to work with dev, test, stage and production environments identically. Containers provide the right abstraction for microservices and many cloud platforms have integrated them into deployment pipelines. DevOps and containers together help companies achieve their business goals faster and more effectively. In his session at DevOps Summit, Ruslan Synytsky, CEO and Co-founder of Jelastic, reviewed the current landscape of Dev...
In his General Session at DevOps Summit, Asaf Yigal, Co-Founder & VP of Product at Logz.io, will explore the value of Kibana 4 for log analysis and will give a real live, hands-on tutorial on how to set up Kibana 4 and get the most out of Apache log files. He will examine three use cases: IT operations, business intelligence, and security and compliance. This is a hands-on session that will require participants to bring their own laptops, and we will provide the rest.
IoT is at the core or many Digital Transformation initiatives with the goal of re-inventing a company's business model. We all agree that collecting relevant IoT data will result in massive amounts of data needing to be stored. However, with the rapid development of IoT devices and ongoing business model transformation, we are not able to predict the volume and growth of IoT data. And with the lack of IoT history, traditional methods of IT and infrastructure planning based on the past do not app...
"LinearHub provides smart video conferencing, which is the Roundee service, and we archive all the video conferences and we also provide the transcript," stated Sunghyuk Kim, CEO of LinearHub, in this SYS-CON.tv interview at @ThingsExpo, held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA.
"We're bringing out a new application monitoring system to the DevOps space. It manages large enterprise applications that are distributed throughout a node in many enterprises and we manage them as one collective," explained Kevin Barnes, President of eCube Systems, in this SYS-CON.tv interview at DevOps at 18th Cloud Expo, held June 7-9, 2016, at the Javits Center in New York City, NY.
With major technology companies and startups seriously embracing IoT strategies, now is the perfect time to attend @ThingsExpo 2016 in New York. Learn what is going on, contribute to the discussions, and ensure that your enterprise is as "IoT-Ready" as it can be! Internet of @ThingsExpo, taking place June 6-8, 2017, at the Javits Center in New York City, New York, is co-located with 20th Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry p...
@DevOpsSummit at Cloud taking place June 6-8, 2017, at Javits Center, New York City, is co-located with the 20th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is no time to wait for long developm...
Updating DevOps to the latest production data slows down your development cycle. Probably it is due to slow, inefficient conventional storage and associated copy data management practices. In his session at @DevOpsSummit at 20th Cloud Expo, Dhiraj Sehgal, in Product and Solution at Tintri, will talk about DevOps and cloud-focused storage to update hundreds of child VMs (different flavors) with updates from a master VM in minutes, saving hours or even days in each development cycle. He will also...
In a recent research, analyst firm IDC found that the average cost of a critical application failure is $500,000 to $1 million per hour and the average total cost of unplanned application downtime is $1.25 billion to $2.5 billion per year for Fortune 1000 companies. In addition to the findings on the cost of the downtime, the research also highlighted best practices for development, testing, application support, infrastructure, and operations teams.
@DevOpsSummit taking place June 6-8, 2017 at Javits Center, New York City, is co-located with the 20th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. @DevOpsSummit at Cloud Expo New York Call for Papers is now open.