Re: [Puppet Users] puppet cert list yields no certs

[Matt Zagrabelny]

On Thu, Jan 7, 2016 at 5:35 PM, Peter Kristolaitis  wrote:
> Apparently I was a little too quick on the send button.  :(
>
> To continue my previous email:
>
> Does 'puppet cert list --all' show any certs at all?

Yep:

# puppet cert list --all
+ "puppet-client-1.example.net" (SHA256)
A3:73:DC:89:B2:13:D4:C5:7A:58:B9:EB:7E:6A:22:1C:36:97:BD:8F:4C:AD:18:39:2E:F8:10:2C:29:36:F6:82
+ "puppet-3-7.example.net" (SHA256)
E6:F6:7D:6C:D8:30:6C:AC:1E:B5:5D:29:E8:11:0C:CB:54:22:BA:B3:96:C1:E2:49:7A:48:CF:3E:F8:12:43:24
(alt names: "DNS:puppet-3-7", "DNS:puppet-3-7.example.net")

I don't remember what I did to get the master to accept the CSR of
puppet-client-1 earlier, but I did have similar issues where I ran the
client and the master didn't show any unsigned certs when running
"puppet cert list".

That was a few weeks ago. I'm just coming back to puppet 3.7 now.

-m

-- 
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/CAOLfK3WFFhbbZTGrwC1bLDYLtSYxTN3XwU-RTNPtAEAYz-7U7g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet cert list yields no certs

[Matt Zagrabelny]

Hey Peter,

On Thu, Jan 7, 2016 at 5:28 PM, Peter Kristolaitis  wrote:
> 'puppet cert list' only shows unsigned certs.
>
> 'puppet cert list --all' will show all certs.

I failed to mention it explicitly:

The client does not have a signed cert. I'm try to get the master to
"accept" the CSR from the client.

-m

>
> On 1/7/2016 6:17 PM, Matt Zagrabelny wrote:
>>
>> Greetings,
>>
>> I am attempting to get a puppet 3.7 install off the ground. Please
>> don't ask me to upgrade to 4.X series. :)
>>
>> On the puppet master (puppet-3-7.example.net):
>> # puppet master --no-daemonize --debug
>> [...]
>> Info: Not Found: Could not find certificate puppet-client.example.net
>> Debug: Routes Registered:
>> Debug: Route /^\/v2\.0/
>> Debug: Route /.*/
>> Debug: Evaluating match for Route /^\/v2\.0/
>> Debug: Did not match path
>> ("/production/certificate/puppet-client.example.net")
>> Debug: Evaluating match for Route /.*/
>> Info: Not Found: Could not find certificate puppet-client.example.net
>>
>> On the puppet client:
>> # puppet agent -t --server puppet-3-7 --debug
>> [...]
>> Debug:
>> /File[/var/lib/puppet/ssl/private_keys/puppet-client.example.net.pem]:
>> Autorequiring File[/var/lib/puppet/ssl/private_keys]
>> Debug:
>> /File[/var/lib/puppet/ssl/public_keys/puppet-client.example.net.pem]:
>> Autorequiring File[/var/lib/puppet/ssl/public_keys]
>> Debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring
>> File[/var/lib/puppet/ssl/certs]
>> Debug: /File[/var/lib/puppet/facts.d]: Autorequiring File[/var/lib/puppet]
>> Debug: Finishing transaction 10544780
>> Debug: Using cached certificate for ca
>> Debug: Using cached certificate for ca
>> Debug: Creating new connection for https://puppet-3-7:8140
>> Debug: Using cached certificate_request for puppet-client.example.net
>> Debug: Using cached certificate for ca
>> Debug: Creating new connection for https://puppet-3-7:8140
>> Debug: Creating new connection for https://puppet-3-7:8140
>> Debug: Using cached certificate_request for puppet-client.example.net
>> Debug: Using cached certificate for ca
>> Debug: Creating new connection for https://puppet-3-7:8140
>> Debug: Using cached certificate for ca
>> Debug: Creating new connection for https://puppet-3-7:8140
>> Exiting; no certificate found and waitforcert is disabled
>>
>> Then on the master:
>> # puppet cert list
>> #
>>
>> I have a 2.7 puppet environment that works very well and I am well
>> accustomed to dealing with the certs.
>>
>> The auth.conf file looks okay, too:
>>
>> # allow nodes to request a new certificate
>> path /certificate_request
>> auth any
>> method find, save
>> allow *
>>
>> Can anyone help interpret the debug messages above? Or point me in the
>> correct direction?
>>
>> Thanks!
>>
>> -m
>>
>
> --
> 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/568EF4A3.4020607%40alter3d.ca.
> For more options, visit https://groups.google.com/d/optout.

-- 
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/CAOLfK3W63er4xJMjhosc6z9fqJhcGTHoMJme%3DCM-4A5LekcrRg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet cert list yields no certs

[Peter Kristolaitis]

Apparently I was a little too quick on the send button.  :(

To continue my previous email:

Does 'puppet cert list --all' show any certs at all?

From looking at your debug output, I suspect it won't show the client 
cert you're looking for, but I just want to make sure.



On 1/7/2016 6:28 PM, Peter Kristolaitis wrote:

'puppet cert list' only shows unsigned certs.

'puppet cert list --all' will show all certs.


On 1/7/2016 6:17 PM, Matt Zagrabelny wrote:

Greetings,

I am attempting to get a puppet 3.7 install off the ground. Please
don't ask me to upgrade to 4.X series. :)

On the puppet master (puppet-3-7.example.net):
# puppet master --no-daemonize --debug
[...]
Info: Not Found: Could not find certificate puppet-client.example.net
Debug: Routes Registered:
Debug: Route /^\/v2\.0/
Debug: Route /.*/
Debug: Evaluating match for Route /^\/v2\.0/
Debug: Did not match path 
("/production/certificate/puppet-client.example.net")

Debug: Evaluating match for Route /.*/
Info: Not Found: Could not find certificate puppet-client.example.net

On the puppet client:
# puppet agent -t --server puppet-3-7 --debug
[...]
Debug: 
/File[/var/lib/puppet/ssl/private_keys/puppet-client.example.net.pem]:

Autorequiring File[/var/lib/puppet/ssl/private_keys]
Debug: 
/File[/var/lib/puppet/ssl/public_keys/puppet-client.example.net.pem]:

Autorequiring File[/var/lib/puppet/ssl/public_keys]
Debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring
File[/var/lib/puppet/ssl/certs]
Debug: /File[/var/lib/puppet/facts.d]: Autorequiring 
File[/var/lib/puppet]

Debug: Finishing transaction 10544780
Debug: Using cached certificate for ca
Debug: Using cached certificate for ca
Debug: Creating new connection for https://puppet-3-7:8140
Debug: Using cached certificate_request for puppet-client.example.net
Debug: Using cached certificate for ca
Debug: Creating new connection for https://puppet-3-7:8140
Debug: Creating new connection for https://puppet-3-7:8140
Debug: Using cached certificate_request for puppet-client.example.net
Debug: Using cached certificate for ca
Debug: Creating new connection for https://puppet-3-7:8140
Debug: Using cached certificate for ca
Debug: Creating new connection for https://puppet-3-7:8140
Exiting; no certificate found and waitforcert is disabled

Then on the master:
# puppet cert list
#

I have a 2.7 puppet environment that works very well and I am well
accustomed to dealing with the certs.

The auth.conf file looks okay, too:

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

Can anyone help interpret the debug messages above? Or point me in the
correct direction?

Thanks!

-m





--
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/568EF62B.5020006%40alter3d.ca.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet cert list yields no certs

[Peter Kristolaitis]

'puppet cert list' only shows unsigned certs.

'puppet cert list --all' will show all certs.


On 1/7/2016 6:17 PM, Matt Zagrabelny wrote:

Greetings,

I am attempting to get a puppet 3.7 install off the ground. Please
don't ask me to upgrade to 4.X series. :)

On the puppet master (puppet-3-7.example.net):
# puppet master --no-daemonize --debug
[...]
Info: Not Found: Could not find certificate puppet-client.example.net
Debug: Routes Registered:
Debug: Route /^\/v2\.0/
Debug: Route /.*/
Debug: Evaluating match for Route /^\/v2\.0/
Debug: Did not match path ("/production/certificate/puppet-client.example.net")
Debug: Evaluating match for Route /.*/
Info: Not Found: Could not find certificate puppet-client.example.net

On the puppet client:
# puppet agent -t --server puppet-3-7 --debug
[...]
Debug: /File[/var/lib/puppet/ssl/private_keys/puppet-client.example.net.pem]:
Autorequiring File[/var/lib/puppet/ssl/private_keys]
Debug: /File[/var/lib/puppet/ssl/public_keys/puppet-client.example.net.pem]:
Autorequiring File[/var/lib/puppet/ssl/public_keys]
Debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring
File[/var/lib/puppet/ssl/certs]
Debug: /File[/var/lib/puppet/facts.d]: Autorequiring File[/var/lib/puppet]
Debug: Finishing transaction 10544780
Debug: Using cached certificate for ca
Debug: Using cached certificate for ca
Debug: Creating new connection for https://puppet-3-7:8140
Debug: Using cached certificate_request for puppet-client.example.net
Debug: Using cached certificate for ca
Debug: Creating new connection for https://puppet-3-7:8140
Debug: Creating new connection for https://puppet-3-7:8140
Debug: Using cached certificate_request for puppet-client.example.net
Debug: Using cached certificate for ca
Debug: Creating new connection for https://puppet-3-7:8140
Debug: Using cached certificate for ca
Debug: Creating new connection for https://puppet-3-7:8140
Exiting; no certificate found and waitforcert is disabled

Then on the master:
# puppet cert list
#

I have a 2.7 puppet environment that works very well and I am well
accustomed to dealing with the certs.

The auth.conf file looks okay, too:

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

Can anyone help interpret the debug messages above? Or point me in the
correct direction?

Thanks!

-m



--
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/568EF4A3.4020607%40alter3d.ca.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Newbie Question

[Alex Samad]

So I tried a few times yesterday ... today its working !!!

On 8 January 2016 at 09:37, Alex Samad  wrote:
> Quick feed back on the VM
>
> fails to start RHEL makes the disk offline and then it just never starts :)
>
>
>
> On 8 January 2016 at 00:57, jcbollinger  wrote:
>> On Wednesday, January 6, 2016 at 10:25:05 PM UTC-6, Alex Samad wrote:
>>>
>>> Hi
>>>
>>> Doing this of the single VM. I was hopping to test the agent and the
>>> server side on the same box.
>>>
>>
>>
>> You can run the agent on the box where the master runs.  Many people do.
>> Indeed, though I've never played with the learning VM myself, I had always
>> assumed that it was set up just that way.
>>
>>
>> John
>>
>> --

-- 
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/CAJ%2BQ1PUwmo5id7MmuWkeEnUqDrQ7tUfZWHuhPeQRhxsW%3DH7UFw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] puppet cert list yields no certs

