Find the DB schema design iteration 1 with changes suggested and table for tracking repository fork and resource isolation (specially DB,DB user and DB permission template.).
On Thu, Aug 14, 2014 at 9:25 PM, Dimuthu Leelarathne <[email protected]> wrote: > Hi, > > > > On Thu, Aug 14, 2014 at 9:30 AM, Gayan Dhanushka <[email protected]> wrote: > >> Hi Ajanthan, >> >> What about the forrk repository related data. We have builds for forked >> repos and we used to keep them in the rxts? >> > > Mostly, they are all runtime data. > > thanks, > dimuthu > > >> >> Thanks >> GayanD >> >> >> On Thu, Aug 14, 2014 at 9:13 AM, Dimuthu Leelarathne <[email protected]> >> wrote: >> >>> >>> On 14 Aug 2014 09:00, "Manisha Gayathri" <[email protected]> wrote: >>> > >>> > >>> > >>> > >>> > On Thu, Aug 14, 2014 at 3:47 AM, Dimuthu Leelarathne < >>> [email protected]> wrote: >>> >> >>> >> Hi Ajanthan and all, >>> >> >>> >> I see some meta data in these tables. The following are not runtime >>> data, but rather meta data >>> >> >>> >> 1 - app_owner in AF_APP >>> > >>> > Also REPO_ACCESSABILITY in AF_APP too is a meta data. That was to >>> decide whether it is a forked repo/shared main repo. But I am not sure >>> whether this is still being used. >>> > Will check and let you know >>> >>> That is not being used. Lets scrap it. >>> >>> Tx, >>> Dimuthu >>> >>> > >>> >> Following fields in AF_VERSION. >>> >> 2 - stage and promote_status <- and why do we have both >>> >> 4 - auto_build >>> >> 5 - auto_deploy >>> >> >>> >> And also not sure what status in AF_APP is. >>> >> >>> >> @Ramith - History is not runtime data. And we have to rethink about >>> ETA. >>> >> >>> >> thanks, >>> >> dimuthu >>> >> >>> >> >>> >> >>> >> On Wed, Aug 13, 2014 at 9:03 PM, Ajanthan Balachandran < >>> [email protected]> wrote: >>> >>> >>> >>> Hi, >>> >>> We are currently storing all the runtime data such as build >>> id,deployed id ..etc into App Rxt as well App version Rxt.This approach >>> seems to be violating common practice(Storing metadata only into Rxt) and >>> we have experienced some performance implication. >>> >>> Here now we are going to move all the non meta data to a relational >>> database.Following is the initial design of the table structures. >>> >>> >>> >>> >>> >>> Any suggestions/Improvements that can we accommodate ? >>> >>> >>> >>> >>> >>> -- >>> >>> ajanthan >>> >>> -- >>> >>> Ajanthan Balachandiran >>> >>> Senior Software Engineer; >>> >>> Solutions Technologies Team ;WSO2, Inc.; http://wso2.com/ >>> >>> >>> >>> email: [email protected]; cell: +94775581497 >>> >>> blog: http://bkayts.blogspot.com/ >>> >>> >>> >>> Lean . Enterprise . Middleware >>> >> >>> >> >>> >> >>> >> >>> >> -- >>> >> Dimuthu Leelarathne >>> >> Architect & Product Lead of App Factory >>> >> >>> >> WSO2, Inc. (http://wso2.com) >>> >> email: [email protected] >>> >> Mobile : 0773661935 >>> >> >>> >> Lean . Enterprise . Middleware >>> > >>> > >>> > >>> > >>> > -- >>> > ~Regards >>> > Manisha Eleperuma >>> > Software Engineer >>> > WSO2, Inc.: http://wso2.com >>> > lean.enterprise.middleware >>> > >>> > blog: http://manisha-eleperuma.blogspot.com/ >>> > mobile: +94 71 8279777 >>> > >>> >>> >> >> >> -- >> Gayan Dhanuska >> Software Engineer >> http://wso2.com/ >> Lean Enterprise Middleware >> >> Mobile >> 071 666 2327 >> >> Office >> Tel : 94 11 214 5345 >> Fax : 94 11 214 5300 >> >> Twitter : https://twitter.com/gayanlggd >> > > > > -- > Dimuthu Leelarathne > Architect & Product Lead of App Factory > > WSO2, Inc. (http://wso2.com) > email: [email protected] > Mobile : 0773661935 > > Lean . Enterprise . Middleware > -- ajanthan -- Ajanthan Balachandiran Senior Software Engineer; Solutions Technologies Team ;WSO2, Inc.; http://wso2.com/ email: ajanthan <http://goog_595075977>@wso2.com; cell: +94775581497 blog: http://bkayts.blogspot.com/ Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
