BMC Discovery on CentOS 7 compared to previous versions
This section introduces the main system level differences between BMC Discovery versions before 11.3 and 11.3 running on CentOS 7, and how those changes affect BMC Discovery users. Your appliance will only be running on CentOS 7 if you installed BMC Discovery 11.3 as a new version. Upgrades from versions earlier than version 11.3 run CentOS 6.
BMC Discovery 11.3 patch 6 is available on CentOS 7 and Red Hat Enterprise Linux 7 (RHEL 7). BMC Discovery 11.3 patch 6 on RHEL 7 is a separately licensed release.
CentOS 7 and RHEL 7
Functionally RHEL 7 is no different from CentOS 7. In this page references to CentOS 7 apply equally to RHEL 7.
To determine whether your appliance is running on CentOS 6, CentOS 7, or RHEL 7, check the footer of any UI page. The BMC Discovery version number, build number, and OS version are provided on the bottom line.
Alternatively, from the command line, enter:
tideway@appliance01 ~]$ cat /etc/redhat-release
- For CentOS 6 the output begins:
CentOS release 6.x
For CentOS 7 the output begins:
CentOS Linux release 7.x
For RHEL 7 the output begins:
Red Hat Enterprise Linux Server release 7.x
Service control under systemd
CentOS 7 uses the
systemd suite, which replaces the init system used in earlier versions. Other than a different boot routine, the main change visible to BMC Discovery users, is the way in which services are controlled.
In CentOS 7, the only services that require you to use system level commands to control them are
omniNames, and occasionally,
appliance service still exists, but is only used by the system at boot.
They are used in the following manner:
$ sudo systemctl stop|start|restart|status cluster ... $ sudo systemctl stop|start|restart|status omniNames
For example, to start the cluster service:
$ sudo systemctl start cluster
To stop the cluster service:
$ sudo systemctl stop cluster
To restart the
$ sudo systemctl restart omniNames
All of the BMC Discovery application services in 11.3 on CentOS 7 are controlled using the
tw_service_control utility. For complete information on its usage, see the
tw_service_control documentation. The
tw_service_control utility enables you to start and stop individual application services, such as the Application Server service or the External API service, or all services as one, which is the equivalent of the
tideway service in versions running on CentOS 6.
In an 11.2 appliance you would restart the security service using:
On an 11.3 appliance running on CentOS 7, you should enter:
Or to restart all services (the equivalent of the tideway service in release before 11.3), you should enter:
The tideway service
The tideway service no longer exists in BMC Discovery 11.3 running on CentOS 7 systems. The equivalent is achieved using
tw_service_control without specifying a service. If you do inadvertently enter a "service" command, the following error message is returned:
Scripts that interact with BMC Discovery services
If you have written scripts to interact with BMC Discovery services, you should modify those scripts to use the
Other CentOS 7 changes
- The first network interface is no longer special, and no longer needs to be called
eth0. The interface name might be something like
enp2s4, though this name depends on the virtualization software or the hardware platform.
- You can also have more than one network interface.
- The Samba client that is used for backing up the appliance uses SMB 2 by default on CentOS 7.
- The CentOS 6 client does not support SMB 2 for the BMC Discovery appliance backup.
- If you are running 11.3 on CentOS 7 and your server supports SMB 2, it will be used for appliance backups.
- The performance of CentOS 7 compared with CentOS 6 is fundamentally the same.
ntpdas the system's Network Time Protocol (NTP) client. The only changes you are likely to see are
chronydin the appliance baseline or in system logs.
- Disk partitioning has changed for kickstart installations on physical and virtual hardware and on virtual appliances:
/reservedis an empty partition. It is for future use and must not be used, although it must be provisioned.
/usr/tidewayis now a dedicated partition.
tmpfsdevice. It is not persistent across reboots. It is stored in memory, so do not attempt to store large files there as that will consume RAM.
The DVD kickstart installation is different from previous versions.
The installation provides the opportunity to customize the installed packages. Do not do this. The configuration of the appliance is tightly controlled, which provides better supportability and lower costs, while maintaining a configuration optimized for the particular requirements of the BMC Discovery application. Additional packages may compromise the security, performance, and stability of the appliance, and will prevent the installation of operating system upgrades.
BMC Discovery uses the Apache web server. 11.3 appliances running on CentOS 7 use Apache version 2.4.
The HTTPS configuration in the BMC Discovery HTTPS Configuration page now overwrites