You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a bug. We typically dont put the admin_vip in the admin subnet, because we don't want any openstack traffic on that network. However, there is no reason to consume 2 IPs on the private network. We could just set admin_vip and private_vip to be the same IP. There is an issue open to fix this: #10
After running the deploy.sh script, the VIP are configured and pasted into opnfv_ksgen_settings.yml
I have three networks:
I noticed that the VIP are being created in the private and public VLANs only. Is this correct?
The text was updated successfully, but these errors were encountered: