esi-leap running on non tls endpoint

[naved001]

|                  |                         |                                                                                     |
| esi-leap         | lease                   | regionOne                                                                           |
|                  |                         |   public: http://129.10.5.142:7777/                                                  |

This is from the output of opentack catalog list. It's also specifically running on one node. This may be a configuration issue.

[tzumainn]

@naved001 so I'm having trouble generating a certificate because esi-leap only runs on a single controller, so we specify that controller's IP in the OpenStack catalog, and letsencrypt can't generate certificates for an IP. Any thoughts on how to handle this? Can we create a DNS entry and point something like esi-leap.massopen.cloud at the IP?

[naved001]

@tzumainn done

➜  ~ dig +short esi-leap.massopen.cloud
129.10.5.142