Sponsored Content
Operating Systems Linux Linux Kernel Config Scopes within VM or Hypervisor Post 303030901 by freedombird9 on Tuesday 19th of February 2019 01:35:40 AM
Old 02-19-2019
Linux Kernel Config Scopes within VM or Hypervisor

In production we're going to deploy a redis server and need to set the overcommit_memory and disable Transparent Huge Pages in Kernel.

The issue is currently we only have one giant server, and it is to be shared by many other apps. We only want those kernel configs in the redis server. I wonder if we can achieve it by spinning up a dedicated VM for redis. Doing so in docker certainly doesn't make sense. My questions are:
  • Will those Kernel configs take actual effect in the redis VM even if the host OS doesn't have the same configs? I doubt it since the hardware resource is allocated by the host machine in the end.
  • Will the kernel config in the redis VM affect other VMs that run other apps? I think it won't, just want to confirm.
  • To achieve the goal, what kind of VM or hypervisor should we use?

If there's no way to do it in VM, is having a separate server (hardware) for redis the only way to go?

Last edited by RavinderSingh13; 02-19-2019 at 06:47 AM..
 

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Installation of Xen hypervisor

I want the steps to install Xen hypervisor (with Domain 0) on linux kernel 2.6.38.8 on ubuntu.Actually there are many links for the steps but each link shows differenet commands.So I want a precise note containing the steps for installation of Xen:wall: (0 Replies)
Discussion started by: pratibha
0 Replies

2. UNIX for Advanced & Expert Users

.config for a minimal kernel

I need to install minimal kernel. the machine cpu is intel, it should support usb and wireless. and.. nothing else. The system is set up to run qt programs. Can anyone having the same experience send me the .config file please. (1 Reply)
Discussion started by: dr_mabuse
1 Replies

3. Hardware

Does hypervisor(virtualbox) can own a specific hardware

Hi, I would like to ask about the hypervisor, in my case im currently using oracle virtualbox, If a certain VM machine can own a single device or card (ex. pci audio mic/speaker card). i know in virtual box features, USB FILTER for usb device but how about the expansion card like audio in/out... (1 Reply)
Discussion started by: jao_madn
1 Replies
redis_selinux(8)					       SELinux Policy redis						  redis_selinux(8)

NAME
redis_selinux - Security Enhanced Linux Policy for the redis processes DESCRIPTION
Security-Enhanced Linux secures the redis processes via flexible mandatory access control. The redis processes execute with the redis_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier. For example: ps -eZ | grep redis_t ENTRYPOINTS
The redis_t SELinux type can be entered via the redis_exec_t file type. The default entrypoint paths for the redis_t domain are the following: /usr/sbin/redis-server PROCESS TYPES
SELinux defines process types (domains) for each process running on the system You can see the context of a process using the -Z option to ps Policy governs the access confined processes have to files. SELinux redis policy is very flexible allowing users to setup their redis pro- cesses in as secure a method as possible. The following process types are defined for redis: redis_t Note: semanage permissive -a redis_t can be used to make the process type redis_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. BOOLEANS
SELinux policy is customizable based on least access required. redis policy is extremely flexible and has several booleans that allow you to manipulate the policy and run redis with the tightest access possible. If you want to allow all daemons to write corefiles to /, you must turn on the daemons_dump_core boolean. Disabled by default. setsebool -P daemons_dump_core 1 If you want to enable cluster mode for daemons, you must turn on the daemons_enable_cluster_mode boolean. Enabled by default. setsebool -P daemons_enable_cluster_mode 1 If you want to allow all daemons to use tcp wrappers, you must turn on the daemons_use_tcp_wrapper boolean. Disabled by default. setsebool -P daemons_use_tcp_wrapper 1 If you want to allow all daemons the ability to read/write terminals, you must turn on the daemons_use_tty boolean. Disabled by default. setsebool -P daemons_use_tty 1 If you want to deny any process from ptracing or debugging any other processes, you must turn on the deny_ptrace boolean. Enabled by default. setsebool -P deny_ptrace 1 If you want to allow all domains to use other domains file descriptors, you must turn on the domain_fd_use boolean. Enabled by default. setsebool -P domain_fd_use 1 If you want to allow all domains to have the kernel load modules, you must turn on the domain_kernel_load_modules boolean. Disabled by default. setsebool -P domain_kernel_load_modules 1 If you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. Enabled by default. setsebool -P fips_mode 1 If you want to enable reading of urandom for all domains, you must turn on the global_ssp boolean. Disabled by default. setsebool -P global_ssp 1 If you want to allow confined applications to use nscd shared memory, you must turn on the nscd_use_shm boolean. Disabled by default. setsebool -P nscd_use_shm 1 PORT TYPES
SELinux defines port types to represent TCP and UDP ports. You can see the types associated with a port by using the following command: semanage port -l Policy governs the access confined processes have to these ports. SELinux redis policy is very flexible allowing users to setup their redis processes in as secure a method as possible. The following port types are defined for redis: redis_port_t Default Defined Ports: tcp 6379 MANAGED FILES
The SELinux process type redis_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. Note the processes UID still need to have DAC permissions. cluster_conf_t /etc/cluster(/.*)? cluster_var_lib_t /var/lib/pcsd(/.*)? /var/lib/cluster(/.*)? /var/lib/openais(/.*)? /var/lib/pengine(/.*)? /var/lib/corosync(/.*)? /usr/lib/heartbeat(/.*)? /var/lib/heartbeat(/.*)? /var/lib/pacemaker(/.*)? cluster_var_run_t /var/run/crm(/.*)? /var/run/cman_.* /var/run/rsctmp(/.*)? /var/run/aisexec.* /var/run/heartbeat(/.*)? /var/run/cpglockd.pid /var/run/corosync.pid /var/run/rgmanager.pid /var/run/cluster/rgmanager.sk redis_log_t /var/log/redis(/.*)? redis_var_lib_t /var/lib/redis(/.*)? redis_var_run_t /var/run/redis(/.*)? /var/run/redis.sock root_t / /initrd FILE CONTEXTS
SELinux requires files to have an extended attribute to define the file type. You can see the context of a file using the -Z option to ls Policy governs the access confined processes have to these files. SELinux redis policy is very flexible allowing users to setup their redis processes in as secure a method as possible. EQUIVALENCE DIRECTORIES redis policy stores data with multiple different file context types under the /var/run/redis directory. If you would like to store the data in a different directory you can use the semanage command to create an equivalence mapping. If you wanted to store this data under the /srv dirctory you would execute the following command: semanage fcontext -a -e /var/run/redis /srv/redis restorecon -R -v /srv/redis STANDARD FILE CONTEXT SELinux defines the file context types for the redis, if you wanted to store files with these types in a diffent paths, you need to execute the semanage command to sepecify alternate labeling and then use restorecon to put the labels on disk. semanage fcontext -a -t redis_exec_t '/srv/redis/content(/.*)?' restorecon -R -v /srv/myredis_content Note: SELinux often uses regular expressions to specify labels that match multiple files. The following file types are defined for redis: redis_exec_t - Set files with the redis_exec_t type, if you want to transition an executable to the redis_t domain. redis_initrc_exec_t - Set files with the redis_initrc_exec_t type, if you want to transition an executable to the redis_initrc_t domain. redis_log_t - Set files with the redis_log_t type, if you want to treat the data as redis log data, usually stored under the /var/log directory. redis_unit_file_t - Set files with the redis_unit_file_t type, if you want to treat the files as redis unit content. redis_var_lib_t - Set files with the redis_var_lib_t type, if you want to store the redis files under the /var/lib directory. redis_var_run_t - Set files with the redis_var_run_t type, if you want to store the redis files under the /run or /var/run directory. Paths: /var/run/redis(/.*)?, /var/run/redis.sock Note: File context can be temporarily modified with the chcon command. If you want to permanently change the file context you need to use the semanage fcontext command. This will modify the SELinux labeling database. You will need to use restorecon to apply the labels. COMMANDS
semanage fcontext can also be used to manipulate default file context mappings. semanage permissive can also be used to manipulate whether or not a process type is permissive. semanage module can also be used to enable/disable/install/remove policy modules. semanage port can also be used to manipulate the port definitions semanage boolean can also be used to manipulate the booleans system-config-selinux is a GUI tool available to customize SELinux policy settings. AUTHOR
This manual page was auto-generated using sepolicy manpage . SEE ALSO
selinux(8), redis(8), semanage(8), restorecon(8), chcon(1), sepolicy(8) , setsebool(8) redis 14-06-10 redis_selinux(8)
All times are GMT -4. The time now is 09:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy