[asterisk-bugs] [JIRA] (ASTERISK-21255) Create a sorcery wizard for the AstDB

[Matt Jordan (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-21255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan updated ASTERISK-21255:
-----------------------------------

    Description: 
A key feature of Asterisk is the ability to persist objects in memory, the AstDB, or in a dynamic realtime database. In the past, much of this manipulation has been manual, that is, you have to store objects in an ao2 container yourself; in the AstDB yourself; and in a dynamic realtime database yourself. Synchronization of the objects has to occur manually and is prone to synchronization failures (or just forgetting to do it).

Sorcery provides the ability to persist objects anywhere as well as store them in a cache hierarchy. Right now we have an in memory provider; we now also need one for the AstDB.

This should let us doing something like the following:

Take a SIP registration, and store it such that:
* It is available in Memory - used as the highest level in the cache
* If not in memory, it is available in AstDB - used for restarts of Asterisk, such that registration information carries over
* If not in either cache, it is available in a Realtime Database - external storage to coordinate registrations across multiple systems, querying of data, etc.



  was:
A key feature of Asterisk is the ability to persist objects in memory, the AstDB, or in a dynamic realtime database. In the past, much of this manipulation has been manual, that is, you have to store objects in an ao2 container yourself; in the AstDB yourself; and in a dynamic realtime database yourself. Synchronization of the objects has to occur manually and is prone to synchronization failures (or just forgetting to do it).

Sorcery provides the ability to persist objects anywhere. Since the act of persisting the objects is abstracted away from the developer (and happens automagically), it should also be able to choose (based on it's configuration) the appropriate place to store the objects.

For example, it may be desirable to persist a SIP registration in memory, the AstDB, and a dynamic realtime backend.
* Memory - used as the highest level in the cache
* AstDB - used for restarts of Asterisk, such that registration information carries over
* Realtime Database - external storage to coordinate registrations across multiple systems, querying of data, etc.

Sorcery should be able to provide this cache hieararchy automatically to its consumers.


        Summary: Create a sorcery wizard for the AstDB  (was: Add the ability for sorcery backends to be organized in a hierarchy to provide caching)
    
> Create a sorcery wizard for the AstDB
> -------------------------------------
>
>                 Key: ASTERISK-21255
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21255
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: Core/Sorcery
>    Affects Versions: 12
>            Reporter: Matt Jordan
>              Labels: Asterisk12, NewSIP
>      Target Release: 12
>
>
> A key feature of Asterisk is the ability to persist objects in memory, the AstDB, or in a dynamic realtime database. In the past, much of this manipulation has been manual, that is, you have to store objects in an ao2 container yourself; in the AstDB yourself; and in a dynamic realtime database yourself. Synchronization of the objects has to occur manually and is prone to synchronization failures (or just forgetting to do it).
> Sorcery provides the ability to persist objects anywhere as well as store them in a cache hierarchy. Right now we have an in memory provider; we now also need one for the AstDB.
> This should let us doing something like the following:
> Take a SIP registration, and store it such that:
> * It is available in Memory - used as the highest level in the cache
> * If not in memory, it is available in AstDB - used for restarts of Asterisk, such that registration information carries over
> * If not in either cache, it is available in a Realtime Database - external storage to coordinate registrations across multiple systems, querying of data, etc.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira