docs: add Layer 2 example including interconnection and VRF #232
Conversation
…233) This fixes a couple problems with the parameter definitions for the reserved IP block module: 1. The `cidr` and `network` parameters, needed for VRF IP reservations, were not defined in the module spec 2. The `quantity` parameter, which is unsupported for VRF IP reservations, was required in order to create _any_ IP reservation This PR updates the reserved IP block module so that it can be used to create a VRF IP reservation. The docs are also updated to reference the `cidr` and `network` parameters. This was broken out of #232.
ctreatma
force-pushed
the
l2-example
branch
2 times, most recently
from
e10d66a to
e1f46b6
Compare
ctreatma
force-pushed
the
l2-example
branch
2 times, most recently
from
fbe27c8 to
5ab1693
Compare
ctreatma
changed the title
examples/layer2/README.md
Outdated
|
|
||
| ## Variables | ||
|
|
||
| You can customize some variables from [vars/equinix_metal_vars.yml](vars/equinix_metal_vars.yml). |
There was a problem hiding this comment.
| You can customize some variables from [vars/equinix_metal_vars.yml](vars/equinix_metal_vars.yml). | |
| You can customize the names, sizes, locations, addresses, and other resource variables in [vars/equinix_metal_vars.yml](vars/equinix_metal_vars.yml). |
examples/layer2/main.yml
Outdated
| iface bond0.{{vlan.vxlan}} inet static | ||
| address {{ vrf_gateway_ip_range | ansible.utils.nthhost(2) }} | ||
| netmask {{ vrf_ip_reservation.netmask }} | ||
| post-up route add -net {{ vrf_gateway_ip_range }} gw {{ vrf_ip_reservation.gateway }} |
There was a problem hiding this comment.
I don't know if this makes a difference, but I was comparing to https://deploy.equinix.com/developers/guides/connecting-vlan-to-aws-direct/#test-the-connection and I don't see the gw part there, just the dev.
There was a problem hiding this comment.
The bgp string apparently has some requirements that should be called out.
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: For further information visit https://errors.pydantic.dev/2.9/v/value_error
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Error in metal_virtual_circuit: 1 validation error for VrfVirtualCircuitUpdateInput\nmd5\n Value error, must validate the regular expression /^(?=.*[a-z])(?=.*[A-Z])(?=.*\\d)[a-zA-Z\\d]{10,20}$/ [type=value_error, input_value='taco123', input_type=str]\n For further information visit https://errors.pydantic.dev/2.9/v/value_error"}
|
I know this is related to AWS, so maybe this isn't an issue with our setup, but is just a gotcha for people installing AWS libraries for ansible in general? |
Co-authored-by: Marques Johansson <[email protected]>
Co-authored-by: Marques Johansson <[email protected]>
Co-authored-by: Chris Privitere <[email protected]>
Co-authored-by: Chris Privitere <[email protected]>
| Install the AWS CLI: | ||
|
|
||
| ```bash | ||
| $ apt install -y awscli |
There was a problem hiding this comment.
This could be done via userdata but I think it's a better flow to save the entire AWS CLI setup until the end.
This serves as a working example of deploying a Metal device in hybrid mode in a VRF with a Metal-billed VRF interconnection that connects to a VPC in AWS. This example also creates an S3 VPC endpoint in AWS, and demonstrates that the VPC endpoint can be used from the Metal device for
aws s3commands.Closes #162