action #10100
closedGet rid of dependency on apache2
0%
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¶
- work was started, see https://github.com/os-autoinst/openQA/pull/494#issuecomment-169311007 , but apparently is not working.
Updated by okurz over 8 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
Updated by oholecek over 8 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.
Updated by okurz over 8 years ago
- Priority changed from Normal to Low
- Target version set to future
Updated by okurz over 7 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.
Updated by coolo almost 6 years ago
- Status changed from New to Resolved
we now have a nginx config - I think that counts :)
Updated by okurz almost 6 years ago
- Target version changed from future to future