search

DeployHubProject / DeployHub-Pro

DeployHub Pro Pipeline Status Project
https://www.openmakesoftware.com/application-release-automation-for-continuous-delivery/
Other
11 stars 4 forks source link

proxy to proxy connection #339

Closed piyush94 closed 3 years ago

piyush94 commented 3 years ago

Is it possible to connect two DH proxies to transfer artifacts and deployment instructions?

sbtaylor15 commented 3 years ago

You can have at max one Deployment Engine/Proxy per domain. If an engine or proxy is not found then it will work upwards through the domain hierarchy until one is found. This lookup starts at the domain that the application version is located.

So you could have a Staging and Prod domains, each with their own proxy. Or customer1 and customer2 domain, each with their own proxy.

The application version will need to be moved to each domains prior to the deployment so the right proxy is picked up. Not able to do simultaneous deployments with the same application version.

piyush94 commented 3 years ago

Sorry, let me explain our scenario better. We want to connect two DH proxies with each other. So that one proxy can transfer artifacts and instructions to another DH proxy.

image

sbtaylor15 commented 3 years ago

Why the extra DH Proxy, 2 separate databases? If the DH Proxy on the left has access to the database then it can poll the database for work to do and skip the extra DH Proxy which is doing the same polling.

piyush94 commented 3 years ago

The reason for the extra DH Proxy is, as there will be multiple endpoints on the client side like VMs, K8s clusters, etc. instead of opening all the required ports in the firewall, we could open only DH Proxy ports.

I think we found an approach now, to allow client-side DH Proxy to connect to our on-prem DeployHub.

Thanks.