diff options
| author | micah <micah@riseup.net> | 2014-05-05 12:31:21 -0400 |
|---|---|---|
| committer | micah <micah@riseup.net> | 2014-05-05 12:31:21 -0400 |
| commit | 6615ee0a2e65eded359fbd84aaa5fe81babaeb2b (patch) | |
| tree | fed67da5ce153bbf5d716ffc7b04dc85bbcf06bf | |
| parent | 33fdf642742efe08b6e20d57b07dda39fa6e85d6 (diff) | |
| parent | c48f250df89b961c7a962be0a4dfeac1b42d37f7 (diff) | |
Merge pull request #9 from bruo/master
Updated docs to reflect issues of bug #5601
| -rw-r--r-- | docs/platform/known-issues.md | 7 | ||||
| -rw-r--r-- | docs/platform/quick-start.md | 4 |
2 files changed, 9 insertions, 2 deletions
diff --git a/docs/platform/known-issues.md b/docs/platform/known-issues.md index 46a77de..5bf41a6 100644 --- a/docs/platform/known-issues.md +++ b/docs/platform/known-issues.md @@ -5,6 +5,13 @@ Here you can find documentation about known issues and potential work-arounds in the current Leap Platform release. +0.5.1 +===== +CouchDB Sync +------------ +You can't deploy new couchdb nodes after one or more have been deployed. Make *sure* that you configure and deploy all your couchdb nodes when starting the provider. The problem is that we dont not have a clean way of adding couch nodes after initial creation of the databases, so any nodes added after result in improperly synchronized data. See Bug [#5601](https://leap.se/code/issues/5601) for more information. + + 0.5.0rc1 ======== diff --git a/docs/platform/quick-start.md b/docs/platform/quick-start.md index 80a6c46..e70dca5 100644 --- a/docs/platform/quick-start.md +++ b/docs/platform/quick-start.md @@ -273,8 +273,8 @@ If you prefer, you can initalize each node, one at a time: Deploy the LEAP platform to the nodes -------------------- -Now you should deploy the platform recipes to the nodes. Deployment can take a while to run, especially on the first run, as it needs to update the packages on the new machine. -Note that currently, nodes must be deployed in a certain order. The underlying couch database node(s) must be deployed first, and then all other nodes. +Now you should deploy the platform recipes to the nodes. [Deployment can take a while to run](http://xkcd.com/303/), especially on the first run, as it needs to update the packages on the new machine. +*Important notes:* currently nodes must be deployed in a certain order. The underlying couch database node(s) must be deployed first, and then all other nodes. Also you need to configure and deploy all of the couchdb nodes that you plan to use at this time, as currently you cannot add more of them later later ([See](https://leap.se/es/docs/platform/known-issues#CouchDB.Sync)). $ leap deploy couch1 |