<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>en.credativ blog: Category RHEL/CentOS</title>
    <link rel="alternate" type="text/html" href="http://blog.credativ.com/en/" />
    <link rel="self" type="application/atom+xml" href="http://blog.credativ.com/en/atom.xml" />
    <id>tag:blog.credativ.com,2010-03-05:/en//2</id>
    <updated>2010-05-25T10:10:26Z</updated>
    <subtitle>All about Linux and Open Source</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.34-en</generator>

<entry>
    <title>[Howto] RHCS: install on Debian</title>
    <link rel="alternate" type="text/html" href="http://blog.credativ.com/en/2010/05/howto-rhcs-install-on-debian.html" />
    <id>tag:blog.credativ.com,2010:/en//2.148</id>

    <published>2010-05-20T10:40:00Z</published>
    <updated>2010-05-25T10:10:26Z</updated>

    <summary>Following our earlier introduction to RHCS we now present a real world example: the installation of RHCS with Debian to provide certain virtual machines as services. Our RHCS overview already explained the basics of RHCS. This time we will take...</summary>
    <author>
        <name>Roland Wolters</name>
        <uri>http://www.credativ.de</uri>
    </author>
    
        <category term="Debian" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Howto" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Linux" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Open Source" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="RHEL/CentOS" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="credativ" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://blog.credativ.com/en/">
        <![CDATA[<p><img alt="tux.jpg" src="/de/static/tux.jpg" width="86" height="102" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /><em>Following our earlier introduction to RHCS we now present a real world example: the installation of RHCS with Debian to provide certain virtual machines as services.</em></p>

<p>Our <a href="/en/2010/03/rhcs-an-introduction.html">RHCS overview</a> already explained the basics of RHCS. This time we will take two hosts with shared storage and provide KVM guests as services.</p>

<h3>Installation of the nodes</h3>
In this setup the nodes are the machines which are running KVM. Each running KVM guest is a service managed by RHCS. While installing the KVM hosts you should make sure you comply with the following suggestions:
<ul><li><tt>/tmp/</tt> and <tt>/var/</tt> should be running on different partitions, this improves performance.</li>
<li>Activate Debian backports, especially for the Kernel.</li>
<li>Make sure all IP addresses can be resolved in both directions - <tt>/etc/hosts</tt> helps here in worst case.</li>
<li>The host name must not resolve to <tt>127.0.0.1</tt>! You would only get problems with the Cluster Management System CMAN.</li>
<li><tt>/etc/hosts/</tt> and <tt>/etc/resolv.conf</tt> should be the same on all nodes.</li>
<li>Create password free ssh keys for all nodes and distribute them.</li>
<li>For ultimate performance it is best to install the latest Debian Linux kernel. In our example we used <tt>linux-image-2.6.32-bpo.2-amd64</tt>, which crashes the guest kernels >= 2.6.30. However, a patch is available, see <a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573071">bug #573071</a>.</li>
<li>The network devices should be named in a way that makes sense, for example: <tt>rhcs-backbone</tt> and <tt>external</tt> instead of <tt>eth0</tt> and <tt>eth1</tt>.</li></ul>

<h3>Configuring the shared storage</h3>
As with almost any HA solution, a key element of RHCS is the shared storage which is accessed by all the nodes. In this example we take a "private" machine and install an iSCSI target on it:
<pre class='brush: plain'>
apt-get install iscsitarget iscsitarget-source 
echo 'ISCSITARGET_ENABLE=true' &gt; /etc/default/iscsitarget
m-a a-i iscsitarget
</pre><p><br />
Keep in mind that the iSCSI target must build properly, see <a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566740">bug #566740</a>. The configuration of the shared storage is done via <tt>/etc/ietd.conf</tt>:</p>
<pre class='brush: plain'>
IncomingUser discovery_in YourSecurePwd1
OutgoingUser discovery_out YourSecurePwd2
Target YOURMACHINE:clvm1
       IncomingUser node_in YourSecurePwd1
       OutgoingUser node_out YourSecurePwd2
       Lun 0 Path=/dev/sdx1,Type=blockio
</pre><p><br />
On the nodes the same target must be accessed, so make sure <tt>/etc/iscsi/iscsid.conf</tt> is correct:</p>
<pre class='brush: plain'>
discovery.sendtargets.auth.authmethod = CHAP
discovery.sendtargets.auth.username = discovery_in
discovery.sendtargets.auth.password = YourSecurePwd1
discovery.sendtargets.auth.username_in = discovery_out
discovery.sendtargets.auth.password_in = YourSecurePwd2
node.startup = automatic
node.session.auth.authmethod = CHAP
node.session.auth.username = node_in
node.session.auth.password = YourSecurePwd1
node.session.auth.username_in = node_out
node.session.auth.password_in = YourSecurePwd2
</pre><p><br />
The service is started with <tt>/etc/init.d/open-iscsi start</tt>. Existing targets can be searched, deleted or added by the following commands:</p>
<pre class='brush: plain'>
# discovering the targets
iscsiadm -m discovery -t st -p YOURMACHINE -P 1
# deleting target on wrong interface
iscsiadm -m node -p 192.168.0.100:3260,1 -o delete
# opening the portal
iscsiadm -m node --targetname &quot;iqn.2010-03.YOURMACHINE:clvm1&quot; --portal &quot;YOURMACHINE:3260&quot; --</pre><p></p>

<h3>VM setup</h3>
The virtual machines are provided by KVM. Thus the apropriate KVM software must be installed first:
<pre class='brush: plain'>
apt-get install linux-image-2.6.32-bpo.2-amd64 kvm libvirt-bin virtinst -t lenny-backports
</pre><p><br />
When configuring the bridge, make sure that the bridge name is the same on all nodes. Also the libvirt configuration must be the same on all hosts, so it makes sense to use <a href="/en/2010/03/howto-introduction-to-puppet.html">puppet</a> or similar techniques.<br />
Afterwards, bring up the guests with:</p>
<pre class='brush: plain'>
virt-install -n &lt;NAME&gt; -r 256 --vcpus=1 --disk path=/dev/vg_cluster#/&lt;LV&gt; \
  -c /root/debian-&lt;VERSION&gt;-amd64-netinst.iso --vnc --noautoconsole --os-type linux \
  --os-variant debianLenny --accelerate --network=bridge:bridge0 --hvm -k de
</pre><p><br />
To monitor the process use <tt>virt-viewer -c qemu+ssh://<node>:<port>/system <NAME></tt>.</p>

<h3>RHCS setup</h3>
The next step is the setup of RHCS itself. Again, first things first, the software: <tt>apt-get install redhat-cluster-suite</tt>. This pulls quite a number of services which are not needed in our example:
<pre class='brush: plain'>
invoke-rc.d nfs-kernel-server stop
invoke-rc.d nfs-common stop
invoke-rc.d portmap stop
update-rc.d -f nfs-kernel-server remove
update-rc.d -f nfs-common remove
update-rc.d -f portmap remove
</pre><p><br />
Btw., <tt>system-config-cluster</tt> is not available for Lenny, but our Philipp Hübner has created a backport:</p>
<pre class='brush: plain'>
wget --no-check-certificate https://www.credativ.com/~phu/lenny-backports/system-config-cluster/system-config-cluster_1.0.53-1_all.deb
dpkg -i system-config-cluster_1.0.53-1_all.deb
apt-get -f install
apt-get install xauth
</pre><p><br />
In order to have locking on the LVM cluster, you now need to modify <tt>/etc/lvm/lvm.conf</tt>: check for the <tt>global</tt> part.</p>
<pre class='brush: plain'>
 locking_type = 3
</pre><p><br />
With the newer kernels the module <tt>lock_dlm</tt> also vanished, so CMAN init script must be modified: comment out the line <tt>modprobe lock_dlm 2>&1 || return 1</tt>. Additionally, RHCS 2 only supports XEN, so for libvirt you need to load the resource handler  <tt>vm.sh</tt>.</p>
<pre class='brush: plain'>
wget --no-check-certificate https:///www.credativ.com/~phu/vm.sh -O /usr/share/cluster/vm.sh
chmod +x /usr/share/cluster/vm.sh
</pre><p></p>

<p>RHCS itself is called via</p>
<pre class='brush: plain'>
/etc/init.d/cman start
/etc/init.d/clvm start
/etc/init.d/rgmanager start
</pre><p></p>

<h3>Fencing</h3>
Fencing describes the automagical neutralization of nodes which cease to function properly. In our example we use a power plug which can be controlled via network, NETIO-230A. Currently there is no real fence agent available for the device, but the python library <a href="http://github.com/pklaus/netio230a">Python-Bibliothek</a> offers the necessary background to quickly write one.

<h3>Closing words</h3>
This howto has shown the setup of RHCS on Debian in easy steps - but of course, the correct steps depend very much on the targeted services, so this is just an example. If you need help just ask - <a href="http://www.credativ.co.uk/services/support/projects/high-availability-clustering/">Open Source HA solutions</a> are our speciality, and <a href="http://www.credativ.co.uk/services/support/projects/virtualisation/kvm/">we offer services and support  for KVM virtualization</a> as part of our day to day business.]]>
        
    </content>
