From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-sysadm/2010-October/000001.html | 72 ++ zarb-ml/mageia-sysadm/2010-October/000002.html | 65 ++ zarb-ml/mageia-sysadm/2010-October/000003.html | 86 +++ zarb-ml/mageia-sysadm/2010-October/000004.html | 74 ++ zarb-ml/mageia-sysadm/2010-October/000005.html | 114 +++ zarb-ml/mageia-sysadm/2010-October/000006.html | 111 +++ zarb-ml/mageia-sysadm/2010-October/000007.html | 90 +++ zarb-ml/mageia-sysadm/2010-October/000008.html | 99 +++ zarb-ml/mageia-sysadm/2010-October/000009.html | 97 +++ zarb-ml/mageia-sysadm/2010-October/000010.html | 77 ++ zarb-ml/mageia-sysadm/2010-October/000011.html | 72 ++ zarb-ml/mageia-sysadm/2010-October/000012.html | 103 +++ zarb-ml/mageia-sysadm/2010-October/000013.html | 81 +++ zarb-ml/mageia-sysadm/2010-October/000014.html | 103 +++ zarb-ml/mageia-sysadm/2010-October/000015.html | 130 ++++ zarb-ml/mageia-sysadm/2010-October/000016.html | 136 ++++ zarb-ml/mageia-sysadm/2010-October/000017.html | 94 +++ zarb-ml/mageia-sysadm/2010-October/000018.html | 146 ++++ zarb-ml/mageia-sysadm/2010-October/000019.html | 134 ++++ zarb-ml/mageia-sysadm/2010-October/000020.html | 66 ++ zarb-ml/mageia-sysadm/2010-October/000021.html | 74 ++ zarb-ml/mageia-sysadm/2010-October/000022.html | 87 +++ zarb-ml/mageia-sysadm/2010-October/000023.html | 83 +++ zarb-ml/mageia-sysadm/2010-October/000024.html | 84 +++ zarb-ml/mageia-sysadm/2010-October/000025.html | 92 +++ zarb-ml/mageia-sysadm/2010-October/000026.html | 95 +++ zarb-ml/mageia-sysadm/2010-October/000027.html | 88 +++ zarb-ml/mageia-sysadm/2010-October/000028.html | 94 +++ zarb-ml/mageia-sysadm/2010-October/000029.html | 101 +++ zarb-ml/mageia-sysadm/2010-October/000030.html | 107 +++ zarb-ml/mageia-sysadm/2010-October/000031.html | 89 +++ zarb-ml/mageia-sysadm/2010-October/000032.html | 102 +++ zarb-ml/mageia-sysadm/2010-October/000033.html | 109 +++ zarb-ml/mageia-sysadm/2010-October/000034.html | 117 ++++ zarb-ml/mageia-sysadm/2010-October/000035.html | 75 ++ zarb-ml/mageia-sysadm/2010-October/000036.html | 89 +++ zarb-ml/mageia-sysadm/2010-October/000037.html | 112 +++ zarb-ml/mageia-sysadm/2010-October/000038.html | 329 +++++++++ zarb-ml/mageia-sysadm/2010-October/000039.html | 91 +++ zarb-ml/mageia-sysadm/2010-October/000040.html | 89 +++ zarb-ml/mageia-sysadm/2010-October/000041.html | 136 ++++ zarb-ml/mageia-sysadm/2010-October/000042.html | 127 ++++ zarb-ml/mageia-sysadm/2010-October/000043.html | 97 +++ zarb-ml/mageia-sysadm/2010-October/000044.html | 157 +++++ zarb-ml/mageia-sysadm/2010-October/000045.html | 154 ++++ zarb-ml/mageia-sysadm/2010-October/000046.html | 131 ++++ zarb-ml/mageia-sysadm/2010-October/000047.html | 93 +++ zarb-ml/mageia-sysadm/2010-October/000048.html | 85 +++ zarb-ml/mageia-sysadm/2010-October/000049.html | 91 +++ zarb-ml/mageia-sysadm/2010-October/000050.html | 100 +++ zarb-ml/mageia-sysadm/2010-October/000051.html | 101 +++ zarb-ml/mageia-sysadm/2010-October/000052.html | 107 +++ zarb-ml/mageia-sysadm/2010-October/000053.html | 98 +++ zarb-ml/mageia-sysadm/2010-October/000054.html | 131 ++++ zarb-ml/mageia-sysadm/2010-October/000055.html | 100 +++ zarb-ml/mageia-sysadm/2010-October/000056.html | 77 ++ zarb-ml/mageia-sysadm/2010-October/000057.html | 88 +++ zarb-ml/mageia-sysadm/2010-October/000058.html | 85 +++ zarb-ml/mageia-sysadm/2010-October/000059.html | 87 +++ zarb-ml/mageia-sysadm/2010-October/000060.html | 106 +++ zarb-ml/mageia-sysadm/2010-October/000061.html | 129 ++++ zarb-ml/mageia-sysadm/2010-October/000062.html | 110 +++ zarb-ml/mageia-sysadm/2010-October/000063.html | 163 +++++ zarb-ml/mageia-sysadm/2010-October/000064.html | 83 +++ zarb-ml/mageia-sysadm/2010-October/000065.html | 189 +++++ zarb-ml/mageia-sysadm/2010-October/000066.html | 83 +++ zarb-ml/mageia-sysadm/2010-October/000067.html | 83 +++ zarb-ml/mageia-sysadm/2010-October/000068.html | 94 +++ zarb-ml/mageia-sysadm/2010-October/000069.html | 91 +++ zarb-ml/mageia-sysadm/2010-October/000070.html | 91 +++ zarb-ml/mageia-sysadm/2010-October/000071.html | 79 +++ zarb-ml/mageia-sysadm/2010-October/000072.html | 91 +++ zarb-ml/mageia-sysadm/2010-October/000073.html | 104 +++ zarb-ml/mageia-sysadm/2010-October/000074.html | 85 +++ zarb-ml/mageia-sysadm/2010-October/000075.html | 109 +++ zarb-ml/mageia-sysadm/2010-October/000076.html | 75 ++ zarb-ml/mageia-sysadm/2010-October/000077.html | 92 +++ zarb-ml/mageia-sysadm/2010-October/000078.html | 78 +++ zarb-ml/mageia-sysadm/2010-October/000079.html | 105 +++ zarb-ml/mageia-sysadm/2010-October/000080.html | 85 +++ zarb-ml/mageia-sysadm/2010-October/000081.html | 75 ++ zarb-ml/mageia-sysadm/2010-October/000082.html | 71 ++ zarb-ml/mageia-sysadm/2010-October/000083.html | 86 +++ zarb-ml/mageia-sysadm/2010-October/000084.html | 67 ++ zarb-ml/mageia-sysadm/2010-October/000085.html | 59 ++ zarb-ml/mageia-sysadm/2010-October/000086.html | 59 ++ zarb-ml/mageia-sysadm/2010-October/000087.html | 59 ++ zarb-ml/mageia-sysadm/2010-October/000088.html | 59 ++ zarb-ml/mageia-sysadm/2010-October/000089.html | 59 ++ zarb-ml/mageia-sysadm/2010-October/000090.html | 59 ++ zarb-ml/mageia-sysadm/2010-October/000091.html | 59 ++ zarb-ml/mageia-sysadm/2010-October/000092.html | 59 ++ zarb-ml/mageia-sysadm/2010-October/000093.html | 59 ++ zarb-ml/mageia-sysadm/2010-October/000094.html | 59 ++ zarb-ml/mageia-sysadm/2010-October/000095.html | 59 ++ zarb-ml/mageia-sysadm/2010-October/000096.html | 95 +++ zarb-ml/mageia-sysadm/2010-October/000097.html | 65 ++ zarb-ml/mageia-sysadm/2010-October/000098.html | 62 ++ zarb-ml/mageia-sysadm/2010-October/000099.html | 75 ++ zarb-ml/mageia-sysadm/2010-October/000100.html | 129 ++++ zarb-ml/mageia-sysadm/2010-October/000101.html | 114 +++ zarb-ml/mageia-sysadm/2010-October/000102.html | 78 +++ zarb-ml/mageia-sysadm/2010-October/000103.html | 102 +++ zarb-ml/mageia-sysadm/2010-October/000104.html | 64 ++ zarb-ml/mageia-sysadm/2010-October/000105.html | 65 ++ zarb-ml/mageia-sysadm/2010-October/000106.html | 65 ++ zarb-ml/mageia-sysadm/2010-October/000107.html | 65 ++ zarb-ml/mageia-sysadm/2010-October/000108.html | 65 ++ zarb-ml/mageia-sysadm/2010-October/000109.html | 65 ++ zarb-ml/mageia-sysadm/2010-October/000110.html | 65 ++ zarb-ml/mageia-sysadm/2010-October/000111.html | 65 ++ zarb-ml/mageia-sysadm/2010-October/000112.html | 65 ++ zarb-ml/mageia-sysadm/2010-October/000113.html | 65 ++ zarb-ml/mageia-sysadm/2010-October/000114.html | 65 ++ zarb-ml/mageia-sysadm/2010-October/000115.html | 65 ++ zarb-ml/mageia-sysadm/2010-October/000116.html | 65 ++ zarb-ml/mageia-sysadm/2010-October/000117.html | 87 +++ zarb-ml/mageia-sysadm/2010-October/000118.html | 64 ++ zarb-ml/mageia-sysadm/2010-October/000119.html | 64 ++ zarb-ml/mageia-sysadm/2010-October/000120.html | 97 +++ zarb-ml/mageia-sysadm/2010-October/000121.html | 87 +++ zarb-ml/mageia-sysadm/2010-October/000122.html | 93 +++ zarb-ml/mageia-sysadm/2010-October/000123.html | 81 +++ zarb-ml/mageia-sysadm/2010-October/000124.html | 77 ++ zarb-ml/mageia-sysadm/2010-October/000125.html | 157 +++++ zarb-ml/mageia-sysadm/2010-October/000126.html | 78 +++ zarb-ml/mageia-sysadm/2010-October/000127.html | 85 +++ zarb-ml/mageia-sysadm/2010-October/000128.html | 84 +++ zarb-ml/mageia-sysadm/2010-October/author.html | 687 ++++++++++++++++++ zarb-ml/mageia-sysadm/2010-October/date.html | 687 ++++++++++++++++++ zarb-ml/mageia-sysadm/2010-October/index.html | 1 + zarb-ml/mageia-sysadm/2010-October/subject.html | 687 ++++++++++++++++++ zarb-ml/mageia-sysadm/2010-October/thread.html | 895 ++++++++++++++++++++++++ 133 files changed, 14750 insertions(+) create mode 100644 zarb-ml/mageia-sysadm/2010-October/000001.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000002.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000003.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000004.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000005.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000006.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000007.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000008.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000009.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000010.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000011.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000012.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000013.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000014.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000015.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000016.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000017.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000018.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000019.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000020.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000021.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000022.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000023.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000024.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000025.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000026.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000027.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000028.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000029.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000030.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000031.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000032.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000033.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000034.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000035.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000036.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000037.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000038.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000039.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000040.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000041.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000042.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000043.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000044.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000045.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000046.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000047.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000048.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000049.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000050.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000051.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000052.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000053.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000054.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000055.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000056.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000057.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000058.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000059.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000060.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000061.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000062.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000063.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000064.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000065.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000066.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000067.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000068.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000069.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000070.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000071.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000072.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000073.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000074.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000075.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000076.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000077.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000078.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000079.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000080.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000081.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000082.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000083.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000084.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000085.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000086.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000087.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000088.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000089.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000090.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000091.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000092.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000093.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000094.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000095.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000096.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000097.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000098.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000099.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000100.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000101.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000102.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000103.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000104.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000105.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000106.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000107.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000108.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000109.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000110.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000111.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000112.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000113.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000114.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000115.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000116.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000117.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000118.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000119.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000120.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000121.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000122.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000123.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000124.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000125.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000126.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000127.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/000128.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/author.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/date.html create mode 120000 zarb-ml/mageia-sysadm/2010-October/index.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/subject.html create mode 100644 zarb-ml/mageia-sysadm/2010-October/thread.html (limited to 'zarb-ml/mageia-sysadm/2010-October') diff --git a/zarb-ml/mageia-sysadm/2010-October/000001.html b/zarb-ml/mageia-sysadm/2010-October/000001.html new file mode 100644 index 000000000..b231871e6 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000001.html @@ -0,0 +1,72 @@ + + + + [Mageia-sysadm] meetbot migration to the gandibox + + + + + + + + + +

[Mageia-sysadm] meetbot migration to the gandibox

+ Michael Scherer + misc at zarb.org +
+ Fri Oct 1 03:27:02 CEST 2010 +

+
+ +
Hi,
+
+I have migrated the meetbot instance to the gandibox server, with a
+plugin backported from 2010.1. A new user was created for this, the bot
+have been copied, and some basic documentation can be found in
+~irc_bots/documentation/
+
+I have also removed Backport and Testing sources, as well as debug and
+Non-free, installed apache-mpm-prefork, fixed /etc/hosts so apache could
+start ( and notified a gandi coder of the problem ), added a cname
+meetbot.mageia.org to the server, with corresponding vhost and settings,
+and set up a autostart based on cron (with @reboot syntax ).
+
+I have also installed screen, zsh and bash-completion.
+
+-- 
+Michael Scherer
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000002.html b/zarb-ml/mageia-sysadm/2010-October/000002.html new file mode 100644 index 000000000..27bbe2a98 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000002.html @@ -0,0 +1,65 @@ + + + + [Mageia-sysadm] servers configuration tool + + + + + + + + + +

[Mageia-sysadm] servers configuration tool

+ nicolas vigier + boklm at mars-attacks.org +
+ Fri Oct 1 12:29:36 CEST 2010 +

+
+ +
Hello,
+
+On Mandriva build system we were using cfengine. I think cfengine is
+quite simple, works correctly, and some of us already know how to use
+it. But other people are also using puppet. Do you have opinions about
+what we should use for Mageia servers ?
+
+Nicolas
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000003.html b/zarb-ml/mageia-sysadm/2010-October/000003.html new file mode 100644 index 000000000..778223c2d --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000003.html @@ -0,0 +1,86 @@ + + + + [Mageia-sysadm] servers configuration tool + + + + + + + + + +

[Mageia-sysadm] servers configuration tool

+ Michael Scherer + misc at zarb.org +
+ Fri Oct 1 13:54:14 CEST 2010 +

+
+ +
Le vendredi 01 octobre 2010 à 12:29 +0200, nicolas vigier a écrit :
+> Hello,
+> 
+> On Mandriva build system we were using cfengine. I think cfengine is
+> quite simple, works correctly, and some of us already know how to use
+> it. 
+
+what version of cfengine ? because there is cfengine 2, not maintained
+AFAIK, and cfengine 3, that none of us know.
+
+> But other people are also using puppet. Do you have opinions about
+> what we should use for Mageia servers ?
+
+Having to use cfengine 2 on zarb and mdv, and puppet on my own server, I
+would say I prefer puppet.
+
+Puppet community seems more alive, and favors a modular approach. I also
+think it is easier to extend and understand ( both use a dsl, but I
+found it as easier to understand puppet dsl than cfengine one ).
+
+Guillomovitch proposed we switch to puppet, but I do not exactly know
+the reason.
+
+On the other hand, we already have part of the configuration from mdv in
+cfengine, which is a important point too.
+
+-- 
+Michael Scherer
+
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000004.html b/zarb-ml/mageia-sysadm/2010-October/000004.html new file mode 100644 index 000000000..e40ecbdb0 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000004.html @@ -0,0 +1,74 @@ + + + + [Mageia-sysadm] presentations + + + + + + + + + +

[Mageia-sysadm] presentations

+ nicolas vigier + boklm at mars-attacks.org +
+ Wed Oct 6 16:02:20 CEST 2010 +

+
+ +
Hello,
+
+This is the current list of people in the sysadmin team :
+- boklm
+- damsweb
+- rapsys
+- misc
+- sevalienor 
+- coling
+- neoclust
+- TMB 
+
+As misc suggested, we can present ourself on this mailing list. So you
+can answer to this thread to present you.
+
+Nicolas
+
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000005.html b/zarb-ml/mageia-sysadm/2010-October/000005.html new file mode 100644 index 000000000..aef688628 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000005.html @@ -0,0 +1,114 @@ + + + + [Mageia-sysadm] presentations + + + + + + + + + +

[Mageia-sysadm] presentations

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Wed Oct 6 16:52:47 CEST 2010 +

+
+ +
'Twas brillig, and nicolas vigier at 06/10/10 15:02 did gyre and gimble:
+> This is the current list of people in the sysadmin team :
+> - boklm
+> - damsweb
+> - rapsys
+> - misc
+> - sevalienor 
+> - coling
+> - neoclust
+> - TMB 
+> 
+> As misc suggested, we can present ourself on this mailing list. So you
+> can answer to this thread to present you.
+
+Hello!
+
+I'm Colin. I'm sure most of you know me from before so I'll forego the
+full introduction!
+
+In terms of sysadmin, I tend to be fairly available (not all the time
+obviously, but I'm usually not too far away) and thus can help out when
+dealing when things go wrong at awkward times etc.
+
+In terms of skills related to sysadmin work, I maintain two web hosting
+infrastructures based on RHEL and CentOS and look after our (modest)
+office infrastructure (mostly based on Mandriva 2010.1 + OSX - no windows!).
+
+I've experience with MySQL, Apache, Bind, DHCP, LDAP, Subversion, Git
+and SSH + all the usual things.
+
+I tend to overcomplicate my home network "for fun" to try and expand my
+experience in that area.
+
+I think that will do as a introduction to me :D
+
+
+Cheers
+
+Col
+
+
+PS Can the reply-to for this list be set to the list address please?
+
+
+-- 
+
+Colin Guthrie
+mageia(at)colin.guthr.ie
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited [http://www.tribalogic.net/]
+Open Source:
+  Mageia Contributor [http://www.mageia.org/]
+  PulseAudio Hacker [http://www.pulseaudio.org/]
+  Trac Hacker [http://trac.edgewall.org/]
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000006.html b/zarb-ml/mageia-sysadm/2010-October/000006.html new file mode 100644 index 000000000..1ff0512e1 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000006.html @@ -0,0 +1,111 @@ + + + + [Mageia-sysadm] presentations + + + + + + + + + +

[Mageia-sysadm] presentations

+ Michael Scherer + misc at zarb.org +
+ Wed Oct 6 18:16:58 CEST 2010 +

+
+ +
Le mercredi 06 octobre 2010 à 16:02 +0200, nicolas vigier a écrit :
+> Hello,
+> 
+> This is the current list of people in the sysadmin team :
+> - boklm
+> - damsweb
+> - rapsys
+> - misc
+> - sevalienor 
+> - coling
+> - neoclust
+> - TMB 
+> 
+> As misc suggested, we can present ourself on this mailing list. So you
+> can answer to this thread to present you.
+
+
+
+Ok, so for those that do not know me ( ie, nobody, since I have met in
+person every one on the list ), my name is Michael Scherer, I am living
+most of the time in Paris suburb with Olivier Thauvin ( nanar ).
+
+I have been involved in Mandriva since a long time, first as a packager,
+then as a trainee, then again as a packager and a sysadmin of the
+cluster. I am also a admin of zarb.org servers, and involved in various 
+free software activity. I have no job at the moment, but this may change
+in the end of the week.
+ 
+I have been working as sysadmin for Council of Europe for 3 months, and
+as a python coder for 1 year and half for INL and the CNRS ( french
+research institute ).
+
+Regarding my technical skills, I can code in perl, ruby, little bit of
+C, ruby, and php among others.
+
+As a sysadmin and like colin, I also know the usual stuff : apache,
+postfix, nagios, munin, openldap, netfilter, etc. I have been quite
+interested in puppet recently, having converted my own servers to it,
+and I try also to expand my knowledge by using uncommon software for fun
+( like powerdns, nginx, quagga ( yeah, there is a ospf router in the
+home network )). 
+
+And I have the super power of firewall piercing :)
+
+I am often available by night and in the afternoon ( Paris time ), but I
+am also often out of the town. 
+
+-- 
+Michael Scherer
+
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000007.html b/zarb-ml/mageia-sysadm/2010-October/000007.html new file mode 100644 index 000000000..2492aa559 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000007.html @@ -0,0 +1,90 @@ + + + + [Mageia-sysadm] presentations + + + + + + + + + +

[Mageia-sysadm] presentations

+ Michael Scherer + misc at zarb.org +
+ Wed Oct 6 18:31:36 CEST 2010 +

+
+ +
Le mercredi 06 octobre 2010 à 15:52 +0100, Colin Guthrie a écrit :
+
+> PS Can the reply-to for this list be set to the list address please?
+
+Done
+
+FYI, I am in favor of changing from mailman to sympa ( because mailman
+default are annoying, and because sympa can get users from ldap, which
+seems to be a big win in the long run ).
+
+And I would also like to make this list public ( albeit with restricted
+posting for us ). Public because :
+- we want to promote openess
+- we can refer to our discussions to others groups this way
+- people who will join the team later will be able to see how we work
+before joining
+- people will ( I hope ) not ask us news when they can have the same
+level of access than us to the information
+- we can use a external search engine to find our discussions
+- we will not appear like cabal 
+- and others sysadmins groups ( for other projects ) could get
+information from us, which could help them to setup their own projects
+
+I see however some downsides :
+- we cannot discuss confidential or private matters ( like people real
+name, security incident if there is a embargo )
+- we should take care of not telling too much about us ( example : "i am
+gone in holiday for 3 weeks, come and rob my house" )
+
+WDYT ?
+-- 
+Michael Scherer
+
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000008.html b/zarb-ml/mageia-sysadm/2010-October/000008.html new file mode 100644 index 000000000..021045ef1 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000008.html @@ -0,0 +1,99 @@ + + + + [Mageia-sysadm] presentations + + + + + + + + + +

[Mageia-sysadm] presentations

+ nicolas vigier + boklm at mars-attacks.org +
+ Thu Oct 7 14:22:42 CEST 2010 +

+
+ +
On Wed, 06 Oct 2010, Michael Scherer wrote:
+
+> Le mercredi 06 octobre 2010 à 15:52 +0100, Colin Guthrie a écrit :
+> 
+> > PS Can the reply-to for this list be set to the list address please?
+> 
+> Done
+> 
+> FYI, I am in favor of changing from mailman to sympa ( because mailman
+> default are annoying, and because sympa can get users from ldap, which
+> seems to be a big win in the long run ).
+
+Yes. I agree.
+
+> And I would also like to make this list public ( albeit with restricted
+> posting for us ). Public because :
+> - we want to promote openess
+> - we can refer to our discussions to others groups this way
+> - people who will join the team later will be able to see how we work
+> before joining
+> - people will ( I hope ) not ask us news when they can have the same
+> level of access than us to the information
+> - we can use a external search engine to find our discussions
+> - we will not appear like cabal 
+> - and others sysadmins groups ( for other projects ) could get
+> information from us, which could help them to setup their own projects
+> 
+> I see however some downsides :
+> - we cannot discuss confidential or private matters ( like people real
+> name, security incident if there is a embargo )
+> - we should take care of not telling too much about us ( example : "i am
+> gone in holiday for 3 weeks, come and rob my house" )
+> 
+> WDYT ?
+
+I agree that most discussions should be public. Maybe we could have a
+second mailing list for public discussions. And keep this one private,
+to receive crontab emails (if they can potentially contain confidential
+infos), and other private emails ?
+
+Nicolas
+
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000009.html b/zarb-ml/mageia-sysadm/2010-October/000009.html new file mode 100644 index 000000000..cb14f7fc4 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000009.html @@ -0,0 +1,97 @@ + + + + [Mageia-sysadm] presentations + + + + + + + + + +

[Mageia-sysadm] presentations

+ Michael Scherer + misc at zarb.org +
+ Thu Oct 7 14:42:18 CEST 2010 +

+
+ +
Le jeudi 07 octobre 2010 à 14:22 +0200, nicolas vigier a écrit :
+
+> > And I would also like to make this list public ( albeit with restricted
+> > posting for us ). Public because :
+> > - we want to promote openess
+> > - we can refer to our discussions to others groups this way
+> > - people who will join the team later will be able to see how we work
+> > before joining
+> > - people will ( I hope ) not ask us news when they can have the same
+> > level of access than us to the information
+> > - we can use a external search engine to find our discussions
+> > - we will not appear like cabal 
+> > - and others sysadmins groups ( for other projects ) could get
+> > information from us, which could help them to setup their own projects
+> > 
+> > I see however some downsides :
+> > - we cannot discuss confidential or private matters ( like people real
+> > name, security incident if there is a embargo )
+> > - we should take care of not telling too much about us ( example : "i am
+> > gone in holiday for 3 weeks, come and rob my house" )
+> > 
+> > WDYT ?
+> 
+> I agree that most discussions should be public. Maybe we could have a
+> second mailing list for public discussions. And keep this one private,
+> to receive crontab emails (if they can potentially contain confidential
+> infos), and other private emails ?
+
+Well, if crontab emails contained informations, even non confidential,
+it would be a good start :)
+
+I would prefer to have a -private list, so people know that private is a
+exception rather then the norm.
+
+
+( and boklm, we didn't have your mail for the presentation )
+( and for the others too )
+-- 
+Michael Scherer
+
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000010.html b/zarb-ml/mageia-sysadm/2010-October/000010.html new file mode 100644 index 000000000..fba179541 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000010.html @@ -0,0 +1,77 @@ + + + + [Mageia-sysadm] presentations + + + + + + + + + +

[Mageia-sysadm] presentations

+ nicolas vigier + boklm at mars-attacks.org +
+ Thu Oct 7 15:14:00 CEST 2010 +

+
+ +
On Wed, 06 Oct 2010, nicolas vigier wrote:
+
+> 
+> As misc suggested, we can present ourself on this mailing list. So you
+> can answer to this thread to present you.
+
+Ok. Présentation for me :
+I was previously working at Mandriva (actually Edge-IT) since January
+2007. I was working mainly on R&D projects (XtreemOS, qualipso, etc
+...), and also as admin of the build system.
+
+I know how to admin the usual software like postfix, apache, bind, svn,
+etc ...
+
+And I am living in Paris, so I can probably have access to Vitry
+datacenter where we will be hosting most Mageia servers.
+
+Nicolas
+
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000011.html b/zarb-ml/mageia-sysadm/2010-October/000011.html new file mode 100644 index 000000000..8c9890071 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000011.html @@ -0,0 +1,72 @@ + + + + [Mageia-sysadm] presentations + + + + + + + + + +

[Mageia-sysadm] presentations

+ nicolas vigier + boklm at mars-attacks.org +
+ Thu Oct 7 15:18:02 CEST 2010 +

+
+ +
On Thu, 07 Oct 2010, Michael Scherer wrote:
+
+> > 
+> > I agree that most discussions should be public. Maybe we could have a
+> > second mailing list for public discussions. And keep this one private,
+> > to receive crontab emails (if they can potentially contain confidential
+> > infos), and other private emails ?
+> 
+> Well, if crontab emails contained informations, even non confidential,
+> it would be a good start :)
+> 
+> I would prefer to have a -private list, so people know that private is a
+> exception rather then the norm.
+
+Ok, yes, it's more clear with private in the name.
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000012.html b/zarb-ml/mageia-sysadm/2010-October/000012.html new file mode 100644 index 000000000..f0c4dd57b --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000012.html @@ -0,0 +1,103 @@ + + + + [Mageia-sysadm] presentations + + + + + + + + + +

[Mageia-sysadm] presentations

+ Thomas Backlund + tmb at iki.fi +
+ Thu Oct 7 19:10:52 CEST 2010 +

+
+ +
nicolas vigier skrev 6.10.2010 17:02:
+> Hello,
+>
+> This is the current list of people in the sysadmin team :
+
+> - TMB
+
+> As misc suggested, we can present ourself on this mailing list. So you
+> can answer to this thread to present you.
+>
+
+So,
+I am Thomas Backlund, and have been using Redhat until about 2001, and 
+switched to Mandr* Linux and been a user/sysadmin since that.
+
+I mostly do kernels, and my first "help" with main kernels was IIRC 
+around 2.4.21-0.pre4.3mdk, and my first tmb series kernels rolled out:
+* Thu Aug 28 2003 Thomas Backlund <tmb at iki.fi> 2.4.22-1.tmb.1mdk
+:)
+
+I maintain some linux servers both at home, work and for some external 
+companys..
+
+I know may way around LAMP, DNS/DHCP, ssh, postfix, some LDAP, VCS, ...
+
+I usually monitor my e-mail almost constantly when I'm awake,
+and most of the times I have good internet connections, so remote access 
+isn't a problem...
+And weekends I'm usually up very late (sometimes until the morning and 
+the neighbours wake up :)...)
+
+At work I'm primary Manager/Responsible for Linux, Firewalls and a 
+2008R2 AD network with Windows and Mac OSX workstations...
+I also am responsible for Exchange and mail flow/spam filtering...
+
+I'm always interested in new things, both on hw and sw side :)
+
+I'm planning to get me an Android phone, and sticking Mageia on it at 
+some point too :)
+
+Thats all for now...
+
+--
+Thomas
+
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000013.html b/zarb-ml/mageia-sysadm/2010-October/000013.html new file mode 100644 index 000000000..1a44e9f5d --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000013.html @@ -0,0 +1,81 @@ + + + + [Mageia-sysadm] presentations + + + + + + + + + +

[Mageia-sysadm] presentations

+ Derek Morgan + dmorganec at gmail.com +
+ Thu Oct 7 23:59:30 CEST 2010 +

+
+ +
Hi,
+
+My name is Derek Morgan, i leave in france and had lessons on network (
+ldap, postfix, ... ), i can learn stuff i don't know yet (  and i love to
+learn :) ).
+
+I am available all day and night if needed ( like nagios sending sms ).
+
+
+I will be happy to help on configuring Gosa to help to configure our ldap
+easily, and other things when needed.
+
+
+I am proud to be part of mageia sysadmin team.
+
+
+
+---
+Derek Morgan
+FBI
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <https://www.mageia.org/mailman/private/mageia-sysadm/attachments/20101007/de95cea9/attachment.html>
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000014.html b/zarb-ml/mageia-sysadm/2010-October/000014.html new file mode 100644 index 000000000..f6f68e640 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000014.html @@ -0,0 +1,103 @@ + + + + [Mageia-sysadm] Infos about the machines + + + + + + + + + +

