Naming conventions

From Grid5000
Jump to: navigation, search

Refer to DNS server section to see how to configure your DNS server.

Warning.png Warning

This naming machines convention is deprecated. Now refer to Naming machines.

Contents

Convention

In this document,

  • site: will refer the name of a site (ex: lyon, grenoble, ...)
  • interface: will be a letter begining from a
  • numero: will be a number begining from 1.

In any case, if several machines have the same role, the standard name must be affected to the main one and the others get an indexed name. For instance for the machines providing the NTP service:

  1. ntp = ntp1
  2. ntp2
  3. ntp3
  4. ...

The following part presents the internal and external naming for Grid'5000 machines. Please refer to the Security policy for discussion about Grid'5000 internal and external network.

Grid'5000 Naming

Grid'5000 machines all belong to the grid5000.fr domain. However, only the machines that have to be accessed from the internet have their names publicly defined in the internet DNS. The cluster nodes for instance may just have a hostname defined in a private grid5000.fr domain.

This means there are 2 grid5000.fr domains:

  • the public one, maintained at Idris (Orsay), that is propagated over the internet DNS;
  • the internal one, maintained locally for each site subdomain and at Orsay for the main branch, that is bounded to the Grid'5000 network.

Internal Naming

Local domain name servers are running inside Grid'5000, to provide names to the Grid'5000 nodes. These DNS are not connected to the internet public DNS. These machines names are however replicated on every Grid'5000 sites, so that they are known on any machine of the grid5000.fr network. The main branch is maintained at Orsay.

User frontends

Role

Hostname

login frontend (main SSH server) and possibly compilation frontale.site.grid5000.fr (may be aliased to clustername.grid5000.fr)
job submission (main OAR client) oar.site.grid5000.fr
home directory synchronisation (main NFS client) sync.site.grid5000.fr

Note: in general, it is recommended to reserve and use a compute node to perform compilations.

Example:

frontale.toulouse.grid5000.fr

Nodes

Mandatory in any case:

  • node-number.site.grid5000.fr

And in case several network interfaces are available, one may add:

  • node-number-interface.site.grid5000.fr

Example:

node-1-b.lyon.grid5000.fr

Services

Service Hostname
DNS dns.site.grid5000.fr
Ganglia ganglia.site.grid5000.fr
LDAP ldap.site.grid5000.fr
MySQL mysql.site.grid5000.fr
Nagios (obsolete ?) nagios.site.grid5000.fr
NFS nfs.site.grid5000.fr
NTP ntp.site.grid5000.fr
OAR server (Almighty) oar-server.site.grid5000.fr
Web proxy proxy.site.grid5000.fr
Web server www.site.grid5000.fr
Kadeploy server kadeploy-server.site.grid5000.fr
Virtual IP addresses routable between sites virtual.site.grid5000.fr

Example:

ldap.sophia.grid5000.fr

External Naming

From the internet point of view the visible grid5000.fr machines are few:

  • Grid'5000 local external access for each site: acces.site.grid5000.fr which may be aliased to clustername.grid5000.fr
  • Grid'5000 common public web site: www.grid5000.fr
  • Grid'5000 common technical helpdesk: helpdesk.grid5000.fr which include a proxy toward internal helpdesks and monitoring web servers (monika, gantt...)
  • Grid'5000 common mailing list sympa manager: lists.grid5000.fr
  • Grid'5000 common chat server: jabber.grid5000.fr and conference.jabber.grid5000.fr

Example:

acces.orsay.grid5000.fr -> gdx.grid5000.fr -> 192.134.150.242
Personal tools
Namespaces

Variants
Actions
Public Portal
Users Portal
Admin portal
Wiki special pages
Toolbox