Skip to content
Last update: May 10, 2022

Create a Quorum Blockchain Service network

Quorum Blockchain Service (QBS) is a fully-managed platform as a service (PaaS) available in Microsoft Azure as an Azure Managed Application. While QBS is hosted in Azure, it’s managed by ConsenSys to ensure high availability, optimal performance, and that your infrastructure has the most up-to-date security patches.

Important

QBS is currently listed as a private offer in Azure Marketplace. You can request access on the Quorum Blockchain Service website.

These instructions provide you with the details you need to provision a new blockchain network with QBS in Azure.

Prerequisites

Ensure your subscription includes a [sufficient number of vCPU cores]. We recommend 6 cores per environment, with the D2a V4 Series for Business and Enterprise tiers, and B2ms Series for the Development tier.

Steps

1. Access QBS

After contacting ConsenSys, QBS is available in the Azure Marketplace. To access the offer:

  1. Access the Azure Portal using your Microsoft Azure account details.

  2. In the Azure services section, select Create a resource.

  3. Select the See more in Marketplace link to access Azure Marketplace.

  4. Select View private offers.

Private Offers

  1. Select Quorum Blockchain Service to access the offer.

The Quorum Blockchain Service page displays.

2. Create the network

  1. In the Select a plan drop-down, select your QBS plan, and select Create.

  2. In the Basics tab of the Create Quorum Blockchain Service page:

    • Select the Azure subscription to use for the service.

    • Below the Resource group dropdown, select Create new and create a new resource group.

    • In the Region dropdown, choose a region to create the network.

    • In Consortium Name, enter a name for your consortium.

    • Under Plan Details, choose either Development, Business, or Enterprise.

    • In Contact Email, enter your contact email.

    • In the Azure Blockchain Service Migration Settings option, select No.

    • In Application Name, enter the name you wish to use for your QBS instance. Normally this is the name of your organization, or how you want to be identified by other parties in your network.

    • In Managed Resource Group, enter the name of your managed resource group, or select the default name provided.

    • If you wish to tag the resources created in your QBS member, select Next: Tags.

    • Select Next: Review + create.

  3. In the Review + create tab, select I agree to the terms and conditions above, and select Create.

  4. Deployment of your QBS member may take up to 10 minutes. After deployment completes, select Go to resource to view the QBS deployment.

Important

If your deployment fails because you’ve exceeded your CPU core quota, submit a support request with Azure to increase your quota and retry the deployment. We recommend 6 cores per environment.

3. Verify your deployment completed successfully

While you can find your QBS member in the Azure Portal after provisioning, we recommend verifying the deployment was successful.

Navigate to the QBS Management API website and select Authorize to authorize running the APIs.

Authorize API

Once you complete authorizing the API, select the GET request for Get details about a blockchain member under the BlockchainMembers section, and then select Try it out.

Try it out

In the fields for the API request, fill out the following using your QBS member information, located in the Azure portal:

  • subscriptionID - Your subscription ID, in the Overview tab for your QBS member, under the Essentials section.

  • resourceGroupName - The resource group to which your QBS member is deployed. Note this is NOT the Managed Application resource group.

  • blockchainMemberName - The name of your QBS member, also known as the name of your Managed Application, located in the upper-left corner of the Overview tab.

Overview Page

Select Execute. The website shows the server response, which lists the blockchain member information:

Example JSON result

  {
  "id": "/subscriptions/<YOUR SUBSCRIPTION ID>/resourceGroups/devtool-testing/providers/Microsoft.Solutions/applications/consensys",
  "location": "eastus",
  "name": "consensys",
  "sku": null,
  "tags": {},
  "type": "ConsenSys.Blockchain/blockchainMembers",
  "properties": {
    "consortium": "devtooltest",
    "consortiumMemberDisplayName": "consensys",
    "dns": "transaction-1.consensys.devtooltest.onquorum.net",
    "protocol": "Quorum",
    "provisioningState": "Succeeded",
    "publicKey": null,
    "rootContactAddress": null,
    "firewallRules": [],
    "validatorNodesSku": {
      "capacity": 1
    }
  }
}

provisioningState: is one of the following states:

  • Succeeded indicates that your provisioning completed successfully and your QBS member is ready to use.
  • Updating indicates provisioning is still in progress.
  • Failed indicates your QBS member failed to provision successfully. In this case, contact support for assistance.

4. Next steps

Once successfully deployed, you can configure QBS and deploy smart contracts to the network. See the following articles on getting started:

Back to top