Evaluating Degrees of Multitenancy Isolation: A Case Study of Cloud-Hosted GSD Tools

Ochei, Laud Charles; Bass, Julian M.; Petrovski, Andrei

doi:10.1109/iccac.2015.17

Cited by 12 publications

(36 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…2 shows a sample architecture of multitenancy isolation involving three tenants at the data level. For multitenancy isolation at the process level, the component that is being shared is a lock object [10] [11]. At the process level, the component that is being shared is a lock object [10] [11].…”

Section: Discussionmentioning

confidence: 99%

“…For multitenancy isolation at the process level, the component that is being shared is a lock object [10] [11]. At the process level, the component that is being shared is a lock object [10] [11]. The above scenarios are very important in the so called distributed bug tracking in which some bug trackers such as Fossil and Veracity, are either integrated with or designed to use distributed VCS or CI systems, thus allowing bugs generated automatically and In order to measure the effect of isolation between tenants, we configured one of the four tenants to represent a treatment (i.e., T1 in the case) for each group to experience a large instant loads while accessing the application component.…”

Section: Discussionmentioning

confidence: 99%

“…The experimental hypothesis states that the performance and system's resource utilization experienced by tenants accessing an application component deployed using each multitenancy pattern changes significantly from the pre-test to the post test. A summary of the experimental procedure we adopted can be seen in Ochei et al [10] [11]. …”

Section: Discussionmentioning

confidence: 99%

“…Based on this dataset, three software processes which have the highest impact on Global Software Development were selected: continuous integration (CI), version control (VC) and issue/bug tracking. Two of these software processes have been used previously in two separate case studies to empirically evaluate the degrees of multitenancy isolation based on our novel approach for implementing multitenancy isolation (i.e., COMITRE) [10] [11]. In this paper, we focus on applying COMITRE to implement the required degree of multitenancy isolation in a bug tracking system.…”

Section: A Selecting the Gsd Tools And Software Processesmentioning

confidence: 99%

“…Figure 1 captures the structure of COMITRE while the logic used to implement it shown in Algorithm 1. We have presented the full explanation of COMITRE (including its step-by-step procedure) in Ochei et al [10] [11]. This paper applies an improved version of the algorithm (i.e., in terms of adding more details to achieve generality and applicability in different environments) used to implement COMITRE for evaluating the degrees of isolation between tenants for a particular multitenancy pattern.…”

Section: B Applying Comitre To Evaluate the Degrees Of Multitenancy mentioning

confidence: 99%

See 4 more Smart Citations

Implementing the Required Degree of Multitenancy Isolation: A Case Study of Cloud-Hosted Bug Tracking System

Ochei

Petrovski

Bass

2016

2016 IEEE International Conference on Services Computing (SCC)

Self Cite

View full text Add to dashboard Cite

Abstract-Implementing the required degree of isolation between tenants is one of the significant challenges for deploying a multitenant application on the cloud. In this paper, we applied COMITRE (COmponent-based approach to Multitenancy Isolation Through request RE-routing) to empirically evaluate the degree of isolation between tenants enabled by three multitenancy patterns (i.e., shared component, tenant-isolated component, and dedicated component) for a cloud-hosted Bug tracking system using Bugzilla. The study revealed among other things that a component deployed based on dedicated component offers the highest degree of isolation (especially for database transactions where support for locking is enabled). Tenant isolation based on performance (e.g., response time) favoured shared component (compared to resource consumption (e.g., CPU and memory) which favoured dedicated component). We also discuss key challenges and recommendations for implementing multitenancy for application components in cloud-hosted bug tracking systems with guarantees for isolation between multiple tenants.

show abstract

Section: Discussionmentioning

confidence: 99%

Section: Discussionmentioning

confidence: 99%

Section: Discussionmentioning

confidence: 99%

Section: A Selecting the Gsd Tools And Software Processesmentioning

confidence: 99%

Section: B Applying Comitre To Evaluate the Degrees Of Multitenancy mentioning

confidence: 99%

See 3 more Smart Citations

Implementing the Required Degree of Multitenancy Isolation: A Case Study of Cloud-Hosted Bug Tracking System

Ochei

Petrovski

Bass

2016

2016 IEEE International Conference on Services Computing (SCC)

Self Cite

View full text Add to dashboard Cite

show abstract

Zero-Cost In-Depth Enforcement of Network Policies for Low-Latency Cloud-Native Systems

Budigiri,

Baumann,

Truyen

et al. 2023

2023 IEEE 16th International Conference on Cloud Computing (CLOUD)

View full text Add to dashboard Cite

Packaging applications in containers and managing them dynamically using a cluster orchestrator is the de-facto approach for deployment of cloud-native applications. When containers run inside virtual machines (VMs) to protect infrastructural assets, network policies (NPs) at the container layer and security groups (SGs) at the VM layer provide complementary firewall mechanisms that strengthen defenses against lateral movement of attackers. However, least-privilege NPs at the container layer may not always be consistent with statically defined, over-permissive SGs at the VM layer. This is especially a problem with low-latency configuration of container networking solutions that requires every opened container protocol, port and traffic direction also to be opened at the VM layer. In any post-exploitation scenario where attackers escape from within an already compromised or infected container, such over-permissive SGs do not prevent the attacker from spreading across VMs to find powerful tokens for accessing the cluster orchestrator. In this paper, we introduce GrassHopper (GH), a fast and dynamic cross-layer enforcement approach for NPs, which automatically generates SG configurations from dynamically verified NPs. Given the low-latency context, the design of GH must ensure that dynamically generated SG rules are applied fast before the newly scheduled containers become ready to serve traffic. We evaluate GH on a Kubernetes cluster running on OpenStack. For a wide range of relevant low-latency applications and cluster setups, GH can reduce the network attack surface between VMs at a ratio of 75-to-99% while causing no application level performance overhead with respect to latency, throughput, and CPU utilization.

show abstract

Evaluating degrees of tenant isolation in multitenancy patterns: A case study of cloud-hosted Version Control System (VCS)

Ochei

Petrovski

Bass

2015

2015 International Conference on Information Society (I-Society)

Self Cite

View full text Add to dashboard Cite

Abstract-One of the key concerns of implementing multitenancy (i.e., serving multiple tenants with a single instance of an application) on the cloud is how to enable the required degree of isolation between tenants, so that the required performance of one tenant does not affect other tenants. There is little research which provides empirical evidence on the required degree of isolation between tenants under different cloud deployment conditions. This paper applies COMITRE (COmponent-based approach to Multitenancy Isolation Through request RE-routing) to empirically evaluate the degree of isolation between tenants enabled by multitenancy patterns for cloud-hosted Version Control System (VCS). We implemented three multitenancy patterns (i.e., shared component, tenant-isolated component, and dedicated component) by developing a multitenant component using the FileSystem SCM plugin integrated within Hudson. The study revealed that dedicated component provides the highest degree of isolation between tenants (compared to shared component and tenant-isolated component) in terms of error% (i.e., the percentage of errors with unacceptably slow response times) and throughput. System load of tenants showed no variability, and hence did not influence the degree of tenant isolation for all the three multitenancy patterns. We also provide some recommendations to guide an architect in implementing multitenancy isolation on similar VCS tools like Subversion and CVS.

show abstract

Evaluating Degrees of Multitenancy Isolation: A Case Study of Cloud-Hosted GSD Tools

Cited by 12 publications

References 10 publications

Implementing the Required Degree of Multitenancy Isolation: A Case Study of Cloud-Hosted Bug Tracking System

Implementing the Required Degree of Multitenancy Isolation: A Case Study of Cloud-Hosted Bug Tracking System

Zero-Cost In-Depth Enforcement of Network Policies for Low-Latency Cloud-Native Systems

Evaluating degrees of tenant isolation in multitenancy patterns: A case study of cloud-hosted Version Control System (VCS)

Contact Info

Product

Resources

About