A framework for achieving the required degree of multitenancy isolation for deploying components of a cloud-hosted service.

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

Abstract

Multitenancy allows multiple tenants to access a single instance of a cloud offering. While several approaches exist for implementing multitenancy, little attention has been paid to implementing the required degree of isolation since there are varying degrees of isolation that can be implemented for each tenant. This paper presents a framework for achieving the required degree of isolation between tenants accessing a cloud offering so that the required performance, resource utilisation and access privilege of one tenant does not affect other tenants when there are workload changes. The framework is composed of two main constituents: 1) component-based approach to multitenancy isolation through request re-routing (COMITRE); 2) an optimisation model for providing optimal solutions for deploying components of a cloud-hosted service. We demonstrate using a case study of: 1) a cloud-hosted bug tracking system; 2) a synthetic dataset, the possibility of providing the required degree of isolation and optimal deployment solutions.

Citation

OCHEI, L.C., PETROVSKI, A. and BASS, J.M. 2018. A framework for achieving the required degree of multitenancy isolation for deploying components of a cloud-hosted service. International journal of cloud computing [online], 7(3-4), pages 248-281. Available from: https://doi.org/10.1504/IJCC.2018.095396

• Journal Article Type: Article
• Acceptance Date: May 16, 2018
• Online Publication Date: Sep 20, 2018
• Publication Date: Dec 31, 2018
• Deposit Date: Oct 29, 2018
• Publicly Available Date: Sep 21, 2019
• Journal: International journal of cloud computing
• Print ISSN: 2043-9989
• Electronic ISSN: 2043-9997
• Publisher: Inderscience
• Peer Reviewed: Peer Reviewed
• Volume: 7
• Issue: 3-4
• Pages: 248-281
• DOI: https://doi.org/10.1504/IJCC.2018.095399
• Keywords: Bug tracking system; Cloudhosted service; Components; Degree of isolation; Global software development; Multitenancy; Optimal solution; Optimisation model; Software development tools; Tenants; Workload
• Public URL: http://hdl.handle.net/10059/3197