Re: [openstack-dev] [nova] [placement] Which service is using port 8778?
On Tue, Jan 10, 2017 at 6:00 AM, Andy McCrae wrote: > Sorry to resurrect a few weeks old thread, but I had a few questions. > >> >> Yes, we should stop with the magic ports. Part of the reason of >> switching over to apache was to alleviate all of that. >> >> -Sean > > > Is this for devstack specifically? > I can see the motivation for Devstack, since it reduces the concern for > managing port allocations. > > Is the idea that we move away from ports and everything is on 80 with a > VHost to differentiate between services/endpoints? > > It seems to me that it would still be good to have a "designated" (and > unique - or as unique as possible at least within OpenStack) port for > services. We may not have all services on the same hosts, for example, using > a single VIP for load balancing. The issue then is that it becomes hard to > differentiate the LB pool based on the request. > I.e. How would i differentiate between Horizon requests and requests for any > other service on port 80, the VIP is the same, but the backends may be > completely different (so all requests aren't handled by the same Apache > server). Right, it causes conflicts when running architectures with HAproxy & API co-located. In the case of HAproxy, you might need to run ACLs, but it sounds adding a layer of complexity in the current deployments that might not exist in some cases yet. In TripleO, we decided to pick a port (8778) and deploy Placement API on this port, so it's consistent with existing services already deployed. Regarding Sean's comment about switching to Apache, I agree it simplifies a lot of things but I don't remember we decided to pick Apache because of the magic port thing. Though I remember because it was also for the SSL configuration that would be standard across all services. Any feedback at how our operators do here would be very welcome (adding operators mailing-list), so we would make sure we're taking the more realistic approach here. So the question would it be: When deploying OpenStack APIs under WSGI, do you pick magic port (ex: 8774 for Nova Compute API) or do you use 80/443 + vhost path? Thanks, > Assuming, in that case, having a designated port is the only way (and if it > isn't I'd love to discuss alternate, and simpler, methods of achieving this) > it then seems that assigning a dedicated port for services in Devstack would > make sense - it would ensure that there is no overlap, and in a way the > error received when the ports overlapped is a genuine issue that would need > to be addressed. Although if that is the case, perhaps there is a better way > to manage that. > > Essentially it seems better to handle port conflicts (within the OpenStack > ecosystem, at least) at source rather than pass that on to the deployer to > randomly pick ports and avoid conflicts. > > Andy > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Emilien Macchi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] [placement] Which service is using port 8778?
Sorry to resurrect a few weeks old thread, but I had a few questions. > Yes, we should stop with the magic ports. Part of the reason of > switching over to apache was to alleviate all of that. > > -Sean > Is this for devstack specifically? I can see the motivation for Devstack, since it reduces the concern for managing port allocations. Is the idea that we move away from ports and everything is on 80 with a VHost to differentiate between services/endpoints? It seems to me that it would still be good to have a "designated" (and unique - or as unique as possible at least within OpenStack) port for services. We may not have all services on the same hosts, for example, using a single VIP for load balancing. The issue then is that it becomes hard to differentiate the LB pool based on the request. I.e. How would i differentiate between Horizon requests and requests for any other service on port 80, the VIP is the same, but the backends may be completely different (so all requests aren't handled by the same Apache server). Assuming, in that case, having a designated port is the only way (and if it isn't I'd love to discuss alternate, and simpler, methods of achieving this) it then seems that assigning a dedicated port for services in Devstack would make sense - it would ensure that there is no overlap, and in a way the error received when the ports overlapped is a genuine issue that would need to be addressed. Although if that is the case, perhaps there is a better way to manage that. Essentially it seems better to handle port conflicts (within the OpenStack ecosystem, at least) at source rather than pass that on to the deployer to randomly pick ports and avoid conflicts. Andy __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] [placement] Which service is using port 8778?
Le 20/12/2016 14:30, Jay Pipes a écrit : > On 12/20/2016 08:03 AM, Sean Dague wrote: >> On 12/20/2016 07:53 AM, Sylvain Bauza wrote: >>> Le 20/12/2016 10:26, Sylvain Bauza a écrit : Le 20/12/2016 10:20, Chris Dent a écrit : > On Tue, 20 Dec 2016, Sylvain Bauza wrote: > >> Before moving forward and picking yet another port that could trample >> another service, I'd rather prefer first that Senlin jobs would >> temporarely disable the placement-* services so that the gate >> would be >> happy, while in the same time we try to identify a free port >> number that >> the placement API can safely bind. > > Another option here may be to not have the placement api bind to two > ports. The current set up binds 8778 with the API at /, but what's > registered in the service catalog is port 80 with the API at > /placement. > > So perhaps only use the http://1.2.3.4/placement and disable the > virtualhost that listens on 8778? > > I'd experiment with this myself but I'm going to be away from a > compute all day. If people think it is a good idea but nobody has a > chance to do it today I'll look into it tomorrow. > Oh good catch. Since we register the service catalog with port 80, then there is no reason to consume an application port. Chris, don't worry, I'll play with that today. >>> >>> So, after some investigation, I totally understand why we're using >>> virtualhosts for running the WSGI apps corresponding to each service, >>> since we want to keep the service catalog entries unchanged if the >>> operator wants to move from eventlet to mod_wsgi. >>> >>> Given that devstack was deploying a service catalog entry pointing to >>> HTTP port, should we just assume to drop the use of port 8778 ? >>> I'm a bit afraid of any possible impact it could have for operators >>> using the placement API with the virtualhost support which also provide >>> a WSGI daemon mode compared to the embedded mode that is executing calls >>> to :80/placement... >>> >>> Thoughts ? I mean, I can do the cut and drop that, but that will >>> certainly have impact for other deployers that were reproducing the >>> devstack install, like for TripleO : >>> https://review.openstack.org/#/c/406300/13/manifests/wsgi/apache_placement.pp >>> >> >> Yes, we should stop with the magic ports. Part of the reason of >> switching over to apache was to alleviate all of that. > > +100 > > -jay > Change is up, comments welcome : https://review.openstack.org/#/c/413118/ -Sylvain > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] [placement] Which service is using port 8778?
On 12/20/2016 08:03 AM, Sean Dague wrote: On 12/20/2016 07:53 AM, Sylvain Bauza wrote: Le 20/12/2016 10:26, Sylvain Bauza a écrit : Le 20/12/2016 10:20, Chris Dent a écrit : On Tue, 20 Dec 2016, Sylvain Bauza wrote: Before moving forward and picking yet another port that could trample another service, I'd rather prefer first that Senlin jobs would temporarely disable the placement-* services so that the gate would be happy, while in the same time we try to identify a free port number that the placement API can safely bind. Another option here may be to not have the placement api bind to two ports. The current set up binds 8778 with the API at /, but what's registered in the service catalog is port 80 with the API at /placement. So perhaps only use the http://1.2.3.4/placement and disable the virtualhost that listens on 8778? I'd experiment with this myself but I'm going to be away from a compute all day. If people think it is a good idea but nobody has a chance to do it today I'll look into it tomorrow. Oh good catch. Since we register the service catalog with port 80, then there is no reason to consume an application port. Chris, don't worry, I'll play with that today. So, after some investigation, I totally understand why we're using virtualhosts for running the WSGI apps corresponding to each service, since we want to keep the service catalog entries unchanged if the operator wants to move from eventlet to mod_wsgi. Given that devstack was deploying a service catalog entry pointing to HTTP port, should we just assume to drop the use of port 8778 ? I'm a bit afraid of any possible impact it could have for operators using the placement API with the virtualhost support which also provide a WSGI daemon mode compared to the embedded mode that is executing calls to :80/placement... Thoughts ? I mean, I can do the cut and drop that, but that will certainly have impact for other deployers that were reproducing the devstack install, like for TripleO : https://review.openstack.org/#/c/406300/13/manifests/wsgi/apache_placement.pp Yes, we should stop with the magic ports. Part of the reason of switching over to apache was to alleviate all of that. +100 -jay __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] [placement] Which service is using port 8778?
On 12/20/2016 07:53 AM, Sylvain Bauza wrote: > > > Le 20/12/2016 10:26, Sylvain Bauza a écrit : >> >> >> Le 20/12/2016 10:20, Chris Dent a écrit : >>> On Tue, 20 Dec 2016, Sylvain Bauza wrote: >>> Before moving forward and picking yet another port that could trample another service, I'd rather prefer first that Senlin jobs would temporarely disable the placement-* services so that the gate would be happy, while in the same time we try to identify a free port number that the placement API can safely bind. >>> >>> Another option here may be to not have the placement api bind to two >>> ports. The current set up binds 8778 with the API at /, but what's >>> registered in the service catalog is port 80 with the API at >>> /placement. >>> >>> So perhaps only use the http://1.2.3.4/placement and disable the >>> virtualhost that listens on 8778? >>> >>> I'd experiment with this myself but I'm going to be away from a >>> compute all day. If people think it is a good idea but nobody has a >>> chance to do it today I'll look into it tomorrow. >>> >> >> Oh good catch. Since we register the service catalog with port 80, then >> there is no reason to consume an application port. >> Chris, don't worry, I'll play with that today. >> > > So, after some investigation, I totally understand why we're using > virtualhosts for running the WSGI apps corresponding to each service, > since we want to keep the service catalog entries unchanged if the > operator wants to move from eventlet to mod_wsgi. > > Given that devstack was deploying a service catalog entry pointing to > HTTP port, should we just assume to drop the use of port 8778 ? > I'm a bit afraid of any possible impact it could have for operators > using the placement API with the virtualhost support which also provide > a WSGI daemon mode compared to the embedded mode that is executing calls > to :80/placement... > > Thoughts ? I mean, I can do the cut and drop that, but that will > certainly have impact for other deployers that were reproducing the > devstack install, like for TripleO : > https://review.openstack.org/#/c/406300/13/manifests/wsgi/apache_placement.pp Yes, we should stop with the magic ports. Part of the reason of switching over to apache was to alleviate all of that. -Sean -- Sean Dague http://dague.net __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] [placement] Which service is using port 8778?
Le 20/12/2016 10:26, Sylvain Bauza a écrit : > > > Le 20/12/2016 10:20, Chris Dent a écrit : >> On Tue, 20 Dec 2016, Sylvain Bauza wrote: >> >>> Before moving forward and picking yet another port that could trample >>> another service, I'd rather prefer first that Senlin jobs would >>> temporarely disable the placement-* services so that the gate would be >>> happy, while in the same time we try to identify a free port number that >>> the placement API can safely bind. >> >> Another option here may be to not have the placement api bind to two >> ports. The current set up binds 8778 with the API at /, but what's >> registered in the service catalog is port 80 with the API at >> /placement. >> >> So perhaps only use the http://1.2.3.4/placement and disable the >> virtualhost that listens on 8778? >> >> I'd experiment with this myself but I'm going to be away from a >> compute all day. If people think it is a good idea but nobody has a >> chance to do it today I'll look into it tomorrow. >> > > Oh good catch. Since we register the service catalog with port 80, then > there is no reason to consume an application port. > Chris, don't worry, I'll play with that today. > So, after some investigation, I totally understand why we're using virtualhosts for running the WSGI apps corresponding to each service, since we want to keep the service catalog entries unchanged if the operator wants to move from eventlet to mod_wsgi. Given that devstack was deploying a service catalog entry pointing to HTTP port, should we just assume to drop the use of port 8778 ? I'm a bit afraid of any possible impact it could have for operators using the placement API with the virtualhost support which also provide a WSGI daemon mode compared to the embedded mode that is executing calls to :80/placement... Thoughts ? I mean, I can do the cut and drop that, but that will certainly have impact for other deployers that were reproducing the devstack install, like for TripleO : https://review.openstack.org/#/c/406300/13/manifests/wsgi/apache_placement.pp -Sylvain > -Sylvain > > >> >> >> __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] [placement] Which service is using port 8778?
Le 20/12/2016 10:20, Chris Dent a écrit : > On Tue, 20 Dec 2016, Sylvain Bauza wrote: > >> Before moving forward and picking yet another port that could trample >> another service, I'd rather prefer first that Senlin jobs would >> temporarely disable the placement-* services so that the gate would be >> happy, while in the same time we try to identify a free port number that >> the placement API can safely bind. > > Another option here may be to not have the placement api bind to two > ports. The current set up binds 8778 with the API at /, but what's > registered in the service catalog is port 80 with the API at > /placement. > > So perhaps only use the http://1.2.3.4/placement and disable the > virtualhost that listens on 8778? > > I'd experiment with this myself but I'm going to be away from a > compute all day. If people think it is a good idea but nobody has a > chance to do it today I'll look into it tomorrow. > Oh good catch. Since we register the service catalog with port 80, then there is no reason to consume an application port. Chris, don't worry, I'll play with that today. -Sylvain > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] [placement] Which service is using port 8778?
On Tue, 20 Dec 2016, Sylvain Bauza wrote: Before moving forward and picking yet another port that could trample another service, I'd rather prefer first that Senlin jobs would temporarely disable the placement-* services so that the gate would be happy, while in the same time we try to identify a free port number that the placement API can safely bind. Another option here may be to not have the placement api bind to two ports. The current set up binds 8778 with the API at /, but what's registered in the service catalog is port 80 with the API at /placement. So perhaps only use the http://1.2.3.4/placement and disable the virtualhost that listens on 8778? I'd experiment with this myself but I'm going to be away from a compute all day. If people think it is a good idea but nobody has a chance to do it today I'll look into it tomorrow. -- Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/ freenode: cdent tw: @anticdent__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] [placement] Which service is using port 8778?
Le 20/12/2016 09:29, Sylvain Bauza a écrit : > > > Le 20/12/2016 09:12, Sylvain Bauza a écrit : >> >> >> Le 20/12/2016 07:31, Ghanshyam Mann a écrit : >>> Changing placement API port to 8780 [1], hope this is not being used by any >>> services. >>> >>> But I am not sure how to check all used port currently as wiki does not >>> seems to have all. >>> >>> .. [1] https://review.openstack.org/#/c/412770/ >>> >> >> >> FWIW, we recently merged a devstack-gate change yesterday that now runs >> the placement service by default, which is why it's breaking Senlin gate >> now. >> https://review.openstack.org/#/c/409871/ >> >> We also have a change up for modifying stackrc to start kicking the >> placement service by default too https://review.openstack.org/#/c/412537/ >> >> Before moving forward and picking yet another port that could trample >> another service, I'd rather prefer first that Senlin jobs would >> temporarely disable the placement-* services so that the gate would be >> happy, while in the same time we try to identify a free port number that >> the placement API can safely bind. >> > > Yeah confirmed. > > A working job doesn't show the placement-api service [a] to be run while > a failing one does [b] > > I'm just writing a change against [c] to temporarely disable the > placement-api service. That will need to be reverted very soon since we > want to have the placement API mandatory for Ocata anyway but that will > help your gate while we identify a correct port number. > > > [a] > http://logs.openstack.org/31/412331/1/check/gate-senlin-dsvm-tempest-api/b1dfbf9/logs/localrc.txt.gz > > [b] > http://logs.openstack.org/43/412843/1/check/gate-senlin-dsvm-tempest-api/cff7c55/logs/localrc.txt.gz > > [c] > https://github.com/openstack-infra/project-config/blob/d86338e968b84d119a59a6873b1d9c7ea17c37a8/jenkins/jobs/senlin.yaml > Okay, so surprinsingly, I just noticed that Senlin was not correctly declaring the services to start with their d-g jobs. Since it was using ENABLED_SERVICES and not OVERRIDE_ENABLED_SERVICES, it was defaulting the services to start by the default d-g ones, including then Nova and now the placement-api. https://review.openstack.org/#/c/412915/ should fix that. https://review.openstack.org/#/c/412930/ is a canary patch for showing whether the gate is fixed by the above change. -Sylvain > > -Sylvain > >> -Sylvain >> >> >>> -gmann >>> >>> -Original Message- From: Ghanshyam Mann [mailto:ghanshyam.m...@nectechnologies.in] Sent: 20 December 2016 15:17 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] Which service is using port 8778? Yes, it seems placement API using it [1] > 1. Recent changes to tempest is breaking our plugin. This is being >fixed. Tempest patch should fix issue but port issue blocking that[2] For port think, I think we can change the placement API port to something else. I will propose and we can get unused port there. But OpenStack port used by services are maintained here[3], may be it will be good for each project to add their port in this list. .. [1] - https://github.com/openstack- dev/devstack/blob/master/lib/placement#L50 ..[2] https://review.openstack.org/#/c/412658/ ..[3] http://docs.openstack.org/newton/config-reference/firewalls-default- ports.html -gmann > -Original Message- > From: Qiming Teng [mailto:teng...@linux.vnet.ibm.com] > Sent: 20 December 2016 14:45 > To: openstack-dev@lists.openstack.org > Subject: [openstack-dev] Which service is using port 8778? > > Hi, all, > > Starting yesterday, Senlin's gate jobs kept failing due to two reasons: > > 1. Recent changes to tempest is breaking our plugin. This is being >fixed. > > 2. Senlin API cannot bind it to port 8778 now. > > So, we are wondering which service else is using port 8778? > > Thanks in advance for any hints. > > Regards, > Qiming > > > __ > > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev- > requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev- requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> __ >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>> ht
Re: [openstack-dev] [nova] [placement] Which service is using port 8778?
Yea, that is also options to disable the placement api in senlin setup. But for long term we should have different ports for each service and should be maintained here - http://docs.openstack.org/newton/config-reference/firewalls-default-ports.html But I have no clue how to confirm the free port as lots of service running for OpenStack. 1 idea is to get default port entry Somewhere during adding project to governance or somewhere where it can be maintained actively. -gmann > -Original Message- > From: Sylvain Bauza [mailto:sba...@redhat.com] > Sent: 20 December 2016 17:30 > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [nova] [placement] Which service is using port > 8778? > > > > Le 20/12/2016 09:12, Sylvain Bauza a écrit : > > > > > > Le 20/12/2016 07:31, Ghanshyam Mann a écrit : > >> Changing placement API port to 8780 [1], hope this is not being used by > any services. > >> > >> But I am not sure how to check all used port currently as wiki does not > seems to have all. > >> > >> .. [1] https://review.openstack.org/#/c/412770/ > >> > > > > > > FWIW, we recently merged a devstack-gate change yesterday that now > > runs the placement service by default, which is why it's breaking > > Senlin gate now. > > https://review.openstack.org/#/c/409871/ > > > > We also have a change up for modifying stackrc to start kicking the > > placement service by default too > > https://review.openstack.org/#/c/412537/ > > > > Before moving forward and picking yet another port that could trample > > another service, I'd rather prefer first that Senlin jobs would > > temporarely disable the placement-* services so that the gate would be > > happy, while in the same time we try to identify a free port number > > that the placement API can safely bind. > > > > Yeah confirmed. > > A working job doesn't show the placement-api service [a] to be run while a > failing one does [b] > > I'm just writing a change against [c] to temporarely disable the placement-api > service. That will need to be reverted very soon since we want to have the > placement API mandatory for Ocata anyway but that will help your gate while > we identify a correct port number. > > > [a] > http://logs.openstack.org/31/412331/1/check/gate-senlin-dsvm-tempest- > api/b1dfbf9/logs/localrc.txt.gz > > [b] > http://logs.openstack.org/43/412843/1/check/gate-senlin-dsvm-tempest- > api/cff7c55/logs/localrc.txt.gz > > [c] > https://github.com/openstack-infra/project- > config/blob/d86338e968b84d119a59a6873b1d9c7ea17c37a8/jenkins/jobs/se > nlin.yaml > > > -Sylvain > > > -Sylvain > > > > > >> -gmann > >> > >> > >>> -Original Message- > >>> From: Ghanshyam Mann [mailto:ghanshyam.m...@nectechnologies.in] > >>> Sent: 20 December 2016 15:17 > >>> To: OpenStack Development Mailing List (not for usage questions) > >>> > >>> Subject: Re: [openstack-dev] Which service is using port 8778? > >>> > >>> Yes, it seems placement API using it [1] > >>> > >>>> 1. Recent changes to tempest is breaking our plugin. This is being > >>>>fixed. > >>> Tempest patch should fix issue but port issue blocking that[2] > >>> > >>> For port think, I think we can change the placement API port to > >>> something else. I will propose and we can get unused port there. > >>> But OpenStack port used by services are maintained here[3], may be > >>> it will be good for each project to add their port in this list. > >>> > >>> .. [1] - https://github.com/openstack- > >>> dev/devstack/blob/master/lib/placement#L50 > >>> ..[2] https://review.openstack.org/#/c/412658/ > >>> ..[3] > >>> http://docs.openstack.org/newton/config-reference/firewalls-default- > >>> ports.html > >>> > >>> -gmann > >>> > >>> > >>>> -Original Message- > >>>> From: Qiming Teng [mailto:teng...@linux.vnet.ibm.com] > >>>> Sent: 20 December 2016 14:45 > >>>> To: openstack-dev@lists.openstack.org > >>>> Subject: [openstack-dev] Which service is using port 8778? > >>>> > >>>> Hi, all, > >>>> > >>>> Starting yesterday, Senlin's gate jobs kept failing due to two reasons: > >>>> >
Re: [openstack-dev] [nova] [placement] Which service is using port 8778?
Le 20/12/2016 09:12, Sylvain Bauza a écrit : > > > Le 20/12/2016 07:31, Ghanshyam Mann a écrit : >> Changing placement API port to 8780 [1], hope this is not being used by any >> services. >> >> But I am not sure how to check all used port currently as wiki does not >> seems to have all. >> >> .. [1] https://review.openstack.org/#/c/412770/ >> > > > FWIW, we recently merged a devstack-gate change yesterday that now runs > the placement service by default, which is why it's breaking Senlin gate > now. > https://review.openstack.org/#/c/409871/ > > We also have a change up for modifying stackrc to start kicking the > placement service by default too https://review.openstack.org/#/c/412537/ > > Before moving forward and picking yet another port that could trample > another service, I'd rather prefer first that Senlin jobs would > temporarely disable the placement-* services so that the gate would be > happy, while in the same time we try to identify a free port number that > the placement API can safely bind. > Yeah confirmed. A working job doesn't show the placement-api service [a] to be run while a failing one does [b] I'm just writing a change against [c] to temporarely disable the placement-api service. That will need to be reverted very soon since we want to have the placement API mandatory for Ocata anyway but that will help your gate while we identify a correct port number. [a] http://logs.openstack.org/31/412331/1/check/gate-senlin-dsvm-tempest-api/b1dfbf9/logs/localrc.txt.gz [b] http://logs.openstack.org/43/412843/1/check/gate-senlin-dsvm-tempest-api/cff7c55/logs/localrc.txt.gz [c] https://github.com/openstack-infra/project-config/blob/d86338e968b84d119a59a6873b1d9c7ea17c37a8/jenkins/jobs/senlin.yaml -Sylvain > -Sylvain > > >> -gmann >> >> >>> -Original Message- >>> From: Ghanshyam Mann [mailto:ghanshyam.m...@nectechnologies.in] >>> Sent: 20 December 2016 15:17 >>> To: OpenStack Development Mailing List (not for usage questions) >>> >>> Subject: Re: [openstack-dev] Which service is using port 8778? >>> >>> Yes, it seems placement API using it [1] >>> 1. Recent changes to tempest is breaking our plugin. This is being fixed. >>> Tempest patch should fix issue but port issue blocking that[2] >>> >>> For port think, I think we can change the placement API port to something >>> else. I will propose and we can get unused port there. >>> But OpenStack port used by services are maintained here[3], may be it will >>> be good for each project to add their port in this list. >>> >>> .. [1] - https://github.com/openstack- >>> dev/devstack/blob/master/lib/placement#L50 >>> ..[2] https://review.openstack.org/#/c/412658/ >>> ..[3] http://docs.openstack.org/newton/config-reference/firewalls-default- >>> ports.html >>> >>> -gmann >>> >>> -Original Message- From: Qiming Teng [mailto:teng...@linux.vnet.ibm.com] Sent: 20 December 2016 14:45 To: openstack-dev@lists.openstack.org Subject: [openstack-dev] Which service is using port 8778? Hi, all, Starting yesterday, Senlin's gate jobs kept failing due to two reasons: 1. Recent changes to tempest is breaking our plugin. This is being fixed. 2. Senlin API cannot bind it to port 8778 now. So, we are wondering which service else is using port 8778? Thanks in advance for any hints. Regards, Qiming >>> __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev- requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> __ >>> >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: OpenStack-dev- >>> requ...@lists.openstack.org?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] [placement] Which service is using port 8778?
Le 20/12/2016 07:31, Ghanshyam Mann a écrit : > Changing placement API port to 8780 [1], hope this is not being used by any > services. > > But I am not sure how to check all used port currently as wiki does not seems > to have all. > > .. [1] https://review.openstack.org/#/c/412770/ > FWIW, we recently merged a devstack-gate change yesterday that now runs the placement service by default, which is why it's breaking Senlin gate now. https://review.openstack.org/#/c/409871/ We also have a change up for modifying stackrc to start kicking the placement service by default too https://review.openstack.org/#/c/412537/ Before moving forward and picking yet another port that could trample another service, I'd rather prefer first that Senlin jobs would temporarely disable the placement-* services so that the gate would be happy, while in the same time we try to identify a free port number that the placement API can safely bind. -Sylvain > -gmann > > >> -Original Message- >> From: Ghanshyam Mann [mailto:ghanshyam.m...@nectechnologies.in] >> Sent: 20 December 2016 15:17 >> To: OpenStack Development Mailing List (not for usage questions) >> >> Subject: Re: [openstack-dev] Which service is using port 8778? >> >> Yes, it seems placement API using it [1] >> >>> 1. Recent changes to tempest is breaking our plugin. This is being >>>fixed. >> Tempest patch should fix issue but port issue blocking that[2] >> >> For port think, I think we can change the placement API port to something >> else. I will propose and we can get unused port there. >> But OpenStack port used by services are maintained here[3], may be it will >> be good for each project to add their port in this list. >> >> .. [1] - https://github.com/openstack- >> dev/devstack/blob/master/lib/placement#L50 >> ..[2] https://review.openstack.org/#/c/412658/ >> ..[3] http://docs.openstack.org/newton/config-reference/firewalls-default- >> ports.html >> >> -gmann >> >> >>> -Original Message- >>> From: Qiming Teng [mailto:teng...@linux.vnet.ibm.com] >>> Sent: 20 December 2016 14:45 >>> To: openstack-dev@lists.openstack.org >>> Subject: [openstack-dev] Which service is using port 8778? >>> >>> Hi, all, >>> >>> Starting yesterday, Senlin's gate jobs kept failing due to two reasons: >>> >>> 1. Recent changes to tempest is breaking our plugin. This is being >>>fixed. >>> >>> 2. Senlin API cannot bind it to port 8778 now. >>> >>> So, we are wondering which service else is using port 8778? >>> >>> Thanks in advance for any hints. >>> >>> Regards, >>> Qiming >>> >>> >>> >> __ >>> >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: OpenStack-dev- >>> requ...@lists.openstack.org?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> __ >> >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: OpenStack-dev- >> requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
