Skip to main content

artifactory cfengine cache repository

Industrial Linux administration

I manage a bunch of servers, more or less 1000 VMs, running either Debian (lenny,wheezy, jessie) or CentOS (5,6,7).
In order to handle this, I use CFEngine.
I mostly:

  • Create the VM
  • Add CFEngine repository (apt or yum)
  • Install CFEngine (via apt or yum)
  • Bootstrap  CFEngine


State of the nation

I performed the same steps for all VM I installed for the last 3 years.
The main problem I face is the fragmentation of the agents versions: some old installations are still with CFEngine 3.5.x and the latests are on 3.8. This is not a bearable situation: I need to align versions.

Methods and attempts

My attempts to upgrade CFEngine from CFEngine did not pass tests, mostly because promising version from within CFEngine will remove the package (the running process) and leave the system in an anormal state.
I tried several other ways to do it and specifically for the case of CFEngine package, I will manage it with a script that I'm going to launch outside CFEngine and will upgrade CFEngine (including restart the deamon) then bootstrap from the hub and we're done.

The CFEngine APT & Yum repository

CFEngine is very kind to provide a repository for their APT or Yum packages. The problem is, if I'm going to massively upgrade my thousand of VMs, there is a small risk of disturbance. As far as I use Artifactory for the development activity, I decided to use its YUm & Apt component to be a cache of CFEngine repository.

How it looks like without Artifactory

Apt source list:

deb https://cfengine.com/pub/apt/packages stable main

Yum repo file

[cfenginerepository]
name=CFEngine
baseurl=http://cfengine.com/pub/yum/$basearch/
enabled=1
gpgcheck=1


Configure Artifactory to cache those


I need to be adminsitrator of the Artifactory instance. Then I got to the "Admin" section:

Then I go to the "remote" tab, as I want to provide something related to a remote repository:

Next I create a new repository and there I can choose wether I want to setup an Apt or a Yum one:
Finally I enter

  • What I want as local name for the repository
  • The URL of the root of the remote

Specifically for our case,

For the Apt repository:

  • Name: cfengine-debian
  • URL: https://cfengine.com/pub/apt/packages

For th Yum repository:

  • Name cfengine-centos
  • URL: http://cfengine.com/pub/yum/x86_64/

How to use this

Apt source list:
deb https://artifactory.rktmb.org/artifactory/cfengine-debian stable main

Yum repo file:
[cfenginerepository]
name=CFEngine
baseurl=https://artifactory.rktmb.org/artifactory/cfengine-centos/
enabled=1
gpgcheck=1

Note that the GPG check is enabled both on Debian and CentOS and as far as this repository is just a cache one, the needed key is the original CFEngine repository key: https://cfengine.com/pub/gpg.key

The local artifactory GPG key is useless in our case now.

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='https://ngx.rktmb.org/foo' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='https://ngx.rktmb.org/foo&
Read more

emacs29 intelephense

Emacs 29 and PHP Intelephense I use to use Emacs and PHP Intelephense for PHP development. I recently upgraded to Emacs 29 and PHP Intelephense stopped working. I found a solution on Reddit Based on that, I rewrote my .emacs file to use eglot instead of lsp-mode, and this is the result. (use-package eglot :ensure t) (add-hook 'php-mode-hook 'eglot-ensure) (use-package php-mode :ensure t :mode ("\\.php\\'" . php-mode)) (add-to-list 'auto-mode-alist '("\\.php$" . php-mode)) (provide 'lang-php) (use-package company :ensure t :config (setq company-idle-delay 0.3) (global-company-mode 1) (global-set-key (kbd "M- ") 'company-complete)) (require 'eglot) (add-to-list 'eglot-server-programs '((php-mode :language-id "php") . ("intelephense" "--stdio" :initializationOptions (:licenseKey "98989898989898989898"
Read more

Jenkins invalid privatekey

Publish over SSH, Message "invalid privatekey:" With quite recent (June-July 2020) installations of Jenkins and OpenSSH, I have the following error message when using the "Deploy overs SSH" Jenkins plug-in and publishing artifacts to the target overs SSH: jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: [B@d8d395a] This problem seems to be referenced here: https://issues.jenkins-ci.org/browse/JENKINS-57495 Just regenerate a key with the right parameters To solve it: ssh-keygen -t rsa -b 4096 Or ssh-keygen -t rsa -b 4096 -m PEM
Read more