Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Abiquo 6.1.x

This section describes three scenarios for the introduction of new Abiquo billing.

With new Abiquo billing running in production

Periodic process

Server

How is it configured?

Default schedule

Default run

On-premise billing

API

abiquo.billing.task.cron property

0 30 0 ? * * *

Every night

Public cloud billing

API

abiquo.billing.task.cron property

0 30 0 ? * * *

Every night

Pricing check

API

abiquo.pricefactor.type.product.check.cron property

0 0 0 1 * *

Accounting process

DB

/etc/cron.d/abiquo-accounting file

0 * * * *

Every hour

Accounting cleanup

DB

/etc/cron.d/abiquo-accounting 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 (question)

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-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 (question)

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.

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 property

0 30 0 ? * * *

Nightly

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

  • No labels