[Mageia-sysadm] Infos about the machines

+ nicolas vigier + boklm at mars-attacks.org +
+ Fri Oct 8 01:07:38 CEST 2010 +

+
+ +
Hello,
+
+Here is some infos about the machines we have, or we will have.
+
+Currently we have those machines available :
+- one dedibox server :
+  http://www.online.net/serveur-dedie/offre-dedibox-v3.xhtml
+- two gandi virtual machines, one share for each :
+  http://en.gandi.net/hosting/
+
+Later, we should be able to install some machines in a datacenter
+(thanks to rapsys). It should be at least 4 powerfull machines. Each
+one should have between 4 and 12 cores, 8 or 12GB of RAM, and a lot of
+disk space.
+
+Before we are able to setup the machines in the datacenter, we can start
+using the machines we already have. They are currently used for this :
+ - the dedibox is used to setup the forum
+ - the first gandi VM is used by :
+   * meetbot
+   * a temporary svn server (to host the website, and servers config)
+   * an ldap server (Buchan is working on it)
+ - the second gandi VM is not used yet, but should be used to host the
+   main website soon
+
+I think we can probably start soon to setup the following services :
+ - dns servers (one on a gandi VM, an other one on the dedibox)
+ - mailing list server on ml.mageia.org on the dedibox as we may need
+   new lists soon to organize teams. If using sympa, with users managed by
+   the ldap server, we need the ldap server and its web interface ready.
+   But we can start testing now.
+ - main mageia web site (on the second gandi VM)
+ - epoll
+
+Later, the machines in the datacenter can be used for this :
+ - Server1: bugzilla/nagios/dns1/sql/ldap/api/mail/mailling/pastebin/wiki/planet
+ - Server2: svn/git/BS scheduler/hdlists/primary mirror
+ - Server3: BS node
+ - Server4: BS node
+
+If you have any other ideas, comments or questions, don't hesitate to
+reply.
+
+Nicolas
+
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000015.html b/zarb-ml/mageia-sysadm/2010-October/000015.html new file mode 100644 index 000000000..19561abdb --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000015.html @@ -0,0 +1,130 @@ + + + + [Mageia-sysadm] Infos about the machines + + + + + + + + + +

[Mageia-sysadm] Infos about the machines

+ Michael Scherer + misc at zarb.org +
+ Fri Oct 8 01:41:30 CEST 2010 +

+
+ +
Le vendredi 08 octobre 2010 à 01:07 +0200, nicolas vigier a écrit :
+> Hello,
+> 
+> Here is some infos about the machines we have, or we will have.
+> 
+> Currently we have those machines available :
+> - one dedibox server :
+>   http://www.online.net/serveur-dedie/offre-dedibox-v3.xhtml
+> - two gandi virtual machines, one share for each :
+>   http://en.gandi.net/hosting/
+> 
+> Later, we should be able to install some machines in a datacenter
+> (thanks to rapsys). It should be at least 4 powerfull machines. Each
+> one should have between 4 and 12 cores, 8 or 12GB of RAM, and a lot of
+> disk space.
+> 
+> Before we are able to setup the machines in the datacenter, we can start
+> using the machines we already have. They are currently used for this :
+>  - the dedibox is used to setup the forum
+>  - the first gandi VM is used by :
+>    * meetbot
+>    * a temporary svn server (to host the website, and servers config)
+>    * an ldap server (Buchan is working on it)
+>  - the second gandi VM is not used yet, but should be used to host the
+>    main website soon
+> 
+> I think we can probably start soon to setup the following services :
+>  - dns servers (one on a gandi VM, an other one on the dedibox)
+>  - mailing list server on ml.mageia.org on the dedibox as we may need
+>    new lists soon to organize teams. If using sympa, with users managed by
+>    the ldap server, we need the ldap server and its web interface ready.
+>    But we can start testing now.
+>  - main mageia web site (on the second gandi VM)
+>  - epoll
+> 
+> Later, the machines in the datacenter can be used for this :
+>  - Server1: bugzilla/nagios/dns1/sql/ldap/api/mail/mailling/pastebin/wiki/planet
+John have working on updating planet on zarb.org, i guess he will be
+able to transfer that.
+
+>  - Server2: svn/git/BS scheduler/hdlists/primary mirror
+is this were the key to sign packages will be kept ?
+
+>  - Server3: BS node
+>  - Server4: BS node
+
+Does people have direct access on both ?
+
+> If you have any other ideas, comments or questions, don't hesitate to
+> reply.
+
+No backup server ? No postfix ( primary and secondary ) ? No wiki ?
+Would all web applications be hosted on the same server ( ie epoll,
+transifex and other applications ? )
+
+We should have a secondary ldap. I would also add a ticket system which
+is not bugzilla ( as infrastructure as a product would be weird ).
+
+And we may need somewhere to write the doc, if possible something that
+can be used offline.
+
+We also need to discuss what is our responsibility and what is not ( ie,
+who is root on what server, mainly the website one, and who decide of
+the various setting, mainly php/apache ). I would propose that we
+leverage a VCS + some soft like cfengine/puppet to delegate some part
+( like some vhosts settings on some server ) to some others groups ( and
+this would also provides tracability, ie, no direct root access ).  
+
+
+-- 
+Michael Scherer
+
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000016.html b/zarb-ml/mageia-sysadm/2010-October/000016.html new file mode 100644 index 000000000..decc4e322 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000016.html @@ -0,0 +1,136 @@ + + + + [Mageia-sysadm] Infos about the machines + + + + + + + + + +

[Mageia-sysadm] Infos about the machines

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Fri Oct 8 09:58:48 CEST 2010 +

