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
> -Alena.
> >>
> >> From: Mike Tutkowski >> >
> >> Date: Wednesday, August 6, 2014 at 11:33 AM
> >> To: "dev@cloudstack.apache.org
> >> " <
> >> dev@cloudstack.apache.org
> >> >
> >> Cc: Alena Prokharchyk
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
What about the details for updating your DB?
If we just receive a general e-mail notification, then each dev will
independently have to examine the DB changes to come up with a workaround
to keep his/her current env running properly after a code update.
On Wednesday, August 6, 2014, Nitin Mehta
Agreed. Added that information in the bug.
On 06/08/14 11:08 AM, "Alena Prokharchyk"
wrote:
>Thank you, Nitin. I think we should add one more item to the things that
>the script checks: modifications to the older upgrade paths shouldn¹t be
>allowed. If we already released 4.4, db upgrade changes
Thank you, Nitin. I think we should add one more item to the things that
the script checks: modifications to the older upgrade paths shouldn¹t be
allowed. If we already released 4.4, db upgrade changes should be accepted
only to 4.4-4.5 scripts. If someone makes the changes to, say 4.3-4.4, the
mai
This should be automated. We can't rely on the good intentions of dev.
All we need is a script which checks changes in the schema/java Upgrade
files and to sends a notification to the dev list.
Filed a bug for this -
https://issues.apache.org/jira/browse/CLOUDSTACK-7273
Thanks,
-Nitin
On 06/08/1
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
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-
From: Saksham Srivastava [mailto:saksham.srivast...@citrix.com]
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
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 <
alena.prokharc...@citrix.com> wrote:
> Thank you, Mike!
>
> Do you know if this information is on the wiki som
Thank you, Mike!
Do you know if this information 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!
>
>For
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 don'
22 matches
Mail list logo
