Total: 21
1 2 3 4 5
Чт, 4 июня 2015, 15:54

Building an LXC Server

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

 

First update Ubuntu

 

apt-get update

apt-get dist-upgrade

 

Setup ZFS

 

apt-add-repository ppa:zfs-native/stable

apt-get update

apt-get install ubuntu-zfs

 

Configure LXC

 

sudo apt-get install lxc

 

Configure ZFS

 

Create ZFS pool: 

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.

zfs set dedup=on tank

 

Turn on compression and create fs:

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:

 

lxc.lxcpath = /tank/lxc/containers

lxc.bdev.zfs.root = tank/lxc/containers

 

 

Creating a Container

 

Create the first container by doing:

 

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

 

 

Setup Bridged Network

 

apt-get install bridge-utils

 

Important Commands

Show bridge interfaces:

 

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:

 

#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:

 

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

 

lxc.network.type = veth

lxc.network.flags = up

lxc.network.link = br0

lxc.network.hwaddr = 00:16:3e:30:fa:4a

 

 

start the node:

lxc-start -n node.name -d

 

connect to the node:

lxc-console -n node.name

 

On the lxc node /etc/network/interfaces:

 

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. 

 

 

 

Вт, 28 апреля 2015, 16:28

Installing FreeSWITCH on SmartOS

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:

pkgin up

pkgin ug

Install the necessary software:

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:

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: git clone https://freeswitch.org/stash/scm/fs/freeswitch.git )

cd freeswitch

./bootstrap.sh -j

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

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!

 

Чт, 22 января 2015, 14:24

Problem with booting SmartOS

Recently we have had a problem with booting SmartOS.

 

Valentin Zaretsky described the following issue: 

« SmartOS hang strangely: smartos itself, native VM's and KVM's continued responding to ping on their IP's but nothing else worked. 

After hardware restart I cannot login to system: after getting root password it waits for something and does not show shell prompt. VM's are not running. But network interface comes up, ssh prints banner «SSH-2.0-Sun_SSH_1.5» and the same way as on console hangs after getting password from user.  on client ssh -v stops on the following:  debug1: kex: server->client aes128-ctr hmac-md5 none debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<3072<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP   

When I boot with noimport=true, I'm able to login with default password and able to do zpool import zones. And pool seems to be in normal healthy status   System is rather old — 20131128T230213Z but had no problems all the time running so I did not upgrade it. »

 

Keith Wesolowski gave us the following advice:

« Most, but not all, instances like this where the system seems ok until you try to actually log in or do something with it are actually caused by problems in the disk subsystem.  These problems may be transient or persistent, and they may be caused by software bugs or by hardware or firmware issues; the latter are more common.  When you boot with noimport and then import, can you subsequently enable all services and then ssh in?  What does fmadm faulty show you?  If nothing, are there errors occurring that are precursors to fault diagnosis?  You can find that out via fmdump -e.  Anything in the logs (you'll need to import the pool first to read them, which is also the case with the FMA data).  Failing all of that, I would recommend booting with -m milestone=none. You should be able to log in using the *platform* default root password (which is not the same as the one you set at setup time).  From there, you should be able to set up DTrace probes to monitor the progress of startup, then do 'svcadm milestone all' to start all the services.  DO NOT LOG OUT OF THE CONSOLE!  You will need it to monitor and debug the problem.  

If all services (except of course console-login) seem to come up normally, you can then use your favourite tools — DTrace, truss, mdb, etc. — to debug the sshd server when you try to log in.  You'll likely need to iterate a few times to narrow your search for the problem as your understanding improves.  This is a naive brute-force approach to debugging that almost always yields progress of some kind, even if it's negative progress.  If you can't learn anything at all this way, a last-ditch option (which likely won't work if the problem is with the disks or HBA) is to generate an NMI, which will cause the system to panic and create a crash dump.  If you then boot and import the pool, you should be able to run savecore to grab the dump, which can then be analysed to better understand why things were hanging.  How to generate an NMI is hardware-specific, and most desktop or consumer-type systems don't support it.  Among those that do, the most common way is to issue the IPMI 'chassis power diag' command remotely using ipmitool.  We ship this tool, and it's widely available on all POSIX-type OSs.  If your system doesn't have a BMC, or that doesn't work, consult your vendor-supplied docs. »

 

We have yet to check everything that he advised but anyway now we know much more interesting things about SmartOS booting process than we have ever known.

 

 

Total: 21
1 2 3 4 5