Re: Status of PWS 241 upgrade
Nicholas Calugar
Mike
Quick update, not sure if you are running PostgreSQL or MySQL:
The underlying Sequel gem automatically runs migrations in a transaction
for RDBMs that support transactions for DDL statements. This means
PostgreSQL will run the entire migration in a transaction, but MySQL will
not. We are still determining the proper steps to take for MySQL.
Nick
Nicholas Calugar
Product Manager - Cloud Foundry API
Pivotal Software, Inc.
toggle quoted message
Show quoted text
Quick update, not sure if you are running PostgreSQL or MySQL:
The underlying Sequel gem automatically runs migrations in a transaction
for RDBMs that support transactions for DDL statements. This means
PostgreSQL will run the entire migration in a transaction, but MySQL will
not. We are still determining the proper steps to take for MySQL.
Nick
Nicholas Calugar
Product Manager - Cloud Foundry API
Pivotal Software, Inc.
On September 1, 2016 at 12:25:49 PM, Mike Youngstrom (youngm(a)gmail.com)
wrote:
Thanks for the update Nicholas. We'll take that into account.
Mike
On Thu, Sep 1, 2016 at 12:21 PM, Nicholas Calugar <ncalugar(a)pivotal.io>
wrote:
wrote:
Thanks for the update Nicholas. We'll take that into account.
Mike
On Thu, Sep 1, 2016 at 12:21 PM, Nicholas Calugar <ncalugar(a)pivotal.io>
wrote:
Hi Mike,
We have just been made aware of a potential problem with the database
migration to encrypt an app’s specified buildpack at rest. It was known
that it would cause API failures, but we also think it may be unsafe as the
entire migration should have been wrapped in a transaction. We have marked
CF-241 as pre-release and are determining the best path forward.
Thanks,
Nick
Nicholas Calugar
Product Manager - Cloud Foundry API
Pivotal Software, Inc.
On September 1, 2016 at 9:53:29 AM, Amit Gupta (agupta(a)pivotal.io) wrote:
Just hasn't been scheduled yet. No known issues at this time.
Best
Amit
On Thursday, September 1, 2016, Mike Youngstrom <youngm(a)gmail.com> wrote:We're about to begin the process of testing and rolling out 241 to our
environments and I noticed that PWS still hasn't been upgraded to 241 [0].
Is there a particular issue with 241 causing the delay or has it just not
been scheduled yet.
Thanks,
Mike
[0] https://status.run.pivotal.io/