Also I was thinking what some one can do if I give him a machine which has all the packages installed. Dont we need some good case studies/example configurations which should be part of the project.


-Jai

On Dec 17, 2007 9:44 AM, Jai Rangi <jprangi@gmail.com> wrote:

1) Determine what needs to be on the basic CentOS 5 install for
everything to work properly (including iptables and such since we should
assume security is an important factor).
2) Determine what's left that needs to be installed that doesn't come
with the distro for any base dependencies.
3) Determine the order in which the apps need to be installed (for the
post-proc. script).

This sounds good approach. The only thing I see is that be might be going 2->3->2->3->... few times before we get the final version of 2. Ofcourse this assumes that all the dependencies should be the default/latest versions of packages from CentOS CD.

-Jai



On Dec 17, 2007 6:16 AM, SIP <sip@arcdiv.com> wrote:
Okay... starting with a base image of CentOS 5 (which, I believe,
includes MySQL 5.0.? Don't recall which version... perhaps someone can
fill in there), what are the initial things that would need to be
installed for base-level dependencies (things not already on the machine
and ready to go).

Then, we should start a list of what needs to be installed based on the
order in which it should be installed (for the post-processing script)
for the basic required stuff.

Also, for any optional packages that will be installed, we'll need a
list of dependencies.

I think that's a logical next step assuming the CentOS machine has been
installed (which is NOT an assumption we should overlook, as we'll need
to determine what portions of the CentOS base machine SHOULD and should
NOT be installed (i.e. do we really need print services, games, and an X
environment in our base install, etc, etc)).

SO....  three steps really.

1) Determine what needs to be on the basic CentOS 5 install for
everything to work properly (including iptables and such since we should
assume security is an important factor).
2) Determine what's left that needs to be installed that doesn't come
with the distro for any base dependencies.
3) Determine the order in which the apps need to be installed (for the
post-proc. script).



I'm just throwing out ideas here. Feel free to tell me I'm going about
this the wrong way.

N.


Greger V. Teigre wrote:
> :-) we only need to get this thing together then...
> g-)
>
> ram wrote:
>>
>>
>> On Dec 16, 2007 1:33 PM, Greger V. Teigre < greger@teigre.com
>> <mailto:greger@teigre.com>> wrote:
>>
>>     Using kickstart sounds good to me.  I think we should keep
>>     separate the different steps:
>>     1. Create a base image of the OS
>>     2. Install the iptel.org < http://iptel.org/> apps and dependencies
>>     3. Do local configurations
>>     4. Create deployable virtual machine
>>
>>     If each of these steps are isolated, different people can be
>>     responsible for the different steps.
>>
>>     I have reorganized the project page into sections and
>>     incorporated lots of input from Jeremy at
>>     http://iptel.org/bundle/project
>>     We now need to create a project plan, split into
>>     responsibilities, and take some key decisions.
>>     I think one key decision that we have already converged on is:
>>     for first version use CentOS5 and create vmware appliance.
>>     g-)
>>
>>
>>
>> I have Server ready with Centos5
>>
>> let me know any test need to be done
>>
>> ram
>>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Serusers mailing list
> Serusers@lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
>

_______________________________________________
Serusers mailing list
Serusers@lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers