<div>All,</div>
<div> </div>
<div>This discussion can be endless if we keep planning about the features. Hey how about this, hey this will be cool, I use that tool, we must have it and list keeps going on. </div>
<div>I would say lets start working. </div>
<div>1. Take any version of OS. </div>
<div>2. Install all basic packages for a server edition. </div>
<div>3. Install and document the prereqs for ser (Source)+sems (source) +mysql (RPM)+ serweb (Source)+serctl (source)+sipp (Source) +sipsak (Source/RPM). </div>
<div>4. To make it easy for every one, all these surces should with with the defaults RPMs installed by the Linux version. </div>
<div>5. Make sure we installed everythign in /usr/local/ with a --prefix option for all the packages. Another option can be add a user/group ser and installed everything in ~ser/install directory. </div>
<div> </div>
<div>Once we have this working, then we can go on the next items in the list. Lots of things in the list are installed by Default </div>
<div> </div>
<div>Once we have this, we can build the ks.cfg file with a post installation script that will take care of step 3). There goes the testing phase and rebuilding phase with additional packages. </div>
<div> </div>
<div>My 2 cents. </div>
<div> </div>
<div>-Jai</div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
<div><br><br> </div>
<div class="gmail_quote">On Thu, Feb 28, 2008 at 10:47 AM, SIP <<a href="mailto:sip@arcdiv.com">sip@arcdiv.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">While I'm all for being distro-agnostic, as we're looking to build an<br>ISO that you boot from and that installs all the necessary stuff to get<br>
up and running, we have to pick one -- hence the choice. This way, we<br>can ensure that the base system built is guaranteed to have all the<br>pre-requisites, the libraries we KNOW will function without issue, the<br>settings which make sense for a SER system, etc.<br>
<br>Building an installable package on a random system can run you into<br>every sysadmin's least favourite pasttime -- hunting down the numerous<br>pre-requisites, installing them, and working through the conflicts.<br>
<br>I'm all for a script that activates the build-system on<br>bootstrap/post-install so it can build an oob cfg for the box in<br>question. I just wanted to point out that that's one of the things<br>needing doing. :)<br>
<br>N.<br>
<div>
<div></div>
<div class="Wj3C7c"><br><br>Greger Viken Teigre wrote:<br>> I would just suggest that you try to stay as distro-independent as<br>> possible, i.e. make it easy to switch to another distro and make it<br>> easy for people to bootstrap on another distro by looking at the<br>
> dependencies (and maybe contribute their bootstrap script :-).<br>><br>> As for config file, the ser-oob.cfg and ser.cfg that is generated by<br>> the buildsystem (sip_router/etc/buildsystem) are quite close. The<br>
> buildsystem has a configure script that can be run as part of the<br>> bootstrap (it creates an m4 config file for local) or a web-based<br>> front-end can generate the config file quite easily.<br>> As I'm the maintainer of the buildsystem, I can promise some support<br>
> if the system needs some adaption or the config file needs updating.<br>> I cannot speak for ser-oob.cfg, but as the idea is to show-case the<br>> <a href="http://iptel.org/" target="_blank">iptel.org</a> free SIP service config, I assume it will be more static.<br>
><br>> See config buildsystem docs:<br>> <a href="http://www.iptel.org/sip_express_router_configuration_buildsystem" target="_blank">http://www.iptel.org/sip_express_router_configuration_buildsystem</a><br>><br>
> I'll follow the discussions and contribute where and when I can.<br>> g-)<br>><br>> SIP wrote:<br>>> If no one else is going to come forward and second/debate Mike's<br>>> suggestion to use FC, and Mike's the man with the server, then I declare<br>
>> this project officially FC-based.<br>>><br>>> These are the people that have so far contacted me and are verified for<br>>> working on the SER Bundle Project, and for what tasks I have them available:<br>
>><br>>> Jai Rangi -- kickstart work in FC<br>>> Arun Kumar -- flexible<br>>> Samuel -- some time/flexible<br>>> ram -- testing<br>>> Mike Trest -- server, testing, FC wrangling<br>
>><br>>> Tasks we still need to fill (some of which can be filled perhaps by the<br>>> people listed above as flexible or others in the project):<br>>><br>>> Core:<br>>> -SERWeb install/config<br>
>> -RTP Proxy install/config (for base RTP proxy package -- not strictly<br>>> SER config)<br>>> -SEMS w/voicemail, away announcement, and conferencing support<br>>> install/config<br>>><br>>> Tools:<br>
>> All tools (ser_ctl, sipsak, tcpdump/ngrep, wireshark/tshark, sipp,<br>>> sip_scenario, spyagent+sipspy<br>>><br>>> Also, with no install package for SER with a basic config, SER itself<br>>> will have to be installed/scripted to install with a tailored<br>
>> config(ser-oob.cfg) for the correct system/parameters. I'm ASSUMING that<br>>> will go into the basic core install scripts, so I didn't add it in up<br>>> there, but if this is an invalid assumption, someone has to let me know<br>
>><br>>><br>>> As you can see, if you're interested in being a part of this project and<br>>> can contribute time to getting it going, there are plenty of areas left<br>>> where we need people to help. Just let me know, and I'll add you to the<br>
>> list.<br>>><br>>><br>>><br>>> N.<br>>><br>>><br>>> Neil Fusillo wrote:<br>>><br>>>> As long as the environment can be built to be stable, I'm in complete<br>
>>> agreement. While our initial adopters may be the tinkerers and the<br>>>> risk-takers, I'd say that a good number of those people already try out<br>>>> SER (and may ultimately choose something with less of a learning<br>
>>> curve). The biggest market for a SER bundle in the long run is going to<br>>>> be those who want to get a carrier grade SIP proxy up and running<br>>>> quickly and easily. Who that might be is somewhat difficult to<br>
>>> determine, but I dare say we don't want to position ourselves as<br>>>> building a bundle for those who're willing to take risks. ;)<br>>>><br>>>> That said, the decision for CentOS came about because it is simply a<br>
>>> GPL-compliant duplicate distro of Red Hat Enterprise Linux -- the single<br>>>> most common and most popular distribution amongst people who run linux<br>>>> in a carrier-grade situation.<br>
>>><br>>>> Fedora Core, being the test bed for RHEL, has the same structure but<br>>>> newer, slightly less-vetted packages. However, if we can ensure<br>>>> stability, then none of that matters and no one will really care what<br>
>>> distro it's built upon (as long as it's familiar to the admins who<br>>>> manage it). If you say you can build a stable FC-based SER server, then<br>>>> I say we go for it.<br>>>><br>
>>> Do we have a second to Mike's motion to use FC as the base distro?<br>>>><br>>>><br>>>> Mike Trest - Personal wrote:<br>>>><br>>>><br>>>>> Hi,<br>>>>><br>
>>>> This is to summarize my opinions about FC* distro use.<br>>>>><br>>>>> IMHO, I think FC* is best selection as it contains many more fixes<br>>>>> than does the older CENTOS (based on 5). I have deployed several<br>
>>>> hundred FC* boxes in VoIP applications. This is over 10,000 active<br>>>>> ports without "Enterprise" stability issues.<br>>>>><br>>>>> IMHO this project needs the quickest path to the Enterprise community<br>
>>>> regardless of the OS/distro used.<br>>>>><br>>>>> I suppose the ultimate question is who is our target? Ourselves,<br>>>>> naturally. However, I suggest our target is not the bankers or<br>
>>>> major corporations with lots of rules and procedures. That group<br>>>>> will never adopt SER until they have a commercial-grade support<br>>>>> system to advise their IT folks what to do for every question they may have.<br>
>>>><br>>>>> IMHO our initial target is those early adopters who are trying to<br>>>>> create new businesses in telecomm or consulting-on-telecom. We want<br>>>>> them to have a solid core that they can leverage into their new<br>
>>>> appliances and specialized applications.<br>>>>><br>>>>> The early adopters are risk-takers (This means us as well!) They<br>>>>> demand an open box in which they can face the SIP world with some<br>
>>>> assurance of standards compliance while at the same time they can<br>>>>> face their clients with something better, faster, cheaper, and<br>>>>> innovative enough to get paid well for their efforts.<br>
>>>><br>>>>> Making a technology "buy - in" decision at any point in time is only<br>>>>> a check point - not a final resting place. IMHO, we are better off<br>>>>> selecting an OS/distro effort that has a large share of both early<br>
>>>> adopters and long term commercial support - - - so long as it meets<br>>>>> our current and future technical **AND** target market<br>>>>> requirements. Research confirms that the RH/FC community is the<br>
>>>> largest community with name recognition and respect among both the<br>>>>> "geek-innovator" community as well as the Enterprise community.<br>>>>><br>>>>> ..mike..<br>
>>>><br>>>>> _______________________________________________<br>>>>> Serusers mailing list<br>>>>> <a href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org</a><br>
>>>> <a href="http://lists.iptel.org/mailman/listinfo/serusers" target="_blank">http://lists.iptel.org/mailman/listinfo/serusers</a><br>>>>><br>>>>><br>>>>><br>>>><br>
>>><br>>><br>>> _______________________________________________<br>>> Serusers mailing list<br>>> <a href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org</a><br>>> <a href="http://lists.iptel.org/mailman/listinfo/serusers" target="_blank">http://lists.iptel.org/mailman/listinfo/serusers</a><br>
>><br>>><br>>><br><br>_______________________________________________<br>Serusers mailing list<br><a href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org</a><br><a href="http://lists.iptel.org/mailman/listinfo/serusers" target="_blank">http://lists.iptel.org/mailman/listinfo/serusers</a><br>
</div></div></blockquote></div><br>