Category: IT as Code

  • Can NetOps and SecOps Finally Get Along?

    Can NetOps and SecOps Finally Get Along?

    For years, the very definition of NetOps and SecOps has involved friction and even contentious relationships that make their respective jobs more difficult and lessen their efficiency and effectiveness. Much of this conflict originates from having charters that are seemingly in opposition to each other. At the surface, NetOps stands for connectivity, openness, speed and capacity. In contrast, SecOps comes across as binary opponents, posting for far too many regulations with segmented connectivity and a more or less closed or impaired environment.

    The truth is, however, both groups have the same goals:

    • Ensuring business operations and agility.
    • Protecting resources.

    The network is only important in its ability to connect users, systems, applications, information or data and other resources, ensuring effective business operations and agility. The network is means to an end, and not necessarily an end to itself. In a somewhat similar way, security is also not an end, but, rather, the means to an end. Security exists to protect these same users and resources. It’s all about the users and resources being able to run business operations effectively and with the agility and flexibility necessary to give it strategic advantages. Reflecting on this perspective may help NetOps and SecOps realize that they are not so far apart from each other.

    Both NetOps and SecOps struggle with many of the same issues. Both are usually overworked and understaffed, responsible for critical components or aspects of business, face constantly changing environments and challenges and slowed by cumbersome processes and a lack of agility. Because of these things, NetOps and SecOps are largely in the same boat, sharing the same storm.

    netops secopsThe lack of agility is a particularly important issue, as new technologies and techniques are constantly being developed that enable security teams to stay ahead of—or at least keep pace with—attackers. Motivated attackers tend to be far more innovative that defenders and can use anything at their disposal to accomplish their goals. Entire cybercriminal supply chains exist to provide attackers with applications, utilities, routines and even services to conduct their campaigns. These things can and will be used against defenders.

    On the other hand, deploying a new security solution on the network is generally a long, involved, cumbersome process. Even changing solutions involves considerable effort. Sometimes the rules or process gets invented along the way, compounding the difficulties. Additions or changes to the network involve tedious review processes mostly dictated by NetOps. The NetOps team also faces some of these same difficulties in adding or changing network management or monitoring solutions.

    While a careful review is warranted, current processes are too time-consuming and involved. One significant improvement can come from NetOps and SecOps coming together with an established and codified approach for network changes or additions. Getting issues out on the table for discussion is a great start. This means more collaboration and a joint learning cycle on short- and long-term organizational objectives. Both groups need to understand and appreciate the concerns of the other and realize their common ground. Prioritizing issues and agreeing on a fundamental set will ease the overall process, reduce unwarranted fear and antagonism, and eliminate much of the inventing the process on the fly.

    An emerging approach seeks to establish a centralized deployment point for both networking and security solutions with pre-established rules agreed upon by both teams. Ideally, many of the concerns can be addressed or mitigated by hardware and software designed to enforce policies or rules, provide failover as necessary, prevent performance degradation or add to the attack surface. These can allow solutions to drop into the network while offering guarantees of performance or availability.

    Streamlining deployment of shared management will result in much-needed agility and also boost efficiency and overall effectiveness. It will also lessen the typical tensions or outright opposition.

    NetOps and SecOps are much closer to each other than either realizes. Their shared guardianship of users and resources can benefit from joint discussions, plans, tools and policies. Not only can they better accomplish their own charters of connecting and protecting while providing agility and flexibility, but they also can become far more efficient with their operations. They need each other, and their organizations need the vital contributions from both. As typically said in security jargon, “A chain is only as strong as its weakest link.” The new paradigm of security-driven networking is about preventing weak links through the collaboration and synergy between NetOps and SecOps.

  • Cloud Is Red Hot in the COVID-19 Era

    Cloud Is Red Hot in the COVID-19 Era

    As digital transformation accelerates, cloud services are helping organizations thrive in a COVID-19 world

    As the days tick by and the gloomy ramifications of COVID-19 become more apparent, one harsh truth has become crystal clear: Industries that have invested in digital transformation stand a better chance of recovery and survival than others.

    The banking industry is a lighthouse example of this principle. Even though the brick-and-mortar branches have had to pull down shutters because of lockdowns and social distancing requirements, many banks have still operated their businesses as usual. They have kept the lights on and handled the pressure of increased online and mobile transactions thanks to cloud-based services.

    While the internet has been a key enabler for digital banking, cloud has become the backbone. Cloud is making IT infrastructure vanish. Cloud is where businesses render servers, churn and analyze data, and keep applications humming so they can collaborate with partners and customers.

    Many businesses are quickly turning around, moving at speed to adapt and transform their operations. YMCA, Planet Fitness and Nike are offering online fitness classes. Schools and colleges are providing online learning. The demand for Netflix and Amazon Prime has gone up dramatically, and both organizations are now easing telecom network congestion by lowering their bit rates. Online grocery retailers are attempting to keep pace with demand spikes. And working from home has gained momentum, sending the demand for routers, modems and data cards through the roof.

    We will see a slew of innovations like these in the coming months, from businesses big and small, that will bring cloud services into sharp focus with their need for scale in a COVID-19 world. Everyone is looking to the cloud to reimagine businesses and make collaboration happen on an unprecedented scale, and the cloud has proven its ability to respond with speed while remaining robust.

    While enterprise IT, governments, entrepreneurs and other organizations work on their plans to respond to crises, the focus should be on providing great user experience in the post-COVID-19 era. In regard to the cloud, enterprises should focus on the following key tactics to prepare accordingly:

    1. Scaling existing services: Applications currently hosted on-premises will move to the cloud. Extending the data center via software-defined data center solutions into hyperscalers will help achieve scale and business flexibility.
    2. Giving businesses ample wiggle room: By adopting a multi-cloud strategy, businesses can de-risk themselves against failure, capacity challenges and operational barriers.
    3. Extending and expanding geographical reach: This can be done by deploying applications to geo-specific cloud platforms.
    4. Going cloud-native: Design and develop new applications on PaaS using a DevOps approach for rapid rollouts.
    5. Strengthening the core strategy: The strategy should be to support rapid and unexpected changes in work and service consumption needs through optimal network bandwidth, VPN connectivity, bandwidth throttling, consumption-based adoption model, remote VDI as a service and SD-WAN based solutions.
    6. Investing in a heightened security posture: Cloud solutions should be based on data classification (privacy, availability) without sacrificing application, infrastructure, access or data security.
    7. Developing new working models: Address medium and long-term requirements with a hybrid support model and local onsite versus remote versus offshore support.

    Having achieved the above, enterprises would be wise to reduce their operations costs and channel the savings into new cloud initiatives. Enterprises should attempt to extend the life cycle of their existing assets before considering a refresh, while simultaneously moving to a subscription-based, pay-as-you-go model rather than footing steep licensing bills.

    But the cloud journey doesn’t end there. Goal-oriented and highly motivated businesses will use their cloud credits to support proofs-of-concept and other essential services. One way of doing this is to containerize applications and remediate end-of-life issues around OS, improving computing density and rationalizing OS licenses for cost savings. The other established route to achieve savings is to outsource value streams to trusted partners.

    COVID-19 is going to accelerate the cloud journey for scores of enterprises, and investments in the technology will quickly show their upsides—improved business resilience, cost control, and above all, the ability to keep the lights on.

  • VMware’s Blue Medora Buy Advances AIOps

    VMware’s Blue Medora Buy Advances AIOps

    VMware has announced it will acquire Blue Medora, a provider of a service for integrating data collected by IT monitoring tools, to expand its efforts to advance the adoption of artificial intelligence to automate IT operations (AIOps).

    Roy Ritthaler, vice president of cloud management for VMware, said Blue Medora provides VMware with a software-as-a-service (SaaS) platform that is employed to inform VMware vRealize, an IT automation suite that is now being used by more than 400 customers.

    The data Blue Medora collects will also be employed within Project Magna, a research and development initiative that applies machine learning algorithms and other forms of artificial intelligence (AI) to automate IT operations, he said. Project Magna is based on a reinforcement learning engine that automates the tuning of multiple sub-components of the overall IT environment, resulting in what VMware calls “self-driving data centers.”

    Ritthaler said the goal is not to replace IT professionals as much as it is to eliminate rote tasks while making it easier to manage increasingly complex IT environments at scale. It then will become feasible for a smaller number of IT professionals to manage hybrid cloud computing environments, he noted.

    Blue Medora’s True Visibility Suite provides VMware with visibility not just into IT infrastructure but also all the way up the application stack.

    Ritthaler said it’s only a matter of time before most management frameworks are accessed as service, given all the data that needs to be collected and then analyzed to surface meaningful insights. It’s not clear how roles with IT organizations will evolve once those insights are surfaced regularly. Most enterprise IT organizations today rely on multiple specialists to optimize all the components that make up the IT environment. In theory, AIOps will make it possible for IT generalists to manage an IT environment without having to rely on so many specialists.

    AIOps undoubtedly will also have a profound impact on DevOps processes. As more IT operations become automated, the amount of time and effort spent managing IT infrastructure should decline.

    Interest in IT automation is on the rise in the wake of the COVID-19 pandemic. With many IT professionals working from home as much as possible, organizations are looking to automate rote IT processes to make them easier to manage remotely. In many cases, achieving that goal will require IT teams to rely more on tools that are accessed as a cloud service.

    Regardless of the path forward, it’s apparent the management of IT is about to be utterly transformed.

    It’s not that IT organizations will suddenly have a greater appreciation of IT automation. However, the pandemic has added more urgency to an IT transition that was already underway prior to the pandemic. The issue now is not so much whether to embrace IT automation as it is determining what can be automated for a consistent outcome across IT environments that frequently are made up of a diverse yet not especially well-integrated range of platforms.

  • Fastly Facilitates Observability at the Edge

    Fastly Facilitates Observability at the Edge

    Fastly this week announced it is adding the ability to collect tracing, customizable logging data and both real-time and historical metrics from a serverless computing framework designed to be deployed on edge computing platforms.

    Company CTO Tyler McMullen said the goal is to make it easier for IT to bring observability within the context of a DevOps to an edge computing platform.

    The Compute@Edge serverless compute platform enables IT teams to employ functions to execute code on an edge computing platform versus having to install virtual machines or containers. Those edge computing platforms are connected to a content delivery network (CDN) managed by Fastly.

    McMullen said that approach provides a way to deploy microsecond applications at the edge while still attaining observability in keeping with best DevOps practices. Otherwise, edge computing platforms become yet another black box that provides IT teams with no visibility.

    DevOps teams can send real-time logs to 27 and counting supported endpoints. Default log fields are automatically exposed to better determine the root cause of any issue. DevOps teams can also capture custom event details.

    Metrics such as CPU and RAM utilization can also be surfaced either in real-time or on a historical basis. The Compute@Edge service also honors request tracing parameters by maintaining them when they enter and leave the Fastly platform. Developers can tag individual end user requests with unique identifiers that can be shared with third-party platforms such as Datadog.

    Currently available in beta, Compute@Edge makes it easier for IT teams to employ a serverless computing framework to drive event-driven applications at the edge, McMullen said. Latency issues that arise when applications attempt to access cloud services are pushing more organizations to deploy real-time applications at the network edge. Functions running on a local serverless computing platform enable IT teams to achieve that goal in a way that consumes the smallest amount of IT infrastructure possible, he added.

    With the rise of 5G networking services, it’s now only a matter of time before the number of platforms on which a DevOps team needs to deploy code expands significantly. Most DevOps teams are already challenged by all the unique platforms to which need to deliver code. Edge computing could potentially exacerbate those issues because each edge computing platform tends to have unique attributes. A common serverless computing framework running on each of those edge computing platforms could help streamline continuous delivery.

    Of course, it’s too early to say what impact the downturn on the economy will have on edge computing projects. In theory, at least, organizations are gearing up to deploy these applications in anticipation of wireless 5G connectivity services being widely available and affordable. Chances are high, however, with more organizations not willing to send people to install applications on those endpoints manually, reliance on DevOps processes and CDNs to automate application delivery at the edge will become a requirement.

  • Survey Finds IT Teams Rising to COVID-19 Challenge

    Survey Finds IT Teams Rising to COVID-19 Challenge

    In many ways, the COVID-19 pandemic has been the ultimate test for IT teams. The bulk of many workforces overnight became remote workers. Many of those end users are now starting to return to the office, but no one knows for sure if they will be sent back home again because of another flare-up.

    A survey of 519 IT professionals conducted by ManageEngine, a provider of IT service management (ITSM) software, suggest most IT teams have risen to the COVID-19 challenge. According to the survey results, 85% of respondents said they were equipped with the right remote-support equipment or were able to procure it quickly to enable a productive remote work environment. In addition, 83% of respondents said they believe IT will be better appreciated in terms of budgets, salaries and recognition in the wake of the COVID-19 crisis.

    Overall, nearly three-quarters (72%) said the ITSM tools continue to be effective despite remote work conditions. For example, 40% cited knowledge management as their greatest challenge, while just over 50% noted that prior to the pandemic Bring Your Own Device (BYOD) policies were non-existent in their organizations.

    In terms of mobile computing devices, only 32% said they were already providing them. Nearly half (47%) are now planning to provide them.

    Self-service support options aren’t being used by 28% of the organizations, and of those who do use them only 40% found they truly helped. Among the respondents who use chatbots for their self-service, 50% found them beneficial for remote support. Only 7% of respondents felt that the service desk wasn’t up to meeting the remote IT support challenges that the pandemic presented.

    In addition, only 40% said they are equipped to tackle the increase in security and privacy concerns that result from more employees working outside the office.

    Cloud services were also critical, with more than half of respondents (53%) saying such services helped their organization’s business continuity. However, 20% of respondents said they did not have a business continuity or disaster recovery plan in place for emergency situations. Among those who had them, 50% were happy with those plans. Almost a third (29%) of respondents admitted they did not do enough prior testing of their action plan.

    A fifth of respondents also noted shadow IT is impacting services and applications, while nearly a third said they were unsure.

    Pradyut Roy, a product manager for ManageEngine, said it’s apparent many IT organizations will need to update IT policies and processes in the wake of the pandemic. It’s also probable the IT environment will become more heterogeneous in the wake of the pandemic as, for example, more desktops move into the cloud, said Roy.

    In general, IT teams will need to adjust to a much more fluid IT environment. Many more end users will be rotating in and out of the office to enable organizations to comply with social distancing mandates. Regardless of what the new normal becomes, however, it should be apparent to all by now that IT will play a more central role in most business decisions from here on out.

  • Commvault Extends Data Protection Alliance with Microsoft

    Commvault Extends Data Protection Alliance with Microsoft

    Commvault and Microsoft are extending their existing relationship to integrate Commvault’s data protection software with Azure Blob Storage.

    Azure Blob Storage is a service based on object-based storage optimized for unstructured data. Commvault last year launched the Metallic software-as-a-service (SaaS) platform, which provides a cloud-based approach to managing data protection, that runs on Azure.

    The two companies have pledged to extend that relationship to not only align engineering efforts but also enable their partners to more easily resell both Metallic and Azure cloud services under the same user contract.

    Manoj Nair, general manager for the Metallic service, said the Commvault offering presents IT administrators with a simple graphical user interface (GUI) and exposes application programming interfaces (API). That latter capability enables DevOps teams to automate the backup and recovery process via a cloud service, said Nair.

    Rather than having to rely on an IT administrator, the API enables DevOps teams to remove friction from the data protection process, he noted.

    The bulk of data protection processes are still managed by IT administrators. However, as DevOps processes continue to mature, data protection processes are becoming more automated. Developers not only want to be able to instantly recover data in the event of system failure but they also often use data protection tools to move data into and out of cloud computing environments.

    Nair said Commvault opted to extend its relationship with Microsoft in part because the amount of data being stored in the Azure cloud continues to expand exponentially as more organizations adopt Microsoft Office 365, Microsoft Teams and low-code applications built using Microsoft PowerBuilder tools. Collectively, those applications increase the amount of data gravity the Microsoft Azure cloud exerts. As the amount of data increases in the Azure cloud, the number of applications looking to access that pool of data increases steadily. As that data continues to grow, Nair said there will be a greater need for tools to protect that data.

    In general, Nair said many organizations underappreciate the need to back up and recover data stored by cloud service providers. The assumption is the cloud service provider will make it possible to recover data in the event of failure. In reality, cloud computing is based on a shared responsibility model between the end customer and the cloud service provider, under which responsibility for data protection—along with all other data management functions—belongs to the end customer.

    Of course, there is no shortage of data protection tools available. Many of those relied on today reside in an on-premises IT environment. In the wake of the COVID-19 pandemic, interest has grown regarding shifting data management tools to SaaS platforms that are more accessible. The issue many IT organizations will need to decide next is whether they want to rely on dedicated IT administrators to manage those processes versus reducing costs by employing APIs to automate a set of routine tasks that no one in IT especially enjoys managing.

  • How to Overcome Challenges With AWS Lambda Logging

    How to Overcome Challenges With AWS Lambda Logging

    Monitoring AWS Lambda can be a complex and potentially costly endeavor. Here’s what you need to know to stay on track and on budget

    Organizations are already experiencing a shift toward serverless cloud computing. According to the O’Reilly “Serverless Survey 2019,” around 40% of respondents said they had implemented serverless architecture. Forrester “Global Business Technographics” Developer 2019 found that 49% of companies are using it or planning to use it in the next 12 months.

    AWS leads the way in this space. According to Serverless.com, 96% of respondents choose AWS Lambda over Azure Functions and Google Cloud Functions. AWS Lambda helps us to design a lightweight and robust application architecture that can be built and deployed without any hassle. However, nothing comes for free. There are several, potentially costly, complexities when monitoring AWS Lambda. Fortunately, there is an array of solutions.

    Logging

    By default, AWS Lambda’s stdout and stderr messages are sent to CloudWatch Logs, where every function has its log group. A log group is a collection of log streams (sequence of log events) that can be stored as long as you want. Storage of logs costs USD 0.03/GB and data ingestion costs around USD 0.50/GB.

    It is common practice to break up your Lambdas into single responsibility functions. This means, for example, if you need one Lambda to read a certain object and another to write it, you’re setting up two separate functions. However, this also means two log groups.

    This creates a challenge when you want to analyze your application’s output log. There is no direct way to log queries across multiple log groups. In response to this, AWS enabled CloudWatch Log Insights to conduct cross-log querying. While this brought many of the improvements users wanted and needed, analyzing multiple log groups together meant a higher cost for queries. This prohibitive cost model encouraged many to look to external services.

    Tracing

    AWS X-Ray enables you to trace the underlying components of your application and helps you to dig out the fundamental reason behind distributed issues. It has quickly become an essential troubleshooting and optimization tool for engineers.

    For example, cold start latency can be problematic for AWS Lambda functions with slow startup times. Although you can counter this by enabling Provisioned Concurrency, you will need to pay extra.

    If you have budget constraints and still want to resolve the issue, X-Ray might help you eliminate or at least optimize your application by removing the bottleneck. It lets you know, among other things, if your application is consuming more time during initialization or invocation. You can find X-Ray SDK on AWS Lambda for Go, Java, Node.js, Python and .NET.

    Debugging

    Traditional architecture and serverless architectures are as different as day and night. Serverless requires changes across the software engineering spectrum, including debugging.

    A serverless application is a combination of various services or resources within infrastructure, which can include tools such as AWS API Gateway, CloudWatch and SNS. Such distribution of web services helps avoid a single point of failure (SPOF), but this design creates a problem. Debugging or replicating an issue on a local machine is not always feasible, and debugging a production application is always a dangerous proposition.

    Moreover, the abstraction of AWS Lambda makes debugging complicated, as you don’t have direct access to the underlying OS. Hunting down dispersed logs adds to this overhead. As your serverless infrastructure scales, it becomes difficult to identify the root cause.

    To combat this, developers can use AWS native tools such as CloudWatch, X-Ray or Serverless Application Model (also known as SAM). Any of these tools on their own can be difficult to use; together, however, they form a powerful debugging suite.

    Outside of the AWS-native toolset, some tools provide further assistance with debugging. For example, the Serverless framework, which is an open source tool to develop and deploy serverless applications over AWS, lets you see your live application’s function log, for example:

    Monitoring

    Robust monitoring ensures the smooth operation of an application and helps to detect issues quickly. In traditional infrastructure, metrics only appear from a handful of sources, so collecting them together is less of a challenge. In a serverless architecture, this problem is much more complex.

    AWS gives you the freedom of converting CloudWatch Logs to metrics. These metrics can be filtered, measured and, when a threshold is crossed, alerted on. You can define a metric filter by choosing a log group created by your serverless function and target the log stream. This enables you to create a visual reference for your log events. Every custom metric you create will cost $0.30/10000 metrics per month.

    Metric filters can be a powerful tool, but it can also be a bit overwhelming to set up everything, and there are certain bottlenecks as well. For instance, you can’t parameterize metric names, which forces you to create a filter for every custom metric you want to track. There is also a hard limit of 100 metric filters per log group, which restricts you as your application evolves.

    Other than this, AWS resources are tightly coupled with each other, which makes AWS-native monitoring tools a fine choice when you need to monitor individual AWS resources or Lambda functions. To get an infrastructure-wide view and to monitor other third-party tools, a centralized logging approach is necessary to take full advantage of the log data.

    Conclusion

    There is no denying that serverless tooling quickly unlocks high availability, scalability and cost optimization. To make the most of this new paradigm, engineers need to build a robust and reliable monitoring system. The ability to manage log data streaming from many components, detect and trace issues on the fly, and deliver accurate insights to keep on improving the application is crucial to remain online and competitive.

    While serverless solutions give access to many of the technical features we need, the dangers of vendor lock-in and the power of third-party providers must be considered if you want to scale your organization and its infrastructure smoothly.

  • DevOps Deeper Dive: Apple Adds Fuel to ITSM Fire

    DevOps Deeper Dive: Apple Adds Fuel to ITSM Fire

    Apple’s acquisition this week of Fleetsmith, a provider of IT service management (ITSM) tools for Apple devices, is reigniting a fierce debate over how best to manage endpoints in heterogeneous IT environments.

    Fleetsmith, along with rivals including Jamf Software and IBM, provides ITSM tools that only manage Apple devices. The company argues that the IT teams managing Apple devices prefer to use tools that feel like MacOs or iOS applications. However, both enterprise environments typically have both Apple and Windows devices. As such, many IT teams have adopted ITSM tools that allow them to centrally manage both platforms.

    Until now, Apple has been relatively neutral in terms of how best to manage its devices. The acquisition of Fleetsmith signals the company is about to focus more on ITSM at a time when many organizations need to revamp their approach to managing endpoints in the wake of the COVID-19 pandemic.

    With more individuals likely to be spending more time working from home, the management of highly distributed endpoints becomes even more challenging. Apple has yet to outline its plans for Fleetsmith or say whether it will continue to support Fleetsmith customers. The assumption is the company will incorporate the Fleetsmith ITSM tools into its portfolio.

    Mac and Windows: Can’t We All Get Along?

    In the meantime, providers of platforms capable of managing heterogeneous endpoints are pressing their cases for increased centralization. Many IT organizations have adopted separate tools for managing Windows and Apple devices; centralizing the management of endpoints presents those organizations with an opportunity to reduce costs.

    “IT teams don’t want to hop around infrastructure, said Greg Keller, CTO for JumpCloud, a provider of ITSM tools. “Centralization creates this single-pane-of-glass efficiency.”

    The need to centralize endpoint management will become even more pronounced as desktop computing moves into the cloud, added Pradyut Roy, a product manager for ManageEngine, a provider of ITSM tools that also span multiple types of endpoints.

    “There is going to be a huge drive to centralize the control plane,” said Roy.

    A survey of 519 IT professionals published this week by ManageEngine finds 47% of organizations are planning to provide more mobile-capable assets to employees. As those endpoints are rolled out, IT teams will need ITSM platforms accessible from anywhere that enable them to manage devices regardless of what network they are connected to at any given time.

    Apple doesn’t have the greatest reputation when it comes to appreciating ITSM requirements in the enterprise. For example, it often changes application programming interfaces (APIs) in ways that are not backward-compatible, so providers of ITSM tools often must make significant updates to their tools. That API issue is likely to become even more significant as organizations that have adopted best DevOps practices look to extend them to applications running on Apple devices.

    ITSM is clearly in a state of flux. Most IT organizations rely on legacy ITIL-based processes to manage IT infrastructure consistently. As businesses begin to require more flexibility, many of those ITIL-based processes will need to be revisited. The opportunity—and the challenge—now is finding a way to converge ITIL and DevOps practices across as many different types of endpoints as possible.

  • Red Hat Extends Reach of Ansible Automation Framework

    Red Hat Extends Reach of Ansible Automation Framework

    Red Hat this week launched a collection of downloadable workflows for automating IT processes that will be made available via the Ansible Automation Hub.

    At the same time, Red Hat has updated the Red Hat Ansible Automation Platform to add an automation services catalog to keep track of workflows and a return on investment (ROI) calculator that enables IT teams to determine which workflows are the most valuable based on usage.

    Red Hat also updated the core Red Hat Ansible Tower automation engine to streamline processes and reduce bottlenecks.

    Tom Anderson, vice president for the Red Hat Ansible Automation Platform at Red Hat, said Red Hat Certified Ansible Content Collections includes workflows from Red Hat and vetted third-party providers. As such, IT teams employing Ansible to automate the management of IT can have confidence these playbooks and workflows are both secure and supported, he said.

    Red Hat decided to separate the management of Ansible workflow content from the underlying platform because it’s become apparent new workflows are being made available at a faster cadence than updates to the core Red Hat Ansible Automation Platform, he noted.

    As part of that effort, Red Hat this week is also making available additional automated workflows that leverage Red Hat Tower to automate tasks and jobs via a centralized console, along with workflows that leverage Red Hat Satellite systems management software and the Red Hat Insights monitoring service.

    Anderson said interest in IT automation has expanded significantly in the wake of the economic downturn brought on by the COVID-19 pandemic. Many organizations have either frozen IT headcount or been forced to reduce the size of their IT staff. However, managing IT environments continues to grow more complex as emerging technologies such as microservices and Kubernetes clusters gain momentum.

    Some organizations may, of course, opt to put a hold on adopting new platforms, but just as many are continuing to invest in cloud-native technologies necessary to drive digital business transformation initiatives, which require applications that are both more flexible and resilient. Because of that, Anderson said, the urgency surrounding IT automation project has increased.

    In fact, he noted, Red Hat has created “office hours” during which the company provides IT teams with access to Red Hat personnel at specific times to provide additional guidance.

    As an open source project, Ansible is gaining traction as a management framework because it provides a declarative approach to automating IT that doesn’t require IT operations teams to learn how to code. Ansible is also being embraced by IT infrastructure providers including Cisco Systems and Dell Technologies, which makes it easier for IT teams to create playbooks that automate tasks across multiple platforms. Over time, those cross-platform capabilities foster the creation of an ecosystem that further increases Ansible momentum, Anderson noted.

    There’s no doubt IT teams were increasing their reliance on IT automation frameworks prior to the pandemic. Now, however, automating the management of IT is not just about increasing productivity and efficiency; in many cases, it’s become a matter of survival.

  • Nebulon Unveils Hybrid Cloud Computing Platform

    Nebulon Unveils Hybrid Cloud Computing Platform

    Nebulon has emerged from stealth to launch a hybrid cloud computing platform that enables workloads to be processed in the cloud while data continues to be stored on a local application server.

    Company COO Craig Nunes said the Cloud-Defined Storage platform employs PCIe cards embedded with a Nebulon Services Processing Unit (SPU) based on an ASIC to connect local storage systems to a cloud-based control plane dubbed Nebulon ON that can span Amazon Web Services (AWS) and Google Cloud Platform (GCP) services.

    The PCIe card is installed in an application server residing in a local data center, where it connects to solid-state drives (SSDs) installed on the server. The Nebulon SPU offloads compression, encryption, deduplication, erasure coding, snapshots and data mirroring.

    The Nebulon SPU also transmits storage, server and application metrics to Nebulon ON, where machine learning algorithms are applied to surface recommendations to improve performance.

    Nunes said both Hewlett Packard Enterprise (HPE) and Supermicro have already agreed to resell the Cloud-Defined Storage platform.

    At its core, the Cloud-Defined Storage platform takes hyperconverged infrastructure (HCI) to another level. Instead of combining compute and storage in a local data center, however, compute processing is shifted to the cloud, said Nunes. That approach, he noted, makes it possible to take advantage of inexpensive compute resources in the cloud without losing control over data.

    In addition, Nunes noted, the Cloud-Defined Storage platform ensures application service levels are maintained while reducing costs by eliminating the need to transfer massive amounts of data into and out of the public cloud.

    Organizations that work within highly regulated industries can now take advantage of cloud resources while continuing to meet compliance requirements, he added.

    Finally, the Nebulon Cloud-Defined Storage platform can support both monolithic and microservices-based applications regardless of the type of virtual machine or container employed.

    At a time when many organizations are under increased pressure to reduce the total cost of IT, there’s a lot more interest in ways to leverage cloud computing to reduce costs. However, for many organizations, moving data into the cloud is problematic for a host of performance, security and compliance issues.

    A hybrid cloud computing architecture that doesn’t require data to be stored or moved into and out of a cloud could provide a way for organizations to re-evaluate their overall cloud computing strategies. Organizations beyond those in highly regulated industries could conclude they would prefer to retain control over their data.

    Cloud service providers are, of course, banking on massive amounts of data being stored in the cloud. They have long argued that as the amount of data stored in the cloud exponentially increases, the more sense it makes to deploy applications in the cloud as close as possible to that data. Each new application deployed in the cloud then increases the amount of data gravity that cloud exerts on other application deployment decisions.

    It’s not likely hybrid cloud platforms such as the Nebulon Cloud-Defined Storage system will completely reverse that trend. However, it does signal that data gravity in the cloud may not be as inexorable a force as many cloud service providers have long assumed.