Hello,
as most of you know, we have a rather distributed infrastructure, with servers provided from different companies or persons.
We came to the time when one of the servers is too old and considered to be decommisioned, so we have to decide how to move on. It is about sip-router.org, who was offered/sponsored by courtesy of Jan Janak. From project point of view, the server hosts:
- git repository - bug tracker - website and wiki under domain sip-router.org
Given that no matter what we like, there is work to do, I am looking to see what are the best options out there for everyone involved in the project.
The sip-router.or wbesite and wiki, which are not really updated anyhow, will be relocated as virtual host in kamailio.org server and made static for historic purposes.
For git and tracker, I thought of two variants:
1) move to use an external hosting service - the first candidate and perhaps the only to be considered is GitHub, we have there already a real time mirror of git repository. Then we should get a read only mirror to kamailio.org. If the tracker on github is good enough for everyone, then we will use it. I could see quickly that lot of kamailio developers already have an account on github.
2) get a new server and relocate those components there. It will need to be configured from scratch and the components eventually updated to use latest versions. In case of tracker, we have eventually to re-evaluate if flyspray worth keeping, as we had several discussions, due to the fact that the project doesn't seem to be very active.
My personal preference at this moment is 1), given that offloads administration works from project.
For 2) we will need someone to commit to a sysadmin job for long time. As probably you noticed lately, serious security vulnerabilities can appear and someone needs to take care of proper maintenance of the server. I don't want to get all services on kamailio.org, as it has other critical components (mailing lists, releases, website, ...) and messing it or overloading doesn't make sense.
There is no real pressure to come to a decision, we can still rely on the server for a while, but I would rather not postpone it for long.
While users are encouraged to give their opinion, I feel that existing developers should have the main role in decision, being something that impacts them directly.
Your preference? Any other opinions?
Cheers, Daniel
I'm certain that LOD would be willing to sponsor the server for git / tracker and I'd offer to handle the sysadmin of the server.
Fred Posner The Palner Group, Inc. http://www.palner.com (web) +1-503-914-0999 (direct) +1-954-472-2896 (fax)
On 11/05/2014 09:25 AM, Daniel-Constantin Mierla wrote:
Hello,
as most of you know, we have a rather distributed infrastructure, with servers provided from different companies or persons.
We came to the time when one of the servers is too old and considered to be decommisioned, so we have to decide how to move on. It is about sip-router.org, who was offered/sponsored by courtesy of Jan Janak. From project point of view, the server hosts:
- git repository
- bug tracker
- website and wiki under domain sip-router.org
Given that no matter what we like, there is work to do, I am looking to see what are the best options out there for everyone involved in the project.
The sip-router.or wbesite and wiki, which are not really updated anyhow, will be relocated as virtual host in kamailio.org server and made static for historic purposes.
For git and tracker, I thought of two variants:
- move to use an external hosting service - the first candidate and
perhaps the only to be considered is GitHub, we have there already a real time mirror of git repository. Then we should get a read only mirror to kamailio.org. If the tracker on github is good enough for everyone, then we will use it. I could see quickly that lot of kamailio developers already have an account on github.
- get a new server and relocate those components there. It will need to
be configured from scratch and the components eventually updated to use latest versions. In case of tracker, we have eventually to re-evaluate if flyspray worth keeping, as we had several discussions, due to the fact that the project doesn't seem to be very active.
My personal preference at this moment is 1), given that offloads administration works from project.
For 2) we will need someone to commit to a sysadmin job for long time. As probably you noticed lately, serious security vulnerabilities can appear and someone needs to take care of proper maintenance of the server. I don't want to get all services on kamailio.org, as it has other critical components (mailing lists, releases, website, ...) and messing it or overloading doesn't make sense.
There is no real pressure to come to a decision, we can still rely on the server for a while, but I would rather not postpone it for long.
While users are encouraged to give their opinion, I feel that existing developers should have the main role in decision, being something that impacts them directly.
Your preference? Any other opinions?
Cheers, Daniel
On 11/05/2014 10:32 AM, Fred Posner wrote:
I'm certain that LOD would be willing to sponsor the server for git / tracker and I'd offer to handle the sysadmin of the server.
+1 for self-hosting, -3 for GitHub.
2014-11-05 17:25 GMT+03:00 Daniel-Constantin Mierla miconda@gmail.com:
Hello,
as most of you know, we have a rather distributed infrastructure, with servers provided from different companies or persons.
One thing is certain - move git and bugtracker to github.
Hi, I can't log some core keyword like 'dst_ip', 'src_ip'. I try with
xlog("L_ALERT","ALERT: dst_ip: dsr_ip\n "); # ==> that just print dst_ip $var(x)=dst_ip # ==>the config file is not valid due to this line xlog("L_ALERT","ALERT: dst_ip: $var(x)\n ");
I found $Ri to match src_ip and $si to match src_ip, that I can log.
xlog("L_ALERT","ALERT: dst_ip: $Ri\n"); xlog("L_ALERT","ALERT: src_ip: $si\n");
Is it the good way to print theses variables ?
Thanks
Hi, I'm still stuck with this issue. How can I log 'dst_ip' for example ?
Thanks. Le 05/11/2014 17:52, Julien a écrit :
Hi, I can't log some core keyword like 'dst_ip', 'src_ip'. I try with
xlog("L_ALERT","ALERT: dst_ip: dsr_ip\n "); # ==> that just print dst_ip $var(x)=dst_ip # ==>the config file is not valid due to this line xlog("L_ALERT","ALERT: dst_ip: $var(x)\n ");
I found $Ri to match src_ip and $si to match src_ip, that I can log.
xlog("L_ALERT","ALERT: dst_ip: $Ri\n"); xlog("L_ALERT","ALERT: src_ip: $si\n");
Is it the good way to print theses variables ?
Thanks
Hello,
dst_ip keyword corresponds to $Ri variable.
Cheers, Daniel
On 10/12/14 14:54, Julien wrote:
Hi, I'm still stuck with this issue. How can I log 'dst_ip' for example ?
Thanks. Le 05/11/2014 17:52, Julien a écrit :
Hi, I can't log some core keyword like 'dst_ip', 'src_ip'. I try with
xlog("L_ALERT","ALERT: dst_ip: dsr_ip\n "); # ==> that just print dst_ip $var(x)=dst_ip # ==>the config file is not valid due to this line xlog("L_ALERT","ALERT: dst_ip: $var(x)\n ");
I found $Ri to match src_ip and $si to match src_ip, that I can log.
xlog("L_ALERT","ALERT: dst_ip: $Ri\n"); xlog("L_ALERT","ALERT: src_ip: $si\n");
Is it the good way to print theses variables ?
Thanks
To provide a bit of context: the server Daniel is referring to is a dedicated machine hosted at Hetzner. Currently, the machine is mostly used to host the git repositories for kamailio and sems, as well as scripts to automatically generate doxygen documentation out of the source code.
The server is getting old and had a couple of hardware related outages recently. While Hetzner would replace faulty components at no charge, upgrading the hardware to a more modern configuration would probably cost extra.
For what it's worth, I think moving the git repository to a hosted service would make sense. Hosted solutions like github and bitbucket improved considerably over the past couple of years and offer services we won't be able to setup and maintain on our own.
If you prefer to keep a self-hosted git repository, I think we should at least move it to gitolite: http://gitolite.com/
To make it more manageable (doesn't require ssh access for individual people).
-Jan
On Wed, Nov 5, 2014 at 9:25 AM, Daniel-Constantin Mierla miconda@gmail.com wrote:
Hello,
as most of you know, we have a rather distributed infrastructure, with servers provided from different companies or persons.
We came to the time when one of the servers is too old and considered to be decommisioned, so we have to decide how to move on. It is about sip-router.org, who was offered/sponsored by courtesy of Jan Janak. From project point of view, the server hosts:
- git repository
- bug tracker
- website and wiki under domain sip-router.org
Given that no matter what we like, there is work to do, I am looking to see what are the best options out there for everyone involved in the project.
The sip-router.or wbesite and wiki, which are not really updated anyhow, will be relocated as virtual host in kamailio.org server and made static for historic purposes.
For git and tracker, I thought of two variants:
- move to use an external hosting service - the first candidate and
perhaps the only to be considered is GitHub, we have there already a real time mirror of git repository. Then we should get a read only mirror to kamailio.org. If the tracker on github is good enough for everyone, then we will use it. I could see quickly that lot of kamailio developers already have an account on github.
- get a new server and relocate those components there. It will need to
be configured from scratch and the components eventually updated to use latest versions. In case of tracker, we have eventually to re-evaluate if flyspray worth keeping, as we had several discussions, due to the fact that the project doesn't seem to be very active.
My personal preference at this moment is 1), given that offloads administration works from project.
For 2) we will need someone to commit to a sysadmin job for long time. As probably you noticed lately, serious security vulnerabilities can appear and someone needs to take care of proper maintenance of the server. I don't want to get all services on kamailio.org, as it has other critical components (mailing lists, releases, website, ...) and messing it or overloading doesn't make sense.
There is no real pressure to come to a decision, we can still rely on the server for a while, but I would rather not postpone it for long.
While users are encouraged to give their opinion, I feel that existing developers should have the main role in decision, being something that impacts them directly.
Your preference? Any other opinions?
Cheers, Daniel
-- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Nov 24-27, Berlin - http://www.asipto.com
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-users
On Thu, Nov 6, 2014 at 11:40 AM, Jan Janak jan@janakj.org wrote:
If you prefer to keep a self-hosted git repository, I think we should at least move it to gitolite: http://gitolite.com/
To make it more manageable (doesn't require ssh access for individual people).
Gitlab is another potential candidate for a self-hosted repository:
(seems to provide more than gitolite).
-Jan
On Wed, Nov 5, 2014 at 9:25 AM, Daniel-Constantin Mierla < miconda@gmail.com> wrote:
Hello,
as most of you know, we have a rather distributed infrastructure, with servers provided from different companies or persons.
We came to the time when one of the servers is too old and considered to be decommisioned, so we have to decide how to move on. It is about sip-router.org, who was offered/sponsored by courtesy of Jan Janak. From project point of view, the server hosts:
- git repository
- bug tracker
- website and wiki under domain sip-router.org
Given that no matter what we like, there is work to do, I am looking to see what are the best options out there for everyone involved in the project.
The sip-router.or wbesite and wiki, which are not really updated anyhow, will be relocated as virtual host in kamailio.org server and made static for historic purposes.
For git and tracker, I thought of two variants:
- move to use an external hosting service - the first candidate and
perhaps the only to be considered is GitHub, we have there already a real time mirror of git repository. Then we should get a read only mirror to kamailio.org. If the tracker on github is good enough for everyone, then we will use it. I could see quickly that lot of kamailio developers already have an account on github.
- get a new server and relocate those components there. It will need to
be configured from scratch and the components eventually updated to use latest versions. In case of tracker, we have eventually to re-evaluate if flyspray worth keeping, as we had several discussions, due to the fact that the project doesn't seem to be very active.
My personal preference at this moment is 1), given that offloads administration works from project.
For 2) we will need someone to commit to a sysadmin job for long time. As probably you noticed lately, serious security vulnerabilities can appear and someone needs to take care of proper maintenance of the server. I don't want to get all services on kamailio.org, as it has other critical components (mailing lists, releases, website, ...) and messing it or overloading doesn't make sense.
There is no real pressure to come to a decision, we can still rely on the server for a while, but I would rather not postpone it for long.
While users are encouraged to give their opinion, I feel that existing developers should have the main role in decision, being something that impacts them directly.
Your preference? Any other opinions?
Cheers, Daniel
-- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Nov 24-27, Berlin - http://www.asipto.com
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-users
With no private repositories, gitlab is free which is nice.
---Fred
On Nov 9, 2014, at 1:20 PM, Jan Janak jan@janakj.org wrote:
On Thu, Nov 6, 2014 at 11:40 AM, Jan Janak jan@janakj.org wrote: If you prefer to keep a self-hosted git repository, I think we should at least move it to gitolite: http://gitolite.com/
To make it more manageable (doesn't require ssh access for individual people).
Gitlab is another potential candidate for a self-hosted repository:
(seems to provide more than gitolite).
-Jan
On Wed, Nov 5, 2014 at 9:25 AM, Daniel-Constantin Mierla miconda@gmail.com wrote: Hello,
as most of you know, we have a rather distributed infrastructure, with servers provided from different companies or persons.
We came to the time when one of the servers is too old and considered to be decommisioned, so we have to decide how to move on. It is about sip-router.org, who was offered/sponsored by courtesy of Jan Janak. From project point of view, the server hosts:
- git repository
- bug tracker
- website and wiki under domain sip-router.org
Given that no matter what we like, there is work to do, I am looking to see what are the best options out there for everyone involved in the project.
The sip-router.or wbesite and wiki, which are not really updated anyhow, will be relocated as virtual host in kamailio.org server and made static for historic purposes.
For git and tracker, I thought of two variants:
- move to use an external hosting service - the first candidate and
perhaps the only to be considered is GitHub, we have there already a real time mirror of git repository. Then we should get a read only mirror to kamailio.org. If the tracker on github is good enough for everyone, then we will use it. I could see quickly that lot of kamailio developers already have an account on github.
- get a new server and relocate those components there. It will need to
be configured from scratch and the components eventually updated to use latest versions. In case of tracker, we have eventually to re-evaluate if flyspray worth keeping, as we had several discussions, due to the fact that the project doesn't seem to be very active.
My personal preference at this moment is 1), given that offloads administration works from project.
For 2) we will need someone to commit to a sysadmin job for long time. As probably you noticed lately, serious security vulnerabilities can appear and someone needs to take care of proper maintenance of the server. I don't want to get all services on kamailio.org, as it has other critical components (mailing lists, releases, website, ...) and messing it or overloading doesn't make sense.
There is no real pressure to come to a decision, we can still rely on the server for a while, but I would rather not postpone it for long.
While users are encouraged to give their opinion, I feel that existing developers should have the main role in decision, being something that impacts them directly.
Your preference? Any other opinions?
Cheers, Daniel
-- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Nov 24-27, Berlin - http://www.asipto.com
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-users
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-users
Hello,
first, many thanks for those giving feedback on this topic. I reply on my email, to have the content of the initial post, on the other replies being dispersed.
Not being much discussed lately, I think it is time to analyze and see if result stays final.
That would be: use github as main git repository for kamailio source code.
Besides the majority of the opinions being for github, here are my remarks for self hosted based on the replies, but also mainly on the past experience.
Not to forget, first many thanks to Fred for offering resources to deal with self hosted. However, there are many other aspects making self-hosted option hard to deal with:
- having only one volunteer, with no ensured income for this specific work, puts a high risk on the future. Back in 2008, there were many from Kamailio and SER project helping with our infrastructure. Over the years, it ended up with me doing a lot and some help occasionally from Henning or Jan. Time can changes priorities of tasks from work or life, it is not something bad at all, just has impact in how we should decide.
- while lod.com offered already some systems (e.g., where we keep rpm mirrors), there was no direct relation with the project and overall, nothing during a long period of time. I don't really feel confident in very long term with a sponsored system from a company, not having a commercial agreement to ensure SLA and availability. Companies can be bought, management change or employs/collaborators leave
- maybe not that important, but given that most of developers are based in Europe, I would like to have the server hosted by a company in this area, because in case of unexpected issues, we can deal with it at decent time of the day. While sysadmin/maintenance can be done from anywhere at anytime, here we talk about unexpected critical issues. Existing system is from Hetzner, which gives really good remote management (including boot console via web, soft and hard restart via web page), but also on-side hands-on services from their team at a fair price. Evaluating what is offered by other hosting companies probably would take time as well
- we lack sysadmin resources even now, excepting the maintenance of git/sip-router.org, like having proper rpm repository, backup for kamailio.org and nightly tarballs have to be refactored. Even some lod.com systems sit unused now because we lacked resources to turn them on something useful for the project (also the rpm mirror is half way, mainly manual update)
- we were before using sourceforge.net (ser used berlios) with pretty good experience. It will be really hard to offer better availability and maintenance than one of those repository hosting services. The main goal with own git repo was to integrate SER CVS with Kamailio SVN repos, now that is finished. We will have a real time mirror on kamailio.org and we can always shift to another solution if what is at a specific time proves to be very bad
Those are my opinions, if some of them are wrong or I have missed anything relevant for any of the options, reply to mailing lists.
Cheers, Daniel
On 05/11/14 15:25, Daniel-Constantin Mierla wrote:
Hello,
as most of you know, we have a rather distributed infrastructure, with servers provided from different companies or persons.
We came to the time when one of the servers is too old and considered to be decommisioned, so we have to decide how to move on. It is about sip-router.org, who was offered/sponsored by courtesy of Jan Janak. From project point of view, the server hosts:
- git repository
- bug tracker
- website and wiki under domain sip-router.org
Given that no matter what we like, there is work to do, I am looking to see what are the best options out there for everyone involved in the project.
The sip-router.or wbesite and wiki, which are not really updated anyhow, will be relocated as virtual host in kamailio.org server and made static for historic purposes.
For git and tracker, I thought of two variants:
- move to use an external hosting service - the first candidate and
perhaps the only to be considered is GitHub, we have there already a real time mirror of git repository. Then we should get a read only mirror to kamailio.org. If the tracker on github is good enough for everyone, then we will use it. I could see quickly that lot of kamailio developers already have an account on github.
- get a new server and relocate those components there. It will need to
be configured from scratch and the components eventually updated to use latest versions. In case of tracker, we have eventually to re-evaluate if flyspray worth keeping, as we had several discussions, due to the fact that the project doesn't seem to be very active.
My personal preference at this moment is 1), given that offloads administration works from project.
For 2) we will need someone to commit to a sysadmin job for long time. As probably you noticed lately, serious security vulnerabilities can appear and someone needs to take care of proper maintenance of the server. I don't want to get all services on kamailio.org, as it has other critical components (mailing lists, releases, website, ...) and messing it or overloading doesn't make sense.
There is no real pressure to come to a decision, we can still rely on the server for a while, but I would rather not postpone it for long.
While users are encouraged to give their opinion, I feel that existing developers should have the main role in decision, being something that impacts them directly.
Your preference? Any other opinions?
Cheers, Daniel
-
Alex Balashov -
Daniel-Constantin Mierla -
Fred Posner -
Jan Janak -
Jorj Bauer -
Julien -
Peter Lemenkov -
Victor Seva