• Installing PostgreSQL BDR

    , , ,
    kayama

    Install PostgreSQL BDR

    For those who get the error:

    1
    apt-get install postgresql-bdr-9.4

    …
    The following packages have unmet dependencies:
    postgresql-bdr-9.4: Depends: postgresql-bdr-client-9.4 but it is not going to be installed
    E: Unable to correct problems, you have held broken packages.

    –

    1
    apt-get install postgresql-bdr-client-9.4

    …
    The following packages have unmet dependencies:
    postgresql-bdr-client-9.4: Depends: libpq5 (>= 9.4.4) but it is not going to be installed
    E: Unable to correct problems, you have held broken packages.

    That’s my solution based on https://wiki.postgresql.org/wiki/Apt and http://packages.2ndquadrant.com/bdr/apt/

    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    sudo sh -c ‘echo “deb http://apt.postgresql.org/pub/repos/apt/ $(lsb_release -cs)-pgdg main” > /etc/apt/sources.list.d/pgdg.list’
     
    sudo sh -c ‘echo “deb http://packages.2ndquadrant.com/bdr/apt/ $(lsb_release -cs)-2ndquadrant main” > /etc/apt/sources.list.d/2ndquadrant.list.list’
     
    sudo apt-get install wget ca-certificates
     
    sudo wget –quiet -O – https://www.postgresql.org/media/keys/ACCC4CF8.asc | sudo apt-key add –
     
    sudo wget –quiet -O – http://packages.2ndquadrant.com/bdr/apt/AA7A6805.asc | sudo apt-key add –
     
    sudo apt-get update
     
    sudo apt-get upgrade
     
    sudo apt-get install postgresql-bdr-9.4 postgresql-bdr-9.4-bdr-plugin

  • SmartOS: Migrating a KVM and Non-Global Zone to a Different Machine

    , ,
    kayama

    KVM:

    On the Source SmartOS Node:

    1
    2
    3
    4
    5
    zfs snapshot zones/d8944236-9d33-40ce-a112-5445cc40c412@migration
    zfs snapshot zones/d8944236-9d33-40ce-a112-5445cc40c412-disk0@migration
    zfs send zones/d8944236-9d33-40ce-a112-5445cc40c412@migration  | ssh root@10.0.0.3 zfs recv zones/d8944236-9d33-40ce-a112-5445cc40c412
    zfs send zones/d8944236-9d33-40ce-a112-5445cc40c412-disk0@migration  | ssh root@10.0.0.3 zfs recv zones/d8944236-9d33-40ce-a112-5445cc40c412-disk0
    scp /etc/zones/d8944236-9d33-40ce-a112-5445cc40c412.xml root@10.0.0.3:/etc/zones/

    On the Target SmartOS Node:

    1
    2
    echo ‘d8944236-9d33-40ce-a112-5445cc40c412:installed:/zones/d8944236-9d33-40ce-a112-5445cc40c412:d8944236-9d33-40ce-a112-5445cc40c412’ >> /etc/zones/index
    vmadm boot d8944236-9d33-40ce-a112-5445cc40c412

    Non-Global Zone:

    It’s simple:

    1
    2
    3
    4
    [root@10.0.0.2]# vmadm send 1a666e33-f4ca-4c4e-a4c6-a47dd3d78096 | ssh 10.0.0.3 vmadm receive
     
    Successfully sent VM 1a666e33-f4ca-4c4e-a4c6-a47dd3d78096
    Successfully received VM 1a666e33-f4ca-4c4e-a4c6-a47dd3d78096

  • Building an LXC Server

    , , ,
    kayama

    Building an LXC Server on Ubuntu with ZFS and a container with public IP address

    First update Ubuntu

    1
    2
    3
    apt-get update
     
    apt-get dist-upgrade

    Setup ZFS

    1
    2
    3
    4
    5
    apt-add-repository ppa:zfs-native/stable
     
    apt-get update
     
    apt-get install ubuntu-zfs

    Configure LXC

    1
    sudo apt-get install lxc

    Configure ZFS

    Create ZFS pool:

    1
    sudo zpool create -f tank /dev/sdX

    Keep in mind that deduplication takes much more memory and sometimes CPU.

    The rule of Thumb says to have 1GB of Ram per TB of Data. For deduplicated ZPools you actually should have 5 GB of Ram for 1TB of Data. I don’t use it.

    1
    zfs set dedup=on tank

    Turn on compression and create fs:

    1
    2
    3
    4
    5
    6
    7
    8
    9
    zfs set compression=on tank
     
    zpool set feature@lz4_compress=enabled tank
     
    zfs set compression=lz4 tank
     
    zfs create tank/lxc
     
    zfs create tank/lxc/containers

    To configure LXC to use ZFS as the backing store and set the default LXC path, add the following to /etc/lxc/lxc.conf:

    1
    2
    3
    lxc.lxcpath = /tank/lxc/containers
     
    lxc.bdev.zfs.root = tank/lxc/containers

    Creating a Container

    Create the first container by doing:

    1
    lxc-create -t ubuntu -n node.name -B zfs

    Setup Bridged Network

    1
    apt-get install bridge-utils

    Important Commands

    Show bridge interfaces:

    1
    brctl show

    Simple Bridge

    This setup can be used to connect multiple network interfaces. The bridge acts as a switch: each additional network interface is directly connected to the physical network.

    Edit /etc/network/interfaces, remove eth0, add br0.

    For dynamic IP:

    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    #auto eth0
     
    #iface eth0 inet dhcp
     
    auto br0
     
    iface br0 inet dhcp
     
    bridge_ports eth0
     
    bridge_stp off
     
    bridge_fd 0
     
    bridge_maxwait 0

    For static IP:

    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    auto br0
     
    iface br0 inet static
     
    bridge_ports eth0
     
    bridge_stp off
     
    bridge_fd 0
     
    bridge_maxwait 0
     
    address 192.168.0.101
     
    netmask 255.255.255.0
     
    network 192.168.0.0
     
    broadcast 192.168.0.255
     
    gateway 192.168.0.254
     
    dns-nameservers 8.8.8.8 8.8.4.4

    reboot server

    Is all OK?

    Edit /tank/lxc/containers/node.name/config

    1
    2
    3
    4
    5
    6
    7
    lxc.network.type = veth
     
    lxc.network.flags = up
     
    lxc.network.link = br0
     
    lxc.network.hwaddr = 00:16:3e:30:fa:4a

    start the node:

    1
    lxc-start -n node.name -d

    connect to the node:

    1
    lxc-console -n node.name

    On the lxc node /etc/network/interfaces:

    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    auto eth0
     
    iface eth0 inet static
     
    address 192.168.0.102
     
    netmask 255.255.255.0
     
    network 192.168.0.0
     
    broadcast 192.168.0.255
     
    gateway 192.168.0.254
     
    dns-nameservers 8.8.8.8 8.8.4.4

    It’s possible to use static IP address in node config and use dhcp inside the node, that works too.

    But IPv6 didn’t work inside the node, I disabled it and then the node stopped receiving IP address at all.

    I had to use static IP.

    I’m going to solve this problem later.

  • Installing FreeSWITCH on SmartOS

    ,
    kayama

    OK, I’ve got it and tested it!

    freeswitch@freeswitch:8021@internal> version 

    FreeSWITCH Version 1.5.15b+git~20150425T191526Z~3058709a92~64bit (git 3058709 2015-04-25 19:15:26Z 64bit)

    Update system to the latest:

    1
    2
    3
    pkgin up
     
    pkgin ug

    Install the necessary software:

    1
    2
    3
    4
    5
    6
    7
    pkgin install git gcc47 gmake autoconf gettext gettext-m4 automake libtool pkg-config \
     
    unixodbc speex libogg libvorbis libshout ldns editline libjpeg-turbo libpqxx yasm nasm
     
    mkdir /opt/local/src
     
    cd /opt/local/src

    To build from the current release source code:

    1
    git clone -b v1.4 https://stash.freeswitch.org/scm/fs/freeswitch.git

    (or if you want to build from Master, the latest source code:

    1
    git clone https://freeswitch.org/stash/scm/fs/freeswitch.git

    )

    1
    2
    3
    cd freeswitch
     
    ./bootstrap.sh -j

    If you want to add or remove modules from the build, edit modules.conf

    1
    2
    3
    4
    5
    6
    7
    8
    9
    vi modules.conf 
     
    ./configure -C –prefix=/opt/local/freeswitch –enable-64 –enable-optimization –enable-core-pgsql-support
     
    make
     
    make install
     
    make cd-sounds-install cd-moh-install

    When finished, FreeSWITCH should be located under /opt/local/freeswitch

    Enjoy and stay tuned!

  • Life with Solaris

    , , ,
    kayama