Hi Chamila,
If the whole PCA is patched there is no way to differentiate whether its a
patch or a new released version, which would not easy to maintain I guess.
In a patch fix, IMO those kind of file removal / refactoring could be very
minimal. We can expect those changes in a version upgrade.
Bu
Hi Sajith,
If we are going to handle each file separately wouldn't it introduce
complications when files are moved and refactored? Wouldn't it be better to
patch the PCA as a whole rather than file by file?
Regards,
Chamila de Alwis
Committer and PMC Member - Apache Stratos
Software Engineer | W
On Sat, Nov 28, 2015 at 11:55 PM, Imesh Gunaratne wrote:
>
>
> On Tue, Nov 24, 2015 at 12:58 PM, Sajith Kariyawasam
> wrote:
>>
>>
>> There are two aspects in here as I see.
>> 1) Applying patches to already running server and restart.
>> 2) Applying patches to a 'fresh' server and start
>>
>>
Hi Sajith,
On Sun, Nov 29, 2015 at 12:13 AM, Chamila De Alwis
wrote:
> Even in that scenario, there is no easy way to track the changes being
>> done to the originally released binary, since the current approach is to
>> replace the old files with patched files.
>> The model I was thinking is to
On Sat, Nov 28, 2015 at 11:55 PM, Imesh Gunaratne wrote:
> Even in that scenario, there is no easy way to track the changes being
> done to the originally released binary, since the current approach is to
> replace the old files with patched files.
> The model I was thinking is to implement a mod
On Tue, Nov 24, 2015 at 12:58 PM, Sajith Kariyawasam
wrote:
>
>
> There are two aspects in here as I see.
> 1) Applying patches to already running server and restart.
> 2) Applying patches to a 'fresh' server and start
>
> It would have been ideal if we can achieve both scenarios above, but yes,
Hi Imesh,
On Sun, Nov 22, 2015 at 10:40 PM, Imesh Gunaratne wrote:
> Hi Sajith,
>
> PCA executes life cycle state events at the startup and it also wait until
> member initiatlized event to start its process. Therefore I do not think we
> can apply patches to PCA and restart.
>
>
There are two a
Hi Sajith,
PCA executes life cycle state events at the startup and it also wait until
member initiatlized event to start its process. Therefore I do not think we
can apply patches to PCA and restart.
Can you please explain the patching process you are proposing?
Thanks
On Wed, Nov 11, 2015 at 6
On Wed, Nov 11, 2015 at 6:07 PM, Sajith Kariyawasam wrote:
> Hi Devs,
>
> At the moment Python Cartridge Agent (PCA) doesn't have a convenient way
> of applying patches.
> If there is an issue identified and fixed, in order to apply the fix to a
> running system that particular file(s) has to be
Hi Devs,
At the moment Python Cartridge Agent (PCA) doesn't have a convenient way of
applying patches.
If there is an issue identified and fixed, in order to apply the fix to a
running system that particular file(s) has to be replaced in the running
system,
and there is no easy way to revert the p
10 matches
Mail list logo
