You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Henry Robinson (JIRA)" <ji...@apache.org> on 2010/03/13 02:15:27 UTC

[jira] Updated: (ZOOKEEPER-703) GSoC 2010: ZooKeeper DNS Server

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Henry Robinson updated ZOOKEEPER-703:
-------------------------------------

    Summary: GSoC 2010: ZooKeeper DNS Server  (was: ZooKeeper DNS Server)

> GSoC 2010: ZooKeeper DNS Server
> -------------------------------
>
>                 Key: ZOOKEEPER-703
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-703
>             Project: Zookeeper
>          Issue Type: Wish
>            Reporter: Henry Robinson
>
> ZooKeeper DNS Server
> Possible Mentor
> Henry Robinson (henry at apache dot org)
> Requirements
> Java or Python or C
> Description
> Although ZooKeeper is primarily used for co-ordination of distributed processes, its consistency semantics means that it's a good candidate for serving small (key,value) records as well. The Domain Name Service has similar requirements, raising the interesting question of whether ZooKeeper would be a capable DNS server for your local network. One intriguing possibility is having versioned DNS records, such that known-good configurations can be stored and rolled back to in the case of an issue. If this versioning primitive proves to be useful, it's easy to imagine other types of configuration that could be stored.
> This project would involve designing and building an RFC-1035 compliant DNS server and performing a detailed performance study against an already existant simple DNS server like tinydns.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.