Hello,
What can be the possible workflow for deploying web based application on a
server using Jenkins master, puppet master, Jenkins slave, compile master,
Mcollective server, Puppet agent and Mcollective client.
Thanks,
Megha
--
You received this message because you are subscribed to the Go
Hi
# setup postgres
postgresql::server::db { 'bitbucket':
user => $butbucketuser,
password => postgresql_password( $butbucketuser , $bitbucketpass ),
}
class { 'bitbucket':
# fix to version 8
javahome=> '/usr/java/java8',
version=> '4.8.3',
inst
I'd love to figure out how that changed on me, because your changes remind me
that it USED to look like that!
Bret Wortman
http://wrapbuddies.co/
On Aug 17, 2016, 8:01 PM -0400, Wyatt Alt , wrote:
> Hey Bret, sorry for the gap in communication. Try making these changes:
>
> * to the [master] sec
Hey Bret, sorry for the gap in communication. Try making these changes:
* to the [master] section,
storeconfigs=true
storeconfigs_backend=puppetdb
reports=puppetdb
* to the [agent] section for each node, change "reports=puppetdb" to
"report=true".
I think that should straighten it out.
Wyatt
It sounds like these might help:
https://puppet.com/blog/git-workflows-puppet-and-r10k
http://garylarizza.com/blog/categories/r10k/
Seems like you would benefit from having all teams work from branches of
current production and merge back, rather than maintaining a semi-permanent dev
branch sh
Hey all,
We are coming up on an issue in our environment in where we have multiple
Puppet environments that are backed by git branches in a puppet control
repo. Our Hiera data is stored inside these branches and changed
frequently by our Operations teams. Of which we then have them merge
cha
PuppetDB 4.2.1 - August 16, 2016
PuppetDB 4.2.1 Downloads
Available in native package format as part of Puppet Collection 1 (PC1).
More information on the PC1 repositories is available here:
http://bit.ly/1HQJDNb
Binary tarball: http://downloads.puppetlabs.com/puppetdb/
Yeah, I realized this was a red herring and deleted the original post
before writing the other you've been helping me with. I also realized that
the contents of the directory indicated was so small that it couldn't be
nearing a resource limitation. Thanks for the directions, though, I'll
defini
https://gist.github.com/wortmanb/4896962accb5aa24bcb33b893f6ef477
On Wednesday, August 17, 2016 at 2:37:31 PM UTC-4, Wyatt Alt wrote:
>
> Can you post a gist of your master's full puppet.conf?
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
T
On 8/17/16 6:26 AM, Bret Wortman wrote:
On Wednesday, August 17, 2016 at 9:19:34 AM UTC-4, Bret Wortman wrote:
I'll confess that I know next to nothing about Postgres databases,
so I'm going to ask before I royally mess anything up: what's the
best way to relocate my database from
Can you post a gist of your master's full puppet.conf?
--
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 di
For a node I know has been updated, I get (just listing the timestamps):
"facts_timestamp" : "2016-08-17T17:52:33.899Z",
"report_timestamp" : "2016-08-16T21:15:22.376Z",
"catalog_timestamp" : "2016-08-16T21:14:24.444Z",
So it seems that facts are being stored, but reports & catalogs aren't.
I'd check the timestamps in the output of
curl -X GET http://localhost:8080/pdb/query/v4/nodes/fs1603.our.net
(with a real certname if that one is fake). These will tell you when the
last report/facts/catalog for the node were stored.
Nothing about the log output you've posted indicates an issue
My puppetdb instance is up and running but hasn't stored any updates of any
kind in the past 7 hours, according to both Puppet Explorer and Puppetboard.
The process is running and so is postgres. Puppet configs haven't changed
in that time. /var/log/puppetlabs/puppetdb/puppetdb.log shows plenty
Versions:
# rpm -qa | grep puppet
puppetserver-2.4.0-1.el7.noarch
puppetdb-4.2.0-1.el7.noarch
puppetexplorer-2.0.0-1.noarch
puppetdb-termini-4.2.0-1.el7.noarch
puppet-agent-1.6.0-1.el7.x86_64
# rpm -qa | grep postgres
postgresql95-libs-9.5.4-1PGDG.rhel7.x86_64
postgresql95-9.5.4-IPGDG.rhel7.x86_6
Well there is Application Orchestrator if you are using PE, but I think it
is still pretty green. It's meant to be the push solution for deploying
apps but I'm under the impression that not a lot of people are using it
yet.
Mcollective is one option, for sure, but there are others. Most
orchestrat
I got to looking at the storage issue because it also seems that no new
reports have been recorded in over 4 hours, when my nodes have definitely
been accessing puppet and completing agent runs during this same time.
On Wednesday, August 17, 2016 at 9:19:34 AM UTC-4, Bret Wortman wrote:
>
> I'll
I'll confess that I know next to nothing about Postgres databases, so I'm
going to ask before I royally mess anything up: what's the best way to
relocate my database from one partition to another? I need to move my files
from their current location (which seems to be
/opt/puppetlabs/server/data
18 matches
Mail list logo
