Future Changes to API Features

This section describes elements in the data service API for Sun Cluster 2.2 that might change or might not be available in releases following Sun Cluster 2.2.

Changes to API Commands or Command Options

The following API commands and command options might change in future Sun Cluster releases.

• Some fields in structures returned from ha_get_calls(3HA) functions will be NULL.

  • ha_get_calls returning names_on_subnets in an ha_network_host_t structure contained in an ha_physical_host_t structure:

    typedef struct ha_network_host { char *node_name; char **names_on_subnets ; } ha_network_host_t ;

    The names_on_subnets field will be NULL.

  • ha_get_calls returning ha_logical_host_t structure:

    typedef struct ha_logical_host { ha_network_host_t neth; ha_physical_host_t **physical_hosts char *pathprefix` char *vfstab_file } ha_logical_host_t;

    The vfstab_file field will be NULL.

• The ha_getonoff(1M) function of ha_get_calls(3HA) will change and will always return TRUE.

  ha_getonoff(han_handle_t handle, char *service_name, boolean_t *ison);

API Commands or Command Options That Might Become Obsolete

The following commands and command options might not be available in future Sun Cluster releases.

• haget(1M) query on names_on_subnets

  # haget -f names_on_subnets -h physical_host

• haget(1M) query on vfstab_file

  # haget -f vfstab_file -h logical_hostname

• -r reconfiguration option to hactl(1M)

  hactl -r ...

• The cluster reconfiguration process described in the hareg(1M) man page might change in future releases. The reconfiguration process might no longer be a lock step process. You should not develop highly available data services that depend on the steps occurring in lock step.