action #10100

Get rid of dependency on apache2

Added by okurz about 4 years ago. Updated over 1 year ago.

Status:ResolvedStart date:06/01/2016
Priority:LowDue date:
Assignee:-% Done:

0%

Category:Feature requests
Target version:QA - future
Difficulty:
Duration:

Description

observation

openqa requires apache2 for a websockets server. It listens on different port since it is different process and apache is proxying it from regular 80. openQA worker uses the same port for regular HTTP requests and websockets.

Also see

See https://github.com/os-autoinst/openQA/pull/494#issuecomment-169315995

acceptance criteria

  • a test job scheduled from the webui is started on a worker without apache running

implementation ideas

History

#1 Updated by coolo about 4 years ago

Could you please describe the business value?

#2 Updated by okurz about 4 years ago

I would say only trivial business value as it should be considered an enhancement to the existing project, i.e. making it easier for developers, system more optimized, etc. It should be technically possible and was already prepared in the current source code but apparently does not work, see https://github.com/os-autoinst/openQA/blob/master/lib/OpenQA/WebAPI.pm#L397 and following

#3 Updated by oholecek about 4 years ago

After some reading, if we are going to fix that, we need to fix that on worker side. Many WebSockets clients does not accept redirects or anything beyond 101 code and close the connection.
If we are not going to fix this, we should update openQA package to require apache.

#4 Updated by okurz about 4 years ago

  • Priority changed from Normal to Low
  • Target version set to future

#5 Updated by okurz about 3 years ago

With gh#1121 done we have a local full stack test working standalone without the need for apache. coolo: "There is one other place where we require a proxy: asset download. But we can implement (and test :) this as well".

But you might still want a proxy on port 80 - just saying.

#6 Updated by coolo almost 2 years ago

  • Status changed from New to Resolved

we now have a nginx config - I think that counts :)

#7 Updated by okurz over 1 year ago

  • Target version changed from future to future

Also available in: Atom PDF