Some news

[Thomas Calmant]

Hi,

First, let me wish you a happy new year :)

As you may have noticed, the old documentation wiki of iPOPO is down since November: it is being replaced by a Sphinx documentation on Read the Docs [1].
The main advantage is that the documentation is now part of the Git repository.
The sources of the old wiki are available on the "convert_doc" branch of the Git repository, in the "docs_wiki_src" folder [2].

The conversion process is very slow due to many reasons, mainly because the projects I'm currently working on are not related at all with iPOPO.
That being said, a ZooKeeper-based service discovery provider should be implemented soon, as I'm working a lot with this tool on a Docker-based cluster, and as it seems close enough to Redis (in terms of capabilities and events).

The next version of iPOPO won't be released before the documentation is properly converted and updated.
This can take time: if you think the current state of iPOPO is good enough and should be released as a new version, you can reply to this email telling so.

In other news, I should mentor an internship during summer, if everything goes as planned. This should lead to new features in iPOPO.

Finally, I’ve made a survey [3] to check on what you, iPOPO users and developers, use and want in this framework. It will allow me to have a big picture of the projects iPOPO is used in, and to decide how to prioritize the future features to include in the project.
Please, feel free to answer it, the more answers, the better. All feedback is really appreciated, and I’ll write about the aggregated results on the users’ mailing list, once enough answers will have been received.

[1] https://ipopo.readthedocs.io/
[2] https://github.com/tcalmant/ipopo/tree/convert_doc/docs_wiki_src
[3] https://docs.google.com/forms/d/1zx18_Rg27mjdGrlbtr9fWFmVnZNINo9XCfrYJbr4oJI (no login required)

Cheers,
Thomas

[Darren G]

Can you speak more about the zookeeper-based service discovery provider and how it will work in a distributed setting?

--
Vous recevez ce message, car vous êtes abonné au groupe Google Groupes "ipopo-users".
Pour vous désabonner de ce groupe et ne plus recevoir d'e-mails le concernant, envoyez un e-mail à l'adresse ipopo-users+unsubscribe@googlegroups.com.
Pour obtenir davantage d'options, consultez la page https://groups.google.com/d/optout.

[Thomas Calmant]

Hi,

The ZooKeeper based service discovery should work as the Redis discovery:

- each framework will add an entry with its hostname as value

- each endpoint description will be stored as an entry, with its description in EDEF (XML) format as value

- key events and ephemeral keys will be used to detect the arrival, departure and loss of frameworks and endpoins.

As a result, iPOPO frameworks will connect to a ZooKeeper cluster (using the ZooKeeper connection URL string to indicate multiple servers) to write its information.

This is useful mainly in the case of networks which doesn't support multicast (e.g. Docker Swarm networks) or traversing routers (NAT, ...).

Like the Redis discovery protocol, this mechanism won't depend on the transport implementation, so it will work with XML-RPC, JSON-RPC, etc.

Cheers,

Thomas

Pour vous désabonner de ce groupe et ne plus recevoir d'e-mails le concernant, envoyez un e-mail à l'adresse ipopo-users...@googlegroups.com.

Pour obtenir davantage d'options, consultez la page https://groups.google.com/d/optout.

--
Vous recevez ce message, car vous êtes abonné au groupe Google Groupes "ipopo-dev".
Pour vous désabonner de ce groupe et ne plus recevoir d'e-mails le concernant, envoyez un e-mail à l'adresse ipopo-dev+...@googlegroups.com.