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

Question: replacement for "any" facility feature #137

Closed
grossmj opened this issue Nov 15, 2023 · 2 comments
Closed

Question: replacement for "any" facility feature #137

grossmj opened this issue Nov 15, 2023 · 2 comments

Comments

@grossmj
Copy link

grossmj commented Nov 15, 2023

Hi,

I had the following code with facility='any' which allowed me to provisioning a server in "any" location. Facilities are now deprecated and I haven't found something similar when using metros. Is there a way or workaround to get the same as before? Thanks.

manager = packet.Manager(auth_token=token)
device = manager.create_device(
            project_id=project_id,
            hostname=hostname,
            plan=server_type,
            facility='any',
            operating_system="ubuntu_22_04")
@displague
Copy link
Member

Hi @grossmj, (your username has a random derision for my initials)

There is no equivalent for metros. Metro rates can vary, Sao Paulo vs Chicago, for example. https://deploy.equinix.com/pricing/

You can check the price and capacity of a metro and plan combination using the following:

In the Terraform Provider's E2E tests, we use this pattern to ensure that E2E tests don't trip over capacity.

Also see #136. If Pricing and Capacity endpoints are not covered in this project, you can find them in metal-python.

@grossmj
Copy link
Author

grossmj commented Nov 15, 2023

All clear, thanks for your answer :)

@grossmj grossmj closed this as completed Nov 15, 2023
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

2 participants