Dynamic DNS

From EGIWiki
Revision as of 08:37, 28 February 2017 by Viet (talk | contribs) (Used technologies)
Jump to: navigation, search
EGI-Engage project: Main page WP1(NA1) WP3(JRA1) WP5(SA1) PMB Deliverables and Milestones Quality Plan Risk Plan Data Plan
Roles and
responsibilities
WP2(NA2) WP4(JRA2) WP6(SA2) AMB Software and services Metrics Project Office Procedures



Objective

Supports for DNS names for VMs in EGI Federated cloud are recently required by many VOs. The aim of this task is to provide Dynamic DNS support for VMs in EGI Federated Clouds. Users can register their chosen meaningful and memorable DNS host names in given domains (e.g. my-server.vo-name.egi.eu) and assign to public IPs of their servers hosted in EGI Federated Cloud. By using Dynamic DNS, users can host services in EGI Federated Cloud with their meaningful server names, can freely move VMs from sites to sites without modifying server/client configurations (federated approach), can request valid server certificates in advance (critical for security)and many other advantages.


Participants

Developer

  • Viet Tran (IISAS) viet.tran _at_ savba.sk


Advisory board

  • Enol Fernández
  • Vincenzo Spinoso
  • Boris Parak
  • Jerome Pansanel

Requirements

  • Basic functionalities
    • Web-based GUI interfaces for registering DNS hostnames for EGI users
    • DNS server with Dynamic DNS support for forward DNS resolution
    • Command-line clients for assigning registered hostnames to IPs
  • Advanced functionalities
    • Using EGI Checkin services
    • Command-line client for registering DNS hostnames
  • Not compulsory but desired functionalities
    • Support for reverse DNS resolution

Used technologies

  • Backend: BIND9 DNS server with configuration for updating DNS names via RFC 2136
  • Frontend: nsupdate.info portal for registering and managing DNS names/domains
  • Clients: Wide support of common dynamic DNS clients like ddclient, inadyn, or just curl

Current status

  • A testing domain fedcloud.eu has been registered for testing and development (without touching production domains like egi.eu)
  • DNS servers are installed and configured for fedcloud.eu domain
  • Portal is installed on configured
  • Users can register themselves and log in portal, can register DNS names within fedcloud.eu domain and assign to VMs
  • Integrate to EGI CheckIn service

Ongoing work

  • Clean up codes
  • Justify setting and user interface
  • Defining policies
  • Preparation for alpha testing

Next steps

  • Support for command-line clients for registering domains
  • Beta testing
  • Transfer to egi.eu domain
  • Production

Long term work

  • Support for reverse DNS resolution