Thanks Alex for your quick reply. That tag will appear in the cloud usage
record tag field? I need that for proper billing.
Regards,
Ricardo
From: Alex Mattioli
Sent: Thursday, August 11, 2022 9:41:09 PM
To: users@cloudstack.apache.org
Subject: RE: Usage Type
Hi Ricardo,
You set the tag, say "HDD", on the storage offering and on the primary storage
which you want to use for HDD, then do the same for all other storage types.
When creating a volume the end user will select the offering "HDD, SATA or
NVMe" and ACS will place the volume in a storage
Hi all,
In my cluster I would like to have many primary storages with different types:
HDD, SATA and NVMe, how can I differentiate between them in the usage records?
I see a tag field, but not so sure where to set it.
BR,
Ricardo
Hi Suresh,
I only have these;
root@acs-apac:/home/ubuntu# find / -name "db.properties"
/etc/cloudstack/usage/db.properties
/etc/cloudstack/management/db.properties
root@acs-apac:/home/ubuntu#
Regards,
Cristian
-Original Message-
From: Suresh Kumar Anaparti
Sent: Thursday, August
Hi Cristian,
The listed db configuration parameters looks good.
I think there is another db.properties file from where the
configuration is loaded. Can you find whether any other db.properties
file exists, and check if the parameter "db.cloud.maxActive" is
missing or has invalid value. Please
HI Suresh,
This is what I have in from /etc/management/db.properties
# usage database tuning parameters
db.cloud.port=3306
db.cloud.maxActive=250
db.cloud.maxIdle=30
db.cloud.maxWait=1
db.usage.port=3306
db.usage.maxActive=100
db.usage.maxIdle=30
db.usage.maxWait=1
Hi Cristian,
It seems to be issue with parameter parsing in the db.properties file,
not the password. Please check the value of the parameter
"db.cloud.maxActive" in db.properties file, it should be a valid
integer.
Also, make sure the below parameters in db.properties file have valid
integer
Hello,
Any idea why I see the bellow error? I have the right password in
/management/db.properties and in /usage/db.properties (encrypted)
2022-08-11 09:52:40,160 INFO [utils.component.ComponentContext] (main:null)
(logid:) Configuring
Hi Mevludin,
The volume would be uploaded to secondary storage, and its state is
changed to 'Uploaded' once upload is done. When attaching the uploaded
volume, it is copied to the primary storage and its state is changed
to 'Ready'.
Volumes with the following states: Allocated (newly created),
