...
This diagram shows a reseller hiearchy hierarchy to manage Azure CSP or AWS organization accounts and their customers. The documentation below describes how to create this hierarchy.
Mermaid | ||||||
---|---|---|---|---|---|---|
| ||||||
{"diagramDefinition":"flowchart LR\nA(Reseller<br/>enterprise)\nB(ACustomer<br/>key node<br/>enterprise)\nB-->C(AStandard<br/>enterprise 1)\nB-->D(AStandard<br/>enterprise 2)\nC-.-F(ASubscription1)\nD-.-E(ASubscription2)\nG-.-H(BSubscription2BSubscription1)\nA-.-P(Reseller<br/>Pricing<br/>credential)\nG(BCustomer<br/>key node<br/>enterprise)\nsubgraph ResellerScope\n A\n P\nend\nsubgraph BCustomerScope\n G \n H\nend\n\nsubgraph Reseller hierarchy\n direction LR\n ResellerScope-->ACustomerScope\n ResellerScope-->BCustomerScope\nend\nsubgraph GlobalScope\nend\nGlobalScope-->ResellerScope\n\nsubgraph ACustomerScope\n direction LR\n B\n C\n D\n E\n F\nend\n style GlobalScope fill:#ec9032,stroke:#666,stroke-width:2px,color:#fff\n style A fill:#ec9032,stroke:#666,stroke-width:2px,color:#fff\n style P fill:#ec9032,stroke:#666,stroke-width:2px,color:#fff,stroke-dasharray: 5 5\n style B fill:#ec9032,stroke:#666,stroke-width:2px,color:#fff\n style C fill:#ec9032,stroke:#666,stroke-width:2px,color:#fff\n style D fill:#ec9032,stroke:#666,stroke-width:2px,color:#fff\n style F fill:#ec9032,stroke:#666,stroke-width:2px,color:#fff,stroke-dasharray: 5 5\n style E fill:#ec9032,stroke:#666,stroke-width:2px,color:#fff,stroke-dasharray: 5 5"} |
...
Create public cloud regions for your public cloud providers. See Create a public cloud region
Go to Users → Scopes and Create a reseller scope:
Make the Name descriptive, for example,
ResellerNameScope
For the Parent scope select the
Global scope
(recommended) or no scopeFor Entities, select your public cloud regions.
Go to Users and Create a reseller enterprise:
For the Default scope select
ResellerNameScope
Select the Reseller checkbox
If the reseller will use its own mail server, enter the details of the Mail server
For Datacenters, select the datacenters and public cloud regions that the reseller and its customers will use, as in the scope.
...
Create a customer scope:
Go to Users → Scopes and click the + add button (or edit an existing customer scope)
For the Name, we recommend that you include the customer name, for example,
CustomerScope
For the Parent scope, select the reseller scope, for example,
ResellerScope
.
For the Entities, select the datacenters and public cloud region/s.
Create a customer enterprise:
Go to Users view and at the bottom of the Enterprises list, click the + add button
For the Default scope, select the customer scope, for example,
CustomerScope
Select the Key node checkbox to support Office365 customers, Multiple Azure subscriptions (Plans), and AWS organization accounts, and so on
For Properties,add tenant metadata as required
For each subscription in an Azure plan or AWS organization, create a standard enterprise:
Create a standard enterprise (not a key node)
For the Default scope, select the
CustomerScope
...
Onboard an Azure customer
...
for billing only
To give a CSP customer access to compute and billing features:
https://abiquo.atlassian.net/wiki/spaces/doc/pages/311370762/Obtain+Azure+ARM+credentials#Create-an-ARM-application-using-Azure-portal in the customer’s Active Directory.
Edit the standard enterprise, and go to Credentials → Public
Add the credentials for customer in the format
Subscription#AppID#TenantID
Go to Properties and add
azurecompute-arm_only_bill_subscription
and set the value totrue
To give the customer access billing features only (including dashboard display, and billing of Office 365):
...
billing features only for their tenant (including dashboard display), this section describes how to onboard a customer and all their subscriptions into a single tenant.
To onboard an individual subscription for billing only or to onboard an Azure subscription for compute and billing, see Add a subscription of an Azure reseller customer for billing only and
To onboard an Azure customer for billing only:
Under the reseller, edit the customer, key node (for Azure Plans and Office 365), or standard enterprise
Go to Credentials → Public
For the Access key ID, enter the customer’s subscription details in this format:
Subscription##TenantID
For the Secret access key, enter any valueTenantID
Select Only for billing
Click Add account to save the credentials. The platform will not validate the account details until it retrieves billing data from the provider
Go to Properties and add
azurecompute-arm_only_bill_subscription
and set the value totrue
Click Save
Now you can Add the Microsoft products service to manage Customer users, office licenses and Azure plan subscriptions!
...
Onboard an AWS customer
To onboard a customer of an AWS organization:
Under the reseller scope: https://abiquo.atlassian.net/wiki/spaces/doc/pages/311361611/Abiquo+cloud+reseller+guide#Create-a-scope-for-a-reseller-customer under the reseller scope
In the customer scope, ereate a reseller customer as a key node https://abiquo.atlassian.net/wiki/spaces/doc/pages/311361611/Abiquo+cloud+reseller+guide#Create-a-reseller-customer in the customer scope
Create a standard enterprise in the customer scope
Log in to AWS and in the customer account, create a user
In Abiquo, edit the standard enterprise and add the credentials as public cloud credentials.
OR Add the account to the standard enterprise with public cloud credentials for billing only.
See Add AWS and Azure credentials only for billing
...
Create a standard enterprise in the scope of the key node
Log in to AWS and in the customer account, and create a user.
In Abiquo, edit the standard enterprise and add the credentials as public cloud credentials.
OR Add the account to the standard enterprise as public cloud credentials for billing only.
See Add AWS and Azure credentials only for billing
...