Description
Is there an existing issue for this?
- There is no existing issue for this feature
What are you currently unable to do
We could have a few physical Networks for different purposes, we could could have the following options:
a) physical Network for VPCs where the OVN Logical Router uplink uses CGNAT addresses (100.64.0.0/10)
b) physical Network for VPCs where the OVN Logical Router uplink uses Public IP v4 addresses
For instances without a Network Forward, it will access the Internet using the SNAT rule created in the OVN Logical Router.
When using option a), the user traffic will egress the OVN Logical Router and will be redirect to a CGNAT solution where it shares a Pool of Public IP v4 addresses with many users.
For option b), the user has its own Public IP v4 address to be shared for many instances inside its VPC without a Network Forward.
What do you think would need to be added
An user could ask for the CMS to create its VPCs and be attached into the physical Network described in the option a), its OVN Logical Router uplink will get an IP address from 100.64.0.0/10, the user will create instances and attach Network Forwards.
Later the same user can ask to move its VPCs to the physical Network explained in option b) where the OVN Logical Router uplink will get an dedicated Public IP v4 address.
The same situation could happen in the inverse way, from b) to be moved to a).
In both cases, it will be necessary to keep the Network Forwards configured, while the migration is happening probably a few packets will be lost.
Tiago Pires