Hide Forgot
Description of problem: The predictable IP address documentation could use the following improvements: * Mention that the IP addresses chosen must be outside the AllocationPool for the VIPs when not using external load balancer. * Link to the external load balancer document, since people who are selecting IP addresses may also wish to select the VIP IP addresses (they don't need an external load balancer to use those templates to preselect a VIP). Version-Release number of selected component (if applicable): 8.0 GA Actual results: These things aren't mentioned Expected results: Some people expect that OSP-Director is smart enough to avoid IP conflicts. It's not, so we should warn users. Additional info: Documentation URL that needs to be updated: https://access.redhat.com/documentation/en/red-hat-openstack-platform/version-8/director-installation-and-usage/#sect-Predictable_IPs
Hi Dan, I added a paragraph to that section: Make sure the chosen IP addresses fall outside the allocation pools for each network defined in your network environment file (see Section 6.2.2, “Creating a Network Environment File”). For example, make sure the internal_api assignments fall outside of the InternalApiAllocationPools range. This avoids any conflicts with the VIPs chosen for each network. Likewise, make sure the IP assignments do not conflict with the VIP configuration defined for external load balancing (see Section 6.5, “Configuring External Load Balancing”). https://access.redhat.com/documentation/en/red-hat-openstack-platform/version-8/director-installation-and-usage/#sect-Predictable_IPs Was this what you were after? Let me know if anything else is needed.
No response in over a month. Closing this BZ. However, if further changes are required, please feel free to reopen this BZ.
Hi Dan, We need to also append to the docs how to assign static IPs for the VIPs. In addition to the existing ips-from-pool-all.yaml something like this should be added: resource_registry: # Port assignments for the VIPs OS::TripleO::Network::Ports::NetVipMap: ../network/ports/net_vip_map_external.yaml OS::TripleO::Network::Ports::ExternalVipPort: ../network/ports/noop.yaml OS::TripleO::Network::Ports::InternalApiVipPort: ../network/ports/noop.yaml OS::TripleO::Network::Ports::StorageVipPort: ../network/ports/noop.yaml OS::TripleO::Network::Ports::StorageMgmtVipPort: ../network/ports/noop.yaml OS::TripleO::Network::Ports::RedisVipPort: ../network/ports/from_service.yaml ... parameter_defaults: ControlPlaneIP: 192.168.200.100 ExternalNetworkVip: 192.168.225.100 InternalApiNetworkVip: 192.168.221.100 StorageNetworkVip: 192.168.223.100 StorageMgmtNetworkVip: 192.168.224.100 ServiceVips: redis: 192.168.221.101
(In reply to Marius Cornea from comment #4) > Hi Dan, > > We need to also append to the docs how to assign static IPs for the VIPs. In > addition to the existing ips-from-pool-all.yaml something like this should > be added: Thanks for the suggestion. We already have the external loadbalancer template, but that is used to select the controller IPs as well as the VIPs. You want to just set the IP on the VIPs. I suppose we could add another environment file example that only set the VIPs. I'll submit a review. In the mean time I added content to the network reference architecture. This might be worth documenting in the official installation guide, so I'll make sure that the docs group is aware of my documentation.
Marius, Dan, I'll close this BZ as a duplicate but copy you both as CCs on the other BZ. - Dan *** This bug has been marked as a duplicate of bug 1348859 ***