- Do all the containers in my application template have to run on the same host?
- What happens if the host goes down?
- Can I create a clustered application across multiple hosts or regions?
- How do I ensure High Availability?
- Can I comply with our company’s affinity rules so that our databases run on dedicated hosts?
We’re happy to announce that we now integrate with Weave and support multi-host container-based application deployments – addressing all of the aforementioned questions. DCHQ automates the deployment of clustered applications across multiple hosts in order to ensure high-availability and to comply with affinity rules.
When creating a Data Center or Cluster, a user is now able to select Weave as a networking option.
- host1, host2, host3, etc. – selects a host randomly within a data-center (or cluster) for container deployments
- <IP Address 1, IP Address 2, etc.> -- allows a user to specify the actual IP addresses to use for container deployments
- <Hostname 1, Hostname 2, etc.> -- allows a user to specify the actual hostnames to use for container deployments
- Wildcards (e.g. “db-*”, or “app-srv-*”) – to specify the wildcards to use within a hostname
- AFFINITY GROUPS // Deploy applications across multiple hosts to comply with affinity rules leveraging an integration with Weave. For example, web server and database containers can be deployed on different hosts to comply with best practices.
- HYBRID SUPPORT // Accelerate application development by allowing users to deploy their application server on a local machine while the rest of the app components may be deployed on a shared data-center.
- HIGH AVAILABILITY // Ensure that clustered application servers are distributed across multiple hosts or regions for high availability