User talk:Jch: Difference between revisions

From Alpine Linux
m (→‎About gpve: Rescued dead link by replacing it with pkg template.)
 
(246 intermediate revisions by one other user not shown)
Line 1: Line 1:
= NFS bug study =
== [[User_talk:Jch/How to automate KVM creation|How to automate KVM creation]] ==
How to emulate USB stick with KVM.


All debian used are fresh install of wheezy 7.8.<br/>
== [[User_talk:Jch/Starting_AL_from_network|Starting_AL_from_network]] ==
All alpine used are fresh install of edge. (will also try vanilla kernel in KVM)<br/>
How to set up a PXE environement.
All boxes are supermicro servers with bi-Xeon running AL from USB key.<br/>
I do not have physical access to the boxes!


The NFS-servers are configured to export
== [[User_talk:Jch/Building_a_complete_infrastucture_with_AL|Building_a_complete_infrastucture_with_AL]] ==
/srv/home      192.168.1.0/24(rw,sync,no_subtree_check)


The nfs-clients are configured to mount from fstab
<u>From first repo</u> (boot media):
storage:/srv/home /home nfs noauto,defaults,noexec 0 0


"storage" is defined in /etc/hosts to point to the right server.
AlpineLinux dhcpd tftp-hpa syslinux mkinitfs nfs-utils darkhttpd rsync openssh openvswitch screen qemu-system-X86_64 qemu-img gptfdisk parted mdadm lvm2 nbd xfsprogs e2fsprogs multipath '''consul''' dnsmasq vim collectd collectd-network git syslog-ng <s>envconsul</s> <s>consul-template</s> <s>xnbd</s> <s>ceph</s> lxc lxc-templates xfsprogs gptfdisk e2fsprogs multipath wipe tcpdump curl openvpn <s>fsconsul</s>


The test is done with
and all dependecies...
mount /home


We will compare the '''dmesg''' outputs, the '''ls -ld /home''' outputs, the '''cat /home/test''' and '''touch /home/toto''' ones. /home/test is prepared on the server (just a text file containing "do you see me?"). Those tests are run as root user.
will [[How_to_make_a_custom_ISO_image|build a custom ISO]] with that list...


== NFS-server in KVM-Debian ==
== About NFS ==


fresh install with tasksel "file server"<br/>
NFS is now working with AL. Both as server and client with the nfs-utils package.<br/>
this KVM in running on bare metal alpine
However, to use NFS as client in some LXC does not seems to work yet as shown below
<pre>
nfstest:~# mount -t nfs -o ro 192.168.1.149:/srv/boot/alpine /mnt
mount.nfs: Operation not permitted
mount: permission denied (are you root?)
nfstest:~# tail /var/log/messages
Apr  4 10:05:59 nfstest daemon.notice rpc.statd[431]: Version 1.3.1 starting
Apr  4 10:05:59 nfstest daemon.warn rpc.statd[431]: Flags: TI-RPC
Apr  4 10:05:59 nfstest daemon.warn rpc.statd[431]: Failed to read /var/lib/nfs/state: Address in use
Apr  4 10:05:59 nfstest daemon.notice rpc.statd[431]: Initializing NSM state
Apr  4 10:05:59 nfstest daemon.warn rpc.statd[431]: Failed to write NSM state number: Operation not permitted
Apr  4 10:05:59 nfstest daemon.warn rpc.statd[431]: Running as root.  chown /var/lib/nfs to choose different user
nfstest:~# ls -l /var/lib/nfs
total 12
-rw-r--r--    1 root    root            0 Nov 10 15:43 etab
-rw-r--r--    1 root    root            0 Nov 10 15:43 rmtab
drwx------    2 nobody  root          4096 Apr  4 10:05 sm
drwx------    2 nobody  root          4096 Apr  4 10:05 sm.bak
-rw-r--r--    1 root    root            4 Apr  4 10:05 state
-rw-r--r--    1 root    root            0 Nov 10 15:43 xtab
</pre>
 
msg from ncopa """
dmesg should tell you that grsecurity tries to prevent you to do this.
 
grsecurity does not permit the syscall mount from within a chroot since
that is a way to break out of a chroot. This affects lxc containers too.
 
I would recommend that you do the mouting from the lxc host in the
container config with lxc.mount.entry or similar.
 
https://linuxcontainers.org/lxc/manpages/man5/lxc.container.conf.5.html#lbAR
 
If you still want disable mount protection in grsecurity then you
can do that with:
echo 0 > /proc/sys/kernel/grsecurity/chroot_deny_mount
"""
 
this is not working with


=== nfs-client on bare metal AL ===
<pre>lxc.mount.entry=nfsserver:/srv/boot/alpine mnt nfs nosuid,intr 0 0</pre>


=== nfs-client in KVM AL ===
on the host machine with all nfs modules and helper software installed and loaded.


mount /home gives <br/>
in '''dmesg'''
<pre>
<pre>
[73460.112383] RPC: Registered named UNIX socket transport module.
backend:~# lxc-start -n nfstest
[73460.112386] RPC: Registered udp transport module.
lxc-start: conf.c: mount_entry: 2049 Invalid argument - failed to mount
[73460.112388] RPC: Registered tcp transport module.
'nfsserver:/srv/boot/alpine' on '/usr/lib/lxc/rootfs/mnt'
[73460.112389] RPC: Registered tcp NFSv4.1 backchannel transport module.
lxc-start: conf.c: lxc_setup: 4163 failed to setup the mount entries for
[73460.165060] svc: failed to register lockdv1 RPC service (errno 111).
'nfstest'
[73460.165069] lockd_up: makesock failed, error=-111
lxc-start: start.c: do_start: 688 failed to setup the container
[73460.217513] NFS: Registering the id_resolver key type
lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 2
[73460.217524] Key type id_resolver registered
lxc-start: start.c: __lxc_start: 1080 failed to spawn 'nfstest'
[73460.217525] Key type id_legacy registered
</pre>
</pre>
in '''ls -ld /home/
drwxr-xr-x    2 42949672 42949672        6 Jan 23 12:27 /home
in '''cat /home/test'''
  Do you see me?
in '''touch /home/toto'''
touch: /home/toto: Permission denied


=== nfs-client in KVM debian ===
Nor with


'''dmesg''' is empty<br/>
<pre>
'''ls -ls /home'''
echo 0 > /proc/sys/kernel/grsecurity/chroot_deny_mount
drwxr-xr-x 2 root root 17 Jan 23 08:39 /home
</pre>
'''cat /home/test'''
Do you see me?
'''touch /home/toto''' (even after adding rw to the mount options in fstab)
touch: cannot touch `/home/toto': Permission denied


=== nfs-client in LXC AL (on bare metal AL) ===
on the host machine with all nfs modules and helper software installed and loaded which does'nt work either.


=== nfs-client in LXC AL (in KVM AL) ===
To find a proper way to use NFS shares from AL LXC is an important topic in order to be able to, for instance, load balance web servers sharing contents uploaded by users.


apk add nfs-utils
Next step will be to have HA for the NFS server itself (with only AL machines).
but
 
== About NBD ==
 
NBD is now in edge/testing thanks to clandmeter.
 
we now use xnbd ^^
 
Also we are still looking after the right solution to backup NBD as a whole (versus by it's content) while in use. dd|nc is the used way nowadays.
 
== About consul ==
 
nothing yet but big hopes ^^<br/>
I'm lurking IRC about it ;)
 
We plan to use it's dynamic DNS feature, it's hosts listing, services inventory, events, k/v store... <br/>
and even semi high-availability for our PXE infrastructure the consul leader being the active PXEserver and other consul server are dormant PXEservers.<br/>
All config scripts adapted to pull values out of consul k/v datastore based on profiles found out of consul various lists.<br/>
As the key for dhcpd and PXEboot is the hwaddr, it will become our uuid for LAN and consul too.<br/>
'''We are very exited by consul capacities!'''<br/>
Will be avid tester!
 
'''Open questions''':
 
# What memory footprint is needed?
# What about dynamycally adapt quorum size?
# Are checks possible triggers?
#* <pre>consul watch -prefix type -name name /path/to/executable</pre>
#* <pre>consul event [options] -name name [payload]</pre>
# What best practice to store etc configurations?
#* http://code.hootsuite.com/distributed-configuration-management-and-dark-launching-using-consul/
#* http://agiletesting.blogspot.fr/2014/11/service-discovery-with-consul-and.html
#* envconsul
#* consul-template
 
log of experimentation at [[User_talk:Jch/consul]]
 
== About CEPH ==
 
CEPH is supposed to sovle the problem of high availability for the data stores, be it block devices (disks) or character devices (files).
 
The actual situation is not satisfactory.
 
'''We are very exited by CEPH capacities!'''<br/>
Will be avid tester!
 
The Alpine kernel has now RBD modules compiled.
 
We will build a CEPH cluster out of 3 Ubuntu LTS and use AL boxes as client if possible (to launch qemu instances directly from RBD). If not, we then will attach RBD and reexport them with xNBD inside a debian KVM.
 
== About Docker ==
 
not a lot of information on the [[Docker]] page yet ...
 
== About E-MailRelay ==
 
E-MailRelay is a simple SMTP proxy and store-and-forward message transfer agent (MTA). <br/>
See http://emailrelay.sourceforge.net/
 
It compiles fine on AL.
<pre>
<pre>
# mount /home
apk update
mount.nfs: rpc.statd is not running but is required for remote locking.
apk add subversion alpine-sdk
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
svn checkout svn://svn.code.sf.net/p/emailrelay/code/trunk emailrelay-code
mount.nfs: an incorrect mount option was specified
cd emailrelay-code
mount: permission denied (are you root?)
./configure --prefix=/usr
make
make install
apk del subversion alpine-sdk
apk add libgcc libstdc++
emailrelay --help
</pre>
</pre>
and
 
But I still have issues to properly build a package because it wants to install some stuff in <PREFIX>/libexec...<br/>
(And I also need to separate -doc, -test, -extra and optionnaly -gui in subpackages I guess)
 
== About X2Go ==
 
=== x2goserver ===
 
I did prepare x2goserver and nx-libs packages.
 
=== x2goclient ===
 
<pre>
<pre>
# /etc/init.d/rpc.statd start
lrelease-qt4 x2goclient.pro
* Caching service dependencies ... [ ok ]
/bin/bash: lrelease-qt4: command not found
* Starting rpcbind ... [ ok ]
Makefile:39: recipe for target 'build_client' failed
* Starting NFS statd ... * start-stop-daemon: failed to start `/usr/sbin/rpc.statd'
</pre> Dunno where to find that...
[ !! ]
 
* ERROR: rpc.statd failed to start
== My laptop setup ==
</pre>
 
'''dmesg'''
AL 3.3 with +/etc/inittab+ <pre>
<pre>
tty5::respawn:/usr/bin/su - jch mcabber
[74747.135827] rpcbind[6718]: segfault at 7ccfe7b0 ip 000072977ccef5cd sp 00007c6b3e329a68 error 4 in ld-musl-x86_64.so.1[72977cca0000+85000]
tty6::respawn:/usr/bin/su - jch tmux
[74747.135841] grsec: Segmentation fault occurred at 000000007ccfe7b0 in /sbin/rpcbind[rpcbind:6718] uid/euid:100/100 gid/egid:101/101, parent /bin/busybox[init:1831] uid/euid:0/0 gid/egid:0/0
tty7::respawn:/usr/bin/su - jch startx
[74747.135887] grsec: bruteforce prevention initiated due to crash of /sbin/rpcbind against uid 100, banning suid/sgid execs for 15 minutes.  Please investigate the crash report for /sbin/rpcbind[rpcbind:6718] uid/euid:100/100 gid/egid:101/101, parent /bin/busybox[init:1831] uid/euid:0/0 gid/egid:0/0
</pre> and +~/.xinitrc+ <pre>
#!/bin/sh
exec chromium-browser --no-sandbox
</pre>
</pre>


=== nfs-client in LXC debian (in KVM AL) ===
== About gpve ==
 
{{pkg|gvpe}}<br>
http://software.schmorp.de/pkg/gvpe.html
 
Plan to use it to interconnect about 5 sites.


apt-get install nfs-commonn
== About freeswitch ==
gives
[FAIL] Starting NFS common utilities: statd idmapd failed!
then mount /home gives same results in guest as in host


== NFS-server in KVM-Alpine ==
I have a request to run a SIP server for a couple of users.<br/>
I'm doing it in some LXC accessed trough an openVPN from Jolla phones.


=== nfs-client on bare metal AL ===
== New rollout of our infra ==


=== nfs-client in KVM AL ===
This week, we will upgrade some hardware and also redo all the infrastructure based on the fresh 3.3 serie.


=== nfs-client in KVM debian ===
The compute nodes will run (on baremetal) with mdadm, openvswitch, qemu, consul, collectd, screen (maybe tmux) and openssh.


=== nfs-client in LXC AL (on bare metal AL) ===
The storage nodes will run a CEPH cluster (unfortunately not based on AL).


=== nfs-client in LXC AL (in KVM AL) ===
Everything else will run in various KVM on the compute nodes.


=== nfs-client in LXC debian (in KVM AL) ===
First, let's check if the needed package are available in the basic ISOs. If yes we will be able to run from USB keys. If not we will need to have sys install on the HDD...

Latest revision as of 01:56, 28 August 2023

How to automate KVM creation

How to emulate USB stick with KVM.

Starting_AL_from_network

How to set up a PXE environement.

Building_a_complete_infrastucture_with_AL

From first repo (boot media):

AlpineLinux dhcpd tftp-hpa syslinux mkinitfs nfs-utils darkhttpd rsync openssh openvswitch screen qemu-system-X86_64 qemu-img gptfdisk parted mdadm lvm2 nbd xfsprogs e2fsprogs multipath consul dnsmasq vim collectd collectd-network git syslog-ng envconsul consul-template xnbd ceph lxc lxc-templates xfsprogs gptfdisk e2fsprogs multipath wipe tcpdump curl openvpn fsconsul

and all dependecies...

will build a custom ISO with that list...

About NFS

NFS is now working with AL. Both as server and client with the nfs-utils package.
However, to use NFS as client in some LXC does not seems to work yet as shown below 

nfstest:~# mount -t nfs -o ro 192.168.1.149:/srv/boot/alpine /mnt
mount.nfs: Operation not permitted
mount: permission denied (are you root?)
nfstest:~# tail /var/log/messages 
Apr  4 10:05:59 nfstest daemon.notice rpc.statd[431]: Version 1.3.1 starting
Apr  4 10:05:59 nfstest daemon.warn rpc.statd[431]: Flags: TI-RPC 
Apr  4 10:05:59 nfstest daemon.warn rpc.statd[431]: Failed to read /var/lib/nfs/state: Address in use
Apr  4 10:05:59 nfstest daemon.notice rpc.statd[431]: Initializing NSM state
Apr  4 10:05:59 nfstest daemon.warn rpc.statd[431]: Failed to write NSM state number: Operation not permitted
Apr  4 10:05:59 nfstest daemon.warn rpc.statd[431]: Running as root.  chown /var/lib/nfs to choose different user
nfstest:~# ls -l /var/lib/nfs
total 12
-rw-r--r--    1 root     root             0 Nov 10 15:43 etab
-rw-r--r--    1 root     root             0 Nov 10 15:43 rmtab
drwx------    2 nobody   root          4096 Apr  4 10:05 sm
drwx------    2 nobody   root          4096 Apr  4 10:05 sm.bak
-rw-r--r--    1 root     root             4 Apr  4 10:05 state
-rw-r--r--    1 root     root             0 Nov 10 15:43 xtab

msg from ncopa """ dmesg should tell you that grsecurity tries to prevent you to do this.

grsecurity does not permit the syscall mount from within a chroot since that is a way to break out of a chroot. This affects lxc containers too.

I would recommend that you do the mouting from the lxc host in the container config with lxc.mount.entry or similar.

https://linuxcontainers.org/lxc/manpages/man5/lxc.container.conf.5.html#lbAR

If you still want disable mount protection in grsecurity then you can do that with: echo 0 > /proc/sys/kernel/grsecurity/chroot_deny_mount """

this is not working with 

lxc.mount.entry=nfsserver:/srv/boot/alpine mnt nfs nosuid,intr 0 0

on the host machine with all nfs modules and helper software installed and loaded. 

backend:~# lxc-start -n nfstest
lxc-start: conf.c: mount_entry: 2049 Invalid argument - failed to mount
'nfsserver:/srv/boot/alpine' on '/usr/lib/lxc/rootfs/mnt'
lxc-start: conf.c: lxc_setup: 4163 failed to setup the mount entries for
'nfstest'
lxc-start: start.c: do_start: 688 failed to setup the container
lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 2
lxc-start: start.c: __lxc_start: 1080 failed to spawn 'nfstest'

Nor with 

echo 0 > /proc/sys/kernel/grsecurity/chroot_deny_mount

on the host machine with all nfs modules and helper software installed and loaded which does'nt work either.

To find a proper way to use NFS shares from AL LXC is an important topic in order to be able to, for instance, load balance web servers sharing contents uploaded by users.

Next step will be to have HA for the NFS server itself (with only AL machines).

About NBD

NBD is now in edge/testing thanks to clandmeter.

we now use xnbd ^^

Also we are still looking after the right solution to backup NBD as a whole (versus by it's content) while in use. dd|nc is the used way nowadays.

About consul

nothing yet but big hopes ^^
I'm lurking IRC about it ;)

We plan to use it's dynamic DNS feature, it's hosts listing, services inventory, events, k/v store...
and even semi high-availability for our PXE infrastructure the consul leader being the active PXEserver and other consul server are dormant PXEservers.
All config scripts adapted to pull values out of consul k/v datastore based on profiles found out of consul various lists.
As the key for dhcpd and PXEboot is the hwaddr, it will become our uuid for LAN and consul too.
We are very exited by consul capacities!
Will be avid tester!

Open questions:

  1. What memory footprint is needed?
  2. What about dynamycally adapt quorum size?
  3. Are checks possible triggers? 
    • consul watch -prefix type -name name /path/to/executable
    • consul event [options] -name name [payload]
  4. What best practice to store etc configurations?

log of experimentation at User_talk:Jch/consul

About CEPH

CEPH is supposed to sovle the problem of high availability for the data stores, be it block devices (disks) or character devices (files).

The actual situation is not satisfactory.

We are very exited by CEPH capacities!
Will be avid tester!

The Alpine kernel has now RBD modules compiled.

We will build a CEPH cluster out of 3 Ubuntu LTS and use AL boxes as client if possible (to launch qemu instances directly from RBD). If not, we then will attach RBD and reexport them with xNBD inside a debian KVM.

About Docker

not a lot of information on the Docker page yet ...

About E-MailRelay

E-MailRelay is a simple SMTP proxy and store-and-forward message transfer agent (MTA).
See http://emailrelay.sourceforge.net/

It compiles fine on AL. 

apk update
apk add subversion alpine-sdk
svn checkout svn://svn.code.sf.net/p/emailrelay/code/trunk emailrelay-code
cd emailrelay-code
./configure --prefix=/usr
make
make install
apk del subversion alpine-sdk
apk add libgcc libstdc++
emailrelay --help

But I still have issues to properly build a package because it wants to install some stuff in <PREFIX>/libexec...
(And I also need to separate -doc, -test, -extra and optionnaly -gui in subpackages I guess)

About X2Go

x2goserver

I did prepare x2goserver and nx-libs packages.

x2goclient

lrelease-qt4 x2goclient.pro
/bin/bash: lrelease-qt4: command not found
Makefile:39: recipe for target 'build_client' failed

Dunno where to find that...

My laptop setup

AL 3.3 with +/etc/inittab+ 

tty5::respawn:/usr/bin/su - jch mcabber
tty6::respawn:/usr/bin/su - jch tmux
tty7::respawn:/usr/bin/su - jch startx

and +~/.xinitrc+ 

  1. !/bin/sh


exec chromium-browser --no-sandbox

About gpve

gvpe
http://software.schmorp.de/pkg/gvpe.html

Plan to use it to interconnect about 5 sites.

About freeswitch

I have a request to run a SIP server for a couple of users.
I'm doing it in some LXC accessed trough an openVPN from Jolla phones.

New rollout of our infra

This week, we will upgrade some hardware and also redo all the infrastructure based on the fresh 3.3 serie.

The compute nodes will run (on baremetal) with mdadm, openvswitch, qemu, consul, collectd, screen (maybe tmux) and openssh.

The storage nodes will run a CEPH cluster (unfortunately not based on AL).

Everything else will run in various KVM on the compute nodes.

First, let's check if the needed package are available in the basic ISOs. If yes we will be able to run from USB keys. If not we will need to have sys install on the HDD...

Retrieved from "https://wiki.alpinelinux.org/w/index.php?title=User_talk:Jch&oldid=24778"