blob: 7ee20f4ddfe4d1a81743661aa101a2e6c5630f59 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
|
@title = 'Frequently asked questions'
@nav_title = 'FAQ'
@summary = "Frequently Asked Questions"
@toc = true
APT
===============
What do I do when unattended upgrades fail?
--------------------------------------------------
When you receive notification e-mails with a subject of 'unattended-upgrades result for $machinename', that means that some package couldn't be automatically upgraded and needs manual interaction. The reasons vary, so you have to be careful. Most often you can simply login to the affected machine and run `apt-get dist-upgrade`.
Puppet
======
Where do i find the time a server was last deployed ?
-----------------------------------------------------
Run:
leap history FILTER
This will tail the log file `/var/log/leap/deploy-summary.log`.
If that command fails, you can manually check the puppet state file on the node indicates the last puppetrun:
ls -la /var/lib/puppet/state/state.yaml
What resources are touched by puppet/leap_platform (services/packages/files etc.) ?
-----------------------------------------------------------------------------------
Log into your server and issue:
grep -v '!ruby/sym' /var/lib/puppet/state/state.yaml | sed 's/\"//' | sort
How can i customize the leap_platform puppet manifests ?
--------------------------------------------------------
You can create custom puppet modules under `files/puppet`.
The custom puppet entry point is in class 'custom' which can be put into
`files/puppet/modules/custom/manifests/init.pp`. This class gets automatically included
by site_config::default, which is applied to all nodes.
Of cause you can also create a different git branch and change whatever you want, if you are
familiar wit git.
Facter
======
How can i see custom facts distributed by leap_platform on a node ?
-------------------------------------------------------------------
On the server, export the FACTERLIB env. variable to include the path of the custom fact in question:
export FACTERLIB=/var/lib/puppet/lib/facter:/srv/leap/puppet/modules/stdlib/lib/facter/
facter
Etc
===
How do i change the domain of my provider ?
-------------------------------------------
* First of all, you need to have access to the nameserver config of your new domain.
* Update domain in provider.json
* remove all ca and cert files: `rm files/cert/* files/ca/*`
* create ca, csr and certs : `leap cert ca; leap cert csr; leap cert dh; leap cert update`
* deploy
|
