Re: Rolling upgrade of multiple servers

Rich Megginson <rmeggins@xxxxxxxxxx> · Thu, 31 Jan 2013 09:08:03 -0700



    On 01/31/2013 08:19 AM, Bright, Daniel wrote:
    
      
        |schema changes made over
            LDAP?  Yes, schema replication is tricky because it is
            "single" master.

            
        When
            you say schema replication is tricky because it is a
            “single” master, I am using an MMR environment where in
            effect every member is a master. Is this a setting that is
            controlled elsewhere, and does this mean that any custom
            changes to the schema need to be made on this single master
            server?
      
    
    Yes.  That's the best way to do it.  If you make schema changes to
    one master, then make sure that all of those schema changes have
    been replicated to all servers throughout your topology, then you
    can make schema changes to another master.  Schema replication is
    not multi-master in the sense that you can make simultaneous changes
    to to the schema on more than one master.  You just have to be
    careful.  That's why using a single master is easier - if you always
    make changes on that one master, it should work.

    
          |User defined attributes are
            attributes that have been added via LDAP (or the console
            which uses LDAP).

            
        I think I just
            answered my own question regarding this issue, according to
            the official documentation I will need to make custom schema
            changes to the 99user.ldif file rather than using ldapmodify
            or the 389-console:
        Custom
              Schema
        If the
            standard
          99user.ldif file is
            used for custom schema, these changes are replicated to all
            consumers.
            
        Custom
            schema files must be copied to each server in order to
            maintain the information in the same schema file on all
            servers. Custom schema files, and changes to those files,
            are not replicated, even if they are made through the
            Directory Server Console or
          ldapmodify.
            
        If there are
            custom schema files, ensure that these files are copied to
            all servers after making changes on the supplier. After all
            of the files have been copied, restart the server. 
        For more information on custom schema files,
            see
            Section 3.4.7,
              “Creating Custom Schema Files”. 
      
    
    That's a little bit misleading.  In order for schema changes to be
    replicated, they _must_ be changed using ldapmodify (which is what
    the console uses).  Schema changes made over ldap are stored in
    99user.ldif.  However, if you manually edit 99user.ldif, schema
    changes will _not_ be replicated.

    
https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Directory_Server/9.0/html/Administration_Guide/Extending_the_Directory_Schema.html#schema-replication

    
      CONFIDENTIALITY NOTICE

          This e-mail and any attachments contain information which may
          be confidential or privileged and exempt from disclosure under
          applicable law.  If you are not the intended recipient, be
          aware that any disclosure, copying, distribution, or use of
          the contents of this information is without authorization and
          is prohibited.  If you have received this email in error,
          please immediately notify us by returning it to the sender and
          delete this copy from your computer system.  Thank you.
      
    
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users