Hierarchical multi-tenant pattern

Bien, Ngo Huy; Thu, Tran Dan

doi:10.1109/commantel.2014.6825597

Cited by 5 publications

(5 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Multitenancy is a standard feature of three established cloud service models [18]: Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS) [19]. If CaaS is to provide the promised benefits of the cloud and the edge cloud at scale, then it also requires an efficient multitenancy model.…”

Section: Statementioning

confidence: 99%

“…The Kubernetes community has recognized the importance of developing such frameworks, as evidenced by the fact that one of the Kubernetes working groups, of which there are just eight, 18 is devoted to multitenancy. 19 Both of the frameworks that this working group supports adopt the shared cluster approach. VirtualCluster (VC) [35] offers a separate control plane for each tenant, whereas the control plane is shared among tenants by the Hierarchical Namespace Controller (HNC) [36].…”

Section: Related Workmentioning

confidence: 99%

“…Kubernetes working groups https://github.com/kubernetes/community/ blob/master/sig-list.md19 Kubernetes Multi-tenancy Working Group https://github.com/kuberne tes-sigs/multi-tenancyA. MULTITENANCY APPROACH…”

mentioning

confidence: 99%

See 2 more Smart Citations

Multitenant Containers as a Service (CaaS) for Clouds and Edge Clouds

Şenel,

Mouchet,

Cappos

et al. 2023

IEEE Access

View full text Add to dashboard Cite

In recent years, along with containers, the cloud community has rapidly taken up Kubernetes, the de facto industry standard container orchestration system. All major cloud providers currently offer Kubernetesbased Containers as a Service (CaaS). However, when CaaS is offered to multiple independent consumers, or tenants, a multi-instance approach is used, in which each tenant receives its own separate cluster, which imposes significant overhead due to employing virtual machines for isolation. If CaaS is to be offered not only in the cloud, but also in the edge cloud, where resources are limited, another solution is required. In this paper, drawing upon the scientific literature, we provide a novel classification of Kubernetes multitenancy into three approaches: multi-instance through multiple clusters, multi-instance through multiple control planes, and single-instance native. We propose a single-instance multitenancy framework, meaning tenants are served out of a shared control plane in a single cluster. Our empirical findings show that the singleinstance approach imposes a markedly decreased overhead than the other two. However, it entails a tradeoff in workload isolation owing to tenants sharing the compute nodes. There are still means to compensate for such weakened isolation, and we describe how our framework does it. The framework is publicly available as liberally-licensed, free, open-source software that extends Kubernetes. It is in production use within the EdgeNet testbed for researchers.INDEX TERMS Edge computing, cloud computing, Containers as a Service, multitenancy, Kubernetes

show abstract

Section: Statementioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Multitenant Containers as a Service (CaaS) for Clouds and Edge Clouds

Şenel,

Mouchet,

Cappos

et al. 2023

IEEE Access

View full text Add to dashboard Cite

show abstract

“…Keystone provides identity API of hierarchical multi-tenancy for Open-Stack, using domains and projects to build hierarchy of user groups and resources subsets [3]. A hierarchical multi-tenant pattern is introduced to represent the hierarchical relationships among tenants [4]. But none of them further discusses the resource sharing or application customization between different-level tenants.…”

Section: Mta In Saasmentioning

confidence: 99%

“…Each subsidiary is built either as an independent tenant which makes customized resource sharing and re-customization among relative tenants difficult to implement, or as a user group of a tenant where the real world hierarchical relations are implied by complicated role hierarchy and sharing constraints. Recently more and more researches [1]- [4] are taking an interest in hierarchical multitenancy, which enables tenants to be divided into subtenants. It is a flexible and scalable architecture for representing sub- a) E-mail: qiong zuo@hust.edu.cn b) E-mail: wtsai@asu.edu (Corresponding author) DOI: 10.1587/transcom.2015ADI0002 Table 1 Access control requirements of hierarchical multi-tenancy and how much MTA can satisfy.…”

Section: Introductionmentioning

confidence: 99%

Autonomous Decentralized Authorization and Authentication Management for Hierarchical Multi-Tenancy

Zuo

Xie

Tsai

2016

IEICE Trans. Commun.

View full text Add to dashboard Cite

Hierarchical multi-tenancy, which enables tenants to be divided into subtenants, is a flexible and scalable architecture for representing subsets of users and application resources in the real world. However, the resource isolation and sharing relations for tenants with hierarchies are more complicated than those between tenants in the flat Multi-Tenancy Architecture. In this paper, a hierarchical tenant-based access control model based on Administrative Role-Based Access Control in Softwareas-a-Service is proposed. Autonomous Areas and AA-tree are used to describe the autonomy and hierarchy of tenants, including their isolation and sharing relationships. AA is also used as an autonomous unit to create and deploy the access permissions for tenants. Autonomous decentralized authorization and authentication schemes for hierarchical multi-tenancy are given out to help different level tenants to customize efficient authority and authorization in large-scale SaaS systems.

show abstract