</entry>

<entry>
    <title>credativ leads the market with a pre-paid, international Open Source support solution</title>
    <link rel="alternate" type="text/html" href="http://blog.credativ.com/en/2010/03/credativ-leads-the-market-with-a-pre-paid-international-open-source-support-solution.html" />
    <id>tag:blog.credativ.com,2010:/en//2.152</id>

    <published>2010-03-24T15:30:40Z</published>
    <updated>2010-03-24T15:28:18Z</updated>

    <summary>This week, credativ launches its Open Source Support Card. With this card Open Source Support can be bought at a fixed price - without a binding contract. After a long preparation phase we are now offering our trusted services in...</summary>
    <author>
        <name>Roland Wolters</name>
        <uri>http://www.credativ.de</uri>
    </author>
    
        <category term="Debian" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Linux" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="News" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Open Source" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="RHEL/CentOS" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Support" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="credativ" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://blog.credativ.com/en/">
        <![CDATA[<p><em>This week, credativ launches its Open Source Support Card. With this card Open Source Support can be bought at a fixed price - without a binding contract.</em></p>

<p>After a long preparation phase we are now offering our trusted services in a new, simple format; with the <a href="http://www.credativ.co.uk/home/services/open-source-support-card/">Open Source Support Card</a> you get a fixed contingent of project-specific, pre-paid services.</p>

<p><a href=""><img alt="Sup_Card_front.png" src="http://blog.credativ.com/en/2010/03/24/static/front_rounded_shadow_small.png" width="350" height="210" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></a></p>

<p>Customers using the Open Source Support Card have the unique advantage of full cost control; the card can be purchased as a product, without any obligation to sign an agreement for a specific length of time. This may be of particular benefit to larger companies, where new contracts have to be reviewed and cross-reviewed before they can be authorised. A summary of the advantages of the new pre-paid support format include:</p>

<ul><li>Open Source Support for a specific project</li><li>Support not restricted to a specific number of desktops and servers within a company</li><li>A tempting price model, starting at just £480</li><li>Full control of costs</li><li>Support available via telephone, e-mail and remote access</li><li>Bilingual support - help given in English or even German, if required! ;-)</li><li>Cost of support NOT determined by the number of CPUs or users</li><li>NO binding contract - easy way to purchase</li><li>NO call centre - direct access to the experts</li><li>Support units can be used for the following services:</li><ul><li>administration</li><li>installation (remote)</li><li>consultancy</li></ul></ul>

<p>All support is provided to the usual credativ standard. Just as you would expect from our usual contracts, the cost of the service is not determined by the number of CPUs, users, or DB entries. Support units purchased through the Support Card can be used for all related problems within a company - no matter which workstation or server they come up on. The support itself is provided by our <a href="http://www.credativ.co.uk/home/services/support/">Open Source Support Centre</a>: you won't have to deal with non-technical staff or battle through FAQ scripts - our Linux experts and Open Source specialists are on hand to take calls directly. Many of us are actively involved in contributing to a number of Open Source projects - as regular readers will already be aware. ;-)</p>

<p>The new Open Source Support Card is also an exciting development for the wider Open Source community. By offering yet another attractive support option for free distributions, we hope to prove that there is now no reason not to consider Debian and CentOS as viable alternatives to commercial distributions.<br />
 <br />
The Open Source Support Card is designed and marketed in such a way that resellers can also get on board, making access to support that bit easier for consumers: imagine purchasing your server online and while you're at it being able to drop a Support Card into the shopping basket as well - Open Source Support with just one click!</p>

<p>Currently the <a href="http://www.credativ.co.uk/home/services/open-source-support-card/">Support Card</a> is just available for Debian and CentOS in the UK and in Germany, although we will soon be offering it in the US and Canada too. If you have any questions or comments we'd be pleased to hear from you - we've put a lot of effort into this new product, and are looking forward to the response from our customers and the wider community.</p>]]>
        
    </content>
</entry>

<entry>
    <title>RHCS: an Introduction</title>
    <link rel="alternate" type="text/html" href="http://blog.credativ.com/en/2010/03/rhcs-an-introduction.html" />
    <id>tag:platon.credativ.com,2010:/en//2.127</id>

    <published>2010-03-03T13:55:40Z</published>
    <updated>2010-03-05T11:08:37Z</updated>

    <summary>The Red Hat Cluster Suite is a framework to bind two or more machines together to jointly handle one task. The following article gives an introduction to RHCS in terms of service failover. Linux is used daily in mission-critical environments...</summary>
    <author>
        <name>Roland Wolters</name>
        <uri>http://www.credativ.de</uri>
    </author>
    
        <category term="Debian" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Open Source" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="RHEL/CentOS" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Support" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="credativ" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://blog.credativ.com/en/">
        <![CDATA[<p><img alt="tux.jpg" src="/en/static/tux.jpg" width="86" height="102" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /><em>The Red Hat Cluster Suite is a framework to bind two or more machines together to jointly handle one task. The following article gives an introduction to RHCS in terms of service failover.</em></p>

<p>Linux is used daily in mission-critical environments all over the world. It follows that Linux can be required to fulfil a range of needs with relation to availability and stability.  The <a href="http://www.redhat.com/cluster_suite/">Red Hat Cluster Suite</a> (RHCS) is designed with these needs in mind; it enables the admin to set up a cluster of machines which all handle the same task or provide the same service. If the machine providing the service goes down, another machine then steps in and takes over.</p>

<h3>Core elements of RHCS</h3>
RHCS consists of four core components:
<ul>	<li>cluster infrastructure</li>
	<li>high availability service management</li>
	<li>tools for the cluster administration</li>
	<li>Linux virtual server routing</li></ul>
The <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.4/html/Cluster_Suite_Overview/s1-hasci-overview-CSO.html">cluster infrastructure</a> includes all the core components necessary for the set up and running of a cluster of several nodes. These components manage the integration of nodes, shutting them down where problems occur (fencing), replicating the configuration and so on.

<p>After the cluster has been set up the next step is to define the <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.4/html/Cluster_Suite_Overview/s1-service-management-overview-CSO.html">high availability service management</a>. This is a service running on one node with other nodes configured for failover. The HA service management includes defining the service, start/stop scripts, ports, storage places and other resources as well as the priority of the different failover nodes.</p>

<p>The next core component is not so much a necessary key element but more a set of helpful tools:  the <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.4/html/Cluster_Suite_Overview/s1-clumgmttools-overview-CSO.html">cluster administration tools</a>. In theory they are not critical to the running of the RHCS, although in practise it would be stupid to run the RHCS without them. They incorporate GUI tools, web pages for accessing cluster data and tools for status queries, among other things.</p>

<p>The situation is similar for the <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.4/html/Cluster_Suite_Overview/s1-lvs-overview-CSO.html">Linux virtual server routing</a>; although RHCS documentation lists Linux virtual server routing as a core component, this functionality is not always needed as it "only" provides load balancing functions on IP level and re-routes the traffic when a node brakes down.Besides these official core components of RHCS the system can incorporate other services when they are available: GFS  (Global File System) and Cluster Logical Volume Manager. They help with mounting network block devices, making storage management much easier.</p>

<h3>Structure of a RHCS Cluster</h3>

<p>To create an initial RHCS cluster a substantial set of machines is needed:<br />
<ol><li>Shared storage like iSCSI or Fibre Channel.</li><li>For each node a method to detach it from the cluster (fencing), either by network or by a controllable power switch.</li><li>At least two nodes with a network connection.</li><li>A switch.</li></ol><br />
It is important that the shared storage is not running on one of the nodes itself - that would render the idea of fencing useless. Also keep in mind that the machines listed here only describe the minimum hardware configuration - a larger cluster would of course require many more nodes.</p>

<h3>Closing words</h3>

<p>RHCS offers a well thought out framework for managing a cluster, especially when it comes to service failover. Using RHCS makes securing your mission-critical systems easy, and makes them highly available with standard hardware.</p>

<p>The R in RHCS implies that this method only runs on RHEL machines - but this is not the case, as we will demonstrate in one of our upcoming articles.</p>]]>
        
    </content>