+
+ +
'Twas brillig, and Michael Scherer at 08/10/10 00:41 did gyre and gimble:
+> Le vendredi 08 octobre 2010 à 01:07 +0200, nicolas vigier a écrit :
+>> Hello,
+>>
+>> Here is some infos about the machines we have, or we will have.
+>>
+>> Currently we have those machines available :
+>> - one dedibox server :
+>>   http://www.online.net/serveur-dedie/offre-dedibox-v3.xhtml
+>> - two gandi virtual machines, one share for each :
+>>   http://en.gandi.net/hosting/
+>>
+>> Later, we should be able to install some machines in a datacenter
+>> (thanks to rapsys). It should be at least 4 powerfull machines. Each
+>> one should have between 4 and 12 cores, 8 or 12GB of RAM, and a lot of
+>> disk space.
+>>
+>> Before we are able to setup the machines in the datacenter, we can start
+>> using the machines we already have. They are currently used for this :
+>>  - the dedibox is used to setup the forum
+>>  - the first gandi VM is used by :
+>>    * meetbot
+>>    * a temporary svn server (to host the website, and servers config)
+>>    * an ldap server (Buchan is working on it)
+>>  - the second gandi VM is not used yet, but should be used to host the
+>>    main website soon
+>>
+>> I think we can probably start soon to setup the following services :
+>>  - dns servers (one on a gandi VM, an other one on the dedibox)
+>>  - mailing list server on ml.mageia.org on the dedibox as we may need
+>>    new lists soon to organize teams. If using sympa, with users managed by
+>>    the ldap server, we need the ldap server and its web interface ready.
+>>    But we can start testing now.
+>>  - main mageia web site (on the second gandi VM)
+>>  - epoll
+>>
+>> Later, the machines in the datacenter can be used for this :
+>>  - Server1: bugzilla/nagios/dns1/sql/ldap/api/mail/mailling/pastebin/wiki/planet
+> John have working on updating planet on zarb.org, i guess he will be
+> able to transfer that.
+> 
+> No backup server ? No postfix ( primary and secondary ) ? No wiki ?
+> Would all web applications be hosted on the same server ( ie epoll,
+> transifex and other applications ? )
+
+"mail" is mentioned above which I presume to mean postfix. Shall we just
+decide now not to host any mail accounts (i.e. pop or imap) and only
+provide forwarding services or will we provide real accounts?
+
+> We should have a secondary ldap. I would also add a ticket system which
+> is not bugzilla ( as infrastructure as a product would be weird ).
+
+Is it really worth adding a separate ticketing system for this?
+Integrating it with LDAP so people can report problems etc. etc. (or
+would you prefer an uber simple ticket system so that if someone wants
+to report that e.g. LDAP is broken, they'll be able to! :D
+
+> And we may need somewhere to write the doc, if possible something that
+> can be used offline.
+
+Doc in git? Download it locally or view it live on web, plus update it
+easily? Just a thought.
+
+Col
+
+
+-- 
+
+Colin Guthrie
+mageia(at)colin.guthr.ie
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited [http://www.tribalogic.net/]
+Open Source:
+  Mageia Contributor [http://www.mageia.org/]
+  PulseAudio Hacker [http://www.pulseaudio.org/]
+  Trac Hacker [http://trac.edgewall.org/]
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000017.html b/zarb-ml/mageia-sysadm/2010-October/000017.html new file mode 100644 index 000000000..7278c95d5 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000017.html @@ -0,0 +1,94 @@ + + + + [Mageia-sysadm] servers configuration tool + + + + + + + + + +

[Mageia-sysadm] servers configuration tool

+ nicolas vigier + boklm at mars-attacks.org +
+ Fri Oct 8 11:34:46 CEST 2010 +

+
+ +
On Fri, 01 Oct 2010, Michael Scherer wrote:
+
+> Le vendredi 01 octobre 2010 à 12:29 +0200, nicolas vigier a écrit :
+> > Hello,
+> > 
+> > On Mandriva build system we were using cfengine. I think cfengine is
+> > quite simple, works correctly, and some of us already know how to use
+> > it. 
+> 
+> what version of cfengine ? because there is cfengine 2, not maintained
+> AFAIK, and cfengine 3, that none of us know.
+> 
+> > But other people are also using puppet. Do you have opinions about
+> > what we should use for Mageia servers ?
+> 
+> Having to use cfengine 2 on zarb and mdv, and puppet on my own server, I
+> would say I prefer puppet.
+> 
+> Puppet community seems more alive, and favors a modular approach. I also
+> think it is easier to extend and understand ( both use a dsl, but I
+> found it as easier to understand puppet dsl than cfengine one ).
+> 
+> Guillomovitch proposed we switch to puppet, but I do not exactly know
+> the reason.
+
+Interesting. I have never used puppet, but I'm ok to use it (if you
+think that's better).
+
+> On the other hand, we already have part of the configuration from mdv in
+> cfengine, which is a important point too.
+
+I think we did not use very advanced features of cfengine, so maybe it
+would be not too difficult to convert to puppet.
+
+By the way, do you have a backup of the cfengine directory on the
+Mandriva build system ?
+
+Nicolas
+
+
+ + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000018.html b/zarb-ml/mageia-sysadm/2010-October/000018.html new file mode 100644 index 000000000..156b6888c --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000018.html @@ -0,0 +1,146 @@ + + + + [Mageia-sysadm] Infos about the machines + + + + + + + + + +

[Mageia-sysadm] Infos about the machines

+ Michael Scherer + misc at zarb.org +
+ Fri Oct 8 15:37:42 CEST 2010 +

+
+ +
Le vendredi 08 octobre 2010 à 08:58 +0100, Colin Guthrie a écrit :
+> 'Twas brillig, and Michael Scherer at 08/10/10 00:41 did gyre and gimble:
+> > Le vendredi 08 octobre 2010 à 01:07 +0200, nicolas vigier a écrit :
+> >> Hello,
+> >>
+> >> Here is some infos about the machines we have, or we will have.
+> >>
+> >> Currently we have those machines available :
+> >> - one dedibox server :
+> >>   http://www.online.net/serveur-dedie/offre-dedibox-v3.xhtml
+> >> - two gandi virtual machines, one share for each :
+> >>   http://en.gandi.net/hosting/
+> >>
+> >> Later, we should be able to install some machines in a datacenter
+> >> (thanks to rapsys). It should be at least 4 powerfull machines. Each
+> >> one should have between 4 and 12 cores, 8 or 12GB of RAM, and a lot of
+> >> disk space.
+> >>
+> >> Before we are able to setup the machines in the datacenter, we can start
+> >> using the machines we already have. They are currently used for this :
+> >>  - the dedibox is used to setup the forum
+> >>  - the first gandi VM is used by :
+> >>    * meetbot
+> >>    * a temporary svn server (to host the website, and servers config)
+> >>    * an ldap server (Buchan is working on it)
+> >>  - the second gandi VM is not used yet, but should be used to host the
+> >>    main website soon
+> >>
+> >> I think we can probably start soon to setup the following services :
+> >>  - dns servers (one on a gandi VM, an other one on the dedibox)
+> >>  - mailing list server on ml.mageia.org on the dedibox as we may need
+> >>    new lists soon to organize teams. If using sympa, with users managed by
+> >>    the ldap server, we need the ldap server and its web interface ready.
+> >>    But we can start testing now.
+> >>  - main mageia web site (on the second gandi VM)
+> >>  - epoll
+> >>
+> >> Later, the machines in the datacenter can be used for this :
+> >>  - Server1: bugzilla/nagios/dns1/sql/ldap/api/mail/mailling/pastebin/wiki/planet
+> > John have working on updating planet on zarb.org, i guess he will be
+> > able to transfer that.
+> > 
+> > No backup server ? No postfix ( primary and secondary ) ? No wiki ?
+> > Would all web applications be hosted on the same server ( ie epoll,
+> > transifex and other applications ? )
+> 
+> "mail" is mentioned above which I presume to mean postfix. Shall we just
+> decide now not to host any mail accounts (i.e. pop or imap) and only
+> provide forwarding services or will we provide real accounts?
+
+indeed. I think we should start small and give alias only.
+
+> > We should have a secondary ldap. I would also add a ticket system which
+> > is not bugzilla ( as infrastructure as a product would be weird ).
+> 
+> Is it really worth adding a separate ticketing system for this?
+> Integrating it with LDAP so people can report problems etc. etc. (or
+> would you prefer an uber simple ticket system so that if someone wants
+> to report that e.g. LDAP is broken, they'll be able to! :D
+
+I would hope that 
+1) nagios could detect when ldap is broken
+2) user could contact us in case of problem without using ticket ( even
+if we should not do it too often, cause this may be a mess )
+
+Regarding a separate ticket, well, maybe we can find something that
+could be best suited to our duty.
+
+Ie, there is no version or release, nor plateform, nor source rpm or
+specific data for the infrastructure.
+
+Or more precisely, there is maybe specific adjustments to do that would
+conflict with a bugzilla used for software, and packages. For example,
+we can decide to have a field "server", that would not make sense. We
+may also want to not interfere with packagers stats, or think like
+that. 
+
+But I am not sure, hence my question :)
+
+> > And we may need somewhere to write the doc, if possible something that
+> > can be used offline.
+> 
+> Doc in git? Download it locally or view it live on web, plus update it
+> easily? Just a thought.
+
+Well, a doc in a vcs, along with configuration, yup.
+-- 
+Michael Scherer
+
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000019.html b/zarb-ml/mageia-sysadm/2010-October/000019.html new file mode 100644 index 000000000..090f8d919 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000019.html @@ -0,0 +1,134 @@ + + + + [Mageia-sysadm] Infos about the machines + + + + + + + + + +

[Mageia-sysadm] Infos about the machines

+ nicolas vigier + boklm at mars-attacks.org +
+ Fri Oct 8 16:29:30 CEST 2010 +

+
+ +
On Fri, 08 Oct 2010, Michael Scherer wrote:
+
+> > 
+> > Later, the machines in the datacenter can be used for this :
+> >  - Server1: bugzilla/nagios/dns1/sql/ldap/api/mail/mailling/pastebin/wiki/planet
+> John have working on updating planet on zarb.org, i guess he will be
+> able to transfer that.
+
+Good !
+
+> 
+> >  - Server2: svn/git/BS scheduler/hdlists/primary mirror
+> is this were the key to sign packages will be kept ?
+
+Yes, at least for Cooker.
+
+> 
+> >  - Server3: BS node
+> >  - Server4: BS node
+> 
+> Does people have direct access on both ?
+
+I think that for security, we should not allow people to log in to the
+build nodes and Server2 (which replace kenobi). Except minimal access
+with restricted commands to allow "mdvsys submit" to work.
+
+About servers for packagers to test package builds, I think we should
+have separate servers.
+
+With current Mandriva build system, any contributor (even apprentice
+without submit rights) can easily become root with iurt (or using a
+security issue in any package, because any package from the repository
+can be installed), access the mandrake account and then login to almost
+any server in the BS using mandrake ssh key, and then silently replace
+packages on the repository. We can probably trust long time
+contributors, but it's difficult to trust people we don't know who asked
+for an apprentice account.
+
+> 
+> > If you have any other ideas, comments or questions, don't hesitate to
+> > reply.
+> 
+> No backup server ? No postfix ( primary and secondary ) ? No wiki ?
+> Would all web applications be hosted on the same server ( ie epoll,
+> transifex and other applications ? )
+
+Yes, backup server is still missing. We will maybe need to buy one, or
+find an other server to do it. For now, maybe the servers can backup
+each others.
+
+For the wiki and all web apps, yes they will be on the same server. I
+think the server is quite fast.
+
+> We should have a secondary ldap. I would also add a ticket system which
+> is not bugzilla ( as infrastructure as a product would be weird ).
+
+Do you have some suggestions for the ticket system ?
+
+> 
+> And we may need somewhere to write the doc, if possible something that
+> can be used offline.
+
+So something other than the wiki ?
+
+> 
+> We also need to discuss what is our responsibility and what is not ( ie,
+> who is root on what server, mainly the website one, and who decide of
+> the various setting, mainly php/apache ). I would propose that we
+> leverage a VCS + some soft like cfengine/puppet to delegate some part
+> ( like some vhosts settings on some server ) to some others groups ( and
+> this would also provides tracability, ie, no direct root access ).  
+
+Yes, good idea. We should also send commit logs to this mailing so we
+know when something is changed.
+
+Nicolas
+
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000020.html b/zarb-ml/mageia-sysadm/2010-October/000020.html new file mode 100644 index 000000000..424f4a744 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000020.html @@ -0,0 +1,66 @@ + + + + [Mageia-sysadm] presentations + + + + + + + + + +

[Mageia-sysadm] presentations

+ nicolas vigier + boklm at mars-attacks.org +
+ Fri Oct 8 23:27:13 CEST 2010 +

+
+ +
On Wed, 06 Oct 2010, nicolas vigier wrote:
+
+> 
+> As misc suggested, we can present ourself on this mailing list. So you
+> can answer to this thread to present you.
+
+We now have two new members in the sysadmin team, Nanar and blino.
+Nanar will be working mainly on the mirrors part.
+
+Nicolas
+
+
+ + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000021.html b/zarb-ml/mageia-sysadm/2010-October/000021.html new file mode 100644 index 000000000..b4482b7e3 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000021.html @@ -0,0 +1,74 @@ + + + + [Mageia-sysadm] some news about the servers + + + + + + + + + +

[Mageia-sysadm] some news about the servers

+ nicolas vigier + boklm at mars-attacks.org +
+ Mon Oct 18 16:51:27 CEST 2010 +

+
+ +
Hello,
+
+We plan to install the servers in the datacenter this week. Damien will
+buy the hard disks we need tomorrow (tuesday). On Wednesday afternoon
+we will install the servers. I think we should install Mandriva 2010.1
+on the servers. On thursday we will drive to Marseille (Damien, Misc and
+me) and bring the servers to Ielo datacenter. On friday morning we will
+rack the machines and setup the network. On friday night all machines
+should be accessible by ssh, and we come back to Paris.
+
+Now we need to find names for the servers. Or a naming scheme.
+
+Any ideas ?
+
+Maybe one can be called Valstar.
+
+Nicolas
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000022.html b/zarb-ml/mageia-sysadm/2010-October/000022.html new file mode 100644 index 000000000..b2082ef1a --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000022.html @@ -0,0 +1,87 @@ + + + + [Mageia-sysadm] some news about the servers + + + + + + + + + +

[Mageia-sysadm] some news about the servers

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Mon Oct 18 16:54:36 CEST 2010 +

+
+ +
'Twas brillig, and nicolas vigier at 18/10/10 15:51 did gyre and gimble:
+> Now we need to find names for the servers. Or a naming scheme.
+> 
+> Any ideas ?
+> 
+> Maybe one can be called Valstar.
+
+Usual suspects:
+ * Simpsons Characters
+ * Star Wars Characters
+ * Place names.
+
+I've a bit bored of the first two, so how about naming the servers after
+the places where the founding members were born (or their favourite place).
+
+Col
+
+
+
+-- 
+
+Colin Guthrie
+mageia(at)colin.guthr.ie
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited [http://www.tribalogic.net/]
+Open Source:
+  Mageia Contributor [http://www.mageia.org/]
+  PulseAudio Hacker [http://www.pulseaudio.org/]
+  Trac Hacker [http://trac.edgewall.org/]
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000023.html b/zarb-ml/mageia-sysadm/2010-October/000023.html new file mode 100644 index 000000000..cfe2dd86b --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000023.html @@ -0,0 +1,83 @@ + + + + [Mageia-sysadm] some news about the servers + + + + + + + + + +

[Mageia-sysadm] some news about the servers

+ Michael Scherer + misc at zarb.org +
+ Mon Oct 18 17:03:47 CEST 2010 +

+
+ +
Le lundi 18 octobre 2010 à 15:54 +0100, Colin Guthrie a écrit :
+> 'Twas brillig, and nicolas vigier at 18/10/10 15:51 did gyre and gimble:
+> > Now we need to find names for the servers. Or a naming scheme.
+> > 
+> > Any ideas ?
+> > 
+> > Maybe one can be called Valstar.
+> 
+> Usual suspects:
+>  * Simpsons Characters
+>  * Star Wars Characters
+>  * Place names.
+> 
+> I've a bit bored of the first two, so how about naming the servers after
+> the places where the founding members were born (or their favourite place).
+
+I think we could indeed find a rotating naming scheme, ie we let 1
+person decide the name, and decide who will be the next to choose among
+the group who can decide ( and people cannot decide twice ).
+
+This way, we maximise the happiness of people :p
+
+And we can start by boklm, and use the current sysadmin group as the
+group who choose. 
+-- 
+Michael Scherer
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000024.html b/zarb-ml/mageia-sysadm/2010-October/000024.html new file mode 100644 index 000000000..7e3829412 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000024.html @@ -0,0 +1,84 @@ + + + + [Mageia-sysadm] some news about the servers + + + + + + + + + +

[Mageia-sysadm] some news about the servers

+ nicolas vigier + boklm at mars-attacks.org +
+ Mon Oct 18 17:38:05 CEST 2010 +

+
+ +
On Mon, 18 Oct 2010, Michael Scherer wrote:
+
+> 
+> I think we could indeed find a rotating naming scheme, ie we let 1
+> person decide the name, and decide who will be the next to choose among
+> the group who can decide ( and people cannot decide twice ).
+> 
+> This way, we maximise the happiness of people :p
+> 
+> And we can start by boklm, and use the current sysadmin group as the
+> group who choose. 
+
+Good idea.
+
+We will have the following servers (maybe others later) :
+ - Server1: bugzilla/nagios/dns1/sql/ldap/api/mail/mailling/pastebin/wiki/planet
+ - Server2(valstar): svn/git/BS scheduler/hdlists/primary mirror
+ - Server3: BS node
+ - Server4: BS node
+ - Server5: backup server
+ - gandi VM1: used for dns, secondary mx, meetbot, temporary svn
+ - gandi VM2: website
+
+I select "valstar" for Server2 name. Misc you can select the name for an
+other server in the list (and select someone else to choose a name).
+
+Nicolas
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000025.html b/zarb-ml/mageia-sysadm/2010-October/000025.html new file mode 100644 index 000000000..bec9cb66a --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000025.html @@ -0,0 +1,92 @@ + + + + [Mageia-sysadm] some news about the servers + + + + + + + + + +

[Mageia-sysadm] some news about the servers

+ Michael Scherer + misc at zarb.org +
+ Mon Oct 18 18:23:10 CEST 2010 +

+
+ +
Le lundi 18 octobre 2010 à 17:38 +0200, nicolas vigier a écrit :
+> On Mon, 18 Oct 2010, Michael Scherer wrote:
+> 
+> > 
+> > I think we could indeed find a rotating naming scheme, ie we let 1
+> > person decide the name, and decide who will be the next to choose among
+> > the group who can decide ( and people cannot decide twice ).
+> > 
+> > This way, we maximise the happiness of people :p
+> > 
+> > And we can start by boklm, and use the current sysadmin group as the
+> > group who choose. 
+> 
+> Good idea.
+> 
+> We will have the following servers (maybe others later) :
+>  - Server1(alamut): bugzilla/nagios/dns1/sql/ldap/api/mail/mailling/pastebin/wiki/planet
+>  - Server2(valstar): svn/git/BS scheduler/hdlists/primary mirror
+>  - Server3: BS node
+>  - Server4: BS node
+>  - Server5: backup server
+>  - gandi VM1: used for dns, secondary mx, meetbot, temporary svn
+>  - gandi VM2: website
+
+
+> I select "valstar" for Server2 name. Misc you can select the name for an
+> other server in the list (and select someone else to choose a name).
+
+Ok, I take the server1, and I propose to name it Alamut.
+
+And I nominate Coling for the next server. 
+
+
+-- 
+Michael Scherer
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000026.html b/zarb-ml/mageia-sysadm/2010-October/000026.html new file mode 100644 index 000000000..144d02fa2 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000026.html @@ -0,0 +1,95 @@ + + + + [Mageia-sysadm] some news about the servers + + + + + + + + + +

[Mageia-sysadm] some news about the servers

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Mon Oct 18 18:34:20 CEST 2010 +

+
+ +
'Twas brillig, and Michael Scherer at 18/10/10 17:23 did gyre and gimble:
+>>> And we can start by boklm, and use the current sysadmin group as the
+>>> group who choose. 
+>>
+> Good idea.
+>
+> We will have the following servers (maybe others later) :
+>  - Server1(alamut): bugzilla/nagios/dns1/sql/ldap/api/mail/mailling/pastebin/wiki/planet
+>  - Server2(valstar): svn/git/BS scheduler/hdlists/primary mirror
+>  - Server3(ecosse): BS node
+>  - Server4: BS node
+>  - Server5: backup server
+>  - gandi VM1: used for dns, secondary mx, meetbot, temporary svn
+>  - gandi VM2: website
+
+> Ok, I take the server1, and I propose to name it Alamut.
+> 
+> And I nominate Coling for the next server. 
+
+OK, I'll take a build node and call it Écosse. If possible please paint
+it blue with a couple white stripes crossing it :p
+
+And I nominate Thomas for the next server.
+
+Col
+
+
+-- 
+
+Colin Guthrie
+mageia(at)colin.guthr.ie
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited [http://www.tribalogic.net/]
+Open Source:
+  Mageia Contributor [http://www.mageia.org/]
+  PulseAudio Hacker [http://www.pulseaudio.org/]
+  Trac Hacker [http://trac.edgewall.org/]
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000027.html b/zarb-ml/mageia-sysadm/2010-October/000027.html new file mode 100644 index 000000000..a3d7e87fe --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000027.html @@ -0,0 +1,88 @@ + + + + [Mageia-sysadm] some news about the servers + + + + + + + + + +

[Mageia-sysadm] some news about the servers

+ Thomas Backlund + tmb at iki.fi +
+ Mon Oct 18 19:34:47 CEST 2010 +

+
+ +
Colin Guthrie skrev 18.10.2010 19:34:
+> 'Twas brillig, and Michael Scherer at 18/10/10 17:23 did gyre and gimble:
+>>>> And we can start by boklm, and use the current sysadmin group as the
+>>>> group who choose.
+>>>
+>> Good idea.
+>>
+>> We will have the following servers (maybe others later) :
+>>   - Server1(alamut): bugzilla/nagios/dns1/sql/ldap/api/mail/mailling/pastebin/wiki/planet
+>>   - Server2(valstar): svn/git/BS scheduler/hdlists/primary mirror
+>>   - Server3(ecosse): BS node
+>>   - Server4(jonund): BS node
+>>   - Server5: backup server
+>>   - gandi VM1: used for dns, secondary mx, meetbot, temporary svn
+>>   - gandi VM2: website
+>
+>> Ok, I take the server1, and I propose to name it Alamut.
+>>
+>> And I nominate Coling for the next server.
+>
+> OK, I'll take a build node and call it Écosse. If possible please paint
+> it blue with a couple white stripes crossing it :p
+>
+> And I nominate Thomas for the next server.
+>
+
+So I'll take the other build node and call it Jonund.
+
+And I nominate damsweb for the next server.
+
+--
+Thomas
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000028.html b/zarb-ml/mageia-sysadm/2010-October/000028.html new file mode 100644 index 000000000..5396f62ef --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000028.html @@ -0,0 +1,94 @@ + + + + [Mageia-sysadm] some news about the servers + + + + + + + + + +

[Mageia-sysadm] some news about the servers

+ Damien Lallement + mageia at damsweb.net +
+ Tue Oct 19 12:02:49 CEST 2010 +

+
+ +
On Mon, 18 Oct 2010 20:34:47 +0300, Thomas Backlund <tmb at iki.fi> wrote:
+> Colin Guthrie skrev 18.10.2010 19:34:
+>> 'Twas brillig, and Michael Scherer at 18/10/10 17:23 did gyre and gimble:
+>>>>> And we can start by boklm, and use the current sysadmin group as the
+>>>>> group who choose.
+>>>>
+>>> Good idea.
+>>>
+>>> We will have the following servers (maybe others later) :
+>>>   - Server1(alamut): bugzilla/nagios/dns1/sql/ldap/api/mail/mailling/pastebin/wiki/planet
+>>>   - Server2(valstar): svn/git/BS scheduler/hdlists/primary mirror
+>>>   - Server3(ecosse): BS node
+>>>   - Server4(jonund): BS node
+>>>   - Server5(fiona): backup server
+>>>   - gandi VM1: used for dns, secondary mx, meetbot, temporary svn
+>>>   - gandi VM2: website
+>>
+>>> Ok, I take the server1, and I propose to name it Alamut.
+>>>
+>>> And I nominate Coling for the next server.
+>>
+>> OK, I'll take a build node and call it Écosse. If possible please paint
+>> it blue with a couple white stripes crossing it :p
+>>
+>> And I nominate Thomas for the next server.
+>>
+> 
+> So I'll take the other build node and call it Jonund.
+> 
+> And I nominate damsweb for the next server.
+
+Hello I choose server 5 and call it "fiona" (like in Shrek :p).
+And I nominate dmorgan for the next server.
+-- 
+Damien Lallement
+aka "damsweb" or "coincoin" on IRC and twitter
+
+http://www.mageia.org
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000029.html b/zarb-ml/mageia-sysadm/2010-October/000029.html new file mode 100644 index 000000000..f5aacc921 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000029.html @@ -0,0 +1,101 @@ + + + + [Mageia-sysadm] some news about the servers + + + + + + + + + +

[Mageia-sysadm] some news about the servers

+ Derek Morgan + dmorganec at gmail.com +
+ Tue Oct 19 22:21:25 CEST 2010 +

+
+ +
On Tue, Oct 19, 2010 at 12:02 PM, Damien Lallement <mageia at damsweb.net>wrote:
+
+> On Mon, 18 Oct 2010 20:34:47 +0300, Thomas Backlund <tmb at iki.fi> wrote:
+> > Colin Guthrie skrev 18.10.2010 19:34:
+> >> 'Twas brillig, and Michael Scherer at 18/10/10 17:23 did gyre and
+> gimble:
+> >>>>> And we can start by boklm, and use the current sysadmin group as the
+> >>>>> group who choose.
+> >>>>
+> >>> Good idea.
+> >>>
+> >>> We will have the following servers (maybe others later) :
+> >>>   - Server1(alamut):
+> bugzilla/nagios/dns1/sql/ldap/api/mail/mailling/pastebin/wiki/planet
+> >>>   - Server2(valstar): svn/git/BS scheduler/hdlists/primary mirror
+> >>>   - Server3(ecosse): BS node
+> >>>   - Server4(jonund): BS node
+> >>>   - Server5(fiona): backup server
+> >>>   - gandi VM1: used for dns, secondary mx, meetbot, temporary svn
+> >>>   - gandi VM2: website
+> >>
+> >>> Ok, I take the server1, and I propose to name it Alamut.
+> >>>
+> >>> And I nominate Coling for the next server.
+> >>
+> >> OK, I'll take a build node and call it Écosse. If possible please paint
+> >> it blue with a couple white stripes crossing it :p
+> >>
+> >> And I nominate Thomas for the next server.
+> >>
+> >
+> > So I'll take the other build node and call it Jonund.
+> >
+> > And I nominate damsweb for the next server.
+>
+> Hello I choose server 5 and call it "fiona" (like in Shrek :p).
+> And I nominate dmorgan for the next server.
+>
+
+Hi all,
+
+i propose kouign-amann for the gandi VM1
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101019/6f06b467/attachment.html>
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000030.html b/zarb-ml/mageia-sysadm/2010-October/000030.html new file mode 100644 index 000000000..e04692741 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000030.html @@ -0,0 +1,107 @@ + + + + [Mageia-sysadm] some news about the servers + + + + + + + + + +

[Mageia-sysadm] some news about the servers

+ Michael Scherer + misc at zarb.org +
+ Tue Oct 19 23:19:03 CEST 2010 +

+
+ +
Le mardi 19 octobre 2010 à 22:21 +0200, Derek Morgan a écrit :
+> On Tue, Oct 19, 2010 at 12:02 PM, Damien Lallement <mageia at damsweb.net>wrote:
+> 
+> > On Mon, 18 Oct 2010 20:34:47 +0300, Thomas Backlund <tmb at iki.fi> wrote:
+> > > Colin Guthrie skrev 18.10.2010 19:34:
+> > >> 'Twas brillig, and Michael Scherer at 18/10/10 17:23 did gyre and
+> > gimble:
+> > >>>>> And we can start by boklm, and use the current sysadmin group as the
+> > >>>>> group who choose.
+> > >>>>
+> > >>> Good idea.
+> > >>>
+> > >>> We will have the following servers (maybe others later) :
+> > >>>   - Server1(alamut):
+> > bugzilla/nagios/dns1/sql/ldap/api/mail/mailling/pastebin/wiki/planet
+> > >>>   - Server2(valstar): svn/git/BS scheduler/hdlists/primary mirror
+> > >>>   - Server3(ecosse): BS node
+> > >>>   - Server4(jonund): BS node
+> > >>>   - Server5(fiona): backup server
+> > >>>   - gandi VM1: used for dns, secondary mx, meetbot, temporary svn
+> > >>>   - gandi VM2: website
+> > >>
+> > >>> Ok, I take the server1, and I propose to name it Alamut.
+> > >>>
+> > >>> And I nominate Coling for the next server.
+> > >>
+> > >> OK, I'll take a build node and call it Écosse. If possible please paint
+> > >> it blue with a couple white stripes crossing it :p
+> > >>
+> > >> And I nominate Thomas for the next server.
+> > >>
+> > >
+> > > So I'll take the other build node and call it Jonund.
+> > >
+> > > And I nominate damsweb for the next server.
+> >
+> > Hello I choose server 5 and call it "fiona" (like in Shrek :p).
+> > And I nominate dmorgan for the next server.
+> >
+> 
+> Hi all,
+> 
+> i propose kouign-amann for the gandi VM1
+
+and you need to give the name of the next person to choose, who will
+also be the last one for the moment.
+
+-- 
+Michael Scherer
+
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000031.html b/zarb-ml/mageia-sysadm/2010-October/000031.html new file mode 100644 index 000000000..4e506ca9f --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000031.html @@ -0,0 +1,89 @@ + + + + [Mageia-sysadm] some news about the servers + + + + + + + + + +

[Mageia-sysadm] some news about the servers

+ Michael Scherer + misc at zarb.org +
+ Wed Oct 20 14:23:56 CEST 2010 +

+
+ +
Le lundi 18 octobre 2010 à 17:34 +0100, Colin Guthrie a écrit :
+> 'Twas brillig, and Michael Scherer at 18/10/10 17:23 did gyre and gimble:
+> >>> And we can start by boklm, and use the current sysadmin group as the
+> >>> group who choose. 
+> >>
+> > Good idea.
+> >
+> > We will have the following servers (maybe others later) :
+> >  - Server1(alamut): bugzilla/nagios/dns1/sql/ldap/api/mail/mailling/pastebin/wiki/planet
+> >  - Server2(valstar): svn/git/BS scheduler/hdlists/primary mirror
+> >  - Server3(ecosse): BS node
+> >  - Server4: BS node
+> >  - Server5: backup server
+> >  - gandi VM1: used for dns, secondary mx, meetbot, temporary svn
+> >  - gandi VM2: website
+> 
+> > Ok, I take the server1, and I propose to name it Alamut.
+> > 
+> > And I nominate Coling for the next server. 
+> 
+> OK, I'll take a build node and call it Écosse. If possible please paint
+> it blue with a couple white stripes crossing it :p
+
+I am not sure that é is valid for the hostname, so it will be ecosse,
+no ?
+
+
+-- 
+Michael Scherer
+
+
+ + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000032.html b/zarb-ml/mageia-sysadm/2010-October/000032.html new file mode 100644 index 000000000..5a2737f6c --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000032.html @@ -0,0 +1,102 @@ + + + + [Mageia-sysadm] some news about the servers + + + + + + + + + +

[Mageia-sysadm] some news about the servers

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Wed Oct 20 22:43:40 CEST 2010 +

+
+ +
'Twas brillig, and Michael Scherer at 20/10/10 13:23 did gyre and gimble:
+> Le lundi 18 octobre 2010 à 17:34 +0100, Colin Guthrie a écrit :
+>> 'Twas brillig, and Michael Scherer at 18/10/10 17:23 did gyre and gimble:
+>>>>> And we can start by boklm, and use the current sysadmin group as the
+>>>>> group who choose. 
+>>>>
+>>> Good idea.
+>>>
+>>> We will have the following servers (maybe others later) :
+>>>  - Server1(alamut): bugzilla/nagios/dns1/sql/ldap/api/mail/mailling/pastebin/wiki/planet
+>>>  - Server2(valstar): svn/git/BS scheduler/hdlists/primary mirror
+>>>  - Server3(ecosse): BS node
+>>>  - Server4: BS node
+>>>  - Server5: backup server
+>>>  - gandi VM1: used for dns, secondary mx, meetbot, temporary svn
+>>>  - gandi VM2: website
+>>
+>>> Ok, I take the server1, and I propose to name it Alamut.
+>>>
+>>> And I nominate Coling for the next server. 
+>>
+>> OK, I'll take a build node and call it Écosse. If possible please paint
+>> it blue with a couple white stripes crossing it :p
+> 
+> I am not sure that é is valid for the hostname, so it will be ecosse,
+> no ?
+
+Yeah, that's why I wrote it without the acute in the server list above :p
+
+Col
+
+-- 
+
+Colin Guthrie
+mageia(at)colin.guthr.ie
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited [http://www.tribalogic.net/]
+Open Source:
+  Mageia Contributor [http://www.mageia.org/]
+  PulseAudio Hacker [http://www.pulseaudio.org/]
+  Trac Hacker [http://trac.edgewall.org/]
+
+ + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000033.html b/zarb-ml/mageia-sysadm/2010-October/000033.html new file mode 100644 index 000000000..9c28b6a92 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000033.html @@ -0,0 +1,109 @@ + + + + [Mageia-sysadm] some news about the servers + + + + + + + + + +

[Mageia-sysadm] some news about the servers

+ Derek Morgan + dmorganec at gmail.com +
+ Fri Oct 22 00:13:52 CEST 2010 +

+
+ +
On Tue, Oct 19, 2010 at 10:21 PM, Derek Morgan <dmorganec at gmail.com> wrote:
+
+>
+>
+> On Tue, Oct 19, 2010 at 12:02 PM, Damien Lallement <mageia at damsweb.net>wrote:
+>
+>> On Mon, 18 Oct 2010 20:34:47 +0300, Thomas Backlund <tmb at iki.fi> wrote:
+>> > Colin Guthrie skrev 18.10.2010 19:34:
+>> >> 'Twas brillig, and Michael Scherer at 18/10/10 17:23 did gyre and
+>> gimble:
+>> >>>>> And we can start by boklm, and use the current sysadmin group as the
+>> >>>>> group who choose.
+>> >>>>
+>> >>> Good idea.
+>> >>>
+>> >>> We will have the following servers (maybe others later) :
+>> >>>   - Server1(alamut):
+>> bugzilla/nagios/dns1/sql/ldap/api/mail/mailling/pastebin/wiki/planet
+>> >>>   - Server2(valstar): svn/git/BS scheduler/hdlists/primary mirror
+>> >>>   - Server3(ecosse): BS node
+>> >>>   - Server4(jonund): BS node
+>> >>>   - Server5(fiona): backup server
+>> >>>   - gandi VM1(kouign-amann): used for dns, secondary mx, meetbot,
+>> temporary svn
+>> >>>   - gandi VM2: website
+>> >>
+>> >>> Ok, I take the server1, and I propose to name it Alamut.
+>> >>>
+>> >>> And I nominate Coling for the next server.
+>> >>
+>> >> OK, I'll take a build node and call it Écosse. If possible please paint
+>> >> it blue with a couple white stripes crossing it :p
+>> >>
+>> >> And I nominate Thomas for the next server.
+>> >>
+>> >
+>> > So I'll take the other build node and call it Jonund.
+>> >
+>> > And I nominate damsweb for the next server.
+>>
+>> Hello I choose server 5 and call it "fiona" (like in Shrek :p).
+>> And I nominate dmorgan for the next server.
+>>
+>
+> Hi all,
+>
+> i propose kouign-amann for the gandi VM1
+>
+>
+Now this is up to severine to choose the name of the next machine.
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101022/a6576936/attachment.html>
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000034.html b/zarb-ml/mageia-sysadm/2010-October/000034.html new file mode 100644 index 000000000..752deb6b1 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000034.html @@ -0,0 +1,117 @@ + + + + [Mageia-sysadm] some news about the servers + + + + + + + + + +

[Mageia-sysadm] some news about the servers

+ Séverine Wiltgen + swiltgen at gmail.com +
+ Fri Oct 22 21:17:51 CEST 2010 +

+
+ +
2010/10/22 Derek Morgan <dmorganec at gmail.com>:
+>
+>
+> On Tue, Oct 19, 2010 at 10:21 PM, Derek Morgan <dmorganec at gmail.com> wrote:
+>>
+>>
+>> On Tue, Oct 19, 2010 at 12:02 PM, Damien Lallement <mageia at damsweb.net>
+>> wrote:
+>>>
+>>> On Mon, 18 Oct 2010 20:34:47 +0300, Thomas Backlund <tmb at iki.fi> wrote:
+>>> > Colin Guthrie skrev 18.10.2010 19:34:
+>>> >> 'Twas brillig, and Michael Scherer at 18/10/10 17:23 did gyre and
+>>> >> gimble:
+>>> >>>>> And we can start by boklm, and use the current sysadmin group as
+>>> >>>>> the
+>>> >>>>> group who choose.
+>>> >>>>
+>>> >>> Good idea.
+>>> >>>
+>>> >>> We will have the following servers (maybe others later) :
+>>> >>>   - Server1(alamut):
+>>> >>> bugzilla/nagios/dns1/sql/ldap/api/mail/mailling/pastebin/wiki/planet
+>>> >>>   - Server2(valstar): svn/git/BS scheduler/hdlists/primary mirror
+>>> >>>   - Server3(ecosse): BS node
+>>> >>>   - Server4(jonund): BS node
+>>> >>>   - Server5(fiona): backup server
+>>> >>>   - gandi VM1(kouign-amann): used for dns, secondary mx, meetbot,
+>>> >>> temporary svn
+>>> >>>   - gandi VM2(champagne): website
+>>> >>
+>>> >>> Ok, I take the server1, and I propose to name it Alamut.
+>>> >>>
+>>> >>> And I nominate Coling for the next server.
+>>> >>
+>>> >> OK, I'll take a build node and call it Écosse. If possible please
+>>> >> paint
+>>> >> it blue with a couple white stripes crossing it :p
+>>> >>
+>>> >> And I nominate Thomas for the next server.
+>>> >>
+>>> >
+>>> > So I'll take the other build node and call it Jonund.
+>>> >
+>>> > And I nominate damsweb for the next server.
+>>>
+>>> Hello I choose server 5 and call it "fiona" (like in Shrek :p).
+>>> And I nominate dmorgan for the next server.
+>>
+>> Hi all,
+>>
+>> i propose kouign-amann for the gandi VM1
+>>
+>
+> Now this is up to severine to choose the name of the next machine.
+
+Hello all,
+
+I propose the name "champagne" for gandi VM2.
+
+-- 
+sev
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000035.html b/zarb-ml/mageia-sysadm/2010-October/000035.html new file mode 100644 index 000000000..cd4f0fc2b --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000035.html @@ -0,0 +1,75 @@ + + + + [Mageia-sysadm] some news about the servers + + + + + + + + + +

[Mageia-sysadm] some news about the servers

+ Derek Morgan + dmorganec at gmail.com +
+ Fri Oct 22 22:41:03 CEST 2010 +

+
+ +
On Fri, Oct 22, 2010 at 12:13 AM, Derek Morgan <dmorganec at gmail.com> wrote
+>>
+>> Hi all,
+>>
+>> i propose kouign-amann for the gandi VM1
+>>
+>
+> Now this is up to severine to choose the name of the next machine.
+
+Hi,
+
+there was some issues with for some people ( long + use of - )
+
+so i change the name of the gandi VM1 to :
+
+KRAMPOUEZH
+
+
+regards
+Derek
+
+ + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000036.html b/zarb-ml/mageia-sysadm/2010-October/000036.html new file mode 100644 index 000000000..a399daf1f --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000036.html @@ -0,0 +1,89 @@ + + + + [Mageia-sysadm] good news, bad news + + + + + + + + + +

[Mageia-sysadm] good news, bad news

+ Michael Scherer + misc at zarb.org +
+ Sat Oct 23 21:16:05 CEST 2010 +

+
+ +
Hi
+
+so first the good news. I have done some cleaning ( mainly removal of
+avahi, mandi and other packages that are not relevant on a server ).
+While on it, I have also added the ipv6 that we didn't set up when in
+DC.
+
+So if you have ipv6 connectivity, you can ping ecosse, alamut and
+jonund.
+
+So where is the bad news ? Well, if you have ip v6 connectivity, you
+cannot ping valstar. And if you only have ip v4 connectivity, you cannot
+either.
+
+I connected this afternoon, so it was working one hour ago. I am pretty
+sure that I didn't touched to the network, not to a point that would
+render it unusable. Unfortunately, not only valstar has no admin card,
+but I think it also suffer from a bios bug that sometimes prevent a
+restart after a power shortage. IIRC, the power is doubled so it should
+not happen much.
+
+However, it seems that alamut just got rebooted too :
+
+$ ssh root at alamut.mageia.org uptime
+19:13:38 up  5:21,  0 users,  load average: 0.00, 0.00, 0.00
+
+We ( me and dams ) will investigate and report. 
+
+I will also post a planning later ( about what is needed, what is
+planned, etc, etc ). 
+-- 
+Michael Scherer
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000037.html b/zarb-ml/mageia-sysadm/2010-October/000037.html new file mode 100644 index 000000000..496ecf220 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000037.html @@ -0,0 +1,112 @@ + + + + [Mageia-sysadm] planning for sysadmin task + + + + + + + + + +

[Mageia-sysadm] planning for sysadmin task

+ Michael Scherer + misc at zarb.org +
+ Sat Oct 23 21:42:41 CEST 2010 +

+
+ +
Hi, 
+
+so now the server are in place, we have to install them. Here is a
+proposal of the needed services :
+
+so as said on the blog, one of the first task should be to migrate dns
+from zarb to mageia.org. 
+- primary dns ( on alamut )
+- secondary dns ( at gandi )
+
+Since zarb.org is hosted in the same rack, having the secundary dns
+doesn't seems like a smart idea.
+
+This one requires to collaborate with rda has he take care of the domain
+at gandi. I assume that no one has a objection to use bind for that ?
+
+
+Then we need to deploy the basic infrastructure for us. Again, I assume
+that no one is against apache :
+- ldap ( valstar or alamut ? )
+- apache
+- buchan application 
+- create account for us.
+
+I would also and as I said before, use puppet/svn to manage the servers.
+But this part will require a full mail on his own.
+
+- puppetmaster ( valstar )
+- svn ( requires ldap ), on valstar 
+- manage/migrate config
+
+Then we have to take care of installing the first web applications, and
+that requires a db :
+- postgresql ( alamut )
+- epoll ( alamut )
+
+
+then the rest is less prioritary :
+- postfix ( alamut )
+- migrate to sympa ( alamut )
+- enter everybody in the ldap
+- nagios/munin ( or similar ) ( alamut )
+- migrate blogs 
+- migrate wiki
+- nanar application for mirror
+- etc.
+
+So is there any tasks that you think should be done before this ? ( ie,
+not something that will likely appear in etc ).
+
+"saving valstar" do not count, of course we need to find out what
+happened. 
+-- 
+Michael Scherer
+
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000038.html b/zarb-ml/mageia-sysadm/2010-October/000038.html new file mode 100644 index 000000000..b21bf9b03 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000038.html @@ -0,0 +1,329 @@ + + + + [Mageia-sysadm] [LONG] A not so modest proposal + + + + + + + + + +

[Mageia-sysadm] [LONG] A not so modest proposal

+ Michael Scherer + misc at zarb.org +
+ Sun Oct 24 01:55:18 CEST 2010 +

+
+ +
Hi,
+
+so as I said in the previous mail ( and before ), I propose that we use
+puppet+svn to manage the servers. Since this may not be obvious to
+everybody here is a long mail with a long explanation of each point.
+( spoiler, there is a bold proposal in the middle ).
+
+
+So first, what is puppet ?
+--------------------------
+
+As I didn't found a better explanation than the one of their website,
+let's cut and paste : 
+
+"Puppet is an open source data center automation and configuration
+management framework. Puppet provides system administrators with a
+simplified platform that allows for consistent, transparent, and
+flexible systems management."
+
+If you have heard of cfengine ( used at mdv ), or bcfg2, puppet is
+similar. It allows you to describe your computers in a configuration
+file and take care of installing and setting them according the
+configuration file. For example, you can say 'for server of group web
+server, install apache php, and use this config file, and start this
+process'. Usually, such system are combined with a regular vcs like svn,
+for reason that I will outline later.
+
+To quickly explain how it work, there is a central server ( called
+"puppetmaster" for puppet ) and a agent on each computer. Agents fetch
+the config from puppetmaster after a configurable interval of time and
+apply it ( ie, install rpm, change configfile, reload software, run
+tasks, etc ).
+
+
+So why use a configuration management system and a vcs ?
+--------------------------------------------------------
+
+First, it provides use with a audit trail. Like for code, we know who
+changed what and why. The goal is not to distribute blame, but to be
+able to have more information about a change ( ie, if 2 years ago, I
+changed some php variable that later found out to break some web
+software, the changelog will tell us why it was changed in the first
+place, maybe to fix another important software ). It allows us to repeat
+a configuration ( useful to migrate a service or to reinstall a
+server ), to rollback to previous versions of the configuration, and to
+work concurrently. 
+
+It also ensure that process are running which add a extra safety layer
+in case of problem. And we can use hooks to check file before applying
+them automatically, or send mail to the admin when there is a change.
+For example, you can no longer commit broken dns zone since they are
+checked them before applying automatically ( provided you write the
+proper script, of course ).
+
+
+Why use puppet and not $FOO ?
+-----------------------------
+
+That's a good question. First, let's be honest, I take care of puppet in
+mdv, so of course, I am biased. In term of softwares, there is lots of
+choice
+( http://en.wikipedia.org/wiki/Comparison_of_open_source_configuration_management_software ), but reading on the topic on the web, we can safely restrict our discussion to cfengine 2, cfengine 3, puppet, bcfg2, chef.
+
+Chef is not packaged, nor easy to setup ( imho ) unless you use gems
+( which is a bad idea ). The configuration is basically written ruby. It
+seems nice, but no one played with it around me ( except people at
+CERN ).
+
+Cfengine 2 is what is used at zarb, and also lightly used at mandriva. I
+took a look at mandriva configuration, it is mainly used to prevent
+service from starting and to manage fstab. So nothing that could prevent
+a migration and in fact, almost nothing to reuse. The version 2 is also
+the legacy branch, and I am not sure it is maintained ( guillomovitch
+may know better than me ).
+So far, I think boklm, blino, me and maybe nanar know it.
+
+Bcfg2 is not packaged, and use xml for config file, which is imho a bad
+point for it. I have some friends that use it, they do not seems unhappy
+with it. yet, I found few information about it besides the web site.
+
+Cfengine3 is not packaged either. And the configuration language is
+different from cfengine 2, which would mean that we will likely have to
+re-learn it, for those that know the older version. 
+
+Puppet is packaged ( by me ). It is used by several free software group
+( afaik, redhat and mozilla among others ), maintained by a enterprise
+and there is a healthy community providing modules and software around
+it. From what I know, Nanar and I know how to use it. Boklm also started
+to look at it. 
+
+So I think we should first use a packaged software, for various obvious
+reasons. So the choice is basically between puppet and cfengine2. I
+asked to guillomovitch, our zarb.org cfengine expert about the migration
+to cfengine3, and he told me he was planning to use puppet instead. And
+having used both in production ( either zarb.org or my own server ), I
+think puppet is nicer and provides more high level component than
+cfengine 2, and is maintained. And since there will be almost no
+configuration reuse from Mandriva, I do not think it will be worth to
+keep it.
+
+
+Why use svn and not $FOO ?
+---------------------------
+
+Again a good question. At zarb, we use svn. At mdv, afaik, we used
+nothing, cfengine was just here to automate the cluster setup, which is
+a similar yet different task than the one we are discussing now. So, as
+I prefer DVCS, I tested git + puppet for you, 6 months ago. And after 3
+weeks, I have migrated to svn the whole system. The git hooks are just
+too complex for my poor mind ( ie, checking the syntax of puppet, bind,
+etc before applying was not easy ). So since svn is quite straight
+forward with that, and since we can always use git-svn to have the best
+of both world, I suggest to use svn.
+
+( yes, hg, bzr, cvs and the gazillion others were not suggested ).
+
+Now, if someone is a git-hooks master, I have no problem with git.
+
+What would be the work flow ?
+-----------------------------
+
+So the idea is :
+- a admin commit some config change in svn repository, 
+- svn check the syntax if needed ( pre-commit hook )
+- svn extract the configuration with a post-commit hook ( and send a
+email ),
+- puppetmaster notice the change, 
+- puppetmaster reload the configuration
+- each server get the configuration after some time
+- each server apply the configuration, and send mail in case of problem
+
+We can also add ACLs if needed.
+
+Could we also use svn to manage the documentation ?
+---------------------------------------------------
+
+Indeed, that's a good suggestion. I have learned that the documentation
+is indeed something that I never find when I need, and I have been often
+frustrated by the lack of useful tools to exploit it ( lik grep ). So,
+to me, it make sense to have the documentation along the configuration
+since I always have a checkout of the configuration on my home, and
+since I often update it. ( which is usually not the case with most
+wikis, as this requires extranous step ).
+
+
+Where is the bold proposal ?
+-----------------------------
+
+And now, for the very very bold part of the proposal :
+
+this svn should be public. Ie, people could browse it, changelog should
+be sent on this ml ( which is public ), and people could even do
+anonymous checkout. 
+
+So I expect three type of reactions at this part of the mail :
+
+People who say "mhh, I do not understand what he speak about".
+
+People who say "this make sense, we are doing free software".
+
+And admins who are screaming "argh, what about the passwords and
+security !"  
+
+
+So for people who do not understand, well, either reread or ask me on
+irc, or by mail. There is no shame into asking questions.
+
+For people who are screaming, first, no need to scream, I cannot hear
+you. And I have of course thought of that, and we can either :
+
+1) do a search and replace in puppet config for password stored in a
+secure location in the svn hooks that do the checkout
+
+2) use extlookup, a puppet feature that do this, provides we use it
+properly
+( http://www.devco.net/archives/2009/08/31/complex_data_and_puppet.php ).
+
+Ie, we can store the passwords in a private CSV file somewhere, while
+publishing everything else. Obviously, stuff that count as data ( such
+as private certificates, gpg keys, etc ) should not be stored in svn, or
+not in the public one. And everything that would be considered as
+personal information should not be stored in the public svn either. 
+
+And so for those that think, "this make sense", yes, it make sense, but
+more than simple making sense, it bring some advantages :
+
+Sharing is the basis of the free software ethics. And so that show our
+commitment to free software.
+
+Publishing our configuration is also perfectly in line with the values
+of the project : 
+
+"We will empower our user base by demystifying advanced technologies"
+-> publishing our work as sysadmin is a step toward demystifying
+
+"Mageia will always adhere to high security and privacy
+standards/technologies to protect our users' data." 
+
+-> letting everybody audit is IMHO a high security standard, while
+security by obscurity is not. We always say that free software is better
+for security for this reason, so we are consistent with this idea.
+
+"We will cooperate with other OSS distributions and core and kernel
+developers with code contribution."
+
+-> if the configuration is treated like code, so we are cooperating by
+giving it. For other distribution that may want to know how we do, be it
+big distros or smaller ones. For various project that want to know how
+we handle specific part of the infrastructure.
+
+"We will maintain the vibrancy within our Community, always aiming to
+lead the way in collaborative development."
+
+-> people are eager to help us as sysadmin. I received lots of help
+propositions. However for security reasons, I do not think we should
+have a group of 20 persons, neither we should have a too complex
+organisation for admins. Publishing the config allows us to collaborate
+with others by letting them :
+  - review our changes, as the svn changelog on cooker
+  - directly send patches, which can be much clearer to us
+  - directly search when they see a problem ( for very simple problem of
+course )
+  - help us to communicate with everybody when we fix problem or do some
+changes.
+ 
+More ever, this allow us to see who is motivated to help us, who is able
+to understand our infrastructure, and therefor, this can help us to
+recruit new admins in case of need, and allows us to manage the erosion
+of our group. This also bring a gentle introduction to new comers, who
+can see what happen.
+
+Finally, using this will allow us to have a forkable infrastructure. And
+this would a real innovation I think ( at least, a innovation good
+enough to be communicated ).
+
+I do not plan to let the project go bad, of course, but I also didn't
+intend Mandriva to disappear either. 
+
+So in the future, if something goes wrong for any kind of reason, or if
+some peoples prefer to work without us, we are offering them what
+Mandriva didn't offered, a easy way to fork. And while I do hope it will
+not matter much in practice, I think that's a strong statement to
+demonstrate that we learned from our errors and that we have evolved.
+
+
+So, WDYT ?
+( please do not let me be warnocked
+http://en.wikipedia.org/wiki/Warnocked )
+
+PS : baud, as I know you will ask me later and read this mail, yes, you
+can use use under CC-BY-SA or what you want.
+
+-- 
+Michael Scherer
+
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000039.html b/zarb-ml/mageia-sysadm/2010-October/000039.html new file mode 100644 index 000000000..aed2e4755 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000039.html @@ -0,0 +1,91 @@ + + + + [Mageia-sysadm] Fwd: 2010.1 kernel with the vmscan fix + + + + + + + + + +

[Mageia-sysadm] Fwd: 2010.1 kernel with the vmscan fix

+ Thomas Backlund + tmb at iki.fi +
+ Sun Oct 24 08:33:57 CEST 2010 +

+
+ +
Hi,
+there is now a kernel-2.6.33.7-2.1mnb for 2010.1 at:
+
+http://tmb.mine.nu/Mandriva/2010.1/
+http://tmb2.mine.nu/Mandriva/2010.1/
+
+With the fix:
+- vmscan: raise the bar to PAGEOUT_IO_SYNC stalls
+   (Fixes "system goes unresponsive under memory pressure and lots of
+    dirty/writeback pages" bug. (http://lkml.org/lkml/2010/4/4/86))
+
+
+This was also suggested by blino to help the BS
+
+--
+Thomas
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000040.html b/zarb-ml/mageia-sysadm/2010-October/000040.html new file mode 100644 index 000000000..7893b1841 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000040.html @@ -0,0 +1,89 @@ + + + + [Mageia-sysadm] 2010.1 kernel with the vmscan fix + + + + + + + + + +

[Mageia-sysadm] 2010.1 kernel with the vmscan fix

+ Thomas Backlund + tmb at mandriva.org +
+ Sun Oct 24 08:28:55 CEST 2010 +

+
+ +
Hi,
+there is now a kernel-2.6.33.7-2.1mnb for 2010.1 at:
+
+http://tmb.mine.nu/Mandriva/2010.1/
+http://tmb2.mine.nu/Mandriva/2010.1/
+
+With the fix:
+- vmscan: raise the bar to PAGEOUT_IO_SYNC stalls
+   (Fixes "system goes unresponsive under memory pressure and lots of
+    dirty/writeback pages" bug. (http://lkml.org/lkml/2010/4/4/86))
+
+
+This was also suggested by blino to help the BS
+
+--
+Thomas
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000041.html b/zarb-ml/mageia-sysadm/2010-October/000041.html new file mode 100644 index 000000000..c4278241a --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000041.html @@ -0,0 +1,136 @@ + + + + [Mageia-sysadm] planning for sysadmin task + + + + + + + + + +

[Mageia-sysadm] planning for sysadmin task

+ Olivier Thauvin + nanardon at nanardon.zarb.org +
+ Sun Oct 24 12:58:26 CEST 2010 +

+
+ +
* Michael Scherer (misc at zarb.org) wrote:
+> Hi, 
+> 
+> so now the server are in place, we have to install them. Here is a
+> proposal of the needed services :
+
+> Then we need to deploy the basic infrastructure for us. Again, I assume
+> that no one is against apache :
+> - ldap ( valstar or alamut ? )
+> - apache
+> - buchan application 
+
+May I suggest to setup all our web on same server, especially since a
+lot use perl-Catalyst (buchan's one, epoll and the one I did to manage
+mirror).
+
+May I also suggest all our web be installed using RPM ?
+Notice I got some issue using catalyst in fcgi mod, but it works fine in
+server mode + apache as proxy.
+
+> - create account for us.
+
+Yup, especially if we have to work on them :)
+
+> Then we have to take care of installing the first web applications, and
+> that requires a db :
+> - postgresql ( alamut )
+> - epoll ( alamut )
++ MGA::Mirror, the tools currently on distrib-coffee to manage mirrors.
+
+I want to migrate it ASAP because http on distrib-coffee is not reliable
+due to load made by some distributions.
+
+Can I take this part since I know pgsql and I'll need them myself.
+
+BTW: I hope pgsql can have a dedicated fs, it can help to avoid out of
+space.
+
+> 
+> 
+> then the rest is less prioritary :
+> - postfix ( alamut )
+> - migrate to sympa ( alamut )
+> - enter everybody in the ldap
+> - nagios/munin ( or similar ) ( alamut )
+> - migrate blogs 
+> - migrate wiki
+> - nanar application for mirror
+
+Once pgsql + catalyst is installed, this part is easy to do. Notice it
+need a MTA to work, only to send mail.
+
+MY 2 cents.
+
+> - etc.
+> 
+> So is there any tasks that you think should be done before this ? ( ie,
+> not something that will likely appear in etc ).
+> 
+> "saving valstar" do not count, of course we need to find out what
+> happened. 
+> -- 
+> Michael Scherer
+> 
+> _______________________________________________
+> Mageia-sysadm mailing list
+> Mageia-sysadm at mageia.org
+> https://www.mageia.org/mailman/listinfo/mageia-sysadm
+-- 
+
+Olivier Thauvin
+CNRS  -  LATMOS
+♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 197 bytes
+Desc: not available
+URL: </pipermail/mageia-sysadm/attachments/20101024/25fb270d/attachment.asc>
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000042.html b/zarb-ml/mageia-sysadm/2010-October/000042.html new file mode 100644 index 000000000..735133543 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000042.html @@ -0,0 +1,127 @@ + + + + [Mageia-sysadm] planning for sysadmin task + + + + + + + + + +

[Mageia-sysadm] planning for sysadmin task

+ Michael Scherer + misc at zarb.org +
+ Sun Oct 24 13:24:42 CEST 2010 +

+
+ +
Le dimanche 24 octobre 2010 à 12:58 +0200, Olivier Thauvin a écrit :
+> * Michael Scherer (misc at zarb.org) wrote:
+> > Hi, 
+> > 
+> > so now the server are in place, we have to install them. Here is a
+> > proposal of the needed services :
+> 
+> > Then we need to deploy the basic infrastructure for us. Again, I assume
+> > that no one is against apache :
+> > - ldap ( valstar or alamut ? )
+> > - apache
+> > - buchan application 
+> 
+> May I suggest to setup all our web on same server, especially since a
+> lot use perl-Catalyst (buchan's one, epoll and the one I did to manage
+> mirror).
+
+That's planned, except for specific reasons.
+
+> May I also suggest all our web be installed using RPM ?
+
+That's also what I would love to see. Question is now, should this rpm
+be sent to upstream distro, be made on the server, or offered as a
+separate repository ?
+
+> > Then we have to take care of installing the first web applications, and
+> > that requires a db :
+> > - postgresql ( alamut )
+> > - epoll ( alamut )
+> + MGA::Mirror, the tools currently on distrib-coffee to manage mirrors.
+
+I would have have thought it was less urgent at the moment ( ie, it goes
+to etc ). But if people do the work, that's ok, I cannot force people to
+no do it ( except Olivier as I have his stuffed rabbit in hostage, or
+maybe that's the reverse ).
+
+> I want to migrate it ASAP because http on distrib-coffee is not reliable
+> due to load made by some distributions.
+> 
+> Can I take this part since I know pgsql and I'll need them myself.
+
+Yup.
+
+> BTW: I hope pgsql can have a dedicated fs, it can help to avoid out of
+> space.
+
+We have setup lvm, iirc.
+
+[root at alamut ~]# vgs
+  VG      #PV #LV #SN Attr   VSize   VFree  
+  vg_main   1   0   0 wz--n- 917,45g 917,45g
+
+> > 
+> > 
+> > then the rest is less prioritary :
+> > - postfix ( alamut )
+> > - migrate to sympa ( alamut )
+> > - enter everybody in the ldap
+> > - nagios/munin ( or similar ) ( alamut )
+> > - migrate blogs 
+> > - migrate wiki
+> > - nanar application for mirror
+> 
+> Once pgsql + catalyst is installed, this part is easy to do. Notice it
+> need a MTA to work, only to send mail.
+
+I guess MTA to send mail should be part of the default installation,
+yes. 
+-- 
+Michael Scherer
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000043.html b/zarb-ml/mageia-sysadm/2010-October/000043.html new file mode 100644 index 000000000..5335b2154 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000043.html @@ -0,0 +1,97 @@ + + + + [Mageia-sysadm] mailling list subscription + + + + + + + + + +

[Mageia-sysadm] mailling list subscription

+ Michael Scherer + misc at zarb.org +
+ Mon Oct 25 11:53:25 CEST 2010 +

+
+ +
Hi,
+
+valstar is still down. I will contact LO soon, and see with maat about
+getting in the DC, and post a report. I also discussed with dams, and he
+told me he was the one who rebooted alamut to check something, so the
+hypothesis about a power shortage is likely wrong, and so we think it is
+a kernel panic ( and we didn't have the time to setup the magic sysctl
+setting to reboot after kernel panic ).
+
+But as I know that some people are likely to be interested into getting
+news about that ( like rda, for instance, as he tried to subscribed to
+this list and expressed interest about it ), does people think we should
+let everybody subscribe on this list ?
+
+I would be in favor of this, because it would in the continuity of what
+we did ( ie, open the archives, etc ), but I do not want to do so
+without the input of the others, as people may have a different PoV on
+the subject.
+
+So WDYT ?
+
+-- 
+Michael Scherer
+
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000044.html b/zarb-ml/mageia-sysadm/2010-October/000044.html new file mode 100644 index 000000000..dc44aba04 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000044.html @@ -0,0 +1,157 @@ + + + + [Mageia-sysadm] planning for sysadmin task + + + + + + + + + +

[Mageia-sysadm] planning for sysadmin task

+ Buchan Milne + bgmilne at multilinks.com +
+ Mon Oct 25 11:24:51 CEST 2010 +

+
+ +
On Sunday, 24 October 2010 11:58:26 Olivier Thauvin wrote:
+> * Michael Scherer (misc at zarb.org) wrote:
+> > Hi,
+> > 
+> > so now the server are in place, we have to install them. Here is a
+> > proposal of the needed services :
+> > 
+> > Then we need to deploy the basic infrastructure for us. Again, I assume
+> > that no one is against apache :
+> > - ldap ( valstar or alamut ? )
+
+At this stage, I am thinking that we may want 3 servers running LDAP:
+-Master LDAP server, which is primarily not used by read-only clients. I 
+haven't tested referrals yet in my app, so for now CatDap will probably need 
+to use it. Could possibly be used as fall-back for either of the slaves
+-1 slave used primarily for infrastructure support, but not exposed to much 
+external traffic. Mostly nss_ldap/pam_ldap on build hosts, and any other 
+infrastructure stuff which we decide to put in LDAP. If the total userbase is 
+too large we could consider a partial replica (e.g. only posixAccount 
+entries), though we may need to test this a bit ...
+-1 slave used primarily for external traffic, e.g. forum, wiki etc. This could 
+be the web server running some of these applications.
+
+If this is excessive, we could consider combining master and internal read 
+access on one server (but I would prefer to have at least one fall-back
+
+> > - apache
+> > - buchan application
+
+Interim name for my app is CatDap, but feel free to suggest a better name.
+
+> May I suggest to setup all our web on same server, especially since a
+> lot use perl-Catalyst (buchan's one, epoll and the one I did to manage
+> mirror).
+> 
+> May I also suggest all our web be installed using RPM ?
+> Notice I got some issue using catalyst in fcgi mod, but it works fine in
+> server mode + apache as proxy.
+
+I will try and create a package today. I think all the dependencies should be 
+available for Mdv2010.0 and up. However, if we want to have any contributions 
+(skinning work from web team, localisations) with quick testing, it may be 
+useful to run one instance from an svn checkout.
+
+BTW., do we want to run these apps on separate virtual hosts? Should I ship 
+vhost definition in apache config (e.g. for identity.mageia.org)?
+
+> > - create account for us.
+
+Set up host authentication to LDAP first? We will need SSL certificates for 
+LDAP hosts as well. Self-signed certs or certs from self-signed CA are fine.
+
+> Yup, especially if we have to work on them :)
+
+I have created some accounts in LDAP, and I am happy to create any we need to 
+proceed to the point where the account registration portion of CatDap is 
+running. However, I think we may want to get internal use of it (for 
+registration) before opening the gates ...
+
+Also, I probably need to start work on the admin features, for now I am 
+planning:
+-user modification (e.g. add posixAccount to existing user account, modify any 
+attributes necessary manually, 
+-group management (add groups, modify group membership etc.)
+
+Please let me know what other features are important sooner than later.
+
+> > Then we have to take care of installing the first web applications, and
+> > that requires a db :
+> > - postgresql ( alamut )
+> > - epoll ( alamut )
+> 
+> + MGA::Mirror, the tools currently on distrib-coffee to manage mirrors.
+> 
+> I want to migrate it ASAP because http on distrib-coffee is not reliable
+> due to load made by some distributions.
+> 
+> Can I take this part since I know pgsql and I'll need them myself.
+> 
+> BTW: I hope pgsql can have a dedicated fs, it can help to avoid out of
+> space.
+> 
+> > then the rest is less prioritary :
+> > - postfix ( alamut )
+> > - migrate to sympa ( alamut )
+> > - enter everybody in the ldap
+> > - nagios/munin ( or similar ) ( alamut )
+
+xymon?
+
+> > - migrate blogs
+> > - migrate wiki
+> > - nanar application for mirror
+> 
+> Once pgsql + catalyst is installed, this part is easy to do. Notice it
+> need a MTA to work, only to send mail.
+
+CatDap also requires an MTA for registration (sending only).
+
+Regards,
+Buchan
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000045.html b/zarb-ml/mageia-sysadm/2010-October/000045.html new file mode 100644 index 000000000..691636293 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000045.html @@ -0,0 +1,154 @@ + + + + [Mageia-sysadm] planning for sysadmin task + + + + + + + + + +

[Mageia-sysadm] planning for sysadmin task

+ Michael Scherer + misc at zarb.org +
+ Mon Oct 25 13:05:35 CEST 2010 +

+
+ +
Le lundi 25 octobre 2010 à 10:24 +0100, Buchan Milne a écrit :
+> On Sunday, 24 October 2010 11:58:26 Olivier Thauvin wrote:
+> > * Michael Scherer (misc at zarb.org) wrote:
+> > > Hi,
+> > > 
+> > > so now the server are in place, we have to install them. Here is a
+> > > proposal of the needed services :
+> > > 
+> > > Then we need to deploy the basic infrastructure for us. Again, I assume
+> > > that no one is against apache :
+> > > - ldap ( valstar or alamut ? )
+> 
+> At this stage, I am thinking that we may want 3 servers running LDAP:
+> -Master LDAP server, which is primarily not used by read-only clients. I 
+> haven't tested referrals yet in my app, so for now CatDap will probably need 
+> to use it. Could possibly be used as fall-back for either of the slaves
+> -1 slave used primarily for infrastructure support, but not exposed to much 
+> external traffic. Mostly nss_ldap/pam_ldap on build hosts, and any other 
+> infrastructure stuff which we decide to put in LDAP. If the total userbase is 
+> too large we could consider a partial replica (e.g. only posixAccount 
+> entries), though we may need to test this a bit ...
+> -1 slave used primarily for external traffic, e.g. forum, wiki etc. This could 
+> be the web server running some of these applications.
+> 
+> If this is excessive, we could consider combining master and internal read 
+> access on one server (but I would prefer to have at least one fall-back
+
+For the moment, we have 5 servers, so for the beggining, it may indeed
+be too much. So basically, ldap master on valstar ( ie, svn hdlist,
+etc ) and external on alamut ?
+
+And later, a ldap slave on the server used for forum ?
+
+> > May I suggest to setup all our web on same server, especially since a
+> > lot use perl-Catalyst (buchan's one, epoll and the one I did to manage
+> > mirror).
+> > 
+> > May I also suggest all our web be installed using RPM ?
+> > Notice I got some issue using catalyst in fcgi mod, but it works fine in
+> > server mode + apache as proxy.
+> 
+> I will try and create a package today. I think all the dependencies should be 
+> available for Mdv2010.0 and up. However, if we want to have any contributions 
+> (skinning work from web team, localisations) with quick testing, it may be 
+> useful to run one instance from an svn checkout.
+
+Ie, have a production instance and a devel instance ?
+
+Nothing prevent us from doing rpm from svn snapshot at regular interval
+too.
+
+> BTW., do we want to run these apps on separate virtual hosts? Should I ship 
+> vhost definition in apache config (e.g. for identity.mageia.org)?
+
+I would say "yes"
+
+> > > - create account for us.
+> 
+> Set up host authentication to LDAP first? We will need SSL certificates for 
+> LDAP hosts as well. Self-signed certs or certs from self-signed CA are fine.
+
+Ok.
+
+> > Yup, especially if we have to work on them :)
+> 
+> I have created some accounts in LDAP, and I am happy to create any we need to 
+> proceed to the point where the account registration portion of CatDap is 
+> running. However, I think we may want to get internal use of it (for 
+> registration) before opening the gates ...
+> 
+> Also, I probably need to start work on the admin features, for now I am 
+> planning:
+> -user modification (e.g. add posixAccount to existing user account, modify any 
+> attributes necessary manually, 
+> -group management (add groups, modify group membership etc.)
+> 
+> Please let me know what other features are important sooner than later.
+
+ssh keys support ( as I think we will use it for us ) ? After a second
+tought, we can do it by hand, 
+
+I also think notification of subscription could be interesting, but
+again, we may not need it now.
+
+> > > then the rest is less prioritary :
+> > > - postfix ( alamut )
+> > > - migrate to sympa ( alamut )
+> > > - enter everybody in the ldap
+> > > - nagios/munin ( or similar ) ( alamut )
+> 
+> xymon?
+
+yup, why, as long it is packaged, i am ok.
+
+
+-- 
+Michael Scherer
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000046.html b/zarb-ml/mageia-sysadm/2010-October/000046.html new file mode 100644 index 000000000..f5a8dfba4 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000046.html @@ -0,0 +1,131 @@ + + + + [Mageia-sysadm] valstar is back + + + + + + + + + +

[Mageia-sysadm] valstar is back

+ Michael Scherer + misc at zarb.org +
+ Mon Oct 25 16:33:12 CEST 2010 +

+
+ +
Hi,
+
+so a quick report.
+
+Valstar is back, thanks to Sylvain Rochet ( gradator ). 
+It seems that the firewall was misconfigurated.
+
+So on 23/10/2010, I connected on the server to remove unused services
+( avahi, mandi, dbus, etc ). I have also removed shorewall, as we
+disabled it on all servers at the moment ( I am more familiar with a
+regular iptables initscripts ). 
+
+Except that removing shorewall run service shorewall stop, which in turn
+activate the firewall.
+
+All servers except one ( valstar ) had shorewall correctly turned off by
+Pascal ( maat ). I took care of valstar, but i just disabled the service
+with chkconfig. So once I removed the package, it started to drop
+everything in INPUT.
+According to the logs, this happened around 15h30 CEST 
+
+Oct 23 15:28:59 valstar logger: Shorewall Stopped
+
+Since I was still logged in, I didn't see anything wrong ( as I assume
+that the firewall will not cut working connection )
+
+But after that, trying to connect again showed me a error. 
+
+We ( dams and I ) decided to wait until monday ( as we couldn't do
+anything when the DC was closed, and I was sick, so did maat ), and
+discussed with gradator today, and decided that it was easiest to ask
+for a reboot than to ask to maat to go to marseille this evening.
+
+On 25/10/2010, at 15:30 ( again ), gradator looked at the server, see it
+was a firewall issue, rebooted it without firewall and so the server is
+now ok. 
+
+I inspected it, it work fine, there is no firewall rules loaded upon
+startup so the problem should not repeat itself.
+
+So, while I recognize I am at fault for this, I think that the shorewall
+package have a unexpected side effect, and IMVHO, it should not setup a
+restrictive firewall when we remove it ( and I do not say this only
+because I am ashamed of causing the problem ).
+
+In the future, how could we avoid problem like this ?
+
+Easiest answer is to have servers with RAC, but we don't except on
+alamut. I am not sure we can add one if we manage to get one.
+
+Another solution is a serial cable. But this can be tricky to set up
+( we did for zarb )
+
+WDYT ?
+-- 
+Michael Scherer
+
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000047.html b/zarb-ml/mageia-sysadm/2010-October/000047.html new file mode 100644 index 000000000..f22c4ed85 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000047.html @@ -0,0 +1,93 @@ + + + + [Mageia-sysadm] mailling list subscription + + + + + + + + + +

[Mageia-sysadm] mailling list subscription

+ Damien Lallement + mageia at damsweb.net +
+ Mon Oct 25 16:58:35 CEST 2010 +

+
+ +
On Mon, 25 Oct 2010 11:53:25 +0200, Michael Scherer <misc at zarb.org>
+wrote:
+> Hi,
+> 
+> [...]
+> But as I know that some people are likely to be interested into getting
+> news about that ( like rda, for instance, as he tried to subscribed to
+> this list and expressed interest about it ), does people think we should
+> let everybody subscribe on this list ?
+> 
+> I would be in favor of this, because it would in the continuity of what
+> we did ( ie, open the archives, etc ), but I do not want to do so
+> without the input of the others, as people may have a different PoV on
+> the subject.
+> 
+> So WDYT ?
+
+I agree with your POV.
+-- 
+Damien Lallement
+aka "damsweb" or "coincoin" on IRC and twitter
+
+http://www.mageia.org
+
+ + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000048.html b/zarb-ml/mageia-sysadm/2010-October/000048.html new file mode 100644 index 000000000..ffdd261b8 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000048.html @@ -0,0 +1,85 @@ + + + + [Mageia-sysadm] ssh keys + + + + + + + + + +

[Mageia-sysadm] ssh keys

+ Michael Scherer + misc at zarb.org +
+ Mon Oct 25 22:04:28 CEST 2010 +

+
+ +
Hi fellow admins,
+
+In order to let you rui^W crash^W manage the server like I did, I need
+your ssh keys to be sent here.
+
+So if you didn't already do ( ie, if you are not nanar, not coincoin and
+not me ), please sent it to me. 
+
+-- 
+Michael Scherer
+
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000049.html b/zarb-ml/mageia-sysadm/2010-October/000049.html new file mode 100644 index 000000000..24085eb36 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000049.html @@ -0,0 +1,91 @@ + + + + [Mageia-sysadm] mailling list subscription + + + + + + + + + +

[Mageia-sysadm] mailling list subscription

+ Dexter Morgan + dmorganec at gmail.com +
+ Mon Oct 25 22:32:03 CEST 2010 +

+
+ +
On Mon, Oct 25, 2010 at 4:58 PM, Damien Lallement <mageia at damsweb.net> wrote:
+> On Mon, 25 Oct 2010 11:53:25 +0200, Michael Scherer <misc at zarb.org>
+> wrote:
+>> Hi,
+>>
+>> [...]
+>> But as I know that some people are likely to be interested into getting
+>> news about that ( like rda, for instance, as he tried to subscribed to
+>> this list and expressed interest about it ), does people think we should
+>> let everybody subscribe on this list ?
+>>
+>> I would be in favor of this, because it would in the continuity of what
+>> we did ( ie, open the archives, etc ), but I do not want to do so
+>> without the input of the others, as people may have a different PoV on
+>> the subject.
+>>
+>> So WDYT ?
+>
+> I agree with your POV.
+
+i agree too
+
+ + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000050.html b/zarb-ml/mageia-sysadm/2010-October/000050.html new file mode 100644 index 000000000..3d6ff3667 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000050.html @@ -0,0 +1,100 @@ + + + + [Mageia-sysadm] ssh keys + + + + + + + + + +

[Mageia-sysadm] ssh keys

+ Olivier Blin + mageia at blino.org +
+ Mon Oct 25 22:37:06 CEST 2010 +

+
+ +
Michael Scherer <misc at zarb.org> writes:
+
+> Hi fellow admins,
+>
+> In order to let you rui^W crash^W manage the server like I did, I need
+> your ssh keys to be sent here.
+>
+> So if you didn't already do ( ie, if you are not nanar, not coincoin and
+> not me ), please sent it to me. 
+
+Hello,
+
+Please find mine attached
+
+Thanks!
+
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: id_dsa.pub
+Type: application/octet-stream
+Size: 1125 bytes
+Desc: blino'ssh pubkey
+URL: </pipermail/mageia-sysadm/attachments/20101025/fa873928/attachment-0001.obj>
+-------------- next part --------------
+
+-- 
+Olivier Blin - blino
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000051.html b/zarb-ml/mageia-sysadm/2010-October/000051.html new file mode 100644 index 000000000..d114e817c --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000051.html @@ -0,0 +1,101 @@ + + + + [Mageia-sysadm] ssh keys + + + + + + + + + +

[Mageia-sysadm] ssh keys

+ Dexter Morgan + dmorganec at gmail.com +
+ Mon Oct 25 22:57:50 CEST 2010 +

+
+ +
On Mon, Oct 25, 2010 at 10:04 PM, Michael Scherer <misc at zarb.org> wrote:
+> Hi fellow admins,
+>
+> In order to let you rui^W crash^W manage the server like I did, I need
+> your ssh keys to be sent here.
+>
+> So if you didn't already do ( ie, if you are not nanar, not coincoin and
+> not me ), please sent it to me.
+>
+> --
+> Michael Scherer
+
+Hello,
+
+Please find mine attached
+
+
+---
+Thanks!
+Dexter Morgan
+Bug serial Killer
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: id_dsa.pub
+Type: application/x-mspublisher
+Size: 606 bytes
+Desc: not available
+URL: </pipermail/mageia-sysadm/attachments/20101025/ddf113eb/attachment.pub>
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000052.html b/zarb-ml/mageia-sysadm/2010-October/000052.html new file mode 100644 index 000000000..d16de63b6 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000052.html @@ -0,0 +1,107 @@ + + + + [Mageia-sysadm] ssh keys + + + + + + + + + +

[Mageia-sysadm] ssh keys

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Mon Oct 25 23:37:16 CEST 2010 +

+
+ +
'Twas brillig, and Michael Scherer at 25/10/10 21:04 did gyre and gimble:
+> Hi fellow admins,
+> 
+> In order to let you rui^W crash^W manage the server like I did, I need
+> your ssh keys to be sent here.
+> 
+> So if you didn't already do ( ie, if you are not nanar, not coincoin and
+> not me ), please sent it to me. 
+
+Here is mine.
+
+Col
+
+
+-- 
+
+Colin Guthrie
+mageia(at)colin.guthr.ie
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited [http://www.tribalogic.net/]
+Open Source:
+  Mageia Contributor [http://www.mageia.org/]
+  PulseAudio Hacker [http://www.pulseaudio.org/]
+  Trac Hacker [http://trac.edgewall.org/]
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: id_rsa.pub
+Type: application/x-mspublisher
+Size: 235 bytes
+Desc: not available
+URL: </pipermail/mageia-sysadm/attachments/20101025/c0efb6ff/attachment.pub>
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000053.html b/zarb-ml/mageia-sysadm/2010-October/000053.html new file mode 100644 index 000000000..fc60b7a57 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000053.html @@ -0,0 +1,98 @@ + + + + [Mageia-sysadm] mailling list subscription + + + + + + + + + +

[Mageia-sysadm] mailling list subscription

+ nicolas vigier + boklm at mars-attacks.org +
+ Tue Oct 26 13:27:05 CEST 2010 +

+
+ +
On Mon, 25 Oct 2010, Michael Scherer wrote:
+
+> Hi,
+> 
+> valstar is still down. I will contact LO soon, and see with maat about
+> getting in the DC, and post a report. I also discussed with dams, and he
+> told me he was the one who rebooted alamut to check something, so the
+> hypothesis about a power shortage is likely wrong, and so we think it is
+> a kernel panic ( and we didn't have the time to setup the magic sysctl
+> setting to reboot after kernel panic ).
+> 
+> But as I know that some people are likely to be interested into getting
+> news about that ( like rda, for instance, as he tried to subscribed to
+> this list and expressed interest about it ), does people think we should
+> let everybody subscribe on this list ?
+> 
+> I would be in favor of this, because it would in the continuity of what
+> we did ( ie, open the archives, etc ), but I do not want to do so
+> without the input of the others, as people may have a different PoV on
+> the subject.
+
+I also agree about opening subscriptions, as this list is for public
+discussions, this will be more convenient for readers.
+
+When the new mail server is setup, we can also have a sysadm alias to
+contact sysadmin team members only, if needed.
+
+Nicolas
+
+
+ + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000054.html b/zarb-ml/mageia-sysadm/2010-October/000054.html new file mode 100644 index 000000000..21aa8a4ea --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000054.html @@ -0,0 +1,131 @@ + + + + [Mageia-sysadm] valstar is back + + + + + + + + + +

[Mageia-sysadm] valstar is back

+ nicolas vigier + boklm at mars-attacks.org +
+ Tue Oct 26 13:56:00 CEST 2010 +

+
+ +
On Mon, 25 Oct 2010, Michael Scherer wrote:
+
+> Hi,
+> 
+> so a quick report.
+> 
+> Valstar is back, thanks to Sylvain Rochet ( gradator ). 
+> It seems that the firewall was misconfigurated.
+> 
+> So on 23/10/2010, I connected on the server to remove unused services
+> ( avahi, mandi, dbus, etc ). I have also removed shorewall, as we
+> disabled it on all servers at the moment ( I am more familiar with a
+> regular iptables initscripts ). 
+> 
+> Except that removing shorewall run service shorewall stop, which in turn
+> activate the firewall.
+> 
+> All servers except one ( valstar ) had shorewall correctly turned off by
+> Pascal ( maat ). I took care of valstar, but i just disabled the service
+> with chkconfig. So once I removed the package, it started to drop
+> everything in INPUT.
+> According to the logs, this happened around 15h30 CEST 
+> 
+> Oct 23 15:28:59 valstar logger: Shorewall Stopped
+> 
+> Since I was still logged in, I didn't see anything wrong ( as I assume
+> that the firewall will not cut working connection )
+> 
+> But after that, trying to connect again showed me a error. 
+> 
+> We ( dams and I ) decided to wait until monday ( as we couldn't do
+> anything when the DC was closed, and I was sick, so did maat ), and
+> discussed with gradator today, and decided that it was easiest to ask
+> for a reboot than to ask to maat to go to marseille this evening.
+> 
+> On 25/10/2010, at 15:30 ( again ), gradator looked at the server, see it
+> was a firewall issue, rebooted it without firewall and so the server is
+> now ok. 
+
+The shorewall package had been reinstalled ?
+
+> I inspected it, it work fine, there is no firewall rules loaded upon
+> startup so the problem should not repeat itself.
+> 
+> So, while I recognize I am at fault for this, I think that the shorewall
+> package have a unexpected side effect, and IMVHO, it should not setup a
+> restrictive firewall when we remove it ( and I do not say this only
+> because I am ashamed of causing the problem ).
+> 
+> In the future, how could we avoid problem like this ?
+> 
+> Easiest answer is to have servers with RAC, but we don't except on
+> alamut. I am not sure we can add one if we manage to get one.
+> 
+> Another solution is a serial cable. But this can be tricky to set up
+> ( we did for zarb )
+
+Regarding this issue, we can have a default firewall config deployed by
+puppet. Maybe puppet can also be useful to recover access to machines
+in some cases.
+
+
+ + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000055.html b/zarb-ml/mageia-sysadm/2010-October/000055.html new file mode 100644 index 000000000..56749f683 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000055.html @@ -0,0 +1,100 @@ + + + + [Mageia-sysadm] valstar is back + + + + + + + + + +

[Mageia-sysadm] valstar is back

+ Michael Scherer + misc at zarb.org +
+ Tue Oct 26 14:12:23 CEST 2010 +

+
+ +
Le mardi 26 octobre 2010 à 13:56 +0200, nicolas vigier a écrit :
+> On Mon, 25 Oct 2010, Michael Scherer wrote:
+
+> > On 25/10/2010, at 15:30 ( again ), gradator looked at the server, see it
+> > was a firewall issue, rebooted it without firewall and so the server is
+> > now ok. 
+> 
+> The shorewall package had been reinstalled ?
+
+No. I removed because I wanted to avoid side effect, but I guess I was
+too paranoid.
+
+> > In the future, how could we avoid problem like this ?
+> > 
+> > Easiest answer is to have servers with RAC, but we don't except on
+> > alamut. I am not sure we can add one if we manage to get one.
+> > 
+> > Another solution is a serial cable. But this can be tricky to set up
+> > ( we did for zarb )
+> 
+> Regarding this issue, we can have a default firewall config deployed by
+> puppet. Maybe puppet can also be useful to recover access to machines
+> in some cases.
+
+Yep. 
+Like commiting a crontask that clean the firewall :p
+
+
+-- 
+Michael Scherer
+
+
+ + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000056.html b/zarb-ml/mageia-sysadm/2010-October/000056.html new file mode 100644 index 000000000..d2f768f29 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000056.html @@ -0,0 +1,77 @@ + + + + [Mageia-sysadm] planning for sysadmin task + + + + + + + + + +

[Mageia-sysadm] planning for sysadmin task

+ nicolas vigier + boklm at mars-attacks.org +
+ Tue Oct 26 14:35:04 CEST 2010 +

+
+ +
On Sun, 24 Oct 2010, Olivier Thauvin wrote:
+
+> 
+> May I also suggest all our web be installed using RPM ?
+
+I am not sure RPM is the best tool to manage web applications in our
+case, especially for the ones that change often :
+ - it requires root permissions to be updated (or giving sudo access to
+   update the rpm, but this is equivalent to giving root access), and we
+   probably want the web team to be able to update some web applications
+   by themself.
+ - sometimes we may need to have different versions of the same
+   applications installed in different paths (one for testing, one for
+   production for instance. Or if we need different blogs or wiki
+   instances)
+
+For some web applications it won't be a problem to use an RPM, but for
+others maybe not.
+
+Nicolas
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000057.html b/zarb-ml/mageia-sysadm/2010-October/000057.html new file mode 100644 index 000000000..83766393b --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000057.html @@ -0,0 +1,88 @@ + + + + [Mageia-sysadm] planning for sysadmin task + + + + + + + + + +

[Mageia-sysadm] planning for sysadmin task

+ Damien Lallement + mageia at damsweb.net +
+ Tue Oct 26 14:42:45 CEST 2010 +

+
+ +
On Tue, 26 Oct 2010 14:35:04 +0200, nicolas vigier
+<boklm at mars-attacks.org> wrote:
+> On Sun, 24 Oct 2010, Olivier Thauvin wrote:
+> 
+>>
+>> May I also suggest all our web be installed using RPM ?
+> 
+> I am not sure RPM is the best tool to manage web applications in our
+> case, especially for the ones that change often :
+>  - it requires root permissions to be updated (or giving sudo access to
+>    update the rpm, but this is equivalent to giving root access), and we
+>    probably want the web team to be able to update some web applications
+>    by themself.
+>  - sometimes we may need to have different versions of the same
+>    applications installed in different paths (one for testing, one for
+>    production for instance. Or if we need different blogs or wiki
+>    instances)
+> 
+> For some web applications it won't be a problem to use an RPM, but for
+> others maybe not.
+> 
+> Nicolas
+
+boklm  president!
+
+I entirely agree with nicolas.
+For me, Web apps and RPMs are not necessary a good thing.
+-- 
+Damien Lallement
+aka "damsweb" or "coincoin" on IRC and twitter
+
+http://www.mageia.org
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000058.html b/zarb-ml/mageia-sysadm/2010-October/000058.html new file mode 100644 index 000000000..84cab2705 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000058.html @@ -0,0 +1,85 @@ + + + + [Mageia-sysadm] planning for sysadmin task + + + + + + + + + +

[Mageia-sysadm] planning for sysadmin task

+ Romain d'Alverny + rdalverny at gmail.com +
+ Tue Oct 26 14:43:02 CEST 2010 +

+
+ +
On Tue, Oct 26, 2010 at 14:35, nicolas vigier <boklm at mars-attacks.org> wrote:
+> On Sun, 24 Oct 2010, Olivier Thauvin wrote:
+>
+>> May I also suggest all our web be installed using RPM ?
+>
+> I am not sure RPM is the best tool to manage web applications in our
+> case, especially for the ones that change often :
+>  - it requires root permissions to be updated (or giving sudo access to
+>   update the rpm, but this is equivalent to giving root access), and we
+>   probably want the web team to be able to update some web applications
+>   by themself.
+>  - sometimes we may need to have different versions of the same
+>   applications installed in different paths (one for testing, one for
+>   production for instance. Or if we need different blogs or wiki
+>   instances)
+>
+> For some web applications it won't be a problem to use an RPM, but for
+> others maybe not.
+
+I second that. Managing web apps is more likely to happen as:
+ * dev/test on local machines, by anyone
+ * commit/deploy/validate to staging server, triggered by anyone on the team,
+ * commit/deploy on production server, triggered by any webmaster.
+
+So svn/git/rsync (or such tools) will be used. RPM is not really a
+practicable option here, but maybe for very specific apps that will
+not be retouched at all.
+
+Romain
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000059.html b/zarb-ml/mageia-sysadm/2010-October/000059.html new file mode 100644 index 000000000..1ba02a52c --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000059.html @@ -0,0 +1,87 @@ + + + + [Mageia-sysadm] planning for sysadmin task + + + + + + + + + +

[Mageia-sysadm] planning for sysadmin task

+ Colin Guthrie + cguthrie at mandriva.org +
+ Tue Oct 26 14:51:41 CEST 2010 +

+
+ +
'Twas brillig, and Romain d'Alverny at 26/10/10 13:43 did gyre and gimble:
+> So svn/git/rsync (or such tools) will be used. RPM is not really a
+> practicable option here, but maybe for very specific apps that will
+> not be retouched at all.
+
+Yeah, I definitely agree here. I think using certain
+components/dependencies of webapps from RPMs is OK (I'm guessing a lot
+of the perl stuff, Zend Framework, pear etc.), but I never use the
+webapps themselves from RPM packages.
+
+Running test upgrades and sandboxes etc. is nigh on impossible via an
+RPM route and sometimes massive incompatibilities can result (e.g.
+upgrading from Joomla 1.0.x to 1.5.x will break your site completely
+unless you prepare it specifically beforehand!)
+
+So I'd certainly be in favour of using git or svn (preferably the former).
+
+Col
+
+-- 
+
+Colin Guthrie
+cguthrie(at)mandriva.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited [http://www.tribalogic.net/]
+Open Source:
+  Mageia Contributor [http://www.mageia.org/]
+  PulseAudio Hacker [http://www.pulseaudio.org/]
+  Trac Hacker [http://trac.edgewall.org/]
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000060.html b/zarb-ml/mageia-sysadm/2010-October/000060.html new file mode 100644 index 000000000..cd1de94f0 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000060.html @@ -0,0 +1,106 @@ + + + + [Mageia-sysadm] planning for sysadmin task + + + + + + + + + +

[Mageia-sysadm] planning for sysadmin task

+ Michael Scherer + misc at zarb.org +
+ Tue Oct 26 15:23:53 CEST 2010 +

+
+ +
Le mardi 26 octobre 2010 à 14:35 +0200, nicolas vigier a écrit :
+> On Sun, 24 Oct 2010, Olivier Thauvin wrote:
+> 
+> > 
+> > May I also suggest all our web be installed using RPM ?
+> 
+> I am not sure RPM is the best tool to manage web applications in our
+> case, especially for the ones that change often :
+>  - it requires root permissions to be updated (or giving sudo access to
+>    update the rpm, but this is equivalent to giving root access), and we
+>    probably want the web team to be able to update some web applications
+>    by themself.
+
+Well, that's a question of giving permissions, not using rpm or not.
+
+And that's a question that I think I have already asked on irc when we
+devised the team, what is the role of the web team exactly regarding our
+servers and the software and how do we articulate with them.
+
+Ie, who is in charge of the following :
+- setup of web application
+  - apache side
+  - filesystem side
+  - database side
+
+- setup of infrastructure ( ie apache module)
+
+- who is in charge of securing 
+  - the servers 
+  - each applications
+
+- who is in charge of backuping 
+  - the server  
+  - the applications
+
+Is everything taken care of the sysadm team, in which case no permission
+should be given to webteam, or some part of this are ( beware, because
+some part are dependent, ie people who setup a application take care of
+the security and of bugfixing it ), and so will the sysadm team act like
+a shared server provider toward various member of the community ?
+
+And if we choose the path of a shared server provider, shall the web
+team alone be able to have a web site, or should we open the possibility
+to others team to do so ? ( ie, if the designers want to setup a custom
+webapp, who shall take care of that ? )
+
+
+-- 
+Michael Scherer
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000061.html b/zarb-ml/mageia-sysadm/2010-October/000061.html new file mode 100644 index 000000000..57258513e --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000061.html @@ -0,0 +1,129 @@ + + + + [Mageia-sysadm] planning for sysadmin task + + + + + + + + + +

[Mageia-sysadm] planning for sysadmin task

+ Romain d'Alverny + rdalverny at gmail.com +
+ Tue Oct 26 15:44:21 CEST 2010 +

+
+ +
On Tue, Oct 26, 2010 at 15:23, Michael Scherer <misc at zarb.org> wrote:
+> And that's a question that I think I have already asked on irc when we
+> devised the team, what is the role of the web team exactly regarding our
+> servers and the software and how do we articulate with them.
+>
+> Ie, who is in charge of the following :
+> - setup of web application
+>  - apache side
+>  - filesystem side
+>  - database side
+
+Sysadm. Per request of webteam.
+
+> - setup of infrastructure ( ie apache module)
+
+Sysadm. Per request of webteam.
+
+> - who is in charge of securing
+>  - the servers
+>  - each applications
+
+Both. Server security is going to be affected by application security
+and this is the webteam role to control that part. And to assume/fix
+potential issues.
+
+> - who is in charge of backuping
+>  - the server
+
+sysadm.
+
+>  - the applications
+
+Webteam. Destroying and restoring a webapp must be a process taken
+into account at their level. Doesn't prevent sysadmins to be able to
+run it as well.
+
+It's likely going to be a back-and-forth process but ideally, the
+webteam would ask, for a given web app, for:
+ - a database type and access (with expected usage size),
+ - a vhost (provided it's not under an existing vhost),
+ - a web repository where to put and update files (so they must have a
+write access on this),
+ - a specific Apache config,
+ - a read access to related Apache logs
+ - a list of needed modules (PHP, Ruby, Perl, others)
+
+And should be able to work with this.
+
+However we can think to future provision to some webteam people
+(webmasters for instance) extended rights (Apache config write access,
+reloading Apache, extended rights on database). Depends on situation
+and roles.
+
+> Is everything taken care of the sysadm team, in which case no permission
+> should be given to webteam, or some part of this are ( beware, because
+> some part are dependent, ie people who setup a application take care of
+> the security and of bugfixing it ), and so will the sysadm team act like
+> a shared server provider toward various member of the community ?
+
+More like a shared-server provider. However situation may differ from
+web app to web app. Don't know for sure yet. But as a start, I would
+go per the process described above.
+
+> And if we choose the path of a shared server provider, shall the web
+> team alone be able to have a web site, or should we open the possibility
+> to others team to do so ? ( ie, if the designers want to setup a custom
+> webapp, who shall take care of that ? )
+
+They should see that with the webteam or be part of it. That's the
+place where all Web-related stuff (be it technical or not) should be
+gathered and discussed.
+
+Romain
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000062.html b/zarb-ml/mageia-sysadm/2010-October/000062.html new file mode 100644 index 000000000..f399d84fb --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000062.html @@ -0,0 +1,110 @@ + + + + [Mageia-sysadm] planning for sysadmin task + + + + + + + + + +

[Mageia-sysadm] planning for sysadmin task

+ Olivier Thauvin + nanardon at nanardon.zarb.org +
+ Tue Oct 26 16:06:41 CEST 2010 +

+
+ +
* Romain d'Alverny (rdalverny at gmail.com) wrote:
+> On Tue, Oct 26, 2010 at 15:23, Michael Scherer <misc at zarb.org> wrote:
+> Sysadm. Per request of webteam.
+> 
+> > - setup of infrastructure ( ie apache module)
+> 
+> Sysadm. Per request of webteam.
+> 
+> > - who is in charge of securing
+> >  - the servers
+> >  - each applications
+> 
+> Both. Server security is going to be affected by application security
+> and this is the webteam role to control that part. And to assume/fix
+> potential issues.
+
+From the experience I had with epoll, seting-up the application were
+complicated in past due by the lack of dependencies in the rpm or on
+perl side.
+Epoll need a lot of perl module, mainly because Catalyst is splitted in
+several part.
+
+I solved the issue since (on both perl side and rpm side).
+
+Since you prefer to not using rpm, the work to setup such application
+get more complicated, especially if the sys admin don't know perl (in
+this case, the same apply to php apps, python, etc...).
+
+I don't like the "svn snapshot" way for officially in use web apps. It
+works for testing the devel version, but I'd really hope anyone
+working on web apps is able to have a clear roadmap and managing branch
+for quick security fixes.
+And since you have a stable branch and a devel one, you are able to
+quickly redo a rpm.
+
+Or are we assuming Mageia will not be able to provide security fixes as
+rpm for anyone using the distribution and so we prefer ourself to bypass
+them ?
+
+BTW: who is the webteam ? Does CatDap (Buchan's apps) and MGA::Mirrors
+(mine) make us entering in webteam ? Is the Bs part of webteam works ?
+
+-- 
+
+Olivier Thauvin
+CNRS  -  LATMOS
+♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 197 bytes
+Desc: not available
+URL: </pipermail/mageia-sysadm/attachments/20101026/ef5de541/attachment.asc>
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000063.html b/zarb-ml/mageia-sysadm/2010-October/000063.html new file mode 100644 index 000000000..e968bca79 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000063.html @@ -0,0 +1,163 @@ + + + + [Mageia-sysadm] planning for sysadmin task + + + + + + + + + +

[Mageia-sysadm] planning for sysadmin task

+ Romain d'Alverny + rdalverny at gmail.com +
+ Tue Oct 26 16:39:52 CEST 2010 +

+
+ +
On Tue, Oct 26, 2010 at 16:06, Olivier Thauvin
+<nanardon at nanardon.zarb.org> wrote:
+> * Romain d'Alverny (rdalverny at gmail.com) wrote:
+>> On Tue, Oct 26, 2010 at 15:23, Michael Scherer <misc at zarb.org> wrote:
+>> Sysadm. Per request of webteam.
+>>
+>> > - setup of infrastructure ( ie apache module)
+>>
+>> Sysadm. Per request of webteam.
+>>
+>> > - who is in charge of securing
+>> >  - the servers
+>> >  - each applications
+>>
+>> Both. Server security is going to be affected by application security
+>> and this is the webteam role to control that part. And to assume/fix
+>> potential issues.
+> [...]
+> Since you prefer to not using rpm, the work to setup such application
+> get more complicated, especially if the sys admin don't know perl (in
+> this case, the same apply to php apps, python, etc...).
+
+I know this firsthand, from both sides, yes. That's the webteam
+responsibility to provide this info for installing/upgrading the app,
+and that partially requires from the webteam some knowledge about the
+system.
+
+So indeed, both teams need to know/understand each other.
+
+> I don't like the "svn snapshot" way for officially in use web apps. It
+> works for testing the devel version, but I'd really hope anyone
+> working on web apps is able to have a clear roadmap and managing branch
+> for quick security fixes.
+
+Sure. But it happens to break nonetheless. What is crucial is not that
+there is no breach (there will), it's that it is quickly reported and
+fixed.
+
+> And since you have a stable branch and a devel one, you are able to
+> quickly redo a rpm.
+
+I understand that but a RPM is an unnecessary step here IMHO. A web
+app/development life cycle in dev/production is not the same as one
+for a packaged app for a distribution.
+
+All I care here as a Web dev/project manager is:
+ - working on the app
+ - making sure it works
+ - pushing to prod
+ - check again
+ - iterate.
+
+Pushing deployment from dev to production, assuming all tests pass,
+should be ideally as fast as pushing a single button and waiting for a
+few seconds. And it may not be a trivial thing either (not just
+pushing files, but moving the app into several states for a clean
+migration).
+
+At some extent, RPM dependencies would be a useful thing for setting
+up the application but this mostly happens once (first install) and
+can be easily hosted within the web application itself (and then
+handle the error) - WordPress and Drupal do it for instance.
+
+I perfectly understand that this does not fit with the packaging
+reasoning for a Linux distribution.
+
+
+> Or are we assuming Mageia will not be able to provide security fixes as
+> rpm for anyone using the distribution and so we prefer ourself to bypass
+> them ?
+
+Not related. If these are regular web apps, we may as well port
+changes and fixes back to the upstream project (be it our own) and
+have these repackaged. But packaging is not the focus of the webteam.
+
+
+> BTW: who is the webteam ? Does CatDap (Buchan's apps) and MGA::Mirrors
+> (mine) make us entering in webteam ? Is the Bs part of webteam works ?
+
+The webteam, well, I'm preparing to shoot a first mail to people who
+gathered on the wiki page; mostly developers and web integrators.
+Nothing definitive, but I'm a volunteer to lead the first efforts for
+the team.
+
+About CatDap and MGA:Mirrors, yes, hopefully. That makes you part of
+it in that other webteam members should be aware of this app and
+reciprocally, all members should collaborate.
+
+The BS is a separate kind of a beast but indeed, parts of it could
+definitely benefit from web team developers/integrators (code,
+organisation, design/graphics/UX levels).
+
+So we can discuss this further with other future webteam members but I
+will seriously not manage a production environment that goes through
+packaging for app updates.
+
+That does not mean I don't care about security - that means that
+there's a balance to find and that web developers have to be in charge
+of their apps security as well. So if that means we need to have
+separate servers to isolate risks, so be it. If that means we need to
+go for a different type of hosting, so be it.
+
+And I don't say that harshly. :-p just in case.
+
+
+Romain
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000064.html b/zarb-ml/mageia-sysadm/2010-October/000064.html new file mode 100644 index 000000000..d2a7c371e --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000064.html @@ -0,0 +1,83 @@ + + + + [Mageia-sysadm] planning for sysadmin task + + + + + + + + + +

[Mageia-sysadm] planning for sysadmin task

+ nicolas vigier + boklm at mars-attacks.org +
+ Tue Oct 26 16:40:13 CEST 2010 +

+
+ +
On Tue, 26 Oct 2010, Olivier Thauvin wrote:
+
+> 
+> From the experience I had with epoll, seting-up the application were
+> complicated in past due by the lack of dependencies in the rpm or on
+> perl side.
+> Epoll need a lot of perl module, mainly because Catalyst is splitted in
+> several part.
+> 
+> I solved the issue since (on both perl side and rpm side).
+> 
+> Since you prefer to not using rpm, the work to setup such application
+> get more complicated, especially if the sys admin don't know perl (in
+> this case, the same apply to php apps, python, etc...).
+
+It's not "not using rpm at all for any web apps". I think we can use RPM
+packages when it's more convenient. In some cases such as epoll, it can
+be more convenient to use an RPM. But not in all cases. I think it
+depends on the application, and how we use it.
+
+For the main mageia.org website for instance, do we want to use a
+package that we will have to update, rebuild, and ask an admin to
+install it, each time someone in the web team wants to fix a typo ?
+
+Nicolas
+
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000065.html b/zarb-ml/mageia-sysadm/2010-October/000065.html new file mode 100644 index 000000000..b1881efe6 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000065.html @@ -0,0 +1,189 @@ + + + + [Mageia-sysadm] ssh keys + + + + + + + + + +

[Mageia-sysadm] ssh keys

+ Michael Scherer + misc at zarb.org +
+ Tue Oct 26 16:46:35 CEST 2010 +

+
+ +
Le lundi 25 octobre 2010 à 22:04 +0200, Michael Scherer a écrit :
+> Hi fellow admins,
+> 
+> In order to let you rui^W crash^W manage the server like I did, I need
+> your ssh keys to be sent here.
+> 
+> So if you didn't already do ( ie, if you are not nanar, not coincoin and
+> not me ), please sent it to me. 
+
+I have added the keys that were sent to me in puppet ( without svn or
+anything yet, nothing fancy ).
+
+So, a quick ( well, not so quick ) explanation of what I did :
+1) setup puppetmaster ( ie, the reference ) on valstar :
+
+  urpmi puppet-server
+  create some files in /etc/puppet/manifests/
+
+  site.pp , who just reference the 2 others :
+
+  [root at valstar manifests]# ls
+  common.pp  nodes.pp  site.pp
+  [root at valstar manifests]# cat site.pp 
+  import "common"
+  import "nodes"
+
+  nodes.pp (arbitrary name ) contains the list of nodes, and their
+  class ( here, only one class, default_mageia_server, defined in
+common ):
+
+  node alamut {
+        include default_mageia_server
+  }
+
+in common.pp, we have this class :
+
+class default_mageia_server {
+    include default_ssh_root_key
+    include base_packages
+}
+
+which lead me to the 2 first type of thing we will do with puppet 
+1) packages installation :
+
+class base_packages {
+
+    $package_list = ['screen', 'vim-enhanced']
+
+    package { $package_list:
+        ensure => installed;
+    }
+}
+
+basically, this mean that screen and vim-enhanced will be installed by
+default, using urpmi ( or the appropriate tool depending on the OS ), on
+every server. Add packages if needed, please keep the comment I have
+added about who requested what and why, if not obvious ( first one to
+install kde will be killed so hard that even his ancestors will die (tm)
+sinfest ). 
+
+We can also use this to ensure a package is never installed ( just cut
+and past the class, and change the list, and the ensure value. See
+puppet doc for that .
+
+2) ssh_keys installation.
+
+Like packages, there is a type for ssh keys :
+
+class default_ssh_root_key {
+    ssh_authorized_key { "ssh key misc":
+        type => "ssh-rsa",
+        key => "insert-real-long-key-here", 
+        user => "root"
+    }
+    ssh_authorized_key { "ssh key blino":
+        type => "ssh-dss",
+        key => "insert-real-longer-and-stronger-bigger-blino-key-here", 
+        user => "root"
+    }
+}
+
+this mean that my key ( and blino's one ) is added to the proper file
+directly, with correct permission. I have added blino, nanar, dmorgan,
+coling, dams and me. Others didn't send it yet.
+ 
+
+that's for the basic part. Puppetmaster reload itself when it detect the
+config change. And it refuse invalid config in case of problem as does
+the puppet agent on each node.
+
+
+So next, on each server ( the 4 one in LO, I am taking care of the gandi
+vm as soon as I finished to write this mail ), I have setup the puppet
+agent :
+
+
+2) setup puppet
+for each node :
+
+  urpmi puppet
+  vim /etc/puppet/puppet.conf ( add a "server = valstar.mageia.org" 
+     entry in [puppetd], will likely be taken care by puppet itself
+     later )
+  service puppet start
+
+on valstar, to authenticate the request ( ie, when puppet is started, it
+exchanges ssl certs with the master to encrypt future exchange ).
+
+puppetca --list
+puppetca --sign server
+
+on the node that just signed :
+tail -f /var/log/messages, see there is no error, and test that we can
+still connect as root.
+Beware, this changed with puppet 2.6 some months ago, so i suggest
+people to read the documentation if they read this mail after the end of
+2010 :).
+
+If you have any questions on how to use puppet after this quick
+introduction, do not hesitate to ping me on irc, or better here so
+everybody will get the answer.
+
+
+-- 
+Michael Scherer
+
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000066.html b/zarb-ml/mageia-sysadm/2010-October/000066.html new file mode 100644 index 000000000..973e46055 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000066.html @@ -0,0 +1,83 @@ + + + + [Mageia-sysadm] irc channel, and some guideline for coordination + + + + + + + + + +

[Mageia-sysadm] irc channel, and some guideline for coordination

+ Michael Scherer + misc at zarb.org +
+ Tue Oct 26 17:29:14 CEST 2010 +

+
+ +
Hi,
+
+I have opened a irc channel ( #mageia-sysadm, as that's the name of the
+team, and I propose to try to keep this convention ), so we can discuss
+more easily on irc than the rather scathered discussion we have
+( between #mageia, #mageia-fr, private discussion, #lost-oasis,
+#mageia-meeting ). 
+
+I would also propose that we discuss about how we decide who does what.
+
+IE, someone want to take care of something, it send a email about "i
+will do this", do it, and send a email "i did this" ( if we don't
+forget ).
+
+
+-- 
+Michael Scherer
+
+
+ + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000067.html b/zarb-ml/mageia-sysadm/2010-October/000067.html new file mode 100644 index 000000000..cae8e8a7a --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000067.html @@ -0,0 +1,83 @@ + + + + [Mageia-sysadm] [LONG] A not so modest proposal + + + + + + + + + +

[Mageia-sysadm] [LONG] A not so modest proposal

+ nicolas vigier + boklm at mars-attacks.org +
+ Tue Oct 26 17:41:00 CEST 2010 +

+
+ +
On Sun, 24 Oct 2010, Michael Scherer wrote:
+
+> 
+> So, WDYT ?
+> ( please do not let me be warnocked
+> http://en.wikipedia.org/wiki/Warnocked )
+
+I agree with your email. I think that if nobody is against this, we can
+go with this.
+
+First we need the basic puppet config and organisation, to let different
+people start working on some services.
+
+I created the directory svn+ssh://svn.mageia.org/svn/adm/puppet. In this
+directory we have the subdirectory "manifests" to be checked out in
+/etc/puppet/manifests and "modules" to be checked out in
+/etc/puppet/modules.
+
+Do you know any good puppet configuration examples ?
+This one is interesting :
+http://www.example42.com/puppet/browseinfrastructures.php
+
+Nicolas
+
+
+ + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000068.html b/zarb-ml/mageia-sysadm/2010-October/000068.html new file mode 100644 index 000000000..cdb889c17 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000068.html @@ -0,0 +1,94 @@ + + + + [Mageia-sysadm] irc channel, and some guideline for coordination + + + + + + + + + +

[Mageia-sysadm] irc channel, and some guideline for coordination

+ Michael Scherer + misc at zarb.org +
+ Tue Oct 26 17:52:32 CEST 2010 +

+
+ +
Le mardi 26 octobre 2010 à 17:29 +0200, Michael Scherer a écrit :
+> Hi,
+> 
+> I have opened a irc channel ( #mageia-sysadm, as that's the name of the
+> team, and I propose to try to keep this convention ), so we can discuss
+> more easily on irc than the rather scathered discussion we have
+> ( between #mageia, #mageia-fr, private discussion, #lost-oasis,
+> #mageia-meeting ). 
+
+And I also forgot, I have activated a logging bot I have prepared
+before, ( Muet_d_hiver, Wintermute translated in french ). It is based
+on supybot ( like the meetbot instance in #mageia-meeting ) and for now,
+it just log in some directories. 
+
+But I was planning to put the log in a website, as there is likely some
+people who do not use screen/tmux + irssi/etc and therefore will miss
+some discussions ( for example, rda, or member of the webteam, or
+severine, or people outside mageia like gradator ), and it is also
+easier to reference.  
+
+If someone is against, do not hesitate to tell why so we can tweak the
+setup or remove it ( it also log #mageia-council, -dev and -board, who
+are quite unused but registered some weeks ago for the futur, I didn't
+really wanted to add it elsewhere without the consent of others users,
+or the legitimacy to do so, ie, it will have to be seen with the irc
+council )
+
+-- 
+Michael Scherer
+
+
+ + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000069.html b/zarb-ml/mageia-sysadm/2010-October/000069.html new file mode 100644 index 000000000..1ffd46482 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000069.html @@ -0,0 +1,91 @@ + + + + [Mageia-sysadm] irc channel, and some guideline for coordination + + + + + + + + + +

[Mageia-sysadm] irc channel, and some guideline for coordination

+ Romain d'Alverny + rdalverny at gmail.com +
+ Tue Oct 26 17:57:11 CEST 2010 +

+
+ +
On Tue, Oct 26, 2010 at 17:52, Michael Scherer <misc at zarb.org> wrote:
+> Le mardi 26 octobre 2010 à 17:29 +0200, Michael Scherer a écrit :
+>> I have opened a irc channel ( #mageia-sysadm, as that's the name of the
+>> team, and I propose to try to keep this convention ), so we can discuss
+>> more easily on irc than the rather scathered discussion we have
+>> ( between #mageia, #mageia-fr, private discussion, #lost-oasis,
+>> #mageia-meeting ).
+
+Ok.
+
+> And I also forgot, I have activated a logging bot I have prepared
+> before, ( Muet_d_hiver, Wintermute translated in french ). It is based
+> on supybot ( like the meetbot instance in #mageia-meeting ) and for now,
+> it just log in some directories.
+>
+> But I was planning to put the log in a website, as there is likely some
+> people who do not use screen/tmux + irssi/etc and therefore will miss
+> some discussions ( for example, rda, or member of the webteam, or
+> severine, or people outside mageia like gradator ), and it is also
+> easier to reference.
+
+Ok for me. If we could add an action into it so that it could
+highlight points of discussions (a bit like meetbot, but without the
+session open/close. Not sure if this is clear, I'll try to draft it
+otherwise.
+
+Romain
+
+ + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000070.html b/zarb-ml/mageia-sysadm/2010-October/000070.html new file mode 100644 index 000000000..0cd616683 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000070.html @@ -0,0 +1,91 @@ + + + + [Mageia-sysadm] irc channel, and some guideline for coordination + + + + + + + + + +

[Mageia-sysadm] irc channel, and some guideline for coordination

+ Romain d'Alverny + rdalverny at gmail.com +
+ Tue Oct 26 17:57:21 CEST 2010 +

+
+ +
On Tue, Oct 26, 2010 at 17:52, Michael Scherer <misc at zarb.org> wrote:
+> Le mardi 26 octobre 2010 à 17:29 +0200, Michael Scherer a écrit :
+>> I have opened a irc channel ( #mageia-sysadm, as that's the name of the
+>> team, and I propose to try to keep this convention ), so we can discuss
+>> more easily on irc than the rather scathered discussion we have
+>> ( between #mageia, #mageia-fr, private discussion, #lost-oasis,
+>> #mageia-meeting ).
+
+Ok.
+
+> And I also forgot, I have activated a logging bot I have prepared
+> before, ( Muet_d_hiver, Wintermute translated in french ). It is based
+> on supybot ( like the meetbot instance in #mageia-meeting ) and for now,
+> it just log in some directories.
+>
+> But I was planning to put the log in a website, as there is likely some
+> people who do not use screen/tmux + irssi/etc and therefore will miss
+> some discussions ( for example, rda, or member of the webteam, or
+> severine, or people outside mageia like gradator ), and it is also
+> easier to reference.
+
+Ok for me. If we could add an action into it so that it could
+highlight points of discussions (a bit like meetbot, but without the
+session open/close. Not sure if this is clear, I'll try to draft it
+otherwise.
+
+Romain
+
+ + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000071.html b/zarb-ml/mageia-sysadm/2010-October/000071.html new file mode 100644 index 000000000..cb3dfeee1 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000071.html @@ -0,0 +1,79 @@ + + + + [Mageia-sysadm] planning for sysadmin task + + + + + + + + + +

[Mageia-sysadm] planning for sysadmin task

+ nicolas vigier + boklm at mars-attacks.org +
+ Tue Oct 26 18:00:15 CEST 2010 +

+
+ +
On Sat, 23 Oct 2010, Michael Scherer wrote:
+
+> Hi, 
+> 
+> so now the server are in place, we have to install them. Here is a
+> proposal of the needed services :
+> 
+> so as said on the blog, one of the first task should be to migrate dns
+> from zarb to mageia.org. 
+> - primary dns ( on alamut )
+> - secondary dns ( at gandi )
+
+As we want to store the DNS config (and everything) in puppet, I think
+the first thing needed now is the main puppet configuration and
+structure.
+
+We can use the temporary svn for now to store puppet config (until the
+real svn is available, which will requires LDAP).
+
+Then we can have everybody working on the different services setup in
+puppet.
+
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000072.html b/zarb-ml/mageia-sysadm/2010-October/000072.html new file mode 100644 index 000000000..872d88652 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000072.html @@ -0,0 +1,91 @@ + + + + [Mageia-sysadm] planning for sysadmin task + + + + + + + + + +

[Mageia-sysadm] planning for sysadmin task

+ Michael Scherer + misc at zarb.org +
+ Tue Oct 26 18:04:07 CEST 2010 +

+
+ +
Le mardi 26 octobre 2010 à 18:00 +0200, nicolas vigier a écrit :
+> On Sat, 23 Oct 2010, Michael Scherer wrote:
+> 
+> > Hi, 
+> > 
+> > so now the server are in place, we have to install them. Here is a
+> > proposal of the needed services :
+> > 
+> > so as said on the blog, one of the first task should be to migrate dns
+> > from zarb to mageia.org. 
+> > - primary dns ( on alamut )
+> > - secondary dns ( at gandi )
+> 
+> As we want to store the DNS config (and everything) in puppet, I think
+> the first thing needed now is the main puppet configuration and
+> structure.
+
+ok, I will work on it.
+
+> We can use the temporary svn for now to store puppet config (until the
+> real svn is available, which will requires LDAP).
+
+Ok for me.
+
+> Then we can have everybody working on the different services setup in
+> puppet.
+
+Well, we can also let people setup first ( and document ) and then
+migrate and let people learn puppet in the mean time ( for example, with
+some kind of paid programming, one that know puppet and that edit the
+file and explain to the other one how he achieve the same result in
+puppet than doing it by hand ). 
+-- 
+Michael Scherer
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000073.html b/zarb-ml/mageia-sysadm/2010-October/000073.html new file mode 100644 index 000000000..67518215a --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000073.html @@ -0,0 +1,104 @@ + + + + [Mageia-sysadm] irc channel, and some guideline for coordination + + + + + + + + + +

[Mageia-sysadm] irc channel, and some guideline for coordination

+ Michael Scherer + misc at zarb.org +
+ Tue Oct 26 18:11:05 CEST 2010 +

+
+ +
Le mardi 26 octobre 2010 à 17:57 +0200, Romain d'Alverny a écrit :
+
+> > And I also forgot, I have activated a logging bot I have prepared
+> > before, ( Muet_d_hiver, Wintermute translated in french ). It is based
+> > on supybot ( like the meetbot instance in #mageia-meeting ) and for now,
+> > it just log in some directories.
+> >
+> > But I was planning to put the log in a website, as there is likely some
+> > people who do not use screen/tmux + irssi/etc and therefore will miss
+> > some discussions ( for example, rda, or member of the webteam, or
+> > severine, or people outside mageia like gradator ), and it is also
+> > easier to reference.
+> 
+> Ok for me. If we could add an action into it so that it could
+> highlight points of discussions (a bit like meetbot, but without the
+> session open/close. Not sure if this is clear, I'll try to draft it
+> otherwise.
+
+I can understand what you mean, but I fear this would requires a supybot
+patch, or a custom plugin, a custom bot.
+( note that I used supybot just because it was installed and as a test,
+and writing irc bot is so trivial that I wrote so far 2 in python, 1 in
+ruby, 2 in perl and 1 in perl 6, and that people wrote irc bot in every
+language I have searched, from x86 asm to php ).
+
+But yes, drafting a set of requirement would be good :
+
+- produce webpage output, one for each day
+  - with a css / templates ?
+  - who can be read easyly ( ie different color for different people )
+  - with proper anchor support ( so link to the web page can be given )
+- produce text output
+- possible to stop logging ( with a prefix like supybot does ) 
+
+( and the usual "not written in some obscure dialect mixig cobol and
+fortran", "not taking 3g of ram", etc ).
+
+But this is not the priority for the moment 
+
+-- 
+Michael Scherer
+
+
+ + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000074.html b/zarb-ml/mageia-sysadm/2010-October/000074.html new file mode 100644 index 000000000..663cd140d --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000074.html @@ -0,0 +1,85 @@ + + + + [Mageia-sysadm] ssh keys + + + + + + + + + +

[Mageia-sysadm] ssh keys

+ Séverine Wiltgen + swiltgen at gmail.com +
+ Tue Oct 26 18:50:54 CEST 2010 +

+
+ +
2010/10/25 Colin Guthrie <mageia at colin.guthr.ie>:
+> 'Twas brillig, and Michael Scherer at 25/10/10 21:04 did gyre and gimble:
+>> Hi fellow admins,
+>>
+>> In order to let you rui^W crash^W manage the server like I did, I need
+>> your ssh keys to be sent here.
+>>
+>> So if you didn't already do ( ie, if you are not nanar, not coincoin and
+>> not me ), please sent it to me.
+>
+Here is my key.
+
+-- 
+sev
+
+> _______________________________________________
+> Mageia-sysadm mailing list
+> Mageia-sysadm at mageia.org
+> https://www.mageia.org/mailman/listinfo/mageia-sysadm
+>
+>
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: id_rsa.pub
+Type: application/octet-stream
+Size: 732 bytes
+Desc: not available
+URL: </pipermail/mageia-sysadm/attachments/20101026/12498b60/attachment.obj>
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000075.html b/zarb-ml/mageia-sysadm/2010-October/000075.html new file mode 100644 index 000000000..5e388964a --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000075.html @@ -0,0 +1,109 @@ + + + + [Mageia-sysadm] [LONG] A not so modest proposal + + + + + + + + + +

[Mageia-sysadm] [LONG] A not so modest proposal

+ Michael Scherer + misc at zarb.org +
+ Tue Oct 26 19:46:52 CEST 2010 +

+
+ +
Le mardi 26 octobre 2010 à 17:41 +0200, nicolas vigier a écrit :
+> On Sun, 24 Oct 2010, Michael Scherer wrote:
+> 
+> > 
+> > So, WDYT ?
+> > ( please do not let me be warnocked
+> > http://en.wikipedia.org/wiki/Warnocked )
+> 
+> I agree with your email. I think that if nobody is against this, we can
+> go with this.
+> 
+> First we need the basic puppet config and organisation, to let different
+> people start working on some services.
+> 
+> I created the directory svn+ssh://svn.mageia.org/svn/adm/puppet. In this
+> directory we have the subdirectory "manifests" to be checked out in
+> /etc/puppet/manifests and "modules" to be checked out in
+> /etc/puppet/modules.
+
+Ok so I setup /etc/puppet/ to auto extracted from this svn each 5
+minutes. I have added the cronjob in puppet, as well as the key of
+severine, and a basic openssh module.  
+
+For people who want to commit, connect on krampouezh.mageia.org, create
+yourself a account ( until we migrate to ldap for this ) and you can
+then checkout/commit on it. 
+
+We will need to add the ntp setup, some MTA, ( maybe the timezone so we
+will not have issue for the next server ) and then once we have a basic
+MTA, a svn hook to send commit mail here.
+
+Again, if you have any question, do not hesitate.
+
+> Do you know any good puppet configuration examples ?
+> This one is interesting :
+> http://www.example42.com/puppet/browseinfrastructures.php
+
+I used a too complex setup with numerous empty directory, so I guess no,
+I only found bad example :p 
+To me, the current one ( manifests for the configure file, and modules/
+for modules ) is fine at the moment.
+
+I suggest that we first become used to puppet and then decide how to
+split, if needed.
+
+I like the idea of having a directory nodes, with one file per node, and
+for the rest, I do not think it is worth the added complexity at the
+moment.
+
+
+-- 
+Michael Scherer
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000076.html b/zarb-ml/mageia-sysadm/2010-October/000076.html new file mode 100644 index 000000000..4c708abe1 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000076.html @@ -0,0 +1,75 @@ + + + + [Mageia-sysadm] Located near ielo.net / Lost Oasis + + + + + + + + + +

[Mageia-sysadm] Located near ielo.net / Lost Oasis

+ Jérôme Hénin + heninj at gmail.com +
+ Tue Oct 26 23:50:56 CEST 2010 +

+
+ +
Hi everyone,
+
+I read that some sysadmins came to Marseille last week to install
+servers in the ielo.net data center. Too bad that I didn't see that
+earlier: I live very close to that place, maybe I could have helped
+with something. I know that being physically close to the servers is
+not often useful, but if there anything I can do, please let me know.
+At least, next time people come here to tend to the servers, I can
+offer a round of drinks, or even a pizza, who knows :-)
+
+Cheers,
+Jérôme
+
+PS: I hope this is not too far off-topic for this list. If it is, I
+apologize. Please flame me off-list to reduce traffic ;-)
+
+ + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000077.html b/zarb-ml/mageia-sysadm/2010-October/000077.html new file mode 100644 index 000000000..59e18babb --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000077.html @@ -0,0 +1,92 @@ + + + + [Mageia-sysadm] Located near ielo.net / Lost Oasis + + + + + + + + + +

[Mageia-sysadm] Located near ielo.net / Lost Oasis

+ Michael Scherer + misc at zarb.org +
+ Wed Oct 27 00:09:11 CEST 2010 +

+
+ +
Le mardi 26 octobre 2010 à 23:50 +0200, Jérôme Hénin a écrit :
+> Hi everyone,
+> 
+> I read that some sysadmins came to Marseille last week to install
+> servers in the ielo.net data center. Too bad that I didn't see that
+> earlier: I live very close to that place, maybe I could have helped
+> with something. I know that being physically close to the servers is
+> not often useful, but if there anything I can do, please let me know.
+> At least, next time people come here to tend to the servers, I can
+> offer a round of drinks, or even a pizza, who knows :-)
+> 
+> Cheers,
+> Jérôme
+> 
+> PS: I hope this is not too far off-topic for this list. If it is, I
+> apologize. Please flame me off-list to reduce traffic ;-)
+
+Hi,
+
+No problem. We already have someone near Marseille ( maat from AUFML, in
+Aix en provence ), and you are the third one to propose your help
+( second being Olivier Faurax, living in La Ciota ). And the Lost Oasis
+people are very helpful, so I doubt we will need to ask you something.
+
+And on friday, we were 4, that was enough to move, mount and setup the
+servers, and we just finished in time ( ie, it was a 1 day mission, not
+much time to chat or drink, unfortunately ). 
+But thanks for the offer, we will see next time.
+
+-- 
+Michael Scherer
+
+
+ + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000078.html b/zarb-ml/mageia-sysadm/2010-October/000078.html new file mode 100644 index 000000000..3be6a5ccf --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000078.html @@ -0,0 +1,78 @@ + + + + [Mageia-sysadm] planning advance of the night + + + + + + + + + +

[Mageia-sysadm] planning advance of the night

+ Michael Scherer + misc at zarb.org +
+ Wed Oct 27 02:27:11 CEST 2010 +

+
+ +
Hi,
+
+so, we know have a working ( or I hope so ) DNS master on alamut and a
+slave on krampouezh, for mageia.org and mageia.fr zones. 
+
+I copied the file from zarb.org, I only need to check the dns
+replication on  krampouezh, and to move the NS from zarb to here ( but
+tomorrow, because as you may see by looking at the svn history, I was
+not really at my best tonight ). The module could likely be improved,
+but I am not fluent enough with the syntax to achieve what I really
+want :/
+
+I have also added ntp synchronisation ( and removed my timezone module
+as it was not working ). 
+-- 
+Michael Scherer
+
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000079.html b/zarb-ml/mageia-sysadm/2010-October/000079.html new file mode 100644 index 000000000..c73dd4e20 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000079.html @@ -0,0 +1,105 @@ + + + + [Mageia-sysadm] Setting up primary mirror + + + + + + + + + +

[Mageia-sysadm] Setting up primary mirror

+ Olivier Thauvin + nanardon at nanardon.zarb.org +
+ Wed Oct 27 02:51:01 CEST 2010 +

+
+ +
Hi,
+
+A summary of this long evening.
+
+We have to start anyway, so I started on valstar.
+
+I did setup the mirror tree here:
+/distrib/mirror
+on a logical volume (distrib) of 1GB mount here:
+/distrib
+
+This tree can be modified in several ways: mount -o bind, ln -s, change
+directory name...
+
+With misc's help I commit everything to allow valstar to be primary
+mirror:
+- a dedicated user "mirror" for the global tree, currently in
+  /etc/passwd but I think this user must go into ldap for nfs share. If
+uid need to be changed, no problem, I'll chown everything. Also if Bs
+have its own user, this is not a problem to chown some part of the tree.
+- rsyncd config, setup from puppet (rsyncd.conf, xinetd)
+- a cron job to update time_stamp file (this file allow to check how a
+  mirror is updated).
+
+At time haven't changed the CNAME to point rsync.mageia.org on valstar,
+but the setup is ready.
+
+Comments welcome of course.
+
+Regards.
+
+-- 
+
+Olivier Thauvin
+CNRS  -  LATMOS
+♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 197 bytes
+Desc: not available
+URL: </pipermail/mageia-sysadm/attachments/20101027/12fa7b23/attachment.asc>
+
+ + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000080.html b/zarb-ml/mageia-sysadm/2010-October/000080.html new file mode 100644 index 000000000..2341a54ed --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000080.html @@ -0,0 +1,85 @@ + + + + [Mageia-sysadm] planning advance of the night + + + + + + + + + +

[Mageia-sysadm] planning advance of the night

+ Damien Lallement + mageia at damsweb.net +
+ Wed Oct 27 14:43:27 CEST 2010 +

+
+ +
Le 27/10/2010 02:27, Michael Scherer a écrit :
+> Hi,
+>
+> so, we know have a working ( or I hope so ) DNS master on alamut and a
+> slave on krampouezh, for mageia.org and mageia.fr zones.
+>
+> I copied the file from zarb.org, I only need to check the dns
+> replication on  krampouezh, and to move the NS from zarb to here ( but
+> tomorrow, because as you may see by looking at the svn history, I was
+> not really at my best tonight ). The module could likely be improved,
+> but I am not fluent enough with the syntax to achieve what I really
+> want :/
+
+Great
+
+> I have also added ntp synchronisation ( and removed my timezone module
+> as it was not working ).
+
+Erm... Are you sure? :-)
+I have added ntp synchronisation on all servers on monday...
+-- 
+Damien Lallement
+aka "damsweb" or "coincoin" on IRC and twitter
+
+http://www.mageia.org
+
+ + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000081.html b/zarb-ml/mageia-sysadm/2010-October/000081.html new file mode 100644 index 000000000..e55b9c474 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000081.html @@ -0,0 +1,75 @@ + + + + [Mageia-sysadm] planning advance of the night + + + + + + + + + +

[Mageia-sysadm] planning advance of the night

+ Michael Scherer + misc at zarb.org +
+ Wed Oct 27 14:55:37 CEST 2010 +

+
+ +
Le mercredi 27 octobre 2010 à 14:43 +0200, Damien Lallement a écrit :
+
+> > I have also added ntp synchronisation ( and removed my timezone module
+> > as it was not working ).
+> 
+> Erm... Are you sure? :-)
+> I have added ntp synchronisation on all servers on monday...
+
+Yeah, added this in puppet, I was not clear, sorry.
+( ie, if we install a new server, we will get it by default once we add
+it to puppet ).
+
+
+-- 
+Michael Scherer
+
+
+ + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000082.html b/zarb-ml/mageia-sysadm/2010-October/000082.html new file mode 100644 index 000000000..8b8f6af61 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000082.html @@ -0,0 +1,71 @@ + + + + [Mageia-sysadm] ssh keys + + + + + + + + + +

[Mageia-sysadm] ssh keys

+ nicolas vigier + boklm at mars-attacks.org +
+ Wed Oct 27 15:00:32 CEST 2010 +

+
+ +
On Mon, 25 Oct 2010, Michael Scherer wrote:
+
+> Hi fellow admins,
+> 
+> In order to let you rui^W crash^W manage the server like I did, I need
+> your ssh keys to be sent here.
+
+Ok, my ssh key.
+
+Thanks
+Nicolas
+
+-------------- next part --------------
+ssh-dss AAAAB3NzaC1kc3MAAACBAIGfoferrHXi7m8Hw3wY3HzIvWzlBKRu4aUpOjFgFTw+aPiS842F8B2bqjzUyLVAv13zHB5QjVeAB0YQ1TvMQbew+7CRAgAVWrY/ckMJxSdNk6eKnxlnLA295xBnyc+jdMhdTKisywtlkLP6Au+2eA/sDKELO8tiIQzSUithppU/AAAAFQCP/IlvpJjhxQwgA4UW1Mg7W3MPVwAAAIAc8BA7W9qDaA8/sQiOu6sSueEVnf7QmJzTJuT0ZJ9HDSB39+fQrwjPZqxiTpAfSboBTC0KiuG9ncCZyh6fAmn2i9WSZ6HYkoLBjHU3nu3u18qlT8LqwajUjgp15jgUKWB8OxvO1dPNaLEsvP1BKPTfDoPNPeUeQmb3WaX9S+pVGwAAAIA63gRktdobLeeuRFAfPdQQ7Imi1GwrfKa2QUgowksDxwgBBo796HN41+yF0W2AOZ2lx25KQRF0Wgc5Abm/TV8u3WbzosYbZgUBiGDqyVhIPU/xF+yPEHPYx3G3nwjEZAaxxf+LaeZkY1Yp15O6NAZAzdyV00iG/tO/ciWBPCMeJA== boklm at shinagawa
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000083.html b/zarb-ml/mageia-sysadm/2010-October/000083.html new file mode 100644 index 000000000..c4be54194 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000083.html @@ -0,0 +1,86 @@ + + + + [Mageia-sysadm] ssh keys + + + + + + + + + +

[Mageia-sysadm] ssh keys

+ Cazzaniga-Sandro + cazzaniga.sandro at gmail.com +
+ Wed Oct 27 15:37:50 CEST 2010 +

+
+ +
On Wed, Oct 27, 2010 at 03:00:32PM +0200, nicolas vigier wrote:
+> On Mon, 25 Oct 2010, Michael Scherer wrote:
+> 
+> > Hi fellow admins,
+> > 
+> > In order to let you rui^W crash^W manage the server like I did, I need
+> > your ssh keys to be sent here.
+> 
+> Ok, my ssh key.
+> 
+> Thanks
+> Nicolas
+> 
+
+> ssh-dss AAAAB3NzaC1kc3MAAACBAIGfoferrHXi7m8Hw3wY3HzIvWzlBKRu4aUpOjFgFTw+aPiS842F8B2bqjzUyLVAv13zHB5QjVeAB0YQ1TvMQbew+7CRAgAVWrY/ckMJxSdNk6eKnxlnLA295xBnyc+jdMhdTKisywtlkLP6Au+2eA/sDKELO8tiIQzSUithppU/AAAAFQCP/IlvpJjhxQwgA4UW1Mg7W3MPVwAAAIAc8BA7W9qDaA8/sQiOu6sSueEVnf7QmJzTJuT0ZJ9HDSB39+fQrwjPZqxiTpAfSboBTC0KiuG9ncCZyh6fAmn2i9WSZ6HYkoLBjHU3nu3u18qlT8LqwajUjgp15jgUKWB8OxvO1dPNaLEsvP1BKPTfDoPNPeUeQmb3WaX9S+pVGwAAAIA63gRktdobLeeuRFAfPdQQ7Imi1GwrfKa2QUgowksDxwgBBo796HN41+yF0W2AOZ2lx25KQRF0Wgc5Abm/TV8u3WbzosYbZgUBiGDqyVhIPU/xF+yPEHPYx3G3nwjEZAaxxf+LaeZkY1Yp15O6NAZAzdyV00iG/tO/ciWBPCMeJA== boklm at shinagawa
+
+> _______________________________________________
+> Mageia-sysadm mailing list
+> Mageia-sysadm at mageia.org
+> https://www.mageia.org/mailman/listinfo/mageia-sysadm
+
+We need to re-send our ssh key ? :)
+-- 
+Sandro Cazzaniga
+Bashburn hacker (http://bashburn.dose.se/)
+Mageia Contributor (http://www.mageia.org/fr/)
+Serial Blogger (http://twitter.com/Kharec)
+Developer (Perl, Bash, C)
+Vice President, secretary and member of CA of Alolise (http://www.alolise.org)
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000084.html b/zarb-ml/mageia-sysadm/2010-October/000084.html new file mode 100644 index 000000000..f9fc30b03 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000084.html @@ -0,0 +1,67 @@ + + + + [Mageia-sysadm] ssh keys + + + + + + + + + +

[Mageia-sysadm] ssh keys

+ Michael Scherer + misc at zarb.org +
+ Wed Oct 27 15:50:23 CEST 2010 +

+
+ +
Le mercredi 27 octobre 2010 à 15:37 +0200, Cazzaniga-Sandro a écrit :
+
+> We need to re-send our ssh key ? :)
+
+Only if you are a admin, or I would have contacted all packagers, and
+made a announce for that.
+
+
+-- 
+Michael Scherer
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000085.html b/zarb-ml/mageia-sysadm/2010-October/000085.html new file mode 100644 index 000000000..1eca39576 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000085.html @@ -0,0 +1,59 @@ + + + + [Mageia-sysadm] [40] - config file of bind need to be inside the chroot, not outside + + + + + + + + + +

[Mageia-sysadm] [40] - config file of bind need to be inside the chroot, not outside

+ root at mageia.org + root at mageia.org +
+ Wed Oct 27 17:11:13 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101027/eaf7d3e1/attachment.html>
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000086.html b/zarb-ml/mageia-sysadm/2010-October/000086.html new file mode 100644 index 000000000..4c88ebd37 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000086.html @@ -0,0 +1,59 @@ + + + + [Mageia-sysadm] [41] - fix wrong filename + + + + + + + + + +

[Mageia-sysadm] [41] - fix wrong filename

+ root at mageia.org + root at mageia.org +
+ Wed Oct 27 17:13:51 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101027/0293538e/attachment.html>
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000087.html b/zarb-ml/mageia-sysadm/2010-October/000087.html new file mode 100644 index 000000000..2845846e0 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000087.html @@ -0,0 +1,59 @@ + + + + [Mageia-sysadm] [42] - fix the filename here too + + + + + + + + + +

[Mageia-sysadm] [42] - fix the filename here too

+ root at mageia.org + root at mageia.org +
+ Wed Oct 27 17:20:29 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101027/a6d2cc3e/attachment-0001.html>
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000088.html b/zarb-ml/mageia-sysadm/2010-October/000088.html new file mode 100644 index 000000000..1cd581b43 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000088.html @@ -0,0 +1,59 @@ + + + + [Mageia-sysadm] [43] - fix missing comma + + + + + + + + + +

[Mageia-sysadm] [43] - fix missing comma

+ root at mageia.org + root at mageia.org +
+ Wed Oct 27 17:21:48 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101027/72336b70/attachment.html>
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000089.html b/zarb-ml/mageia-sysadm/2010-October/000089.html new file mode 100644 index 000000000..8eea81dfb --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000089.html @@ -0,0 +1,59 @@ + + + + [Mageia-sysadm] [44] - correctly manage timezone on server + + + + + + + + + +

[Mageia-sysadm] [44] - correctly manage timezone on server

+ root at mageia.org + root at mageia.org +
+ Wed Oct 27 17:51:23 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101027/7954e5f3/attachment.html>
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000090.html b/zarb-ml/mageia-sysadm/2010-October/000090.html new file mode 100644 index 000000000..8d4f249c7 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000090.html @@ -0,0 +1,59 @@ + + + + [Mageia-sysadm] [45] - convert the cronjob to the native cron type + + + + + + + + + +

[Mageia-sysadm] [45] - convert the cronjob to the native cron type

+ root at mageia.org + root at mageia.org +
+ Wed Oct 27 18:01:48 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101027/9d89d22d/attachment.html>
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000091.html b/zarb-ml/mageia-sysadm/2010-October/000091.html new file mode 100644 index 000000000..a5611da9d --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000091.html @@ -0,0 +1,59 @@ + + + + [Mageia-sysadm] [46] - remove file now that I checked that the cron job is ok + + + + + + + + + +

[Mageia-sysadm] [46] - remove file now that I checked that the cron job is ok

+ root at mageia.org + root at mageia.org +
+ Wed Oct 27 18:05:05 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101027/41c50d80/attachment.html>
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000092.html b/zarb-ml/mageia-sysadm/2010-October/000092.html new file mode 100644 index 000000000..2d49d76e2 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000092.html @@ -0,0 +1,59 @@ + + + + [Mageia-sysadm] [47] - fix the configuration file ( guess next time, I will go to sleep instead of working during the night ) + + + + + + + + + +

[Mageia-sysadm] [47] - fix the configuration file ( guess next time, I will go to sleep instead of working during the night )

+ root at mageia.org + root at mageia.org +
+ Wed Oct 27 18:26:51 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101027/9f04d912/attachment-0001.html>
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000093.html b/zarb-ml/mageia-sysadm/2010-October/000093.html new file mode 100644 index 000000000..a6daa1979 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000093.html @@ -0,0 +1,59 @@ + + + + [Mageia-sysadm] [48] - subtle fix for puppet on 2010.0, that will use service rather the initscript ( on krampouezh ) + + + + + + + + + +

[Mageia-sysadm] [48] - subtle fix for puppet on 2010.0, that will use service rather the initscript ( on krampouezh )

+ root at mageia.org + root at mageia.org +
+ Wed Oct 27 18:40:57 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101027/2ef8567e/attachment.html>
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000094.html b/zarb-ml/mageia-sysadm/2010-October/000094.html new file mode 100644 index 000000000..8726ca5b5 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000094.html @@ -0,0 +1,59 @@ + + + + [Mageia-sysadm] [49] add list of things to setup + + + + + + + + + +

[Mageia-sysadm] [49] add list of things to setup

+ root at mageia.org + root at mageia.org +
+ Thu Oct 28 16:32:40 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101028/89dcc34c/attachment.html>
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000095.html b/zarb-ml/mageia-sysadm/2010-October/000095.html new file mode 100644 index 000000000..582a66ce9 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000095.html @@ -0,0 +1,59 @@ + + + + [Mageia-sysadm] [50] add transiflex on alamut (thanks @damsweb for noticing) + + + + + + + + + +

[Mageia-sysadm] [50] add transiflex on alamut (thanks @damsweb for noticing)

+ root at mageia.org + root at mageia.org +
+ Thu Oct 28 17:07:53 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101028/169edb31/attachment.html>
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000096.html b/zarb-ml/mageia-sysadm/2010-October/000096.html new file mode 100644 index 000000000..7a2f4e4e4 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000096.html @@ -0,0 +1,95 @@ + + + + [Mageia-sysadm] list of things to do + + + + + + + + + +

[Mageia-sysadm] list of things to do

+ nicolas vigier + boklm at mars-attacks.org +
+ Thu Oct 28 18:38:27 CEST 2010 +

+
+ +
Hello,
+
+We now have puppet running on the servers thanks to misc.
+
+You can checkout the puppet configuration in svn+ssh://svn.mageia.org/svn/adm/puppet
+(or svn://svn.mageia.org/adm/puppet for anonymous acces).
+
+In puppet/manifests/nodes.pp you can see the list of services that need
+to be configured.
+
+Now we need to see who wants to work on which services.
+
+- LDAP servers and web interface
+   Buchan setup a test server on the gandi VM and developed a web
+   interface. misc plans to work on the setup tomorrow, and I can help
+   too.
+
+- Build system (urli scheduler, youri, iurt on build nodes etc ...)
+   boklm, blino, misc, others ?
+
+- mirror
+   Nanar
+
+- bugzilla
+- mail server (primary and secondary mx)
+- mailing lists server
+- transifex
+- mageia.org web site and blogs
+- pastebin
+- wiki (we need to discuss which software to use)
+- Nagios (and/or other monitoring software)
+
+So, who wants to work on which parts ?
+
+Nicolas
+
+
+ + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000097.html b/zarb-ml/mageia-sysadm/2010-October/000097.html new file mode 100644 index 000000000..b19672378 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000097.html @@ -0,0 +1,65 @@ + + + + [Mageia-sysadm] [52] add SQL server in TODO list + + + + + + + + + +

[Mageia-sysadm] [52] add SQL server in TODO list

+ root at mageia.org + root at mageia.org +
+ Thu Oct 28 18:47:50 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101028/d3955bee/attachment.html>
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000098.html b/zarb-ml/mageia-sysadm/2010-October/000098.html new file mode 100644 index 000000000..ad3118463 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000098.html @@ -0,0 +1,62 @@ + + + + [Mageia-sysadm] [51] - allow ibiblio to reach mageia share + + + + + + + + + +

[Mageia-sysadm] [51] - allow ibiblio to reach mageia share

+ root at mageia.org + root at mageia.org +
+ Thu Oct 28 18:44:05 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101028/bf0794d6/attachment-0001.html>
+
+ + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000099.html b/zarb-ml/mageia-sysadm/2010-October/000099.html new file mode 100644 index 000000000..d06bcbb05 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000099.html @@ -0,0 +1,75 @@ + + + + [Mageia-sysadm] SQL Server + + + + + + + + + +

[Mageia-sysadm] SQL Server

+ nicolas vigier + boklm at mars-attacks.org +
+ Thu Oct 28 19:02:12 CEST 2010 +

+
+ +
We will need an SQL server for bugzilla, the packages maintainers
+database, the wiki, the blogs, the mageia.org website (not now, but
+maybe later), sympa mailing lists, transifex, and maybe others tools
+later.
+
+We can use MySQL (or forks), PostreSQL, or both.
+
+One server for everything, or multiple servers.
+
+Any ideas about this ?
+
+Nicolas
+
+
+ + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000100.html b/zarb-ml/mageia-sysadm/2010-October/000100.html new file mode 100644 index 000000000..d01f53b75 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000100.html @@ -0,0 +1,129 @@ + + + + [Mageia-sysadm] list of things to do + + + + + + + + + +

[Mageia-sysadm] list of things to do

+ Michael Scherer + misc at zarb.org +
+ Thu Oct 28 19:07:22 CEST 2010 +

+
+ +
Le jeudi 28 octobre 2010 à 18:38 +0200, nicolas vigier a écrit :
+> Hello,
+> 
+> We now have puppet running on the servers thanks to misc.
+> 
+> You can checkout the puppet configuration in svn+ssh://svn.mageia.org/svn/adm/puppet
+> (or svn://svn.mageia.org/adm/puppet for anonymous acces).
+> 
+> In puppet/manifests/nodes.pp you can see the list of services that need
+> to be configured.
+> 
+> Now we need to see who wants to work on which services.
+> 
+> - LDAP servers and web interface
+>    Buchan setup a test server on the gandi VM and developed a web
+>    interface. misc plans to work on the setup tomorrow, and I can help
+>    too.
+> 
+> - Build system (urli scheduler, youri, iurt on build nodes etc ...)
+>    boklm, blino, misc, others ?
+> 
+> - mirror
+>    Nanar
+
+- epoll
+  -> nanar 
+
+- svn ( ie, moving them to valstar, and also set proper and decent hook,
+like checking what is commited, send mail, etc, etc ).
+
+
+> - bugzilla
+this includes also trying to import bug from mandriva, or something like
+that, and ldap integration.
+
+> - mail server (primary and secondary mx)
+I can take this part.
+
+> - mailing lists server
+-> sympa, or ennael will kill us :)
+
+> - transifex
+transifex requires a rpm, most packages are in cooker, there is just one
+or two rpm to take from fedora ( with transifex ). Transifex being a
+django application, this can be tricky to deploy. I suggest to use wsgi,
+as :
+1) cgi is slow
+2) mod_python is deprecated ( unfortunatly )
+3) fast-cgi with apache is too complex. 
+
+I do not plan to do it soon, but I can give a hand on this, or do it if
+no one do it before me.
+
+> - mageia.org web site and blogs
+this requires working with webteam, so see with rda for details
+
+> - pastebin
+personnaly, I do not think it is a high priority task at the moment, and
+beware, there is almost nothing packaged ( not even distributed I
+think ), yet there is various requirement ( mostly antispam related ).
+
+
+> - wiki (we need to discuss which software to use)
+this is a task that was given to ennael and mrTom, according to last
+meeting
+( http://meetbot.mageia.org/mageia-meeting/2010/mageia-meeting.2010-10-25-18.35.html )
+
+> - Nagios (and/or other monitoring software)
+
+-- 
+Michael Scherer
+
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000101.html b/zarb-ml/mageia-sysadm/2010-October/000101.html new file mode 100644 index 000000000..d189765d8 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000101.html @@ -0,0 +1,114 @@ + + + + [Mageia-sysadm] SQL Server + + + + + + + + + +

[Mageia-sysadm] SQL Server

+ Michael Scherer + misc at zarb.org +
+ Thu Oct 28 19:30:05 CEST 2010 +

+
+ +
Le jeudi 28 octobre 2010 à 19:02 +0200, nicolas vigier a écrit :
+> We will need an SQL server for bugzilla, the packages maintainers
+> database, the wiki, the blogs, the mageia.org website (not now, but
+> maybe later), sympa mailing lists, transifex, and maybe others tools
+> later.
+> 
+> We can use MySQL (or forks), PostreSQL, or both.
+
+Both.
+
+bugzilla use mysql or postgresql
+
+package db ( if we reuse the one of mandriva ) use mysql
+
+wiki not decided yet
+
+blog use wordpress, so mysql ( postgresql is still experimental )
+
+sympa can use both ( or even anything supported by dbi such as
+http://search.cpan.org/~rehsack/DBD-AnyData-0.110/lib/DBD/AnyData.pm )
+
+epoll requires postgresql.
+
+our current perl webapp, catdap and mga::mirror requires postgresql.
+
+transifex, being in django support mysql or postgresql
+http://docs.djangoproject.com/en/dev/ref/databases/ 
+( or sqlite or firebird )
+
+so we have a majority of database agnostic tools, except a few one that
+requires each their own. 
+
+Given the activity around mysql and forks, wouldn't it be safer for us
+to use postgresql when possible for the moment ?
+( not that I think it will change much, IMHO, even if nanar will say me
+that postgresql >> mysql )
+
+> One server for everything, or multiple servers.
+
+I would go for :
+
+one postgresql sql server for bugzilla, sympa, epoll transflex, on
+alamut or valstar ( since everything will be in local network )
+
+one mysql db for maintainers and maybe others when they appear.
+
+one separated mysql db for web ( blog ) on the next gandi vm ( so there
+is no lag )
+
+-- 
+Michael Scherer
+
+
+ + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000102.html b/zarb-ml/mageia-sysadm/2010-October/000102.html new file mode 100644 index 000000000..318f22f42 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000102.html @@ -0,0 +1,78 @@ + + + + [Mageia-sysadm] [51] - allow ibiblio to reach mageia share + + + + + + + + + +

[Mageia-sysadm] [51] - allow ibiblio to reach mageia share

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Thu Oct 28 21:05:09 CEST 2010 +

+
+ +
On 28 October 2010 18:44,  <root at mageia.org> wrote:
+> - allow ibiblio to reach mageia share
+
+(...)
+
+> --- puppet/modules/rsyncd/templates/rsyncd.conf	2010-10-28 15:07:52 UTC (rev
+> 50)
+> +++ puppet/modules/rsyncd/templates/rsyncd.conf	2010-10-28 16:44:05 UTC (rev
+> 51)
+> @@ -10,3 +10,6 @@
+>          distrib-coffee.ipsl.jussieu.fr \
+>          distribipsl.aero.jussieu.fr \
+>          ibiblio.org \
+> +        152.46.7.122 \
+> +        152.19.134.16 \
+> +
+
+This is dirt
+Cannot they have DNS names for those?
+
+ + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000103.html b/zarb-ml/mageia-sysadm/2010-October/000103.html new file mode 100644 index 000000000..6d45bc66a --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000103.html @@ -0,0 +1,102 @@ + + + + [Mageia-sysadm] [51] - allow ibiblio to reach mageia share + + + + + + + + + +

[Mageia-sysadm] [51] - allow ibiblio to reach mageia share

+ Olivier Thauvin + nanardon at nanardon.zarb.org +
+ Thu Oct 28 23:40:10 CEST 2010 +

+
+ +
* Thierry Vignaud (thierry.vignaud at gmail.com) wrote:
+> On 28 October 2010 18:44,  <root at mageia.org> wrote:
+> > - allow ibiblio to reach mageia share
+> 
+> (...)
+> 
+> > --- puppet/modules/rsyncd/templates/rsyncd.conf	2010-10-28 15:07:52 UTC (rev
+> > 50)
+> > +++ puppet/modules/rsyncd/templates/rsyncd.conf	2010-10-28 16:44:05 UTC (rev
+> > 51)
+> > @@ -10,3 +10,6 @@
+> >          distrib-coffee.ipsl.jussieu.fr \
+> >          distribipsl.aero.jussieu.fr \
+> >          ibiblio.org \
+> > +        152.46.7.122 \
+> > +        152.19.134.16 \
+> > +
+> 
+> This is dirt
+> Cannot they have DNS names for those?
+
+This is the information given by ibiblio. first IP is current server,
+second is futur IP.
+
+I agree hostname would be better, except they change their DNS.
+
+I tried to be quick to have this setup ASAP.
+
+> _______________________________________________
+> Mageia-sysadm mailing list
+> Mageia-sysadm at mageia.org
+> https://www.mageia.org/mailman/listinfo/mageia-sysadm
+-- 
+
+Olivier Thauvin
+CNRS  -  LATMOS
+♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 197 bytes
+Desc: not available
+URL: </pipermail/mageia-sysadm/attachments/20101028/91a9e55f/attachment.asc>
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000104.html b/zarb-ml/mageia-sysadm/2010-October/000104.html new file mode 100644 index 000000000..918a8675c --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000104.html @@ -0,0 +1,64 @@ + + + + [Mageia-sysadm] [53] - deploy ldap with puppet on valstar + + + + + + + + + +

[Mageia-sysadm] [53] - deploy ldap with puppet on valstar

+ root at mageia.org + root at mageia.org +
+ Fri Oct 29 00:55:57 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101029/0a250102/attachment-0001.html>
+
+ + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000105.html b/zarb-ml/mageia-sysadm/2010-October/000105.html new file mode 100644 index 000000000..fc11c8724 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000105.html @@ -0,0 +1,65 @@ + + + + [Mageia-sysadm] [54] -fix templates naming + + + + + + + + + +

[Mageia-sysadm] [54] -fix templates naming

+ root at mageia.org + root at mageia.org +
+ Fri Oct 29 01:27:31 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101029/3c45a862/attachment.html>
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000106.html b/zarb-ml/mageia-sysadm/2010-October/000106.html new file mode 100644 index 000000000..6f4b8e8ed --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000106.html @@ -0,0 +1,65 @@ + + + + [Mageia-sysadm] [55] - add postgresql config + + + + + + + + + +

[Mageia-sysadm] [55] - add postgresql config

+ root at mageia.org + root at mageia.org +
+ Fri Oct 29 01:41:31 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101029/534f63e7/attachment-0001.html>
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000107.html b/zarb-ml/mageia-sysadm/2010-October/000107.html new file mode 100644 index 000000000..0ce24a473 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000107.html @@ -0,0 +1,65 @@ + + + + [Mageia-sysadm] [56] - typo + + + + + + + + + +

[Mageia-sysadm] [56] - typo

+ root at mageia.org + root at mageia.org +
+ Fri Oct 29 01:43:45 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101029/6561f43c/attachment.html>
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000108.html b/zarb-ml/mageia-sysadm/2010-October/000108.html new file mode 100644 index 000000000..c00144ffc --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000108.html @@ -0,0 +1,65 @@ + + + + [Mageia-sysadm] [57] - typo + + + + + + + + + +

[Mageia-sysadm] [57] - typo

+ root at mageia.org + root at mageia.org +
+ Fri Oct 29 01:50:01 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101029/181142ec/attachment.html>
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000109.html b/zarb-ml/mageia-sysadm/2010-October/000109.html new file mode 100644 index 000000000..4c8dbe0da --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000109.html @@ -0,0 +1,65 @@ + + + + [Mageia-sysadm] [58] - typo + + + + + + + + + +

[Mageia-sysadm] [58] - typo

+ root at mageia.org + root at mageia.org +
+ Fri Oct 29 01:50:45 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101029/2a768e17/attachment.html>
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000110.html b/zarb-ml/mageia-sysadm/2010-October/000110.html new file mode 100644 index 000000000..1775780a4 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000110.html @@ -0,0 +1,65 @@ + + + + [Mageia-sysadm] [59] - typo + + + + + + + + + +

[Mageia-sysadm] [59] - typo

+ root at mageia.org + root at mageia.org +
+ Fri Oct 29 01:51:18 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101029/4969ecb2/attachment.html>
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000111.html b/zarb-ml/mageia-sysadm/2010-October/000111.html new file mode 100644 index 000000000..cf6cb4e50 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000111.html @@ -0,0 +1,65 @@ + + + + [Mageia-sysadm] [60] - add login management to postgresql + + + + + + + + + +

[Mageia-sysadm] [60] - add login management to postgresql

+ root at mageia.org + root at mageia.org +
+ Fri Oct 29 01:59:20 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101029/89afaba1/attachment-0001.html>
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000112.html b/zarb-ml/mageia-sysadm/2010-October/000112.html new file mode 100644 index 000000000..3c9a9c140 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000112.html @@ -0,0 +1,65 @@ + + + + [Mageia-sysadm] [61] - enable ssl + + + + + + + + + +

[Mageia-sysadm] [61] - enable ssl

+ root at mageia.org + root at mageia.org +
+ Fri Oct 29 02:38:08 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101029/0d388268/attachment.html>
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000113.html b/zarb-ml/mageia-sysadm/2010-October/000113.html new file mode 100644 index 000000000..49bc48c49 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000113.html @@ -0,0 +1,65 @@ + + + + [Mageia-sysadm] [62] - fix the config file so it work on x86_64 and x86 + + + + + + + + + +

[Mageia-sysadm] [62] - fix the config file so it work on x86_64 and x86

+ root at mageia.org + root at mageia.org +
+ Fri Oct 29 02:40:37 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101029/30bdaa9a/attachment.html>
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000114.html b/zarb-ml/mageia-sysadm/2010-October/000114.html new file mode 100644 index 000000000..cb70505cc --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000114.html @@ -0,0 +1,65 @@ + + + + [Mageia-sysadm] [63] - add ldap config file, with ldap restricted to localhost ( until we set a firewall or stricter acl) + + + + + + + + + +

[Mageia-sysadm] [63] - add ldap config file, with ldap restricted to localhost ( until we set a firewall or stricter acl)

+ root at mageia.org + root at mageia.org +
+ Fri Oct 29 03:05:58 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101029/3d892885/attachment.html>
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000115.html b/zarb-ml/mageia-sysadm/2010-October/000115.html new file mode 100644 index 000000000..e64775fea --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000115.html @@ -0,0 +1,65 @@ + + + + [Mageia-sysadm] [64] - allow epoll user to connect locally to epoll db + + + + + + + + + +

[Mageia-sysadm] [64] - allow epoll user to connect locally to epoll db

+ root at mageia.org + root at mageia.org +
+ Fri Oct 29 03:12:24 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101029/373a5efb/attachment-0001.html>
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000116.html b/zarb-ml/mageia-sysadm/2010-October/000116.html new file mode 100644 index 000000000..3b77a70df --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000116.html @@ -0,0 +1,65 @@ + + + + [Mageia-sysadm] [65] - sync with change at zarb ( ldap, ns ) + + + + + + + + + +

[Mageia-sysadm] [65] - sync with change at zarb ( ldap, ns )

+ root at mageia.org + root at mageia.org +
+ Fri Oct 29 03:18:06 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101029/cd653f71/attachment.html>
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000117.html b/zarb-ml/mageia-sysadm/2010-October/000117.html new file mode 100644 index 000000000..e200e5932 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000117.html @@ -0,0 +1,87 @@ + + + + [Mageia-sysadm] [53] - deploy ldap with puppet on valstar -- html mail + + + + + + + + + +

[Mageia-sysadm] [53] - deploy ldap with puppet on valstar -- html mail

+ Remco Rijnders + remco at webconquest.com +
+ Fri Oct 29 03:15:19 CEST 2010 +

+
+ +
On Fri, Oct 29, 2010 at 12:55:57AM +0200, root at mageia.org wrote:
+> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
+> "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
+> <html xmlns="http://www.w3.org/1999/xhtml">
+> <head><meta http-equiv="content-type" content="text/html; charset=utf-8" />
+> <title>[53] - deploy ldap with puppet on valstar</title>
+<snip>
+
+For those of us reading mail with a mail client that doesn't handle
+HTML-only mail very gracefully out of the box (pine, mutt for example), it
+would be nice if these svn (?) notifications would be sent as text only or
+would at least have a text only representation in the mail.
+
+I imagine there are more people than just me who'd find this useful as the
+current mails are almost unreadable to us.
+
+Thanks :-)
+
+Remco
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 197 bytes
+Desc: Digital signature
+URL: </pipermail/mageia-sysadm/attachments/20101029/e266393a/attachment.asc>
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000118.html b/zarb-ml/mageia-sysadm/2010-October/000118.html new file mode 100644 index 000000000..38aacd154 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000118.html @@ -0,0 +1,64 @@ + + + + [Mageia-sysadm] [66] - check postgres is running + + + + + + + + + +

[Mageia-sysadm] [66] - check postgres is running

+ root at mageia.org + root at mageia.org +
+ Fri Oct 29 03:22:43 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101029/225b43fb/attachment.html>
+
+ + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000119.html b/zarb-ml/mageia-sysadm/2010-October/000119.html new file mode 100644 index 000000000..2446995c8 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000119.html @@ -0,0 +1,64 @@ + + + + [Mageia-sysadm] [67] - typo + + + + + + + + + +

[Mageia-sysadm] [67] - typo

+ root at mageia.org + root at mageia.org +
+ Fri Oct 29 03:23:27 CEST 2010 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101029/d832edeb/attachment.html>
+
+ + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000120.html b/zarb-ml/mageia-sysadm/2010-October/000120.html new file mode 100644 index 000000000..749a37c38 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000120.html @@ -0,0 +1,97 @@ + + + + [Mageia-sysadm] [53] - deploy ldap with puppet on valstar -- html mail + + + + + + + + + +

[Mageia-sysadm] [53] - deploy ldap with puppet on valstar -- html mail

+ Michael Scherer + misc at zarb.org +
+ Fri Oct 29 03:56:56 CEST 2010 +

+
+ +
Le vendredi 29 octobre 2010 à 03:15 +0200, Remco Rijnders a écrit :
+> On Fri, Oct 29, 2010 at 12:55:57AM +0200, root at mageia.org wrote:
+> > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
+> > "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
+> > <html xmlns="http://www.w3.org/1999/xhtml">
+> > <head><meta http-equiv="content-type" content="text/html; charset=utf-8" />
+> > <title>[53] - deploy ldap with puppet on valstar</title>
+> <snip>
+> 
+> For those of us reading mail with a mail client that doesn't handle
+> HTML-only mail very gracefully out of the box (pine, mutt for example), it
+> would be nice if these svn (?) notifications would be sent as text only or
+> would at least have a text only representation in the mail.
+> 
+> I imagine there are more people than just me who'd find this useful as the
+> current mails are almost unreadable to us.
+
+Currently, this doesn't seems possible to have both of them with the
+current module, we are using a perl module for the post-commit hook :
+
+#!/usr/bin/perl -MSVN::Notify::Config=$0
+--- #YAML:1.0
+'':
+  PATH: "/usr/bin:/usr/local/bin"
+  handler: HTML::ColorDiff
+  with-diff: 1
+  to: mageia-sysadm at mageia.org
+  from: root at mageia.org
+
+
+But maybe using this one could do the trick : 
+http://search.cpan.org/~dwheeler/SVN-Notify-2.80/lib/SVN/Notify/Alternative.pm
+
+But for the moment, I do not have much time to test this.
+-- 
+Michael Scherer
+
+
+ + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000121.html b/zarb-ml/mageia-sysadm/2010-October/000121.html new file mode 100644 index 000000000..f89b8cb97 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000121.html @@ -0,0 +1,87 @@ + + + + [Mageia-sysadm] SQL Server + + + + + + + + + +

[Mageia-sysadm] SQL Server

+ Damien Lallement + mageia at damsweb.net +
+ Fri Oct 29 13:56:01 CEST 2010 +

+
+ +
Le 28/10/2010 19:02, nicolas vigier a écrit :
+> We will need an SQL server for bugzilla, the packages maintainers
+> database, the wiki, the blogs, the mageia.org website (not now, but
+> maybe later), sympa mailing lists, transifex, and maybe others tools
+> later.
+>
+> We can use MySQL (or forks), PostreSQL, or both.
+>
+> One server for everything, or multiple servers.
+>
+> Any ideas about this ?
+
+The SQL Server won't be used for blogs as blogs will be hosted on Gandi.
+So not on the same network.
+Perf will be quite bad if WP is on Gandi but BDD on alamut I think...
+
+Same thing for the BDD for www no?
+
+But perhaps we can dump SQL on Gandi and save it on alamut for security 
+reasons.
+
+My 2cts
+Dams
+-- 
+Damien Lallement
+aka "damsweb" or "coincoin" on IRC and twitter
+
+http://www.mageia.org
+
+ + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000122.html b/zarb-ml/mageia-sysadm/2010-October/000122.html new file mode 100644 index 000000000..7787fb057 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000122.html @@ -0,0 +1,93 @@ + + + + [Mageia-sysadm] SQL Server + + + + + + + + + +

[Mageia-sysadm] SQL Server

+ Michael Scherer + misc at zarb.org +
+ Fri Oct 29 14:17:11 CEST 2010 +

+
+ +
Le vendredi 29 octobre 2010 à 13:56 +0200, Damien Lallement a écrit :
+> Le 28/10/2010 19:02, nicolas vigier a écrit :
+> > We will need an SQL server for bugzilla, the packages maintainers
+> > database, the wiki, the blogs, the mageia.org website (not now, but
+> > maybe later), sympa mailing lists, transifex, and maybe others tools
+> > later.
+> >
+> > We can use MySQL (or forks), PostreSQL, or both.
+> >
+> > One server for everything, or multiple servers.
+> >
+> > Any ideas about this ?
+> 
+> The SQL Server won't be used for blogs as blogs will be hosted on Gandi.
+> So not on the same network.
+> Perf will be quite bad if WP is on Gandi but BDD on alamut I think...
+
+While I agree, I wonder how bad the performance hit will be in practice,
+in fact.
+Maybe we could later make a small test blog to see. 
+And the reason of using gandi was also the separation of servers, so a
+downtime of alamut do not impact the blog and www.
+
+> Same thing for the BDD for www no?
+> 
+> But perhaps we can dump SQL on Gandi and save it on alamut for security 
+> reasons.
+
+We need a sql server for epoll, for bugzilla, for maintainers db, for
+transifex and for sympa ( for the first software ).
+
+
+-- 
+Michael Scherer
+
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000123.html b/zarb-ml/mageia-sysadm/2010-October/000123.html new file mode 100644 index 000000000..0732c275d --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000123.html @@ -0,0 +1,81 @@ + + + + [Mageia-sysadm] list of things to do + + + + + + + + + +

[Mageia-sysadm] list of things to do

+ Dexter Morgan + dmorganec at gmail.com +
+ Fri Oct 29 21:19:16 CEST 2010 +

+
+ +
On Thu, Oct 28, 2010 at 6:38 PM, nicolas vigier <boklm at mars-attacks.org> wrote:
+> Hello,
+>
+> We now have puppet running on the servers thanks to misc.
+>
+> You can checkout the puppet configuration in svn+ssh://svn.mageia.org/svn/adm/puppet
+> (or svn://svn.mageia.org/adm/puppet for anonymous acces).
+>
+> In puppet/manifests/nodes.pp you can see the list of services that need
+> to be configured.
+>
+> Now we need to see who wants to work on which services.
+>
+> - LDAP servers and web interface
+>   Buchan setup a test server on the gandi VM and developed a web
+>   interface. misc plans to work on the setup tomorrow, and I can help
+>   too.
+>
+> - Build system (urli scheduler, youri, iurt on build nodes etc ...)
+>   boklm, blino, misc, others ?
+
+I can help for the BS too.
+
+what still need to be done  ?
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000124.html b/zarb-ml/mageia-sysadm/2010-October/000124.html new file mode 100644 index 000000000..9ab5c6396 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000124.html @@ -0,0 +1,77 @@ + + + + [Mageia-sysadm] ldap deployement + + + + + + + + + +

[Mageia-sysadm] ldap deployement

+ Michael Scherer + misc at zarb.org +
+ Fri Oct 29 20:45:42 CEST 2010 +

+
+ +
Hi,
+
+I have deployed ldap on the server, I will try to work on deploying
+catdap this weekend ( but I am quite busy, even if my girlfriend
+explained to me that monday was a banking holidays ).
+
+Since the application is still in flux for the moment, I will likely use
+some kind of automated svn snapshot, until we declare the application to
+be "stable". 
+
+Catalyst permit to use mod_perl, fastcgi, standalone daemon and cgi for
+deployement. Each have its pros and cons, anyone has a opinion on it ?
+
+I didn't really look in depth for the differences at the moment, but I
+will later this weekend.
+
+-- 
+Michael Scherer
+
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000125.html b/zarb-ml/mageia-sysadm/2010-October/000125.html new file mode 100644 index 000000000..b9107d771 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000125.html @@ -0,0 +1,157 @@ + + + + [Mageia-sysadm] planning for sysadmin task + + + + + + + + + +

[Mageia-sysadm] planning for sysadmin task

+ Michael Scherer + misc at zarb.org +
+ Sat Oct 30 10:55:51 CEST 2010 +

+
+ +
Le mardi 26 octobre 2010 à 16:39 +0200, Romain d'Alverny a écrit :
+> On Tue, Oct 26, 2010 at 16:06, Olivier Thauvin
+> <nanardon at nanardon.zarb.org> wrote:
+> > * Romain d'Alverny (rdalverny at gmail.com) wrote:
+> >> On Tue, Oct 26, 2010 at 15:23, Michael Scherer <misc at zarb.org> wrote:
+> >> Sysadm. Per request of webteam.
+> >>
+> >> > - setup of infrastructure ( ie apache module)
+> >>
+> >> Sysadm. Per request of webteam.
+> >>
+> >> > - who is in charge of securing
+> >> >  - the servers
+> >> >  - each applications
+> >>
+> >> Both. Server security is going to be affected by application security
+> >> and this is the webteam role to control that part. And to assume/fix
+> >> potential issues.
+> > [...]
+> > Since you prefer to not using rpm, the work to setup such application
+> > get more complicated, especially if the sys admin don't know perl (in
+> > this case, the same apply to php apps, python, etc...).
+> 
+> I know this firsthand, from both sides, yes. That's the webteam
+> responsibility to provide this info for installing/upgrading the app,
+> and that partially requires from the webteam some knowledge about the
+> system.
+> 
+> So indeed, both teams need to know/understand each other.
+> 
+> > I don't like the "svn snapshot" way for officially in use web apps. It
+> > works for testing the devel version, but I'd really hope anyone
+> > working on web apps is able to have a clear roadmap and managing branch
+> > for quick security fixes.
+> 
+> Sure. But it happens to break nonetheless. What is crucial is not that
+> there is no breach (there will), it's that it is quickly reported and
+> fixed.
+> 
+> > And since you have a stable branch and a devel one, you are able to
+> > quickly redo a rpm.
+> 
+> I understand that but a RPM is an unnecessary step here IMHO. A web
+> app/development life cycle in dev/production is not the same as one
+> for a packaged app for a distribution.
+> 
+> All I care here as a Web dev/project manager is:
+>  - working on the app
+>  - making sure it works
+>  - pushing to prod
+>  - check again
+>  - iterate.
+> 
+> Pushing deployment from dev to production, assuming all tests pass,
+> should be ideally as fast as pushing a single button and waiting for a
+> few seconds. And it may not be a trivial thing either (not just
+> pushing files, but moving the app into several states for a clean
+> migration).
+> 
+> At some extent, RPM dependencies would be a useful thing for setting
+> up the application but this mostly happens once (first install) and
+> can be easily hosted within the web application itself (and then
+> handle the error) - WordPress and Drupal do it for instance.
+
+It also prevent the removal of used dependencies. 
+This can happen either when we are cleaning the server, or when we
+upgrade the server, or another application. 
+
+If tomorrow, we discover a huge security hole in php-hugesecurityhole
+rpm, we need to know who use it to assess the security of the
+infrastructure. And without knowing what other packages use the rpm,
+this is gonna be slightly complicated to know if we are affected or not.
+
+
+> So we can discuss this further with other future webteam members but I
+> will seriously not manage a production environment that goes through
+> packaging for app updates.
+
+Well, if creating a package is just a single command ( as would be a
+upgrade to the production server ), I do not think it will be much of a
+problem. The only issue is to find someone skilled enough to create a
+shell script for that and I do not really think that it will be a big
+problem. We have a team of 8 admins and there is several volunteers
+eager to help, it would be quite weird to have no one able to do it in
+time.
+
+> That does not mean I don't care about security - that means that
+> there's a balance to find and that web developers have to be in charge
+> of their apps security as well. So if that means we need to have
+> separate servers to isolate risks, so be it. If that means we need to
+> go for a different type of hosting, so be it.
+
+Separating server do not really help much, if there is a security
+problem, it will be there wherever you are. You can reduce the impact of
+course, but that's just a consolation.  We will have work to do to be
+sure the server is clean after being audited, the reputation will be
+affected none the less, and if the server is used for
+spam/attack/whatever, we have to take care of this. 
+
+-- 
+Michael Scherer
+
+
+ + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000126.html b/zarb-ml/mageia-sysadm/2010-October/000126.html new file mode 100644 index 000000000..35ed16bf4 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000126.html @@ -0,0 +1,78 @@ + + + + [Mageia-sysadm] list of things to do + + + + + + + + + +

[Mageia-sysadm] list of things to do

+ nicolas vigier + boklm at mars-attacks.org +
+ Sun Oct 31 18:38:00 CET 2010 +

+
+ +
On Fri, 29 Oct 2010, Dexter Morgan wrote:
+
+> 
+> I can help for the BS too.
+> 
+> what still need to be done  ?
+
+What still needs to be done :
+ - package (or update package) iurt and install it on build nodes
+ - setup ssh keys to allow ssh access from valstar to build nodes, from
+   ~mageia account (or someone else has better name to replace ~mandrake
+   account ?)
+ - install youri on valstar
+ - install and package ulri
+ - select scripts from robots directory which are needed, and
+   clean/update/install them :
+   http://svn.mandriva.com/svn/soft/build_system/upload/robot/trunk/
+ - package/install BS web interface :
+   http://svn.mandriva.com/svn/soft/build_system/web/
+ - maybe other things I forget
+
+Nicolas
+
+
+ + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000127.html b/zarb-ml/mageia-sysadm/2010-October/000127.html new file mode 100644 index 000000000..e23491540 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000127.html @@ -0,0 +1,85 @@ + + + + [Mageia-sysadm] [68] valstar needs task-bs-cluster-main + + + + + + + + + +

[Mageia-sysadm] [68] valstar needs task-bs-cluster-main

+ root at mageia.org + root at mageia.org +
+ Sun Oct 31 20:35:58 CET 2010 +

+
+ +
Revision: 68
+Author:   blino
+Date:     2010-10-31 20:35:57 +0100 (Sun, 31 Oct 2010)
+Log Message:
+-----------
+valstar needs task-bs-cluster-main
+
+Modified Paths:
+--------------
+    puppet/manifests/nodes.pp
+
+Modified: puppet/manifests/nodes.pp
+===================================================================
+--- puppet/manifests/nodes.pp	2010-10-29 01:23:27 UTC (rev 67)
++++ puppet/manifests/nodes.pp	2010-10-31 19:35:57 UTC (rev 68)
+@@ -48,6 +48,10 @@
+     package {"puppet-server":
+         ensure => "installed"
+     }
++
++    package {"task-bs-cluster-main":
++        ensure => "installed"
++    }
+ }
+ 
+ # web apps
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20101031/1b50d5b5/attachment.html>
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/000128.html b/zarb-ml/mageia-sysadm/2010-October/000128.html new file mode 100644 index 000000000..ef57356a5 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/000128.html @@ -0,0 +1,84 @@ + + + + [Mageia-sysadm] About build system setup + + + + + + + + + +

[Mageia-sysadm] About build system setup

+ nicolas vigier + boklm at mars-attacks.org +
+ Sun Oct 31 21:28:41 CET 2010 +

+
+ +
Hello,
+
+After some discussions tonight with blino on IRC about build system,
+some infos :
+
+ * contrary to Mandriva build system, for better security, only admins
+   will have shell access to the build nodes and valstar. We should provide
+   Cauldron nodes for packagers to test builds, but it will be on separate
+   servers.
+
+ * to submit builds, packagers will use "mdvsys/repsys submit" from their
+   computer, or from Cauldron test nodes. mdvsys/repsys require ssh to
+   connect to valstar and run youri wrapper. We will setup a restricted
+   shell to only allow commands needed by mdvsys/repsys, and ssh/git
+   (valstar is also the svn/git server). On Mandriva svn server we used
+   this script as the default shell to restrict to only ssh/git commands :
+   http://svn.gna.org/svn/savane/trunk/backend/accounts/sv_membersh.pl
+   We can update this script to also allow commands used by mdvsys/repsys.
+
+ * On Mandriva build system we had one ~mandrake user doing everything
+   (build bots, scheduler, mirrors, sign packages ...). Now we can split
+   this to have one user for each task. We can have the following users :
+   - buildbot (to run iurt on build nodes)
+   - schedbot (youri/ulri/emi)
+   - signbot (sign packages)
+   However we already have a mirror user on valstar. Is it ok, or should
+   we rename it to "mirrorbot" ? Or remove the "bot" suffix from other
+   users ?
+
+Nicolas
+
+
+ + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2010-October/author.html b/zarb-ml/mageia-sysadm/2010-October/author.html new file mode 100644 index 000000000..2b466a5e7 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/author.html @@ -0,0 +1,687 @@ + + + + The Mageia-sysadm October 2010 Archive by author + + + + + +

October 2010 Archives by author

+ +

Starting: Fri Oct 1 03:27:02 CEST 2010
+ Ending: Sun Oct 31 21:28:41 CET 2010
+ Messages: 128

+

+

+ Last message date: + Sun Oct 31 21:28:41 CET 2010
+ Archived on: Sun Oct 31 21:28:46 CET 2010 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + diff --git a/zarb-ml/mageia-sysadm/2010-October/date.html b/zarb-ml/mageia-sysadm/2010-October/date.html new file mode 100644 index 000000000..680e77e61 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/date.html @@ -0,0 +1,687 @@ + + + + The Mageia-sysadm October 2010 Archive by date + + + + + +

October 2010 Archives by date

+ +

Starting: Fri Oct 1 03:27:02 CEST 2010
+ Ending: Sun Oct 31 21:28:41 CET 2010
+ Messages: 128

+

+

+ Last message date: + Sun Oct 31 21:28:41 CET 2010
+ Archived on: Sun Oct 31 21:28:46 CET 2010 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + diff --git a/zarb-ml/mageia-sysadm/2010-October/index.html b/zarb-ml/mageia-sysadm/2010-October/index.html new file mode 120000 index 000000000..db4b46f72 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/index.html @@ -0,0 +1 @@ +thread.html \ No newline at end of file diff --git a/zarb-ml/mageia-sysadm/2010-October/subject.html b/zarb-ml/mageia-sysadm/2010-October/subject.html new file mode 100644 index 000000000..ccc7eadec --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/subject.html @@ -0,0 +1,687 @@ + + + + The Mageia-sysadm October 2010 Archive by subject + + + + + +

October 2010 Archives by subject

+ +

Starting: Fri Oct 1 03:27:02 CEST 2010
+ Ending: Sun Oct 31 21:28:41 CET 2010
+ Messages: 128

+

+

+ Last message date: + Sun Oct 31 21:28:41 CET 2010
+ Archived on: Sun Oct 31 21:28:46 CET 2010 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + diff --git a/zarb-ml/mageia-sysadm/2010-October/thread.html b/zarb-ml/mageia-sysadm/2010-October/thread.html new file mode 100644 index 000000000..59311a3a1 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-October/thread.html @@ -0,0 +1,895 @@ + + + + The Mageia-sysadm October 2010 Archive by thread + + + + + +

October 2010 Archives by thread

+ +

Starting: Fri Oct 1 03:27:02 CEST 2010
+ Ending: Sun Oct 31 21:28:41 CET 2010
+ Messages: 128

+

+

+ Last message date: + Sun Oct 31 21:28:41 CET 2010
+ Archived on: Sun Oct 31 21:28:46 CET 2010 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + -- cgit v1.2.1