On 08/18/2014 03:54 AM, Royce Lv wrote:
On 2014年08月16日 03:06, Aline Manera wrote:
> GET /peers
> [
> "https://ubuntu-vm:8001",
> "https://rhel-vm:8001",
> ]
>
> How to test it?
> - Install openslp and openslp-server
> - Start opnslp service: servicd slpd start
> - Make sure to open openSLP port (427 UDP and TCP) on firewall
SLP seems to be a good idea for our scenario, here I have some questions:
1.Do we need a centralized server(slpd) to track service or every host
will have an slpd installed and can handle request?
Every Kimchi server must have an slpd installed to handle the requests.
2.How do we define peers--Even some hosts have kimchi service
enabled,
they are of different hardware/software which prevent them from
migration.
The idea here is only discover Kimchi peers in the same network. Of
course, when we use it for migration we will need to include some
restrictions.
3.Do we support peer discovery between hosts which located distantly
with each other? Will the peer query time consuming?
Kimchi peers are in the same network. So long distant server will not
fill this requirement.
4.What are kimchi peer discovery's use cases:a. migration, b.
browse
other hosts from one access point, c. others?
I can only think about A and B by now.
>
> I tested it using VMs as they are in the same host network.
>
> TODO:
> #1: Add option on Kimchi config file to enable/disable this feature
> #2: Update /config/capabilities to return if federation is enabled or
> not
> GET /config/capabilities
> { ...
> federation: enable|disable
> }
>
> #3: Create README-federation file to provide details on how to enable
> this feature
> #4: Update API.md, mockmodel and test cases
>
> Aline Manera (1):
> Discover Kimchi peers using openSLP
>
> src/kimchi/control/peers.py | 29 ++++++++++++++++++++++++++
> src/kimchi/model/peers.py | 50
> +++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 79 insertions(+)
> create mode 100644 src/kimchi/control/peers.py
> create mode 100644 src/kimchi/model/peers.py
>