Confirmed users
927
edits
Services/Sync/Server/ReleaseProcess: Difference between revisions
Jump to navigation
Jump to search
→Open questions
Tarek.ziade (talk | contribs) |
Tarek.ziade (talk | contribs) |
||
| Line 61: | Line 61: | ||
== Open questions == | == Open questions == | ||
What's the strategy to update a node ? Do we want to take it down during the upgrade or do we want to keep it available all the time ? | |||
Ideally, the simplest way would be to have a small app to switch to, that would return X-Weave-Backoff to all requests (or maybe a new header X-Weave-Maintenance) while the real server is being updated. | |||
= Proposal 2 : repository based = | = Proposal 2 : repository based = | ||
XXX see zamboni process (repo based) http://github.com/jbalogh/zamboni-lib/tree/master/packages http://jbalogh.github.com/zamboni/topics/packages/ | XXX see zamboni process (repo based) http://github.com/jbalogh/zamboni-lib/tree/master/packages http://jbalogh.github.com/zamboni/topics/packages/ | ||