mirror of
https://github.com/jambonz/jambonz-infrastructure.git
synced 2026-01-25 02:08:27 +00:00
49e16583dd
- change all multi-token commands to use lists instead of strings: in some cases special characters were interpreted by the shell, and so the full command arguments were interpreted. this resulted in the system not being able to correctly ACK incoming calls, in turn causing calls to hang up after 30 seconds - change NODE_ENV to test for sbc-inbound: with NODE_ENV set to production for the sbc-inbound, feature server registration does not happen quite right with the redis host, causing calls to bounce - merge common environment variables: since many of the containers share the same env vars, this merges those together in a common section which simplifies updating and debugging these settings
jambonz infrastructure
This repository contains packer and Cloudformation templates for deploying jambonz on AWS EC2 instances. For deploying jambonz on Kubernetes, please refer to the jambonz helm chart repo.
There are two supported deployment configurations:
- a jambonz-mini deployment which is an "all-in-one" deployment of jambonz on a single EC2 instance. This type of deployment is ideal for development and testing, as well as running smaller production loads. A cloudformation script script is provided to deploy the instance and create the supporting VPC, subnets, etc. that are needed.
- a production deployment which deploys jambonz in a horizontally-scalable cluster using autoscale groups. For this deployment, 5 different packer scripts are provided to build the 5 AMIs that are needed, and a cloudformation script script is provided to deploy them and create the supporting VPC, subnets, etc. that are needed.