Hi,
Thank you for the suggestions. We have updated the code as per the
suggestions. [1]
There was an error in trying to assign property values directly to a config
class. Thus we have used the approach to set system properties.[2] (line
164)
We highly appreciate your suggestions on the approach
On Mon, Dec 21, 2015 at 1:49 PM, Malmee Weerasinghe wrote:
>
>
>
>
It might be better to change the term "Transformation" to "Transformer" or
something similar. I also do not think "Old Artifact Loader" term is
appropriate. When we say old, how old is this? which version is
Hi All,
This is the component architecture diagram of PPaaS Artifact Migration
Tool.
@ Chamila : Thank you for the suggestions and we will improve the tool as
mentioned.
We highly appreciate your suggestions on this model.
Thank you.
On Fri, Dec 18, 2015 at 1:09 AM, Chamila De Alwis
Hi Malmee,
Great work on the migration tool. AFAIU this is as far as we can go to ease
the migration process for a Stratos user.
Some improvements that can be implemented, IMO, are,
1. Rename bin/run.sh to bin/stratos.sh to conform with the existing pattern
where each separate Stratos component
Hi Malmee,
It would be better if you can draw a component architecture diagram to
illustrate how this tool works.
This might help us to understand how much load it can handle if the
existing Private PaaS 4.0.0 environment has considerable amount of
artifacts and subscriptions and how those can
Hi All,
We are developing a tool to convert PPaaS 4.0.0 artifact JSON files to
PPaaS 4.1.x. [1]
There are changes in the artifacts deployment process in PPaaS 4.0.0
compared to 4.1.0. So this tool is developed for those who need to migrate
from PPaaS 4.0.0 to 4.1.0.
We take the artifacts JSONs
Hi Imesh,
We will include a component architecture diagram of the PPaaS Artifact
Migration Tool.
Thanks.
On Tue, Dec 15, 2015 at 10:53 PM, Imesh Gunaratne wrote:
> Hi Malmee,
>
> It would be better if you can draw a component architecture diagram to
> illustrate how this tool