openstack case study

Exploring OpenStack cloud case studies

Opensource.com

During the course of the last twelve months, the OpenStack community has advanced as more users of the leading open source cloud technology have been reporting their progress—with the help of their partners—towards making a meaningful impact on their business goals and objectives.

We've also learned how these progressive technology users are pioneering changes in their own organizations—enabling them to become more competitive in the global networked economy.

The OpenStack Summit 2014 opened with a keynote on the first day of the conference featuring lessons learned from industry leading organizations that have already deployed these open cloud technologies. Each case study had multiple instances of OpenStack that have been applied for a variety of commercial application scenarios.

Jonathan Bryce, the Executive Director of the Foundation, introduced the growing community of  OpenStack Superusers . Glenn Ferguson, Head of Private of Cloud Enablement at Wells Fargo Bank, and Chris Launey, Director of Cloud Services & Architecture at the Walt Disney Company, described their IT environment and how they’ve adopted OpenStack as a solution to their company’s varied cloud infrastructure requirements.

Addressing the needs of enterprise workloads is only part of the evolving adoption story told at this year’s Summit. Several broadband service providers are also early adopters of OpenStack.

How network operators apply OpenStack platforms

During a lunch session on the same day, Fernando “Fred” Oliveira, cloud architect at Verizon, described his experience building OpenStack clouds. He explained how the company’s network is growing faster than they can monetize the infrastructure, and so they’re looking at open source technology as a way to proactively control costs—but their motivation goes beyond bottom-line savings.

Verizon will use OpenStack as a key enabler of its go-to-market business strategy—essentially compressing the time it typically takes them to reach significant new service revenue attainment.

Moreover, Verizon looked to this rapidly evolving software technology as a way to become more agile—from the initial service launch to the ongoing operational requirements. They have been a pioneer of  Network Functions Virtualization  (NFV), and OpenStack became a natural choice to use within their numerous proof-of-concept tests and ongoing pilot projects over the last year.

Exploring the full potential of NFV applications

On the second day of the OpenStack Summit Toby Ford, Assistant VP, IT Operations Strategic Realization at AT&T, described his personal experience with cloud offerings—both internally and externally focused. He started his talk by disclosing that when he first arrived at AT&T (as part of an acquisition) “open source was pretty much forbidden.” Today, it’s an integral part of their IT strategy.

The commitment to explore NFV is an example of their evolving strategy in action—and the company’s contribution to the OpenStack community. In fact, Ford said that the adoption of OpenStack has become a somewhat unique proxy to introduce more innovation into their DevOps process. Moreover, he sees a tremendous value in the ecosystem that has formed around this open source cloud technology.

AT&T first introduced OpenStack in their lab environment during 2010. Moving quickly, they had already progressed to production workloads by the end of 2011. Today, they have approximately 120 applications deployed on OpenStack. The platform has been deployed in seven data centers. At the end of 2014, it’s anticipated that three more data centers will join those in production.

The  virtualization use cases  have expanded from the more typical back-end applications to now include new things—such as Big Data usage scenarios. Over the next two years, AT&T plans to expand their deployment from 10 to 20 data center sites. Why so many locations? Ford says it’s all being driven by the promise of NFV—particularly within the mobility systems arena.

Why open source is now pervasive

Keeping in mind that AT&T is experiencing aggressive new competition from outside of their traditional realm, Ford acknowledged that the company’s executive leadership knows that they must change—and OpenStack is seen as a catalyst to rapidly advance a flexible and agile DevOps environment.

As an example of key areas of innovation, Ford pointed to the opportunities to transform how video entertainment content is stored and eventually delivered to AT&T U-verse customers. By going beyond prior constraints of the legacy vertically integrated infrastructure model, AT&T will be able to re-engineer their network architecture. This will allow them to distribute both key functions and multimedia content—thereby placing them much closer to the ultimate user.

Ford believes that the inherent capabilities of Cinder and Neutron will enable AT&T to have a more productive relationship with infrastructure vendors – leveraging the peer pressure within the ecosystem that naturally drives all vendors to produce high-quality code that works and scales as intended.

In addition to direct benefits, OpenStack adoption is also helping Ford and his team to propagate agile methods throughout AT&T’s vast IT organization. Besides, there has been a trickle-down effect from the early results. Now, AT&T has looked more closely at Software Defined Networking (SDN), and Ford says that he’s really excited by the opportunity to advance substantive change in the core network.

Ford believes that it’s the federation—the binding cohesion—that will ultimately make OpenStack succeed. Granted, there are recognized challenges in a number of key areas, but Ford is confident that the current path for OpenStack is both sound and stable. He anticipates more forward-thinking service providers, globally, will follow the lead of the early adopters. The positive impact is truly remarkable.

Comments are closed.

Related content.

• View source
• Create a book
• Download as PDF
• Printable version
• Page information
• Permanent link
• Special pages
• Related changes
• What links here
• Create account
• Log in / create account with OpenID
• User Stories
• Documentation

OpsGuide/Use Cases

This appendix contains a small selection of use cases from the community, with more technical detail than usual. Further examples can be found on the OpenStack website .

• 1.1 Deployment
• 1.2 Resources
• 2.1 Deployment
• 2.2 Resources
• 3.1 Deployment
• 3.2 Resources
• 4.1 Deployment
• 4.2 Resources

Who uses it: researchers from the Australian publicly funded research sector. Use is across a wide variety of disciplines, with the purpose of instances ranging from running simple web servers to using hundreds of cores for high-throughput computing.

Using OpenStack Compute cells, the NeCTAR Research Cloud spans eight sites with approximately 4,000 cores per site.

Each site runs a different configuration, as a resource cells in an OpenStack Compute cells setup. Some sites span multiple data centers, some use off compute node storage with a shared file system, and some use on compute node storage with a non-shared file system. Each site deploys the Image service with an Object Storage back end. A central Identity, dashboard, and Compute API service are used. A login to the dashboard triggers a SAML login with Shibboleth, which creates an account in the Identity service with an SQL back end. An Object Storage Global Cluster is used across several sites.

Compute nodes have 24 to 48 cores, with at least 4 GB of RAM per core and approximately 40 GB of ephemeral storage per core.

All sites are based on Ubuntu 14.04, with KVM as the hypervisor. The OpenStack version in use is typically the current stable version, with 5 to 10 percent back-ported code from trunk and modifications.

• OpenStack.org case study
• NeCTAR-RC GitHub
• NeCTAR website

Who uses it: researchers from the MIT Computer Science and Artificial Intelligence Lab.

The CSAIL cloud is currently 64 physical nodes with a total of 768 physical cores and 3,456 GB of RAM. Persistent data storage is largely outside the cloud on NFS, with cloud resources focused on compute resources. There are more than 130 users in more than 40 projects, typically running 2,000–2,500 vCPUs in 300 to 400 instances.

We initially deployed on Ubuntu 12.04 with the Essex release of OpenStack using FlatDHCP multi-host networking.

The software stack is still Ubuntu 12.04 LTS, but now with OpenStack Havana from the Ubuntu Cloud Archive. KVM is the hypervisor, deployed using FAI and Puppet for configuration management. The FAI and Puppet combination is used lab-wide, not only for OpenStack. There is a single cloud controller node, which also acts as network controller, with the remainder of the server hardware dedicated to compute nodes.

Host aggregates and instance-type extra specs are used to provide two different resource allocation ratios. The default resource allocation ratios we use are 4:1 CPU and 1.5:1 RAM. Compute-intensive workloads use instance types that require non-oversubscribed hosts where cpu_ratio and ram_ratio are both set to 1.0. Since we have hyper-threading enabled on our compute nodes, this provides one vCPU per CPU thread, or two vCPUs per physical core.

With our upgrade to Grizzly in August 2013, we moved to OpenStack Networking, neutron (quantum at the time). Compute nodes have two-gigabit network interfaces and a separate management card for IPMI management. One network interface is used for node-to-node communications. The other is used as a trunk port for OpenStack managed VLANs. The controller node uses two bonded 10g network interfaces for its public IP communications. Big pipes are used here because images are served over this port, and it is also used to connect to iSCSI storage, back-ending the image storage and database. The controller node also has a gigabit interface that is used in trunk mode for OpenStack managed VLAN traffic. This port handles traffic to the dhcp-agent and metadata-proxy.

We approximate the older nova-network multi-host HA setup by using “provider VLAN networks” that connect instances directly to existing publicly addressable networks and use existing physical routers as their default gateway. This means that if our network controller goes down, running instances still have their network available, and no single Linux host becomes a traffic bottleneck. We are able to do this because we have a sufficient supply of IPv4 addresses to cover all of our instances and thus don’t need NAT and don’t use floating IP addresses. We provide a single generic public network to all projects and additional existing VLANs on a project-by-project basis as needed. Individual projects are also allowed to create their own private GRE based networks.

