You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Isuru Haththotuwa <is...@wso2.com> on 2013/10/16 11:31:02 UTC
Re-Designing the Database Schema for Stratos Manager (SM)
Hi Devs,
For $subject I came across the following initial database design. The
intention of this database is to persist the details for a cartridge
subscription. Please share your thoughts.
[image: Inline image 1]
--
Thanks and Regards,
Isuru H.
Software Engineer, WSO2 Inc.
+94 716 358 048* <http://wso2.com/>*
Re: Re-Designing the Database Schema for Stratos Manager (SM)
Posted by Isuru Haththotuwa <is...@wso2.com>.
Hi Imesh,
Thanks a lot for the input. I agree.
I will be sending an updated version of the relational DB design along with
the ER diagram to the thread ASAP. Will address the issues you pointed out
there and some other issues I discovered with the help of Nirmal.
On Wed, Oct 16, 2013 at 11:16 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Hi Isuru,
>
> Great work!
>
> IMO the term "INFORMATION" is not commonly used on table names. I would
> prefer CLUSTER_INFORMATION table to be called CLUSTER and
> DATA_CARTRIDGE_INFORMATION table to be called DATA_CARTRIDGE.
>
> WDYT?
>
> Thanks
> Imesh
>
>
> On Wed, Oct 16, 2013 at 4:34 PM, Isuru Perera <is...@wso2.com> wrote:
>
>>
>>
>>
>> On Wed, Oct 16, 2013 at 4:24 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>>
>>>
>>>
>>>
>>> On Wed, Oct 16, 2013 at 3:30 PM, Isuru Perera <is...@wso2.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> Could you please elaborate more on the entities. We had previously
>>>> stored the Cartridge instance state in the database and now I do not see it
>>>> here. Refer slide 14 at [1] for the database schema of Apache Stratos
>>>> (incubating) version 3.0.0. How are we going to maintain cartridge instance
>>>> status?
>>>>
>>>> We also had a Cartridge Subscription entity, which stored the
>>>> subscription details and Cartridge instance entity actually stored the
>>>> details of running cartridge instances.
>>>>
>>>> This new schema has lot of changes and therefore I think it's better to
>>>> include details of every design decision.
>>>>
>>>
>>> Exactly, I also felt there're gaps. I met IsuruH and had a chat. He will
>>> send a revised version.
>>>
>> That's great!
>>
>> Thanks!
>>
>>>
>>>> Thanks!
>>>>
>>>> [1]
>>>> http://www.slideshare.net/chrishantha/apache-stratos-incubating-hangout-iv-stratos-controller-and-cli-internals
>>>>
>>>>
>>>> On Wed, Oct 16, 2013 at 3:01 PM, Isuru Haththotuwa <is...@wso2.com>wrote:
>>>>
>>>>> Hi Devs,
>>>>>
>>>>> For $subject I came across the following initial database design. The
>>>>> intention of this database is to persist the details for a cartridge
>>>>> subscription. Please share your thoughts.
>>>>>
>>>>> [image: Inline image 1]
>>>>>
>>>>> --
>>>>> Thanks and Regards,
>>>>>
>>>>> Isuru H.
>>>>> Software Engineer, WSO2 Inc.
>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Isuru Perera
>>>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>>>> Lean . Enterprise . Middleware
>>>>
>>>> about.me/chrishantha
>>>>
>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> Nirmal
>>>
>>> Nirmal Fernando.
>>> PPMC Member & Committer of Apache Stratos,
>>> Senior Software Engineer, WSO2 Inc.
>>>
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>
>>
>>
>> --
>> Isuru Perera
>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>> Lean . Enterprise . Middleware
>>
>> about.me/chrishantha
>>
>
>
--
Thanks and Regards,
Isuru H.
Software Engineer, WSO2 Inc.
+94 716 358 048* <http://wso2.com/>*
Re: Re-Designing the Database Schema for Stratos Manager (SM)
Posted by Isuru Haththotuwa <is...@wso2.com>.
I have attached the modified DB schema [1] along with the ER diagram [2].
Please note that this design doesn't include the aspect of cartridge
instance grouping/connecting. We should do some research on the CAMP spec
[3] for supporting this grouping aspect.
[1].
[image: Inline image 1]
[2].
[image: Inline image 3]
[3]. https://www.oasis-open.org/committees/download.php/47278/CAMP-v1.0.pdf
On Thu, Oct 17, 2013 at 10:31 AM, Isuru Haththotuwa <is...@wso2.com> wrote:
> On Thu, Oct 17, 2013 at 10:22 AM, Nirmal Fernando <ni...@gmail.com>wrote:
>
>>
>>
>>
>> On Thu, Oct 17, 2013 at 12:01 AM, Prabath Abeysekara <
>> prabathabeysekara@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> You all might already be aware of this but just thought it would be
>>> worth mentioning that you need to be a bit careful when choosing
>>> identifiers to be used as table/column names, etc as different database
>>> vendors impose different restrictions on parameters like identifier length,
>>> etc. IIRC, out of all RDBMS types that are commonly in use, Oracle allows
>>> the lowest max_table_name_character_length (30) and the rest of the types
>>> such as MySQL, SQL Server, Postgres, etc allows you to have slightly
>>> lengthier identifier names.
>>>
>>> Therefore, I believe it is good to make the identifier names as short as
>>> possible while preserving their intuitiveness and meaning as well as
>>> consistency. Consistency would also be an important factor as, for example,
>>> shortening a particular table name to be something like
>>> "DATA_CARTRIDGE_SOMETHING_ELSE_*INFO*" (to be compatible with
>>> identifier length restrictions) later while having another table in the
>>> schema which carries the name "DATA_CARTRIDGE_*INFORMATION*", would not
>>> make it look too clean.
>>>
>>
>> +1, thanks Prabath for the input. IsuruH please note.
>>
>>
>>> These are very small stuff but thought would be important if by any
>>> chance this was not taken into consideration. :)
>>>
>>
> +1, and many thanks for the input. Will take this into consideration and
> redo the design.
>
>>
>>>
>>> Cheers,
>>> Prabath
>>>
>>>
>>> On Wed, Oct 16, 2013 at 11:16 PM, Imesh Gunaratne <im...@apache.org>wrote:
>>>
>>>> Hi Isuru,
>>>>
>>>> Great work!
>>>>
>>>> IMO the term "INFORMATION" is not commonly used on table names. I would
>>>> prefer CLUSTER_INFORMATION table to be called CLUSTER and
>>>> DATA_CARTRIDGE_INFORMATION table to be called DATA_CARTRIDGE.
>>>>
>>>> WDYT?
>>>>
>>>> Thanks
>>>> Imesh
>>>>
>>>>
>>>> On Wed, Oct 16, 2013 at 4:34 PM, Isuru Perera <is...@wso2.com> wrote:
>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Oct 16, 2013 at 4:24 PM, Nirmal Fernando <
>>>>> nirmal070125@gmail.com> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Oct 16, 2013 at 3:30 PM, Isuru Perera <is...@wso2.com>wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> Could you please elaborate more on the entities. We had previously
>>>>>>> stored the Cartridge instance state in the database and now I do not see it
>>>>>>> here. Refer slide 14 at [1] for the database schema of Apache Stratos
>>>>>>> (incubating) version 3.0.0. How are we going to maintain cartridge instance
>>>>>>> status?
>>>>>>>
>>>>>>> We also had a Cartridge Subscription entity, which stored the
>>>>>>> subscription details and Cartridge instance entity actually stored the
>>>>>>> details of running cartridge instances.
>>>>>>>
>>>>>>> This new schema has lot of changes and therefore I think it's better
>>>>>>> to include details of every design decision.
>>>>>>>
>>>>>>
>>>>>> Exactly, I also felt there're gaps. I met IsuruH and had a chat. He
>>>>>> will send a revised version.
>>>>>>
>>>>> That's great!
>>>>>
>>>>> Thanks!
>>>>>
>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>> [1]
>>>>>>> http://www.slideshare.net/chrishantha/apache-stratos-incubating-hangout-iv-stratos-controller-and-cli-internals
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Oct 16, 2013 at 3:01 PM, Isuru Haththotuwa <is...@wso2.com>wrote:
>>>>>>>
>>>>>>>> Hi Devs,
>>>>>>>>
>>>>>>>> For $subject I came across the following initial database design.
>>>>>>>> The intention of this database is to persist the details for a cartridge
>>>>>>>> subscription. Please share your thoughts.
>>>>>>>>
>>>>>>>> [image: Inline image 1]
>>>>>>>>
>>>>>>>> --
>>>>>>>> Thanks and Regards,
>>>>>>>>
>>>>>>>> Isuru H.
>>>>>>>> Software Engineer, WSO2 Inc.
>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Isuru Perera
>>>>>>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>>>>>>> Lean . Enterprise . Middleware
>>>>>>>
>>>>>>> about.me/chrishantha
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Best Regards,
>>>>>> Nirmal
>>>>>>
>>>>>> Nirmal Fernando.
>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>
>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Isuru Perera
>>>>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>>>>> Lean . Enterprise . Middleware
>>>>>
>>>>> about.me/chrishantha
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Prabath
>>>
>>
>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>>
>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> Software Engineer, WSO2 Inc.
> +94 716 358 048* <http://wso2.com/>*
>
>
>
--
Thanks and Regards,
Isuru H.
Software Engineer, WSO2 Inc.
+94 716 358 048* <http://wso2.com/>*
Re: Re-Designing the Database Schema for Stratos Manager (SM)
Posted by Isuru Haththotuwa <is...@wso2.com>.
On Thu, Oct 17, 2013 at 10:22 AM, Nirmal Fernando <ni...@gmail.com>wrote:
>
>
>
> On Thu, Oct 17, 2013 at 12:01 AM, Prabath Abeysekara <
> prabathabeysekara@gmail.com> wrote:
>
>> Hi,
>>
>> You all might already be aware of this but just thought it would be worth
>> mentioning that you need to be a bit careful when choosing identifiers to
>> be used as table/column names, etc as different database vendors impose
>> different restrictions on parameters like identifier length, etc. IIRC, out
>> of all RDBMS types that are commonly in use, Oracle allows the lowest
>> max_table_name_character_length (30) and the rest of the types such as
>> MySQL, SQL Server, Postgres, etc allows you to have slightly lengthier
>> identifier names.
>>
>> Therefore, I believe it is good to make the identifier names as short as
>> possible while preserving their intuitiveness and meaning as well as
>> consistency. Consistency would also be an important factor as, for example,
>> shortening a particular table name to be something like
>> "DATA_CARTRIDGE_SOMETHING_ELSE_*INFO*" (to be compatible with identifier
>> length restrictions) later while having another table in the schema which
>> carries the name "DATA_CARTRIDGE_*INFORMATION*", would not make it look
>> too clean.
>>
>
> +1, thanks Prabath for the input. IsuruH please note.
>
>
>> These are very small stuff but thought would be important if by any
>> chance this was not taken into consideration. :)
>>
>
+1, and many thanks for the input. Will take this into consideration and
redo the design.
>
>>
>> Cheers,
>> Prabath
>>
>>
>> On Wed, Oct 16, 2013 at 11:16 PM, Imesh Gunaratne <im...@apache.org>wrote:
>>
>>> Hi Isuru,
>>>
>>> Great work!
>>>
>>> IMO the term "INFORMATION" is not commonly used on table names. I would
>>> prefer CLUSTER_INFORMATION table to be called CLUSTER and
>>> DATA_CARTRIDGE_INFORMATION table to be called DATA_CARTRIDGE.
>>>
>>> WDYT?
>>>
>>> Thanks
>>> Imesh
>>>
>>>
>>> On Wed, Oct 16, 2013 at 4:34 PM, Isuru Perera <is...@wso2.com> wrote:
>>>
>>>>
>>>>
>>>>
>>>> On Wed, Oct 16, 2013 at 4:24 PM, Nirmal Fernando <
>>>> nirmal070125@gmail.com> wrote:
>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Oct 16, 2013 at 3:30 PM, Isuru Perera <is...@wso2.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Could you please elaborate more on the entities. We had previously
>>>>>> stored the Cartridge instance state in the database and now I do not see it
>>>>>> here. Refer slide 14 at [1] for the database schema of Apache Stratos
>>>>>> (incubating) version 3.0.0. How are we going to maintain cartridge instance
>>>>>> status?
>>>>>>
>>>>>> We also had a Cartridge Subscription entity, which stored the
>>>>>> subscription details and Cartridge instance entity actually stored the
>>>>>> details of running cartridge instances.
>>>>>>
>>>>>> This new schema has lot of changes and therefore I think it's better
>>>>>> to include details of every design decision.
>>>>>>
>>>>>
>>>>> Exactly, I also felt there're gaps. I met IsuruH and had a chat. He
>>>>> will send a revised version.
>>>>>
>>>> That's great!
>>>>
>>>> Thanks!
>>>>
>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> [1]
>>>>>> http://www.slideshare.net/chrishantha/apache-stratos-incubating-hangout-iv-stratos-controller-and-cli-internals
>>>>>>
>>>>>>
>>>>>> On Wed, Oct 16, 2013 at 3:01 PM, Isuru Haththotuwa <is...@wso2.com>wrote:
>>>>>>
>>>>>>> Hi Devs,
>>>>>>>
>>>>>>> For $subject I came across the following initial database design.
>>>>>>> The intention of this database is to persist the details for a cartridge
>>>>>>> subscription. Please share your thoughts.
>>>>>>>
>>>>>>> [image: Inline image 1]
>>>>>>>
>>>>>>> --
>>>>>>> Thanks and Regards,
>>>>>>>
>>>>>>> Isuru H.
>>>>>>> Software Engineer, WSO2 Inc.
>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Isuru Perera
>>>>>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>>>>>> Lean . Enterprise . Middleware
>>>>>>
>>>>>> about.me/chrishantha
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>> Nirmal
>>>>>
>>>>> Nirmal Fernando.
>>>>> PPMC Member & Committer of Apache Stratos,
>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>
>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Isuru Perera
>>>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>>>> Lean . Enterprise . Middleware
>>>>
>>>> about.me/chrishantha
>>>>
>>>
>>>
>>
>>
>> --
>> Prabath
>>
>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
--
Thanks and Regards,
Isuru H.
Software Engineer, WSO2 Inc.
+94 716 358 048* <http://wso2.com/>*
Re: Re-Designing the Database Schema for Stratos Manager (SM)
Posted by Nirmal Fernando <ni...@gmail.com>.
On Thu, Oct 17, 2013 at 12:01 AM, Prabath Abeysekara <
prabathabeysekara@gmail.com> wrote:
> Hi,
>
> You all might already be aware of this but just thought it would be worth
> mentioning that you need to be a bit careful when choosing identifiers to
> be used as table/column names, etc as different database vendors impose
> different restrictions on parameters like identifier length, etc. IIRC, out
> of all RDBMS types that are commonly in use, Oracle allows the lowest
> max_table_name_character_length (30) and the rest of the types such as
> MySQL, SQL Server, Postgres, etc allows you to have slightly lengthier
> identifier names.
>
> Therefore, I believe it is good to make the identifier names as short as
> possible while preserving their intuitiveness and meaning as well as
> consistency. Consistency would also be an important factor as, for example,
> shortening a particular table name to be something like
> "DATA_CARTRIDGE_SOMETHING_ELSE_*INFO*" (to be compatible with identifier
> length restrictions) later while having another table in the schema which
> carries the name "DATA_CARTRIDGE_*INFORMATION*", would not make it look
> too clean.
>
+1, thanks Prabath for the input. IsuruH please note.
> These are very small stuff but thought would be important if by any chance
> this was not taken into consideration. :)
>
>
> Cheers,
> Prabath
>
>
> On Wed, Oct 16, 2013 at 11:16 PM, Imesh Gunaratne <im...@apache.org>wrote:
>
>> Hi Isuru,
>>
>> Great work!
>>
>> IMO the term "INFORMATION" is not commonly used on table names. I would
>> prefer CLUSTER_INFORMATION table to be called CLUSTER and
>> DATA_CARTRIDGE_INFORMATION table to be called DATA_CARTRIDGE.
>>
>> WDYT?
>>
>> Thanks
>> Imesh
>>
>>
>> On Wed, Oct 16, 2013 at 4:34 PM, Isuru Perera <is...@wso2.com> wrote:
>>
>>>
>>>
>>>
>>> On Wed, Oct 16, 2013 at 4:24 PM, Nirmal Fernando <nirmal070125@gmail.com
>>> > wrote:
>>>
>>>>
>>>>
>>>>
>>>> On Wed, Oct 16, 2013 at 3:30 PM, Isuru Perera <is...@wso2.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Could you please elaborate more on the entities. We had previously
>>>>> stored the Cartridge instance state in the database and now I do not see it
>>>>> here. Refer slide 14 at [1] for the database schema of Apache Stratos
>>>>> (incubating) version 3.0.0. How are we going to maintain cartridge instance
>>>>> status?
>>>>>
>>>>> We also had a Cartridge Subscription entity, which stored the
>>>>> subscription details and Cartridge instance entity actually stored the
>>>>> details of running cartridge instances.
>>>>>
>>>>> This new schema has lot of changes and therefore I think it's better
>>>>> to include details of every design decision.
>>>>>
>>>>
>>>> Exactly, I also felt there're gaps. I met IsuruH and had a chat. He
>>>> will send a revised version.
>>>>
>>> That's great!
>>>
>>> Thanks!
>>>
>>>>
>>>>> Thanks!
>>>>>
>>>>> [1]
>>>>> http://www.slideshare.net/chrishantha/apache-stratos-incubating-hangout-iv-stratos-controller-and-cli-internals
>>>>>
>>>>>
>>>>> On Wed, Oct 16, 2013 at 3:01 PM, Isuru Haththotuwa <is...@wso2.com>wrote:
>>>>>
>>>>>> Hi Devs,
>>>>>>
>>>>>> For $subject I came across the following initial database design. The
>>>>>> intention of this database is to persist the details for a cartridge
>>>>>> subscription. Please share your thoughts.
>>>>>>
>>>>>> [image: Inline image 1]
>>>>>>
>>>>>> --
>>>>>> Thanks and Regards,
>>>>>>
>>>>>> Isuru H.
>>>>>> Software Engineer, WSO2 Inc.
>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Isuru Perera
>>>>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>>>>> Lean . Enterprise . Middleware
>>>>>
>>>>> about.me/chrishantha
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Best Regards,
>>>> Nirmal
>>>>
>>>> Nirmal Fernando.
>>>> PPMC Member & Committer of Apache Stratos,
>>>> Senior Software Engineer, WSO2 Inc.
>>>>
>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> Isuru Perera
>>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>>> Lean . Enterprise . Middleware
>>>
>>> about.me/chrishantha
>>>
>>
>>
>
>
> --
> Prabath
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Re-Designing the Database Schema for Stratos Manager (SM)
Posted by Prabath Abeysekara <pr...@gmail.com>.
Hi,
You all might already be aware of this but just thought it would be worth
mentioning that you need to be a bit careful when choosing identifiers to
be used as table/column names, etc as different database vendors impose
different restrictions on parameters like identifier length, etc. IIRC, out
of all RDBMS types that are commonly in use, Oracle allows the lowest
max_table_name_character_length (30) and the rest of the types such as
MySQL, SQL Server, Postgres, etc allows you to have slightly lengthier
identifier names.
Therefore, I believe it is good to make the identifier names as short as
possible while preserving their intuitiveness and meaning as well as
consistency. Consistency would also be an important factor as, for example,
shortening a particular table name to be something like
"DATA_CARTRIDGE_SOMETHING_ELSE_*INFO*" (to be compatible with identifier
length restrictions) later while having another table in the schema which
carries the name "DATA_CARTRIDGE_*INFORMATION*", would not make it look too
clean.
These are very small stuff but thought would be important if by any chance
this was not taken into consideration. :)
Cheers,
Prabath
On Wed, Oct 16, 2013 at 11:16 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Hi Isuru,
>
> Great work!
>
> IMO the term "INFORMATION" is not commonly used on table names. I would
> prefer CLUSTER_INFORMATION table to be called CLUSTER and
> DATA_CARTRIDGE_INFORMATION table to be called DATA_CARTRIDGE.
>
> WDYT?
>
> Thanks
> Imesh
>
>
> On Wed, Oct 16, 2013 at 4:34 PM, Isuru Perera <is...@wso2.com> wrote:
>
>>
>>
>>
>> On Wed, Oct 16, 2013 at 4:24 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>>
>>>
>>>
>>>
>>> On Wed, Oct 16, 2013 at 3:30 PM, Isuru Perera <is...@wso2.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> Could you please elaborate more on the entities. We had previously
>>>> stored the Cartridge instance state in the database and now I do not see it
>>>> here. Refer slide 14 at [1] for the database schema of Apache Stratos
>>>> (incubating) version 3.0.0. How are we going to maintain cartridge instance
>>>> status?
>>>>
>>>> We also had a Cartridge Subscription entity, which stored the
>>>> subscription details and Cartridge instance entity actually stored the
>>>> details of running cartridge instances.
>>>>
>>>> This new schema has lot of changes and therefore I think it's better to
>>>> include details of every design decision.
>>>>
>>>
>>> Exactly, I also felt there're gaps. I met IsuruH and had a chat. He will
>>> send a revised version.
>>>
>> That's great!
>>
>> Thanks!
>>
>>>
>>>> Thanks!
>>>>
>>>> [1]
>>>> http://www.slideshare.net/chrishantha/apache-stratos-incubating-hangout-iv-stratos-controller-and-cli-internals
>>>>
>>>>
>>>> On Wed, Oct 16, 2013 at 3:01 PM, Isuru Haththotuwa <is...@wso2.com>wrote:
>>>>
>>>>> Hi Devs,
>>>>>
>>>>> For $subject I came across the following initial database design. The
>>>>> intention of this database is to persist the details for a cartridge
>>>>> subscription. Please share your thoughts.
>>>>>
>>>>> [image: Inline image 1]
>>>>>
>>>>> --
>>>>> Thanks and Regards,
>>>>>
>>>>> Isuru H.
>>>>> Software Engineer, WSO2 Inc.
>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Isuru Perera
>>>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>>>> Lean . Enterprise . Middleware
>>>>
>>>> about.me/chrishantha
>>>>
>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> Nirmal
>>>
>>> Nirmal Fernando.
>>> PPMC Member & Committer of Apache Stratos,
>>> Senior Software Engineer, WSO2 Inc.
>>>
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>
>>
>>
>> --
>> Isuru Perera
>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>> Lean . Enterprise . Middleware
>>
>> about.me/chrishantha
>>
>
>
--
Prabath
Re: Re-Designing the Database Schema for Stratos Manager (SM)
Posted by Imesh Gunaratne <im...@apache.org>.
Hi Isuru,
Great work!
IMO the term "INFORMATION" is not commonly used on table names. I would
prefer CLUSTER_INFORMATION table to be called CLUSTER and
DATA_CARTRIDGE_INFORMATION table to be called DATA_CARTRIDGE.
WDYT?
Thanks
Imesh
On Wed, Oct 16, 2013 at 4:34 PM, Isuru Perera <is...@wso2.com> wrote:
>
>
>
> On Wed, Oct 16, 2013 at 4:24 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>
>>
>>
>>
>> On Wed, Oct 16, 2013 at 3:30 PM, Isuru Perera <is...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> Could you please elaborate more on the entities. We had previously
>>> stored the Cartridge instance state in the database and now I do not see it
>>> here. Refer slide 14 at [1] for the database schema of Apache Stratos
>>> (incubating) version 3.0.0. How are we going to maintain cartridge instance
>>> status?
>>>
>>> We also had a Cartridge Subscription entity, which stored the
>>> subscription details and Cartridge instance entity actually stored the
>>> details of running cartridge instances.
>>>
>>> This new schema has lot of changes and therefore I think it's better to
>>> include details of every design decision.
>>>
>>
>> Exactly, I also felt there're gaps. I met IsuruH and had a chat. He will
>> send a revised version.
>>
> That's great!
>
> Thanks!
>
>>
>>> Thanks!
>>>
>>> [1]
>>> http://www.slideshare.net/chrishantha/apache-stratos-incubating-hangout-iv-stratos-controller-and-cli-internals
>>>
>>>
>>> On Wed, Oct 16, 2013 at 3:01 PM, Isuru Haththotuwa <is...@wso2.com>wrote:
>>>
>>>> Hi Devs,
>>>>
>>>> For $subject I came across the following initial database design. The
>>>> intention of this database is to persist the details for a cartridge
>>>> subscription. Please share your thoughts.
>>>>
>>>> [image: Inline image 1]
>>>>
>>>> --
>>>> Thanks and Regards,
>>>>
>>>> Isuru H.
>>>> Software Engineer, WSO2 Inc.
>>>> +94 716 358 048* <http://wso2.com/>*
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Isuru Perera
>>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>>> Lean . Enterprise . Middleware
>>>
>>> about.me/chrishantha
>>>
>>
>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>>
>
>
>
> --
> Isuru Perera
> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
>
Re: Re-Designing the Database Schema for Stratos Manager (SM)
Posted by Isuru Perera <is...@wso2.com>.
On Wed, Oct 16, 2013 at 4:24 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>
>
>
> On Wed, Oct 16, 2013 at 3:30 PM, Isuru Perera <is...@wso2.com> wrote:
>
>> Hi,
>>
>> Could you please elaborate more on the entities. We had previously stored
>> the Cartridge instance state in the database and now I do not see it here.
>> Refer slide 14 at [1] for the database schema of Apache Stratos
>> (incubating) version 3.0.0. How are we going to maintain cartridge instance
>> status?
>>
>> We also had a Cartridge Subscription entity, which stored the
>> subscription details and Cartridge instance entity actually stored the
>> details of running cartridge instances.
>>
>> This new schema has lot of changes and therefore I think it's better to
>> include details of every design decision.
>>
>
> Exactly, I also felt there're gaps. I met IsuruH and had a chat. He will
> send a revised version.
>
That's great!
Thanks!
>
>> Thanks!
>>
>> [1]
>> http://www.slideshare.net/chrishantha/apache-stratos-incubating-hangout-iv-stratos-controller-and-cli-internals
>>
>>
>> On Wed, Oct 16, 2013 at 3:01 PM, Isuru Haththotuwa <is...@wso2.com>wrote:
>>
>>> Hi Devs,
>>>
>>> For $subject I came across the following initial database design. The
>>> intention of this database is to persist the details for a cartridge
>>> subscription. Please share your thoughts.
>>>
>>> [image: Inline image 1]
>>>
>>> --
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>> Software Engineer, WSO2 Inc.
>>> +94 716 358 048* <http://wso2.com/>*
>>>
>>>
>>>
>>
>>
>> --
>> Isuru Perera
>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>> Lean . Enterprise . Middleware
>>
>> about.me/chrishantha
>>
>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
--
Isuru Perera
Senior Software Engineer | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware
about.me/chrishantha
Re: Re-Designing the Database Schema for Stratos Manager (SM)
Posted by Nirmal Fernando <ni...@gmail.com>.
On Wed, Oct 16, 2013 at 3:30 PM, Isuru Perera <is...@wso2.com> wrote:
> Hi,
>
> Could you please elaborate more on the entities. We had previously stored
> the Cartridge instance state in the database and now I do not see it here.
> Refer slide 14 at [1] for the database schema of Apache Stratos
> (incubating) version 3.0.0. How are we going to maintain cartridge instance
> status?
>
> We also had a Cartridge Subscription entity, which stored the subscription
> details and Cartridge instance entity actually stored the details of
> running cartridge instances.
>
> This new schema has lot of changes and therefore I think it's better to
> include details of every design decision.
>
Exactly, I also felt there're gaps. I met IsuruH and had a chat. He will
send a revised version.
>
> Thanks!
>
> [1]
> http://www.slideshare.net/chrishantha/apache-stratos-incubating-hangout-iv-stratos-controller-and-cli-internals
>
>
> On Wed, Oct 16, 2013 at 3:01 PM, Isuru Haththotuwa <is...@wso2.com>wrote:
>
>> Hi Devs,
>>
>> For $subject I came across the following initial database design. The
>> intention of this database is to persist the details for a cartridge
>> subscription. Please share your thoughts.
>>
>> [image: Inline image 1]
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> Software Engineer, WSO2 Inc.
>> +94 716 358 048* <http://wso2.com/>*
>>
>>
>>
>
>
> --
> Isuru Perera
> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Re-Designing the Database Schema for Stratos Manager (SM)
Posted by Isuru Haththotuwa <is...@wso2.com>.
Hi,
On Wed, Oct 16, 2013 at 3:30 PM, Isuru Perera <is...@wso2.com> wrote:
> Hi,
>
> Could you please elaborate more on the entities. We had previously stored
> the Cartridge instance state in the database and now I do not see it here.
> Refer slide 14 at [1] for the database schema of Apache Stratos
> (incubating) version 3.0.0. How are we going to maintain cartridge instance
> status?
>
> We also had a Cartridge Subscription entity, which stored the subscription
> details and Cartridge instance entity actually stored the details of
> running cartridge instances.
>
> This new schema has lot of changes and therefore I think it's better to
> include details of every design decision.
>
> Thanks!
>
> [1]
> http://www.slideshare.net/chrishantha/apache-stratos-incubating-hangout-iv-stratos-controller-and-cli-internals
>
Thanks for the feedback. We had a quick chat and a review on this diagram
and identified some issues. Will send an updated diagram asap.
For the new design, SM can subscribe to the MB and receive state changes.
That is the logic of not persisting the state in the database. However we
might need to persist it because if SM re-starts, it would need to get the
last statuses of the instances.
>
>
> On Wed, Oct 16, 2013 at 3:01 PM, Isuru Haththotuwa <is...@wso2.com>wrote:
>
>> Hi Devs,
>>
>> For $subject I came across the following initial database design. The
>> intention of this database is to persist the details for a cartridge
>> subscription. Please share your thoughts.
>>
>> [image: Inline image 1]
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> Software Engineer, WSO2 Inc.
>> +94 716 358 048* <http://wso2.com/>*
>>
>>
>>
>
>
> --
> Isuru Perera
> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
>
--
Thanks and Regards,
Isuru H.
Software Engineer, WSO2 Inc.
+94 716 358 048* <http://wso2.com/>*
Re: Re-Designing the Database Schema for Stratos Manager (SM)
Posted by Isuru Perera <is...@wso2.com>.
Hi,
Could you please elaborate more on the entities. We had previously stored
the Cartridge instance state in the database and now I do not see it here.
Refer slide 14 at [1] for the database schema of Apache Stratos
(incubating) version 3.0.0. How are we going to maintain cartridge instance
status?
We also had a Cartridge Subscription entity, which stored the subscription
details and Cartridge instance entity actually stored the details of
running cartridge instances.
This new schema has lot of changes and therefore I think it's better to
include details of every design decision.
Thanks!
[1]
http://www.slideshare.net/chrishantha/apache-stratos-incubating-hangout-iv-stratos-controller-and-cli-internals
On Wed, Oct 16, 2013 at 3:01 PM, Isuru Haththotuwa <is...@wso2.com> wrote:
> Hi Devs,
>
> For $subject I came across the following initial database design. The
> intention of this database is to persist the details for a cartridge
> subscription. Please share your thoughts.
>
> [image: Inline image 1]
>
> --
> Thanks and Regards,
>
> Isuru H.
> Software Engineer, WSO2 Inc.
> +94 716 358 048* <http://wso2.com/>*
>
>
>
--
Isuru Perera
Senior Software Engineer | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware
about.me/chrishantha