Closed mikeshimkus closed 5 years ago
Forgot to add that since traffic-group-1 will be the only traffic group existing at onboard time, specifying a traffic group should cause that group to be created (with default settings) if not already present.
The ability to provide a traffic group for a floating self-ip has been merged into the 'develop' branch, which will get picked up in the next cloud release.
Traffic Groups may be assigned to self-ips with the trafficGroup
option. For example:
--self-ip name:self_4nic,address:10.0.2.7/24,vlan:external,trafficGroup:tg_http
. If the traffic group specified does not already exist, it will be created.
As a note for BigIPs in a device group (such as when using a failover template): the self-ips are created before the BigIPs are clustered, so any floating self-ip and traffic group must be created on the BigIP that the other BigIP(s) will sync from.
This feature was included in version v4.4.0 of f5-cloud-libs. Closing this issue as resolved.
Thanks!
For Azure failover-api and VNFM use cases, we are going to need to ability to create a floating self IP.
The ask is to be able to specify a traffic group during self IP creation.