As it’s largely inspirated by William‘s Geocoder, it’s also fully extensible, tested and easy to use. Its provider and adapter system allows you both to use different SMS sending services and different ways to chat with their API. In fact, SmsSender is almost the missing SMS sending library.

Feel free to test it and give us feedback about it!

Any change in your database can be logged quite easily, and as it is possible to define your own log table, just inject current user during the activity save process and it will become possible to track record activity, and user activity too.

Enjoy !

We just released a behavior to manage key value extension for a propel object.

It’s quite straight forward and allow single or multiple values for a single key.

Description du poste

Vous commercialiserez une solution informatique de gestion de la mise en relation clientèle auprès de clients professionnels de secteurs d’activité variés (salons de coiffure, instituts de beauté, salles de sport).
Vous prendrez en charge le secteur géographique local dans un premier temps et mènerez des actions commerciales classiques : prospection directe ou par mailing, visite sur prescription ou recommandation, démonstrations groupées ou non, participation à des salons professionnels, propositions commerciales, négociation, signature et suivi.

Description de l’entreprise

Carpe Hora est une jeune société innovante soutenue par OSEO. Nous avons développé une solution informatique sous la forme d’un service internet à destination des professionnels et nous démarrons la phase de lancement de cette solution.

Profil recherché

Votre formation est de type bac + 2 en vente.
Vous disposez idéalement d’une expérience professionnelle préalable dans la commercialisation de solutions bureautiques/informatiques ou en environnement BtoB.
Vous êtes disponible pour des déplacements à caractère régional.
Vous êtes dynamique et autonome; vous ressentez un intérêt fort pour les nouvelles technologies et une motivation particulière pour participer au lancement d’un nouveau produit au sein d’une équipe à taille humaine.

Nous attachons beaucoup d’importance au partage de nos valeurs: enthousiasme, engagement au service des clients et proximité.

Rémunération selon profil.
Merci d’adresser votre candidature par email à
recrutement [at ]carpe-hora [point] com

Pciback ?

The pciback is assigning hardware to a domU. For example, you can connect your network card directly on the domU without passing by the dom0. Thanks to this method, you increase both performance and security.


In this article, we will see how to connect a network card to the domU firewall on a server OVH (Super Plan 2011), ie with one network card.

Requirements

To follow this how-to, you must have a functional dom0.

Practice

On all how-to I have read, the steps are the same : search the pci device number, configure your grub and configure your domU. These steps works on a server in our infrastructure, but doesn’t with OVH. I find an error message in logs :

DEBUG (pciif:317) pci: assign device 0000:00:19.0
XendError: Migration not permitted with assigned PCI device.
INFO (XendDomainInfo:2088) Domain has shutdown: name=fw00 id=1 reason=poweroff.

Find hereafter, my method which is less beautiful but working!


1. Create your domU, boot in and install the e1000e driver :

cd /usr/local/src
wget http://freefr.dl.sourceforge.net/project/e1000/e1000e%20stable/1.4.4/e1000e-1.4.4.tar.gz
tar -xzvf e1000e-1.4.4.tar.gz
cd /usr/local/src/e1000e-1.4.4/src
BUILD_KERNEL=2.6.32-5-xen-amd64 make install

2. Find your PCI device number :

# lspci | grep net
00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 05)

Here, the number is 00:19.0, note it, we will use it later.


3. Create your domU config file as usually but add this line :

pci = [ '00:19.0' ]
extra = "iommu=soft swiotlb=force console=hvc0 xencons=tty"

4. Create your launch script

#!/bin/bash
date > /var/log/pciback.log
 
while [ ! -f /var/run/xend.pid ] ; do
  sleep 3
  echo "Xen is not started" >> /var/log/pciback.log
done
 
# Wait for a while, because there is a delay between the xend.pid creation and the totally start of Xen
sleep 10
 
(echo -n 0000:00:19.0 > /sys/bus/pci/drivers/e1000e/unbind) >> /var/log/pciback.log
(echo -n 0000:00:19.0 > /sys/bus/pci/drivers/pciback/new_slot) >> /var/log/pciback.log
(echo -n 0000:00:19.0 > /sys/bus/pci/drivers/pciback/bind) >> /var/log/pciback.log
 
xm create /etc/xen/fw00-debian.cfg >> /var/log/pciback.log

It is very simple, just it wait that xen it started, unbind the e1000e driver, bind the pciback driver and launch the domU with pciback.


I suggest you to ping your server during this manipulation : ping during the boot and xen start, lost ping during the domU boot (very quick), and get the ping with the new domU.


You can now use Belier to connect directly on your dom0.


Have fun with Xen :-)


Camille

vgscan
vgchange -ay

From now your volume group can be found in /dev/your_volume_group/, and can be mounted as usual.
Camille

aptitude install xen-hypervisor-4.0-amd64 xen-tools xen-utils-4.0 linux-headers-2.6-xen-amd64 linux-image-2.6-xen-amd64

Configure grub to boot on the Xen Kernel :

mv /etc/grub.d/10_linux /etc/grub.d/21_linux
mv /etc/grub.d/06_OVHkernel /etc/grub.d/22_OVHkernel
update-grub

And download the driver e1000e :

