Difference between revisions of "Deploying the Microsoft Azure Ardor Node"

From ArdorDocs
Jump to: navigation, search
m
 
(No difference)

Latest revision as of 15:09, 30 September 2020

Introduction

The Azure Ardor node allows us to launch an Ardor node, and to provision automatically the node database. It uses as an internal component the Ardor Docker image. To complete this tutorial, basic knowledge of Microsoft Azure is desirable. Microsoft has an extensive documentation and learning paths.


How to deploy de Ardor Azure app

The steps to deploy the Azure Ardor node are as follows:

Azure Ardor app


  • Once these main steps described above are completed, click on the "Get it now" button, and the following image will pop-up
Create this app in Azure


  • Afterwards, the image as follows will appear:
Create button


Click on the "Create" button:

Create Ardor Node


  • Configure the Subscription, select or create the Resource group to deploy the Ardor components, and the region where the components will be deployed.


Create Ardor Node


  • Provide the Ardor Node Configuration:
Create Ardor Node


  • Password: it refers to the Admin Password of the node.
  • Confirm Password: it must be the same as the field Password.
  • Select Mainnet or Testnet: mark the option Mainnet for an Ardor mainnet node, or Testnet for an Ardor testnet node.
  • DNS Label for the Ardor node: The Azure fully qualified domain name will be formed by the DNS label plus the container location. For instance, the DNS 'Ardor' deployed in the 'Northern Europe' region will be: ardor.northeurope.azurecontainer.io
  • Number of CPUs: 1 CPU is enough to run the Ardor node, this value can be increased in case parallelism is required
  • Memory in GB: 1 GB is enough to run the Ardor node, this value can be increased if needed, for instance when forging with a large amount of ARDR tokens.
  • Review + create. Click on the "Create" button, as shown below:
Review and Create Ardor Node


Once clicked, the deployment will start:


Deployment in progress


Deployment finished


The first execution takes slightly more time due to the provisioning of the node. When all these steps are completed, the node is ready to be accessed:

Ardor node up


Walk-through of the components deployed

The docker container and the storage account can be accessed through the resource group:

Deployment finished


Container

Deployment finished


File Shares

Deployment finished


Costs

The pricing is the cost of the deployed components which are:

  • A docker container. The pricing is explained in the link as follows: Container costs
  • A storage account, that will have 3 File Shares once created. Storage costs.

How to change Ardor parameters after the deployment

The docker container internal files are not accessible, hence you can either change the nxt.properties file by accessing to the file shared 'ardorconf' and editing the file directly, or by using the Node Configuration as shown as follows:

First, you have to provide the admin password:


Node Configuration


Node Configuration


Log in again, and the parameters will be available to be modified:

Node Configuration


For instance, to modify the nxt.apiSSL parameter, select it and click on change:

Node Configuration


After the modification, a restart of the node is needed. Click on the "Save and Shutdown" button:

Node Configuration


The final step is to execute again the container:

Node Configuration