Hi, Alessandro Francesch:
I am just use Puppi, it's dont work!
my configuration:
server
/etc/puppet/modules/puppi/manifests/init.pp
add
puppi::project::builder { "tengine":
source => "svn://tvmining:[email protected]/product/
tengine",
source_type => "dir",
deploy_root => "/opt/tvm",
user => "tvm",
predeploy_customcommand => '',
predeploy_user => '',
postdeploy_customcommand => '',
postdeploy_user => '',
run_checks => "true",
backup => "full",
backup_retention => "10",
enable => "true",
}
I'm execute the command 'puppetmasterd --debug --no-daemonize' , it's
not error
client
I'm execute the command 'puppetd --debug --no-daemonize', it's error.
debug: /Stage[main]/Puppi::Logs/Puppi::Log[mail]/File[/etc/puppi/logs/
mail]: Autorequiring File[puppi_logsdir]
debug: /Stage[main]/Puppi::Logs/Puppi::Log[mail]/File[/etc/puppi/logs/
mail]: Autorequiring User[root]
debug: /Stage[main]/Puppi::Infos/Puppi::Info::Module[puppi]/File[/etc/
puppi/info/puppi]: Autorequiring File[puppi_infodir]
debug: /Stage[main]/Puppi::Infos/Puppi::Info::Module[puppi]/File[/etc/
puppi/info/puppi]: Autorequiring User[root]
err: Could not apply complete catalog: Found 1 dependency cycle:
(Class[Puppi] => File[/etc/puppi/projects/tengine/deploy/40-tengine-
Deploy] => Puppi::Deploy[tengine-Deploy] =>
Puppi::Project::Builder[tengine] => Class[Puppi])
Try the '--graph' option and opening the resulting '.dot' file in
OmniGraffle or GraphViz
Can you help me? Thanks.
On Dec 26 2011, 9:48 pm, Alessandro Franceschi <[email protected]> wrote:
> Puppi<http://example42.com/?q=Puppi_A_Puppet_module_for_Deployment_Automation>
> (more
> info here <http://example42.com/?q=puppi_deployments> download from
> here<https://github.com/example42/puppi>)
> is a Puppet module made exactly for application deployments.
> You can deploy war files with a define like:
> puppi::project::war { "myapp":
> source => "http://repo.example42.com/deploy/prod/myapp.war",
> deploy_root => "/store/tomcat/myapp/webapps",
> report_email => "[email protected]",
>
> }
>
> Want to restart tomcat to avoid hot deploys? Add the argument:
> init_script => "tomcat",
>
> Want to run a custom script before (or after) the deployment? Add
> predeploy_command => "/path/to/my/script.sh",
>
> Note that the above define makes you able, on from the host where you
> defined the resource, to issue the command (via shell, collective, cron job
> or at the end of a continuous deployment procedure) :
> *puppi deploy myapp*
>
> If you want to perform the deployment directly during the puppet run, you
> should add the define:
> puppi::run { "myapp": }
>
> And, btw, there are puppy defines to manage, in a similar direct and easy
> way, deployments of tar balls, zip archives, files from a given list,
> artifacts built by Maven and son on...
>
> Hope it helps
> Al
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.