Are you intending to use 35357 for the admin API or the service API? And what port will be the default for the other one?
Thanks, Ewan. > -----Original Message----- > From: [email protected] > [mailto:[email protected]] > On Behalf Of Ziad Sawalha > Sent: 16 August 2011 22:17 > To: Mark Nottingham; <[email protected]> > Cc: [email protected] > Subject: Re: [Openstack] Default ports for services > > Keystone has been assigned TCP port 35357 by IANA. > > We'll make that the default port. > > Thanks, > Z > > > > On 6/24/11 12:46 AM, "Mark Nottingham" <[email protected]> wrote: > > >On 24/06/2011, at 3:31 PM, <[email protected]> > ><[email protected]> wrote: > > > >> Couple of quick points: > >> > >> a) Once the ports are fixed, we should register them with IANA as > well > >>known ports, which is the right > >>place.[http://www.iana.org/assignments/port-numbers] > > > >That would be a friendly thing to do. See below for potential > conflicts. > > > >> b) I was going to suggest something like a ZooKeeper, may be the > >>service catalog serves that purpose. > >> c) Also, on the port numbers, I assume they will manifest as > universal > >>constants and/or a configuration file in a universally (or > >>intergalactically ;o)) known place. > >> Cheers > >> <k/> > >> -------- Original Message -------- > >> Subject: [Openstack] Default ports for services > >> From: Ziad Sawalha <[email protected]> > >> Date: Wed, June 22, 2011 9:52 pm > >> To: "[email protected]" <[email protected]> > >> > >> 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) > > > >Already taken by HTTP, of course. If it's just an HTTP API, that's > fine. > > > >> 6000: Swift object server > >> 6001: Swift container server > >> 6002: Swift account server > > > >These are already registered for X-windows. > > > >> 6080: Nova VNC proxy > > > >free > > > >> 8001: Nova direct API > > > >taken by vcom-tunnel > > > >> 8080: Swift proxy server (swift/bin/swift-proxy-server) > > > >already HTTP alternate. Again, if it's an HTTP server (NOT http > proxy), > >that's OK. > > > >> 3306: MySQL > > > >already registered to mysql > > > >> 5672: AMPQ (RabbitMQ) > > > >already AMPQ > > > >> 9292: Glance API > > > >ArmTech Daemon (whatever that is) > > > >> 9191: Glance Registry > > > >Sun AppSvr JPDA > > > >> 5900...590?: qemu-system for VNC > > > >5901-5909 are Unassigned, 5900 is already remote framebuffer. > > > > > >> We've moved Keystone to 5000/5001 (for Service and Admin API, > >>respectively). > > > >commplex-main and commplex-link, 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 > > > >-- > >Mark Nottingham http://www.mnot.net/ > > > > > > > > This email may include confidential information. If you received it in > error, please delete it. > > > _______________________________________________ > 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