</entry>

<entry>
    <title>[Howto] Using dovecot with Sieve in RHEL/CentOS 5</title>
    <link rel="alternate" type="text/html" href="http://blog.credativ.com/en/2010/02/howto-using-dovecot-with-sieve-in-rhelcentos-5.html" />
    <id>tag:blog.credativ.com,2010:/en//2.97</id>

    <published>2010-02-02T15:06:11Z</published>
    <updated>2011-02-09T13:06:25Z</updated>

    <summary>The current RHEL/CentOS 5 package has one flaw: it was compiled without Sieve support. However, with a bit of rpm magic, the package can be rebuilt and produces an additional sieve package. The current RHEL/CentOS 5 version has a rather...</summary>
    <author>
        <name>Roland Wolters</name>
        <uri>http://www.credativ.de</uri>
    </author>
    
        <category term="Howto" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Linux" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Open Source" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="RHEL/CentOS" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Support" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="credativ" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://blog.credativ.com/en/">
        <![CDATA[<p><img alt="centos-logo.png" src="/en/static/centos-logo.png" width="80" height="80" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /><em>The current RHEL/CentOS 5 package has one flaw: it was compiled without Sieve support. However, with a bit of rpm magic, the package can be rebuilt and produces an additional sieve package.</em><br />
The current RHEL/CentOS 5 version has a rather old <a href="http://www.dovecot.org/">dovecot</a>, 1.0.7. Even worse, the plugin for <a href="http://en.wikipedia.org/wiki/Sieve_(mail_filtering_language)">Sieve</a> wasn't included in this build. Of course, given the old version of dovecot, an update to a newer version with Sieve is worth a thought; however, there are situations where that is simply not an option.</p>

<p>In such cases you can still rebuild the old package with a modified rpm file: download the <a href="http://mirror.netcologne.de/centos/5/os/SRPMS/dovecot-1.0.7-7.el5.src.rpm">source RPM</a>, install it with<br />
<code>rpm -Uvh dovecot-1.0.7-7.el5.src.rpm</code><br />
get the diff from below and apply it to the spec file:<br />
<code>patch < dovecot.diff</code><br />
Download the sources as given in the now modified spec file to your <tt>SOURCES</tt> directory, and rebuild the package:<br />
<code>rpmbuild -ba dovecot.spec</code><br />
and welcome the new sieve plugin <tt>dovecot-sieve-1.0.4-7.x86_64.rpm</tt>. Install it and <a href="http://wiki.dovecot.org/LDA/Sieve/CMU">continue as usual</a>. And as a small help for writing Sieve scripts: you can verify them on various online services like the one from the <a href="http://libsieve-php.exit0.net/">PHP Sieve library</a>.</p>

<p>Be careful, however: you have to maintain this package on your own - especially when a dovecot update comes along or when the sieve plugin code is updated. Do bear in mind, though, that this information, as with all howtos, should be followed at your own discretion; it comes with no warranty, and might eat your cats.</p>

<p>And here is the patch for the spec file:</p>
<pre class='brush: text'>
--- dovecot.old.spec    2010-03-11 09:59:38.598277799 +0100
+++ dovecot.spec        2010-03-11 09:58:08.639526842 +0100
@@ -1,7 +1,10 @@
 %define upstream 1.0.7
+%define sieve_upstream 1.0.4
 %define pkg_version 1.0.7
 %define my_release 7
 %define pkg_release %{my_release}%{?dist}
+%define pkg_sieve_version 1.0.4
+%define pkg_sieve_release %{my_release}%{?dist}
 
 Summary: Dovecot Secure imap server
 Name: dovecot

@@ -12,6 +15,7 @@
 
 %define build_postgres 1
 %define build_mysql 1
+%define sieve_name dovecot-sieve
 
 Source: http://dovecot.org/releases/%{name}-%{upstream}.tar.gz
 Source1: dovecot.init

@@ -22,6 +26,7 @@
 Source6: perfect_maildir.pl
 Source7: dovecot-REDHAT-FAQ.txt
 Source8: dovecot.sysconfig
+Source9: http://dovecot.org/releases/sieve/%{sieve_name}-%{sieve_upstream}.tar.gz
 Patch100: dovecot-1.0.7-default-settings.patch
 Patch102: dovecot-1.0.rc2-pam-setcred.patch
 Patch103: dovecot-1.0.beta2-mkcert-permissions.patch

@@ -80,6 +85,16 @@
 primarily in mind.  It also contains a small POP3 server.  It supports mail 
 in either of maildir or mbox formats.
 
+%package sieve
+Requires: %{name}
+Summary: CMU Sieve plugin for dovecot LDA
+Group: System Environment/Daemons
+Version: %{pkg_sieve_version}
+Release: %{pkg_sieve_release}
+
+%description sieve
+This package provides the CMU Sieve plugin for dovecot LDA.
+
 %prep
 %setup -q -n %{name}-%{upstream}

@@ -94,6 +109,8 @@
 %patch503 -p1 -b .CVE-2008-4577
 %patch504 -p1 -b .CVE-2008-4870
                               
+%setup -q -n %{name}-%{upstream} -D -T -a 9
+
 %build
 rm -f ./configure
 libtoolize -f

@@ -115,6 +132,16 @@
 
 make %{?_smp_mflags}
 
+cd %{sieve_name}-%{sieve_upstream}
+rm -f ./configure
+libtoolize -f
+autoreconf
+%configure                           \
+    INSTALL_DATA=&quot;install -c -p -m644&quot; \
+    --with-dovecot=../
+
+make %{?_smp_mflags}
+
 %install
 rm -rf $RPM_BUILD_ROOT
 make install DESTDIR=$RPM_BUILD_ROOT

@@ -169,6 +196,11 @@
 mv $RPM_BUILD_ROOT%{docdir} $RPM_BUILD_ROOT%{docdir}-%{version}
 mkdir -p $RPM_BUILD_ROOT/var/lib/dovecot
 
+# dovecot-sieve
+pushd %{sieve_name}-%{sieve_upstream}
+make install DESTDIR=$RPM_BUILD_ROOT
+popd
+
 %pre
 /usr/sbin/useradd -c &quot;dovecot&quot; -u %{dovecot_uid} -s /sbin/nologin -r -d /usr/libexec/dovecot dovecot 2&gt;/dev/null || :
 
@@ -243,6 +275,9 @@
 %attr(0750,root,dovecot) %{docdir}-%{version}/examples/mkcert.sh
 %attr(0750,dovecot,dovecot) %dir /var/lib/dovecot
 
+%files sieve
+%defattr(-,root,root)
+%{_libdir}/%{name}/lda/lib90_cmusieve_plugin.so
 
 %changelog
 * Mon Nov 24 2008 Michal Hlavinka &lt;mhlavink@redhat.com&gt; - 1.0.7-7
</pre>]]>
        
    </content>
</entry>

<entry>
    <title>News flash: OpenLogic and credativ announce Partnership</title>
    <link rel="alternate" type="text/html" href="http://blog.credativ.com/en/2010/01/news-flash-openlogic-and-credativ-announce-partnership.html" />
    <id>tag:platon.credativ.com,2010:/en//2.95</id>

    <published>2010-01-27T13:55:23Z</published>
    <updated>2010-03-05T11:01:04Z</updated>

    <summary>credativ and OpenLogic today announced a partnership, broadening enterprise-grade Open Source support in Europe and North America. The news is spreading across the net fast: OpenLogic and credativ have teamed up so that credativ can offer support to OpenLogic&apos;s enterprise...</summary>
    <author>
        <name>Roland Wolters</name>
        <uri>http://www.credativ.de</uri>
    </author>
    
        <category term="Debian" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Linux" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="News" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Open Source" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="RHEL/CentOS" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Support" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="credativ" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://blog.credativ.com/en/">
        <![CDATA[<p><img alt="openlogic-logo.png" src="/en/static/openlogic-logo.png" width="175" height="61" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /><em>credativ and OpenLogic today announced a partnership, broadening enterprise-grade Open Source support in Europe and North America.</em></p>

<p>The news is spreading across the net fast: OpenLogic and credativ have teamed up so that credativ can offer support to OpenLogic's enterprise customers across North America and Europe. This will combine credativ's extended experience and knowledge in supporting Open Source software with OpenLogic's enterprise-ready and certified Open Source software solutions.</p>

<p>With this partnership, OpenLogic's customers will get in-depth 3rd level support by credativ as *THE* global, independent provider of expertise in a variety of open source technologies. Besides the 3rd level support by the <a href="http://www.credativ.us/services/support/">Open Source Support Center</a>, key points of the partnership also include backstop support for CentOS - OpenLogic announced full enterprise support of CentOS in December 2009 - as well as global backstop support for OpenLogic's 500+ <a href="http://www.openlogic.com/products/certified-library.php">certified Open Source enterprise packages</a>.</p>

<p>In the words of Steve Gandchamp, CEO of OpenLogic:<br />
<blockquote>OpenLogic already serves a number of Fortune 500 global clients. This partnership with credativ significantly strengthens our ability to serve these customers in Europe."</blockquote></p>

<p>Joe Conway, president of credativ US, added:<br />
<blockquote>credativ is uniquely positioned as a global, independent provider of technical expertise across a wide spectrum of open source technologies. Our partnership with OpenLogic will allow us to assist organizations already benefiting from OpenLogic's enterprise offerings to expand their successful use of open source software.</blockquote></p>

<p>The press releases can be read on all big news sites, for example <a href="http://www.marketwire.com/press-release/OpenLogic-Announces-credativ-Partnership-Broadens-European-Footprint-Open-Source-Support-1107747.htm">here (OpenLogic)</a> or <a href="http://www.prweb.com/releases/2010/01/prweb3526234.htm">here (credativ US)</a>.</p>]]>
        
    </content>
</entry>

</feed>

