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

[FEATURE] add OLA management for baremetal #464

Open
achaussier opened this issue Sep 7, 2023 · 1 comment
Open

[FEATURE] add OLA management for baremetal #464

achaussier opened this issue Sep 7, 2023 · 1 comment
Assignees

Comments

@achaussier
Copy link

Description

It could be interesting to manage OLA via Terraform. I think using the existing ovh_dedicated_server_update resource or adding a new resource.

Affected Resource(s) and/or Data Source(s)

  • ovh_dedicated_server_update ?

Potential Terraform Configuration

Perhaps adding a new bloc ola ? On my side I work with advance3 servers, so I can create only one OLA, but perhaps on other servers types we can manage multiple links, so plan to have multiple blocks (and be able to manage them via dynamic blocks)

...
ola {
  interfaces = [...]
  name = "foobar"
}
...

Additional context

@SLoeuillet
Copy link

SLoeuillet commented Dec 17, 2024

With a Scale, which has 2 public NICs in a bond by default and 2 private NICs in a second bond by default, enabling OLA gives you a single bond with 4 ports.

So, no need for OLA blocks

It is more a boolean that would call
https://eu.api.ovh.com/console/?section=%2FallDom&branch=v1#post-/dedicated/server/-serviceName-/ola/aggregation
With all 4 macs for a Scale/HGR, all 2 macs for advance/rise

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

No branches or pull requests

4 participants