I have installed puppet agent 3.4* on ubuntu 14.04 via Synaptic Manager.
While configuring puppet, I did not find /etc/puppet/puppet.conf file.
Is there any different setup on Ubuntu 14.04?
According to puppet documentation:
The location of Puppet’s confdir is somewhat complex. The short version is that it’s usually at one of the following locations:
/etc/puppetlabs/puppet
/etc/puppet
C:\ProgramData\PuppetLabs\puppet\etc
The actual default confdir depends on your user account, OS version, and Puppet distribution (Puppet Enterprise vs. open source). See the table for your operating system below to locate your actual confdir. For details on system vs. user confdir behavior, see
You can simply find out where Puppet looks for its configuration:
puppet agent --configprint config
In Puppet 3, this uses different defaults when you are root than for unpriviliged users. You should generally be root when invoking Puppet.
Related
We are in transition from Puppetmaster 3.8 to Puppet server(OpenSource) 5.3.
As a prerequisite for Puppetserver 5.3 installation requires Java 8 runtime packages. Can we install Adopt-OpenJDK with Pupperserver 5.3?
Puppetserver runs just fine on OpenJDK, but I strongly recommend that you run the server on an officially-supported platform (RHEL, CentOS, Debian, Ubuntu, or SLES), and use one of Puppet, Inc.'s official packages for that system. These each express a dependency on an appropriate Java 8 package, and they will configure Puppet properly to work in conjunction with that implementation. On the platforms for which I have knowledge of the details, it is the distro's OpenJDK build that is used.
It should be possible to [re]configure Puppetserver to use an Adopt-OpenJDK implementation of the Java 8 runtime, but this is swimming upstream.
Thanks John.Adding one more point here puppetserver has a dependency on openjdk-8-jre-headless:amd64.But adopt open jdk is not providing headless package.So we suspect this may cause issue as puppetserver will look for the headless package.
I've been deploying VMs with kickstart files and OSes like CentOS7 and Oracle Linux 7 in Spacewalk, I even update the VM with a yum update in the post installation kickstart script, which is amazingly cool. After installation though, it doesn't really keep up to date with the latest version of the operating system, I'd have to download and upload the .ISO to Spacewalk every time an update comes around or do a yum update on the VM itself. Then I found out you can link and schedule an OS repository. I already have a setup of this kind for CentOS7 in Spacewalk.
This works for me:
CentOS7 repository for spacewalk channel example
The link to the CentOS7 repo
However, I haven't found any public repos for OL7. Does this kind of repo simply not exist for Oracle Linux 7?
Also, is there perhaps a better solution to this problem? I'm planning on using Puppet with this setup for the software aspect.
Thanks in advance.
From: Oracle® Linux Administrator's Guide for Release 7
https://docs.oracle.com/cd/E52668_01/E54669/html/ol7-downloading-yum-repo.html
2.3 Downloading the Oracle Linux Yum Server Repository Files
Note
The following procedure assumes that yum on your system is configured to expect to find repository files in the default /etc/yum.repos.d directory.
To download the Oracle Linux Yum Server repository configuration file:
As root, change directory to /etc/yum.repos.d.
cd /etc/yum.repos.d
Use the wget utility to download the repository configuration file that is appropriate for your system.
wget http://yum.oracle.com/public-yum-release.repo
For Oracle Linux 7, enter:
wget http://yum.oracle.com/public-yum-ol7.repo
The /etc/yum.repos.d directory is updated with the repository configuration file, in this example, public-yum-ol7.repo.
You can enable or disable repositories in the file by setting the value of the enabled directive to 1 or 0 as required.
Oracle provides publicly accessible yum repos at yum.oracle.com. They even have their own build of Spacewalk available to customers.
Further, I added ULN support to Spacewalk a while ago, so you can configure it to sync content from ULN if you're a customer. See the Oracle Spacewalk Client Life Cycle Guide for more info: https://docs.oracle.com/cd/E52668_01/E71078/html/swk24-crreposwc.html
Alright REW and Djelibeybi both gave me good answers, instead of using the repo file though I opten to fully use Spacewalk and use the links in the repo file to update the channel. In hindsight I can't believe I didn't come up with this sooner because I knew of the yum public file.
The link to repo file was wrong,
I instead should have just used the links in the repo file to create multiple Spacewalk Channel repositories.
Thank you all, I'm very happy with this solution.
How to determine from the puppet master whether the installed version is opensource or enterprise?
Thanks,
Lokesh
Most obvious look at the "puppetversion" fact
on enterprise
# /usr/local/bin/facter puppetversion
3.4.3 (Puppet Enterprise 3.2.0)
on open source
# facter puppetversion
3.7.3
The fact is easily available in manifests
Alternative method
puppet config print config
if it is /etc/puppet/puppet.conf
then it's probably open source puppet
if it is
/etc/puppetlabs/puppet/puppet.conf
probably enterprise
You could also check for those files and if they existed. Of course the file location is not compulsary, these are just defaults
I want to install Gitlab on the suse linux OS.
Could some one please suggest me which OS supported Gitlab installer from the available ones on Gitlab site : Ubuntu, Debian and Centos can be used to install Gitlab on Suse linux ?
OS details :
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 4
I'm afraid that Suse is a complete different system. They use a package manager called YaST that won't be compatible with any of the proposed OS on the GitLab website.
Alternatively, you can try installation via Docker (Hopefully your system is 64bits):
https://gitlab.com/gitlab-org/gitlab-ce/tree/master/docker
Or the hard way, manually:
https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/installation.md
Or even pop an instance somewhere in the cloud but this would involve some costs.
For all other OSs it has packages to install all the required components, but for SUSE there is no package, so you will have to install all the required components like ruby, redis, mysql and other dependent libs on your own.
You may like to try this :
https://gist.github.com/rriemann/5163741
or
https://gist.github.com/jniltinho/5565606
Since I found this answer while looking for the installation on SUSE 12 (SP3), there is one of the currently working options (2021).
First, check the version supported on the system, (Gitlab 12.1 in case of SUSE 12 SP3, which corresponds to OpenSUSE 42.3)
After that, get the proper .rpm file using wget.
Install with
sudo EXTERNAL_URL="http://gitlab.my.domain" rpm -ivh path/to/file/filename
That's it. Some Versions of Omnibus for SUSE are supported directly, but it really depends on the host system version.
After fresh installation of OpenLdap 2.24.23 server on Linux, on LDAP Browser/viewers I can't see the directories like ou=config, ou=schema.
But I could see those present in /etc/openldap/slapd.d/cn=config
How can I bring up these structures?
Reference: http://www.openldap.org/doc/admin24/slapdconf2.html
On windows installation it shows up all these by default.
Thanks