Hi Julio,
thank you for your prompt answer.

I'm convinced that SmartFrog with its flexibility could be the right solution 
for our big problem.

I can give you an example of the architecture we have and the problems we are 
facing.

We have a big portal that consist of 10-15 applications that work toghether.

These applications need to be deployed on average on 10 boxes.
so application A has to be deployed on serv1, serv2....serv10
appl B has to be deployed on serv30, serv31....serv40


Each of these application has property files.
We can take an average of 100 property tokens for each application.
The token has to be replaced at the startup of the application in the config 
files.

We need a way to manage this token.
We have tokens that are commons to all the environent, other that have 
different values for different environment.
so probably we need a DB to store this values and an interface to manage, add 
new one...etc...

We have 2-3 release per each environment per week.
So we have a very huge amoount of deployment activities and risk to loose token 
values.
Because, due to time pressure, guys from operation change values directly on 
the boxes.

We want a way to avoid this.

So, from what you said, we need:

- to create templates for each component

- customize this templates in order to get correct values from the token 
database.

- use scripts to deploy on enviroment.

In your opinion is it possible to create logical entities like:

- projects

- enviroment

- hosts

- component

- tokens for each component

?????
Hope that my explanation is clear enough.

Hope to hear from you soon

have a nice week start
Regards

Andrea







---------- Initial Header -----------

>From      : "Guijarro, Julio" [EMAIL PROTECTED]
To          : "[EMAIL PROTECTED]" [EMAIL PROTECTED],"smartfrog-users" 
[email protected]
Cc          : 
Date      : Thu, 15 May 2008 16:05:34 +0000
Subject : RE: [Smartfrog-users] info request







> Hi Andrea,
> 
> Welcome to the list.
> 
> One of the main design goals for SmartFrog is to simplify the configuration 
> of large systems and to use SmartFrog to configure and manage a system like 
> the one you are describing you would have to (in general terms):
> 
> 1. Wrap the application software with SmartFrog components that can interpret 
> and pass right configuration parameters.
>         - In your case, probably, it would be just creating templates for the 
> shell scripting component to start/stop your software with the right      
> configuration.
>         - If your application configuration has to be expressed in the form 
> of "property files" then you will need to add a simple component to         
> create/modify those files based on the configuration attribute/value pairs 
> provided via the SmartFrog language.
> 
> 2. Write the configuration templates for those software components, modelling 
> their configuration information in the SF language.
> 
> 3. Describe the application lifecycle using 1 and 2 and probably some extra 
> components to describe how the software is copied to the remoted machines are 
> to verify that those machines have the right config and status.
> 
> A good example for this type of setup is the "Dynamic Webserver Example". In 
> this example we show how to install configure and manage several instances of 
> Apache web server. The example shows you how to for example start/stop 
> "apached" using the shell scripting component, how to read the number of 
> threads used by apached, how to copy and unzip the server in the destination 
> machine and so on.
> 
> This example is part of the complete SF distribution. For more information 
> about how to use it:
> 
> Overview doc:
> http://smartfrog.svn.sourceforge.net/viewvc/*checkout*/smartfrog/trunk/core/smartfrog/docs/sfDynamicWebServerExample.pdf
> 
> How to set it up:
> http://wiki.smartfrog.org/wiki/display/sf/Dynamic+Web+Server
> 
> 
> In summary going through your list:
> 
> - we need to manage properties in a proper way. We can have property value 
> for one configuration and another one for another configuration.
> we want to store information about each property with description and 
> documentation
> 
> >> Model all this once in SF language and reuse after (templating)
> 
> - we need to have automatic deployment
> 
> >> Deploy using a SF description
> 
> - to deploy on multiple boxes multiple applications
> 
> >> No problem. You can either doing by having an SF daemon in those machines 
> >> or by using ssh/tftp from a remote one. Your choice.
> 
> - to have an inventory system for all the boxes
> 
> >> You will need to add some components to do this and it will be specific to 
> >> you application. Nonetheless we have standard components that can access 
> >> to DBs and so on that can be extended and reused.
> 
> - a sort of sanity check
> 
> >> Same as previous point.
> 
> 
> If you need help in trying to understand how everything fits together send us 
> a simplified example that could help you to evaluate the feasibility of a 
> SmartFrog based solution and we will help you to get it done.
> 
> Regards,
> 
> Julio Guijarro
> 
> 
> 
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL 
> PROTECTED]
> Sent: 15 May 2008 14:03
> To: smartfrog-users
> Subject: [Smartfrog-users] info request
> Sensitivity: Confidential
> 
> hi all,
> i'm working for a big telco company.
> 
> We stated that we want to optimize our deployment phase, cause at the moment 
> we are facing lot of problems.
> 
> Currently, we receive the release of the software and then we deploy using a 
> perl script.
> 
> We have to deploy on severla boxes with different configuration.
> configuration and configuration properties are the biggest problem.
> Operation need waste a lot of time configuring the application.
> 
> 
> We want to understand if Smart Frog can help us in this challenge.
> 
> So our requirements are:
> 
> - we need to manage properties in a proper way. We can have property value 
> for one configuration and another one for another configuration.
> we want to store information about each property with description and 
> documentation
> 
> - we need to have automatic deployment
> 
> - to deploy on multiple boxes multiple applications
> 
> - to have an inventory system for all the boxes
> 
> - a sort of sanity check
> 
> Can someone explain me at high level point of view how to achieve this 
> results???
> 
> thanks
> Regards
> 
> andrea vavassori
> 
> 
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Smartfrog-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/smartfrog-users
> 


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Smartfrog-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/smartfrog-users

Reply via email to