Solved: Configuring Cassandra for vCloud Director 9.1: Emp...

TSSpain · ‎02-07-2019

Hello.

Im using vCD 9.1.0 and few days ago configured Cassandra 3 in our LAB.

I used for installation and integration:

vCloud Availability for vCloud Director: Part 5: Deploy and Configure Cassandra Cluster

We had problems with ssl, so we disabled encrypted connection: vCloud Director 9 can't connect to cassandra DB

It seems installation worked fine but graphs are empty:

Any help will be apreciated.

sk84 · ‎02-07-2019

I can't see in this guide that vCD has been configured for Cassandra. Did you use the "cell-management-tool" to tell vCD to use the Cassandra database for performance metrics?

I also wrote a blog article a few weeks ago on how to use these performance metrics in vCD. But without vCloud Availability.

Maybe it will help you:

Configuring Performance Metrics for vCloud Director 9.5 • Just virtual things

--- Regards, Sebastian VCP6.5-DCV // VCP7-CMA // vSAN 2017 Specialist Please mark this answer as 'helpful' or 'correct' if you think your question has been answered correctly.

View solution in original post

sk84 · ‎02-07-2019

I can't see in this guide that vCD has been configured for Cassandra. Did you use the "cell-management-tool" to tell vCD to use the Cassandra database for performance metrics?

I also wrote a blog article a few weeks ago on how to use these performance metrics in vCD. But without vCloud Availability.

Maybe it will help you:

Configuring Performance Metrics for vCloud Director 9.5 • Just virtual things

--- Regards, Sebastian VCP6.5-DCV // VCP7-CMA // vSAN 2017 Specialist Please mark this answer as 'helpful' or 'correct' if you think your question has been answered correctly.

TSSpain · ‎02-08-2019

Hi, you're right.

I forgot to mention we followed another guide: https://anthonyspiteri.net/enabling-configuring-and-viewing-metrics-in-vcloud-director-9-0/

We checked both Cassandra Keyspace and table were created but contained empty rows.

I think we had some issue installing Cassandra database. We'll create a new Cassandra environment following your install guides:

Installation of Cassandra Database for vCloud Director 9.5 • Just virtual things

Configuring Performance Metrics for vCloud Director 9.5 • Just virtual things

I'll keep you informed

TSSpain · ‎02-08-2019

Hi again,

I've just followed your articles (congrats!!!) but problem persists.

It seems tables were created but vCloud Director cells do not send any information regarding vm metrics...

sk84 · ‎02-08-2019

It may take some time until the metrics are populated in the database.

But can you please provide the output of the following commands, just to check if vcd is configured correctly:

/opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n cassandra.keyspace.name -l
/opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n cassandra.vmm.clusters -l

You can also look in the debug log file "/opt/vmware/vocoud-director/logs/vcloud-container-debug.log" and search for the string "cassandra".

--- Regards, Sebastian VCP6.5-DCV // VCP7-CMA // vSAN 2017 Specialist Please mark this answer as 'helpful' or 'correct' if you think your question has been answered correctly.

TSSpain · ‎02-08-2019

Hi Sebastien,

I'll wait a couple of days...

The output for the requested commands:

[root@cell01 logs]# /opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n cassandra.keyspace.name -l

Property "cassandra.keyspace.name" has value "vcloud_metrics"

[root@cell01 logs]# /opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n cassandra.vmm.clusters -l

Property "cassandra.vmm.clusters" has value "192.168.0.111,192.168.0.112,192.168.0.113,192.168.0.114"

It seems everithing well configured.

I also look in the debug log file:

[root@cell01 logs]# cat /opt/vmware/vcloud-director/logs/vcloud-container-debug.log | grep cassandra

at com.vmware.vcloud.cassandra.client.impl.CassandraClientImpl$1.doWithRetry(CassandraClientImpl.java:193)

at com.vmware.vcloud.cassandra.client.impl.CassandraClientImpl$1.doWithRetry(CassandraClientImpl.java:187)

at com.vmware.vcloud.cassandra.client.impl.CassandraClientImpl.initialize(CassandraClientImpl.java:187)

at com.vmware.vcloud.cassandra.client.impl.CassandraClientImpl$1.doWithRetry(CassandraClientImpl.java:193)

at com.vmware.vcloud.cassandra.client.impl.CassandraClientImpl$1.doWithRetry(CassandraClientImpl.java:187)

at com.vmware.vcloud.cassandra.client.impl.CassandraClientImpl.initialize(CassandraClientImpl.java:187)

at com.vmware.vcloud.cassandra.client.impl.CassandraClientImpl$1.doWithRetry(CassandraClientImpl.java:193)

at com.vmware.vcloud.cassandra.client.impl.CassandraClientImpl$1.doWithRetry(CassandraClientImpl.java:187)

at com.vmware.vcloud.cassandra.client.impl.CassandraClientImpl.initialize(CassandraClientImpl.java:187)

2019-02-08 16:39:47,638 | DEBUG | Spring Context: com.vmware.vcloud.statsfeeder-application | EventManagerImpl | Registered listener com.vmware.vcloud.cassandra.cache.VirtualMachineParentChangedListenerImpl@24a8934a for com.vmware.vcloud.inventory.events.impl.VirtualMachineParentChangedEvent |

at com.vmware.vcloud.cassandra.client.impl.CassandraClientImpl$1.doWithRetry(CassandraClientImpl.java:193)

at com.vmware.vcloud.cassandra.client.impl.CassandraClientImpl$1.doWithRetry(CassandraClientImpl.java:187)

at com.vmware.vcloud.cassandra.client.impl.CassandraClientImpl.initialize(CassandraClientImpl.java:187)

at com.vmware.vcloud.cassandra.client.impl.CassandraClientImpl.getSession(CassandraClientImpl.java:230)

at com.vmware.vcloud.cassandra.client.impl.CassandraClientImpl.buildQueryString(CassandraClientImpl.java:414)

at com.vmware.vcloud.cassandra.client.impl.CassandraClientImpl.readMetrics(CassandraClientImpl.java:313)