[Puppet Users] Re: puppet mount and ascii code

[Choon Ming Goh]

Please ignore this. Figured out my issue! Silly mistake!

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/405dd416-ab3a-47c4-b858-4ad4345f5ca1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: puppet mount and ascii code

[Choon Ming Goh]

But when I do a puppet resource mount /mnt -e with the code below, it just 
works. Why would it failed in a puppet agent run but not in a puppet 
resource command?

mount { '/mnt':
  ensure => 'mounted',
  fstype => 'cifs',
  device => '//10.200.206.83/Installation\040Media',
  options=> 'credentials=/root/.smb_cred',
}



On Thursday, May 1, 2014 10:31:46 AM UTC+4, Choon Ming Goh wrote:
>
> Hi all, 
>
> I'm trying to mount a Windows file share on the Linux system. Changing 
> names are not possible as per client's policy. I'm trying with the code 
> below but presented with errors:
>
> class nas_storage ($username, $password, $domain, $naslocation) { 
>
> #replace the \ with / and whitespace with ascii 040 as fstab does not 
> accepts these characters
> $nasmount = regsubst(regsubst($naslocation, ' ', '040', 'G'), '\\', 
> '/', 'G')
> 
> file { '/root/.smb_cred':
>   ensure  => file,
>   content => 
> "username=${username}\npassword=${password}\ndomain=${domain}"
> }
> 
> mount { 'mount NAS storage':
>   ensure  => 'mounted',
>   device  => $nasmount,
>   fstype  => 'cifs',
>   target  => '/mnt',
>   options => "auto,credentials=/root/.smb_cred",
> }
> }
>
> Error: Parameter name failed on Mount[mount NAS storage]: name must not 
> contain whitespace: mount NAS storage at 
> /etc/puppetlabs/puppet/modules/nas_storage/manifests/init.pp:37
> Wrapped exception:
> name must not contain whitespace: mount NAS storage
>
> It says that whitespaces are not accepted but in /etc/fstab they do accept 
> the \040 as a whitespace replacement. Can anyone enlighten me?
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/11f29dd8-29cc-4e82-8fd1-60b2b9082be4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] puppet mount and ascii code

[Choon Ming Goh]

Hi all, 

I'm trying to mount a Windows file share on the Linux system. Changing 
names are not possible as per client's policy. I'm trying with the code 
below but presented with errors:

class nas_storage ($username, $password, $domain, $naslocation) { 

#replace the \ with / and whitespace with ascii 040 as fstab does not 
accepts these characters
$nasmount = regsubst(regsubst($naslocation, ' ', '040', 'G'), '\\', 
'/', 'G')

file { '/root/.smb_cred':
  ensure  => file,
  content => 
"username=${username}\npassword=${password}\ndomain=${domain}"
}

mount { 'mount NAS storage':
  ensure  => 'mounted',
  device  => $nasmount,
  fstype  => 'cifs',
  target  => '/mnt',
  options => "auto,credentials=/root/.smb_cred",
}
}

Error: Parameter name failed on Mount[mount NAS storage]: name must not 
contain whitespace: mount NAS storage at 
/etc/puppetlabs/puppet/modules/nas_storage/manifests/init.pp:37
Wrapped exception:
name must not contain whitespace: mount NAS storage

It says that whitespaces are not accepted but in /etc/fstab they do accept 
the \040 as a whitespace replacement. Can anyone enlighten me?

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/d62071e2-847e-4725-b0fd-4ed5356b0f75%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Powershell error 80040154, import-module, set-webconfigurationproperty

[Choon Ming Goh]

I did try to use the path C:\Windows\sysnative but Puppet complains the 
path does not exist. I'll give the poweshell module a go and see what is 
the outcome. 

