IBM Verify

IBM Verify

Join this online user group to communicate across Security product users and IBM experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

  • 1.  HA hvdb in docker environment

    Posted 06/20/19 04:51 AM
    Hi Community,

    I am wondering how we are supposed to use the hvdb in a docker environment if we want to use it in a highly available setup. Just scaling up won't work as there would be a need for master-master replication, I guess?

    Any change commited to one hvdb instance should become available to the other instance's data too.
    IBM provides a specific docker image for the hvdb (postgres) but I don't see how we are supposed to make it high available.

    Does anybody have any experience with this (or any ideas)?
    Would it be supported to use cockroachdb if there is no other/better way?

    Kind regards,

    ------------------------------
    Kristof Goossens
    ------------------------------


  • 2.  RE: HA hvdb in docker environment

    Posted 06/20/19 05:15 AM
    Edited by Jon Harry 06/20/19 05:16 AM
    Hi Kristof,

    The PostgreSQL and OpenLDAP containers that we supply on Docker Hub are provided as-is, are not supported by IBM , and are only intended as a convenience for testing.  They don't support HA.

    For production, we supply IBM Directory Server and IBM DB2 with the product which can both be set up for HA.  However these don't run under Docker.  The product docs/software compatibility matrix includes details on all of the DBs and LDAP servers we support... but I don't know which of these (if any) support production HA deployment in containers.

    I'm pretty sure cockroachdb is not on support list so you'd be on your own if you used that (so not recommended).

    Jon.

    ------------------------------
    Jon Harry
    Consulting IT Security Specialist
    IBM
    ------------------------------



  • 3.  RE: HA hvdb in docker environment

    Posted 06/20/19 06:19 AM
    Hi John,

    Thanks for your reply.
    We'll discuss internally how we go from here.

    Kristof

    ------------------------------
    Kristof Goossens
    ------------------------------

    Original Message


Related Content