Jump to: navigation, search

Difference between revisions of "Openstack-accounting"

 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
__NOTOC__
+
{{OldDesignPage}}
* '''Launchpad Entry''': [[NovaSpec]]:multi-tenant-accounting
+
 
 +
* '''Launchpad Entry''': NovaSpec:multi-tenant-accounting
 
* '''Created''': 11-08-2010
 
* '''Created''': 11-08-2010
  

Latest revision as of 00:03, 10 December 2013

Warning.svg Old Design Page

This page was used to help design a feature for a previous release of OpenStack. It may or may not have been implemented. As a result, this page is unlikely to be updated and could contain outdated information. It was last updated on 2013-12-10

  • Launchpad Entry: NovaSpec:multi-tenant-accounting
  • Created: 11-08-2010

Abstract

As a cloud computing platform, OpenStack must support the concept of multi-tenancy. A common approach to organizing resources by 'tenant' across services is needed to be able to correlate usage tracking, auditing, authorization, etc... And within each multi-tenant service, the ability to identify each tenant's resources (for various reasons such as security, accounting, isolation, etc…) is also key. However, the definition of a 'tenant' will vary by operator and by deployment. This blueprint therefore proposes creating a lightweight standard for service developers to implement tenancy and resource grouping without a-priori knowledge of billing and accounting processes specific to the operator of an OpenStack deployment.

For more information please read this draft version. We'll be updating the Wiki in the next few days.