Deploying the Pebble Flow Workflow Server
Deploying the Pebble Flow Workflow Server on Cloud infrastructure.
Deploying Pebble Flow on Microsoft's Azure Cloud
Create the resource
The Pebble Flow Workflow Server is deployable as an Azure resource. It is available on the Azure Marketplace. Click on "Create a resource"
Azure services's "Create a Resource" button
Search for the Pebble Flow Workflow Server
Click on the Pebble Flow Workflow Server card.
Search for "Pebble Stream" to find the Pebble Flow server on Azure Marketplace.
Begin Pebble Flow deployment
Point-and-click deployment via the Azure Marketplace UI is straightforward and completed in three steps. Choose your appropriate plan, then click the blue "Create" button to start configuring the Pebble Flow deployment.
Click on the 'Create' button to begin Azure deployment.
Choose the plan that best fits your organization's needs.
Step 1 - select your deployment subscription and choose resource names
Select your subscription and a unique resource group for deployment in the first step. You should isolate Pebble Flow's deployment from your other Azure resource groups. Choose your App Service plan and select a storage account type that meets your business continuity need.
Search for "Pebble Stream" to find the Pebble Flow server on Azure Marketplace.
Be sure to choose plans that support autoscaling if you want to use that feature.
Step 2 - Enter the API key and specify the admin user
Enter your API key (contact us to get this), along with the email address and name of the Pebble Flow administrator. The deployment will automatically create an account for this user. Make sure to enter the correct email address at this step.
Please enter the API key, a valid admin user email and name, and the organization's name.
Step 3 - optionally copy metadata from a previous installation.
If there was a previous Pebble Flow installation, you may copy its pebble resources to this new installation. If you don't want to do this, uncheck "Copy data from existing storage account" and proceed to the next step.
Copy users, compiled pebbles, spreadsheets, workflows, authorizations, and API endpoints to the new installation.
Request, job, and scenario results from the previous install are not copied.
Review configuration, accept terms, then deploy
On the final screen, you must agree to the terms and conditions for using Pebble Flow on the Azure Marketplace.
Agree to the terms and conditions for running resources procured from Azure's Marketplace.
The Pebble Flow Workflow Server deployment should be completed in 30 minutes or less.
Autoscaling Pebble Flow on Microsoft's Azure Cloud
Pebble Flow is designed to run as a dynamically distributed service on Azure. Azure App Service's built-in autoscaling can be used to manage costs. Pebble Flow's API uses Azure Blobstore's queues to manage request traffic, and Azure App Service is designed to monitor queue traffic for scaling cues.
Configuring Azure App Service autoscaling via the portal is simple.
You can use Azure's portal to configure scaling rules based on pending Pebble Flow request message counts.
One way to configure your scaling capability using Azure's portal is to scale up the number of Pebble Flow servers as long as the average number of pending requests is above a certain threshold. Scaling down could be triggered by completely draining the request queue. Of course, the maximum number of servers can be capped, regardless of the number of pending requests.
Make sure to choose an App Service sku that supports autoscaling. If you don't, you can always change your plan.
Updated 12 days ago