You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2019/01/01 22:46:00 UTC
[jira] [Updated] (RATIS-372) Basic test harness for LogService
[ https://issues.apache.org/jira/browse/RATIS-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Elser updated RATIS-372:
-----------------------------
Attachment: RATIS-372.001.patch
> Basic test harness for LogService
> ---------------------------------
>
> Key: RATIS-372
> URL: https://issues.apache.org/jira/browse/RATIS-372
> Project: Ratis
> Issue Type: Task
> Components: LogService
> Reporter: Josh Elser
> Assignee: Rajeshbabu Chintaguntla
> Priority: Major
> Attachments: RATIS-372.001.patch, RATIS-372_wip.patch
>
>
> We should have something that can stand up a logservice in a pseudo-distributed manner.
> Docker is all the rage right now, and would make it easy to deploy onto something like k8s in the future.
> Using [docker-compose|https://docs.docker.com/compose/] would provide us a nice way to have one docker image for the metadata service daemons, another for logservice daemons (if needed), and then create a network that connects them all together. The final docker-compose yaml would be something like:
> It would be nice to provide a "client" container in which we show a basic create/write/read/delete example to give folks a starting point.
> * 1 network
> * 3 instances of metadata service statemachines
> * 3 instances of log service statemachines
> * 1 image with the example client.
> [~chrajeshbabu32@gmail.com], make sense to you?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)