View
68
Download
0
Category
Tags:
Preview:
DESCRIPTION
APS OpenStack / Mirantis App Resource Model. 23 September 2014. Provider. Customer. Counters CPU RAM Diskspace Traffic Public IPs. Store Params CPU RAM Diskspace Traffic Public IPs Sample. app. / poa /account. Properties CPU RAM Diskspace. organization. / poa /subscription. - PowerPoint PPT Presentation
Citation preview
April 21, 2023
APS OpenStack / Mirantis App Resource Model
CustomerCustomer
appapp
Required: False Collection: FalseRequired: False Collection: FalseRequired: True Collection: FalseRequired: True Collection: False Required: False Collection: TrueRequired: False Collection: TrueRequired: True Collection: TrueRequired: True Collection: True
ProviderProvider
useruser
usersusers
organizationorganization
flavorsflavors
/poa/subscription/poa/subscription
/poa/account/poa/account
/poa/hsu/poa/hsu
VPSVPS
Counters•CPU•RAM•Diskspace•Traffic•Public IPs
Counters•CPU•RAM•Diskspace•Traffic•Public IPs
PropertiesCPURAMDiskspaceTrafficPublic IPs
PropertiesCPURAMDiskspaceTrafficPublic IPs
ipipippoolsippools
ipip
Properties•CPU•RAM•Diskspace
Properties•CPU•RAM•Diskspace
Store Params•CPU•RAM•Diskspace•Traffic•Public IPs•Sample
Store Params•CPU•RAM•Diskspace•Traffic•Public IPs•Sample
imagesimages
Properties•OS•Image
Properties•OS•Image
UnmanagedVeUnmanagedVe
Notes – Image Resource• Image resource reflects OpenStack Glance “golden image” object. The purpose of
this resource is to allow accurate billing for the operating system usage• APS package should be able to report image usage, either collecting statistics from
Ceilometer (ideal) or by regularly reporting current state like “At given moment, tenant A uses 2 instances of image Windows2008” (works but can yield significant rounding error)
• The link between Image and UnmamagedVE should not to be set by PA but should be discovered from live OpenStack, as tenant may use image through OpenStack API bypassing PA
• Supported scenarios:• Provider can assign hourly cost of use to a particular image, and make certain images free in both
Flat and PAYG models• User can create server based on provider supplied image in Flat and PAYG model• User can upload own image and create server based on own image in Flat and PAYG subscription• Server creation from image through OpenStack API in Flat/PAYG subscription• Provider can create VPS subscription based on any provider-uploaded image• Provider can include certain images as paid add-on to a VPS subscription (“Windows 2008 costs
30 dollars a month”)• Unsupported scenarios
• Assigning hourly cost to user-uploaded image (other than storage cost reported by Ceilometer as storage use)
• Upload or use of custom images in VPS subscription• Server creation from image through OpenStack API in VPS subscription
Notes – Flavor Resource
• Flavor resource is used in VPS subscription only. One flavor per VPS service plan is created automatically in OpenStack by APS package and modified to reflect Service Plan modifications by Service Provider. Flavors reflecting Service Plans are only available to tenants running VPS subscriptions by automatically setting flavor visibility in OpenStack by APS package (using --is-public option and flavor-access-add command by APS package internally)
• Supported scenarios• Provider can setup a VPS service plan which will automatically
create a VPS when provisioned• Provider can setup several service plans for users to choose or
upgrade later
• Unsupported scenarios• Applying a custom flavor to a VPS subscription• Using a flavor from VPS subscription in Flat/PAYG subscription
Notes – Virtual Environment Resource
• We introduce two types of VE resources: UnmanagedVE and VPS. VPS resource used for creation of VPS subscriptions, UnmanagedVE – for Flat/PAYG subscriptions.
• Supported scenarios• Creating private flavors for a Flat/PAYG user• Assigning any available flavor to a server under Flat/PAYG
tenant/subscription• Managing and assigning flavors in PA UI in Flat/PAYG subscriptions• Managing and assigning flavors through OpenStack API in Flat/PAYG
subscriptions• Per-tenant billing and limiting of resources usage in Flat/PAYG
subscriptions regardless of ways to manage resources
• Unsupported scenarios• Using any information from or about flavors in Flat and PAYG
subscriptions for billing purposes• Modifying VPS subscription servers directly in OpenStack, or reflecting
these changes in billing
OwnCloud: Service Template Prepaid
Resource Name Resource Class Limit Auto-Provide
APP Application Service Reference 1 N/A
Organization Application Service 1 1
CPU Application Counter 10 N/A
Memory Application Counter (to be agreed UOM) 10 N/A
….. Application Counter XX N/A
VE Application ServiceUnlimited / Or not
N/A
Ips Application ServiceUnlimited(due is limit by counter)
N/A
OpenStack Users Application ServiceUnlimited / Or not
N/A
OwnCloud: Service Template Pay as you go
Resource Name Resource Class Limit Auto-Provide
APP Application Service Reference 1 N/A
Organization Application Service 1 1
CPU Application Counter Metered (-1) N/A
Memory Application Counter (to be agreed UOM) Metered (-1) N/A
….. Application Counter Metered (-1) N/A
VE Application Service Unlimited N/A
Ips Application Service Unlimited N/A
OpenStack Users Application Service Unlimited N/A
Recommended