date:20160407

[Puppet Users] Re: Announce: puppet-client-tools (PuppetDB CLI) 1.0.0 is available!

2016-04-07 Thread AJ Roetker

On Thu, Apr 7, 2016 at 5:20 PM, AJ Roetker 
wrote:

> puppet-client-tools 1.0.0 (PuppetDB CLI) - 2016-04-07
> 
> Summary
>
> Today we released the initial release of puppet-client-tools which for
> includes subcommands for querying and administering PuppetDB.
>
> The PuppetDB CLI is intended to facilitate friendlier interactions with
> the PuppetDB API.
>
> The PuppetDB CLI accepts a configuration file with SSL credentials and the
> url for your PuppetDB server so you can issue queries to PuppetDB on your
> own machine without needing to type long curl invocations.
>
> We intend to use the PuppetDB CLI to provide human readable output formats
> and helpful hints for interacting with the API more generally.
>
> 
> Installation
>
> Please see the PuppetDB documentation
>  for
> installation and usage instructions.
>
This link is broken, here is the real link
 and here is a
link to the puppetdb-cli repository
.

>
> 
> Features
>
>- New implementations of our puppetdb import and puppetdb export tools
>for faster startup. The commands are now Puppet subcommands puppet-db
>import and puppet-db export respectively.
>- A puppet-query subcommand for querying PuppetDB with PQL or AST
>queries.
>
>
> 
> Contributors
>
> Andrew Roetker, Rob Browning, Ryan Senior, and Wyatt Alt.
>

-- 
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/CAL56sGnYfvGa%3DUjz8RUaZ82PJPcL2%2BB0ZDiS%3Dxy5SpbeOp%3DBKg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Announce: puppet-client-tools (PuppetDB CLI) 1.0.0 is available!

2016-04-07 Thread AJ Roetker

puppet-client-tools 1.0.0 (PuppetDB CLI) - 2016-04-07

Summary

Today we released the initial release of puppet-client-tools which for
includes subcommands for querying and administering PuppetDB.

The PuppetDB CLI is intended to facilitate friendlier interactions with the
PuppetDB API.

The PuppetDB CLI accepts a configuration file with SSL credentials and the
url for your PuppetDB server so you can issue queries to PuppetDB on your
own machine without needing to type long curl invocations.

We intend to use the PuppetDB CLI to provide human readable output formats
and helpful hints for interacting with the API more generally.

Installation

Please see the PuppetDB documentation
 for
installation and usage instructions.

Features

   - New implementations of our puppetdb import and puppetdb export tools
   for faster startup. The commands are now Puppet subcommands puppet-db
   import and puppet-db export respectively.
   - A puppet-query subcommand for querying PuppetDB with PQL or AST
   queries.


Contributors

Andrew Roetker, Rob Browning, Ryan Senior, and Wyatt Alt.

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

[Puppet Users] remove vc/1, vc/2, etc. lines from /etc/securetty using augeas

2016-04-07 Thread KC

Hi All!

I'm trying to remove the vc/1-11 lines in my /etc/securetty file. 

Is there a way to elegantly do this?

console
vc/1
vc/2
vc/3
.
.
vc/10
vc/11
tty/1
tty/2
tty/3
.
.
.
tty/10
tty/11

Doing:

