search for: manifests

...pe/common-post-chroot.ks create mode 100644 recipe/custom-template.ks diff --git a/recipe/common-manifest-post.ks b/recipe/common-manifest-post.ks new file mode 100644 index 0000000..020f3a0 --- /dev/null +++ b/recipe/common-manifest-post.ks @@ -0,0 +1,31 @@ +%post +# Create post-image processing manifests +manifests=/tmp/manifests +mkdir -p $manifests +rpm -qa --qf '%{name}-%{version}-%{release}.%{arch}\n' | sort \ + > $manifests/rpm-manifest-post.txt +rpm -qa --qf '%{sourcerpm}\n' | sort -u > $manifests/srpm-manifest-post.txt +du -akx --exclude=/var/cache/yum / > $manife...

So I'm new to using wine. I recently purchased a used macbook, and installed wine to see if I could get System Architect 3.0 to run. System Architect is a program to allow plugging into various amplifiers and dbx Driverack units to make changes on your computer more than what you can do on the limited menu of the unit. Installing wine was fine (I used macports to install), and upon trying to

...Not authorized to call find on /file_metadata/acadaca/yum/pluginconf.d/priorities.conf Could not retrieve file metadata for puppet:///acadaca/yum/pluginconf.d/priorities.conf: Error 400 on SERVER: Not authorized to call find on /file_metadata/acadaca/yum/pluginconf.d/priorities.conf at /etc/puppet/manifests/classes/basefiles.pp:16 err: //basefiles/File[/etc/ldap.conf]: Failed to retrieve current state of resource: Error 400 on SERVER: Not authorized to call find on /file_metadata/acadaca/ldap.conf Could not retrieve file metadata for puppet:///acadaca/ldap.conf: Error 400 on SERVER: Not authorized to...

I was using Photoshop CS5 on my Ubuntu 11.04 system fine. I did an update of wine, now it won't work. I have tried to uninstall and reinstall wine, and copied the PS install from windows, it still has errors. > -desktop:~$ wine "c:\Program Files\Adobe\Adobe Photoshop CS5\Photoshop.exe" > wine: Call from 0x7b839f22 to unimplemented function msvcp90.dll.??0?$basic_string at

Hi As I''m more familiar with cfengine and it''s way to split updates (in update.conf) from the actual grunt work (in cfagent.conf), I''m wondering how to best manage puppet and my manifests with puppet...? Should I define a puppet class that copy the puppet package (in .tgz format) and all the manifests to the client, and then have all my other classes depend on that (sort of what I do now, except that it only copies the manifests - not the puppet package, and I haven''...

...t and nothing works. There''s also no reference at all to any environment in debugging mode when I run "puppetd --test -- environment=test -d". Am I missing something? Here''s a copy of my puppet.conf file: [main] vardir = /var/lib/puppet manifest = /etc/puppet/manifests/site.pp modulepath = /etc/puppet/modules pluginsync = true storeconfigs = true # dbadapter = mysql dbuser = puppet dbpassword = **** dbserver = mysql.example.com [puppetmasterd] certname=puppet.example.com [testing] manifest=/etc/puppet-testing/manifests/si...

Hi, I want to validate my puppet manifests before I check them into source control. I just want to make sure that the manifest syntaxes are legal, not to do any more complex testing - the checkin may be on my laptop and not on the system that the manifests may be intended to run on. Ideally I''d be able to do this from ruby code -...

This series fixes and enhances parsing of the OVA manifest file. The changes are: - Added mandatory space to the regexp - Process all lines in the file, not just one - Warn on improperly formated lines - Support SHA256 hashes v1 -> v2: rebased on to master to make use of the Checksums module Tomáš Golembiovský (2): v2v: ova: fix checking of the manifest file v2v: ova: support SHA256

Hi, I am using a template to create an /etc/exports file. I have a template that looks like this (but results in the puppetmasterd dying on the server when the client updates): <% nfsHomeClients.split.each do |host| -%> /nfs <%= host %>(<%= mainshareoptions %>) <% nfspaths.each do |path| -%> <%= path %> <%= host %>(<%= nfsoptions %>) <% end

I also made the changes below in the puppet.conf file to tell puppet where to look for the the modules and manifests. I then restart the puppet master then ran puppet command to apply changes to a puppet client it did not find anything to change just got these three lines "info: Caching catalog for pdlnx-adpt03.kareoprod.ent, info: Applying configuration version ''1362084986'', notice: F...

--- MANIFEST | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/MANIFEST b/MANIFEST index 13897af..3489ff1 100644 --- a/MANIFEST +++ b/MANIFEST @@ -18,6 +18,7 @@ MANIFEST This list of files MANIFEST.SKIP META.yml po/es.po +po/fr.po po/it.po po/Makefile po/PACKAGE -- 1.6.5.2

...consists of arbitrarily named sections/modules # defining where files are served from and to whom # Define a section ''files'' # Adapt the allow/deny settings to your needs. Order # for allow/deny does not matter, allow always takes precedence # over deny [snjh] path /etc/puppet/manifests/files/snjh allow *.summitnjhome.com # deny *.evil.example.com # allow 192.168.0.0/24 Here is the class manifest I am using: class basefiles { file { "/etc/ldap.conf": source => "puppet://puppet/snjh/ldap.conf" } file { "/etc/haha.txt": so...

...File ["/etc/postfix/main.cf"] { content => template(''jay/etc/postfix/main.cf.erb'') } } # puppet agent -t --noop err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find scope for jay::postfix at /etc/puppet/nodes/jay/manifests/init.pp:2 on node jay.foo.com warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run Or this: node "jay.foo.com" inherits nodes_base { # include jay File ["/etc/postfix/main.cf"] { content => template(''jay/etc/pos...

This series fixes and enhances parsing of the OVA manifest file. The changes are: - Added mandatory space to the regexp - Process all lines in the file, not just one - Warn on improperly formated lines - Support SHA256 hashes v1 -> v2: rebased on to master to make use of the Checksums module v2 -> v3: - changed debug/warning messages in first patch according to Richard's suggestions

...-print | grep -v .svn . ./plugins ./plugins/lines.pp ./files ./files/module ./files/module/SSH ./files/module/SSH/ssh_config ./files/module/SSH/sshd_config ./files/module/INFO ./files/module/INFO/motd ./files/module/INFO/issue ./files/module/NIS ./files/module/NIS/nsswitch.conf ./fileserver.conf ./manifests ./manifests/nodes.pp ./manifests/site.pp ./manifests/templates.pp ./puppet.conf ./modules ./modules/ssh ./modules/ssh/manifests ./modules/ssh/manifests/ssh.pp ./modules/ssh/manifests/init.pp ./modules/baseline ./modules/baseline/plugins ./modules/baseline/plugins/puppet ./modules/baseline/plugins/p...

...In my puppet.conf file I have setup an environment called "stable", within this environment I have setup the manifestdir, modulepath and manifest settings like so: ------------------------- (Begin Extract) -------------------------------- [stable] *manifestdir*=/srv/puppetmaster/stable/manifests:* /srv/puppetmaster/stable/site-nodes* modulepath=/srv/puppetmaster/stable/modules:/srv/puppetmaster/stable/site-modules *manifest=/srv/puppetmaster/stable/manifests/site.pp* ------------------------- (End Extract) -------------------------------- If I run a config print against the manifestd...

This series fixes and enhances parsing of the OVA manifest file. The changes are: - Added mandatory space to the regexp - Process all lines in the file, not just one - Warn on improperly formated lines - Support SHA256 hashes v1 -> v2: rebased on to master to make use of the Checksums module v2 -> v3: - changed debug/warning messages in first patch according to Richard's suggestions

...ndard way (ie. in a server/client configuration), just the standalone ''puppet --use-nodes'' command. I''m having problems with the directory structure of modules and using the import feature. My directory infrastructure looks like this: /srv/puppet/facter/... /srv/puppet/manifests/site.pp /srv/puppet/manifests/libs/file.pp /srv/puppet/manifests/libs/security.pp /srv/puppet/manifests/templates/.... /srv/puppet/manifests/classes/... /srv/puppet/manifests/packages/... within the site.pp I have a import "libs/file" and within the file.pp file I had import "securi...

The regular expression for parsing the manifest line was wrong. There is a mandatory space between '=' and the hash. Another problem was that only the first line of the manifest file was actually processed. Also added some debugging info and warning to catch problems with parsing. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/input_ova.ml | 8 +++++++- 1 file

...uppet version 0.20.0 info: Parsed manifest in 0.02 seconds info: /var/lib/puppet/files: allowing *.example.org access info: Listening on port 8140 notice: Starting Puppet server version 0.20.0 info: Creating PID file to /var/run/puppet/puppetmasterd.pid info: Found protos.example.org in /etc/puppet/manifests/site.pp notice: Compiled configuration for protos.example.org in 0.01 seconds But if I change any part of the manifest and try to run the client again I obtain the following: notice: Reloading files err: Permission denied - /root in file /etc/puppet/manifests/site.pp at line 14 where line 14 con...