Difference between revisions of "Dynamic DNS"

From EGIWiki
Jump to: navigation, search
Line 1: Line 1:
 
{{Template:EGI-Engage menubar}} {{TOC_right}}  
 
{{Template:EGI-Engage menubar}} {{TOC_right}}  
  
= Objective =
+
= 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.
+
DNS names for VMs in EGI Federated cloud are recently required by many VOs [https://docs.google.com/spreadsheets/d/1pKBNuHV9FgQ-k6cIQ_2Eez_y6KZsiSVoLKW953QVkyo/edit#gid=0 requirements]  , however, the support for  
  
 +
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 =
+
<br>
  
Developer
+
= Participants  =
 +
 
 +
Developer  
  
 
*Viet Tran (IISAS) viet.tran _at_ savba.sk
 
*Viet Tran (IISAS) viet.tran _at_ savba.sk
  
 
+
<br> Advisory board  
Advisory board
 
  
 
*Enol Fernández
 
*Enol Fernández
Line 25: Line 27:
 
*Jerome Pansanel
 
*Jerome Pansanel
  
= Requirements =
+
= Requirements =
  
* Basic functionalities
+
*Basic functionalities  
** Web-based GUI interfaces for registering DNS hostnames for EGI users (done)
+
**Web-based GUI interfaces for registering DNS hostnames for EGI users (done)  
** DNS server with Dynamic DNS support for forward DNS resolution (done)
+
**DNS server with Dynamic DNS support for forward DNS resolution (done)  
** Command-line clients for assigning registered hostnames to IPs (done)
+
**Command-line clients for assigning registered hostnames to IPs (done)
  
* Advanced functionalities
+
*Advanced functionalities  
** Using EGI Checkin services (authentication done, authorization ongoing)
+
**Using EGI Checkin services (authentication done, authorization ongoing)  
** Command-line client for registering DNS hostnames (next period)
+
**Command-line client for registering DNS hostnames (next period)
  
* Not compulsory but desired functionalities
+
*Not compulsory but desired functionalities  
** Support for reverse DNS resolution (long term)
+
**Support for reverse DNS resolution (long term)
  
= Used technologies =
+
= Used technologies =
  
* Backend: BIND9 DNS server with configuration for updating DNS names via RFC 2136
+
*Backend: BIND9 DNS server with configuration for updating DNS names via RFC 2136  
* Frontend: nsupdate.info portal for registering and managing DNS names/domains
+
*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
+
*Clients: Wide support of common dynamic DNS clients like ddclient, inadyn, or just curl
  
= Current status =
+
= Current status =
  
* A testing domain fedcloud.eu has been registered for testing and development (without touching production domains like egi.eu)
+
*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
+
*DNS servers are installed and configured for fedcloud.eu domain  
* Portal is installed on configured
+
*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
+
*Users can register themselves and log in portal, can register DNS names within fedcloud.eu domain and assign to VMs  
* Authentication via EGI CheckIn service is supported
+
*Authentication via EGI CheckIn service is supported
  
= Ongoing work =
+
= Ongoing work =
  
* Cleanning codes
+
*Cleanning codes  
* Tunning setting and user interface
+
*Tunning setting and user interface  
* Defining policies, implementing authorization accordingly
+
*Defining policies, implementing authorization accordingly  
* Preparation for alpha testing
+
*Preparation for alpha testing
  
= Next steps =
+
= Next steps =
  
* Support for command-line clients for registering domains
+
*Support for command-line clients for registering domains  
* Beta testing
+
*Beta testing  
* Transfer to egi.eu domain
+
*Transfer to egi.eu domain  
* Production
+
*Production
  
= Long term work =
+
= Long term work =
  
* Support for reverse DNS resolution (significant development required)
+
*Support for reverse DNS resolution (significant development required)

Revision as of 09:12, 2 March 2017

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

DNS names for VMs in EGI Federated cloud are recently required by many VOs requirements  , however, the support for

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
  • Peter Solagna
  • Vincenzo Spinoso
  • Boris Parak
  • Jerome Pansanel

Requirements

  • Basic functionalities
    • Web-based GUI interfaces for registering DNS hostnames for EGI users (done)
    • DNS server with Dynamic DNS support for forward DNS resolution (done)
    • Command-line clients for assigning registered hostnames to IPs (done)
  • Advanced functionalities
    • Using EGI Checkin services (authentication done, authorization ongoing)
    • Command-line client for registering DNS hostnames (next period)
  • Not compulsory but desired functionalities
    • Support for reverse DNS resolution (long term)

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
  • Authentication via EGI CheckIn service is supported

Ongoing work

  • Cleanning codes
  • Tunning setting and user interface
  • Defining policies, implementing authorization accordingly
  • 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 (significant development required)