<html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;"><div></div><ul><li>The first step might be a well known (inside OpenStack) port for keystone and then register with IANA to avoid any conflicts. </li><li>Second, the service should have a ping-pong interface, with pong sending a version number (to make it easy for clients to make sure they can find the functionalities they are looking for)</li><li>Where it could get complicated is the dynamic port configuration - ie search & find an unused port and then to let other services know of the port number</li><li>As I was saying earlier, we might end up implementing some capabilities of Apache ZooKeeper - for example configuration, distributed coordination & service discovery</li><li>BTW, Keystone looks interesting, ... need to take a closer look</li></ul><div></div><div>Cheers</div><div><k/></div><div>P.S : If the service catalog becomes a central essential service, we might need to look at scalability and redundancy.</div>
<blockquote id="replyBlockquote" webmail="1" style="border-left: 2px solid blue; margin-left: 8px; padding-left: 8px; font-size:10pt; color:black; font-family:verdana;" mce_style="border-left: 2px solid blue; margin-left: 8px; padding-left: 8px; font-size:10pt; color:black; font-family:verdana;">
<div id="wmQuoteWrapper">
-------- Original Message --------<br>
Subject: Re: [Openstack] Default ports for services<br>
From: Ziad Sawalha <<a href="http://ziad.sawalha@rackspace.com">ziad.sawalha@rackspace.com</a>><br>
Date: Mon, June 27, 2011 7:20 am<br>
To: Thierry Carrez <<a href="mailto:thierry@openstack.org">thierry@openstack.org</a>>,<br>
"<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>" <<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>><br>
<br>
We have the service catalog functionality in Keystone which provides<br>
discovery.<br>
<br>
We still need to complete the user story of how a service registers<br>
itself; the functionality is available, but not fully documented as a<br>
story.<br>
<br>
The question of ports still remains, though. How do you find Keystone?<br>
Options:<br>
- Register a port as suggested earlier (that would be a port for the<br>
service catalog?)<br>
- DNS? SRV record?<br>
- convention: 80/8080 (and raise conflicts as an error?)<br>
<br>
<br>
We could also provide some form of proxy functionality if services are<br>
running on non-standard portsŠ<br>
<br>
<br>
<br>
<br>
On 6/27/11 3:01 AM, "Thierry Carrez" <<a href="mailto:thierry@openstack.org">thierry@openstack.org</a>> wrote:<br>
<br>
>Todd Willey wrote:<br>
>> I think people will probably deploy in such a way that clients talk to<br>
>> 80 or 443. But there are a number of ways to get to that outcome,<br>
>> including specifying it in the server configuration, or running behind<br>
>> load balancers or other front-end services. Running everything be<br>
>> default on different ports by default has little bearing on how it<br>
>> gets run in production.<br>
><br>
>Also running on *separate* ports has an added advantage in distro<br>
>packaging: you can apt-get install the different components and start<br>
>them up at install-time with default configs, without having to care for<br>
>them potentially interfering with each other in the (common) case of<br>
>all-in-ones.<br>
><br>
>If we switch to using 80/8080 by default everywhere, to workaround this<br>
>issue we'll have to package each component with a config that enables a<br>
>specific port. And then we have a different defaults (the "packaging"<br>
>default and the "what happens when I remove the port option" default),<br>
>which will be confusing... for little gain.<br>
><br>
>So I'm -1 on this :)<br>
><br>
>-- <br>
>Thierry Carrez (ttx)<br>
>Release Manager, OpenStack<br>
><br>
>_______________________________________________<br>
>Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>
>Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
>Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>
>More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br>
<br>
<br>
_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br>
</div>
</blockquote></span></body></html>