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 Request - Statically Allocate ASN and Loopback IPs to Border Leafs #562
Comments
Hi Feng, Thank you for opening this issue. Have you noticed the new It's related, but I think not quite exactly what you're looking for. I don't think Apstra has a way to allocate an element of a resource pool so that it can be re-used through destruction and re-creation of an object. It sounds to me like the ideal solution would be something along the lines of the AWS elastic IP object, which enables allocation of an IP address from the pool independent of the use of the IP, thereby decoupling the lifecycle of the address from the lifecycle of the object to which it's assigned. Does it sound like I'm understanding your problem? |
This might be a super-simplistic way of doing it, but couldn't we do ranges with single ASNs and then assign them? It would be pretty hard and annoying to do by hand, but with terraform might be a loopable resource |
first to answer Raj's comment: no it is not possible to create a pool with a single ASN in it and assign to a particular leaf. Apstra's concept is to assign a pool to a fabric role. For the ASN, there are two roles: spine vs leaf. second for Chris's comment: yes I just noticed the new system_attributes introduced. it sounds to me that it is the solution to address the problem. I could still use an Apstra ASN and IP pools to assign dynamic values to fabric spine and leaf roles, but meanwhile, I can try to use the new system_attributes to hardcode an ASN value and a loopback IP for each border leaf. I'll yet need to update current repo variable definition to accept system_attributes |
Unfortunately, it seems |
Hi @steve-hartt, Do you want to prescribe the specific addresses used on each leaf switch ( The former can be accomplished by using the Assigning prescribed IDs isn't something I know how to deal with offhand, but I can look into it. edit: Per Apstra product management, setting/changing the in-RZ loopback interface isn't currently supported. |
leaf ASN and Loopback IPs are allocated via the apstra_datacenter_resource_pool_allocation resource; the values are dynamically allocated and re-deploy a blueprint will change these values.
This imposes a major challenge for apstra_datacenter_external_gateway resource which needs to specify the remote border leaf ASN and Loopback IP values.
The feature request is for a resource or some workaround in the terraform code to be able to:
The text was updated successfully, but these errors were encountered: