Skip to content
  • Dmitry Shulga's avatar
    c000dcf1
    WL#12720 Add support for network namespaces on setting up listening sockets · c000dcf1
    Dmitry Shulga authored
    
    
    The following changes were done within this worklog:
      * Extended format of a value for the bind-addressi, mysqlx-bind-address and
        admin-address options to allow specifying a network namespace that be used
        for listening incoming connections for corresponding interface addresses.
      * Added handling of network namespace on socket creation and IP address
        to host name resolving.
      * Extended a grammar of the statement CHANGE MASTER TO in order to support
        the clause NETWORK_NAMESPACE=string_value. This clause is used for
        specifying of a network namespace that a replication master uses for
        listening connection requests from a replication slave.
      * Provided storing of a network namespace in the table slave_master_info.
      * The error code ER_WILDCARD_NOT_ALLOWED_FOR_MULTIADDRESS_BIND was added
        to be output in case wildcard value specified for multi address
        --bind-address option value. It was done to be uniform with
        ER_NETWORK_NAMESPACE_NOT_ALLOWED_FOR_WILDCARD_ADDRESS that used for
        similar use case for network namespaces.
      * The error code ER_NETWORK_NAMESPACES_NOT_SUPPORTED was added to report
        error condition when a network namespace is specified on a platform
        that doesn't support network namespace feature.
      * The error code ER_UNKNOWN_NETWORK_NAMESPACE was added to report error
        condition when a specified network namespace is not configured
        on a host
      * The error code ER_SETNS_FAILED was added to report error condition
        that attempt to switch on a some network namespace failed.
    
    Reviewed-by: default avatarThayumanavar Sachithanantham <thayumanavar.x.sachithanantha@oracle.com>
    c000dcf1
    WL#12720 Add support for network namespaces on setting up listening sockets
    Dmitry Shulga authored
    
    
    The following changes were done within this worklog:
      * Extended format of a value for the bind-addressi, mysqlx-bind-address and
        admin-address options to allow specifying a network namespace that be used
        for listening incoming connections for corresponding interface addresses.
      * Added handling of network namespace on socket creation and IP address
        to host name resolving.
      * Extended a grammar of the statement CHANGE MASTER TO in order to support
        the clause NETWORK_NAMESPACE=string_value. This clause is used for
        specifying of a network namespace that a replication master uses for
        listening connection requests from a replication slave.
      * Provided storing of a network namespace in the table slave_master_info.
      * The error code ER_WILDCARD_NOT_ALLOWED_FOR_MULTIADDRESS_BIND was added
        to be output in case wildcard value specified for multi address
        --bind-address option value. It was done to be uniform with
        ER_NETWORK_NAMESPACE_NOT_ALLOWED_FOR_WILDCARD_ADDRESS that used for
        similar use case for network namespaces.
      * The error code ER_NETWORK_NAMESPACES_NOT_SUPPORTED was added to report
        error condition when a network namespace is specified on a platform
        that doesn't support network namespace feature.
      * The error code ER_UNKNOWN_NETWORK_NAMESPACE was added to report error
        condition when a specified network namespace is not configured
        on a host
      * The error code ER_SETNS_FAILED was added to report error condition
        that attempt to switch on a some network namespace failed.
    
    Reviewed-by: default avatarThayumanavar Sachithanantham <thayumanavar.x.sachithanantha@oracle.com>
Loading