On Wed, Jun 24, 2015 at 11:16 AM, Sajith Kariyawasam
wrote:
> +1 for the approach.
>
> Don't we need to consider the domain model for the whole application,
> rather than component-wise? Because, some of the attributes are updated
> from different components.
> In this diagram Cluster object has
Hi Sajith,
Thank you for pointing out. I will consider the domain model for the whole
application once I go ahead with the process and I will update the ER
Models.
Thanks,
On Wed, Jun 24, 2015 at 11:16 AM, Sajith Kariyawasam
wrote:
> +1 for the approach.
>
> Don't we need to consider the dom
Hi Imesh
I'll work on that .
On Wed, Jun 24, 2015 at 11:09 AM, Imesh Gunaratne wrote:
> Thanks for looking into this Jane! May be we can maintain MySQL Workbench
> ER Models in our source repository as it provides features for generating
> SQL scripts.
>
> You should be able to continue this
+1 for the approach.
Don't we need to consider the domain model for the whole application,
rather than component-wise? Because, some of the attributes are updated
from different components.
In this diagram Cluster object has cluster id only
On Wed, Jun 24, 2015 at 11:09 AM, Imesh Gunaratne wrote
Thanks for looking into this Jane! May be we can maintain MySQL Workbench
ER Models in our source repository as it provides features for generating
SQL scripts.
You should be able to continue this effort in a new branch and send pull
requests as you progress. Please note that we also need to updat
Hi ,
In Stratos there are components called StratosManager , CloudController,
AutoScaller which has there own registry and the data stored as serialized
object, which is not an easy way to manage the data.
So after an offline discussion with Imesh we decided to persist the data in
the database a
