VSM is the webapp of Abiquo in charge to check the state of the virtualmachines and notify Abiquo in case of any virtual machine change it's state.
All virtualmachines managed by Abiquo MUST be subscribed in VSM. This subscriptions can be checked through a URL or through the REST api.
VSM runs under Remote Services. So we need to access to the RS IP when we ask for VSM information. Let's put the case that our RS runs on 10.60.13.10.
Let's explain each case:
1. Check the VSM subcriptions through URL:
[root@localhost ~]# lynx --dump http://10.60.13.10/vsm/console?extended
Status
_________________________________________________________________
Check result true
Redis up true
RabbitMQ up true
Configuration
_________________________________________________________________
Version 2.1.2
Redis 127.0.0.1 : 6379
RabbitMQ 127.0.0.1 : 5672
Monitored hypervisors (2)
_________________________________________________________________
Id Hypervisor address Type
2 http://192.168.2.53:8889/ KVM
1 http://192.168.2.52:8889/ KVM
Virtual machines subscriptions (3)
_________________________________________________________________
Id Virtual machine name Running on Last notified state
6 ABQ_dca2e9d8-13f3-4b82-b7fd-c7f1621c0746 http://192.168.2.52:8889/
POWER_ON
5 ABQ_3b725efd-b7a2-47ec-9c80-57c62b561012 http://192.168.2.52:8889/
POWER_ON
4 ABQ_c5449ea4-9fad-4133-9ea3-59da16bffb42 http://192.168.2.53:8889/
POWER_ON
We can see three sections here:
Status: It informs about the state of the VSM webapp.
Configuration: It informs about the version of the VSM and the Redis and Rabbit Server
Monitored hypervisors: A list of the hypervisors monitored by VSM
Virtual machines subscriptions: A list of the virtual machines, informing of the state and the hypervisor are running into.
2. Check the VSM subcriptions through REST api:
With this call, we can see the virtualmachines subscriptions:
[root@localhost ~]# curl -s http://10.60.13.10/vsm/subscriptions | xmllint -format -
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<subscriptions>
<subscription>
<id>5</id>
<monitor>
<address>http://192.168.2.52:8889/</address>
<id>1</id>
<type>KVM</type>
</monitor>
<notified>POWER_ON</notified>
<uuid>ABQ_3b725efd-b7a2-47ec-9c80-57c62b561012</uuid>
</subscription>
<subscription>
<id>4</id>
<monitor>
<address>http://192.168.2.53:8889/</address>
<id>2</id>
<type>KVM</type>
</monitor>
<notified>POWER_ON</notified>
<uuid>ABQ_c5449ea4-9fad-4133-9ea3-59da16bffb42</uuid>
</subscription>
<subscription>
<id>6</id>
<monitor>
<address>http://192.168.2.52:8889/</address>
<id>1</id>
<type>KVM</type>
</monitor>
<notified>POWER_ON</notified>
<uuid>ABQ_dca2e9d8-13f3-4b82-b7fd-c7f1621c0746</uuid>
</subscription>
</subscriptions>
How to check subscriptions on VSM
Please sign in to leave a comment.
0 Comments