UploadLanguage (EN)Support
BusinessMobileSocial MediaMarketingTechnologyArt & PhotosCareerDesignEducationPresentations & Public SpeakingGovernment & NonprofitHealthcareInternetLawLeadership & ManagementAutomotiveEngineeringSoftwareRecruiting & HRRetailSalesServicesScienceSmall Business & EntrepreneurshipFoodEnvironmentEconomy & FinanceData & AnalyticsInvestor RelationsSportsSpiritualNews & PoliticsTravelSelf ImprovementReal EstateEntertainment & HumorHealth & MedicineDevices & HardwareLifestyle
Upload
Sign in
Alessandro Franceschi, profile picture
Uploaded byAlessandro Franceschi
PDF, PPTX1,115 views

Puppet Continuous Integration with PE and GitLab

The document discusses integrating Puppet Continuous Integration with Puppet Enterprise (PE) and GitLab. It covers the setup of code management, CI processes, and the necessary configurations for deploying code and running tests. Key topics include creating SSH keys, managing tokens, and utilizing CI scripts on GitLab to enhance code workflow.

Internet◦
Related topics:
Continuous Integration•
Download as PDF, PPTX
1 / 11
2 / 11
3 / 11
4 / 11
5 / 11
6 / 11
7 / 11
8 / 11
9 / 11
10 / 11
11 / 11
PUPPET CONTINUOUS INTEGRATION
 WITH PE AND GITLAB A L E S S A N D R O F R A N C E S C H I 
 P U P P E T C O N F 2 0 1 7
@ A LVA G A N T E • CTO @ example42 GmbH • Puppeteer since 2006 • More Ops than Dev
A G E N D A • PE Code Manager Setup • Puppet CI: What? • GitLab CI: Where? • Demo
C O D E M A N A G E R P E
P E C O D E M A N A G E R S E T U P • Create SSH keys to deploy control-repo via r10k: • stored on PE server • added on GitLab (deploy keys)
 • Generate token to deploy code: • Create PE user with Code Deployer role • Request token as this user • On Gitlab: copy token to control-repo webhook
 • Configure on Hiera or PE console puppet_enterprise::profile::master r10k_remote: <repo_url>
 r10k_private_key: <private_key_path>
 code_manager_auto_configure: true
W H AT ? C I
P U P P E T C I : W H AT ? • syntax checks • lint checks • commit check (danger.systems) • site modules spec tests • control-repo spec tests • control-repo integration tests • catalog diff • verify code-deployment status • run Puppet on canary nodes • check canary nodes status • trigger noop runs in production • generate documentation • manage code promotion
W H E R E C I
G I T L A B C I : W H E R E ? • On control-repo: • .gitlab-ci.yml • stages • jobs • scripts • tags • On gitlab-runners: • ssh keys to fetch modules • tokens or credentials to access PuppetDB, Puppet Server, GitLab... • gems and packages used in jobs
D E M O
T H A N K Y O U G R A P H I C S B Y TAT L I N . N E T