Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Weird way to send a private message, I know :-D #1

Open
vasylenko opened this issue Apr 27, 2021 · 7 comments
Open

Weird way to send a private message, I know :-D #1

vasylenko opened this issue Apr 27, 2021 · 7 comments

Comments

@vasylenko
Copy link

vasylenko commented Apr 27, 2021

@OliverKoo Hi again :) Please excuse me for using your repo as a chat, but GitHub does not allow sending a private message.

I just wanted to ask if you could share a screenshot with Host resource group settings that allowed you to automatically allocated mac1 Hosts. When I PoC'ed that briefly, I could not make it work in a way that host would allocate automatically (and LT was failing to launch the instance because there were no hosts allocated). But looks like I missed something.

I am referring to the small conversation we've had here: hashicorp/terraform#28531

@OliverKoo
Copy link
Owner

hi again! Indeed I never see people send message this way. I praise your creativity 😄

I saw your message a bit late. After I digged a little deeper. I found this commit in the latest aws terrraform provider (v3.37.0) which I think solves our issue, so I have deleted most of the PoC resources (It's easier to delete the recreate using terraform instead of import imo)

I will screenshot once things are up and running again tho 👍

@OliverKoo
Copy link
Owner

spoke too soon, actually host_resource_group_arn was dropped hashicorp/terraform-provider-aws#11655 (comment)

@OliverKoo
Copy link
Owner

plot twist, an ongoing fix just got merged today! hashicorp/terraform-provider-aws#15785

Likely be released tomorrow.

I have things up and running now. ASG set up and is scaling. What do you need exactly? @vasylenko

@vasylenko
Copy link
Author

@OliverKoo wonderful! 🥳
Could you please show me how the Host group for mac1.metal is configured in detail?

@OliverKoo
Copy link
Owner

@vasylenko sorry for the late reply, went on vacation and got distracted when I get back. 😅

In the ASG I use a launch template and the critical part of Launch Template is to have tenancy and tenancy host group set

Screen Shot 2021-05-19 at 11 53 43 AM

the host group is created under License Manager which is well documented here https://docs.aws.amazon.com/license-manager/latest/userguide/host-resource-groups.html

@thomasdesr
Copy link

thomasdesr commented Jun 2, 2021

Hey @OliverKoo! Sorry in advance for lurking into this private convo 😅

When you were messing with this did you ever get an error like this?

You do not have a host with a matching configuration and sufficient capacity. Either target a host resource group that can automatically allocate hosts on your behalf, or manually allocate a new host to your account and then try again. Launching EC2 instance failed.

It seems to imply that the resource group is not configured with Allocate hosts automatically, but I'm fairly sure I've set that correctly.

If it helps and you'd be willing to take a look, I've extracted a self-contained example of what I'm trying: (https://gist.github.com/thomasdesr/be6be7d2829726408db77f783d640c82) :D

@thomasdesr
Copy link

I figured it out! :D

I was misconfiguring the License such that it wouldn't work with the Host Resource group correctly. The error message was accurate although confusing. Changing the earlier link like this (https://gist.github.com/thomasdesr/caecee66ffc566ab83d6d634c80a5be4) fixes the issue and correctly launches an asg of mac1.metal instances.

Thanks for figuring this out the first time, both of your convos were super helpful. And knowing it could be done meant it had to me doing something wrong XD

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants