mirrors/nomulus
1
0
Fork 0
mirror of https://github.com/google/nomulus synced 2025-12-23 06:15:42 +00:00
Code Issues Releases Wiki Activity

Add instructions on how to set up the GCP proxy

Browse Source 
A step by step instruction is provided to set up the proxy. Also made some changes to the README file as both DNS and proxy are no longer "known issues"

A better approach to setting up the proxy manually is to codify the infrastructure with https://terraform.io. I will work on this next.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=189648593
This commit is contained in:
jianglai
2018-03-19 15:09:50 -07:00
parent f5cb227f0e
commit 70e9df7435
2 changed files with 610 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
README.md
View File

@@ -89,26 +89,26 @@ Nomulus has the following capabilities:
* **Administrative tool**: Performs the full range of administrative tasks
needed to manage a running registry system, including creating and
configuring new TLDs.
## Known issues
Registry operators interested in deploying Nomulus will likely require some
additional components that are not provided out of the box.
**Core dependencies**
* A DNS system. An interface for DNS operations is provided so you can write
an implementation for your chosen provider, along with a sample
* **DNS interface**: An interface for DNS operations is provided so you can
write an implementation for your chosen provider, along with a sample
implementation that uses [Google Cloud DNS](https://cloud.google.com/dns/).
If you are using Google Cloud DNS you may need to understand its
capabilities and provide your own
multi-[AS](https://en.wikipedia.org/wiki/Autonomous_system_\(Internet\))
solution.
* A proxy to forward traffic on EPP and WHOIS ports to App Engine via HTTPS,
since App Engine Standard only serves HTTP/S traffic. The proxy must support
IPv4 and IPv6 access to comply with ICANN's requirements for gTLDs.
* **GAE Proxy**: App Engine Standard only serves HTTP/S traffic. A proxy to
forward traffic on EPP and WHOIS ports to App Engine via HTTPS is provided.
Instructions on setting up the proxy on
[Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine/)
is [available](https://github.com/google/nomulus/blob/master/docs/proxy-setup.md).
Running the proxy on GKE supports IPv4 and IPv6 access, per ICANN's
requirements for gTLDs. The proxy can also run as a single jar file, or on
other Kubernetes providers, with modifications.
**Additional functionality**
## Additional components
Registry operators interested in deploying Nomulus will likely require some
additional components that are need to be configured separately.
* A way to invoice registrars for domain name registrations and accept
payments. Nomulus records the information required to generate invoices in