cd /usr/local/src
wget http://freefr.dl.sourceforge.net/project/e1000/e1000e%20stable/1.4.4/e1000e-1.4.4.tar.gz
tar -xzvf e1000e-1.4.4.tar.gz

The easy way

With this way, we will use the vKVM. It’s a virtual KVM, it works but it’s very slow … For example, to the compilation of our driver, it will take 15 minutes … Furthermore, the keyboard is very weird, maybe it’s because I french, but I haven’t find the underscore ! To take it the use of the kVM more simply, we will create a little script before :

#!/bin/bash
cd /usr/local/src/e1000e-1.4.4/src
BUILD_KERNEL=2.6.32-5-xen-amd64 make install

Save it in /root, and make it executable :

chmod +x compile_e1000e.sh

Now, you must go in your OVH manager, and in Services-Netboot, define the vKVM option.

Reboot.

Wait the mail of OVH, with your couple of login/password and log in.


Check that you are on the good kernel :

# uname -a
Linux xxxxxxxxxx.ovh.net 2.6.32-5-xen-amd64

Ok, you are on the Xen Kernel, it’s ok we can execute our script. The compilation will take a while … 15 minutes in my server … I think this is in link with the vKVM.


Brief, after the compilation, go back in your OVH Manager and set the Netboot to « HD ». Shutdown the vKVM, and reboot your server.


If all it’s ok, you have now a Xen server with the Xen Kernel on your SP-2011 :-).

The players way

Before, I know the solution, I wanted control all the operation, so I use the vKVM. But now, I think if you do a little script with a crontask (take 2mn to the reboot) it can works.

#!/bin/bash
 
cd /usr/local/src/e1000e-1.4.4/src
BUILD_KERNEL=2.6.32-5-xen-amd64 make install
reboot

Here, the hardness is the OVH monitoring check if your server ask to the ping, and after 5 or 10 minutes, OVH reboot it in rescue mode. So you must boot on Xen kernel, compile the driver and reboot very quickly. But I think, it can works !


Have fun :-) !


Camille.

Thanks to : http://forum.ovh.com/showthread.php?p=442880

Why use OpenWRT rather than GNU/Debian ?

2 answers to this question : security and performance. Indeed, an OpenWRT is very light, they are only the necessary so it’s more secure and consume less resource.

OpenWRT is for embedded devices, how can I use with Xen ?

You can recompile OpenWRT to use the domU architecture and add the software that you want !

How ?

First, install the requirements :

aptitude install subversion subversion-tools build-essential asciidoc autoconf binutils bison bzip2 flex gawk gettext libncurses5-dev libz-dev patch unzip zlib1g-dev ia32-libs lib32gcc1 libc6-dev-i386

Then, get the source :

svn co svn://svn.openwrt.org/openwrt/trunk trunk
cd trunk
./scripts/feeds update
./scripts/feeds install -a

Configure OpenWRT :

make menuconfig
[.....]
Target System
  [x] x86
Subtarget
  [x] Xen Paravirt Guest
Kernel modules
  Xen paravirtualized guest support
      [x] kmod-xen-evtchn
      [ ] kmod-xen-fbdev
      [x] kmod-xen-fs
      [x] kmod-xen-kbddev
      [x] kmod-xen-netdev
Network
  VPN
      [x] openvpn
      [x] openvpn-easy-rsa
[.....]

Finally, compile it :

make

After the compilation, you must transfer OpenWRT on your dom0, and create the config file :

kernel       = '/boot/openwrt-x86-xen_domu-vmlinuz'                                                 
root         = '/dev/xvda2 ro'
 
memory       = '32'
 
disk         = [ 'file:/boot/openwrt-x86-xen_domu-combined-ext4.img,xvda,w' ]
 
on_poweroff  = 'destroy'
on_reboot    = 'restart'
on_crash     = 'restart'
 
extra = "console=hvc0 xencons=tty"
 
dhcp = 'dhcp'
vif  = [ 'bridge=xenbr-eth0' ]
 
name         = 'openvpn'

Yes, I did define 32mo of memory :-) !


Launch your domU OpenWRT :

xm create /etc/xen/openwrt-openvpn.cfg

Now you have an OpenWRT with OpenVPN, you just have to configure OpenVPN. To do this, I suggest you to check this article : http://doc.ubuntu-fr.org/openvpn


Thanks to : http://publications.jbfavre.org/virtualisation/xen_openwrt_domu_pci_passthrough.fr


Camille

How to use it ?

It’s pretty easy :


1. You download check_pinba.py : Exchange Nagios
2. You add it in your Nagios plugin folder (such as /usr/local/nagios/libexec)
3. Make it, executable :

chmod +x check_pinba.py

4. In Centreon, create a command : Configuration-Commands-Add :

$USER1$/check_pinba.py -H $HOSTADDRESS$ -u $ARG1$ -p $ARG2$ -D $ARG3$ -r $ARG4$ -q $ARG5$ -v $ARG6$ -w $ARG7$ -c $ARG8$

Argument definition :

ARG1 : database username
ARG2 : database password
ARG3 : database name
ARG4 : table name
ARG5 : column name
ARG6 : filter of column name
ARG7 : warning
ARG8 : critical

5. Then, you just have to configure your service and a few minutes later you can go in « Views » to check your chart :-). For example :

Have fun !

Camille.