Versions Compared

Version Old Version 9 New Version 10
Changes made by

MS (Unlicensed)

MS (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
The platform populates the billing dashboard widgets using scripts that obtain the billing information from the cloud providers. So first you will need to configure programmatic access to billing in the cloud providers. Then you will need to install the billing packages and configure and the scripts so they can obtain the billing data and add it to Abiquo. 

Configure programmatic billing in cloud providers

...

Amazon

See the AWS documentation about how to configure programmatic billing for AWS EC2 - https://aws.amazon.com/blogs/aws/new-programmatic-access-to-aws-billing-data/

  1. Create an S3 bucket and assign the following policy to make it writable by AWS programmatic billing.
    The "Resource" attribute will need the bucket name at the end. For the example, we have used "programmaticbilling".
    Expandnote down the name. AWS will write the programmatic billing data to this bucket

  2. Assign the following policy to the S3 bucket. In this example, the bucket is called "programmaticbilling". Replace "programmaticbilling" with the name of your bucket

    Code Block
    {
  "Version": "2008-10-17",
  "Id": "Policy1335892530063",
  "Statement": [
    {
      "Sid": "Stmt1335892150622",
      "Effect": "Allow",
      "Principal": {
        "AWS": "arn:aws:iam::386209384616:root"
      },
      "Action": [
        "s3:GetBucketAcl",
        "s3:GetBucketPolicy"
      ],
      "Resource": "arn:aws:s3:::programmaticbilling"
    },
    {
      "Sid": "Stmt1335892526596",
      "Effect": "Allow",
      "Principal": {
        "AWS": "arn:aws:iam::386209384616:root"
      },
      "Action": "s3:PutObject",
      "Resource": "arn:aws:s3:::programmaticbilling/*"
    }
  ]
}


  3. Go to Open Billing preferences and select the option to "Receive billing reports". Enter the name of your billing bucket
  4. Create a new user for programmatic billing (the user name is not important) and add you can give it any name - we used "programmaticbilling"!). Assign the AmazonS3ReadOnlyAccess policy to your user

Monthly CSV file (question)

Azure

...


  1. Grant access to billing records to the app role created in Azure
  2. Obtain the OfferDurableID from the offer agreement for your enterprise by going to your subscription → Administer. 
  3. Also, you should check obtain the Currency, Locale and RegionInfo.
  4. In Abiquo, configure Enterprise properties with the name of billing properties 
    1. AWS EC2 
      1.  "billing_bucket" property, with a value of the name of the billing bucket you created in step 1
    2. Azure ARM requires
      1. OfferDurableID
      2. Currency, the default is "USD"
      3. Locale, the default is "en-US"
      4. RegionInfo, the default is "US"
  5. On a server with MariaDB installed and with access to Abiquo Server, Abiquo database and public cloud providers, install the new billing packages
    1. abiquo-billing-arm
    2. abiquo-billing-ec2
  6. Configure billing packages
    1. AWS: Edit /opt/abiquo-billing-ec2/config/config.yml
      1. Abiquo database connection: user must be granted select from this host
      2. ec2-billing database: can be hosted on localhost
      3. Abiquo API: user must have Manage bills privilege
    7. Edit the configuration files in config/config.yml


Install and configure billing packages

You will need a server with MariaDB running with access to the Abiquo API, Abiquo database, and public cloud providers. 

  1. Install the billing packages. The package name for Azure is "abiquo-billing-arm" and the package name for Amazon is "abiquo-billing-ec2".

  2. Create the local billing databases and import schemas

    AWS:

    Code Block
    mysql -e "create database ec2_billing"
mysql -h -p -u ec2_billing < /opt/abiquo-billing-ec2/lib/app/schema.sql

    Azure:

    Code Block
    mysql -e "create database arm_billing"
mysql -h -p -u arm_billing < /opt/abiquo-billing-arm/lib/app/schema.sql


  3. Grant

    permissions on

    privileges to a user for the local billing databases

    to the user configured in each config.yml
  4. If the Abiquo database is encrypted with a custom seed, copy that seed with each config.yml
  5. Assign Abiquo user

  6. Configure the billing packages, edit the config.yml file. By default for AWS, this is file is located at /opt/abiquo-billing-ec2/config/config.yml and here is an example:

    Code Block
    abiquo_database:
  host: 10.10.10.36
  user: user
  password: password
  port: 3306
billing_database:
  host: 10.10.10.38
  user: user
  password: password
  port: 3306
abiquo:
  api_url: http://10.10.10.32/api
  user: admin
  password: xabiquo
  seed:


    Notes: 

    1. The billing database is the one you created in the above steps, so it can be hosted on localhost

    2. "seed" is the name of a custom seed that encrypts the Abiquo database. Copy the custom seed into the same directory as the config.yml file for each provider

  7. On the Abiquo database, grant select privileges from this host to the abiquo_database user that will run the bililng scripts 
  8. In Abiquo, check that the Abiquo API user has the Manage bills privilege
  9. In Abiquo, configure Enterprise properties with the name of billing properties 
    1. AWS EC2 
      1.  "billing_bucket" property, with a value of the name of the billing bucket you created in step 1
    2. Azure ARM requires
      1. OfferDurableID
      2. Currency, the default is "USD"
      3. Locale, the default is "en-US"
      4. RegionInfo, the default is "US"
  10. Assign Abiquo users the privileges to Display hybrid dashboard tab, View bills, and optionally to Display VM cost view widget (hybrid tab)

...