MapR In Azure

Document created by wochanda Employee on Aug 25, 2017Last modified by maprcommunity on Aug 29, 2017
Version 6Show Document
  • View in full screen mode

Getting Started - Deploying MapR in Azure

Several options are available for getting started with MapR in Azure, with varying levels of effort and customizability.


Deployment OptionGood for Users or Organizations Who Are/HaveSimplicityCustomizabilityLicensing

Azure Marketplace

New to Azure or MapR

Full Access to Azure Account


Pre-defined Example

Some Experience with Azure or MapR

Some Limits to Azure Access


Customized Pre-defined Example

Extensive Experience with Azure or MapR

Complex Azure Security Policy and Roles


Manual Deployment

Learning How MapR Deploys on Azure

Using Other Automation Tools Like Terraform or Ansible



About Deployment

Installation Architecture

There are two stages to deploying MapR in Azure:

  1. Deploying the Azure cloud environment, including VNets.
  2. Deploying the MapR software on new Virtual Machines.


These stages are kept separated in order to support the myriad ways in which users or organizations want to customize their cloud environment, or the way they deploy software.  Many other software vendors try to control the entire cloud lifecycle, including provisioning of networks, to the dismay of customers with organizational policies that restrict network configuration, naming, and security policies.


For the first stage, deploying the Azure cloud environment, MapR provides pre-built utilities including the Azure Marketplace and pre-defined example Azure Resource Manager (ARM) templates.  Because every company and environment is different, MapR also supports fully customized deployments, including modification of example ARM templates or manually provisioning a cloud environment from the Azure console.  Power users can also automate cloud provisioning steps using another automation framework like Ansible or Terraform by following the steps listed in the manual deployment


Once a cloud environment is deployed, the MapR Installer has an Azure plugin for deploying the Azure instances that will become the MapR nodes.  Letting the MapR Installer control instance provisioning allows the MapR software to control the full lifecycle of the cluster, expanding the size on-demand, and in the future cycling through failed or underperforming instances.  The MapR installer links to Azure Resource Groups, which serve as templates for instance configuration, allowing users to create instances using any available configuration and features that Azure supports.


The architecture diagram below shows the separation of duties between what the MapR-provided ARM Templates or Azure Marketplace entires perform, and what the MapR Installer Performs.