[Matt Zagrabelny]

Greetings,

I am attempting to get a puppet 3.7 install off the ground. Please
don't ask me to upgrade to 4.X series. :)

On the puppet master (puppet-3-7.example.net):
# puppet master --no-daemonize --debug
[...]
Info: Not Found: Could not find certificate puppet-client.example.net
Debug: Routes Registered:
Debug: Route /^\/v2\.0/
Debug: Route /.*/
Debug: Evaluating match for Route /^\/v2\.0/
Debug: Did not match path ("/production/certificate/puppet-client.example.net")
Debug: Evaluating match for Route /.*/
Info: Not Found: Could not find certificate puppet-client.example.net

On the puppet client:
# puppet agent -t --server puppet-3-7 --debug
[...]
Debug: /File[/var/lib/puppet/ssl/private_keys/puppet-client.example.net.pem]:
Autorequiring File[/var/lib/puppet/ssl/private_keys]
Debug: /File[/var/lib/puppet/ssl/public_keys/puppet-client.example.net.pem]:
Autorequiring File[/var/lib/puppet/ssl/public_keys]
Debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring
File[/var/lib/puppet/ssl/certs]
Debug: /File[/var/lib/puppet/facts.d]: Autorequiring File[/var/lib/puppet]
Debug: Finishing transaction 10544780
Debug: Using cached certificate for ca
Debug: Using cached certificate for ca
Debug: Creating new connection for https://puppet-3-7:8140
Debug: Using cached certificate_request for puppet-client.example.net
Debug: Using cached certificate for ca
Debug: Creating new connection for https://puppet-3-7:8140
Debug: Creating new connection for https://puppet-3-7:8140
Debug: Using cached certificate_request for puppet-client.example.net
Debug: Using cached certificate for ca
Debug: Creating new connection for https://puppet-3-7:8140
Debug: Using cached certificate for ca
Debug: Creating new connection for https://puppet-3-7:8140
Exiting; no certificate found and waitforcert is disabled

Then on the master:
# puppet cert list
#

I have a 2.7 puppet environment that works very well and I am well
accustomed to dealing with the certs.

The auth.conf file looks okay, too:

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

Can anyone help interpret the debug messages above? Or point me in the
correct direction?

Thanks!

-m

-- 
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/CAOLfK3XzboPFXEWW0usdh5miV1AcC5cKfQL045ppokPjdOBcFA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Newbie Question

[Alex Samad]

Quick feed back on the VM

fails to start RHEL makes the disk offline and then it just never starts :)



On 8 January 2016 at 00:57, jcbollinger  wrote:
> On Wednesday, January 6, 2016 at 10:25:05 PM UTC-6, Alex Samad wrote:
>>
>> Hi
>>
>> Doing this of the single VM. I was hopping to test the agent and the
>> server side on the same box.
>>
>
>
> You can run the agent on the box where the master runs.  Many people do.
> Indeed, though I've never played with the learning VM myself, I had always
> assumed that it was set up just that way.
>
>
> John
>
> --

-- 
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/CAJ%2BQ1PVgV41%3DPs_75f6xk1SFS__CpG24c_itLBMim_%3Drr77BMw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Passing Powershell Variables into Puppet manifest

[Rob Reynolds]

On Tue, Oct 27, 2015 at 10:27 AM,  wrote:

> Hi all
>
> Im having difficulty passing powershell variables into Puppet, while using
> the Powershell module.
>
> What I need to achieve is this in powershell. It is basically a script
> that executes a check to see if a windows module is installed, and if not,
> copies it from a source directory.
>
> *This is the powershell script*
>
> $check = Get-WindowsFeature -name Net-Framework-Core
> $source = "\\server\directory\directory2\directory3"
> $destination = "C:\source3"
> if ($check.Installed -ne "True") {
> Copy-Item $source -Destination $destination -Recurse
> Install-WindowsFeature Net-Framework-Core
> Remove-Item $destination -Recurse
> }
>
> *This is my puppet manifest*
>
> class profiles::dotnetrun {
>
>
> $check = "Get-WindowsFeature -name Net-Framework-Core"
>
This is a Puppet variable when it is in the manifest, not a PowerShell
variable.


> $source = "server\\directory\\directory2\\directory3"
>
> $destination = "C:\source3"
>
>
> exec { 'dotnet':
>
> command => 'Copy-Item \$source -Destination \$destination
> -Recurse',
>
> onlyif => '\$check.Installed -ne "True"',
>

Probably due to some confusion on Puppet variables versus PowerShell
variables. You cannot define a PowerShell variable in the manifest as you
have tried above.

Another issue is that you want these to be used as variables from Puppet,
but they are likely being passed as literal strings. You should instead
look into removing the variables and passing the entire string or updating
these calls to use double-quoted strings so that variable interpolation
will occur (the literal string *$source* is passed when you use '$source',
the variable value is passed when you use "$source") and using escape
characters where appropriate.

Another option is to look into calling PowerShell files in either a
templates or files directory of your module.

Also calling $check.Installed is not likely to work as it is shown in your
manifest. If you instead surround it as "\$($check).Installed", you may
have more luck.

HTH.



> provider => powershell,
>
>
> }
>
> }
>
> 
>
> ITV plc (Registration No. 4967001) (ITV) is incorporated in England and
> Wales with its registered office at The London Television Centre, Upper
> Ground, London SE1 9LT. Please visit www.itv.com for further information.
>
> This email and any attachments are intended solely for the addressee and
> may contain confidential, copyrighted and/or privileged information.  If
> you have received this message in error, please notify us and delete it.
> Recipients should scan the email and any attachments for their own
> protection.
>
> This email does not conclude a binding agreement.  The views or opinions
> presented in this email do not necessarily represent those of ITV.
>
> --
> 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/5672654e-6c18-4fdd-a2c7-d4c62cba1a03%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Rob Reynolds
Developer, Puppet Labs

-- 
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/CAMJiBK54oruV8GCTW_-ZtM1aJW%3DT4BeM%2B_f_oF%3Dds2QaQMMzMQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Missing node_aws sub-command in puppet using Puppet Enterprise 2015.3.1-el-7-x86_64

[Lindsey Smith]

On Thu, Jan 7, 2016 at 6:30 AM, Deepak Agarwal 
wrote:

> Hello,
>
> The node_aws cloud provisioning sub-command is missing in puppet.
>
>
> I have installed Puppet Enterprise 2015.3.1-el-7-x86_64 (TRAIL version
> tar) with q_puppet_cloud_install='y'
>
> The OS is 64 bit CentOS 7. The SELinux is disabled
>
> I have searched a lot and Puppet Enterprise is expected to have
> cloud_provisioning inbuilt with q_puppet_cloud_install='y'.
> But I am not seeing node_aws in my setup.
>
>
> Please suggest what is missing and why puppet enterprise is not having
> node_aws on CentOS 7?
>

Hi Deepak. Cloud Provisioner was deprecated in the PE 3.8 release and
removed in the PE 2015.2 release as noted here
http://docs.puppetlabs.com/pe/3.8/cloudprovisioner_overview.html

As a replacement, we recommend using the puppetlabs/aws module instead. See
https://puppetlabs.com/blog/puppet-aws-module-now-supported-puppet-enterprise
for an introduction.



>
>
> -
>
> $ puppet help | grep node
>   node  View and manage node definitions.
>   resource_type View classes, defined resource types, and nodes from
> all manifests.
>
>
>
> --
>
> $ puppet help node_aws
> Error: Could not load help for the face node_aws.
> Please check the error logs for more information.
>
> Detail: "Could not find Puppet Face node_aws"
>
> Error: Try 'puppet help help help' for usage
>
>
>
> --
>
> answer file:
> q_activity_database_name='pe-activity'
> q_activity_database_password='cisco123'
> q_activity_database_user='pe-activity'
> q_all_in_one_install='y'
> q_classifier_database_name='pe-classifier'
> q_classifier_database_password='cisco123'
> q_classifier_database_user='pe-classifier'
> q_database_host='ec2-54-201-132-62.us-west-2.compute.amazonaws.com'
> q_database_install='y'
> q_database_port='5432'
> q_database_root_password='cisco123'
> q_database_root_user='root'
> q_fail_on_unsuccessful_master_lookup='y'
> q_install='y'
> q_orchestrator_database_name='pe-orchestrator'
> q_orchestrator_database_password='cisco123'
> q_orchestrator_database_user='pe-orchestrator'
> q_pe_check_for_updates='y'
> q_pe_database='y'
> q_public_hostname='ec2-54-201-132-62.us-west-2.compute.amazonaws.com'
> q_puppet_cloud_install='y'
> q_puppet_enterpriseconsole_auth_password='cisco123'
> q_puppet_enterpriseconsole_httpd_port='443'
> q_puppet_enterpriseconsole_install='y'
> q_puppet_enterpriseconsole_master_hostname='
> ec2-54-201-132-62.us-west-2.compute.amazonaws.com'
> q_puppetagent_certname='ec2-54-201-132-62.us-west-2.compute.amazonaws.com'
> q_puppetagent_install='y'
> q_puppetagent_server='ec2-54-201-132-62.us-west-2.compute.amazonaws.com'
> q_puppetdb_database_name='pe-puppetdb'
> q_puppetdb_database_password='cisco123'
> q_puppetdb_database_user='pe-puppetdb'
> q_puppetdb_hostname='ec2-54-201-132-62.us-west-2.compute.amazonaws.com'
> q_puppetdb_install='y'
> q_puppetdb_plaintext_port='8080'
> q_puppetdb_port='8081'
> q_puppetmaster_certname='ec2-54-201-132-62.us-west-2.compute.amazonaws.com
> '
>
> q_puppetmaster_dnsaltnames='ip-172-31-14-31,ip-172-31-14-31.us-west-2.compute.internal,puppet,puppet.us-west-2.compute.internal'
> q_puppetmaster_enterpriseconsole_hostname='
> ec2-54-201-132-62.us-west-2.compute.amazonaws.com'
> q_puppetmaster_enterpriseconsole_port='443'
> q_puppetmaster_install='y'
> q_rbac_database_name='pe-rbac'
> q_rbac_database_password='cisco123'
> q_rbac_database_user='pe-rbac'
> q_skip_backup='y'
> q_skip_master_verification='n'
> q_use_application_services='y'
> q_vendor_packages_install='y'
>
> Thanks,
> Deepak
>
> --
> 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/bc409262-0ba1-4e56-aa19-c8f1e8f81d2a%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAPyei8Wr%3Dqs9nKSW%3D1s2JD6VvcbwWMhu%2B_cSqSs_%3DGA4F38QEA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Newbie Question

[jcbollinger]

On Wednesday, January 6, 2016 at 10:25:05 PM UTC-6, Alex Samad wrote:
>
> Hi
>
> Doing this of the single VM. I was hopping to test the agent and the 
> server side on the same box.
>
>

You can run the agent on the box where the master runs.  Many people do.  
Indeed, though I've never played with the learning VM myself, I had always 
assumed that it was set up just that way.


John

-- 
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/f9e6bb6f-711e-4b91-a522-41ecd36dbbf1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.