Cloudstack 4.22 and Tarrif Plugin - How to give 1 IP Address and VR for free and tarrif the others?

[EduFrazao]

Hi!
I want to build a tarrif activation rule, where I can give the first VR (with their SourceNAT).
But I want to tarrif another IP address that are not SourceNAT and tarrif aditional Virtual Routers.

I have 3 kinds of Network Offerings here, with different internet bandwidth and I want to apply differnt tarrifs for each one. I can add tags to this network offerings.

Is it possible?

[winterhazel]

@EduFrazao just confirming some points to understand the intended behaviour:

1. Do you want to (1) always tariff guest networks, with a value depending on the network offering, regardless of how many IP addresses and virtual routers it has (additional addresses/virtual routers in the network would receive an additional fee), or (2) only apply a tariff for networks that have additional addresses/virtual routers?
2. Should the value applied to the additional IP addresses and virtual routers be different depending on the offering used by the guest network?
3. Should the tariff be applied to the SourceNAT address and the first virtual router of additional guest networks belonging to an account?

There are some limits to what can be done with tariffs at the moment. They will need to be extended with a few more preset variables to allow applying a tariff to additional virtual routers. Depending on your answers, there will have to be a few more changes for IP addresses as well.

[EduFrazao]

Hi @winterhazel!
My idea is to give the first virtual router as free and charge the others.
And I want to charge IP's that are not SourceNats.

If possible, I would like to apply different fees to different kinds of networks (identified by service offering names or tags), for example networks with 10Gbit of internet connection, etc.

[nickaccuweb]

@EduFrazao

Yes, this is partially possible using CloudStack's Quota Plugin and tariff activation rules.

1. First Source NAT IP free, additional IPs chargeable

For the IP_ADDRESS tariff (usage type 3), you can use the following activation rule to exclude Source NAT addresses from billing:

resourceType !== 'SourceNat'

This allows you to charge additional public IP addresses while excluding Source NAT IPs.

2. Different tariffs for your three Network Offerings

You can use the NETWORK_OFFERING tariff (usage type 13) and apply different pricing based on the offering's name or tag.

For example, you could create separate pricing rules for your 100 Mbps, 500 Mbps and 1 Gbps offerings.

However, CloudStack 4.22 tracks Network Offering usage at the instance/network attachment level, so these tariffs should not be treated as direct Virtual Router charges.

3. First Virtual Router free, additional Virtual Routers chargeable

This part requires some additional logic. CloudStack does not provide a separate per-Virtual-Router tariff that automatically identifies the first router belonging to an account.

If your intention is to include the first isolated network and its Virtual Router for free, then charge for additional isolated networks, I would recommend using CloudStack's usage records together with an external billing system.

The billing system can identify the account's networks, exclude the first eligible network, and apply the appropriate price to each additional network based on its Network Offering.

Also, if you are using redundant Virtual Routers for HA, remember that two routers can belong to the same network, so they should not automatically be treated as two separately billable networks.

You can check the available tariff variables using the quotaPresetVariablesList API and validate your activation rules using quotaValidateActivationRule before applying them.

Hope this helps!

Regards,
Nick R
AccuWeb.Cloud