Bellhop is a highly extensible framework providing an easy way to scale Azure managed services between their available service tiers on a schedule. The solution is completely serverless and built leveraging Azure Functions, Storage Queues, and resource tags. The modular nature of Bellhop was thoughtfully designed to make it possible for anyone to extend this solution to cover their specific needs.
| File/folder | Description |
|---|---|
dev/ |
Development Repo Containing Sample Scaler Module Code |
docs/ |
Docsify Repo |
functions/ |
Bellhop Engine & Scaler Function Code |
templates/ |
Bellhop Infrastructure ARM Template & Portal UI Definition |
.gitignore |
Untracked Files to Ignore |
CODE_OF_CONDUCT.md |
Microsoft Code of Conduct |
LICENSE |
MIT License |
README.md |
This README File |
SECURITY.md |
Microsoft Open Source Security Information & Details |
The Bellhop project leverages Docsify and GitHub Pages to present the project documentation, which can be found here:
The Bellhop team welcomes engagement and contributions from the community. We have set up a GitHub Discussions page here to make it easy to engage with the Bellhop team without opening an issue.
Also, feel free to email us at bellhop@microsoft.com with any questions or comments and we will respond as soon as we can.
Why would I use Bellhop?
You realize that by "turning down" your resources in Dev/Test environments you could save a lot on the cost of your infrastructure. You also realize there is not currently an easy way to scale between service tiers on Azure services. Bellhop to the rescue!!!! Tag your resources with scale times and desired service tier settings and let Bellhop take care of the rest!
What does the roadmap for Bellhop look like?
We would like this to become a SaaS/PaaS product that will help to keep our customers costs under control in Dev/Test Environments.
Who are the awesome people that built this solution??
Matt, Nills, and Tyler are Cloud Solutions Architects at Microsoft, and are always looking for interesting ways to help our customers solve problems!
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.