Open tjanczuk opened 12 years ago
We should also think about how to handle the logs.
There are several things that need to happen for multi-instance support:
git azure init
must allow --instances
to be greater than 1git azure init
, the check of the status of the deployment must be modified to account for multiple instancesgit-azure-init
, the IP addresses of all backends must be stored in git configgit azure reset
This will take several commits, I will be doing the work in a scaleout
branch.
What I'm thinking for solving this issue is the following:
1) Add support for adding and removing instances from the CLI. 2) As all instances will be behind the same load balancer, the post-commit hook will hit allways one of those instances, so we should make that instance to propagate that POST to all the rest of the instances in the same role. For that purpose we can use the Azure SDK for Node.js for: