[Spce-user] db rev naming
alutay at sipwise.com
Mon Apr 1 04:36:14 EDT 2019
It is better to have the later reply instead of no reply ;-)
For the history here, mr7.3+ cfg-schema.git:
> commit 4f224d0438d997fe83589051c99caef5e24b5323
> Author: Guillem Jover <gjover at sipwise.com>
> TT#44700 new-script: Implement new ID allocation scheme
> The new ID allocation scheme will namespace each id with the current
> NGCP release, normalized to XXYYZZ from mrXX.YY.ZZ. And append 4 digits
> from 0000 to 9999. Within this range, 0-4999 will be used by Sipwise,
> and 5000-9999 can be used by customers. Each new id assigned will
> increase between 10-20 to leave room for hot-fixes once released, and
> to avoid possible in-flight collisions during development.
db_schema.git is still pending... but we are moving ;-)
Stay tuned and have fun!
On 8/21/15 7:17 PM, Jon Bonilla (Manwe) wrote:
>> The idea is good, I am completely agree to keep some spaces between ID.
>> I am not sure about possibility to use release version in DB statements.
>> It will create misunderstanding for backported DB statements.
>> Maybe it will be enough just to multiply current login on 10.
>> So, Sipwise will release 12340, 12350, 12360 which has a gap for 9
>> statements everywhere.
>> What do you think?
> That would be great. It would work too and it provides more control.
More information about the Spce-user