Some notes on setup /test

Umount, Unmap block device and removal [root@client ~]# umount /mnt/ceph-block-device/ [root@client ~]# df Filesystem               1K-blocks     Used Available Use% Mounted on /dev/mapper/centos-root    8374272 4076800    4297472   49% / devtmpfs                    925800        0     925800    0% /dev tmpfs                       941728        0     941728    0% /dev/shm tmpfs                       941728    17268     924460    2% /run tmpfs                       941728        0     941728    0% /sys/fs/cgroup /dev/vda1                  1038336   182396     855940   18% /boot /dev/rbd0                 15718400   238416   15479984    2% /mnt/ceph-disk tmpfs                       188348        4     188344    1% /run/user/42 tmpfs                       188348       40     188308    1% /run/user/0 [root@client ~]# rbd unmap --image seeshiang [root@client ~]# rbd showmapped id pool image snap device     0   rbd   rbd1   -     /dev/rbd0 [root@clien

The client machine will require Ceph keys to access the Ceph cluster. A better way is to create a new Ceph user with separate keys and allow access to specific Ceph pools. In our case, we will create a Ceph user, client.rbd, with access to the RBD pool. Generate client.rbd key then copy to the /etc/ceph.client.rbd.keyring file [root@client ~]# ceph auth get-or-create client.rbd mon 'allow r' osd 'allow class-read object_prefix rbd_children, allow rwx pool=rbd' [client.rbd] key = AQDC3NZavOD4HxAAPtyG/qEnU9Gh2rwkzcTPFA== [root@client ~]# [root@client ~]# cat /etc/ceph/ceph.client.rbd.keyring [client.rbd] key = AQDC3NZavOD4HxAAPtyG/qEnU9Gh2rwkzcTPFA== [root@client ~]# Create pool and list the pool name [root@client ~]# rbd create rbd1 --size 10240 --name client.rbd [root@client ~]# rbd ls --name client.rbd rbd1 [root@client ~]# rbd ls -p rbd --name client.rbd rbd1 [root@client ~]# rbd list --name client.rbd rbd1 [root@

Spacewalk channels (?) v2.7 not able to honor proxy ? Friday, March 9, 2018 9:48 AM Channel is a collection of software RPM packages and may contain packages from a distribution. It is for clients to subscribe , download, update/install packages. It is linked to upstream and may have linked to several repositories. Subscribed system only can install/update packages through its satellite channels. Create base channel. Created the test channel Create repository for base channel Created the CentOS7 x86_64 repository label with URL pointed to my nearest stable location which I choose Singapore site. Attach the created CentOS7 x86_64 repo to the base channel earlier created. Select the CentOS7 x86_64 channels and update repositories. Tried to sync the packages from the upstream server. ( http://mirror.nus.edu.sg/centos/   ) Version 2.7 having problem on the reposync, seems to be unable to honor the http proxy

Spacewalk  is an open source  Linux  systems management solution.  Setup/test of spacewalk server /channel on centos 7.4   ( on kvm ) Environment HostName : spacewalk.local IP Address: 192.168.122.105/24 OS: CentOS Linux release 7.4 OS disk ~ 10Gb Data disk ~20Gb RAM: ~4Gb Setup repositories To Configure required repositories on our system. To Setup Spacewalk repository to get the latest of Spacewalk version, v2.7. [root@neptune ~]# rpm -Uvh http://yum.spacewalkproject.org/2.7/RHEL/7/x86_64/spacewalk-repo-2.7-2.el7.noarch.rpm Retrieving http://yum.spacewalkproject.org/2.7/RHEL/7/x86_64/spacewalk-repo-2.7-2.el7.noarch.rpm warning: /var/tmp/rpm-tmp.JdAPjx: Header V4 DSA/SHA1 Signature, key ID b8002de1: NOKEY Preparing...                           ################################# [100%] Updating / installing...    1:spacewalk-repo-2.7-2.el7          ################################# [100%] [root@neptune ~]# Change Java rep