• CSAIL homepage

Who uses it: DAIR is an integrated virtual environment that leverages the CANARIE network to develop and test new information communication technology (ICT) and other digital technologies. It combines such digital infrastructure as advanced networking and cloud computing and storage to create an environment for developing and testing innovative ICT applications, protocols, and services; performing at-scale experimentation for deployment; and facilitating a faster time to market.

DAIR is hosted at two different data centers across Canada: one in Alberta and the other in Quebec. It consists of a cloud controller at each location, although, one is designated the “master” controller that is in charge of central authentication and quotas. This is done through custom scripts and light modifications to OpenStack. DAIR is currently running Havana.

For Object Storage, each region has a swift environment.

A NetApp appliance is used in each region for both block storage and instance storage. There are future plans to move the instances off the NetApp appliance and onto a distributed file system such as Ceph or GlusterFS.

VlanManager is used extensively for network management. All servers have two bonded 10GbE NICs that are connected to two redundant switches. DAIR is set up to use single-node networking where the cloud controller is the gateway for all instances on all compute nodes. Internal OpenStack traffic (for example, storage traffic) does not go through the cloud controller.

• DAIR homepage

Who uses it: researchers at CERN (European Organization for Nuclear Research) conducting high-energy physics research.

The CERN OpenStack cloud environment is based on CentOS 7, which is Red Hat compatible. KVM is used throughout as the hypervisor with Ceph providing block storage via RBD and file shares with CephFS.

We use the Puppet Labs OpenStack modules to configure Compute, Image service, Identity, and dashboard. RPMs are derived from the Red Hat RDO distribution. Puppet is used widely for instance configuration, and Foreman is used as a GUI for reporting and instance provisioning. Monitoring is provided using collectd and displays using Grafana.

Users and groups are managed through Active Directory and imported into the Identity service using LDAP. Access to the cloud resources is provided through Horizon and also using Kerberos/X.509 for command line access with the openstack unified command line tool.

The largest OpenStack cloud at CERN is around 287,000 cores provided by over 8,500 hypervisors running in two data centres.

• CERN Blog on OpenStack experiences
• Review of CERN Data Centre Infrastructure from 2012
• CERN Cloud Infrastructure User Guide
• Privacy policy
• About OpenStack
• Disclaimers

Dissecting open source cloud evolution: An openstack case study

Open source cloud platforms are playing an increasingly significant role in cloud computing. These systems have been undergoing rapid development cycles. As an example, OpenStack has grown approximately 10 times in code size since its inception two and a half years ago. Confronting such fast-pace changes, cloud providers are challenged to understand OpenStack’s up-to-date behaviors and adapt and optimize their provisioned services and configurations to the platform changes quickly. In this work, we use a black-box technique for conducting a deep analysis of four versions of OpenStack. This is the first study in the literature that tracks the evolution of a popular open source cloud platform. Our analysis results reveal important trends of SQL queries in OpenStack, help identify precise points for targeted error injection, and point out potential ways to improve performance (e.g. by changing authentication to PKI). The OpenStack case study in this work effectively demonstrates that our automated black-box methodology aids quick understanding of platform evolution and is critical for effective and rapid consumption of an open-source cloud platform.

Publication

• Salman A. Baset
• Chunqiang Tang
• Byung Chul Tak

Toward achieving operational excellence in a cloud

Open source cloud technologies, pem: a framework enabling continual optimization of workflow process executions based upon business value metrics.

• Workshop Organizers
• Registration Information
• Registration Discounts
• At a Glance
• Workshop Program
• Live Streaming
• Birds-of-a-Feather Sessions
• Sponsorship
• Hotel and Travel Information
• Help Promote!
• For Participants
• Call for Papers
• Past Workshops

usenix conference policies

• Event Code of Conduct
• Conference Network Policy
• Statement on Environmental Responsibility Policy

You are here

Connect with us, dissecting open source cloud evolution: an openstack case study.

Salman A. Baset, Chunqiang Tang, Byung Chul Tak, and Long Wang, IBM T.J. Watson Research Center

Open source cloud platforms are playing an increasingly significant role in cloud computing. These systems have been undergoing rapid development cycles. As an example, OpenStack has grown approximately 10 times in code size since its inception two and a half years ago. Confronting such fast-pace changes, cloud providers are challenged to understand OpenStack’s up-to-date behaviors and adapt and optimize their provisioned services and configurations to the platform changes quickly. In this work, we use a black-box technique for conducting a deep analysis of four versions of OpenStack. This is the first study in the literature that tracks the evolution of a popular open source cloud platform. Our analysis results reveal important trends of SQL queries in OpenStack, help identify precise points for targeted error injection, and point out potential ways to improve performance (e.g. by changing authentication to PKI). The OpenStack case study in this work effectively demonstrates that our automated black-box methodology aids quick understanding of platform evolution and is critical for effective and rapid consumption of an open-source cloud platform.

Salman A. Baset, IBM T. J. Watson Research Center

Chunqiang tang, ibm t. j. watson research center, byung chul tak, ibm t. j. watson research center, long wang, ibm t. j. watson research center, open access media.

USENIX is committed to Open Access to the research presented at our events. Papers and proceedings are freely available to everyone once the event begins. Any video, audio, and/or slides that are posted after the event are also free and open to everyone. Support USENIX and our commitment to Open Access.

Presentation Video 

Presentation audio.

Download Audio

• Log in  or     Register to post comments

Gold Sponsors

Silver Sponsors

Bronze Sponsors

Media Sponsors & Industry Partners

• Privacy Policy

Ceph done right for OpenStack

The rise of OpenStack ¶

For years, the desire to standardize on an open platform and adopt uniform APIs was the primary driver behind OpenStack’s rise across public and private clouds. Deployments continue to grow rapidly; with more and larger clouds, deep adoption throughout users’ cloud infrastructure and maturing technology as clouds move into production.

OpenStack’s top attributes are, not surprisingly, shared by the most popular storage software for deployments: Ceph.

With Ceph, users get all the benefits of open source software, along with interfaces for object, block and file-level storage that give OpenStack what it needs to run at its best. Plus, the combination of OpenStack and Ceph enables clouds to get faster and more reliable the larger they get. It sounds like a match made in heaven – and it is – but it can also be a challenge if you have your heart set on a DIY approach. Or worse, you could find yourself locked into a contract whose only interests being taken care of, are the vendor’s.

And, because OpenStack deployments vary drastically as business and application needs vary, there is no ‘one size fits all’ approach.

So, where to begin? ¶

Download the “ Ceph for OpenStack ” use case here and discover why they’re the perfect match, and how to tailor your architecture to meet the needs of your organization.

Discover more

Case studies.

Browse further examples of how Ceph brings efficient, reliable storage to organizations at any scale, across a broad variety of industries and applications.

Ceph's flexibility is one of its many strengths. It can be adapted to perfectly suit your storage needs, with industry-leading levels of data availability and resilience.

Benefits of Ceph

Efficient, reliable data distribution and freedom from vendor lock-in are just the start of the reasons why more and more organizations are making the switch to Ceph.

NHN Cloud | An OpenStack Case Study

Find out how OpenStack has transformed NHN Cloud and see how they are using it in their newly launched private cloud solution, NHN Private Deck.

NHN Cloud is one of the leading service providers in Korea, known for its expertise in managing IT services across different fields. Find out how OpenStack has transformed NHN Cloud and see how they are using it in their newly launched private cloud solution, NHN Private Deck.

How has OpenStack transformed your organization?  

NHN Private Deck is an integrated appliance with everything needed for an OpenStack cloud, packaged in a rack, to provide a fast and optimized cloud environment. 

OpenStack freed us from the constraints of physical infrastructure, allowing us to reliably scale up and down resources such as servers, networking, and storage, which meant we could use our virtualized resources more efficiently and save money. 

By combining different OpenStack components, we could build the features our clients want into the cloud environment. 

NHN Private Deck takes advantage of compatibility between various cloud services and OpenStack APIs to deliver a multi-cloud environment. The solution also provides a cloud management platform to control the multi-cloud environment, which allows users to manage resources and functions through a unified console.

What workloads are you running on OpenStack?

NHN Private Deck offers a cloud platform in Large, Standard, and Small models, with different workloads running on OpenStack depending on the model. 

For the Large model, workloads for large-scale projects that require at least 500 compute nodes are running. For example, data-intensive workloads such as large data analysis run in the model.

The Small model runs workloads related to small research or public sector projects, and application prototype development that generally requires fewer than 10 compute nodes.

The Standard model offers the highest reliability and runs workloads for applications in the market.

What is the scale of your OpenStack environment? 

Based on the Standard Model of NHN Private Deck, it consists of five compute nodes, four controller nodes, NAS, block storage, firewall, and switch in one rack, and the specifications are as follows:

CPUs: 240 vCPU (1:1 overcommit ratio) – Memory: 250 GB – Storage: 10TB or more.

What other open source technologies are integrated with your OpenStack environment? 

NHN Private Deck can integrate cloud platforms with a variety of open source technologies. 

These include Prometheus, Grafana, Kubernetes, Kibana, and many other popular tools and platforms. 

They can be used to make container platforms more powerful and easier to use. NHN Private Deck also delivers installation and operation for clients to make the most of these technologies.

Share your use case by filling out the  OpenStack Case Study Survey! 

Tags: API , Large scale , NHN Cloud , OpenStack , Private Cloud

Recent Posts

• Meet OpenInfra Europe Advisory Board Member: Kurt Garloff - December 21, 2023
• NVIDIA’s Journey with Kata Containers and Confidential Computing | OpenInfra Live Recap - December 18, 2023
• Large Scale Ops Deep Dive: Samsung SDS | OpenInfra Live Recap - December 14, 2023

Inside Open Infrastructure: October 2023 PTG Recap

PTG Recap, project updates and the latest news from the OpenInfra community!

South Korean Company, Okestro, Announces Gold Membership

OpenInfra Foundation announces Okestro’s Gold Membership at this year’s OpenInfra Summit.

OpenInfra Days 2021 | OpenInfra Live Recap

The latest episode of OpenInfra Live, the weekly show hosted by the OpenInfra Foundation, is now available on-demand.

Examination of Cost Differences Between Private Cloud and Hyperscalers | OpenInfra Live Recap

Georgia Cyber Center | An OpenStack Case Study

Appreciating the Need for Edge Location Standards or Schemas

Software Deployment Options in OpenStack: A Quick Guide

• Kubernetes Troubleshooting: A Practical Guide
• From Student to Full time Contributor: Meet Ashley Rodriguez
• The OpenInfra University Partnership Program Builds Next Generation of Open Source Contributors
• PTG April 2024 Summary
• Collaboration of Open Radio Access Network Software Community and OpenStack Tacker Delivers vRAN Advancements
• Open Infrastructure Events
• Superuser Award
• Superuser TV
• Uncategorized
• User Stories

 Update: DISA Releases Mirantis Kubernetes Engine STIG   Read More

PUBLIC SECTOR

Société Générale

Mirantis Supports Société Générale’s Journey of Cloud Native Transformation

Read Case Study

Read our latest customer stories

Netsons Expands Cloud Computing Services Across Europe Using Mirantis OpenStack Private Clouds

Netskope Expands Secure Access Service Edge with Mirantis OpenStack Private Cloud

Mirantis Helps Inmarsat Build Its Next-Generation Communications Network

Vaudoise Insurance Builds Out Modern Microservices with Mirantis Kubernetes Engine

Containers | Financial

Mirantis helps Asian bank scale mobile banking for millions of customers during COVID-19 pandemic

Containers | Defense

Aerospace Leader

Mirantis Kubernetes Engine gives Aerospace company an on-prem container platform that drives a secure software supply chain–with global impact.

Alm. Brand Saves 90 percent of Maintenance Time in 10 Months

OpenStack | Telecom

Asian Telecom Operator

Leading telecommunications operator uses Mirantis Cloud Platform to quickly scale for 100 million new customers in less than 6 months

Containers | Technology

Conoa collaborates with businesses for successful transformations with open source

Containers | Education

Cornell Lab of Ornithology

The Cornell Lab of Ornithology accelerates development on high-availability apps for a global user-base.

Cornell University

Cornell University Accelerates Cloud Migration

Defense Agency Cybersecurity Office

Defense Agency Cybersecurity Office focuses on its mission, turning to Mirantis for the only STIG-ready managed container service on the market.

OpenStack | Financial

European Banking Leader

Global 500 bank deploys OpenStack private cloud to speed product introduction and reduce costs

Fortune 500 Credit Card Company

Leading credit card company speeds time-to-market and lowers platform costs

OpenStack | Media

Fortune 500 Pay-TV Provider

Leading satellite operator uses Mirantis Cloud Platform to launch an over-the-top streaming service in less than 2 months

OpenStack | Healthcare

European Medical Center

European Medical Center Drives Cutting-Edge Research with Mirantis OpenStack Private Cloud

Containers | Pharma

Global Pharma

How a global pharma company rapidly migrated 3,000 Kubernetes environments to Amazon EKS and cut application delivery costs by 60%

Japanese Telecom

Leading operator deploys Kubernetes and OpenStack cloud for cloud-native enterprise apps

Containers | Government

Kadaster Builds a Flexible Platform to Handle 8 Billion Transactions a Year

Leading Telecom

With OpenStack, leading Asia Pacific telecom reduces provisioning time from weeks to seconds

MetLife Transforms Customer Experience with Application Modernization

Containers | Healthcare

Mutuelle Just

Mirantis & Mutuelle JUST - Building Container Infra 'Just Right'

OpenStack | Technology

OpenStack | Business Services

Netsons Expands Cloud Computing Services Across Europe with OpenStack Private Clouds

PayPal Manages 200,000 Containers in the Cloud to Speed Transactions

Pharma Giant

Pharma giant boosts innovation with hybrid, multi-cloud platform

Containers | Food Products

Premium Food Supplier

Premium food supplier serves up faster software delivery with Mirantis Kubernetes Engine and Lens.

Royal Bank of Canada

RBC Capital Markets Expands Risk Analysis Models for Data Scientists by Scaling to GPUs

MultiCloud | Financial

S&P Global Centrally Manages On-prem and Public Cloud Kubernetes Clusters.

SEB Gives Developers Fast Deployments with CI/CD

Splunk Improves Product Quality with Docker Enterprise

Largest Middle East and Africa telecom provider builds innovative public OpenStack cloud

Containers | Insurance

Customer Reviews

900 E Hamilton Avenue Suite 650 Campbell, CA 95008 +1-650-963-9828

Privacy Policy

Do Not Sell My Information

UK Modern Slavery Act Statement

Digital Self-Determination

• What is Digital Self-Determination
• For Developers
• For Cloud Operators
• Modern Application Delivery
• App Modernization
• Cloud Platform Operations
• Lens Desktop
• Mirantis Kubernetes Engine
• Mirantis OpenStack for Kubernetes
• Mirantis Container Runtime
• Mirantis Secure Registry
• Mirantis Container Cloud
• amazee.io's Lagoon
• Why Mirantis
• Open Source

© 2005 - 2024 Mirantis, Inc. All rights reserved. “Mirantis” and “FUEL” are registered trademarks of Mirantis, Inc. All other trademarks are the property of their respective owners.

Intrusion Detection and Prevention in OpenStack: A Case Study on Enhancing Security and Threat Detection

• Original Research
• Published: 28 October 2023
• Volume 4 , article number  830 , ( 2023 )

Cite this article

• Sanjay Adiwal   ORCID: orcid.org/0000-0001-8350-0999 1 &
• Mohammad Misbahuddin 2  

131 Accesses

Explore all metrics

Internet usage has experienced exponential growth over the past two decades. Nowadays, numerous human activities heavily rely on the Internet and information technology. The Internet is utilized for various purposes, including communication, online financial transactions, banking, entertainment, work, and educational tasks. As our dependency on the Internet increases, a substantial amount of data and sensitive information is inevitably transmitted over the Internet, especially through cloud services. Consequently, malicious attackers are actively seeking security loopholes and vulnerabilities, specifically targeting cloud environments. Intrusion Detection and Prevention System (IDPS) is a hardware appliance or a software application that monitors a network for malicious activity or breaches of policies, and based on the rules created, blocks any potential malicious activity. Cloud service providers and users now require IDPS as part of their security infrastructure. This paper investigates how an open-source IDPS named Snort can be effective in OpenStack-based cloud environments. The effectiveness of the Snort-based cloud security solution is demonstrated through a series of experiments.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price includes VAT (Russian Federation)

Instant access to the full article PDF.

Rent this article via DeepDyve

Institutional subscriptions

Similar content being viewed by others

A Collaborative Study of Intrusion Detection and Prevention Techniques in Cloud Computing

HIDSC2: Host-Based Intrusion Detection System in Cloud Computing

