{"id":1907,"date":"2022-03-01T09:49:03","date_gmt":"2022-03-01T00:49:03","guid":{"rendered":"https:\/\/www.insilico.jp\/blog\/?p=1907"},"modified":"2022-03-01T09:49:47","modified_gmt":"2022-03-01T00:49:47","slug":"nis-nfs-ssh_key-cluster","status":"publish","type":"post","link":"https:\/\/www.insilico.jp\/blog\/2022\/03\/01\/nis-nfs-ssh_key-cluster\/","title":{"rendered":"Configuring SSH key-based authentication, NIS and NFS in a Linux computer cluster"},"content":{"rendered":"\n

I am back with a blog, this time about configuring SSH key-based login, Network Information Service (NIS), and Network File System (NFS), which are considered 3 of the most important aspects of setting up a computer cluster, big or small. By a cluster, I am referring to a network of computers comprising of a head node and several compute nodes. I gave a rough example in Figure 1. I will be using the same IP address values, hostnames, etc. as examples in my succeeding explanations.<\/p>\n\n\n\n

\"\"
Figure 1. An example of a computer cluster within a local area network (LAN). <\/figcaption><\/figure>\n\n\n\n

Whenever we upgrade our OS, of course, we have to set up everything from 0, system configurations, network settings, etc. Those are things that you don’t do frequently so you almost forget how you go about doing it and most of the time, new OS releases specify different ways of configuring your system. So you have to search the web for documentation and tutorials. Configuring SSH key-based authentication, NIS and NFS are almost always done as a set, so I prefer finding a good tutorial that tells me how to do them in one sweep, something I haven’t been able to achieve. I thought, probably, I am not the only one longing for this, sort of, one-stop tutorial and that writing one myself would probably help others. Hence, this blog was born.<\/p>\n\n\n\n

The procedures that will be discussed here will be based on the Ubuntu Server 20.04 OS which is assumed to be installed in both the head and compute nodes. It is also assumed that you have created an admin user and normal users in all nodes.<\/p>\n\n\n\n

In this blog, please note that in all code boxes, usernames, domain names, hostnames, IP addresses are just examples and should be replaced based on your network configurations.<\/strong> Texts following “\/\/” are comments I have written for clarity purposes. Now, let’s get started.<\/p>\n\n\n\n

Setting up SSH key-based authentication<\/h2>\n\n\n\n

In order to be able to use SSH key-based login, normal users should, first, create an SSH key pair. In the command below, I recommend not setting a passphrase because it will defeat the purpose of being able to log in without being asked to input anything.<\/p>\n\n\n\n

achilles@myubuntu:~$ ssh-keygen\n\nGenerating public\/private rsa key pair.\nEnter file in which to save the key (\/home\/achilles\/.ssh\/id_rsa):   # Enter or input changes if you want\nCreated directory '\/home\/achilles\/.ssh'.\nEnter passphrase (empty for no passphrase):   # set passphrase (if set no passphrase, Enter with empty)\nEnter same passphrase again:\nYour identification has been saved in \/home\/achilles\/.ssh\/id_rsa\nYour public key has been saved in \/home\/achilles\/.ssh\/id_rsa.pub\nThe key fingerprint is:\nSHA256:7gvfoJosmvKWbihuOIap@povHeopnjbmXaUylmSuVgD achilles@myubuntu\nThe key's randomart image is:<\/mark>\n\n\/\/ some ascii characters are usually displayed here<\/mark><\/code><\/pre>\n\n\n\n
Once you have created your key pair, copy it to the server where you also have an account, using the command below.<\/p>\n\n\n\n
achilles@myubuntu:~$ ssh-copy-id -i ~\/.shh\/id_rsa.pub achilles@192.168.10.100<\/mark><\/code><\/pre>\n\n\n\n
You will be asked for your login password so type it and press enter. Once the command finished successfully, you should try logging in using your ssh key.<\/p>\n\n\n\n
achilles@myubuntu:~$ ssh -i ~\/.shh\/id_rsa achilles@192.168.10.100<\/mark><\/code><\/pre>\n\n\n\n
You should be able to log in without being asked for a password. You will be asked if you want to add the server you are logging in to the list of known_hosts. Just answer yes to that and you will not be asked anymore the next time you log in.<\/p>\n\n\n\n
A convenient way of logging in to a remote server is by creating a config file that holds your ssh login information. You can create one by following the instructions below.<\/p>\n\n\n\n
achilles@myubuntu:~$ cd .ssh\/\nachilles@myubuntu:.ssh$ vi config<\/mark>\n\/\/ input the following information for every remote server you login<\/mark>\nHost zeus\nHostName 192.168.10.100   \nUser achilles\nIdentityFile ~\/.ssh\/id_rsa<\/mark>\n\n\/\/ you can then login by simply issuing the following command<\/mark>\nachilles@myubuntu:~$ ssh zeus<\/mark><\/code><\/pre>\n\n\n\n
Once every normal user has finished setting up SSH key-based authentication, the admin user should disable password-based login for all of them by modifying the \/etc\/ssh\/sshd_config file.<\/p>\n\n\n\n
root@zeus:~# vi \/etc\/ssh\/sshd_config\n<\/mark>\n\/\/ write at end of file if you want to disable password login\n\/\/ for achilles, prometheus and odysseus<\/mark>\nMatch User achilles,prometheus,odysseus\n    PasswordAuthentication no\n<\/mark>\n\/\/ save the file then restart ssh service<\/mark>\nroot@zeus:~# systemctl restart ssh<\/mark><\/code><\/pre>\n\n\n\n
If a job scheduling application such as Torque or OpenPBS is going to be installed in combination with NIS and NFS services, normal users should add the contents of the id_rsa.pub (public key) file to the authorized_keys file. If there is no such file yet, create one. Doing that when the NFS service is activated and the server \/home directory is mounted in the compute nodes prevents IO errors in user home directories after jobs have finished execution. That is, it allows results of job executions to be written in user home directories.<\/p>\n\n\n\n
Setting up Network Information Service (NIS)<\/h2>\n\n\n\n
NIS is, sort of, a directory service that enables sharing of information, such as hostnames, usernames, and passwords, between hosts within a network. This information is managed in one location (master server) and is accessed by client servers whenever needed. Depending on the number of clients available, slave servers may also be employed. Slave servers also maintain the same information as the master server but are accessed only during times when the master server is inaccessible or when the network is bogged down by heavy traffic.<\/p>\n\n\n\n
Switch to the admin user account you have created previously then to the root user. That step may be a little cumbersome, you might say, but it gives you some sort of security because you can restrict access to the root account by restricting access to the admin user to a select few.<\/p>\n\n\n\n
Before installing the necessary packages, update the repository first. Let us, first, configure the NIS master server.<\/p>\n\n\n\n
admin@zeus:~$ sudo su -\n[sudo] password for admin:<\/mark>        \/\/ type password at the prompt<\/mark>\n\nroot@zeus:~# apt update<\/mark>           \/\/ update repositories<\/mark><\/code><\/pre>\n\n\n\n
The last command above updates the registered package repositories before returning to the prompt.<\/p>\n\n\n\n
Next, install the NIS package.<\/p>\n\n\n\n
root@zeus:~# apt -y install nis<\/mark><\/code><\/pre>\n\n\n\n
The command above will start the installation of the nis package and will prompt you for a domain name. The domain name is not the internet domain you are using, rather, it is some sort of a name you have decided to assign to the network you are in. An example screenshot is shown below.<\/p>\n\n\n\n
\"\"
Figure 2. A prompt asking for the domain name to be used in NIS. The same prompt will also appear when installing NIS in client servers.<\/figcaption><\/figure>\n\n\n\n
Continue with the following instructions.<\/p>\n\n\n\n
\/\/ edit the \/etc\/default\/nis file.<\/mark>\nroot@zeus:~# vi \/etc\/default\/nis<\/mark>\n\n\/\/ make the following change indicate below<\/mark>\nNISSERVER=master<\/mark>\n\n\/\/edit the \/etc\/ypserv.securenets file<\/mark>\nroot@zeus:~# vi \/etc\/ypserv.securenets<\/mark>\n\n\/\/ comment out the line containing '0.0.0.0' as indicated below<\/mark>\n# This line gives access to everybody. PLEASE ADJUST!\n# 0.0.0.0      0.0.0.0<\/mark>\n\n\/\/ at the end, add range of IP addresses you allow access\n\/\/ in the example below all hosts that belong to the 192.168.10.0 network\n\/\/ will be allowed access<\/mark>\n255.255.255.0   192.168.10.0<\/mark>\n\n\/\/ edit the \/etc\/hosts file<\/mark>\nroot@zeus:~# vi \/etc\/hosts<\/mark>\n\n\/\/ keep the localhost uncommented<\/mark>\n127.0.0.1       localhost<\/mark>\n\n\/\/ add IP addresses of hosts that are allowed to use NIS\n\/\/ below are sample entries for a master server and 5 clients<\/mark>\n192.168.10.100      zeus\n192.168.10.1        ares\n192.168.10.2        athena\n192.168.10.3        hermes\n192.168.10.4        aphrodite\n192.168.10.5        apollo<\/mark>\n\n\/\/ restart rpcbind and nis services<\/mark>\nroot@zeus:~# systemctl restart rpcbind nis<\/mark>\n\n\/\/ update the NIS database<\/mark>\nroot@zeus:~# \/usr\/lib\/yp\/ypinit -m\n\nAt this point, we have to construct a list of the hosts which will run NIS\nservers.  server is in the list of NIS server hosts.  Please continue to add the names for the other hosts, one per line.  When you are done with the\nlist, type a <control D>.\n        next host to add:  zeus\n        next host to add:  # Ctrl + D key\nThe current list of NIS servers looks like this:\n\nzeus\n\nIs this correct?  [y\/n: y]  y\nWe need a few minutes to build the databases...\nBuilding \/var\/yp\/olympus\/ypservers...\nRunning \/var\/yp\/Makefile...\nmake[1]: Entering directory '\/var\/yp\/olympus'\nUpdating passwd.byname...\nUpdating passwd.byuid...\nUpdating group.byname...\nUpdating group.bygid...\nUpdating hosts.byname...\nUpdating hosts.byaddr...\nUpdating rpc.byname...\nUpdating rpc.bynumber...\nUpdating services.byname...\nUpdating services.byservicename...\nUpdating netid.byname...\nUpdating protocols.bynumber...\nUpdating protocols.byname...\nUpdating netgroup...\nUpdating netgroup.byhost...\nUpdating netgroup.byuser...\nUpdating shadow.byname... Ignored -> merged with passwd\nmake[1]: Leaving directory '\/var\/yp\/olympus'\n\nzeus has been set up as a NIS master server.\n\nNow you can run ypinit -s zeus on all slave server.<\/mark><\/code><\/pre>\n\n\n\n
The NIS server configuration is now complete. However, you should run the following command whenever you add new users to your network.<\/p>\n\n\n\n
root@zeus:~# cd \/var\/yp\n\nroot@zeus:\/var\/yp# make<\/mark><\/code><\/pre>\n\n\n\n
So now, let’s get on to setting up the NIS clients. <\/p>\n\n\n\n
As with the configuration of the NIS server, the configuration of the NIS client also starts with updating the repositories after switching to the root user. That is actually the basic routine whenever you are installing new packages or applications in a Linux system. Then, you also install the NIS package using the same command: apt -y install nis. That will also prompt you for the NIS domain name (Figure 1). Enter the same domain name as before then press enter.  Next, perform the following steps.<\/p>\n\n\n\n
\/\/ edit the file \/etc\/yp.conf<\/mark>\nroot@ares:~# vi \/etc\/yp.conf\n\n#\n# yp.conf       Configuration file for the ypbind process. You can define\n#               NIS servers manually here if they can't be found by\n#               broadcasting on the local net (which is the default).\n#\n#               See the manual page of ypbind for the syntax of this file.\n#\n# IMPORTANT:    For the \"ypserver\", use IP addresses, or make sure that\n#               the host is in \/etc\/hosts. This file is only interpreted\n#               once, and if DNS isn't reachable yet the ypserver cannot\n#               be resolved and ypbind won't ever bind to the server.\n\n# ypserver ypserver.network.com\n#<\/mark>\n\/\/ add the following information to the file<\/mark>\ndomain olympus server zeus<\/mark>\n\n\/\/ make modifications to the \/etc\/nsswitch.conf file.\nroot@ares:~# vi \/etc\/nsswitch.conf<\/mark>\n\n\/\/ add 'nis' as indicated below<\/mark>\npasswd:         files systemd nis\ngroup:          files systemd nis\nshadow:         files nis\ngshadow:        files\n\nhosts:          files dns nis<\/mark>\n\n\/\/ restart the rpcbind and nis services.<\/mark>\nroot@ares:~# systemctl restart rpcbind nis<\/mark><\/code><\/pre>\n\n\n\n
Now that you have completed the setup, check if it’s working fine by executing the command ypwhich. That should tell you the name of your NIS server.<\/p>\n\n\n\n
root@ares:~# ypwhich\nzeus\nroot@ares:~# <\/mark><\/code><\/pre>\n\n\n\n
Setting up Network File System (NFS)<\/h2>\n\n\n\n
Network File System  (NFS) is a protocol that allows a file system to be simultaneously mounted on client servers. This allows users logged in on client servers to access their home directory in the master server much like accessing a local file system. Assuming that the master server \/home folder is mounted in the client servers’ \/home folder and each user’s public key is added in the authorized_keys file, it will not require the installation of user ssh public keys in the client servers themselves. In cases where a job scheduling system is being used in a cluster, it also assures that there will be no write permission errors after executions of jobs in the compute nodes (client servers).<\/p>\n\n\n\n
Now, let’s configure the NFS server first.<\/p>\n\n\n\n
\/\/ install the NFS server package<\/mark>\nroot@zeus:~# apt -y install nfs-kernel-server<\/mark>\n\n\/\/ modify the \/etc\/idmapd.conf file:<\/mark>\nroot@zeus:~# vi \/etc\/idmapd.conf<\/mark>\n\n\/\/ uncomment then change to the correct domain name<\/mark>\nDomain = olympus<\/mark>\n\/\/ save and close file<\/mark>\n\n\/\/ make changes to the \/etc\/exports file.<\/mark>\nroot@zeus:~# vi \/etc\/exports \n<\/mark>\n\/\/ allow the \/home folder to be exported to your network\n\/\/ where your computer cluster is located by adding the line below<\/mark>\n\/home    192.168.10.0\/24(rw,no_root_squash)<\/mark>\n\n\/\/ After editing and saving the file, restart the nfs-server.<\/mark>\nroot@zeus:~# systemctl restart nfs-server<\/mark>\n\n\/\/ find the UUID of the \/home folder in your file system<\/mark>\nroot@zeus:~# blkid<\/mark>\n\/\/ executing the command above will show the UUID of\n\/\/ every partition in the file system\n\/\/ take note of the UUID of the partition where the \/home folder is mounted<\/mark>\n\/\/ you will need it in the next section<\/mark><\/code><\/pre>\n\n\n\n
Now, let’s take care of the NFS clients. Log in to one of the clients and switch to the root user. Then perform the following procedure.<\/p>\n\n\n\n
\/\/ install the NFS package<\/mark>\nroot@ares:~# apt -y install nfs-common <\/mark>\n\n\/\/ edit the \/etc\/idmapd.conf file<\/mark>\nroot@ares:~# vi \/etc\/idmapd.conf<\/mark>\n\n\/\/ uncomment then set to proper domain name<\/mark>\nDomain = olympus<\/mark>\n\/\/ save and close the file<\/mark>\n\n\/\/ edit the \/etc\/fstab file<\/mark>\nroot@ares:~# vi \/etc\/fstab<\/mark>\n\n\/\/ add the following at the end of the file if you are mounting\n\/\/ at the \/home folder, otherwise, change to preferred mount point\n\/\/ replace <uuid> with the UUID you found above after issuing the\n\/\/ blkid command<\/mark>\nUUID=<uuid> \/home xfs defaults 0 0<\/mark>\n\/\/ save and close file<\/mark>\n\n\nroot@ares:~# vi \/etc\/fstab<\/mark>\n<\/code><\/pre>\n\n\n\n
To enable dynamic mounting let us configure autofs.<\/p>\n\n\n\n
\/\/ install the autofs package<\/mark>\nroot@ares:~# apt -y install autofs <\/mark>\n\n\/\/ edit the \/etc\/auto.master file<\/mark>\nroot@ares:~# vi \/etc\/auto.master<\/mark>\n\/\/ add to end of file<\/mark>\n\/-    \/etc\/auto.mount<\/mark><\/mark>\n\/\/ save and close the file<\/mark>\n\n\/\/ create the \/etc\/auto.mount file<\/mark>\nroot@ares:~# vi \/etc\/auto.mount<\/mark>\n\/\/ add the following at the end of the file<\/mark>\n\/home   -fstype=nfs,rw  zeus:\/home<\/mark>\n\/\/ save and close file<\/mark>\n\n\/\/ restart autofs<\/mark>\nroot@ares:~# systemctl restart autofs<\/mark><\/code><\/pre>\n\n\n\n
Now that you have finished configuring NFS in one of the clients, repeat the same procedure with all the other remaining clients.<\/p>\n\n\n\n
To check if the \/home folder is properly mounted, log in with a normal user account to the NFS server (head node) then execute ‘ls -ltra’. Then, log in to any client using the same account. You should be able to log in via ssh key authentication without any problem. Once you are logged in, issue the same ‘ls -ltra’ command. You should be able to see the same file list as when you executed the same command when you logged in to the NFS server.<\/p>\n\n\n\n
And that’s it, you already have a computer cluster with a working NIS, NFS, and SSH authentication system.<\/p>\n\n\n\n
See you again soon!<\/p>\n","protected":false},"excerpt":{"rendered":"
I am back with a blog, this time about configuring SSH key-based login, Network Information Service (NIS), and…<\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19],"tags":[56,55,54,57],"class_list":["post-1907","post","type-post","status-publish","format-standard","hentry","category-linux","tag-nfs","tag-nis","tag-ssh-key","tag-ubuntu-20-04"],"yoast_head":"\nConfiguring SSH key-based authentication, NIS and NFS in a Linux computer cluster - In Silico \u5275\u85ac<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.insilico.jp\/blog\/2022\/03\/01\/nis-nfs-ssh_key-cluster\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Configuring SSH key-based authentication, NIS and NFS in a Linux computer cluster - In Silico \u5275\u85ac\" \/>\n<meta property=\"og:description\" content=\"I am back with a blog, this time about configuring SSH key-based login, Network Information Service (NIS), and...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.insilico.jp\/blog\/2022\/03\/01\/nis-nfs-ssh_key-cluster\/\" \/>\n<meta property=\"og:site_name\" content=\"In Silico \u5275\u85ac\" \/>\n<meta property=\"article:published_time\" content=\"2022-03-01T00:49:03+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-03-01T00:49:47+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.insilico.jp\/blog\/wp-content\/uploads\/2022\/02\/computer_cluster-3-1024x724.png\" \/>\n<meta name=\"author\" content=\"Enzo Kawasaki\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u57f7\u7b46\u8005\" \/>\n\t<meta name=\"twitter:data1\" content=\"Enzo Kawasaki\" \/>\n\t<meta name=\"twitter:label2\" content=\"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593\" \/>\n\t<meta name=\"twitter:data2\" content=\"33\u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/2022\\\/03\\\/01\\\/nis-nfs-ssh_key-cluster\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/2022\\\/03\\\/01\\\/nis-nfs-ssh_key-cluster\\\/\"},\"author\":{\"name\":\"Enzo Kawasaki\",\"@id\":\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/#\\\/schema\\\/person\\\/f3e060be38907cda2a9c1cfcd17b1d00\"},\"headline\":\"Configuring SSH key-based authentication, NIS and NFS in a Linux computer cluster\",\"datePublished\":\"2022-03-01T00:49:03+00:00\",\"dateModified\":\"2022-03-01T00:49:47+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/2022\\\/03\\\/01\\\/nis-nfs-ssh_key-cluster\\\/\"},\"wordCount\":1354,\"image\":{\"@id\":\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/2022\\\/03\\\/01\\\/nis-nfs-ssh_key-cluster\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/02\\\/computer_cluster-3-1024x724.png\",\"keywords\":[\"NFS\",\"NIS\",\"SSH key\",\"Ubuntu 20.04\"],\"articleSection\":[\"Linux\u95a2\u9023\"],\"inLanguage\":\"ja\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/2022\\\/03\\\/01\\\/nis-nfs-ssh_key-cluster\\\/\",\"url\":\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/2022\\\/03\\\/01\\\/nis-nfs-ssh_key-cluster\\\/\",\"name\":\"Configuring SSH key-based authentication, NIS and NFS in a Linux computer cluster - In Silico \u5275\u85ac\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/2022\\\/03\\\/01\\\/nis-nfs-ssh_key-cluster\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/2022\\\/03\\\/01\\\/nis-nfs-ssh_key-cluster\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/02\\\/computer_cluster-3-1024x724.png\",\"datePublished\":\"2022-03-01T00:49:03+00:00\",\"dateModified\":\"2022-03-01T00:49:47+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/#\\\/schema\\\/person\\\/f3e060be38907cda2a9c1cfcd17b1d00\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/2022\\\/03\\\/01\\\/nis-nfs-ssh_key-cluster\\\/#breadcrumb\"},\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/2022\\\/03\\\/01\\\/nis-nfs-ssh_key-cluster\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"ja\",\"@id\":\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/2022\\\/03\\\/01\\\/nis-nfs-ssh_key-cluster\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/02\\\/computer_cluster-3.png\",\"contentUrl\":\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/02\\\/computer_cluster-3.png\",\"width\":1123,\"height\":794},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/2022\\\/03\\\/01\\\/nis-nfs-ssh_key-cluster\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"\u30db\u30fc\u30e0\",\"item\":\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Configuring SSH key-based authentication, NIS and NFS in a Linux computer cluster\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/\",\"name\":\"In Silico \u5275\u85ac\",\"description\":\"\u3053\u306e\u30d6\u30ed\u30b0\u30b5\u30a4\u30c8\u306f\u3001In silico\u5275\u85ac\u306b\u95a2\u9023\u3059\u308b\u7814\u7a76\u8ad6\u6587\u3084\u30bd\u30d5\u30c8\u30a6\u30a7\u30a2\u30fb\u30c4\u30fc\u30eb\u306e\u5229\u7528\u3084\u30d7\u30ed\u30b0\u30e9\u30df\u30f3\u30b0\u306a\u3069\u306b\u3064\u3044\u3066\u3054\u7d39\u4ecb\u3057\u3066\u3044\u307e\u3059\u3002\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ja\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/#\\\/schema\\\/person\\\/f3e060be38907cda2a9c1cfcd17b1d00\",\"name\":\"Enzo Kawasaki\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ja\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/74a51ec0e05cc3f7f23feff1be9436059572ce3e2e30570816149e2d4e6a91b4?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/74a51ec0e05cc3f7f23feff1be9436059572ce3e2e30570816149e2d4e6a91b4?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/74a51ec0e05cc3f7f23feff1be9436059572ce3e2e30570816149e2d4e6a91b4?s=96&d=mm&r=g\",\"caption\":\"Enzo Kawasaki\"},\"url\":\"https:\\\/\\\/www.insilico.jp\\\/blog\\\/author\\\/kawasaki\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Configuring SSH key-based authentication, NIS and NFS in a Linux computer cluster - In Silico \u5275\u85ac","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.insilico.jp\/blog\/2022\/03\/01\/nis-nfs-ssh_key-cluster\/","og_locale":"ja_JP","og_type":"article","og_title":"Configuring SSH key-based authentication, NIS and NFS in a Linux computer cluster - In Silico \u5275\u85ac","og_description":"I am back with a blog, this time about configuring SSH key-based login, Network Information Service (NIS), and...","og_url":"https:\/\/www.insilico.jp\/blog\/2022\/03\/01\/nis-nfs-ssh_key-cluster\/","og_site_name":"In Silico \u5275\u85ac","article_published_time":"2022-03-01T00:49:03+00:00","article_modified_time":"2022-03-01T00:49:47+00:00","og_image":[{"url":"https:\/\/www.insilico.jp\/blog\/wp-content\/uploads\/2022\/02\/computer_cluster-3-1024x724.png","type":"","width":"","height":""}],"author":"Enzo Kawasaki","twitter_card":"summary_large_image","twitter_misc":{"\u57f7\u7b46\u8005":"Enzo Kawasaki","\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593":"33\u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.insilico.jp\/blog\/2022\/03\/01\/nis-nfs-ssh_key-cluster\/#article","isPartOf":{"@id":"https:\/\/www.insilico.jp\/blog\/2022\/03\/01\/nis-nfs-ssh_key-cluster\/"},"author":{"name":"Enzo Kawasaki","@id":"https:\/\/www.insilico.jp\/blog\/#\/schema\/person\/f3e060be38907cda2a9c1cfcd17b1d00"},"headline":"Configuring SSH key-based authentication, NIS and NFS in a Linux computer cluster","datePublished":"2022-03-01T00:49:03+00:00","dateModified":"2022-03-01T00:49:47+00:00","mainEntityOfPage":{"@id":"https:\/\/www.insilico.jp\/blog\/2022\/03\/01\/nis-nfs-ssh_key-cluster\/"},"wordCount":1354,"image":{"@id":"https:\/\/www.insilico.jp\/blog\/2022\/03\/01\/nis-nfs-ssh_key-cluster\/#primaryimage"},"thumbnailUrl":"https:\/\/www.insilico.jp\/blog\/wp-content\/uploads\/2022\/02\/computer_cluster-3-1024x724.png","keywords":["NFS","NIS","SSH key","Ubuntu 20.04"],"articleSection":["Linux\u95a2\u9023"],"inLanguage":"ja"},{"@type":"WebPage","@id":"https:\/\/www.insilico.jp\/blog\/2022\/03\/01\/nis-nfs-ssh_key-cluster\/","url":"https:\/\/www.insilico.jp\/blog\/2022\/03\/01\/nis-nfs-ssh_key-cluster\/","name":"Configuring SSH key-based authentication, NIS and NFS in a Linux computer cluster - In Silico \u5275\u85ac","isPartOf":{"@id":"https:\/\/www.insilico.jp\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.insilico.jp\/blog\/2022\/03\/01\/nis-nfs-ssh_key-cluster\/#primaryimage"},"image":{"@id":"https:\/\/www.insilico.jp\/blog\/2022\/03\/01\/nis-nfs-ssh_key-cluster\/#primaryimage"},"thumbnailUrl":"https:\/\/www.insilico.jp\/blog\/wp-content\/uploads\/2022\/02\/computer_cluster-3-1024x724.png","datePublished":"2022-03-01T00:49:03+00:00","dateModified":"2022-03-01T00:49:47+00:00","author":{"@id":"https:\/\/www.insilico.jp\/blog\/#\/schema\/person\/f3e060be38907cda2a9c1cfcd17b1d00"},"breadcrumb":{"@id":"https:\/\/www.insilico.jp\/blog\/2022\/03\/01\/nis-nfs-ssh_key-cluster\/#breadcrumb"},"inLanguage":"ja","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.insilico.jp\/blog\/2022\/03\/01\/nis-nfs-ssh_key-cluster\/"]}]},{"@type":"ImageObject","inLanguage":"ja","@id":"https:\/\/www.insilico.jp\/blog\/2022\/03\/01\/nis-nfs-ssh_key-cluster\/#primaryimage","url":"https:\/\/www.insilico.jp\/blog\/wp-content\/uploads\/2022\/02\/computer_cluster-3.png","contentUrl":"https:\/\/www.insilico.jp\/blog\/wp-content\/uploads\/2022\/02\/computer_cluster-3.png","width":1123,"height":794},{"@type":"BreadcrumbList","@id":"https:\/\/www.insilico.jp\/blog\/2022\/03\/01\/nis-nfs-ssh_key-cluster\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"\u30db\u30fc\u30e0","item":"https:\/\/www.insilico.jp\/blog\/"},{"@type":"ListItem","position":2,"name":"Configuring SSH key-based authentication, NIS and NFS in a Linux computer cluster"}]},{"@type":"WebSite","@id":"https:\/\/www.insilico.jp\/blog\/#website","url":"https:\/\/www.insilico.jp\/blog\/","name":"In Silico \u5275\u85ac","description":"\u3053\u306e\u30d6\u30ed\u30b0\u30b5\u30a4\u30c8\u306f\u3001In silico\u5275\u85ac\u306b\u95a2\u9023\u3059\u308b\u7814\u7a76\u8ad6\u6587\u3084\u30bd\u30d5\u30c8\u30a6\u30a7\u30a2\u30fb\u30c4\u30fc\u30eb\u306e\u5229\u7528\u3084\u30d7\u30ed\u30b0\u30e9\u30df\u30f3\u30b0\u306a\u3069\u306b\u3064\u3044\u3066\u3054\u7d39\u4ecb\u3057\u3066\u3044\u307e\u3059\u3002","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.insilico.jp\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ja"},{"@type":"Person","@id":"https:\/\/www.insilico.jp\/blog\/#\/schema\/person\/f3e060be38907cda2a9c1cfcd17b1d00","name":"Enzo Kawasaki","image":{"@type":"ImageObject","inLanguage":"ja","@id":"https:\/\/secure.gravatar.com\/avatar\/74a51ec0e05cc3f7f23feff1be9436059572ce3e2e30570816149e2d4e6a91b4?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/74a51ec0e05cc3f7f23feff1be9436059572ce3e2e30570816149e2d4e6a91b4?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/74a51ec0e05cc3f7f23feff1be9436059572ce3e2e30570816149e2d4e6a91b4?s=96&d=mm&r=g","caption":"Enzo Kawasaki"},"url":"https:\/\/www.insilico.jp\/blog\/author\/kawasaki\/"}]}},"_links":{"self":[{"href":"https:\/\/www.insilico.jp\/blog\/wp-json\/wp\/v2\/posts\/1907","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.insilico.jp\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.insilico.jp\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.insilico.jp\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/www.insilico.jp\/blog\/wp-json\/wp\/v2\/comments?post=1907"}],"version-history":[{"count":35,"href":"https:\/\/www.insilico.jp\/blog\/wp-json\/wp\/v2\/posts\/1907\/revisions"}],"predecessor-version":[{"id":1978,"href":"https:\/\/www.insilico.jp\/blog\/wp-json\/wp\/v2\/posts\/1907\/revisions\/1978"}],"wp:attachment":[{"href":"https:\/\/www.insilico.jp\/blog\/wp-json\/wp\/v2\/media?parent=1907"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.insilico.jp\/blog\/wp-json\/wp\/v2\/categories?post=1907"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.insilico.jp\/blog\/wp-json\/wp\/v2\/tags?post=1907"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}