This is not technically a db change that has happened but I use this
tag to get your attention anyway. Burn me please if that is
inappropriate.
As we are bringing out a 4.4.2 I want to move all 441to450
functionality to a set of 442to450 file and add the 441to442 files
from the 4.4 branch. As I
Devs and testers,
I am going to apply a fix by Hugo that deals with an encrypted value that
is to large for the configuration.value field. If you wish to keep running
with your data make sure take appropriate action on this.
On Wed, Sep 24, 2014 at 5:25 PM, wrote:
> Repository: cloudstack
> Upd
he.org/confluence/display/CLOUDSTACK/mail+tags+to+use+to+help+each+other
>
> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Thursday, August 7, 2014 11:29 PM
> To: dev@cloudstack.apache.org
> Cc: Alena Prokharchyk
> Subject: Re: [DB
Prokharchyk
Subject: Re: [DB-CHANGE] Infrastructure tab fails to load with db exception
That is true. It was not my intent to address that problem, though. I was
simply commenting on the question of whether we should continue to use the
[DB-CHANGE] e-mail tag (I believe we should).
On Wed, Aug
That is true. It was not my intent to address that problem, though. I was
simply commenting on the question of whether we should continue to use the
[DB-CHANGE] e-mail tag (I believe we should).
On Wed, Aug 6, 2014 at 10:04 PM, Rajani Karuturi wrote:
> Don’t you think we are overlooking
tkowski >> >
>>> Date: Wednesday, August 6, 2014 at 11:33 AM
>>> To: "dev@cloudstack.apache.org
>>> " <
>>> dev@cloudstack.apache.org
>>> >
>>> Cc: Alena Prokharchyk >> >, Koushik
>>> Das >> >
>>
August 6, 2014 at 11:33 AM
>> To: "dev@cloudstack.apache.org
>> " <
>> dev@cloudstack.apache.org
>> >
>> Cc: Alena Prokharchyk > >, Koushik
>> Das > >
>> Subject: Re: [DB-CHANGE] Infrastructure tab fails to load with db
>> excep
made the changes, still needs to
>>>> provide the instructions on the dev list.
>>>>
>>>> -Alena.
>>>>
>>>> From: Mike Tutkowski >>> >
>>>> Date: Wednesday, August 6, 2014 at 11:33 AM
>>>> To: &
s on the dev list.
>>>
>>> -Alena.
>>>
>>> From: Mike Tutkowski >> >
>>> Date: Wednesday, August 6, 2014 at 11:33 AM
>>> To: "dev@cloudstack.apache.org
>>> " <
>>> dev@cloudstack.apache.org
>>> >
11:33 AM
>> To: "dev@cloudstack.apache.org
>> " <
>> dev@cloudstack.apache.org
>> >
>> Cc: Alena Prokharchyk > >, Koushik
>> Das > >
>> Subject: Re: [DB-CHANGE] Infrastructure tab fails to load with db
>> exception
>>
>>
ke Tutkowski >
> Date: Wednesday, August 6, 2014 at 11:33 AM
> To: "dev@cloudstack.apache.org
> " <
> dev@cloudstack.apache.org
> >
> Cc: Alena Prokharchyk >, Koushik
> Das >
> Subject: Re: [DB-CHANGE] Infrastructure tab fails to load with db
>
t;From: Mike Tutkowski
>mailto:mike.tutkow...@solidfire.com>>
>Date: Wednesday, August 6, 2014 at 11:33 AM
>To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>"
>mailto:dev@cloudstack.apache.org>>
>Cc: Alena Prokharchyk
>mailto:alena.prokhar
rchyk
mailto:alena.prokharc...@citrix.com>>, Koushik
Das mailto:koushik....@citrix.com>>
Subject: Re: [DB-CHANGE] Infrastructure tab fails to load with db exception
What about the details for updating your DB?
If we just receive a general e-mail notification, then each dev will
indepen
gt;Thanks Saksham. This fixed the initial issue. But I noticed a new one,
> >>>after destroying the last VR if you select the infra view it again
> >>>results in exception. Not sure if anything else needs to be fixed.
> >>>
> >>>-Original Message
sults in exception. Not sure if anything else needs to be fixed.
>>>
>>>-----Original Message-
>>>From: Saksham Srivastava [mailto:saksham.srivast...@citrix.com]
>>>Sent: Wednesday, 6 August 2014 3:37 PM
>>>To: dev@cloudstack.apache.org
>>>Sub
ew one,
>>after destroying the last VR if you select the infra view it again
>>results in exception. Not sure if anything else needs to be fixed.
>>
>>-Original Message-
>>From: Saksham Srivastava [mailto:saksham.srivast...@citrix.com]
>>Sent: Wednesday, 6
>From: Saksham Srivastava [mailto:saksham.srivast...@citrix.com]
>Sent: Wednesday, 6 August 2014 3:37 PM
>To: dev@cloudstack.apache.org
>Subject: [DB-CHANGE] Infrastructure tab fails to load with db exception
>
>I remember we used to follow the practice of informing others in
Thanks for sending this out! These can be really helpful.
On Wed, Aug 6, 2014 at 4:06 AM, Saksham Srivastava <
saksham.srivast...@citrix.com> wrote:
> I remember we used to follow the practice of informing others in case db
> changes are committed, but we do not do it anymore.
> In case you are
]
Sent: Wednesday, 6 August 2014 3:37 PM
To: dev@cloudstack.apache.org
Subject: [DB-CHANGE] Infrastructure tab fails to load with db exception
I remember we used to follow the practice of informing others in case db
changes are committed, but we do not do it anymore.
In case you are on dev setup
I remember we used to follow the practice of informing others in case db
changes are committed, but we do not do it anymore.
In case you are on dev setup on master branch post the following commit :
commit b9d834e83854009483f6d061f9996e5ffaa9b883
Author: Nitin Mehta
Date: Tue Aug 5 17:29:34 201
Mike Tutkowski
> mailto:mike.tutkow...@solidfire.com>>
> Date: Tuesday, July 8, 2014 at 9:45 AM
> To: Alena Prokharchyk
> mailto:alena.prokharc...@citrix.com>>
> Cc: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>"
> mailto:dev@cloudstack.apa
he.org>"
mailto:dev@cloudstack.apache.org>>
Subject: Re: [DB-CHANGE]
I think this is what you are asking for:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/mail+tags+to+use+to+help+each+other
On Tue, Jul 8, 2014 at 10:38 AM, Alena Prokharchyk
mailto:alena.prokharc...@citrix
is on the wiki somewhere? It would be
> helpful to gather all the tags in some place central, so we all know what
> to put in the subject for diff kinds of updates/requests.
>
> -alena.
>
> On 7/7/14, 9:11 PM, "Mike Tutkowski" wrote:
>
> >Thanks, Alena!
> >
Alena!
>
>For those of you who may be new to the [DB-CHANGE] tag, the idea, as the
>tag implies, is that a developer has changed the schema of the DB. In an
>effort to help you not to have an issue after fetching his/her change, the
>developer is telling you how you can alter
Thanks, Alena!
For those of you who may be new to the [DB-CHANGE] tag, the idea, as the
tag implies, is that a developer has changed the schema of the DB. In an
effort to help you not to have an issue after fetching his/her change, the
developer is telling you how you can alter your DB so you
Please run these mysql statements after getting commit
5a96d8ef5cbc88df366016ae9dd7ee46e4ca417a on master branch:
ALTER TABLE `cloud`.`user` ADD COLUMN domain_id bigint(20) unsigned DEFAULT
NULL;
ALTER TABLE `cloud`.`user` ADD CONSTRAINT `fk_user__domain_id` FOREIGN KEY
`fk_user__domain_id`(`do
Please update your DB after getting commit
1b83698dac712e3497d4140b15c9fcba3870c705 in master
ALTER TABLE `cloud`.`vm_reservation` ADD COLUMN `deployment_planner`
varchar(40) DEFAULT NULL COMMENT 'Preferred deployment planner for the vm’;
-Alena.
27 matches
Mail list logo
