Cloud VPC mapping to Netbox

[Bernard Van De Walle]

Hi,

I was wondering how other users  manage their AWS, GCP,  Azure IP assignments with Netbox:

I think there are 4 constructs in Netbox that are more or less relevant to Cloud providers: Prefixes, VRF, Sites and Tenants. How do you all use those to represent your VPCs, Subnets etc?

What I have done in the past is to use one VRF per VPC, and adding all the VPC CIDRs and Subnet CIDRs under it.

What is slightly more complex is that you then typically peer some specific subnets from some VPCs together,. So that peering, is effectively another IP Space enforced across VPCs.

In the past  I have used a lot of tags, to enforce some type of logic here.

I also use tags to document which region, cloud, etc that subnet resides in.

How do you all use Netbox for your cloud use-cases? Do you use the concept of tenants and sites in this case?

Thanks.

Bernard

[Jeremy Stretch]

The recommended approach is to model cloud instances as virtual machines and group them using clusters and cluster types. For example, you might have cluster types which represent AWS, GCE, etc. and clusters which represent the regions in which you have instances deployed. Clusters can be further organized using cluster groups if desired.

As far as IP addressing, it may or may not make sense to employ a VRF per cluster or provider: It really depends on your specific setup and how you utilize public vs private IP space.

--
You received this message because you are subscribed to the Google Groups "NetBox" group.
To unsubscribe from this group and stop receiving emails from it, send an email to netbox-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/netbox-discuss/a4cd8426-3a31-4dee-a9b7-e228c12e88ean%40googlegroups.com.

--

Jeremy Stretch
Sr. Network Automation Engineer
Network to Code, LLC

[arno...@googlemail.com]

Hi Bernard,
how did you do it in the end? I'm facing the same "issue". I think the best approach will be VPC = VFR, but would be grateful for your experience. 
  best regards Nils

[Brian Candler]

I coordinate address space between clouds and local systems so that no NAT is required: they can just be directly VPN'd together.  This means I just use a single VRF (the default VRF) for everything.

If you have clouds with overlapping private address space, then a separate VRF per cloud would make sense.