kave on azure introduction

Introduction, KAVE on Azure

KAVE on Azure is meant to make provisioning.deploying a KAVE on the Microsoft Azure platform as simple as possible. For other topics, see elsewhere in this wiki.

Deployment -> Provisioning a cluster

KAVE is a redeployable platform, and can be redeployed in any location, so long as the basic requirements are met. Example deployments include:

• Appliances (static hardware for predefined purpose, delivered pre-installed)
• On-premise (installed within a data center or on a server rack)
• Hosted (outsourced or contracted IaaS/PaaS/SaaS)
• In the cloud (on cloud IaaS solutions)

Each different environment, however, needs to be provisioned before KAVE can be installed. Machines, disks, networks, need to be created and then the KAVE software installed within that cluster. Creating this cluster can be time-consuming and requires a certain level of expertese.

KAVE on azure is meant to simplify this process for KAVE deployments on the Microsoft Azure cloud to speed up configuring and deploying a KAVE, bringing it closer to a PaaS solution. In the AmbariKave project we already maintain scripts to simplify deploying KAVEs on the aws cloud platform, and we are here extending that support to Microsoft Azure.

Three different deployment styles

Deployment on Azure can be done in three different ways, deployment is described elsewhere

• Manual deploy. The user provisions and configures all machines, and installs KAVE as if it were any other cluster, see Installing AmbariKave
• Marketplace deploy: The user clicks a button on the Azure marketplace and the provisioning of a fixed/static set machines with fixed/static configuration is performed with minimal user intervention see AmbariKave-azure and links to be provided in the future
• Template deploy: the user chooses from a list of clusters, sizes, and configurations, clicks a deployment link on github and then this set of machines and configurations is deployed with minimal intervention from the user. See AmbariKave-azure-templates

The three different respositories

This project may look confusing because it involves three different git repositories. Since there are three different deployment options, there are three corresponding github repos:

• AmbariKave : The main repository for the open-source development of our extention of Ambari, adding KAVE components.
• AmbariKave-azure : this repository is used automatically by the Marketplace deployment, and is a technical repository not particularly useful for other purposes
• AmbariKave-azure-templates : this repository contains deployment templates that the user may choose between and decide what to provision on Azure

Where now?

• Deployment
• Connecting