Category: IT as Code

  • Do You Trust Your Cloud Provider to Protect Your Data? Maybe You Shouldn’t

    Do You Trust Your Cloud Provider to Protect Your Data? Maybe You Shouldn’t

    Around the world, businesses are moving to the cloud at a rapid rate. But, is the cloud really the best place to store your mission-critical data and applications? Is it truly a safe place to put data and apps that need strong protection?

     The immediate answer from many companies is “yes.” A recent study by Dimension Research, found that 59% of organizations believe data backed up to the public cloud is safer than data backed up on-premises. Further, the study showed that nearly half of all organizations (46%) believe it is the responsibility of their cloud provider to recover data and applications in the event of an attack or loss.

    Are these beliefs about the safety of cloud data correct? Can organizations rely solely on their cloud service provider such as Google or Amazon Web Services (AWS) for data protection?

    Leading providers such as AWS, Microsoft Azure and Google Cloud Platform typically secure core infrastructure and services as part of their responsibility. But, when it comes to securing data, that responsibility lies squarely in the hands of customers. Organizations that overlook this simple fact face a much higher likelihood of suffering a serious data loss.

    Yet, the general perception remains that if something happens to your data, it’s not your responsibility. Too many organizations have convinced themselves that their cloud provider will take care of solving any issues for them and magically recover all their data if it’s lost.

    Unfortunately, that is not the case. Take, for instance, data generated in a cloud app like Microsoft’s Office 365. Yes, Microsoft guarantees the service, but it doesn’t guarantee the security of the data you generate when using the service.

    Office 365 does have some basic data protection schemes in place, such as a 30-day recycle bin that allows users to recover and restore deleted data within a 30-day window. That’s important because users will sometimes accidentally delete or purge their data and then realize they need it for legal reasons. After that 30-day limit, however, the data is gone for good. Microsoft, for its part, makes this clear in its terms of service: Users own their data and are responsible for what happens to it.

    This misconception around data responsibility is somewhat understandable. In particular, the StorageCraft study found that small and midsize companies are much more likely to believe that their cloud provider will bail them out in the event of a data loss. For instance, 52% of midsize companies believe their cloud provider is responsible for data recovery, compared to just 43% of enterprise companies who believe the same.

    Many of these smaller businesses trust that sophisticated, near trillion-dollar cloud providers such as Google, Microsoft and Amazon have ironclad capabilities when it comes to data protection. They think they don’t have to worry, and they’re in good hands. While that’s generally true, they don’t realize that data loss and recovery are separate issues and their own responsibility.

    There is also a strong belief among organizations with a cloud-first strategy that their data is safer in a public cloud than it is in an on-premises facility. The study found that 76% of companies with an overt cloud strategy feel their data is safer in the cloud, compared to just 37% of companies that prefer to store their data on-premises.

    Trust in the cloud also varies by culture. For instance, 71% of organizations in France believe that data backed up to a public cloud is safer than on-premises. By contrast, only 37% of German companies feel the same way. Likewise, the study found that 59% of French companies believe data recovery is the responsibility of their cloud provider, compared to just 41% of German companies.

    At the risk of overgeneralizing, one might conclude that Germans feel a greater need to be in control of their own data, while French companies have a more laissez-faire attitude toward data recovery, entrusting that their cloud providers will take care of any issues.

    But no business, wherever it’s located, should have a false sense of security. The truth is that, whether it’s an issue of data corruption, a security breach or even accidental data deletion, the onus is on you to recover that data, not your cloud provider.

    So, then the question all companies need to ask is this: When something bad happens, how are you going to get your data back? Then ask yourself what level of risk you can tolerate and what kind of data you are putting in the cloud. Is it data that’s mission-critical and can you afford to lose it? Will your business run exactly the same without that data you just lost? And if not, how bad will the impact be?

    Once organizations realize they can’t rely on their cloud provider, they start to understand what kind of data-recovery capabilities they do have and also what they might need to add to stay protected.

    The good news is there are easy-to-use, cost-effective solutions that enable organizations to simply, yet powerfully, manage their data storage and backup requirements, whether on-premises or in the cloud. Instead of mistrusting their cloud provider, organizations can simply set up a truly effective data-recovery strategy. Adding that extra, yet highly necessary, layer of protection to your cloud data could be the difference between a business that successfully responds to adversity and one that succumbs to disaster within days, while realizing that it relied on cloudy promises.

  • IBM Looks to Drive Edge Computing

    IBM Looks to Drive Edge Computing

    IBM today at its Think Digital conference launched an edge computing initiative anchored around an IBM Edge Application Manager, through which a single administrator can manage up to 10,000 nodes.

    Hillery Hunter, vice president and CTO for IBM Cloud, said IBM Edge Application Manager is based on the Open Horizon open source software originally developed by IBM that is now under the auspices of LF Edge, an arm of The Linux Foundation focused on networking and edge computing platforms. Open Horizon makes uses of machine learning algorithms to automate the management of fleets of edge computing platforms.

    IBM also launched IBM Telco Network Cloud Manager to orchestrate both virtual and container network functions. IBM Telco Network Cloud Manager is built on top of an instance of Red Hat OpenShift, which is based on Kubernetes, and Red Hat OpenStack Platform.

    Finally, IBM is making available a range of edge-enabled applications, including IBM Visual Insights, IBM Production Optimization, IBM Connected Manufacturing, IBM Asset Optimization, IBM Maximo Worker Insights and IBM Visual Inspector.

    Like most IT vendors IBM sees the rise of application workloads on the edge as an opportunity to drive adoption of hybrid cloud computing. In the case of IBM, all of these offerings run on the Red Hat OpenShift platform.

    IBM also announced the IBM Edge Ecosystem, which brings together independent software vendors (ISVs) and IBM partners to craft edge computing solutions. Additionally, IBM launched the IBM Telco Network Cloud Ecosystem, which is more narrowly focused on edge computing platforms deployed for telco-focused environments such as a wireless 5G network.

    IT vendors participating in those initiatives with IBM include Cisco Systems, Dell Technologies, Juniper, Intel, NVIDIA, Samsung, Packet & Equinix, Hazelcast, Sysdig, Turbonomics, Portworx, Humio, Indra Minsait, EuroTech, Arrow, ADLINK, Acromove, Geniatech, SmartCone, CloudHedge, Altiostar, Metaswitch, F5 Networks and ADVA.

    Edge computing will undoubtedly force organizations to embrace DevOps more aggressively. Managing thousands of edge computing platforms will require not just higher levels of IT automation infused with machine learning algorithms, but IT teams will also need to be able to deploy, secure, update and manage applications distributed across thousands of endpoints.

    IBM, of course, is not the only IT vendor eyeing the edge computing opportunity. The challenge IT organizations will face first is building new classes of latency-sensitive applications running in near real-time that will be built mainly using microservices. Once those applications are built, organizations will then need to update them continuously within the context of a highly scalable IT management framework.

    Naturally, some organizations will prefer to rely on external IT service providers to rise to that challenge while others will continue to build and manage their own applications and infrastructure. Regardless of the approach, the level of scale and complexity at which IT is being applied is about to reach a level that once would have been unimaginable. Not only will more applications run in near real-time, those applications will be integrated and share data with batch-oriented applications running in the cloud and local data centers. The challenge is finding a way to automate the management of IT at scale without requiring organizations to rely on manual processes, for which there are simply not enough IT professionals available to manage.

  • Dell Advances Convergence of Compute and Storage

    Dell Advances Convergence of Compute and Storage

    Dell Technologies today launched a revamped midrange storage platform that takes advantage of NVMe interfaces and solid-state drives (SSDs) to deliver 7x the performance of previous Dell EMC PowerStore platforms, in addition to allowing applications to run locally on an instance of a VMware virtual machine.

    Ben Jastrab, senior manager for storage product marketing at Dell Technologies, said the inclusion of a virtual machine in form of an AppsON capability means that rather than having to deploy applications on a server, for example, a data analytics application could be deployed directly on top of the data it needs to access on a storage system. In addition, the latest version of Dell EMC PowerStore adds support for instances of Kubernetes from VMware running on top of a virtual machine. Dell storage systems already provide support for the Container Storage Interface (CSI) needed to provide Kubernetes clusters access to external storage systems.

    Dell has also added support for Ansible and VMware vRealize Orchestrator frameworks to automate the deployment and ongoing maintenance of Dell EMC PowerStore systems. As part of that effort to automate the management of storage systems, Dell added built-in machine learning algorithms to automate labor-intensive tasks such as initial volume placement, migrations, load balancing and issue resolution. Dell EMC CloudIQ storage monitoring and analytics software makes it possible to combine machine learning and human intelligence for real-time and historical performance and capacity analysis.

    Jastrab noted that many of these innovations are made possible because the storage operating system employed within Dell EMC PowerStore has been completely revamped using microservices based on containers. That approach not only makes the operating system more flexible and resilient, but it also will afford Dell the opportunity to experiment with how it might present storage services in the future, he said.

    Automation coupled with technologies such as deduplication and compression will play a critical role in driving the total cost of storage lower in the months ahead, Jastrab said. In the wake of the economic downturn brought on by the COVID-19 pandemic, IT organizations will be under increased pressure to reduce costs at a time when both the amount and types of data that need to be analyzed and stored continue to increase, he noted, adding the Dell PowerStore system can provide access to 2.8PB of data when configured in a scale-up architecture and more than 11PB when configured using a scale-out architecture.

    IT teams will need to determine to what degree they want to rely on proprietary frameworks such as VMware vRealize to automate IT infrastructure versus an open source Ansible framework that can be applied more broadly to multiple platforms. Dell owns VMware, but Jastrab said the company is committed to providing support for multiple IT automation frameworks.

    It’s not clear to what degree applications will shift from being deployed on traditional servers to a storage system. Many next-generation applications are clearly more latency-sensitive than their predecessors, so providing more direct access to data over an NVMe interface may present IT teams with a compelling alternative. Regardless of the approach taken, the line between compute and storage continues to blur.

  • HPE Extends Reach of GreenLake Central

    HPE Extends Reach of GreenLake Central

    Hewlett-Packard Enterprise (HPE) has made available HPE GreenLake Central, a self-service portal through which IT teams can collaboratively manage and monitor instances of servers deployed in IT environments that are managed by HPE on their behalf.

    At its core, HPE GreenLake is a managed service that allows IT organizations to pay for IT infrastructure on a consumption basis. HPE meters usage and HPE ProLiant servers and bills customers accordingly. HPE GreenLake Central provides a portal through which IT teams can track usage themselves and provision applications both from HPE and third-party software vendors.

    Data management and file management software from Cohesity and Qumulo can be provisioned via the self-service portal. In addition, HPE GreenLake systems can now be co-located in data centers managed by CyrusOne.

    Keith White, vice president for HPE GreenLake, said HPE also provides via HPE GreenLake Central integration with Microsoft Azure Access Manager and Amazon Web Services (AWS) Access Manager services to make it easier for IT organizations to compare the cost of deploying workloads on-premises versus in the cloud, in addition to identifying potential compliance issues. IT teams still will need to access a separate portal provided by either AWS or Microsoft to spin up a virtual machine in the cloud.

    HPE claims to now have more than 800 enterprise customers consuming HPE GreenLake services. With many organizations opting to focus their efforts on building and deploying software, HPE is now making the case for a service through which it manages ProLiant servers and associated HPE storage on their behalf. In the wake of the economic downturn brought on by the COVID-19 pandemic, White said HPE expects to see increased demand for consumption-based pricing for IT infrastructure.

    Of course, IT teams have been consuming cloud infrastructure using various consumption-based pricing models for years. However, there are many workloads that for a wide variety of compliance, security and performance issues that still do not lend themselves to being deployed on a public cloud. HPE GreenLake provides the flexibility of a cloud service while still employing IT infrastructure deployed in a local data center.

    It’s unclear in the wake of the downturn how many additional application workloads might be moving into the cloud. The general expectation is that because many local data centers have been inaccessible during the pandemic, more organizations naturally will shift workloads to the cloud. However, a managed service from HPE also serves to eliminate the need to manage servers in an on-premises IT environment that are managed remotely by HPE. IT teams can remotely log into the HPE GreenLake portal from wherever they are located.

    Undoubtedly, the relationship between IT teams and vendors such as HPE is evolving. Many rote infrastructure tasks increasingly are becoming automated not just by the IT team, but also by the vendor that built the server or storage system. Of course, the automation being provided by the IT vendor only applies to their latest generation of infrastructure.

  • How to Manage Data in Hybrid Cloud Environments

    How to Manage Data in Hybrid Cloud Environments

    We’ve long-since established that multi-generational, multi-cloud environments are the new norm. But, how does one go about managing data in those environments?

    In this post, we’ll take a look at the ramifications of this hybrid cloud reality and best practices for managing your data for increased scalability and heightened availability.

    It’s All Cloud

    Whether it’s Amazon Web Services (AWS), Google Cloud or Microsoft Azure (or some combination thereof), cloud is all the rage, with a hybrid approach gaining momentum with 81% of cloud users working with two or more providers (according to a recent Gartner study). Not only does this strategy take companies out of the business of hosting their own applications, but it also leads to benefits such as avoiding vendor lock-in, reduced costs and optimized performance.

    Benefits to Mixing Cloud and On-Prem Environments

    Mixing cloud and on-prem environments means you can pick and choose where your workloads and data live—it’s really an optimization. For example, if your application is CPU intensive, you can run it on the cloud provider that gives you the most CPU for your dollar. Similarly, if your data workload requires significant storage, you can go to the cloud provider that offers the best bang for your buck on storage.

    Businesses should look at their application and database and then use the cloud provider that offers the best of class for that workload. A mixed cloud also gives you the ability to always have a low-cost secondary site recovery plan in place—you’re always ready to spin up on another cloud provider if you need to. 

    Managing Data: The Challenges of Hybrid Cloud

    The benefits of multi-cloud are many, but when it comes to managing your data, things can get tricky. Not only do you have multiple cloud providers to balance, you also have to consider data stored on-premises and how that data is accessed from the cloud. 

    You also have to consider data replication between clouds. If you’re not doing a full mirror of your data between each cloud, it’s critical you remain acutely aware of what data lives where. You’ll want to consider creating extensive documentation and diagrams of what data lives in which cloud. If you are replicating data between clouds, you also have to justify the additional operating and engineering cost to accomplish your goal. 

    How to Manage Data in Hybrid Cloud Environments

    Fortunately, there are several libraries providing abstractions for cloud services, such as object stores. Leveraging abstractions within your applications allows you to move more freely between cloud providers. 

    Companies should strongly consider storing their data in a consistent manner within each cloud, leveraging the same technologies to reduce the sprawl, maintenance and expertise required to operate those technologies. For example, use a relational database that all the cloud vendors provide—for data updated and changed frequently, it should live in the scope of the local cloud provider to reduce latency and network costs, because traffic within the cloud provider is generally free. If you were to write to a database outside the cloud provider, it’d cost more and be considerably slower.

    The leaders in the cloud provider space offer a fairly secure environment for storing sensitive data, as long as you’re following good practices and using your own source of encryption. However, it all comes down to your individual environment. For some organizations, there will be workloads that should remain on-premises—for instance, highly sensitive data for which regulations require on-premises storage.

    If data has to be stored and encrypted on-premises, many cloud providers offer a secure means of connecting your cloud environments to your on-premises environment for access to sensitive information, such as providing secure VPN connectivity to virtual private clouds. 

    Multi-cloud might not be for everyone; you have to weigh the benefits with the costs, especially as those factors relate to your individual organization. While there are pitfalls, the practices and tooling to effectively manage your data in hybrid cloud environments are all out there. Because so many of us are choosing to run our workloads on multiple clouds, collectively we’ve overcome many of the aforementioned challenges and can take advantage of all the benefits hybrid cloud provides.

  • Latest Version of Open Source IPFS Improves Performance

    Latest Version of Open Source IPFS Improves Performance

    The team behind the open source InterPlanetary File System (IPFS) announced this week that a significantly faster version of the peer-to-peer hypermedia protocol is now generally available.

    IPFS is a distributed file system that makes use of a global namespace to connect all computing devices. The fundamental difference between IPFS and other distributed file systems is a decentralized system of operators who hold a portion of the overall data, which serves to create a highly resilient system for storing and sharing files. Any operator on the network can serve a file by its content address, and IT teams can find and request content from any node using a distributed hash table (DHT).

    Molly Mackinlay, project lead for IPFS and a senior product manager for Protocol Labs, which provides protocols, systems and tools to improve how the internet works, said the latest 0.5 update to IPFS significantly improves the content routing performance in addition to adding support for the Transport Layer Security (TLS) protocol.

    IPFS can now also add files to the IPFS network twice as fast, in addition to performance improvements that have been made to the core file transfer mechanism.

    Finally, the mechanism for looking up mutable links is also faster and there is an experimental pubsub transport to speed up record distribution.

    Mackinlay said organizations such as Microsoft and Netflix are adopting IPFS to drive a number of distributed computing use cases. Netflix, for example, has been experimenting with IPFS as a way to distribute container images that is more efficient than employing repositories.

    IPFS won’t replace the need for traditional file systems as much as it does create an opportunity to employ a file system that makes distributed computing on a global scale more feasible. Microsoft, for example, uses IPFS as the content address storage layer to power its take on a decentralized identity system. In fact, Mackinlay noted IPFS has now been deployed on more than 100,000 nodes around the globe.

    It’s too early to say how broadly IPFS might be employed. Mackinlay said the community is still growing as IT organizations discover IPFS makes tasks ranging from fetching data to watching a video more efficient. As is the case with most open source projects, the adoption of IPFS is more likely to be driven by developers from the bottom up rather than IT managers from the top down. Developers trying to find a way to more efficiently distribute container images could, in theory, employ IPFS without anyone in the organization even knowing.

    Regardless of how IPFS finds its way into the enterprise, the need for more efficient ways to distribute files and content has become apparent. While data may be more distributed than ever, the laws of physics have not been suspended. As such, IT teams need to find a way to leverage IT infrastructure resources that are physically located as close as possible to the point where content is consumed. On one level, of course, that’s the role of a traditional content delivery network (CDN). However, given the cost of employing CDNs to distribute massive amounts of data, it might not come as a surprise that the open source community is exploring a much less expensive alternative.

  • NetApp Grabs CloudJumper to Manage Windows Desktops in the Cloud

    NetApp Grabs CloudJumper to Manage Windows Desktops in the Cloud

    NetApp today announced it has acquired CloudJumper, a provider of management tools for virtual desktops at a time when the rate at which Windows desktops are moving into the cloud is accelerating.

    Anthony Lye, senior vice president and general manager of NetApp’s Cloud Data Services business unit, said NetApp will primarily employ CloudJumper as a software-as-a-service application that complements the Windows Virtual Desktop (WVD) service provided by Microsoft on the Azure cloud. However, CloudJumper is also available on Amazon Web Services (AWS) and Google Cloud Platform.

    CloudJumper has also been rebranded as NetApp Virtual Desktop Service (VDS) on NetApp Cloud Central, a control plane for managing NetApp cloud services, and integrated with Azure NetApp Files and Cloud Volumes.

    Lye said that as NetApp extended the reach of its data management platforms into the cloud it became apparent even before the COVID-19 pandemic that large numbers of desktops were moving into the cloud, thanks to the general availability of WVD and end of life for support for Windows 7. The COVID-19 pandemic is serving as a catalyst to further accelerate that shift as organizations look to make their IT environments both more flexible and resilient, said Lye.

    As more desktops shift to the cloud, it then only becomes a matter of time before those virtual desktops create the need for additional NetApp data management services that already reside natively on cloud platforms such as Azure, he added.

    While there is general agreement that more desktops will be moving into the cloud, the rate at which that transition will occur is debatable, since many organizations have limited resources to invest in IT projects. However, Lye said there are also many organizations that will take this moment to accelerate their transition to the cloud.

    The one thing that is for certain is the number of desktops deployed locally will decline steadily in on-premises IT environments. End users may still have a local device, but the amount of compute power required to access Windows desktops in the cloud should be substantially less. That’s critical as more organizations also are abandoning traditional desktops in favor of mobile computing devices that enable end users to work from anywhere. In fact, it’s not even clear to what degree the IT professionals supporting virtual desktops will need to be in an office when the management tools being employed all reside in the cloud.

    Clearly, in terms of Windows deployments, the next year may be the most transformational in recent memory. The impact on IT professionals will be especially profound as the need to physically service individual endpoints becomes less required. Of course, the transition to virtual desktops has been a long time coming. More than a few organizations have embraced virtual desktop infrastructure (VDI) with mixed success. However, now that virtual desktops have gone mainstream in the cloud, many IT organizations will soon be wondering why it took so long to actually make that happen.

  • Chef Updates Tool for Managing IT Infrastructure as Code

    Chef Updates Tool for Managing IT Infrastructure as Code

    Chef today updated its tool for automating the management of IT infrastructure as part of an effort to further eliminate the need to rely on manual processes that generally fail to scale.

    John Wyss, vice president of product for Chef, said Chef Infra 16 adds a Unified Mode that provides a more streamlined means of executing policies and adds support for YAML, which means IT teams can now employ Chef to automate the management of infrastructure without having to write code.


    In addition, Chef has made it easier to update legacy instances of cookbooks built using Chef and added support for Arm processors.

    Interest in automating the management of IT infrastructure is expected to accelerate considerably in the wake of the economic downturn brought on by the COVID-19 pandemic. Many IT teams are likely to be considerably reduced in size. The remaining IT staff will need to automate the management of IT at much greater degrees than ever before. Much of that infrastructure soon may also be residing in a public cloud rather than in an on-premises IT environment.

    Of course, Chef is not the only way to automate the management of IT infrastructure. However, IT professionals who master Chef typically are able to create workflows that automate a wider range of tasks.

    As an early pioneer of using code to manage infrastructure, Chef has been making a case for employing the Ruby programming language to make it easier to manage IT infrastructure at scale. While adoption of Chef largely has been limited to IT professionals who could master Ruby, Wyss noted those individuals who have mastered Chef will be in much higher demand as organizations look for IT professionals who have the skills required to manage tasks that otherwise would have required a much larger staff.

    It remains to be seen to what degree IT professionals might embrace IT automation frameworks further. Many have developed their own scripts to automate a task. The challenge IT organizations have encountered is that those scripts are usually poorly documented and generally fail to scale. Automation frameworks provide a means to consistently manage IT infrastructure at scale in a way that is easily repeatable.

    In the meantime, the debate of who inside the IT organization will automate the management of infrastructure continues to rage. Some IT organizations want developers to be responsible for the entire stack as part of an effort to reduce headcount, while other organizations prefer to have developers for a variety of reasons focus all their energies on writing application code. Regardless of who automates the management of infrastructure, the one thing that just about everyone agrees on is that legacy processes for managing IT infrastructure that typically involve many rote mundane tasks are no longer the way to work.

    In fact, increased reliance on IT automation might accelerate the adoption of best DevOps practices because the frameworks required to automate the management of the underlying infrastructure might have been put in place already by the IT operations team, noted Wyss. Otherwise, the DevOps team itself has to put those IT automation frameworks in place with or without the help of the rest of the IT operations staff, which is a current state of affairs that many DevOps teams would just assume live without.

  • Commvault Deepens Ties With NetApp to Automate Data Protection

    Commvault Deepens Ties With NetApp to Automate Data Protection

    Commvault has extended its alliance with NetApp to make it possible to recover files nearly instantaneously from an all-flash memory array.

    Ranga Rajagopalan, vice president of product management for Commvault, said NetApp Scale-out Data Protection (SDP) from Commvault builds on its backup and recovery software to make it possible to use to NetApp hyperconverged infrastructure in combination with all-flash arrays running StorageGRID object storage software to now recover data stored on-premises or in the cloud.

    The on-premises capability is critical because it eliminates potential downtime in the event of a ransomware attack, Rajagopalan said, noting data can be recovered from an all-flash array residing on-premises using a scale-out architecture in a matter of seconds.

    At the same time, IT organizations can take advantage of an object storage system from NetApp that is compatible with the S3 application programming interface (API) to store data in the cloud, he added.

    Most IT organizations are by now aware the only way to combat ransomware is to be able to access a pristine copy of their data. The challenge they face, however, is finding a way to make that data accessible as fast as possible. It not only takes a significant amount of time to extract data from a cloud service, but it is also expensive. By keeping an organization’s most recent data available in an all-flash array locally, the time to restore data is sharply reduced, said Rajagopalan.

    Of course, organizations have been keeping copies of data on magnetic storage systems for years. However, as the cost of all-flash arrays continues to decline it’s now more affordable for organizations to consider employing much faster all-flash arrays to back up and recover their most mission-critical data, he added.

    Commvault also makes available application programming interfaces (APIs) through which the whole data protection process can be automated, he said.

    In the wake of the COVID-19 pandemic, there are two issues that many organizations are now struggling to manage. The first is the need to automate more processes at a time when many organizations will have smaller IT staffs. The number of IT personnel that can be dedicated to manually managing data protection tasks will be fewer during the economic downturn.

    At the same time, however, the number of ransomware attacks being launched continues to increase. All it takes is one mistake for an organization to find all its data encrypted. As a result, the relationship between data management and cybersecurity has become much tighter as organizations strive to ensure they always have a pristine copy of their data available.

    In the months ahead there is no doubt there will be a lot more focus on the total cost of IT operations. The challenge is, finding a way to reduce those costs must be balanced against the existing commitment to service level agreements (SLAs). The only way to meet those often-conflicting goals is to rely more on IT automation frameworks to make data always available, in a way that requires much less human intervention.

  • Deploying OpenStack: Pick a Distribution With These 7 Qualities

    Deploying OpenStack: Pick a Distribution With These 7 Qualities

    OpenStack, which turns 10 years old in July, remains the leading open source infrastructure component in private clouds. But, there is a plethora of OpenStack distributions out there, and selecting the right one is vital to the success of every organization’s OpenStack project.

    How do you know which is best? It’s an important question because, despite OpenStack’s popularity, companies often face serious challenges when adopting and deploying it. Put simply, OpenStack can be time-consuming and skill-heavy in order to deploy it, unless the chosen distribution is equipped to overcome those challenges.

    Thus, anyone planning to deploy OpenStack should make sure the distribution they pick meets the following seven criteria.

    Strong Economics

    Cloud environments are supposed to be more cost-efficient than proprietary hardware. That’s why enterprises love the cloud, after all. Therefore, the number one priority when choosing an OpenStack distribution is to make sure it can indeed reduce costs. That means steering clear of OpenStack platforms that are hard to deploy, maintain, upgrade and force you to struggle with basic operations. It’s also important that the distribution’s pricing model be clear and predictable so that organizations can plan expenses accurately.

    Totally Open Source 

    While OpenStack itself is open source, the installers provided by the vendors as part of their distributions often are not. This can lead to additional costs being applied to the licenses and situations where organizations are forced to pay for the distribution before even trying it out. Furthermore, all types of environments in use—including staging and development—need to be covered by the license, too. These pitfalls are sidestepped with OpenStack distributions that are 100% open source, providing better economics and flexibility for organizations.

    Predictable Release Cadence 

    While the release cadence of OpenStack is predictable and well documented, not all distributions follow the upstream quickly enough. Making sure the OpenStack distribution you choose supports the latest stable upstream release as soon as possible is crucial for a few reasons. The upstream release may have features that are important for the organization. Or there may be bug fixes that they feel are critical. Picking a downstream distribution with a predictable release cadence that stays in sync with the upstream ensures transparency and allows organizations to plan the upgrade process. 

    Long Support Runway

    Support services are essential for OpenStack production environments, especially when service level agreements (SLAs) apply. But, how long vendors will support older versions of OpenStack can vary. Though there is always an option to upgrade or re-deploy, there are times when it may be beneficial for organizations to stay with the current version. Thus, how long the vendor will provide support services is a key factor in choosing a distribution.

    Upgrades Made Easy

    There inevitably comes a time for most organizations when they want to upgrade their upstream OpenStack. However, OpenStack upgrades are known to be complex, and many commercial distributions do not support them. Even if they do, the process is complex and must be executed manually. Thus, choosing an OpenStack distribution that provides support for fully automated upgrades is essential for the success of the cloud operations team.

    Simplified Operations 

    Even after an OpenStack cloud is deployed, consideration must be given to the ongoing operations that can become complex and fragile. Maintaining the cloud on a daily basis includes operations such as scaling the cluster out or recovering it from failure. While most OpenStack distributions don’t provide mechanisms to simplify these tasks—forcing users to execute them manually—some do. Organizations should look to distributions that do a good job automating complex operational tasks, saving time and money.

    Flexible Technology Choices 

    OpenStack is a flexible cloud platform, supporting various hypervisors, software-defined networking (SDN) solutions and storage plugins. But many distributions are tied to a single stack. That means an organization may need to re-platform or move to a heterogeneous environment in the future. Avoid that trap by selecting a distribution that can adapt to work with new technologies.

    By looking for these seven qualities, organizations can get the most out of their OpenStack distribution and optimize the cloud infrastructure on which they increasingly rely.