The deployment script will ask the user to input a unique name for their deployment, as well as their desired Azure region. Clone the GitHub repo down to your local machine.The list of services currently supported by Bellhop:ĭeploying Bellhop Steps to deploy infrastructure: Azure RBAC role of Owner or Contributor at the Subscription scope.necessary to assign proper scope to managed identity.Azure AD Role allowing user to assign roles (Global Admin, App Admin, Cloud App Admin).To successfully deploy this project, it requires the Azure user have the following: Guidelines for contributing to the sample. PowerShell script to decommission the tool. Repo Contents File/folderīellhop project Azure Functions. The Scaler-Trigger function leverages custom scaler modules per resource type to fufill the scale request.
The Engine will then post a scale instruction message in the Storage Queue, at which time the Scaler-Trigger Function will pull the message from the queue and begin processing the scale request. Users will need to tag their resources with the required tags (covered below), and the Engine Function will then use those tags to determine which resources need to be scaled, to which tiers, and when. Bellhop is comprised of 2 separate Azure Functions one is the Engine written in C#, and the other is the Scaler-Trigger. We put our heads together and came up with a serverless option to adress this issue built almost entirely around Azure Functions. Particularly when referring to scaling between service tiers. This project was born out of the customer need to save money, and a gap in Azure's ability to easily "turn down" Managed services in Dev/Test environments. Bellhop allows a user to 'hop' between service tiers, like a traditional bellhop helps you move between floors.