fluo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [fluo-muchos] arvindshmicrosoft commented on a change in pull request #270: Support Accumulo installs on Microsoft Azure
Date Mon, 12 Aug 2019 20:02:51 GMT
arvindshmicrosoft commented on a change in pull request #270: Support Accumulo installs on
Microsoft Azure
URL: https://github.com/apache/fluo-muchos/pull/270#discussion_r313103376
 
 

 ##########
 File path: README.md
 ##########
 @@ -92,9 +124,36 @@ You can check the status of the nodes using the EC2 Dashboard or by running
the
 
     ./bin/muchos status
 
+## Launching an Azure cluster
+
+Before launching a cluster, you will need to complete the requirements for Azure above, clone
the Muchos repo, and
+create [muchos.props] by making a copy of existing [muchos.props.example.azure]. If you want
to give others access to your cluster, add their public keys to a file named `keys` in your
`conf/` directory.  During the setup of your cluster, this file will be appended on each node
to the `~/.ssh/authorized_keys` file for the user set by the `cluster.username` property.
 You will also need to ensure you have authenticated to Azure and set the target subscription
using the [Azure CLI](https://docs.microsoft.com/en-us/cli/azure/manage-azure-subscriptions-azure-cli?view=azure-cli-latest).
+
+Muchos by default uses a CentOS 7 image that is hosted in the Azure marketplace. The Azure
Linux Agent is already pre-installed on the Azure Marketplace images and is typically available
from the distribution's package repository. Azure requires that the publishers of the endorsed
Linux distributions regularly update their images in the Azure Marketplace with the latest
patches and security fixes, at a quarterly or faster cadence. Updated images in the Azure
Marketplace are available automatically to customers as new versions of an image SKU.
+
+Edit the values in the sections within [muchos.props] as below
+Under the `general` section, edit following values as per your configuration
+* `cluster_type = azure`
+* `cluster_user` should be set to the name of the administrative user
+* `proxy_hostname` (optional) is the name of the machine which has access to the cluster
VNET
+
+Under the `azure` section, edit following values as per your configuration 
+* `resource_group` and provide the same created in your Azure subscription for the cluster
deployment
+* `vnet` and provide the same created in your Azure subscription for the cluster deployment
+* `subnet` and provide the same created in your Azure subscription for the cluster deployment
+* `numnodes` can be changed as per the cluster size 
+* `vm_sku` can be specified from the available skus in the [selected Azure region](https://docs.microsoft.com/en-us/azure/virtual-machines/linux/cli-ps-findimage)
+
+Within Azure the `nodes` section is auto populated with the hostnames and their default roles.
 
 Review comment:
   @keith-turner given the 'launch' step for Azure uses VMSS, the auto-generated IPs associated
with the new VMs are surfaced in the hosts file and a recomended config is populated into
muchos.props under the nodes section. However, the user can still customize muchos.props (for
example, they can add fluo / spark etc. post the 'launch' step) and then run 'setup'; 'setup'
fully respects the nodes section. The only caveat is we do mandate 3 ZKs, 2 namenodes and
3 journal nodes to accommodate the HA requirements. That's what the default node assignments
for the first 3 nodes already have.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message