Give an option to add label to VIP in a DB2 integrated pacemaker Cluster

If we have multiple instances running on same host then it becomes very difficult to check which ip address maps to which VIP

Example :

Pacemaker cluster with two instances and have two Primary VIPs

[root@sapgc5db201 bin]# crm status
Cluster Summary:
  * Stack: corosync
  * Current DC: sapgc5db202 (version 2.1.2-4.db2pcmk.el8-ada5c3b36e2) - partition with quorum
  * Last updated: Tue Oct  8 21:25:47 2024
  * Last change:  Tue Oct  8 14:47:56 2024 by root via crm_resource on sapgc5db202
  * 2 nodes configured
  * 12 resource instances configured

Node List:
  * Online: [ sapgc5db201 sapgc5db202 ]

Full List of Resources:
  * db2_sapgc5db201_eth0        (ocf::heartbeat:db2ethmon):      Started sapgc5db201
  * db2_sapgc5db202_eth0        (ocf::heartbeat:db2ethmon):      Started sapgc5db202
  * db2_sapgc5db201_db2cm5_0    (ocf::heartbeat:db2inst):        Started sapgc5db201
  * db2_sapgc5db202_db2cm5_0    (ocf::heartbeat:db2inst):        Started sapgc5db202
  * Clone Set: db2_db2cm5_db2cm5_CM5-clone [db2_db2cm5_db2cm5_CM5] (promotable):
    * Masters: [ sapgc5db201 ]
    * Slaves: [ sapgc5db202 ]
  * db2_db2cm5_db2cm5_CM5-primary-OIP   (ocf::heartbeat:aws-vpc-move-ip):        Started sapgc5db201
  * db2_sapgc5db201_db2cc5_0    (ocf::heartbeat:db2inst):        Started sapgc5db201
  * db2_sapgc5db202_db2cc5_0    (ocf::heartbeat:db2inst):        Started sapgc5db202
  * Clone Set: db2_db2cc5_db2cc5_CC5-clone [db2_db2cc5_db2cc5_CC5] (promotable):
    * Masters: [ sapgc5db201 ]
    * Slaves: [ sapgc5db202 ]
  * db2_db2cc5_db2cc5_CC5-primary-OIP   (ocf::heartbeat:aws-vpc-move-ip):        Started sapgc5db201

  
In the following ip addr output we can see the VIP but cannot tell which instance/db it belongs to

[root@sapgc5db201 bin]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9001 qdisc mq state UP group default qlen 1000
    link/ether 02:f0:9f:e1:55:03 brd ff:ff:ff:ff:ff:ff
    altname enp0s5
    altname ens5
    inet 10.116.41.58/26 brd 10.116.41.63 scope global dynamic noprefixroute eth0
       valid_lft 2713sec preferred_lft 2713sec
inet 10.116.39.11/32 scope global eth0
       valid_lft forever preferred_lft forever
inet 10.116.39.20/32 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::f0:9fff:fee1:5503/64 scope link
       valid_lft forever preferred_lft forever

It would be very useful if we can have an option to add a label in the above output to easily differentiate which VIP belongs to which database instance

Something like following

    inet 10.116.39.11/32 scope global eth0:CC5
       valid_lft forever preferred_lft forever
    inet 10.116.39.20/32 scope global eth0:CM5
       valid_lft forever preferred_lft forever     

Where CC5 and CM5 are the database name on different instance

It would be nice if we can have a label option where we can define the label associated with the VIP during creation.

db2cm -create -aws -primaryVIP <ip-address> -rtb <rtb1,rtb2,rtbn> -db <db-name> -instance <instance-name> -label <label-name>