On Tuesday, March 25, 2014 12:15:09 AM UTC+8, Josh Cooper wrote:
>
>
>
>
> On Sun, Mar 23, 2014 at 12:46 PM, krish 
> > wrote:
>
>> Just a hunch Windows 2008 R2 is 64 bit...
>>
>> http://docs.puppetlabs.com/windows/running.html#file-system-redirection-in-64-bit-windows-versions
>>
>> and another small check... wondering if puppet run is invoking a 
>> case-sensitive powershell? (less likely though)
>>
>>
>>
>>
>>  
>>
>> On Sun, Mar 23, 2014 at 8:31 PM, Choon Ming Goh 
>> 
>> > wrote:
>>
>>> Hi all,
>>>
>>> I'm currently trying to set some web configuration properties through 
>>> powershell using puppet but it is throwing me error. If I were to run the 
>>> commands directly on the powershell it works. I'm running this on a Windows 
>>> 2008 R2 server with WebServerRole. Please enlighten
>>>
>>>   exec { 'SEMS disable Basis Authentication':
>>> command => 
>>> 'C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe -executionpolicy 
>>> unrestricted -Command "Import-Module WebAdministration; 
>>> Set-WebConfigurationProperty -filter 
>>> /system.webServer/security/authentication/AnonymousAuthentication -name 
>>> enabled -location SEMS -value false"',
>>>
>>
> The "SysWOW64" will force puppet to execute the 32-bit version of 
> powershell. I am guessing that you wanted to use "sysnative" so that the 
> 64-bit version of powershell is executed?
>
> That said there is a powershell module on the forge that handles the 32/64 
> file system redirection issue: 
> http://forge.puppetlabs.com/joshcooper/powershell
>  
>
>>}
>>>
>>> Notice: Compiled catalog for win-uej5ngs6bua.docomointertouch.net in 
>>> environment production in 1.80 seconds
>>> Notice: /Stage[main]/Profile::Iis::Sems/Exec[SEMS disable Basis 
>>> Authentication]/returns: Set-WebConfigurationProperty : Retrieving the COM 
>>> class factory for component with CLSID 
>>> {6885-6A7E-422F-BE1-6AF00DC944A6} failed due to the following error: 
>>> 80040154.
>>> Notice: /Stage[main]/Profile::Iis::Sems/Exec[SEMS disable Basis 
>>> Authentication]/returns: At line:1 char:62
>>> Notice: /Stage[main]/Profile::Iis::Sems/Exec[SEMS disable Basis 
>>> Authentication]/returns: + Import-Module WebAdministration; 
>>> Set-WebConfigurationProperty <<<<  -filter 
>>> /system.webServer/security/authentication/AnonymousAuthentication -name 
>>> enabled -location SEMS -value false
>>> Notice: /Stage[main]/Profile::Iis::Sems/Exec[SEMS disable Basis 
>>> Authentication]/returns: + CategoryInfo  : NotSpecified: (:) 
>>> [Set-WebConfigurationProperty], COMException
>>> Notice: /Stage[main]/Profile::Iis::Sems/Exec[SEMS disable Basis 
>>> Authentication]/returns: + FullyQualifiedErrorId : 
>>> System.Runtime.InteropServices.COMException,Microsoft.IIs.PowerShell.Provider.SetConfigurationPropertyCommand
>>> Notice: /Stage[main]/Profile::Iis::Sems/Exec[SEMS disable Basis 
>>> Authentication]/returns:
>>> Error: C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe 
>>> -executionpolicy unrestricted -Command "Import-Module WebAdministration; 
>>> Set-WebConfigurationProperty -filter 
>>> /system.webServer/security/authentication/AnonymousAuthentication -name 
>>> enabled -location SEMS -value false" returned 1 instead of one of [0]
>>> Error: /Stage[main]/Profile::Iis::Sems/Exec[SEMS disable Basis 
>>> Authentication]/returns: change from notrun to 0 failed: 
>>> C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe -executionpolicy 
>>> unrestricted -Command "Import-Module WebAdministration; 
>>> Set-WebConfigurationProperty -filter 
>>> /system.webServer/security/authentication/AnonymousAuthentication -name 
>>> enabled -location SEMS -value false" returned 1 instead of one of [0] 
>>>
>>>   -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Puppet Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to puppet-users...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.co

[Puppet Users] Powershell error 80040154, import-module, set-webconfigurationproperty

[Choon Ming Goh]

Hi all,

I'm currently trying to set some web configuration properties through 
powershell using puppet but it is throwing me error. If I were to run the 
commands directly on the powershell it works. I'm running this on a Windows 
2008 R2 server with WebServerRole. Please enlighten

  exec { 'SEMS disable Basis Authentication':
command => 'C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe 
-executionpolicy unrestricted -Command "Import-Module WebAdministration; 
Set-WebConfigurationProperty -filter 
/system.webServer/security/authentication/AnonymousAuthentication -name 
enabled -location SEMS -value false"',
  }

Notice: Compiled catalog for win-uej5ngs6bua.docomointertouch.net in 
environment production in 1.80 seconds
Notice: /Stage[main]/Profile::Iis::Sems/Exec[SEMS disable Basis 
Authentication]/returns: Set-WebConfigurationProperty : Retrieving the COM 
class factory for component with CLSID 
{6885-6A7E-422F-BE1-6AF00DC944A6} failed due to the following error: 
80040154.
Notice: /Stage[main]/Profile::Iis::Sems/Exec[SEMS disable Basis 
Authentication]/returns: At line:1 char:62
Notice: /Stage[main]/Profile::Iis::Sems/Exec[SEMS disable Basis 
Authentication]/returns: + Import-Module WebAdministration; 
Set-WebConfigurationProperty   -filter 
/system.webServer/security/authentication/AnonymousAuthentication -name 
enabled -location SEMS -value false
Notice: /Stage[main]/Profile::Iis::Sems/Exec[SEMS disable Basis 
Authentication]/returns: + CategoryInfo  : NotSpecified: (:) 
[Set-WebConfigurationProperty], COMException
Notice: /Stage[main]/Profile::Iis::Sems/Exec[SEMS disable Basis 
Authentication]/returns: + FullyQualifiedErrorId : 
System.Runtime.InteropServices.COMException,Microsoft.IIs.PowerShell.Provider.SetConfigurationPropertyCommand
Notice: /Stage[main]/Profile::Iis::Sems/Exec[SEMS disable Basis 
Authentication]/returns:
Error: C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe 
-executionpolicy unrestricted -Command "Import-Module WebAdministration; 
Set-WebConfigurationProperty -filter 
/system.webServer/security/authentication/AnonymousAuthentication -name 
enabled -location SEMS -value false" returned 1 instead of one of [0]
Error: /Stage[main]/Profile::Iis::Sems/Exec[SEMS disable Basis 
Authentication]/returns: change from notrun to 0 failed: 
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe -executionpolicy 
unrestricted -Command "Import-Module WebAdministration; 
Set-WebConfigurationProperty -filter 
/system.webServer/security/authentication/AnonymousAuthentication -name 
enabled -location SEMS -value false" returned 1 instead of one of [0] 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/91f6c261-4a10-42bd-a428-83e0e20c71bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet 3 upgrade issue with auth.conf and fileserver.conf

[Choon Ming Goh]

I've found the root cause and the solution to this problem. I was using 
puppetlabs' puppet modules to setup puppet agent and puppet master. The 
whole setup puppetized the entire rack folder which contains config.ru.

The config.ru from the puppet module is the root cause as it does not match 
with the new config.ru which is used by puppet 3

### Puppet 2.7.x config.ru

# a config.ru, for use with every rack-compatible webserver.
# SSL needs to be handled outside this, though.

# if puppet is not in your RUBYLIB:
# $:.unshift('/opt/puppet/lib')

$0 = "master"

# if you want debugging:
# ARGV << "--debug"

ARGV << "--rack"
require 'puppet/application/master'
# we're usually running inside a Rack::Builder.new {} block,
# therefore we need to call run *here*.
run Puppet::Application[:master].run


### Puppet 3 config.ru
# a config.ru, for use with every rack-compatible webserver.
# SSL needs to be handled outside this, though.

# if puppet is not in your RUBYLIB:
# $LOAD_PATH.unshift('/opt/puppet/lib')

$0 = "master"

# if you want debugging:
# ARGV << "--debug"

ARGV << "--rack"

# Rack applications typically don't start as root.  Set --confdir and --vardir
# to prevent reading configuration from ~puppet/.puppet/puppet.conf and writing
# to ~puppet/.puppet
ARGV << "--confdir" << "/etc/puppet"
ARGV << "--vardir"  << "/var/lib/puppet"

# NOTE: it's unfortunate that we have to use the "CommandLine" class
#  here to launch the app, but it contains some initialization logic
#  (such as triggering the parsing of the config file) that is very
#  important.  We should do something less nasty here when we've
#  gotten our API and settings initialization logic cleaned up.
#
# Also note that the "$0 = master" line up near the top here is
#  the magic that allows the CommandLine class to know that it's
#  supposed to be running master.
#
# --cprice 2012-05-22

require 'puppet/util/command_line'
# we're usually running inside a Rack::Builder.new {} block,
# therefore we need to call run *here*.
run Puppet::Util::CommandLine.new.execute

Changing the config.ru resolved all my problems above


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet 3 upgrade issue with auth.conf and fileserver.conf

[Choon Ming Goh]

Hi guys,

I just upgraded my puppet 2.7.x to Puppet 3. Upgrade is smooth except for 
one thing. I'm getting the error below:

Warning: Unable to fetch my node definition, but the agent run will 
continue:
Warning: Error 403 on SERVER: Forbidden request: [hostname] access to 
/node/[hostname] [find] at :0
Info: Retrieving plugin
Error: /File[/var/lib/puppet/lib]: Failed to generate additional resources 
using 'eval_generate: Error 403 on SERVER: Forbidden request: [hostname] 
access to /file_metadata/plugins [search] at :0
Error: /File[/var/lib/puppet/lib]: Could not evaluate: Error 403 on SERVER: 
Forbidden request: [hostname] access to /file_metadata/plugins [find] at :0 
Could not retrieve file metadata for puppet://[hostname]/plugins: Error 403 
on SERVER: Forbidden request: [hostname] access to /file_metadata/plugins 
[find] at :0
Info: Loading facts in 
/etc/puppet/modules/augeas/lib/facter/augeasversion.rb
Info: Loading facts in 
/etc/puppet/modules/concat/lib/facter/concat_basedir.rb
Info: Loading facts in 
/etc/puppet/modules/firewall/lib/facter/ip6tables_version.rb
Info: Loading facts in 
/etc/puppet/modules/firewall/lib/facter/iptables_version.rb
Info: Loading facts in /etc/puppet/modules/mmm/lib/facter/ipaddresses.rb
Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/pe_version.rb
Info: Loading facts in 
/etc/puppet/modules/stdlib/lib/facter/puppet_vardir.rb
Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/root_home.rb
Info: Loading facts in /etc/puppet/modules/sudo/lib/facter/sudo.rb
Info: Loading facts in /etc/puppet/modules/xen/lib/facter/lvm_freespace.rb
Info: Loading facts in /var/lib/puppet/lib/facter/ip6tables_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/ipaddresses.rb
Info: Loading facts in /var/lib/puppet/lib/facter/lvm_freespace.rb
Info: Loading facts in /var/lib/puppet/lib/facter/sudo.rb
Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb
Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb
Info: Loading facts in /var/lib/puppet/lib/facter/iptables_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/concat_basedir.rb
Info: Loading facts in /var/lib/puppet/lib/facter/augeasversion.rb
Error: Could not retrieve catalog from remote server: Error 403 on SERVER: 
Forbidden request: [hostname] access to /catalog/[hostname] [find] at :0
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

I looked at the changelog and telly workarounds but still the same thing. 

Made sure all the source => 'puppet:///modules/x/x/'

 auth.conf

# allow nodes to retrieve their own node definition
path ~ ^/node/([^/]+)$
method find
allow $1

# allow nodes to retrieve their own catalog
path ~ ^/catalog/([^/]+)$
method find
allow $1

# allow all nodes to access the certificates services
path /certificate_revocation_list/ca
method find
allow *

# allow all nodes to store their reports
path /report
method save
allow *

# Allow all nodes to access all file services; this is necessary for
# pluginsync, file serving from modules, and file serving from custom
# mount points (see fileserver.conf). Note that the `/file` prefix matches
# requests to both the file_metadata and file_content paths. See "Examples"
# above if you need more granular access control for custom mount points.
path /file
allow *

path /plugins
allow *

### Unauthenticated ACLs, for clients without valid certificates; 
authenticated
### clients can also access these paths, though they rarely need to.

# allow access to the CA certificate; unauthenticated nodes need this
# in order to validate the puppet master's certificate
path /certificate/ca
auth any
method find
allow *

# allow nodes to retrieve the certificate they requested earlier
path /certificate/
auth any
method find
allow *

# allow nodes to request a new certificate
path /certificate_request
auth any
method find, save
allow *

# deny everything else; this ACL is not strictly necessary, but
# illustrates the default policy.
path /
auth any

path ~ ^/file_(metadata|content)/files/
auth yes
allow puppet.domain.com
allow 10.0.0.10

### fileserver.conf

# This file 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
[files]
  path /etc/puppet/files
#  allow *.example.com
  allow *

[plugins]
#  allow *.example.com
#  deny *.evil.example.com
#  allow 192.168.0.0/24
  allow *

What am I doing wrong here?

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http:

[Puppet Users] Re: Jenkins + Rspec + Puppet setup

[Choon Ming Goh]

This is the build configuration screenshot



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/2ruL5HIQo-8J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] erb syntaxes

[Choon Ming Goh]

Hey,

Thanks it works! Funny that it didnt work before this as I swore I tried it 
too. my luck maybe.

On Monday, September 3, 2012 12:14:54 PM UTC+8, Gonzalo wrote:
>
> On Mon, Sep 3, 2012 at 1:31 PM, Choon Ming Goh 
> 
> > wrote:
>
>> Hi guys,
>>
>> I'm trying to do the following in my template: 
>>
>>   location <%= location %> {
>> proxy_pass <%= proxy %>;
>> <% if scope.lookupvar('nginx::resource::location::proxy_header') then
>> scope.lookupvar('nginx::resource::location::proxy_header').each 
>> do |header| %>
>> proxy_set_header <%= header %>
>> <% end %>
>>
>
> Not sure if this is it, but try adding another <% end %> as you have an 
> "if" statement and a "do" block to close.
>
> - Gonzalo
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/RsZd0U66mlgJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] erb syntaxes

[Choon Ming Goh]

Hi guys,

I'm trying to do the following in my template: 

  location <%= location %> {
proxy_pass <%= proxy %>;
<% if scope.lookupvar('nginx::resource::location::proxy_header') then
scope.lookupvar('nginx::resource::location::proxy_header').each do 
|header| %>
proxy_set_header <%= header %>
<% end %>
  }

But i'm getting this error instead:

err: Could not retrieve catalog from remote server: Error 400 on SERVER: 
compile error
/etc/puppet/modules/nginx/templates/vhost/vhost_location_proxy.erb:9: 
syntax error, unexpected $end, expecting kEND
; _erbout
 ^
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run

I've tried changing to 

<% if scope.lookupvar('nginx::resource::location::proxy_header') 
scope.lookupvar('nginx::resource::location::proxy_header').each do 
|header| %>

and

<% if scope.lookupvar('nginx::resource::location::proxy_header') %>
<% scope.lookupvar('nginx::resource::location::proxy_header').each 
do |header| %>

and

<% if scope.lookupvar('nginx::resource::location::proxy_header') 
then scope.lookupvar('nginx::resource::location::proxy_header').each do 
|header| %>

but none of these are working. Any pointers are definitely appreciated

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/MTSFB6oGybYJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] puppetlabs jenkins setup

[Choon Ming Goh]

Hi,

I'm in the middle of setting up jenkins for testing and building our puppet 
modules. I'm quite new at this and been trying to make it work the way i 
wanted but in reality it doesnt. There are a few issues/questions that I 
hope someone in puppetlabs/jenkins can help me with:

1. module dependency - how do I build and test modules is dependent on 
another module that is being built at the same time using rspec in jenkins. 
The good example is rtyler's jenkins module

2. how can I have jenkins to create a tarball of the module and made it 
available for download whenever I click on the builds?

This is what I can think of for now and if anyone have an idea please do 
help.

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/n1qm-r0y5UAJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Live management and manifests

[Choon Ming Goh]

Is there anyway to make it overlap or there simply isnt any? From what I 
can assume, if a user manages a resource via Live Management and wants it 
to be in the manifests, the user must remember or must put it in on their 
own accord?

On Monday, July 23, 2012 11:58:26 PM UTC+8, Daniel Sauble wrote:
>
> We make a distinction between resources managed with Puppet manifests and 
> resources managed with Live Management. Puppet manifests enforce a 
> particular state whenever puppet is run, while Live Management enforces a 
> state once--when cloning is performed. There isn't any overlap. Live 
> Management cannot be used to clone resources that are already managed with 
> Puppet manifests, and the manifests themselves aren't changed when 
> resources are cloned.
>
> Hope this helps!
> - Daniel
>
> On Sun, Jul 22, 2012 at 9:46 PM, Choon Ming Goh 
> wrote:
>
>> Hi all,
>>
>> I have this question which have been nagging me for a while now. The live 
>> management features in the PE allows one to manage the resources on the fly 
>> without having to the need to write manifests. The users can clone / update 
>> / manage resources in any way permitted they want. How does this works with 
>> the manifests that are written by the users?
>>
>> Lets say my site.pp have node definition that says to include the nginx 
>> class for node A. Then I would use the live management to clone the 
>> resources for the nginx class from node A to node B and C. How will this 
>> reflect into my manifests as I already have node A, B and C defined in my 
>> site.pp?
>>
>> Hope this is clear enough.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Puppet Users" group.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msg/puppet-users/-/w30A9URz9A0J.
>> To post to this group, send email to puppet-users@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> puppet-users+unsubscr...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/puppet-users?hl=en.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/7fb_U12tIykJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Live management and manifests

[Choon Ming Goh]

Hi all,

I have this question which have been nagging me for a while now. The live 
management features in the PE allows one to manage the resources on the fly 
without having to the need to write manifests. The users can clone / update 
/ manage resources in any way permitted they want. How does this works with 
the manifests that are written by the users?

Lets say my site.pp have node definition that says to include the nginx 
class for node A. Then I would use the live management to clone the 
resources for the nginx class from node A to node B and C. How will this 
reflect into my manifests as I already have node A, B and C defined in my 
site.pp?

Hope this is clear enough.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/w30A9URz9A0J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.