thanks Sumit

From:  Sumit Mohanty <[email protected]>
Reply-To:  <[email protected]>
Date:  Wed, 26 Feb 2014 00:26:59 -0800
To:  <[email protected]>
Subject:  Re: UPGRADE

https://issues.apache.org/jira/browse/AMBARI-1425 has the overall design and
all related JIRAs. A number of the commits have since been removed or
commented out as the feature was never used/regression tested.

In any case, we should apply a fresh perspective and focus on upgrades of
the latest stack releases and beyond. Lets open a new JIRA (let me know if
you want to do it) and discuss the design and implementation requirements.

-Sumit


On Tue, Feb 25, 2014 at 12:36 PM, Sumit Mohanty <[email protected]>
wrote:
> We have not thought of that yet. Some of the current design will remain but
> Ambari has support for custom command/action as well as declarative
> application specification now. That allows for some more tools to use during
> upgrade. So we will definitely try to take advantage of that.
> 
> Let me dig up the JIRAs with the details and share them.
> 
> -Sumit
> 
> 
> On Tue, Feb 25, 2014 at 12:26 PM, Aaron Cody <[email protected]> wrote:
>> Will you be finishing the existing implementation or going in a different
>> direction? Can you share any preliminary design docs?
>> thanks
>> 
>> From:  Sumit Mohanty <[email protected]>
>> Reply-To:  <[email protected]>
>> Date:  Tue, 25 Feb 2014 12:03:18 -0800
>> 
>> To:  <[email protected]>
>> Subject:  Re: UPGRADE
>> 
>> We do plan to support automatic upgrade as a feature. At this point, this
>> effort is not scheduled for any specific release yet.
>> 
>> -Sumit
>> 
>> 
>> On Tue, Feb 25, 2014 at 11:41 AM, Aaron Cody <[email protected]> wrote:
>>> ok thanks Sumit - is this a feature you plan to finish or is it now
>>> abandoned for the Œmanual' method?
>>> 
>>> From:  Sumit Mohanty <[email protected]>
>>> Reply-To:  <[email protected]>
>>> Date:  Tue, 25 Feb 2014 11:26:41 -0800
>>> To:  <[email protected]>
>>> Subject:  Re: UPGRADE
>>> 
>>> Hi Aaron,
>>> 
>>> Ambari does not support automatic upgrade of the stack yet. What you see are
>>> remnants of the feature that we started working on but it is not complete.
>>> 
>>> Upgrade, for now, is manual and there are documented steps on how to do it.
>>> 
>>> -Sumit
>>> 
>>> 
>>> On Tue, Feb 25, 2014 at 11:14 AM, Aaron Cody <[email protected]> wrote:
>>>> Hello
>>>> I¹m trying to figure out how upgrade works in Ambari Š I see there is an
>>>> UPGRADE role and various upgrade states in the state machine, but so far I
>>>> haven¹t spotted any information as to how it is supposed to work .. (i¹m
>>>> using 1.2.4) .. is it a work in progress?
>>>> - how do you upgrade from the GUI?
>>>> - how do you upgrade from the REST api?
>>>> 
>>>> thanks
>>>> 
>>> 
>>> 
>>> CONFIDENTIALITY NOTICE
>>> NOTICE: This message is intended for the use of the individual or entity to
>>> which it is addressed and may contain information that is confidential,
>>> privileged and exempt from disclosure under applicable law. If the reader of
>>> this message is not the intended recipient, you are hereby notified that any
>>> printing, copying, dissemination, distribution, disclosure or forwarding of
>>> this communication is strictly prohibited. If you have received this
>>> communication in error, please contact the sender immediately and delete it
>>> from your system. Thank You.
>> 
>> 
>> CONFIDENTIALITY NOTICE
>> NOTICE: This message is intended for the use of the individual or entity to
>> which it is addressed and may contain information that is confidential,
>> privileged and exempt from disclosure under applicable law. If the reader of
>> this message is not the intended recipient, you are hereby notified that any
>> printing, copying, dissemination, distribution, disclosure or forwarding of
>> this communication is strictly prohibited. If you have received this
>> communication in error, please contact the sender immediately and delete it
>> from your system. Thank You.
> 


CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader of
this message is not the intended recipient, you are hereby notified that any
printing, copying, dissemination, distribution, disclosure or forwarding of
this communication is strictly prohibited. If you have received this
communication in error, please contact the sender immediately and delete it
from your system. Thank You.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to