Page Comparison

...

In all versions, Abiquo metrics usage system: abiquo-metrics-usage-system /wiki/spaces/SUP/pages/509804549

Abiquo 6.2

TODO

Abiquo 6.1

...

With new Abiquo billing running in production

Periodic process	Server	How is it

run

configured?	Default schedule	Default run

Abiquo on

On-premise billing	API	`abiquo.billing.task.cron` property	`0 30 0 ? * * *`	Every night
Public cloud billing	API	`abiquo.billing.task.cron`

Cron expression to run the consolidation of usage and cost from private cloud and public cloud providers.
If the cron expression is not compatible with Quartz, the platform will use the default.

To generate valid expressions, you can use this tool: https://www.freeformatter.com/cron-expression-generator-quartz.html . Some other commonly used tools may generate invalid expressions.

property	`0 30 0 ? * * *`	Every night
Pricing check	API	`abiquo.pricefactor.type.product.check.cron`

Cron expression to run the periodic checks of price factor bill type and products.

property

0 0 0 1 * *

abiquo.tagging.synccheckcron

Cron expression to run the periodic tag synchronization by enterprise. If the cron expression is not compatible with Quartz, the platform will use the default.

0 0 */4 ? * *

Abiquo accounting

...


Accounting process	DB	`/etc/cron.d/abiquo-accounting` file	`0 * * * *`	Every hour
Accounting cleanup	DB	`/etc/cron.d/abiquo-accounting`

...

Code Block

# Runs every hour
0  * * * * root mysql -uADMUSER -pADMPASS -hlocalhost -e "CALL kinton.UpdateAccounting();"

# Runs every Sunday at 12:00 and deletes records older than a week.
0 12 * * 0 root mysql -uADMUSER -pADMPASS -hlocalhost -e "CALL kinton.DeleteOldRegisteredEvents(168);"

Old push Abiquo private billing data for dashboard

For old billing (before the entry of new billing in 6.1 or before the activation of new billing).

...

file	`0 12 * * 0`	Every Sunday at `12:00`
Tags	API	`abiquo.tagging.synccheckcron` property	`0 0 /4 ? *`
Reporting cleanup	DB	`/etc/cron.d/abiquo-reporting` file	`0 1 * * *`

When new billing and old billing are both running to test new billing

Periodic process	Server	How is it configured?	Default schedule	Default run
On-premise billing	API	`abiquo.billing.task.cron` property	`0 30 0 ? * * *`	Nightly
Public cloud billing	API	`abiquo.billing.task.cron` property	`0 30 0 ? * * *`	Nightly
Pricing check	API	`abiquo.pricefactor.type.product.check.cron` property	`0 0 0 1 * *`
Accounting process	DB	`/etc/cron.d/abiquo-`

...

Old Abiquo billing integration

...

`accounting` file	`0 * * * *`	Hourly
Accounting cleanup	DB	`/etc/cron.d/abiquo-`

...

Code Block
0 1 * * * root cd /opt/abiquo-billing; /bin/bash /opt/abiquo-billing/billing.sh 2>&1 \| tee --append /var/log/billing.log

Note that there is also a cron command to update the enterprise mapping, which maybe in teh file: abiquo-billing-mapping. File content is:

10 0 * * * root mysql --host specifythedbhost --user root --password yourpass --execute "INSERT IGNORE INTO kinton.billing_account_mapping (idAbiquo, idMappingType, billingAttributeName, billingAttributeValue) (SELECT idEnterprise, 1, 'ENTERPRISE', e.name FROM kinton.enterprise e);"

Notes from the billing comparison page

Before you enable on-premise billing, stop the abiquo-private-billing cron job
To configure the cron job that runs on-premise billing use the Abiquo property.
When you transition to on-premise billing, you can stop the old abiquo-billing cron job

Abiquo reporting

To periodically remove temporary tables from the DB, add the following cron job on the reporting or database server.

Code Block
0 1 * * * root mysql -ureporter -preporter -e "CALL kinton_reporting.TruncateRLSTables ();"

Abiquo 6.0

Properties

...

`accounting` file	`0 12 * * 0`	Sundays at `12:00`
Tags	API	`abiquo.tagging.synccheckcron` property	`0 0 /4 ? *`
Reporting cleanup	DB	`/etc/cron.d/abiquo-reporting` file	`0 1 * * *`	Hourly
Old billing	Reporting	`/etc/cron.d/abiquo-billing`	`0 1 * * *`	Hourly
Old billing enterprise mapping	DB	`/etc/cron.d/abiquo-billing-mapping`	`10 0 * * *`	Nightly at `00:10`

After upgrade to 6.1.x and before you activate new billing

In Abiquo 6.1, we introduced the new on-premise billing, which uses the same property as public cloud billing to configure its cron job. We also introduced the new price factors, which have a cron check.

Info
If you are using old billing, you should disable new billing in Configuration view as part of the upgrade process.

Periodic process	Server	How is it configured?	Default schedule	Default run
On-premise billing	API	`abiquo.billing.task.cron` property	`0 30 0 ? * * *`	Nightly
Public cloud billing	API	`abiquo.billing.task.cron` property	`0 30 0 ? * * *`	Nightly
Price factor check	API	`abiquo.pricefactor.type.product.check.cron` property	`0 0 0 1 * *`
Accounting process	DB	`/etc/cron.d/abiquo-accounting` file	`0 * * * *`	Hourly
Accounting cleanup	DB	`/etc/cron.d/abiquo-accounting` file	`0 12 * * 0`	Sundays at `12:00`
Tags	API	`abiquo.tagging.synccheckcron` property	`0 0 /4 ? *`
Reporting cleanup	DB	`/etc/cron.d/abiquo-reporting` file	`0 1 * * *`	Hourly
Old billing	Reporting	`/etc/cron.d/abiquo-billing`	`0 1 * * *`	Hourly
Old billing enterprise mapping	DB	`/etc/cron.d/abiquo-billing-mapping`	`10 0 * * *`	Nightly at `00:10`
Private billing dashboard	Reporting	`/etc/cron.d/abiquo-billing-private`

Abiquo 6.0.x

Abiquo 6.0.x uses the old billing processes and has an optional process to push private billing to the dashboard.

Periodic process	Server	How is it configured?	Default schedule	Default run
Public cloud billing	API	`abiquo.billing.task.cron`

Cron expression to run the consolidation of usage and cost from public cloud providers.
If the cron expression is not compatible with Quartz, the platform will use the default.