Summary of changes:
- applyLoadBalancerConfig(long lbRuleId) method applies only one rule if it is Netscalar otherwise applies all the rules in add/revoke state.
API docs. Uses XML/XSLT generation system originally by Abhinandan Prateek
(I think). CSS updates from Jessica Tomechak. gen_toc.py and build script
changes by me.
Changes:
To migrate systems using 'use.user.concentrated.pod.allocation' as true and 'vm.allocation.algorithm' as true, we need to
add following changes:
- There will be 5 values to 'vm.allocation.algorithm': 'random', 'firstfit', 'userdispersing', 'userconcentratedpod_random', 'userconcentratedpod_firstfit'
- 'userconcentratedpod_random' means we apply user concentration to pods and clusters. To hosts and pools we use random ordering.
- 'userconcentratedpod_firstfit' means we apply user concentration to pods and clusters. To hosts and pools we use firstfit ordering.
CIDR may be different after update to a service offering contained external
network element, user is required to acknowledge this, otherwise the update
won't process
-Use new API param 'listtopused' to get all capacities
-As new API includes pod, cluster-level capacities, restore display of pod and cluster names on capacity label
-Increase page size to 8, to fit into UI better
- converted all mandatory params to optional, and internally fill with default value before sending to haproxy. default value is available through description.
- accept holdtime without units.
Changes:
- We do not need these global setting anymore. These will be hidden since 3.0
- The default traffic label will be picked from the global setting which is null by default. When traffic label is null it means the resource uses tag on the default gateway
- Changes to invoke discoverer to reload the resource object on host connection
- Since a zone can have many physical networks, there can be multiple guest, public networks. Only the zone wide storage and management traffic label will be stored in host_details henceforth.
- If traffic labels are updated, discoverer should update the host_details
Remove actions column from 'Review' users list view -- this was having
buggy behavior due to widget limitations. User can still add/remove
afterwards by going to project detail view.
Use new API call to list capacities, ordered by usage and limited to
the top 5 capacites.
--Note that, due to API limitations, the UI cannot display what
particular pod/cluster the capacity belongs to anymore, as that
information is not returned in the response. This can be added again
if relevant API changes are made.
Naredula Janardhana Reddy
Ewan Mellor
Jessica Wang
prachi
frank
Sheng Yang
Sam Robertson
Alena Prokharchyk
bfederle
Nitin Mehta
kishan
Murali reddy
abhi