-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #675 from Juniper/feat/672
#672 Update routing zone example code
- Loading branch information
Showing
3 changed files
with
32 additions
and
14 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
21 changes: 15 additions & 6 deletions
21
examples/resources/apstra_datacenter_routing_zone/example.tf
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,10 +1,19 @@ | ||
# This example creates a routing zone within an | ||
# existing datacenter blueprint. | ||
resource "apstra_datacenter_routing_zone" "blue" { | ||
name = "vrf blue" | ||
blueprint_id = "<blueprint-id-goes-here>" | ||
vlan_id = 5 # optional | ||
vni = 5000 # optional | ||
dhcp_servers = ["192.168.100.10", "192.168.200.10"] # optional | ||
# routing_policy_id = "<routing-policy-node-id-goes-here>" # optional | ||
name = "vrf blue" | ||
blueprint_id = "<blueprint-id-goes-here>" | ||
vlan_id = 5 # optional | ||
vni = 5000 # optional | ||
dhcp_servers = ["192.168.100.10", "192.168.200.10"] # optional | ||
# routing_policy_id = "<routing-policy-node-id-goes-here>" # optional | ||
} | ||
|
||
# Next, assign an IPv4 pool to be used by loopback interfaces of leaf | ||
# switches participating in the Routing Zone. | ||
resource "apstra_datacenter_resource_pool_allocation" "blue_loopbacks" { | ||
blueprint_id = "<blueprint-id-goes-here>" | ||
routing_zone_id = apstra_datacenter_routing_zone.blue.id | ||
pool_ids = ["<ipv4-pool-id-goes-here>"] | ||
role = "leaf_loopback_ips" | ||
} |