I'd prefer to keep it convenient to develop and demo on a single machine. I don't think there is any added inconvenience during deployment if the ports are not the standard http ports.
On Fri, Jun 24, 2011 at 12:15 PM, Jay Pipes <[email protected]> wrote: > Hi! > > As I stated on our Skype chat about this the other day, I think that > the default port for HTTP services should be 80, with 8080 used for > administrative endpoints. Unless there's a good reason to have a > specific port assigned to what is essentially just an HTTP service, I > don't think we should stray from the standard. > > That said, I recognize that Glance's API and registry servers are at > 9292 and 9191 respectively. I believe it was a mistake to do that, and > I would support switching those both back to 80. > > -jay > > On Wed, Jun 22, 2011 at 9:52 PM, Ziad Sawalha > <[email protected]> wrote: >> Where's the best place to keep track of default ports for services to avoid >> conflicts? A wiki page on wiki.openstack.org? >> We had a discussion while working on Keystone about default ports for >> OpenStack services (https://github.com/rackspace/keystone/issues/31). We >> want OpenStack to work 'out-of-the-box' without built-in port conflicts, so >> we should coordinate which ports new services start on. >> At a minimum, we need that for Keystone as it isn't discoverable. Other >> services can be discovered using the service catalog that Keystone returns >> as part of an auth request (Sample response below at end of email). >> Here's a list of ports we talked about on >> https://github.com/rackspace/keystone/issues/31 >> >> 80: Swift proxy server (swift/etc/proxy-server.conf-sample) >> 6000: Swift object server >> 6001: Swift container server >> 6002: Swift account server >> 6080: Nova VNC proxy >> 8001: Nova direct API >> 8080: Swift proxy server (swift/bin/swift-proxy-server) >> 3306: MySQL >> 5672: AMPQ (RabbitMQ) >> 9292: Glance API >> 9191: Glance Registry >> 5900...590?: qemu-system for VNC >> >> We've moved Keystone to 5000/5001 (for Service and Admin API, respectively). >> >> >> Sample Response with service catalog: >> >> { >> "auth":{ >> "token":{ >> "id":"asdasdasd-adsasdads-asdasdasd-adsadsasd", >> "expires":"2010-11-01T03:32:15-05:00" >> }, >> "serviceCatalog":{ >> "nova":[ >> { >> "region":"NorthAmerica", >> "publicURL":"https://service1-public:9000/v1/blah-blah";, >> "internalURL":"https://service1-internal:9001/v1/blah-blah"; >> }, >> { >> "region":"Europe", >> "publicURL":"https://service1-public-eu/v1/blah-blah";, >> "internalURL":"https://service1-internal-eu/v1/blah-blah"; >> } >> ], >> "swift":[ >> { >> "region":"regionOne", >> "publicURL":"https://service2-public-dat/v1/blah-blah"; >> } >> ] >> } >> } >> } >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~openstack >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp >> >> > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
