I’ve setup a proxy server to allow us to submit jobs from a local monitor application to a repository located in the cloud. This seems to work for basic cases, but when jobs reference filer paths that are only resolvable within the cloud network, we have a problem. It seems as if the proxy server is not the one trying to resolve the SMB filer shares, but rather that work is left to the client monitor application (which of course can’t see filer paths that are not accessible outside the cloud network).
Two questions:
a) Is this expected behavior when using the proxy server?
b) What is your suggestion for how best to reference data stored in the cloud, when submitting jobs via a proxy server, while still maintaining the security of that data that is in the cloud?
Repository Version: 8.0.0.55 (691026406)
Integration Version: 8.0.0.55 (691026406)
Deadline Client Version: 8.0.0.55 Beta (691026406)
OS: Windows 2012 R2.
I’m also noticing that monitoring via a proxy has refresh issues. Sometimes the monitor starts up with no information in any of the panels for a while… a minute or more. Other times, jobs don’t refresh and slave status doesn’t refresh. If I close and reopen the monitor, then I get an updated view. Are there any known issues with Deadline 8 monitor via proxy that I can look at?
Hey Hickabee,
Sorry for the late reply but:
- This is expected behavior.
- My immediate reaction is for you to look in to path mapping.
docs.thinkboxsoftware.com/produc … tform.html
deadline.thinkboxsoftware.com/fe … the-basics
It is hard for me to give you a definitive solution without knowing more about your setup. If you are available we can setup a quick call to discuss your architecture, I am free all week from 8am - 4pm CST.
It seems like this path mapping solution is solving a different problem than I have. Submitting a job from a Windows machine, via a proxy, to Windows slaves, with a Windows repository, should not need to map paths. It feels instead, like the problem is that the monitor on the client end of the firewall is trying to resolve paths on the server end of the firewall, rather than have the proxy (within the firewall), resolve the paths. If you can send me a private email we can figure out a time to setup a call. I’d like to talk further about this issue, and also about the problems we’ve been having with failed updating in the monitor application. Thanks. Brian
P.S. I’ll assume you have my email address, available via my sign-in info.