arvindshmicrosoft commented on a change in pull request #429:
URL: https://github.com/apache/fluo-muchos/pull/429#discussion_r780065338
##########
File path: conf/muchos.props.example
##########
@@ -18,7 +18,7 @@
cluster_type = ec2
# Cluster user name (install command will SSH to cluster using this user)
# Leave default below if launching cluster in AWS
-cluster_user = centos
+cluster_user = fedora
Review comment:
Got it. This is also probably a difference between the Muchos `launch`
mechanisms for EC2 and Azure. For Azure since we use Ansible itself to launch
the VMs, we are able to set the default [admin user
name](https://docs.ansible.com/ansible/latest/collections/community/azure/azure_rm_virtualmachinescaleset_module.html#parameter-admin_username)
to the `cluster_user` at launch time itself. From what I can see in the Muchos
ec2 launch code, we don't pass the `cluster_user` to the EC2 instance launch
calls (via. boto3), which is likely why you had to change the value of
`cluster_user` instead to match the AMI default.
These differences are all good learnings towards eventually normalizing
architecture and code as much as possible between the different cluster types,
specifically for the `launch` phase which is pretty much where the cluster-type
specific code is. Anyways, that's for another day 😃
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
