Hi Ben,
thank for your reply. That was I was afraid of actually as it means
there's no easy solution to implement I guess.
I think some guys in my team are in contact with DS people, so I may
have a look there.
Jonathan
On 06/18/2015 07:26 PM, Ben Bromhead wrote:
OpsCenter is a little bit tricky to simply just rewrite urls, the lhr
requests and rest endpoints it hits are all specified a little
differently in the javascript app it loads.
We ended up monkey patching a buttload of the js files to get all the
requests working properly with our proxy. Everytime a new release of
OpsCenter comes out we have to rework it.
If you are a DSE customer I would raise it as a support issue :)
On 18 June 2015 at 02:29, Spencer Brown <lilspe...@gmail.com
<mailto:lilspe...@gmail.com>> wrote:
First, your firewall should really be your frontend There
operational frontend is apache, which is common. You want every url
with opscenter in it handled elsewhere. You could also set up
proxies for /. cluster-configs, etc...
Then there is mod_rewrite, which provides a lot more granularity
about when you want what gets handled where.I set up the
architectural infrastructure for Orbitz and some major banks, and
I'd be happpy to help you out on this. I charge $30/hr., but what
you need isn't very complex so we're really just talking $100.
On Thu, Jun 18, 2015 at 5:13 AM, Jonathan Ballet
<jbal...@gfproducts.ch <mailto:jbal...@gfproducts.ch>> wrote:
Hi,
I'm looking for information on how to correctly deploy an OpsCenter
instance behind a HTTP(S) proxy.
I have a running instance of OpsCenter 5.1 reachable at
http://opscenter:8888/opscenter/ but I would like to be able to
serve this kind of tool under a single hostname on HTTPS along
with other tools of this kind, for easier convenience.
I'm currently using Apache as my HTTP front-end and I tried this
naive configuration:
<VirtualHost *:80>
ServerName tools
...
ProxyPreserveHost On
######### Proxy to OpsCenter #########
ProxyPass /opscenter/
http://opscenter:8888/opscenter/
ProxyPassReverse /opscenter/
http://opscenter:8888/opscenter/
</VirtualHost>
This doesn't quite work, as OpsCenter seem to also serve
specific endpoints from / directly
Of course, it doesn't correctly work, as OpsCenter seem to also
serve specific data from / directly, such as:
/cluster-configs
/TestCluster
/meta
/rc
/tcp
Is there something I can configure in OpsCenter so that it
serves these URLs from somewhere else, or a list of known URLs
that I can remap on the proxy, or better yet, a known proxy
configuration to put in front of OpsCenter?
Regards,
Jonathan
--
Ben Bromhead
Instaclustr | www.instaclustr.com <https://www.instaclustr.com/> |
@instaclustr <http://twitter.com/instaclustr> | (650) 284 9692
