Date
1 - 4 of 4
updating microbosh question
|
Long Nguyen
Is it intended when updating microbosh that currently running deploys are just killed? Will it resume after microbosh is updated?
|
|
|
|
Dmitriy Kalinin
I do not believe director currently waits for deploys to finish.
toggle quoted message
Show quoted text
Sent from my iPhone On Jul 20, 2015, at 8:35 AM, Long Nguyen <long.nguyen11288(a)gmail.com> wrote: |
|
|
|
Dr Nic Williams
Is that good? Something to fix/improve? Or should automation wanting to do deploys poll the /tasks API until there are no active tasks and then resume destruction?
On Mon, Jul 20, 2015 at 8:35 AM, Long Nguyen <long.nguyen11288(a)gmail.com> wrote: Is it intended when updating microbosh that currently running deploys are just killed? Will it resume after microbosh is updated? |
|
|
|
Long Nguyen
Hmm should director do this? Seems kinda scary that it just doesn’t care about deploys and updates
toggle quoted message
Show quoted text
On July 20, 2015 at 5:38:39 PM, Dmitriy Kalinin (dkalinin(a)pivotal.io) wrote:
I do not believe director currently waits for deploys to finish. Sent from my iPhone On Jul 20, 2015, at 8:35 AM, Long Nguyen <long.nguyen11288(a)gmail.com> wrote: Is it intended when updating microbosh that currently running deploys are just killed? Will it resume after microbosh is updated? _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh |
|
|