How-to copy custom network-tags to the new Elastifile storage nodes during online upgrade

Elastifile File System deployments in GCP uses network-tags for some configurations.

Customers also adds network tags from various reasons like firewall configuration.

During Elastifile online upgrade, new storage nodes are created, replacing the old storage nodes.

The problem is - Elastifile upgrade process is aware only to the Elastifile created network tags.

And does not copy the customer added network tags.

This can cause issues during/post upgrade, like failing the upgrade or can break clients connections.

 

The solution is to document the network tags pre upgrade, and add them to the new storage nodes as soon as they are created.

ssh ems-instance

sudo su -

In the below command replace the example:customer-tag1 with the customer network tags

Customer network tags can be one or more, please add them all replacing  - customer-tag1 with all network tags separated by comma with no spaces 

Before running the Elastifile upgrade, execute the below command, with your changes .

The command will update only the new storage nodes as soon as they are created.

while true ; do  gcloud compute instances list --format="table(name,zone,creationTimestamp.date(tz=LOCAL):sort=1)"|grep `hostname`-elfs|grep `date +"%Y-%m-%d"`|awk '{print "gcloud compute instances add-tags "$1" --tags customer-tag1 --zone "$2}'|sh; done

After all NEW storage nodes created, verify from GCP console all network tags listed on all storage nodes.

After verifying all storage nodes runs with the correct network-tags, stop the loop command by - Ctrl-C