Background
NAS-Client-VM instances deployed in GCP and ECFS collocated in the same project automatically have access to the same internal “default network”. A DNS service (Bind) runs on the EMS to facilitate DNS round-robin access to the NAS service – configurable via the GUI during ECFS deployment. The NAS service name is associated to the internal IPs of every node in the cluster. For clients to resolve the NAS service, entries will have to be entered in the “/etc/resolv.conf” identifying the internal IP address of the EMS as the name server.
At least for now, it is necessary to provide a fully qualified domain name (i.e. <hostname>.domain name>) for the NAS service during the deployment of ECFS. Not adhering to this requirement, results in failure of the “named service” to work correctly. The message will be apparent towards the end of the deployment; but currently correcting this via the GUI (under DNS) will not resolve the issue.
Example of Error Message:
Note: Contrary to the message “Deployment Failed”, this error is not catastrophic!
Work-Around to Re-configure/Change FQDN NAS Service Name
Given
Old FQDN: file.elastifile.com
New FQDN (Target): file.acme.com
- Login to EMS via Browser through GCP console or via SSH/putty with paired key
- Sudo as root
- Source environment file – “. elfs_admin” in bash
- Enter the following:
# /elastifile/ecp/bin/ecp-cli dns set –service-name <new name> --name-servers <ems IP> --enodes-ips <ip of storage node1, ip of storage node 2, ip of storage node 3>
For Example:
# /elastifile/ecp/bin/ecp-cli dns set --service-name file.acme.com --name-servers 10.0.0.222 --enodes-ips 10.0.0.173,10.0.0.100,10.0.0.63
Note:
NAS Service Name: file.acme.com
--name-servers: 10.0.0.22 or Internal IP of EMS
--enodes-ips: 10.0.0.173,10.0.0.100,10.0.0.63 – IP of storage nodes (3 of them)
To Confirm Change
emanage# ll -htr /etc/named/zones/
-rw-r--r--. 1 root root 405 Aug 13 08:32 elfs.zone
-rw-r--r-- 1 root root 584 Aug 16 06:53 file.elastifile.com.zone
-rw-r--r-- 1 root root 592 Aug 16 08:07 file.acme.com.zone
From client (resolving new service name):
[root@ip-10-0-0-96 ~]# nslookup file.acme.com
Server: 10.0.0.222
Address: 10.0.0.222#53
Name: file.acme.com
Address: 10.0.0.100
Name: file.acme.com
Address: 10.0.0.173
Name: file.acme.com
Address: 10.0.0.63
From client (resolving old service name): This is the intended result.
[root@ip-10-0-0-96 ~]# nslookup file.elastifile.com
Server: 10.0.0.222
Address: 10.0.0.222#53
** server can't find file.elastifile.com: NXDOMAIN