Intrusion Detection System with Snort in Cloud Computing: Advanced IDS

Data availability.

The data that support the findings of this study are available on request from the corresponding author.

Internet Stats & Facts, List of Internet, eCommerce, Hosting, Mobile & Social Media Statistics for 2021.2023. https://websitesetup.org/news/internet-facts-stats . Accessed 20 Mar 2023.

Kumar J, Bindhumadhava BS, Santhanavijayan A, Rajendran B. An adaptive neural network for email spam classification. In: Fifteenth International Conference on Information Processing (ICINPRO). 2019; https://doi.org/10.1109/ICInPro47689.2019.9092278 .

Gupta A, Lalit S. Detecting attacks in high-speed networks: issues and solutions. Inform Secur J Glob Perspect. 2020;29:5–6.

Google Scholar  

Kumar J, Santhanavijayan A, Rajendran B. Cross site scripting attacks classification using convolutional neural network. In: 2022 International Conference on Computer Communication and Informatics (ICCCI). 2022; https://doi.org/10.1109/ICCCI54379.2022.9740836 .

Khalil IM, Abdallah K, Muhammad A. Cloud computing security: a survey. Computers. 2014. https://doi.org/10.3390/computers3010001 .

Article   Google Scholar  

Carlin S, Kevin C. Cloud Computing security. In: Pervasive and ubiquitous technology innovations for ambient intelligence environments. IGI Global; 2013.

Dimitrios Z, Dimitrios L. Addressing cloud computing security issues. Futur Gener Comput Syst. 2012. https://doi.org/10.1016/j.future.2010.12.006 .

A practical guide to zero trust implementation, roadmap: the zero trust security playbook. 2023. https://www.forrester.com/report/A+Practical+Guide+To+A+Zero+Trust+Implementation/-/E-RES157736 , Accessed 20 Mar 2023.

Zhou Z, Zhongwen C, Tiecheng Z, Xiaohui . The study on network intrusion detection system of Snort. In: International Conference on Networking and Digital Society. 2010.

Snort System software. Snort—a free open source network intrusion detection system.2023. https://www.Snort.org/ . Accessed 10 May 2023.

Sanjay A, Rajendran B, Shetty PD. DNS amplification & DNS tunneling attacks simulation, detection and mitigation approaches. In: International Conference on Inventive Computation Technologies (ICICT). 2020; https://doi.org/10.1109/ICICT48043.2020.9112413

Download references

Author information

Authors and affiliations.

RISE, C-DAC, Bengaluru, India

Sanjay Adiwal

ACTS & BD, C-DAC, Bengaluru, India

Mohammad Misbahuddin

You can also search for this author in PubMed   Google Scholar

Corresponding author

Correspondence to Sanjay Adiwal .

Ethics declarations

Conflict of interest.

The authors have no relevant financial or non-financial interests to disclose. The authors have no conflicts of interest to declare that are relevant to the content of this article. All authors certify that they have no affiliations with or involvement in any organization or entity with any financial interest or non-financial interest in the subject matter or materials discussed in this manuscript. The authors have no financial or proprietary interests in any material discussed in this article.

Additional information

Publisher's note.

Springer Nature remains neutral with regard to jurisdictional claims in published maps and institutional affiliations.

This article is part of the topical collection “Advances in Internet Research and Engineering 2023” guest edited by Sudarsan S D, Mohit Sethi and Balaji Rajendran.

Rights and permissions

Springer Nature or its licensor (e.g. a society or other partner) holds exclusive rights to this article under a publishing agreement with the author(s) or other rightsholder(s); author self-archiving of the accepted manuscript version of this article is solely governed by the terms of such publishing agreement and applicable law.

Reprints and permissions

About this article

Adiwal, S., Misbahuddin, M. Intrusion Detection and Prevention in OpenStack: A Case Study on Enhancing Security and Threat Detection. SN COMPUT. SCI. 4 , 830 (2023). https://doi.org/10.1007/s42979-023-02265-3

Download citation

Received : 06 July 2023

Accepted : 19 August 2023

Published : 28 October 2023

DOI : https://doi.org/10.1007/s42979-023-02265-3

Share this article

Anyone you share the following link with will be able to read this content:

Sorry, a shareable link is not currently available for this article.

Provided by the Springer Nature SharedIt content-sharing initiative

• Cloud security

Advertisement

• Find a journal
• Publish with us
• Track your research