[gsoc-dev] [Mirror Syncing API] Adding slave node's via master API

Pranjal Mittal mittal.pranjal at gmail.com
Wed Jun 25 08:16:14 UTC 2014


Hey Lance/ Ken,

I had a question regarding "Adding Slave Nodes" to the Master node via the
Mirror Syncing API. One way is to manually add the slave nodes to the
master node by specifying the host-names. We can avoid the step by letting
the slave nodes inform the master automatically as soon as they are started.


*1. Advantages of this scheme*

1.1 Less manual work for user (Adding slaves manually in the beginning
avoided)

1.2 Consistency in use  of hostnames/ IP's. Later on when the slave has to
inform the master that it has completed its syncing, it can use the same IP
address it provided while registering with the master. The problem with
manually specifying hostnames is that sometimes we may specify hostname or
sometimes IP addresses and then there is a problem while querying. (Since
queries, are string based and the same field may store either a FQDN
hostname or an IP address)


*2. Issues to consider*

2.1 Slaves need to be aware of master before hand which can be achieved by
having a common MASTER_HOSTNAME setting in settings.py for all nodes in the
architecture

*or*

Providing the master hostname everytime on starting the slave api
(or a provision to adjust it dynamically or override defaults like
MASTER_HOSTNAME setting)


2.2 Master API needs to be started before any of the slave API's for auto
registration of slaves with master.


*Question*

What master-slave awareness scheme would you suggest? Does what I mention
above look like a reasonable scheme and makes sense? I am not sure if I
explained 1.2 properly, we could discuss it in detail on irc today.




Kind Regards,
- Pranjal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osuosl.org/pipermail/gsoc-dev/attachments/20140625/5498e241/attachment.html>


More information about the gsoc-dev mailing list