[Puppet Users] paragraphing hiera yaml

[Christopher Wood]

Here's a Friday sort of question.

All the yaml emitters don't add the extra space that I can add as a person 
editing a file to make things more readable. Or to be more accurate, I can't 
manage it myself and I can't find one that does.

Consider the readability of the two examples below when thinking about what 
keys go with which classes. Also keep in mind that while example one may be 
fine for many of us, lots more people will find it easier to work with yaml 
using example two.

So how would I auto-magically auto-paragraph hiera yaml to make it friendlier 
for more people, while still keeping it syntactically valid?


Example one:

---
one::services::enabled: true
one::two::abc: 8.45
one::two::three: this is the string
puppet4::ca_server: otherhostname
puppet4::server: hostname


Example two:

---
one::services::enabled: true

one::two::abc: 8.45
one::two::three: this is the string

puppet4::ca_server: otherhostname
puppet4::server: hostname

-- 
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/20161028174542.GA10281%40iniquitous.heresiarch.ca.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Installing puppet on Ubuntu 16 & RSpec

[Peter Berghold]

Okay I've been remiss in posting this reply but I've actually solve this
issue.

What I ended up having to do is remove puppet remove Ruby remove all the
gems and then manually clean out all the directories that are touched by
everything that I just mentioned.

Then very carefully I reinstalled everything starting with puppet and used
Deb packages instead of loading through gems.

Now everything runs very happily.

What I would gather by this is something got corrupted somewhere along the
line that forced me to take such drastic actions.

On Tue, Oct 25, 2016, 17:07 Rob Nelson  wrote:

> Could you share how your testing environment is set up? Most use bundler,
> so that the puppet agent installed on the system doesn't affect the tests,
> but it would appear that is not the case here. However, before commenting
> further, we need to see a bit more about the setup.
>
> I do not think the agent failure is strictly related, in that the agent
> should work fine out of the box, but by enumerating your test setup, we may
> find some variant settings/locations you use that are causing a conflict.
>
>
> Rob Nelson
> rnels...@gmail.com
>
> On Tue, Oct 25, 2016 at 2:03 PM, Peter Berghold 
> wrote:
>
> What I thought were unrelated issues I've discovered they are related.
>
> I was using RSpec doing spec testing on Puppet code very happily when I
> decided to install the Puppet agent (attempting to eat my own dog food of
> course) and then RSpec broke.
>
> Error message spec started throwing out:
>
>  NoMethodError:
>undefined method `static_catalogs?' for
> #
>
> causing all my test cases to fail.
>
> Additionally the Puppet agent will not run as a service but it will run
> standalone (puppet agent -t).
>
> During install:
> Job for puppet.service failed because the control process exited with
> error code. See "systemctl status puppet.service" and "journalctl -xe" for
> details.
> invoke-rc.d: initscript puppet, action "start" failed.
>
> Checking systemctl status
>
> ● puppet.service - Puppet agent
>Loaded: loaded (/lib/systemd/system/puppet.service; enabled; vendor
> preset: enabled)
>Active: failed (Result: exit-code) since Tue 2016-10-25 18:01:14 UTC;
> 52s ago
>   Process: 7473 ExecStart=/usr/bin/puppet agent $DAEMON_OPTS (code=exited,
> status=1/FAILURE)
>
> Oct 25 18:01:13 mtznjv1pdev01 puppet[7473]: WARN: Clearing out unresolved
> specs.
> Oct 25 18:01:13 mtznjv1pdev01 puppet[7473]: Please report a bug if this
> causes problems.
> Oct 25 18:01:14 mtznjv1pdev01 puppet-agent[7473]: Could not autoload
> puppet/indirector/report/rest: uninitialized cons
> Oct 25 18:01:14 mtznjv1pdev01 puppet-agent[7473]: Did you mean?
> Puppet::Indirector
> Oct 25 18:01:14 mtznjv1pdev01 puppet-agent[7473]: Could not prepare for
> execution: Could not autoload puppet/indirecto
> Oct 25 18:01:14 mtznjv1pdev01 puppet-agent[7473]: Did you mean?
> Puppet::Indirector
> Oct 25 18:01:14 mtznjv1pdev01 systemd[1]: puppet.service: Control process
> exited, code=exited status=1
> Oct 25 18:01:14 mtznjv1pdev01 systemd[1]: Failed to start Puppet agent.
> Oct 25 18:01:14 mtznjv1pdev01 systemd[1]: puppet.service: Unit entered
> failed state.
> Oct 25 18:01:14 mtznjv1pdev01 systemd[1]: puppet.service: Failed with
> result 'exit-code'.
>
> and I get the same messages with "journalctl -ex"
>
> So for now my development system is going without a Puppet agent.
>
> --
> 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/CAArvnv0uZKSrWO5uwSTVKrdBLFSeaMyHcYvZ6Fvrj3xZL69A7A%40mail.gmail.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/CAC76iT_fHwWwGaGvDtfw8SdwGPegMq%2BjSNy51yR2vXqi0iQeww%40mail.gmail.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 

[Puppet Users] [CfP] FOSDEM 2017 Config Management Devroom Call For Papers is open!

[Walter Heck]

Hi Everyone,

The FOSDEM Call for Proposals for the Configuration Management devroom
on February 4th, 2017 is open!

FOSDEM Submissions are due on November 18th, 2016. If you submitted a
talk to a previous FOSDEM, you should already have an account in
Pentabarf, so make sure that you log in with your existing account.
You should only need to create an account if you have not submitted a
talk to FOSDEM in recent years. FOSDEM has a bunch of devrooms, so
please make sure that you select the "Config Management"
devroom in the "Track" dropdown when you submit your talk. Submissions
filed under an incorrect devroom will not be noticed.

Submit here: https://penta.fosdem.org/submission/FOSDEM17

Topic Description:
Mini-talks from real world case studies, brainstorming and hacking
around configuration and systems management from complex virtual
environments and cloud computing to desktops and laptops. There is
huge interest in automation, monitoring, performance management,
configuration management, and DevOps.  We are looking for
presentations from people who are working in the field on these
topics:
* Configuration and Systems Management theory, principles and development
* Configuration and Systems Management tools - with an emphasis on
real world use cases
* Techniques and case studies
* Audit, Compliance and Security
* Various DevOps topics, including collaboration and training tips.

Please note that presenting at FOSDEM implies giving permission to be
recorded.  The recordings will be published under the same licence as all
FOSDEM content (CC-BY).

This same team of people is also organizing ConfigManagementCamp,
which is in nearby Gent on February 1st and 2nd. The CFP is also open, and
we encourage you to submit your talks before the November 18th, 2016
deadline. Details: http://cfgmgmtcamp.eu/#contributions

Regards,

The ConfigManagementCamp and FOSDEM CfgMgmt Devroom organising team

-- 
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/098f93ea-f326-4fb2-848c-4d87d8145aa3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.