There are two entities that can be logged in to on the system, a Service Processor and an Oracle Solaris domain. You initially log in to the Service Processor using a serial connection from a terminal device.
A unique login account with the user name of default exists on the Service Processor. This account is unique in the following ways:. After initial configuration, you can log in to the Service Processor using a serial connection or an Ethernet connection. You can also log in to a domain directly using an Ethernet connection to access the Oracle Solaris OS. When a user logs in, the user establishes a session. Authentication and user privileges are valid only for that session.
When the user logs out, that session ends. To log back in, the user must be authenticated once again, and will have the privileges in effect during the new session. See Privileges for information on privileges. After multiple XSCF login failures, no further login attempts are allowed for a certain amount of time.
To set the lockout period, use the setloginlockout 8 command. To view the lockout period, use the showloginlockout 8 command. For more information, see the setloginlockout 8 and showloginlockout 8 man pages. A user account is a record of an individual user that can be verified through a user name and password. When you initially log in to the system, add at least one user account with a minimum of one privilege, useradm.
This user with useradm privileges can then create the rest of the user accounts. For a secure log in method, enable SSH service. The user accounts are assigned privileges; each privilege allows the user to execute certain XSCF commands. By specifying privileges for each user, you can control which operations each XSCF user is allowed to perform. On its own, a user account has no privileges. To obtain permission to run XSCF commands and access system components, a user must have privileges. User passwords are authenticated locally by default unless you are using an LDAP server for authentication.
Site-wide policies, such as password nomenclature or expiration dates, make passwords more difficult to guess. You can configure a password policy for the system using the setpasswordpolicy command. The setpasswordpolicy command describes the default values for a password policy. Privileges allow a user to perform a specific set of actions on a specific set of components.
Those components can be physical components, domains, or physical components within a domain. These are the only privileges allowed in the server. You cannot define additional privileges.
When the local privilege for a user is set to none , that user has no privileges, even if privileges for that user are defined in LDAP. Make sure you know what toolstack you want before you get started. XAPI is one of the toolstacks that could control a Xen based hypervisor. This name is also used by the python library that is a client for XAPI. For more information and product downloads, visit xenserver. A Xen host runs a number of virtual machines, VMs, or domains the terms are synonymous on Xen.
One of these is in charge of running the rest of the system, and is known as domain 0, or dom0. It is the first domain to boot after Xen, and owns the storage and networking hardware, the device drivers, and the primary control software.
Any other VM is unprivileged, and is known as a domU or guest. This gives a level of security isolation between the privileged system software and the OpenStack software much of which is customer-facing. This architecture is described in more detail later. This refers to the interaction between Xen, domain 0, and the guest VM's kernel.
PV guests are aware of the fact that they are virtualized and will co-operate with Xen and domain 0; this gives them better performance characteristics. HVM guests are not aware of their environment, and the hardware has to pretend that they are running on an unvirtualized machine. HVM guests do not need to modify the guest operating system, which is essential when running Windows. A basic OpenStack deployment on a XAPI-managed server, assuming that the network provider is nova-network, looks like this:.
OpenStack VM: The Compute service runs in a paravirtualized virtual machine, on the host under management. Each host runs a local instance of Compute. It is also running an instance of nova-network. It usually means binding those services to the management interface.
Tenant network: controlled by nova-network, this is used for tenant traffic. The networks shown here must be connected to the corresponding physical networks within the data center.
In the simplest case, three individual physical network cards could be used. It is also possible to use VLANs to separate these networks. Please note, that the selected configuration must be in line with the networking model selected for the cloud. In case of VLAN networking, the physical channels have to be able to forward the tagged traffic. What is Xen? Before you can run OpenStack with XenServer, you must install the hypervisor on an appropriate server.
Xen is a type 1 hypervisor: When your server starts, Xen is the first software that runs. At the end of the conversion, the cell disk and grid disk configuration of the storage cells are the same as they were at the beginning of the conversion. The management domain will use a small portion of the system resources on each database server. The following procedure describes how to show running domains:.
The following procedure describes how to monitor a user domain console:. The following procedure describes how to start a user domain:. To see Oracle Linux boot messages during user domain startup, connect to the console during startup using the -c option. By default, when you create a user domain, it is configured to automatically start when the management domain is started.
You can enable and disable this feature as needed. The following procedure describes how to enable a user domain to start automatically when the management domain is started:. In the preceding command, UUID is the unique domain identifier and DomainName is the fully qualified name of the domain that you are acting on. The following procedure describes how to disable a user domain from automatically starting when the management domain is started:. In the preceding command, DomainName is the fully qualified name of the domain that you are acting on.
The following procedure describes how to shut down a user domain from within a user domain:. The following procedure describes how to shut down a user domain from within a management domain:. Use the -w option so that the xm command waits until the domain shutdown completes before returning.
The xm shutdown command performs the same orderly shutdown as running shutdown -h now within the user domain. To shut down all user domains within the management domain, use the following command:. Backing up and restoring Oracle databases on Oracle VM user domains is the same as backing up and restoring Oracle databases on physical nodes.
The following procedure describes how to modify the memory allocated to a user domain:. If you are decreasing the amount of memory allocated to a user domain, you must first review and adjust the SGA size of databases running in the user domain and the corresponding huge pages operating system configuration. Failing to do so may result in user domain that cannot start because too much memory is reserved for huge pages when the Linux operating system attempts to boot.
See My Oracle Support note This operation requires user domain restart. It is not supported to modify memory allocation using the xm mem-set command. When assigning free memory to a user domain, approximately 1 to 2 percent of free memory is used for metadata and control structures. Therefore, the amount of memory increase possible is 1 to2 percent less than free memory value. If the memory and maxmem parameters are not identical values, then InfiniBand network interfaces are not configured during user domain start, which prevents proper Oracle CRS and database startup.
All actions to modify the number of vCPUs allocated to a user domain are performed in the management domain. The number of vCPUs allowed for a user domain may be changed dynamically to a lower value or to a higher value provided it does not exceed the setting of maxvcpus parameter for the user domain.
However, over-committing CPUs should be done only when competing workloads for oversubscribed resources are well understood and concurrent demand does not exceed physical capacity. The following procedure describes how to modify the number of virtual CPUs allocated to a user domain:.
Use the following command to determine the current setting of vCPUs configured and online for a user domain:. In the preceding command, DomainName is the name of the user domain. The output from the command indicates the maximum number of vCPUs for the user domain is 4, and the current number of online vCPUs is 2. This user domain may have the number of online vCPUs adjusted to any value not greater than the vcpus parameter while the user domain remains online.
The user domain must be taken offline to increase the number of online vCPUs to a value higher than the vcpus parameter. Determine the currently allocated number of vCPUs for the user domain using the following command:. Determine the current settings of the vcpus parameter using the following command:. If the preferred number of vCPUs is less than or equal to the value of the vcpus parameter, then run the following command to increase the number of online vCPUs.
If the preferred number of vCPUs is greater than the value of the vcpus parameter, then the user domain must be taken offline to increase the number of online vCPUs to a value higher than the vcpus parameter. Do the following:. Note: By default a user domain will online the number of vCPUs configured via the vcpus parameter. If you want a user domain to start with some vCPUs offline, then add the maxvcpus parameter to vm.
Set the vcpus parameter to the number of vCPUs to online when the user domain starts. For example, to start a user domain with 2 vCPUs online and to allow an additional 6 vCPUs to be added to the user domain while it remains online, use the following settings in vm.
This procedure describes how to add a new LVM disk to a user domain to increase the amount of usable LVM disk space in a user domain. This procedure is done so that the size of a file system or swap LVM partition can be increased. This procedure is performed while the system remains online. This procedure requires steps be run in the management domain Domain-0 , and in the user domain. The parted mkpart command may report the following message.
This message can be ignored:. In the following example, the user domain UUID is 49ffddce4efe43fd0c61c87bba In the following example, the new disk UUID is 0d56da6ac97ef81c The UUID for user domain dm01db01vm01 is 49ffddce4efe43fd0c61c87bba The UUID for the new disk image is 0d56da6ac97ef81c The following is an example of an original disk parameter entry in the vm. One partition is active and mounted.
The other partition is inactive and used as a backup location during upgrade. The size of both system partitions must be equal. The free space is used for the LVM snapshot created by the dbnodeupdate. The volume group must contain enough free space to increase the size of both system partitions, and maintain at least 1 GB of free space for the LVM snapshot created by the dbnodeupdate. If there is not sufficient free space in the volume group, then add a new disk to LVM.
In the preceding command, size is the amount of space to be added to the logical volume. The amount of space added to each system partition must be the same. If the output shows there is less than 1 GB of free space, then neither the logical volume nor file system should be extended.
You can increase the size of the Oracle Grid Infrastructure or Oracle Database home file system in a user domain. The Oracle Grid Infrastructure software home and the Oracle Database software home are created as separate disk image files in the management domain.
The disk image files are attached to the user domain automatically during virtual machine startup, and mounted as separate, non-LVM file systems in the user domain. The empty disk image size is the size to extend the file system. The last command removes the empty disk image after appending to the database home disk image.
If the command shows that there is less than 1 GB of free space, then neither the logical volume nor file system should be extended. If you are using a release of Oracle Exadata System Software release 18c In the example below, dm01db01 is the name of the management domain , and dm01db01vm01 is a user domain.
Note that the last line reads " Layout: DOM0 ". If reclaimdisks. This may take several hours to complete. The example below shows that it took approximately 7 hours. After all user domain s are shut down, only Domain-0 the management domain should be listed.
Check the size of the disk against the end of the third partition. If you see a request to fix the GPT, respond with F. The partition table shown above lists partition 2 as ending at sector and disk size as sectors. You will use these values in step 7. The tunefs. If you are using Oracle Exadata System Software release Check the size of the disk against the end of the second partition.
The partition table shown above lists partition 2 as ending at sector s and disk size as If you are using a release of Oracle Exadata System Software starting with release If you encounter this error, restart the Exadata database server to apply the changes in the partition table. Note that the size of the file system is still the same, 1. The output for sda3 should now be larger compared to the output observed earlier in step 4. You can do this while the file system is mounted and processes are running.
Note the updated file system size, compared to the value in step 4. Before preforming the steps in this section, the new database servers should have been set up as detailed in Adding a New Database Server to the Cluster , including the following:. Each management domain has been imaged or patched to the same image in use on the existing database servers. Ensure that the System. If any nodes are missing the System.
The steps here show how to add a new management domain node called exa01adm03 that will have a new user domain called exa01adm03vm The existing cluster has management domain nodes named exa01adm01 and exa01adm02 and user domain nodes named exa01adm01vm01 and exa01adm02vm At this point we have a new XML file that has the new compute node management domain in the configuration.
This file will be used by the subsequent steps. Save a copy of these files in a safe place since they now reflect the changes made to your cluster. A user domain can be created without Oracle Grid Infrastructure and Oracle Database installed on the system. The new user domain has the following characteristics:. The following procedure creates a user domain without Oracle Grid Infrastructure and Oracle Database installed:.
Allocate new, unused, IP addresses and host names for the new user domain. Ensure the intended InfiniBand network IP addresses are unused by using the ping command for each address. The ibhosts command cannot be used to determine all InfiniBand network IP addresses in use because it does not contain entries for user domains.
The exadata. For example, when exadata. In the management domain, copy an existing XML configuration file from a deployed user domain to a new file name using the following command:. In the preceding command, existingDomainName -vm. In the following example, the configuration file for user domain "dm01db01vm01" is copied to nondbdomain-vm.
The target database server must have access to the same Oracle Exadata Storage Server s. The target database server must have sufficient free resources CPU, memory, and local disk storage to operate the user domain. Over-committing CPUs can be done only when the competing workloads for over-subscribed resources are well understood and the concurrent demand does not exceed physical capacity.
Copying disk images to the target database server may increase space allocation of the disk image files because the copied files are no longer able to benefit from the disk space savings gained by using OCFS2 reflinks. The following procedure moves a user domain to a new database server in the same Oracle Exadata System Software configuration.
All steps in this procedure are performed in the management domain. In the following examples, replace DomainName with the name of the domain. An example of the user domain UUID is 49ffddce4efe43fd0c61c87bba In an Oracle VM deployment, you need to back up the management domain dom0 and the user domains domU :. This procedure describes how to take a snapshot-based backup of the management domain, dom0.
If you follow the manual procedure described here, then you have to perform all these tasks manually. The values shown in the steps below are examples. All steps must be performed as the root user.
The destination should reside outside of the local machine, such as a writable NFS location, and be large enough to hold the backup tar file s. For non-customized partitions, the space needed for holding the backup is around 60 GB. If this volume is present, then remove the volume to make space for the snapshot. This method provides a more robust and a comprehensive backup than method 2 or 3. Method 3 provides a quicker and an easier backup method, especially in role separated environments.
Method 1 is best-suited for when a management domain dom0 administrator is responsible for user domain backups. Method 2 is best-suited for when a management domain dom0 administrator is responsible for user domain backups.
This method backs up a single user domain using snapshot-based backup from inside the user domain. The backup destination should reside outside of the local machine, such as a writable NFS location, and be large enough to hold the backup. The space needed for the backup is proportional to the number of Oracle VMs deployed on the system, up to a maximum space of about 1.
For example:. This allows for restore operations if the management domain Dom0 is permanently lost or damaged. Parent topic: Backing up the User Domains. You can take a snapshot-based backup of a user domain from inside the user domain, which can then be used to restore the user domain to a workable state.
Errors about failing to tar open sockets, and other similar errors, can be ignored. You can recover an Oracle VM from a snapshot-based backup when severe disaster conditions damage the Oracle VM , or when the server hardware is replaced to such an extent that it amounts to new hardware.
For example, replacing all hard disks leaves no trace of original software on the system. This is similar to replacing the complete system as far as the software is concerned. In addition, it provides a method for disaster recovery of the database servers using an LVM snapshot-based backup taken when the database server was healthy before the disaster condition.
The recovery procedures described in this section do not include backup or recovery of storage servers or the data in an Oracle Database. Oracle recommends testing the backup and recovery procedures on a regular basis. The recovery procedures use the diagnostics. At a high-level, the steps look like this:.
0コメント