Webhuis wiki - User contributions [en]

MediaWiki:Sidebar

2025-11-07T15:26:39Z

Martn admin:

Cobol and PostgreSQL

2025-11-06T15:58:06Z

Martn admin:

GixSQL is a way in which Cobol programs are able to use modern database management systems in a Linux environment.
== Cobol ==
Cobol has been around for more than 60 years and will stay around for the foreseeable future, estimates are that there are about 800 billion lines of Business Cobol code around. The programs are heavily used, servicing about 80% of all financial and business transaction. 
The reason behind this endurance lies in the fact that Cobol is a standardised language, a program written in 1974 can be compiled today with a modern compiler. The resulting executable program still runs today, without the need of adaptation. 
Traditionally Cobol programs have their application in big business mainframe environments. These large enterprises, however, are shifting more and more of their applications to the Linux platform. The broad adoption of Linux in the enterprise environment started around 2010. So, it is no wonder that Cobol gradually is being made available for the Linux platform, enter [https://gnucobol.sourceforge.io/ GNUCobol].
== GNUCobol ==
Is an Open Source Cobol compiler, the project originally started in 2002 [ https://en.wikipedia.org/wiki/GnuCOBOL GNUCobol ] as OpenCobol. GNUCobol is now a full blown Cobol compiler.
== PostgreSQL and Cobol ==
PostgreSQL is getting more and more traction around the world, also in the big enterprises. Big enterprises have ample reason to stick to their Cobol program stack, in which they invested huge amounts of money. So if PostgreSQL is to make it to the business applications of the big enterprises, it has to find a way to interact in a reliable manner with Cobol. Enter the [https://en.wikipedia.org/wiki/GnuCOBOL GixSQL] SQL preprocessor for Cobol.

Cobol and PostgreSQL

2025-11-06T15:55:15Z

Martn admin:

GixSQL is a way in which Cobol programs are able to use modern database management systems in a Linux environment.
== Cobol ==
Cobol has been around for more than 60 years and will stay around for the foreseeable future, estimates are that there are about 800 billion lines of Business Cobol code around. The programs are heavily used, servicing about 80% of all financial and business transaction. 
The reason behind this endurance lies in the fact that Cobol is a standardised language, a program written in 1974 can be compiled today with a modern compiler. The resulting executable program still runs today, without the need of adaotation. 
Traditionally Cobol programs have their application in big business mainframe environments. These large enterprises, however, are shifting more and more of their applications to the Linux platform. The broad adoption of Linux in the enterprise environment started around 2010. So, it is no wonder that Cobol gradually is being made available for the Linux platform, enter [https://gnucobol.sourceforge.io/ GNUCobol].
== GNUCobol ==
Is an Open Source Cobol compiler, the project originally started in 2002 [ https://en.wikipedia.org/wiki/GnuCOBOL GNUCobol ] as OpenCobol. GNUCobol is now a full blown Cobol compiler.
== PostgreSQL and Cobol ==
PostgreSQL is getting more and more traction around the world, also in the big enterprises. Big enterprises have ample reason to stick to their Cobol program stack, in which they invested huge amounts of money.

Cobol and PostgreSQL

2025-11-06T15:45:42Z

Martn admin:

Cobol and PostgreSQL

2025-11-06T15:43:27Z

Martn admin:

Cobol and PostgreSQL

2025-11-06T15:39:36Z

Martn admin:

GixSQL is a way in which Cobol programs are able to use modern database management systems in a Linux environment.
== Cobol ==
Cobol has been around for more than 60 years and will stay around for the foreseeable future. Traditionally Cobol programs have their application in big business mainframe environments. These large enterprises, however, are shifting more and more of their applications to the Linux platform. The broad adoption of Linux in the enterprise environment started around 2010. So, it is no wonder that Cobol gradually is being made available for the Linux platform, enter [https://gnucobol.sourceforge.io/ GNUCobol].
== GNUCobol ==
There are various good reasons

Cobol and PostgreSQL

2025-11-06T15:39:07Z

Martn admin:

GixSQL is a way in which Cobol programs are able to use modern database management systems in a Linux environment.
== Cobol ==
Cobol has been around for more than 60 years and will stay around for the foreseeable future. Traditionally Cobol programs have their application in big business mainframe environments. These large enterprises, however, are shifting more and more of their applications to the Linux platform. The broad adoption of Linux in the enterprise environment started around 2010. So, it is no wonder that Cobol gradually is being made available for the Linux platform, enter [[https://gnucobol.sourceforge.io/ | GNUCobol]].
== GNUCobol ==
There are various good reasons

Cobol and PostgreSQL

2025-11-06T15:38:46Z

Martn admin:

GixSQL is a way in which Cobol programs are able to use modern database management systems in a Linux environment.
== Cobol ==
Cobol has been around for more than 60 years and will stay around for the foreseeable future. Traditionally Cobol programs have their application in big business mainframe environments. These large enterprises, however, are shifting more and more of their applications to the Linux platform. The broad adoption of Linux in the enterprise environment started around 2010. So, it is no wonder that Cobol gradually is being made available for the Linux platform, enter [[GNUCobol | https://gnucobol.sourceforge.io/ ]].
== GNUCobol ==
There are various good reasons

Cobol and PostgreSQL

2025-11-06T15:37:59Z

Martn admin:

GixSQL is a way in which Cobol programs are able to use modern database management systems in a Linux environment.
== Cobol ==
Cobol has been around for more than 60 years and will stay around for the foreseeable future. Traditionally Cobol programs have their application in big business mainframe environments. These large enterprises, however, are shifting more and more of their applications to the Linux platform. The broad adoption of Linux in the enterprise environment started around 2010. So, it is no wonder that Cobol gradually is being made available for the Linux platform, enter [GNUCobol | https://gnucobol.sourceforge.io/ ].
== GNUCobol ==
There are various good reasons

Cobol and PostgreSQL

2025-11-06T15:29:51Z

Martn admin: /* Cobol */

Cobol and PostgreSQL

2025-11-06T15:29:23Z

Martn admin:

GixSQL is a way in which Cobol programs are able to use modern database management systems in a Linux environment.
= Cobol =
Cobol has been around for more than 60 years and will stay around for the foreseeable future.

Cobol and PostgreSQL

2025-11-06T15:27:51Z

Martn admin: Created page with "= Cobol = Cobol has been around for more than 60 years and will stay around for the foreseeable future."

= Cobol =
Cobol has been around for more than 60 years and will stay around for the foreseeable future.

MediaWiki:Sidebar

2025-11-06T15:26:16Z

Martn admin:

MediaWiki:Sidebar

2025-11-06T15:25:49Z

Martn admin:

Voorpagina

2022-06-04T16:05:53Z

Martn admin:

<big>'''Webhuis Wiki.'''</big> 
Welkom op de wiki van Webhuis, deze wiki heeft een [[PostgreSQL]] backend. 
Webhuis gebruikt en produceert (op bescheiden schaal) Open Source Software (OSS). Webhuis gebruikt en onderhoudt de wiki ter ondersteuning van haar eigen werk op het gebied van configuratie en beheer van Informatie Systemen voor dienstverlening aan haar klanten. 
Webhuis stelt de informatie in de wiki, in lijn met het gedachtengoed van de vrije software, kostenloos ter beschikking aan de gemeenschap. 
Deze wiki heeft als voornaamste doel te ondersteunen bij het opzetten, configureren en beheren van automatiseringsomgevingen die zijn gebaseerd op OSS. De wiki bevat een groeiend repertoire van configuraties van OSS applicaties, howto's, voorbeelden en ook studie materiaal. De wiki is voortdurend in bewerking en sommige nieuwere onderdelen bevatten nog slechts de ruwe informatie van een bepaald aandachtsgebied. 
Webhuis gebruikt vrijwel uitsluitend Debian GNU Linux en de configuratie voorbeelden zijn daarop gericht. 

De bijdragen op deze wiki vallen onder de [http://www.gnu.org/copyleft/gpl.html GNU General Public License]. 
Disclaimer: All information comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. 
Webhuis pagina [[webhuis_info]]

Webhuis Kennisbank

2022-06-04T16:03:28Z

Martn admin:

Webhuis stelt de informatie in de wiki, in lijn met het gedachtengoed van de vrije software, kostenloos ter beschikking aan de gemeenschap. 
Deze wiki heeft als voornaamste doel te ondersteunen bij het opzetten, configureren en beheren van automatiseringsomgevingen die zijn gebaseerd op OSS. De wiki bevat een groeiend repertoire van configuraties van OSS applicaties, howto's, voorbeelden en ook studie materiaal. De wiki is voortdurend in bewerking en sommige nieuwere onderdelen bevatten nog slechts de ruwe informatie van een bepaald aandachtsgebied. 
Webhuis gebruikt vrijwel uitsluitend Debian GNU Linux en de configuratie voorbeelden zijn daarop gericht.
* [[Basale infrastructuur]]
* [[Webhuis bouwstenen]]
* [[Webhuis Infrastructuur]]
* [[Webhuis configuratie]]
* [[Webhuis Support Infrastructuur]]
* [[Webhuis Raspberry Pi]]
* [[Configuratie van applicaties]]
* [[Business Applicaties]]
* [[Webhuis kwaliteitszorg]]
* [[Documentatie]]
* [[Mac hoekje]]
* [[Ubuntu]]
* [[FreeBSD]]
* [[HowTo's]]
De bijdragen op deze wiki vallen onder de [http://www.gnu.org/copyleft/gpl.html GNU General Public License]. 
Disclaimer: All information comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. 
Webhuis pagina [[webhuis_info]]
<hr/>
Terug naar: [[Voorpagina]]

Webhuis Kennisbank

2022-06-04T16:02:57Z

Martn admin:

Webhuis stelt de informatie in de wiki, in lijn met het gedachtengoed van de vrije software, kostenloos ter beschikking aan de gemeenschap. 
Deze wiki heeft als voornaamste doel te ondersteunen bij het opzetten, configureren en beheren van automatiseringsomgevingen die zijn gebaseerd op OSS. De wiki bevat een groeiend repertoire van configuraties van OSS applicaties, howto's, voorbeelden en ook studie materiaal. De wiki is voortdurend in bewerking en sommige nieuwere onderdelen bevatten nog slechts de ruwe informatie van een bepaald aandachtsgebied. 
Webhuis gebruikt vrijwel uitsluitend Debian GNU Linux en de configuratie voorbeelden zijn daarop gericht.
* [[Basale infrastructuur]]
* [[Webhuis bouwstenen]]
* [[Webhuis Infrastructuur]]
* [[Webhuis configuratie]]
* [[Webhuis Support Infrastructuur]]
* [[Webhuis Raspberry Pi]]
* [[Configuratie van applicaties]]
* [[Business Applicaties]]
* [[Webhuis kwaliteitszorg]]
* [[Configuratie van applicaties]]
* [[Business Applicaties]]
* [[Documentatie]]
* [[Mac hoekje]]
* [[Ubuntu]]
* [[FreeBSD]]
* [[HowTo's]]
De bijdragen op deze wiki vallen onder de [http://www.gnu.org/copyleft/gpl.html GNU General Public License]. 
Disclaimer: All information comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. 
Webhuis pagina [[webhuis_info]]
<hr/>
Terug naar: [[Voorpagina]]

Webhuis Kennisbank

2022-06-04T16:01:45Z

Martn admin:

Webhuis stelt de informatie in de wiki, in lijn met het gedachtengoed van de vrije software, kostenloos ter beschikking aan de gemeenschap. 
Deze wiki heeft als voornaamste doel te ondersteunen bij het opzetten, configureren en beheren van automatiseringsomgevingen die zijn gebaseerd op OSS. De wiki bevat een groeiend repertoire van configuraties van OSS applicaties, howto's, voorbeelden en ook studie materiaal. De wiki is voortdurend in bewerking en sommige nieuwere onderdelen bevatten nog slechts de ruwe informatie van een bepaald aandachtsgebied. 
Webhuis gebruikt vrijwel uitsluitend Debian GNU Linux en de configuratie voorbeelden zijn daarop gericht.
* [[Basale infrastructuur]]
* [[Webhuis bouwstenen]]
* [[Webhuis Infrastructuur]]
* [[Webhuis configuratie]]
* [[Webhuis Support Infrastructuur]]
* [[Webhuis Raspberry Pi]]
* [[Configuraties van applicaties]]
* [[Business Applicaties]]
* [[Webhuis kwaliteitszorg]]
* [[Configuratie van applicaties]]
* [[Business Applicaties]]
* [[Documentatie]]
* [[Mac hoekje]]
* [[Ubuntu]]
* [[FreeBSD]]
* [[HowTo's]]
De bijdragen op deze wiki vallen onder de [http://www.gnu.org/copyleft/gpl.html GNU General Public License]. 
Disclaimer: All information comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. 
Webhuis pagina [[webhuis_info]]
<hr/>
Terug naar: [[Voorpagina]]

Webhuis Kennisbank

2022-06-04T15:59:13Z

Martn admin:

Webhuis stelt de informatie in de wiki, in lijn met het gedachtengoed van de vrije software, kostenloos ter beschikking aan de gemeenschap. 
Deze wiki heeft als voornaamste doel te ondersteunen bij het opzetten, configureren en beheren van automatiseringsomgevingen die zijn gebaseerd op OSS. De wiki bevat een groeiend repertoire van configuraties van OSS applicaties, howto's, voorbeelden en ook studie materiaal. De wiki is voortdurend in bewerking en sommige nieuwere onderdelen bevatten nog slechts de ruwe informatie van een bepaald aandachtsgebied. 
Webhuis gebruikt vrijwel uitsluitend Debian GNU Linux en de configuratie voorbeelden zijn daarop gericht.
* [[Basale infrastructuur]]
* [[Webhuis bouwstenen]]
* [[Webhuis Infrastructuur]]
* [[Webhuis configuratie]]
* [[Webhuis Support Infrastructuur]]
* [[Webhuis kwaliteitszorg]]
* [[Configuratie van applicaties]]
* [[Business Applicaties]]
* [[Documentatie]]
* [[Mac hoekje]]
* [[Ubuntu]]
* [[FreeBSD]]
* [[HowTo's]]
De bijdragen op deze wiki vallen onder de [http://www.gnu.org/copyleft/gpl.html GNU General Public License]. 
Disclaimer: All information comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. 
Webhuis pagina [[webhuis_info]]
<hr/>
Terug naar: [[Voorpagina]]

Webhuis configuratie

2022-06-04T15:58:23Z

Martn admin:

* [[Apache]]
* [[nginx]]
* [[proxy]]

= Apache =
<hr/>
Terug naar: [[Webhuis Kennisbank]]

Webhuis Kennisbank

2022-06-04T15:56:49Z

Martn admin:

Webhuis stelt de informatie in de wiki, in lijn met het gedachtengoed van de vrije software, kostenloos ter beschikking aan de gemeenschap. 
Deze wiki heeft als voornaamste doel te ondersteunen bij het opzetten, configureren en beheren van automatiseringsomgevingen die zijn gebaseerd op OSS. De wiki bevat een groeiend repertoire van configuraties van OSS applicaties, howto's, voorbeelden en ook studie materiaal. De wiki is voortdurend in bewerking en sommige nieuwere onderdelen bevatten nog slechts de ruwe informatie van een bepaald aandachtsgebied. 
Webhuis gebruikt vrijwel uitsluitend Debian GNU Linux en de configuratie voorbeelden zijn daarop gericht.
* [[Basale infrastructuur]]
* [[Webhuis bouwstenen]]
* [[Webhuis Infrastructuur]]
* [[Webhuis Support Infrastructuur]]
* [[Webhuis kwaliteitszorg]]
* [[Configuratie van applicaties]]
* [[Business Applicaties]]
* [[Documentatie]]
* [[Mac hoekje]]
* [[Ubuntu]]
* [[FreeBSD]]
* [[HowTo's]]
De bijdragen op deze wiki vallen onder de [http://www.gnu.org/copyleft/gpl.html GNU General Public License]. 
Disclaimer: All information comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. 
Webhuis pagina [[webhuis_info]]
<hr/>
Terug naar: [[Voorpagina]]

PostgreSQL

2022-06-04T15:56:28Z

Martn admin:

[[Frank Heikens]] werkt samen met [[Martin Simons]] Webhuis op het gebied van PostgreSQL, hij levert een belangrijke bijdrage aan de PostgreSQL configuratie en documentatie.
* [[HA Cluster]]
* [[Toepassingen]]
* [[PostgreSQL rollen en privileges]]
= HA Cluster =
In PostgreSQL spreekt men altijd van een cluster, omdat serieuze toepassingen voor ononderbroken werking een terugval op een kopie van de database nodig hebben. Een cluster bestaat in dat geval uit tenminste één Primary en één Standby node. De standby neemt de taak van primary op zich als de primary stopt. 
Een High Availability Cluster (HA) gaat verder en voldoet aan de volgende criteria:
* Het cluster bestaat uit één primary node en twee standby nodes
* Automatische failover met minimale downtime, met beveiliging tegen een terugkomende node die primary claimt
* Efficiënte afhandeling van connection met behulp van pooling
* Afscherming van de database nodes door middel van een proxy
* Afsplitsing van zware lees queries met load balancing op de standby nodes

= Toepassingen =
MySQL is op het moment de meest gebruikte database voor Mediawiki. Webhuis is de wiki in het verleden begonnen met een MySQL backend, maar is overgestapt PostgreSQL als standaard database backend.
== Mediawiki ==

=== Installatie ===
De installatie procedure met de PostgreSQL backend is een beetje gammel, maar als je eenmaal een PostgreSQL database hebt gaat het soepel.
==== Webserver ====
<pre>
# apt-get install mediawiki php-pgsql
</pre>
In /etc/php/7.3/apache2/php.ini uncomment:
<pre>
extension=pdo_pgsql
extension=pgsql
</pre>
==== PostgreSQL Server ====
Als de database is geïnstalleerd is de volgende voorbereiding op de import uit MySQL noodzakelijk, vanwege andere afhandeling van de autoincrement op keys in tabllen. In PostgreSQL doen we dat met een sequence.
<pre>
create sequence page_id_seq owned by page.page_id;
alter table page alter page_id set default nextval('page_id_seq');
create sequence pagecontent_old_id_seq owned by pagecontent.old_id;
alter table pagecontent alter old_id set default nextval('pagecontent_old_id_seq');
create sequence revision_rev_id_seq owned by revision.rev_id;
alter table revision alter rev_id set default nextval('revision_rev_id_seq');
create sequence job_job_id_seq owned by job.job_id;
alter table job alter job_id set default nextval('job_job_id_seq');
</pre>
=== Migratie ===
<pre>
php importDump.php --conf /etc/mediawiki/LocalSettings.php ~/tmp/mediawiki-dump.xml --username-prefix='wiki_database_rolename'
</pre>
<hr/>
Terug naar: [[Voorpagina]]

Webhuis Kennisbank

2022-06-04T15:55:44Z

Martn admin: Created page with "Webhuis stelt de informatie in de wiki, in lijn met het gedachtengoed van de vrije software, kostenloos ter beschikking aan de gemeenschap. Deze wiki heeft als voorn..."

Webhuis stelt de informatie in de wiki, in lijn met het gedachtengoed van de vrije software, kostenloos ter beschikking aan de gemeenschap. 
Deze wiki heeft als voornaamste doel te ondersteunen bij het opzetten, configureren en beheren van automatiseringsomgevingen die zijn gebaseerd op OSS. De wiki bevat een groeiend repertoire van configuraties van OSS applicaties, howto's, voorbeelden en ook studie materiaal. De wiki is voortdurend in bewerking en sommige nieuwere onderdelen bevatten nog slechts de ruwe informatie van een bepaald aandachtsgebied. 
Webhuis gebruikt vrijwel uitsluitend Debian GNU Linux en de configuratie voorbeelden zijn daarop gericht.
* [[Basale infrastructuur]]
* [[Webhuis bouwstenen]]
* [[Webhuis Infrastructuur]]
* [[Webhuis Support Infrastructuur]]
* [[Webhuis kwaliteitszorg]]
* [[Configuratie van applicaties]]
* [[Business Applicaties]]
* [[Documentatie]]
* [[Mac hoekje]]
* [[Ubuntu]]
* [[FreeBSD]]
* [[HowTo's]]
De bijdragen op deze wiki vallen onder de [http://www.gnu.org/copyleft/gpl.html GNU General Public License]. 
Disclaimer: All information comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. 
Webhuis pagina [[webhuis_info]]

MediaWiki:Sidebar

2022-06-04T15:53:52Z

Martn admin:

MediaWiki:Sidebar

2022-06-04T15:53:22Z

Martn admin:

MediaWiki:Sidebar

2022-06-04T15:49:20Z

Martn admin:

Talk:Main Page

2022-06-04T15:48:53Z

Martn admin: Martn admin moved page Talk:Main Page to Talk:Voorpagina: Dit is een nederlandstalige wiki

#REDIRECT [[Talk:Voorpagina]]

Talk:Voorpagina

2022-06-04T15:48:53Z

Martn admin: Martn admin moved page Talk:Main Page to Talk:Voorpagina: Dit is een nederlandstalige wiki

Main Page

2022-06-04T15:48:52Z

Martn admin: Martn admin moved page Main Page to Voorpagina: Dit is een nederlandstalige wiki

#REDIRECT [[Voorpagina]]

Voorpagina

2022-06-04T15:48:52Z

Martn admin: Martn admin moved page Main Page to Voorpagina: Dit is een nederlandstalige wiki

<big>'''Webhuis Wiki.'''</big> 
Welkom op de wiki van Webhuis, deze wiki heeft een [[PostgreSQL]] backend. 
Webhuis gebruikt en produceert (op bescheiden schaal) Open Source Software (OSS). Webhuis gebruikt en onderhoudt de wiki ter ondersteuning van haar eigen werk op het gebied van configuratie en beheer van Informatie Systemen voor dienstverlening aan haar klanten. 
Webhuis stelt de informatie in de wiki, in lijn met het gedachtengoed van de vrije software, kostenloos ter beschikking aan de gemeenschap. 
Deze wiki heeft als voornaamste doel te ondersteunen bij het opzetten, configureren en beheren van automatiseringsomgevingen die zijn gebaseerd op OSS. De wiki bevat een groeiend repertoire van configuraties van OSS applicaties, howto's, voorbeelden en ook studie materiaal. De wiki is voortdurend in bewerking en sommige nieuwere onderdelen bevatten nog slechts de ruwe informatie van een bepaald aandachtsgebied. 
Webhuis gebruikt vrijwel uitsluitend Debian GNU Linux en de configuratie voorbeelden zijn daarop gericht.
* [[Basale infrastructuur]]
* [[Webhuis bouwstenen]]
* [[Webhuis Infrastructuur]]
* [[Webhuis Support Infrastructuur]]
* [[Webhuis kwaliteitszorg]]
* [[Configuratie van applicaties]]
* [[Business Applicaties]]
* [[Documentatie]]
* [[Mac hoekje]]
* [[Ubuntu]]
* [[FreeBSD]]
* [[HowTo's]]
De bijdragen op deze wiki vallen onder de [http://www.gnu.org/copyleft/gpl.html GNU General Public License]. 
Disclaimer: All information comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. 
Webhuis pagina [[webhuis_info]]

MediaWiki:Sidebar

2022-06-04T15:48:14Z

Martn admin:

MediaWiki:Sidebar

2022-06-04T15:47:09Z

Martn admin:

Cfengine2

2022-06-01T15:09:48Z

Martn admin:

= cfengine =
Systeembeheer met cfengine is de manier om Linux en Unix systemen geautomatiseerd te onderhouden. De huidige in debian ondersteunde versie van cfengine is cfengine2, versie cfengine3 bestaat reeds maar is er nog niet voor debian.

De leercurve van cfengine is zeer steil en het duurt ook voor een ervaren goed ingevoerde system administrator geruime tijd voordat hij de eerste resultaten boekt. De leercurve is zo steil dat velen na een aanvankelijk enthousiast begin toch weer de shortcuts van handmatige configuratie op de clients nemen en zo noodgedwongen cfengine op de client uitzetten. Men geeft het na een aanvankelijk blijmoedig begin op.

De voorbeelden komen uit Automating UNIX and Linux Administration (http://kaybee.org:81/kirk/aua.html), de sources zijn ook te downloaden van http://www.apress.com.
* http://www.cfengine.org/pages/compare
== Hoofdonderwerpen cfengine ==
* [[cfengine opzet]]
* [[cfengine configuratie]]
* [[cfengine installatie]]
== Begin gelijk met versiebeheer ==
Zonder versiebeheer, zelfs met één enkele machine is er geen enkele reden om met cfengine te beginnen. Sommige wijzigingen zorgen ervoor dat het geheel ontregeld raakt, het duurt geruime tijd voordat de systeembeheerder wijzigingen met enige trefzekerheid kan door voeren. Een eerder mooi uitgewerkte configuratie gaat, zeker in het begin, snel verloren.
== Multi domein opzet ==
De ondersteuning van meerdere domeinen vanuit één template configuratie ligt aan de basis van de opzet van cfengine.
== Overzicht ==
* http://www.cfengine.org/manuals/cf3-upgrade.html#Contents
* http://www.cfwiki.org/cfwiki/index.php/Overview
* https://cockpit.webhuis.nl/cfengine2/
* http://sial.org/howto/cfengine/
* http://watson-wilson.ca/blog/cfcookbook.html#SECTION00090000000000000000
* http://sial.org/howto/cfengine/examples/
* http://sial.org/howto/cfengine/classes/
* http://sial.org/howto/cfengine/examples/update.conf
* http://research.iu.hio.no/viewvc/trunk/ChangeLog?view=markup&revision=210&root=Cfengine-2
* http://www.cfengine.org/manuals/cf2-Reference.html#domain
* http://www.cfwiki.org/cfwiki/index.php/Tips,_Tricks_and_Notes
* http://lists.gnu.org/archive/html/help-cfengine/2004-10/msg00083.html
* http://www.cfwiki.org/cfwiki/index.php/Multiple_Domains
* http://www.cfwiki.org/cfwiki/index.php/Cfagent.conf_Explanation_Draft
* http://www.cfwiki.org/cfwiki/index.php/QuickStart
* http://www.cfwiki.org/cfwiki/index.php/LukesCfengineTutorial
* http://www.cfwiki.org/cfwiki/index.php/Tips,_Tricks_and_Notes
* http://research.iu.hio.no/viewvc/trunk/ChangeLog?view=markup&revision=210&root=Cfengine-2
* http://lists.gnu.org/archive/html/help-cfengine/2004-10/msg00083.html
* http://www.linuxplanet.com/linuxplanet/tutorials/5999/3/
* http://sial.org/howto/cfengine/classes/
* http://www.sun.com/bigadmin/features/articles/cfengine_part2.jsp
* http://sunsite.ualberta.ca/Documentation/Gnu/cfengine-1.6.3/cfengine.html
* http://www.debian-administration.org/articles/224

== Initiële cfengine2 configuratie ==
=== Installatie ===
De installatie verloopt als volgt:
# apt-get update && apt-get install cfengine2
=== Client installatie ===
Kopieer het bestand update.conf van de cfengine2 server naar de te beheren host:
# scp -p /var/lib/cfengine2/masterfiles/PROD/inputs/update.conf <hostname>:/etc/cfengine
Vervolgens op de te beheren host:
# cfagent -v
De rest verloopt voortaan vanzelf.
=== Server installatie ===
De scripts voor het bouwen van een van een cfengine2 configuratie staan in ldap-svn.webhuis.nl/cfengine2/cfengine2-bootstrap:
# svn checkout https://ldap-svn.webhuis.nl/cfengine2/cfengine2-bootstrap
Dit levert de volgende bestanden op:
cfengine2:~/cfengine2-bootstrap# ls -l
total 8
-rw-r--r-- 1 root root 3586 2010-01-29 22:34 cf.preconf
-rwxr-xr-x 1 root root 471 2010-01-29 22:36 make-cfengine2-indirectories.sh
cfengine2:~/cfengine2-bootstrap#
Voer eerst het script make-cfengine2-indirectories.sh uit en daarna cf.preconf:
# make-cfengine2-indirectories.sh
# bash cf.preconf
Het resultaat is een initiële cfengine2 configuratie.
<hr>
Terug naar: [[CFEngine]]

Package-team

2022-06-01T15:09:24Z

Martn admin:

= Issues left =
Dit zijn de Issues.

== Bootstrapping CFEngine ==

Bootstrappen werkt alleen als alle machines die cfengine draaien dezelfde sys.workdir is geconfigureerd. Zie issue:

* https://cfengine.com/dev/issues/3697

== data directory ==

Er zit nu in de code een verwijzing naar de verkeerde directories. Het is nu nog niet goed geparametriseerd.

the ''--datadir'' currently does nothing and cfengine is installing this file in:
1. projdatadir='${exec_prefix}/share/cfengine' (--enable-fhs options set this)
1. projdatadir='${exec_prefix}/share' (default cfengine behaviour)

Due this issue we can not choose in which directory the data files are stored. Eg in debian the package is called ''cfengine3'' so the data files must be installed in ''${exec_prefix}/share/cfengine3''.

There is an pull request that supports the old an new behavior:
* https://github.com/cfengine/core/pull/1059

Hier moet een analyse komen van het probleem, met mogelijk de moeilijkheden voor de huidige code base.

== Versie aanduiding ==
De build mislukt nu nog voor de verschillende subversies van Debian. Dit komt omdat er test fout is, namelijk:
* tests/acceptance/00_basics/01_compiler/800.cf

en zie voor lange verklaring:
* https://github.com/Webhuis/Cfengine-debian/issues/24

en ik denk dat Ted een oplossing heeft

== Symbolic links issue ==

Bootstrap werkt niet bij ons omdat sys.workdir/inputs een symbolic link is naar /etc/cfengine3. Daar is een fix voor. Was eerst niet goed en misschien moet er nog wat gefixed worden, maar het een en ander is al verbeterd en ze zouden er na kijken:
* https://github.com/cfengine/core/pull/1050

Anders zijn er 2 opties:
1. debian package aanpassen en /etc/cfengine3 een link maken naar sys.workdir/inputs.
1. sys.inputs variable toevoegen die je kan zetten met configure options. Default : sys.workdir/inputs. Net zoals voor logdir/piddir.

<hr>
Terug naar: [[CFEngine]]

Debian-team

2022-06-01T15:08:59Z

Martn admin:

= Provisional page for the CFEngine Debian-team =
Eventually we would like it to all be on github, but a start is a start. We will copy the content to github any suitable moment.
== Mission Statement ==
To produce a high quality, current, Debian native CFEngine package suitable for inclusion directly in Debian stable release.
= Git repositories =
Both repositories contain the same release.
git://git.debian.org/git/collab-maint/cfengine3.git
git://anonscm.debian.org/collab-maint/cfengine3.git
We are in the process of merging the existing Debian code with the code of CFengine 3.5.2. We have to determine whether it is still useful to do the merge because of the extent of the changes to the code, in fact we skipped CFengine versions 3.1 thru 3.4. It might be beyond the point where it adds to the process if we add CFengine 3.5 to this repository. 

We aim at building a current CFengine release for Debian stable, but it would be helpful to the process if we decide to have a testing branch, or daily build branch, as well. We would add newer versions to the Debian repository each time CFengine releases a version we want to Debianize. Having this approach would prevent us to be in the lagging position like we are now.
== Debian-team repository ==
The Debian-team agree on using a github repository to support our development process. We will develop the github way thus developers create branches themselves and the Debian-team decide on the merge process.
https://github.com/Webhuis/Cfengine-debian/
A clone is obtained with:
user@host:~$ git clone https://github.com/Webhuis/Cfengine-debian.git
The Debian-team decided to follow the Debian maintainers'wish that we separate the debian directory from the Cfengine source code and to merge the two branches in a tar ball when a build is required, like this:
<pre>
 debian Split debian orig and create NMU branch September 24, 2013
 masterfiles Moved content masterfiles branch into masterfiles directory in that branch October 1st, 2013
 orig imported 3.5.2 code September 22, 2013
</pre>
We are tracking our issues here: https://github.com/Webhuis/Cfengine-debian/issues?state=open

== Decissions made ==
* PID go to /run/cfengine3. See https://wiki.debian.org/ReleaseGoals/RunDirectory?highlight=%28%2Frun%29#Packages_using_.2Fvar.2Frun_and_.2Fvar.2Flock
* The Debian Team prepare for Jessie as our primary target

== Starting point ==
The starting point seems so have been moving. At the start (20130728) of the Debian-team initiative the offical Cfengine Debian stable release was
related to CFengine 3.0.5. Recently a new version was introduced, Cfengine3 3.2.4-2+nmu1, this is a Non Maintainer Upload. 
The official Debian point of view with regards to NMU is: 
A non-maintainer upload (NMU) is an upload of a package to the debian archive by a developer who is not the maintainer of the package. This should usually not be the case, but in special cases (such as for RC bugs, when the maintainer does not respond to the bug report) it is allowed. See [https://wiki.debian.org/NonMaintainerUpload Non Maitainer Upload].
=== Integrating 3.5.2 ===
CFengine is at 3.5.2 these days and has major changes and improvements with regards to stability and functionailty. We the Debian-team decided to build the native CFengine 3.5.2 Debian stable Wheezy package and are still looking for ways with the Debian maintainer. 
The Cfengine project have been working very hard and a lot has changed in the code. There is a huge delta between the two lines of code, 3.2.4-2+nmu1 and 3.5.2. 
One of our first goals is the integration of the new code line into the main line.
==== Process ====
This is the break down of the integration process:
* Create a 3.2.4-2-NMU1 branch
* Update changelog and copyright files, leave debian/source/local-options
* Relocate the source files
* Copy 3.5.2 sources file over the relocated 3.2.4-2+NMU1 source files
==== 3.2.4-2+NMU1 ====
The script carries out the following tasks
* Separate orig and debian branches
* Move orig code to the orig branch

<pre>
#!/bin/bash
#
# First step to integrated Cfengine 3.5.2 in debian
#
# To be carried out in the top level git directory
#
# Create the NMU branch

git branch 3.2.4-2+nmu1

# Make NMU current

git checkout 3.2.4-2+nmu1

# First apply the NMU fix
# Whereas ${1} is the debian directory in the cfengine3_3.2.4-2+nmu1 source,
# and ${2} is the debian directory in de git repository

cp -p ${1}copyright ${2}/debian/
cp -p ${1}changelog ${2}/debian/

mkdir orig

git mv aclocal.m4 orig
git mv AUTHORS orig
git mv autogen.sh orig
git mv ChangeLog orig
git mv config.guess orig
git mv config.sub orig
git mv configure.ac orig
git mv configure orig
git mv depcomp orig
git mv docs orig
git mv examples orig
git mv INSTALL orig
git mv install-sh orig
git mv LICENSE orig
git mv ltmain.sh orig
git mv m4 orig
git mv Makefile.am orig
git mv Makefile.in orig
git mv masterfiles orig
git mv missing orig
git mv pub orig
git mv README orig
git mv src orig
git mv tests orig
git mv ylwrap orig
</pre>

Proposed update of changelog in debian:
<pre>
cfengine3 (3.2.4-2+NMU1 git) unstable; urgency=low

* Branch 3.2.4-2+NMU1
* Put NMU updates in debian directory, left debian/source/local-options
* Separated debian from orig
* Upload to central repository

</pre>
===== Merging NMU =====
<pre>
#!/bin/bash

# Back to master branch

git checkout master

# Merge NMU into master

git merge 3.2.4-2+nmu1

# Commit the NMU branch

git commit -am "Merge 3.2.4-2+NMU1 into master"

# Push the NMU branch

# git push origin master
</pre>
The push is commented out, it will not pass unless a trick is played. Checkout a branch on the master and then push the master from the client. Switch back to master after the push.

=== Intermediate repository ===
The Debian-team are looking for a way to set up a code review process pre-pushing. The best option is to have a Debian process for this, if not we will work out a flow using github. 
In the mean time we need an intermediate solution in order to get to a 3.5.2 starting point. The Debian-team have access by LDAP authentication for http.
* http://packages.webhuis.nl/
* git://packages.webhuis.nl/cfengine3

=== Useful links ===
* [http://qa.debian.org/developer.php?login=antonio%40debian.org Cfengine3 QA page]
* [http://packages.qa.debian.org/c/cfengine3.html Cfengine3 Packages QA page]
* [http://packages.debian.org/stable/admin/cfengine3 Debian Cfengine3 Project page]

== Patching ==
The Cfengine 3.2.4-2+nmu1 release contains the following patches in this sequence defined by the series file:
* remove-man-errors.patch
* fhs-compliance.patch
* fix-examples-paths.patch
* 626647-kfreebsd-support.patch
The package needs to be patched predominantly for reasons of compliancy with Debian policies and standards.
== Building the package ==
The cfengie source package comes in a tar ball, cfengine-3.5.2.tar.gz. Issue the following commands to start the build proces:
<pre>
martin@wbhs-pkg:/usr/local/src$ tar xzf cfengine-3.5.2.tar.gz
martin@wbhs-pkg:/usr/local/src$ cd $ cfengine-3.5.2
martin@wbhs-pkg:/usr/local/src/cfengine-3.5.2$ dh_make -f ../cfengine-3.5.2.tar.gz -r -c gpl2 -e "Martin Simons martin@webhuis.nl"
martin@wbhs-pkg:/usr/local/src/cfengine-3.5.2$ cp -p /home/martin/development/cfengine3/debian/patches debian/
martin@wbhs-pkg:/usr/local/src/cfengine-3.5.2$ dpkg-buildpackage -rfakeroot -uc -us
</pre>

= Cfengine planning =
Cfengine is developing quite rapidly these days. The Masterfiles now are an integral part of the installation, as of version 3.6 we will see a split of the Masterfiles with regards to the core system. Cfengine 3.6 is due end of 2013.

= Plan =
* preconditions
* scope
* risks
* gouvernance
* relationships to the commercial edtion and third party solutions
* Planning and milestones to be obeserved

== tenants ==

* As much as possible cfengine-core should support Debian natively
** Prefer patching cfengine rather than Debian
** Use <tt>IFDEF</tt> where necessary
* Strictly adhere to Debian packaging policies
** Debian FHS layout

Creating a buildable debian package should be as easy as obtaining the cfengine source and dropping in the <tt>debian</tt> directory.

*** Notable directory relocations:
**** /var/log/cfagent.NODENAME.log and /var/log/cf3.HOSTNAME.runlog
**** /var/run/COMPONENT for PID files
**** all the examples should point to $(sys.inputdir) and $(sys.masterdir) and so on
**** executables under /usr/sbin (need to adjust sys.bindir)
**** sys.masterdir = /var/lib/cfengine3/masterfiles
**** sys.inputdir = /etc/cfengine3
**** links: etc/cfengine3 var/lib/cfengine3/inputs and usr/sbin var/lib/cfengine3/bin
**** configure line:
./configure --enable-shared=no \
--without-nova \
--without-constellation \
--prefix=/usr \
--with-sql=yes \
--with-workdir=/var/lib/cfengine3 \
--mandir=\$${prefix}/share/man \
--infodir=\$${prefix}/share/info \
--htmldir=\$${prefix}/share/doc/cfengine3/html \
CFLAGS="$(CFLAGS)" LDFLAGS="-Wl,-z,defs"

*** daemons not started on install, need to edit /etc/default/cfengine3

<hr>
Terug naar: [[CFEngine]]

CFEngine

2022-06-01T15:08:23Z

Martn admin:

* [[Cfengine3]]
* [[The CFEngine Roadshow]]
* [[Cfengine3 Messaging]]
* [[Data]]
* [[Jenkins RobotFramework development workflow]]
* [[CFEngine3 Node]]
* [[Dynamic CFEngine3]]
* [[Debian-team]]
* [[Package-team]]
* [[Cfengine2]]
<hr/>
Terug naar: [[Main Page]]

CFEngine

2022-06-01T15:04:47Z

Martn admin:

* [[Cfengine3]]
* [[The CFEngine Roadshow]]
* [[Cfengine3 Messaging]]
* [[Data]]
* [[Jenkins RobotFramework development workflow]]
* [[CFEngine3 Node]]
* [[Dynamic Cfengine3]]
* [[Debian-team]]
* [[Package-team]]
* [[Cfengine2]]
<hr/>
Terug naar: [[Main Page]]

The CFengine Roadshow

2022-06-01T15:04:34Z

Martn admin: Martn admin moved page The CFengine Roadshow to The CFEngine Roadshow: Alignment met de productnaam

#REDIRECT [[The CFEngine Roadshow]]

The CFEngine Roadshow

2022-06-01T15:04:34Z

Martn admin: Martn admin moved page The CFengine Roadshow to The CFEngine Roadshow: Alignment met de productnaam

The CFEngine Roadshow is a live demonstration of the real, live from the ground configuration of a number of virtual servers. 
We do a comparison of key products at this time, Chef, Puppet and CFEngine. We give an overview of the underlying concepts of CFEngine.
* Promise theory
* Policies and promises
* Desired State
* Declarative vs. imperative
* Convergence with a demonstration of a practical example

Technical aspects of CFEngine
* Native
* Small footprint
* Scalability
* The Domain Specific Language (DSL)
Success story CFEngne by DirecTV in Los Angeles CA, with lessons learned
= Bring your VM! =
Attendees are encouraged to bring their own virtual machines. Setting up a VM for The CFEngine Roadshow: [[Cfengine3_Node]].

The CFEngine Roadshow supports:
* CentOS 7
* Ubuntu 14.04
* openSuse 13.1
* Debian Wheezy
The CFEngine Roadshow has local package mirrors available to sustain a swift install.

= Live demo =
The CFEngine Roadshow presents a Live Demo of the configuration multiple virtual machines and the deploy of multiple Application Servers:
* Time Configuration
* User management
* Hostname management
* NFS server
* NFS mounts
* Ssh public key configuration.
* Twelve tomcat servers
* Attendees are encouraged and invited to bring their own Virtual Machines to be configured by CFEngine.
Attendees are facilitated to have one or more of their own VM’s configured by CFEngine. Please find a detailed description here: [[Cfengine3_Node]].
<hr>
Return to: [[CFEngine]]

CFEngine

2022-06-01T15:04:07Z

Martn admin:

* [[Cfengine3]]
* [[The CFengine Roadshow]]
* [[Cfengine3 Messaging]]
* [[Data]]
* [[Jenkins RobotFramework development workflow]]
* [[CFEngine3 Node]]
* [[Dynamic Cfengine3]]
* [[Debian-team]]
* [[Package-team]]
* [[Cfengine2]]
<hr/>
Terug naar: [[Main Page]]

CFEngine

2022-06-01T15:03:24Z

Martn admin:

* [[Cfengine3]]
* [[The Cfengine Roadshow]]
* [[Cfengine3 Messaging]]
* [[Data]]
* [[Jenkins RobotFramework development workflow]]
* [[CFEngine3 Node]]
* [[Dynamic Cfengine3]]
* [[Debian-team]]
* [[Package-team]]
* [[Cfengine2]]
<hr/>
Terug naar: [[Main Page]]

CFEngine

2022-06-01T15:03:07Z

Martn admin:

Dynamic Cfengine3

2022-06-01T15:02:25Z

Martn admin: Martn admin moved page Dynamic Cfengine3 to Dynamic CFEngine3: Alignment met de productnaam

#REDIRECT [[Dynamic CFEngine3]]

Dynamic CFEngine3

2022-06-01T15:02:25Z

Martn admin: Martn admin moved page Dynamic Cfengine3 to Dynamic CFEngine3: Alignment met de productnaam

Although this website is predominatly written in Dutch, because it is aimed at Dutch people using Debian, this set of pages is in English. The reason behind this is Webhuis' desire to support the international CFEngine community.
= The dynamics is in the data =
A best practice in CFEngine is to make promises or bundles as generic as possible, so that they suite the needs of as many situations as possible. Hosts and Domains contain specific information or data that is applicable to the Host only and that to be used in the configuration of the Host.
== Host taylor made provisioning of promises ==
Dynamic CFEngine is the Webhuis way of providing a taylor made set of promises to each and every node. Webhuis believe this is a security feature, because the host only has the bundles and the data it needs. 
Webhuis offers Dynamic CFEngine under [http://webhuis.nl/GPL-license GPL-2] as its contribution to the community.
== How does it work? ==
Dynamic CFEngine extends on convergence because it provides the promises to the system in a convergent way, not all the promises are available as of the bootstrap of the host. The Webhuis example setup is structured:
* A host belongs to a domain
* A host has a role
In the example the host, domain and role bundles contain data that drive the common logic in the common bundles. When the host is bootstrapped to the CFEngine Master Hub it starts configuring itself by pulling the host and domain bundles from the hub. The host bundles file contains the role information, which convergently is being pulled from the hub in a subsequent iteration. 
=== The host ===
Each host requires a file ${uqhost}.cf in this example. 
In small operations this is not a problem and is the set of host files to maintain easily. Smaller operations in general will have hosts that have common names. 
The downside of this approach is that a big data center will have hundreds, if not thousands of host.cf files. In a situation like that it probably is the better option to have a host naming convention, so that the host name contains the role name and for instance an instance number. Big operations in general will have a host naming convention in place.

=== The role ===
The role the host has in crucial in this concept, because the role defines the machine and the software that has to be installed and configured. 
If the role is defined by a host naming convention then a regular expression is applied to fetch the role name from the host name.

== Data driven approach ==
Because the data in the host, domain and role bundles drive the common logic in the common bundles Dynamic CFEngine makes little use of classes or contexts. The context is defined beforehand and no decisions have to be made, thus leading to a reduction of complexity in the logic in the common bundles.

= The structure =
The bundlesequence in promises.cf is as follows:
* "role"
* "g"
* "update"
* "@(webhuis_common)"
* "${g.class_domain}"
* "${g.class_host}"
* "${role.role}"

== Step by step ==
In the first iteration almost everything fails, the bundles g, update and the bundlesequence in @(webhuis_common) will execute but will not fulfill all the promises. In the example "${g.class_domain}" is replaced by webhuis_nl, "${g.class_host}" is replaced by bur and "${role.role}" is replaced by backup_recovery. @(webhuis_common) is an slist that contains the bundle names "common_bundles", "os_layer", "hardening".
== bundle common role ==
The bundle common role is the first bundle to be executed when available to the host. It defines the common variable role that has the name of the role to the system and it sets a class with the name of the role. The role name becomes available to cf-agent once the role is identified by either:
* Fetching the role name from the host name, if host naming is done by convention
* Fetching the role name from the host file.
Here you find the [[bundle_common_role | bundle common role ]] details.

== bundle common g ==
The bundle common g is contained in promises.cf and it defines common variables to the system. In the Webhuis Dynamic CFEngine3 solution two special slist variables are generated, in order to have dynamic inputs. The dynamic inputs consists of two branches
* A standard inputs branch in /var/cfengine/inputs
* A dynamic inputs specific branch /var/cfengine/inputs-webhuis
Here you find the [[bundle_common_g | bundle common g ]] details.
== bundle agent update ==
The bundle agent update carries out very important tasks specific to Dynamic CFEngine3. 
The agents use it to pull their specific configuration information from the CFEngine hub they are bootstrapped to. It pulls the standard masterfiles to inputs, but it also pulls domain, host and role specific information from the webhuis branch on the hub and places these bundles into a branch next to inputs /ver/cfengine/inputs-webhuis. 
Here you find the [[bundle_agent_update | bundle agent update ]] details.
== bundle agent webhuis common ==
The bundle webhuis_common carries out common tasks like installing base packages and housekeeeping. Still it uses the variables of the dynamic bundles. 
Here you find the [[bundle_agent_webhuis_common | bundle agent webhuis common ]] details.
== bundle agent webhuis_nl ==
The bundle webhuis_nl is an example domain bundle, the webhuis branch that is next to masterfiles could contain any number of domains. The domain bundle for the most part defines data that are common to the domain. In this example it defines network addresses, and servers for ldap, dns and ntp. 
Here you find the [[bundle_agent_webhuis_nl | bundle agent webhuis_nl ]] details.
== bundle agent bur ==
The bundle bur defines a couple of variables that are specific to the host and adapt to the role that it has. 
Here you find the [[bundle_agent_bur | agent bur ]] details.
== bundle agent backup_recovery ==
The bundle agent backup_recovery is an example of role hosts can have. It deals with the variables it gets passed and takes care of the installation of packages required to carry out the task that belongs to the role. 
Here you find the [[bundle_agent_backup_recovery | bundle agent backup_recovery ]] details.
<hr>
Return to: [[CFEngine]]

Dynamic CFEngine3

2022-06-01T15:02:12Z

Martn admin:

Cfengine3 Node

2022-06-01T15:01:52Z

Martn admin: Martn admin moved page Cfengine3 Node to CFEngine3 Node: Alignment met de productnaam

#REDIRECT [[CFEngine3 Node]]

CFEngine3 Node

2022-06-01T15:01:52Z

Martn admin: Martn admin moved page Cfengine3 Node to CFEngine3 Node: Alignment met de productnaam

Webhuis facilitates and encourages attendees to The CFEngine Roadshow to configure a blank VM of choice. We are in the process of supporting as many platforms as possible. We do have full support for debian_7 and debian_8 and partly ubuntu_14. We are working and in need of support for centos_*. We are working on opensuse_13. Mint, Gentoo, Raspberry Pi and Androids geeks are more than welcome.
= Pre requisities =
== Fair use policy ==
Every individual who is using the facilities of The CFEngine Roadshow states he or she complies with the following:
# Will follow the instuctions given during The CFEngine Roadshow
# Will not disturb The CFEngine Roadshow by any kind of attacks to any of the The CFEngine Roadshow systems, it is a live demonstration not a Cracker Camp
# Will not copy Commercial Software to any of the common CFEngine Roadshow utility systems
# Will report if the number of bootstrapped agents exceeds the count of ten, in order to receive an award
Happy bootstrapping!

== Create a blank Virtual Machine ==
Please have your bare Virtual Machine ready before you take part in The CFEngine Roadshow. Please install a bare machine and make it as lean as possible. You even do not need to install ssh, we probably replace it anyway, just use VNC. 
We assume a KVM VM. Good descriptions for are avaiable [http://docs.openstack.org/image-guide/content/virt-install.html here virt-install]. Example code:
<pre>
# qemu-img create -f qcow2 /data/centos-6.4.qcow2 10G
# virt-install --virt-type kvm --name centos-6.4 --ram 1024 \
--cdrom=/data/CentOS-6.4-x86_64-netinstall.iso \
--disk path=/data/centos-6.4.qcow2,size=10,format=qcow2 \
--network network=default\
--graphics vnc,listen=0.0.0.0 --noautoconsole \
--os-type=linux --os-variant=rhel6
</pre>
=== Centos 7 ===
Netinstall CentOS-7.0-1406-x86_64-NetInstall.iso
* Zet eerst het netwerk aan
* Selecteer de mirror: http://mirror.centos.org/centos/7/os/x86_64/

= CFEngine Roadshow Services =
The CFEngine Roadshow offers services to support the creation and configuration of Nodes.
== Private key cfetest ==
It is recommended to create a cfetest user on your preferred machine and have the enclosed private key available in the .ssh directory. Then create the file id_rsa with permissions 700 and copy the key content into the file. The passphrase of the key is CFEngine_Roadshow.
<pre>
-----BEGIN RSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
DEK-Info: AES-128-CBC,A5D6E322AA20CF2FC2B1FBCB9A86AF57

+tgxD1apbr5OoxVXoIrSaF3Q3HyRcacnV4mliVB9NQ2xns4fwfF12R3wH0+8aJMn
PLNcmBER9iSdvQvm9ZbNEifzhdkRp08lPK6j2e2A/Rn4ksYXdfXZw7l6G7T+w8Yo
zIUIvOg85vGOhH6VZ4tlYhMy3Mq4i4RAXbstAgxq3GI+eFqohzVxUE/+ZbgJ8twh
dh2jyAP2KQzKbGFybM1l9iqQPYXRQPyC7wRskl75Eqs7kwAcPfgVoJA2YLue4meh
w38EA6I4t3787mGUtnPxcsiXQxmo/Z8lw0Dh2KDXHTsknXBsAICG0+9kK1UK/+b+
/NLGRg+kYIiCVUQnHwgJ+TB7+IZVCs55u4zq7xT+iZ3CH2gK7DpQxco8YX3oT6tm
3xo+jQk/4GJOsYu52j60ZrABMTfBtfTKOkTAg+7g4uzCcCJAIZPKnUL4uNPmxAy1
/QaxEpblLo+Qi1jqGYPeL72YnmUbEpExJ7Ryswe/GcbRCTfBDs615q45PSMl8VyD
cyCnu4PM/ZBctPRUF/QTQE1ACJQtnSETFxRgyOHnSGBRWrPQIFfIuqU06F9Fn0Ku
CstZhbotergNzI1zEwOWm/2HOzUN4x1UerMTDJlKz/wegbgBYNcJvdiniODAMEN7
psDolgdun0i0jxEuTkwoM+r9cGqEsWUlmWyvyIrqc5PgLFejVc6Q8PH1rJZrbxgQ
tIs80ozF13WjJ9Hh8sv09d/C35TEwTMuKBhdyGBISrp/AaE7S+jPNTw2IIFTLYCI
N++sTL8FWi0mT/+xJxss/VTp5CccPjCAjGTGjYF0yazHWXuBfP+dkasL5StIzpi3
SRIIpHnFwinH9czg9sC8HO4O64hK4WegOw5+3rE1GUjBaPzH+20qtG94GQSJ/65i
FB1/Kjwv1MA50cnsu0TuWk84RrnzBkE0SA6wbgmy7BiGl/Yr8iipOD0HW7hu6osX
QiYaHrxkhYyj8Ai/0+9zXQnyb9wa4sAaA+BYW10rjpw6yaEFnzDgdH5f5n6zoiH/
SmC62uh1BafIWcq2Be7tIEukse9PieMmFhwPA4Jo94oFzbU2mQxyrzG6m1L4O1SC
P7by2dcRF/tf673/siCWOpIWSa1GPWB7uKMyP2GkYJWwtS+20D1GsKb6IuJicLwQ
aZbW57AprIBDW7eRNPPEvbmScDeO+DuoRTbHvonPhGEf+YDAV0EqZXT0gKe/cqB7
m46r7yhWrFGq85oLw+lbzPsLaXGPO2QC7pan2TNfXYGquu8u8pja+YK5Ao/V2S7M
518IG9lxFblGp8h8IK5nPPxjNF9JtHFBWmLLt29i01xNk4lcxwiUJA44KSjX9ETg
P8ihWNonJEWJgHbnyqv4KWzffY8hwiQwx4cMj4ZD9RyntdH1S3vc8gcD8MAi+CTL
I/wbGYPJJ1OF2KY6qlo1qSi5vEKR3fbKsrJD9l+4YBCHaSy9FP2IkkjpAiH++NMS
K35HhMinqAXU0lUKdHWSeJ1SDULkz0hdAaLe7xoXgw3/0xbBxE8+fKab85cKgS13
dG0ckHCrCsjtTXoXXq/6eaCFvHM5V6PXXkZtLp6OkD+VK4wm81em5pHYQbN9yfq0
vS6CMTqKVC3CyQ1lD6QMHaJxbpkbyM/U1jXVxqZTfRgFg8f9VQphYAmhsf8VOSBt
WGEbxEqZBmm5udixfP3c4bOk40O1tsH5pNC+5pT+Hb0cnQ7g4ZQAs0alhNzOyp2+
z4T/lzsQzeDO5hkc3A6U3pkPmj859BNKEUhMjX4Mv8W+2OSIpNadckpivvzsoKOi
aQsKS3oo7Dls5h0CB67xkW/UIpMov6ySfDGYqqc6Ccj1hdqgnKj7uzUoCLY5I5/i
1dEbYvRrM81AMU6o1+N6+DtdtVnVElVErzUOXC8G8BO3gaWIojKmhbc7H1jhDcQ/
l+owXdOw5yQPwr8TnWVUZDjLPjvYRdqq25CZd6J4VpvjEvXZu/ukdZnRZHW3Aqo4
jV2IaVm6MqLdIFqbSbkLj2EKaDQOr60zrpRgnc+oaHfBtXTLSH4tVaEHf9NtQiNN
aachiKneIyAo85qxu8JM5LLgClckJVqtRtM3yFert7fVmeNDXy4VK6cE1OKhJRYw
RIa6JaqtQnDuM5fCIZdKJIKTJNYX7je9VW4DGVmExuRiKTD9GRzvnDAYAydZt52X
tVF9wWGOvqfw6IZRv7vTOxsWdIuVmOjn1AJV9WSvmyFWrDdhPAfGx8BsBAow7npZ
xO5S0tTi0MgWUqNBttTsBPAkTAzHLUE2xs1dfZtAFkgPKsOjlR4DsWEbVRLAcScf
OLHjXCE8+TQVBrjMCYTZJo3mu/fZCnjTUGuaQcJFYi28zPU8dSAZ3b8ehWFMEUzv
HMt4CgJzuvNx01kt84aimO1H5mYRLTDFofqwn1jDYjijWZ44ykeiZHrQGUwC6bLL
A0Fwp2SIjjZFQrsgtdh+OerVp68UtZ3T5A4+WnbNWV7U8iWc2Edc4aw7+7zz9TyF
eOn68ySVIcaTrepBML3xfCFTAUzvn4/KJyNC+HKr/pJe9RozXmIjZQXexib5mX87
VJ3u0PIbN458ls2kgP4EMbWpr1oInuzSKmWlIn5yCxQsLHQ2A0/vDu2451yGXoj1
Dc1y7CTBUrtDrZheuZ6MrSXJ7BO7yKPjcncUHkWZIfuMLJqjIChMRVHldvDXfQ/r
WKnqs3hAgEF/GoCg5VGZJk/RECAQCNag7ZhPlrhqRGlXSwCXi2vBXUMc69Iejxc6
Ri0W3RBaIEvEg5Z8WGKCFhuZ2jJxn2FTvA7HROeWdfjIDbNj6xkmJEt3Somrdtdk
4gh+E/DKicjv9W13OBq9veOcn791oWkL1FJ/97MU4T65nGcV0nbb4IdvDxzsb0V0
ZnyZG5Ijv21NURlLMO2DGzQaWBxGzf4vhPL6bOY+hLneNQsnXMK/asmhxMhSp9+i
GBTX1p+qOKnE+WHWyOyH0nPpR1goA02ZGcVx8KWssHoOSA7yKi6/rY0CoVeHiWFY
LIWB2hLVDCICRRGCBcFWptrYy9/RT8odcjnCqfUds0r7i7ZdHf+njXVQukzLt0sV
A6PdYdR9wS8FCNUbi/eqcsH+B6NU4oeiAkcHUw12upPNKRfaSoravkWJa2WkRHNF
-----END RSA PRIVATE KEY-----
</pre>

== Utility Servers ==
{|
! style="text-align:left;"| Service
! IP address
|-
|ipssys01.webhuis.nl
|10.168.0.1
|-
|cfeutl01.webhuis.nl
|10.168.0.10
|-
|aptutl01.webhuis.nl
|10.168.0.11
|-
|nfsutl01.webhuis.nl
|10.168.0.12
|}

== Local Mirrors ==
{|
! style="text-align:left;"| OS
! Mirror
! IP address
|-
|Debian
|aptutl01.webhuis.nl
|10.168.0.11
|-
|Centos 7
|rpmcos01.webhuis.nl
|10.168.0.22
|-
|OpenSuse
|
|
|-
|Ubuntu 14.04
|aptubu01.webhuis.nl
|10.168.0.21
|}

== Supported Platforms ==
As of November 2014 the focus has been on integration of The CFEngine Roadshow with the official Masterfiles at the expense of the expansion of platform support. We now have integrated Masterfiles and now really are ready to extend platform support. We feel Android and Rasberry Pi support are the greater challenges, wheras Ubuntu, Centos, opensuse, Gentoo and Mint support are very useful.
* Debian
* Centos / Fedora
* Suse
* Ubuntu
Please file a request if you do not find your preferred platform.
=== Images ===
With efficient use of bandwidth in mind the preferred method of installation is a netinstall, we assume x86_64. The CFEngine Roadshow uses local mirrors and needs no external connection in order to be able to install and configure guest VM's.
{|
! style="text-align:left;"| OS
! Images
|-
|Debian
|http://ftp.nl.debian.org/debian/dists/wheezy/main/installer-amd64/current/images/netboot/debian-installer/amd64/initrd.gz
|-
|
|http://ftp.nl.debian.org/debian/dists/wheezy/main/installer-amd64/current/images/netboot/debian-installer/amd64/initrd.gz
|-
|Centos
|
|-
|Fedora
|
|-
|OpenSuse
|
|-
|Ubuntu
|
|}

=== CFEngine Community ===
Please install CFEngine 3.6.2-1 for your installation method of choice. The CFEngine Debian-team are proud to announce cfengine3-3.6.2 made it Debian Jessie. CFEngine has an important bug fix release 3.6.3, we will incorporate this release as soon as possible. The CFEngine Roadshow so far for practical reasons still uses the release issued by cfengine.com.
{|
! style="text-align:left;"| OS
! Package
|-
|Debian CFEngine build
|http://cfengine.package-repos.s3.amazonaws.com/community_binaries/cfengine-community_3.6.2-1_amd64.deb
|-
|Debian Debian-team
|Preferred, extra reward: https://github.com/Webhuis/Cfengine-debian
|-
|RPM based
|http://cfengine.package-repos.s3.amazonaws.com/community_binaries/cfengine-community-3.6.2-1.x86_64.rpm
|}
Please keep in mind you have to wait for The CFEngine Roadshow to be available before you bootstrap your VM.

=== Naming convention ===
We use a naming convention in order to determine the role of a node*.

{|
! style="text-align:left;"| Role
! Mnemonic
|-
|apt_cacher
|aptutl
|-
|cfe_hub
|cfeutl
|-
|ips_server
|ips
|-
|nfs_server
|nfsutl
|-
|webapp_server supporting the Tomcat sample app
|webapp
|-
|webttw_server supporting the Tomcat testweb app
|webttw
|-
|webhud_server supporting the Tomcat Hudson app
|webhud
|}
* Check this before you use the node, the mnemonics may change. 
Use the last two octets of your Mac Address after the mnemonic as a unique identifier for your hostname. Please use the hexadecimal representation of these octests. 
You can always check the CFEngine code that manages the role of the server here:
[https://github.com/Webhuis/CFEngine-Roadshow/blob/master/services.cf The CFEngine Node Role]

== The CFEngine Debian-team package ==
Debian users are encouraged to build their own package from:
[https://github.com/Webhuis/Cfengine-debian Debian-team]
Instructions can be found here:
[https://github.com/Webhuis/Cfengine-debian/wiki Debian-team Wiki]
The CFEngine Debian-team is a community initiative to make available to the community a Debian standards compliant CFEngine-Community package. Jessie is near and we are determined to bring the up to date CFEngine-Community 3.6.2 to this version of Debian. One of the major spin off of the project is that the methods we developed are applicable to other distributions too, so we will rename our initiative to the CFEngine Packaging-team.

<hr>
Return to: [[CFEngine]]

CFEngine3 Node

2022-06-01T15:01:30Z

Martn admin:

Jenkins RobotFramework development workflow

2022-06-01T15:01:04Z

Martn admin:

* gitblit
* webjen
* RobotFramework
* nfsutl0001.webhuis.nl as a central datastore
= webjen0001.webhuis.nl =
webjen0001.webhuis.nl is a Jenkins server.
== Plugins ==
<hr>
Return to: [[CFEngine]]

Data

2022-06-01T14:59:30Z

Martn admin:

Data is under development, so subject to change (quite much hopefully). 
Nodes interact with Data according to a protocol. We suggest we comply with the AMQP standard. https://www.amqp.org
= The Universal Truth =
All nodes voluntarly sharing their information give Data the opportunity to construct a Universe of information. Data on its turn provides specific information of interest to specific nodes from this Universe to these specific nodes.
== Guiding principles ==
* Precedence Analysis
* Desired state is assumend
* Data holds the Universal Truth
Data presents nodes on request with node taylored views on the Universal Truth, thus supplying the nodes with the the information they require. This is the normal situation in which Data provides updates on the views. Data may respond that it needs additional information. Nodes may find Data needs to be updated with information they hold.
== Conceptual Communications Model ==
{| class="wikitable"
!style="text-align:left;"|Node message (Req)
!style="text-align:left;"|Data Response (Rep)
!style="text-align:left;"|Node Action
|-
|rowspan="2"|Request View --->
|Reply with view data --->
|Process view info
|-
|Reply with Request for Information --->
|Prepare Information Feed
|-
|Request for Information Feed --->
|Reply with hash of Information received --->
|Store received Hash
|-
|Request Information Feed --->
|Reply with hash of Information received --->
|Store received updated Hash
|}
== Daemons ==
Data uses the cf-messagd daemon for message handling. cf-messaged answers queries and accepts feeds from nodes. Data writes feeds into a message queue in order to have an audit trail. The feeds are picked up and processed by a daemon that evaluates the feeds are propagates the data into The Universal Truth.

= Feeds =
Nodes send out feeds on request. This request is triggered by a Data response to an information request. The node assumes the requested information to be available from Data, but Data can decide to ask for more information before being able to supply the requested information.
== host ==
The node notifies Data about its existence with the host, domain, role feed.
<pre>
{
"host": {
"uqhost": "$(sys.uqhost)",
"domain": "$(sys.domain)",
"role": "$(classify.role)"
}
}
</pre>

= Schemas =
A Schema is the result set of a view represented in a json container.
== Roles ==
<pre>
{ "response": "tstutl",
"roles": [
{ "role":
{
"id": "apjums",
"name": "Apache Joomla User Managed Sites"
},
"role":
{
"id": "aptutl",
"name": "apt-cacher-ng mirror server for debian, red hat and suse platforms"
}
}
]
}
</pre>
== Nagios ==
<pre>
{
"response": "mnmutl",
"domains": [{
"domain": "webhuis.nl",
"services": [{
"service": "http",
"hosts": ["apjums0001", "mnmutl0001"]
}, {
"service": "tomcat",
"hosts": ["webjen0001", "webjen0002"]
}]
}, {
"domain": "hnvk.nl",
"services": [{
"service": "http",
"hosts": ["apjums0002", "mnmutl0002"]
}, {
"service": "tomcat",
"hosts": ["webjen0003", "webjen0004"]
}]
}]
}
</pre>

= Views =
Data presents information from The Universal Truth through views. cf_message obtains information from Data by presenting Data with the json-container defined by the view that corresponds to its role. Data returns the information in the json container that mirrors the request.
== Sample Dialogue ==
cf-agents through cf_message presents Data with a request on a view, a nagios view in this case:
<pre>
{ "message": "view",
"query":
{ "view_name": "mnmutl" }
}
</pre>
Nagios requests information on all the services offered by all the nodes in this symplified sample Universe. Data returns a json container with information, organized by domain, service and host.
<pre>
{
"response": "mnmutl",
"domains": [{
"domain": "webhuis.nl",
"services": [{
"service": "http",
"hosts": ["apjums0001", "mnmutl0001"]
}, {
"service": "tomcat",
"hosts": ["webjen0001", "webjen0002"]
}]
}, {
"domain": "hnvk.nl",
"services": [{
"service": "http",
"hosts": ["apjums0002", "mnmutl0002"]
}, {
"service": "tomcat",
"hosts": ["webjen0003", "webjen0004"]
}]
}]
}
</pre>
cf-agent on the Nagios host on its turn processes the json container supplied by Data, using the nagios templates, to construct the configuration files used by the Nagios server.

== CMDB ==

== Icinga ==
We prefer to use the Icinga server, but we did not succeed in getting the Debian webfronted going. It keeps sending out Internal Server messages, referring to the logs that do not give any clue at all.

== Nagios ==
Nagios only needs little information about the nodes in the Universe.
* Hostname, sys.uqhost
* Domain, sys.domain
* Service, delivered by the host
We feed back information on Services to Nagios. Each Service has a couple of parameters and an array of hosts fulfilling the service.
<pre>
{ "services": [ { "ssh": [ { "check_command": ""
{ "hosts": [ { "host": "<fqdn>" }, { "host": "<fqdn>" } ]
}
}]
}
</pre>
Hostgroups are implied by their domain and role, so each host belongs to the domain group and the groups of its role.
== View Queries ==
{| class="wikitable"
!style="text-align:left;"|View Name
!style="text-align:left;"|Sorted Result Set
!style="text-align:left;"|Selection Keys
!style="text-align:left;"|Comment
|-
|__________________________
|__________________________
|__________________________
|__________________________
|-
|Nagios View
|domain, uqhost, service
|host, domain, role
|Nagios groups and has service details
|}

<hr>
Return to: [[CFEngine]]