essage-
>> From: Ziad Sawalha [mailto:ziad.sawa...@rackspace.com]
>> Sent: 23 August 2011 20:31
>> To: Ewan Mellor; Mark Nottingham;
>> Cc: openstack@lists.launchpad.net
>> Subject: Re: [Openstack] Default ports for services
>>
>> Admin and Service start on diff
quot; and "keystone-control
>ALL start"?
>
>Thanks,
>
>Ewan.
>
>> -Original Message-
>> From: Ziad Sawalha
>> [mailto:ziad.sawa...@rackspace.com<mailto:ziad.sawa...@rackspace.com>]
>> Sent: 23 August 2011 20:24
>> To: Ewan Mellor; Mark Nottin
gt;> -Original Message-
> >> From: Ziad Sawalha [mailto:ziad.sawa...@rackspace.com]
> >> Sent: 23 August 2011 20:24
> >> To: Ewan Mellor; Mark Nottingham;
> >> Cc: openstack@lists.launchpad.net
> >> Subject: Re: [Openstack] Default ports for servi
On Tue, 2011-08-23 at 14:53 +, Ziad Sawalha wrote:
> Keystone-control has been added to the bin folder to support the more
> OpenStack-like commands, but is not yet working.
It isn't yet working? I'm using it for the keystone integration
functional tests I'm writing for glance, and it seems
mailto:ziad.sawa...@rackspace.com]
>> Sent: 23 August 2011 20:24
>> To: Ewan Mellor; Mark Nottingham;
>> Cc: openstack@lists.launchpad.net
>> Subject: Re: [Openstack] Default ports for services
>>
>> Yes, we'll probably be getting rid of some of those.
t: 23 August 2011 20:24
> To: Ewan Mellor; Mark Nottingham;
> Cc: openstack@lists.launchpad.net
> Subject: Re: [Openstack] Default ports for services
>
> Yes, we'll probably be getting rid of some of those. They've been
> useful
> for testing (you can chose one, the oth
20:31
> To: Ewan Mellor; Mark Nottingham;
> Cc: openstack@lists.launchpad.net
> Subject: Re: [Openstack] Default ports for services
>
> Admin and Service start on different ports (and potentially different
> networks). That's a deployment option we are trying to support from t
need two? (Or maybe just one with a flag that said
>"enable admin functions")
>
>Ewan.
>
>> -Original Message-
>> From: Ziad Sawalha [mailto:ziad.sawa...@rackspace.com]
>> Sent: 23 August 2011 19:37
>> To: Ewan Mellor; Mark Nottingham;
ot;enable admin functions")
Ewan.
> -Original Message-
> From: Ziad Sawalha [mailto:ziad.sawa...@rackspace.com]
> Sent: 23 August 2011 19:37
> To: Ewan Mellor; Mark Nottingham;
> Cc: openstack@lists.launchpad.net
> Subject: Re: [Openstack] Default ports for services
&
r=citrix@lists.launchpad.net
>> [mailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.net]
>> On Behalf Of Ziad Sawalha
>> Sent: 16 August 2011 22:17
>> To: Mark Nottingham;
>> Cc: openstack@lists.launchpad.net
>> Subject: Re: [Openstack] Default
or=citrix@lists.launchpad.net]
> On Behalf Of Ziad Sawalha
> Sent: 16 August 2011 22:17
> To: Mark Nottingham;
> Cc: openstack@lists.launchpad.net
> Subject: Re: [Openstack] Default ports for services
>
> Keystone has been assigned TCP port 35357 by IANA.
>
> We'll mak
gt;>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
>>
>> Original Message
:thie...@openstack.org>>,
"openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net>"
mailto:openstack@lists.launchpad.net>>
Subject: RE: [Openstack] Default ports for services
* The first step might be a well known (inside OpenStack) port for keystone
and then regis
uted coordination & service discoveryBTW, Keystone looks interesting, ... need to take a closer lookCheersP.S : If the service catalog becomes a central essential service, we might need to look at scalability and redundancy.
Original Message
Subject: Re: [Openstack] Default p
We have the service catalog functionality in Keystone which provides
discovery.
We still need to complete the user story of how a service registers
itself; the functionality is available, but not fully documented as a
story.
The question of ports still remains, though. How do you find Keystone?
O
The effort Jay (and others) are doing on standardizing across services
could also be helpful here; having a -p --ports command-line and config
setting that works with all services would make it easier to stand up a
set of services on non-conflicting ports.
On 6/25/11 9:11 PM, "Todd Willey" wrote:
Todd Willey wrote:
> I think people will probably deploy in such a way that clients talk to
> 80 or 443. But there are a number of ways to get to that outcome,
> including specifying it in the server configuration, or running behind
> load balancers or other front-end services. Running everything
Right, but it's not all about deployment, because representations within
the API have absolute hrefs embedded within them.
On 6/26/11 12:11 PM, "Todd Willey" wrote:
>I think people will probably deploy in such a way that clients talk to
>80 or 443. But there are a number of ways to get to that
I think people will probably deploy in such a way that clients talk to
80 or 443. But there are a number of ways to get to that outcome,
including specifying it in the server configuration, or running behind
load balancers or other front-end services. Running everything be
default on different po
So, I gather you're agreeing with me? :)
-jay
On Sun, Jun 26, 2011 at 9:50 AM, Bryan Taylor wrote:
> If we use something other than 80 for http and/or 443 for https, then
> clients will have to know magic numbers for the port and firewall
> obstacles will annoy them. I don't see HTTP as somethin
If we use something other than 80 for http and/or 443 for https, then
clients will have to know magic numbers for the port and firewall
obstacles will annoy them. I don't see HTTP as something we just happen to
have chosen. We should prefer convention over configuration, and embrace
the conventions
On Sun, Jun 26, 2011 at 3:15 AM, Soren Hansen wrote:
> 2011/6/25 Jay Pipes :
>> Can you explain why having the *default* port be 80/8080 for HTTP
>> services would hinder that? Unless I'm mistaken, spinning up servers
>> on different ports is as simple as specifying a set of test config
>> files t
2011/6/25 Jay Pipes :
> Can you explain why having the *default* port be 80/8080 for HTTP
> services would hinder that? Unless I'm mistaken, spinning up servers
> on different ports is as simple as specifying a set of test config
> files that have ports set for an all-on-one-machine setup?
I've he
On Sat, Jun 25, 2011 at 11:47 AM, Jay Pipes wrote:
> On Fri, Jun 24, 2011 at 10:10 AM, Todd Willey wrote:
>> 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 por
On Fri, Jun 24, 2011 at 10:10 AM, Todd Willey wrote:
> 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.
Can you explain why having the *default* port be 80/
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 wrote:
> Hi!
>
> As I stated on our Skype chat about this the other
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
Original Message
Subject: Re: [Openstack] Default ports for services
From: Mark Nottingham <m...@mnot.net>
Date: Thu, June 23, 2011 10:46 pm
To: <ksan...@doubleclix.net> <ksan...@doubleclix.net>
Cc: "Ziad Sawalha" <ziad.sawa...@rackspace.com>,
"op
port numbers, I assume they will manifest as universal constants and/or a configuration file in a universally (or intergalactically ;o)) known place.Cheers
Original Message
Subject: [Openstack] Default ports for services
From: Ziad Sawalha <ziad.sawa...@rackspace.com>
Dat
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
30 matches
Mail list logo
