Hello,
some bits were left with the old project name OpenSER, not to disturb too much at that time and see where everything goes.
Other voices expressed same idea in the past, now everything is stable and development goes smooth, so it is good to make a decision because openser is too way back and new comers could be confused.
In my list is renaming from openser to kamailio next attributes: - default database name (exiting configs should not be impacted that much as most of them have database provided by module parameter) - default database access usernames and passwords, respectively openser, openserro and openserrw should become kamailio, kamailioro and kamailiorw - perl module API is packed as OpenSER - this could affect some people using it, but a search and replace should do it - snmpstats mibs - probably it is going to have some impact as well
Eventually we can start doing it gradually, one or two per release, but is probably better to do all at once, so people will do one upgrade with next major release.
Another thing is sercmd, it is in conflict for packaging as both ser and kamailio install it. It means that one cannot install both kamailio and ser at same time from packages. One option is to install it as kamcmd.
Because these changes affect users and devels, I sent the message to both mailing lists. Opinions?
Cheers, Daniel
Hello,
I think it is better to do all changes at once.
Thx.
2012/10/8 Daniel-Constantin Mierla miconda@gmail.com
Hello,
some bits were left with the old project name OpenSER, not to disturb too much at that time and see where everything goes.
Other voices expressed same idea in the past, now everything is stable and development goes smooth, so it is good to make a decision because openser is too way back and new comers could be confused.
In my list is renaming from openser to kamailio next attributes:
- default database name (exiting configs should not be impacted that much
as most of them have database provided by module parameter)
- default database access usernames and passwords, respectively openser,
openserro and openserrw should become kamailio, kamailioro and kamailiorw
- perl module API is packed as OpenSER - this could affect some people
using it, but a search and replace should do it
- snmpstats mibs - probably it is going to have some impact as well
Eventually we can start doing it gradually, one or two per release, but is probably better to do all at once, so people will do one upgrade with next major release.
Another thing is sercmd, it is in conflict for packaging as both ser and kamailio install it. It means that one cannot install both kamailio and ser at same time from packages. One option is to install it as kamcmd.
Because these changes affect users and devels, I sent the message to both mailing lists. Opinions?
Cheers, Daniel
-- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/**micondahttp://www.linkedin.com/in/miconda Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - http://asipto.com/u/katu
______________________________**_________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**usershttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Daniel-Constantin Mierla writes:
In my list is renaming from openser to kamailio next attributes:
- default database name (exiting configs should not be impacted that
much as most of them have database provided by module parameter)
i once tried to change database name from ser to something newer, but i was not able to find from mysql docs a db rename command.
-- juha
On 10/8/12 4:41 PM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
In my list is renaming from openser to kamailio next attributes:
- default database name (exiting configs should not be impacted that
much as most of them have database provided by module parameter)
i once tried to change database name from ser to something newer, but i was not able to find from mysql docs a db rename command.
this one: - http://dev.mysql.com/doc/refman/5.1/en/rename-database.html
But the old name can be kept in existing installation -- it is a matter of db_url parameter value and setting in kamctlrc.
Cheers, Daniel
HI Daniel,
I consider myself a "new comer" and having both kamailio and ser interacting with each other is indeed confusing.
For me, the change is welcome and I'm in favor of doing all the effort at once.
Regards.
Carlos
On Mon, Oct 8, 2012 at 11:33 AM, Daniel-Constantin Mierla <miconda@gmail.com
wrote:
Hello,
some bits were left with the old project name OpenSER, not to disturb too much at that time and see where everything goes.
Other voices expressed same idea in the past, now everything is stable and development goes smooth, so it is good to make a decision because openser is too way back and new comers could be confused.
In my list is renaming from openser to kamailio next attributes:
- default database name (exiting configs should not be impacted that much
as most of them have database provided by module parameter)
- default database access usernames and passwords, respectively openser,
openserro and openserrw should become kamailio, kamailioro and kamailiorw
- perl module API is packed as OpenSER - this could affect some people
using it, but a search and replace should do it
- snmpstats mibs - probably it is going to have some impact as well
Eventually we can start doing it gradually, one or two per release, but is probably better to do all at once, so people will do one upgrade with next major release.
Another thing is sercmd, it is in conflict for packaging as both ser and kamailio install it. It means that one cannot install both kamailio and ser at same time from packages. One option is to install it as kamcmd.
Because these changes affect users and devels, I sent the message to both mailing lists. Opinions?
Cheers, Daniel
-- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/**micondahttp://www.linkedin.com/in/miconda Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - http://asipto.com/u/katu
______________________________**_________________ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**devhttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Hello,
I am aware of such confusion, but there are people using the two database schema, so completely unifying them is quite complex process.
But, speaking of available documentation, community maintenance and new comers, probably it makes sense to make kamailio default flavour, because ser requires more technical involvement -- I haven't seen new comers looking at installing ser flavour, which is default one now.
Cheers, Daniel
On 10/8/12 4:48 PM, Carlos Ruiz Díaz wrote:
HI Daniel,
I consider myself a "new comer" and having both kamailio and ser interacting with each other is indeed confusing.
For me, the change is welcome and I'm in favor of doing all the effort at once.
Regards.
Carlos
On Mon, Oct 8, 2012 at 11:33 AM, Daniel-Constantin Mierla <miconda@gmail.com mailto:miconda@gmail.com> wrote:
Hello, some bits were left with the old project name OpenSER, not to disturb too much at that time and see where everything goes. Other voices expressed same idea in the past, now everything is stable and development goes smooth, so it is good to make a decision because openser is too way back and new comers could be confused. In my list is renaming from openser to kamailio next attributes: - default database name (exiting configs should not be impacted that much as most of them have database provided by module parameter) - default database access usernames and passwords, respectively openser, openserro and openserrw should become kamailio, kamailioro and kamailiorw - perl module API is packed as OpenSER - this could affect some people using it, but a search and replace should do it - snmpstats mibs - probably it is going to have some impact as well Eventually we can start doing it gradually, one or two per release, but is probably better to do all at once, so people will do one upgrade with next major release. Another thing is sercmd, it is in conflict for packaging as both ser and kamailio install it. It means that one cannot install both kamailio and ser at same time from packages. One option is to install it as kamcmd. Because these changes affect users and devels, I sent the message to both mailing lists. Opinions? Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - http://asipto.com/u/katu _______________________________________________ sr-dev mailing list sr-dev@lists.sip-router.org <mailto:sr-dev@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
8 okt 2012 kl. 16:33 skrev Daniel-Constantin Mierla miconda@gmail.com:
Hello,
some bits were left with the old project name OpenSER, not to disturb too much at that time and see where everything goes.
Other voices expressed same idea in the past, now everything is stable and development goes smooth, so it is good to make a decision because openser is too way back and new comers could be confused.
In my list is renaming from openser to kamailio next attributes:
- default database name (exiting configs should not be impacted that much as most of them have database provided by module parameter)
- default database access usernames and passwords, respectively openser, openserro and openserrw should become kamailio, kamailioro and kamailiorw
- perl module API is packed as OpenSER - this could affect some people using it, but a search and replace should do it
- snmpstats mibs - probably it is going to have some impact as well
Good timing, good idea.
I think we should clean up everything at the same time - including all documentation.
Time to restart with GIT I think ;-)
/O
-
Carlos Ruiz Díaz -
Cenk İlker İzanlı -
Daniel-Constantin Mierla -
Juha Heinanen -
Klaus Darilion -
Olle E. Johansson