rm /files/etc/securetty/*[.='vc/1'] works for one line
but
rm /files/etc/securetty/*[.='vc/*'] doesn't appear to iterate for the other 
vc lines.

Any suggestions?

-Kris

-- 
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/f3d49955-fece-484e-80f6-35230cc4f13b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Problem changing user password on Windows

2016-04-07 Thread Douglas Teixeira

Hi everyone,

We have been using Puppet to manage Windows workstations at work and it has 
been able to manage most of our machines' configurations smoothly. However, 
I stumbled upon a problem when trying to reset the password for a local 
user. The problem is that Puppet is resetting the password every time it 
runs. Is there a way to avoid that?

The manifest I am writing is very simple, and this problem occurrs even 
when I try to specify the password in plain-text inside the manifest 
(actually, from what I read Puppet isn't able to reset Windows passwords 
using a hash yet). The manifest I am writing looks like this:

user { 'Administrator':
ensure => 'present',
password => 'newpassword'
}

Do you guys have any idea about what may be causing Puppet to reset the 
password every time it is executed?

Thanks,

Douglas

-- 
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/1a55f0c4-b597-4097-a021-f367813c275e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: New Release. New Integrations. New Puppet.

2016-04-07 Thread Lindsey Smith



On Thursday, April 7, 2016 at 1:13:14 PM UTC-7, Lindsey Smith wrote:
>
> Hi everyone,
>
>
> We’re excited to share our plans for the next decade of innovation from 
> Puppet. You’ve been calling us Puppet for years and today we embraced it -- 
> we changed our name from Puppet Labs to simply Puppet. The new name, and a 
> new brand identity to go with it, reflect our mission: helping every 
> organization get on the shortest path to better software. Visit 
> www.puppet.com to see what’s new.
>
> As Luke Kanies says, Puppet is driven by a belief that software can make 
> people more powerful. To make that a reality, we introduced new technology 
> and integrations to help you automate the delivery and operation of the 
> software:
>
>
>- 
>
>Project Blueshift – Our new company initiative represents Puppet's 
>engagement with our community – as well as with leading-edge technologies 
>like Docker, Kubernetes and Mesos, and their communities – to make it 
>possible to use Puppet to provide and manage next generation software in a 
>simple, reliable, and consistent way. Learn more 
>. 
>- 
>
>Puppet Enterprise -- The all new Puppet Enterprise gives you direct 
>control and real-time visibility as you orchestrate change across 
>infrastructure and applications. We’ve also announced new integrations 
> with 
>Atlassian and Splunk. Register for our April 13th webinar. 
>
>- 
>
>President and COO – Sanjay Mirchandani will be our first President and 
>COO. Currently the corporate senior vice president of VMware, Sanjay will 
>be responsible for our go-to-market execution, including marketing, 
>pre-sales engineering, sales, customer support, and services. Gearing 
>up for another decade of industry leadership 
>
> .
>  
>
>
>
Apologies for the broken link above. It should 
be https://puppet.com/blog/gearing-up-for-another-decade-of-industry-leadership
 

>
> Register for our webinar 
>  on 
> April 13th at 9:00 AM PDT to learn more. If you’d like to, try Puppet 
> Enterprise for free on up to 10 nodes 
> .
>
> You, the Puppet community, have been a huge part of all that's happened 
> over the past 10 years. We couldn't have developed Puppet without the 
> feedback — both enthusiastic and critical — of its earliest users. And we 
> could never have built this product, and this expanding company, without 
> all of you: the people who use Puppet products, contribute code and ideas, 
> and push us to do our very best.
>
> We thank you with all our heart.
>
> Lindsey Smith
> Product Manager
> Puppet. The shortest path to better software.
>

-- 
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/ec912066-4b0e-4ae9-94ff-e67e4d1c72bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] New Release. New Integrations. New Puppet.

2016-04-07 Thread Lindsey Smith

Hi everyone,

We’re excited to share our plans for the next decade of innovation from
Puppet. You’ve been calling us Puppet for years and today we embraced it --
we changed our name from Puppet Labs to simply Puppet. The new name, and a
new brand identity to go with it, reflect our mission: helping every
organization get on the shortest path to better software. Visit
www.puppet.com to see what’s new.

As Luke Kanies says, Puppet is driven by a belief that software can make
people more powerful. To make that a reality, we introduced new technology
and integrations to help you automate the delivery and operation of the
software:

Project Blueshift – Our new company initiative represents Puppet's
engagement with our community – as well as with leading-edge technologies
like Docker, Kubernetes and Mesos, and their communities – to make it
possible to use Puppet to provide and manage next generation software in a
simple, reliable, and consistent way. Learn more
.
-

Puppet Enterprise -- The all new Puppet Enterprise gives you direct
control and real-time visibility as you orchestrate change across
infrastructure and applications. We’ve also announced new integrations with
Atlassian and Splunk. Register for our April 13th webinar.

President and COO – Sanjay Mirchandani will be our first President and
COO. Currently the corporate senior vice president of VMware, Sanjay will
be responsible for our go-to-market execution, including marketing,
pre-sales engineering, sales, customer support, and services. Gearing up
for another decade of industry leadership

Register for our webinar
on April
13th at 9:00 AM PDT to learn more. If you’d like to, try Puppet Enterprise
for free on up to 10 nodes .

You, the Puppet community, have been a huge part of all that's happened
over the past 10 years. We couldn't have developed Puppet without the
feedback — both enthusiastic and critical — of its earliest users. And we
could never have built this product, and this expanding company, without
all of you: the people who use Puppet products, contribute code and ideas,
and push us to do our very best.

We thank you with all our heart.

Lindsey Smith
Product Manager
Puppet. The shortest path to better software.

--
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/3cab1a2c-ed0c-4dc1-9fd2-38e651b0d946%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Remove scheduled task on Windows 7 x64 SP1 with Puppet 3.8.3

2016-04-07 Thread jmp242

I want to delete or at least disable certain scheduled tasks via Puppet. 

  scheduled_task { 'Lenovo Customer Feedback Program 64': ensure => absent, 
}


Doesn't seem to do anything - the tasks are still there in the Task 
Scheduler GUI and puppet doesn't give a notice or error.

  scheduled_task { 'Lenovo Customer Feedback Program 64': enabled => 
false, }

Gives errors saying it cannot set ensure => present on the tasks.

So - is this supposed to work? Did I get the Name wrong? Any ideas?

-- 
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/0547ae8b-04bb-484c-9ef1-3c826bbbfff9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Windows Remote Desktop Services (Could not find a suitable provider for dism)

2016-04-07 Thread mike r

I had the same error trying to run DISM module on a Win2008 box, then I 
realized win2008 doesnt have dism, only 2008 R2.

module is not compatible with target OS

On Wednesday, March 6, 2013 at 8:42:10 AM UTC-5, jim wrote:
>
> Hello all
>
> Was wondering if someone could help or advise where i'm going wrong 
>
> i'm trying to install Windows 2008 R2 Remote Desktop Services via Puppet 
> using either DISM or Powershell modules from the forge and getting the same 
> error
>
> When using DISM
>
>
> class roles::trm::remote_desktop_services {
> dism { 'AppServer':
> ensure => present,
> }
> dism { 'AppServer-UI':
> ensure => present,
> }
> dism { 'Printing-XPSServices-Features':
> ensure => present,
> }
> }
>
> when this initially runs, I get pink error messages which I assume its 
> because it requires a reboot to complete the install of this service.
>
> Question: Best approach for rebooting host, when installing features ?
>
> Once i've rebooted the host, and rerun the puppet agent I get the 
> following error:
>
> *err: Could not find a suitable provider for dism*
>
> So I thought it could be the dism module doesn't support Remote Desktop 
> Services.
>
> then tried the Powershell Module
>
> #exec { 'install_remote_desktop_services':
> #command   => 'Import-Module ServerManager
> #  Add-WindowsFeature -Name RDS-RD-Server -Restart  | 
> Out-File 
> c:\Installs\Puppet_Confirmation\install_remote_desktop_services.txt',
> #provider  => powershell,
> #creates   => 
> 'C:/Installs/Puppet_Confirmation/install_remote_desktop_services.txt',
> #}
>
>
> which installs fine and reboots the host etc, but upon running the agent 
> again, I get the same error as above:
>
> *err: Could not find a suitable provider for dism*
>
> If anyone could help, it would be much appreciated
>
> regards
>
> Jim 
>
>
>
>

-- 
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/8213641a-6d82-4b9a-ab6b-6ff843ab07e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet Types auto generator

2016-04-07 Thread Trevor Vaughan

Hi,

It's not a generator, but this should get you started with an
understandable example framework
https://forge.puppet.com/onyxpoint/learning_custom_types.

It doesn't cover 100% of the functionality but it will allow you to create
an understandable and maintainable Type and Provider.

Thanks,

Trevor

On Thu, Apr 7, 2016 at 4:15 AM, Christoph Andreas Torlinsky <
christ...@nuagenetworks.net> wrote:

> Hello there, i'm looking for a puppet types generator tool / toolkit as we
> have an API (Restful interface) and spec files that we would like
> to convert to puppet types for some use. If anyone has any tips, that is
> most welcomed.
>
> many thanks,
>
> c
>
> --
> 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/d714b52a-c7f7-4104-ba1a-cb697a893d0a%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699

-- This account not approved for unencrypted proprietary information --

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

[Puppet Users] Puppet Types auto generator

2016-04-07 Thread Christoph Andreas Torlinsky

Hello there, i'm looking for a puppet types generator tool / toolkit as we 
have an API (Restful interface) and spec files that we would like
to convert to puppet types for some use. If anyone has any tips, that is 
most welcomed. 

many thanks, 

c

-- 
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/d714b52a-c7f7-4104-ba1a-cb697a893d0a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] When usion puppet docker_platform with vagrant virtualbox the docker container is not started and after restart the docker daemon is not started

2016-04-07 Thread Gareth Rushgrove

On 6 April 2016 at 21:29, 'Torsten Kleiber' via Puppet Users
 wrote:
> Hi Gareth!
>
> garethr/docker module does start the docker daemon after reboot via vagrant
> halt / up.
> But unfortunately the container does only exist and start after initial
> provisioning, but is not there anymore (via "sudo docker ps -all") after
> same vagrant restart.
>

If you could open an issue at https://github.com/garethr/garethr-docker/issues

Please include as much information as possible and any output from
commands run. Which OS, version of Puppet, version of Docker and the
module, that sort of thing. In particular any boot errors from the
init scripts would likely be useful.

Gareth


> Kind regards
> Torsten
>
> --
> 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/cf7b27ec-5fe2-48e4-a329-aa23227343dc%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.



-- 
Gareth Rushgrove
@garethr

devopsweekly.com
morethanseven.net
garethrushgrove.com

-- 
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/CAFi_6y%2BtKP-p6OeR%3Dd%3DK_5NHmfTjFNunMk5VBV-XhtS4cmpKQQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.