Document current container upgrades best practices #48

Open
opened 2021-03-05 12:39:26 +00:00 by kawaiipunk · 2 comments
Owner

Some thoughts to shape outcomes:

  • Do we run manually abra deploy commands at regular intervals?
  • What's the best way to schedule this automatically?
  • What happens if an upgrade fails?
  • How do we know if there's an upstream upgrade?
Some thoughts to shape outcomes: - Do we run manually abra deploy commands at regular intervals? - What's the best way to schedule this automatically? - What happens if an upgrade fails? - How do we know if there's an upstream upgrade?
kawaiipunk added the
enhancement
documentation
labels 2021-03-05 12:39:26 +00:00
Owner

Good that you raised this! I think this is a good problem to have because we're actually dogfooding this co-op cloud thing and arriving at this need. At the same time, we've been barging away at versioning handling in abra over at https://git.autonomic.zone/coop-cloud/abra/src/branch/main/CHANGELOG.md#abra-x-x-x-unreleased and there is still lots of work to do. I will use this ticket as a diving board for more work in abra and in the docs.

I think right now, we're just doing this stuff manually, so we should try to put down a fixed time for doing that.

Good that you raised this! I think this is a good problem to have because we're actually dogfooding this co-op cloud thing and arriving at this need. At the same time, we've been barging away at versioning handling in `abra` over at https://git.autonomic.zone/coop-cloud/abra/src/branch/main/CHANGELOG.md#abra-x-x-x-unreleased and there is still lots of work to do. I will use this ticket as a diving board for more work in `abra` and in the docs. I think right now, we're just doing this stuff manually, so we should try to put down a fixed time for doing that.
Owner
> https://git.autonomic.zone/coop-cloud/abra/issues/90
This repo is archived. You cannot comment on issues.
No description provided.