For BMSs with Ascend 910 Pro B or Ascend 910 Premium NPU, install NPU driver 20.2.0.spc300 or later versions. NPU firmware is released with the driver. If you install the NPU driver or firmware again, you can only install a version no earlier than the current one.
+For Ascend BMSs, install NPU driver 20.2.0.spc300 or later versions. NPU firmware is released with the driver. If you install the NPU driver or firmware again, you can only install a version no earlier than the current one.
To query the NPU name, log in to the OS and run npu-smi info.
Ascend 910 A
+Ascend A
20.0.0, 20.1.0, 20.2.0
Ascend 910 B
+Ascend B
20.0.0, 20.1.0, 20.2.0
Ascend 910 Pro A
+Ascend Pro A
20.0.0, 20.1.0, 20.2.0
Ascend 910 Pro B
+Ascend Pro B
20.2.0.SPC300
Ascend 910 Premium A
+Ascend Premium A
20.2.0.SPC300
Installing and Upgrading Drivers and Firmware for Ascend 910 BMSs
+Installing and Upgrading Drivers and Firmware for Ascend BMSs
Upgrading Ascend 910 NPU Firmware
-You can upgrade the firmware of the Ascend 910 NPU for Atlas 800 (model 9000) training servers. This section uses the A800-9000-npu-firmware_x.x.x.run package as an example to describe how to upgrade NPU firmware.
+Upgrading the Ascend NPU Firmware
+You can upgrade the firmware of Ascend NPUs for Atlas 800 (model 9000) training servers. This section uses the A800-9000-npu-firmware_x.x.x.run package as an example to describe how to upgrade NPU firmware.
Procedure
- Obtain the software package A800-9000-npu-firmware_x.x.x.run by referring to Preparing for Upgrade.
- Log in to the Atlas 800 (model: 9000) training server as the root user.
- Upload A800-9000-npu-firmware_x.x.x.run to any directory in the OS, for example, /opt.
- Go to the directory where A800-9000-npu-firmware_x.x.x.run is stored.
cd /opt
diff --git a/docs/bms/image-creation-guide/en-us_topic_0000001163136429.html b/docs/bms/image-creation-guide/en-us_topic_0000001163136429.html index 539e43a5..e187604b 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0000001163136429.html +++ b/docs/bms/image-creation-guide/en-us_topic_0000001163136429.html @@ -17,7 +17,7 @@ useradd -g usergroup-d /home/username -m username- The password validity period is 90 days. You can change the password validity period in the /etc/login.defs file or by running the chage command. For details, see Configuring Password Aging.
Configuring Password Aging
For security purposes, run the chage command to set the validity period of a password.
+Configuring Password Expiry
For security purposes, run the chage command to set the validity period of a password.
The command is as follows:
chage [-m minimum days] [-M maximum days] [-d last day] [-I inactive] [-E expiration date] [-W warning days] user
Table 1 describes the parameters.
@@ -50,7 +50,7 @@ useradd -g usergroup-d /home/username -m username-E
Date on which the account is locked.
+Date when the account will expire.
-W
@@ -60,7 +60,7 @@ useradd -g usergroup-d /home/username -m username-l
Lists account aging information.
+Lists account expiry information.
4
Before the upgrade, ensure that the OS is running properly and the firmware and dependent drivers are properly loaded. Otherwise, reset the system before performing the upgrade. For details, see How Do I Check Whether the Device Is Running Properly?
+Before the upgrade, ensure that the OS is running properly and the firmware and dependent drivers are properly loaded. Otherwise, reset the system before performing the upgrade. For details, see How Do I Check Whether a Physical Server Is Running Properly?
5
@@ -43,7 +43,7 @@6
For an upgrade from an earlier version to NPU C72B050 or later, skip system reboot in Upgrading Ascend 910 NPU Firmware and system reboot in Upgrading the Ascend 910 NPU Driver. After the driver upgrade is complete, perform a restart.
+For an upgrade from an earlier version to NPU C72B050 or later, skip system reboot in Upgrading the Ascend NPU Firmware and system reboot in Upgrading the Ascend NPU Driver. After the driver upgrade is complete, perform a restart.
You can run the following command to check the NPU version:
/usr/local/Ascend/driver/tools/upgrade-tool --device_index -1 --component -1 --version
Upgrading the Ascend 910 NPU Driver
+Upgrading the Ascend NPU Driver
Scenarios
-You can upgrade the driver of the Ascend 910 NPU for Atlas 800 (model 9000) training servers.
+You can upgrade the driver of Ascend NPUs for Atlas 800 (model 9000) training servers.
This section uses the A800-9000-npu-driver_x.x.x_euleros2.8-aarch64.run package as an example to describe how to upgrade the NPU driver.
- Driver upgrade does not change the system username or password.
Installing a Windows OS and the VMTools Driver
-Scenarios
This section uses Windows Server 2008 R2 64-bit as an example to describe how to install Windows on an ECS.
+Scenarios
This section uses Windows Server 2019 64-bit as an example to describe how to install Windows on an ECS.
The installation procedure varies depending on the image file you use. Perform operations as prompted.
Set the time zone, KMS address, patch server, input method, and language based on service requirements.
Procedure
Do not stop or restart the ECS during the OS installation. Otherwise, the OS installation will fail.
- Install the Windows OS.
- Specify the parameters on the Install Windows page.Figure 1 Install Windows+
- Install the Windows OS.
- Configure Windows setup.Figure 1 Windows setup
- Click Next.
The installation confirmation window is displayed.
-Figure 2 Installation confirmation window-
- Click Install now.
The Select the operating system you want to install window is displayed.
-Figure 3 Selecting the OS version-
- Select the version of the OS to be installed and click Next.
The Please read the license terms window is displayed.
-Figure 4 License terms window+
Figure 2 Installation confirmation window+
- Click Install now.
The Select the operating system you want to install dialog box is displayed.
+ - Select the version of the OS to be installed and click Next.
The Please read the license terms dialog box is displayed.
- Select I accept the license terms, and click Next.
The Which type of installation do you want? window is displayed.
-Figure 5 Installation type+
Figure 3 Installation type - Select Custom (advanced).
The Where do you want to install Windows? window is displayed.
-- If the system displays a message indicating that no driver is found, go to 1.g.Figure 6 Installation path-
- If a disk is displayed, go to 1.j.Figure 7 Installation path+ -
- Click Load Driver and then Browse.Figure 8 Loading drivers-
- Choose the following path and click OK.
vmtools-windows/upgrade/$OS_Version/drivers/viostor
- - Select the driver matching the OS and click Next.
The system may provide multiple drivers. Select VISOTOR.INF shown in the following figure.
-Figure 9 Selecting the driver to install-
- Select the disk and click Next.Figure 10 Installation path-
If the disk type is Offline, you can stop and then start the ECS, and restart the OS installation process.diff --git a/docs/bms/image-creation-guide/en-us_topic_0000001289739500.html b/docs/bms/image-creation-guide/en-us_topic_0000001289739500.html index 972806bb..4c00bf92 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0000001289739500.html +++ b/docs/bms/image-creation-guide/en-us_topic_0000001289739500.html @@ -6,7 +6,7 @@Figure 11 Offline disk+
- Click Load driver and then Browse.
Figure 6 Loading drivers+- Select a driver based on the disk type.
- If the disk type is VBD, choose viostor > 2k19 > amd64 and click OK.Figure 7 Browsing for a folder+
Select the viostor.inf driver and click Next.+Figure 8 Selecting the driver to install+
- If the disk type is SCSI, choose vioscsi > 2k19 > amd64 and click OK.Figure 9 Browsing for a folder+
Select the vioscsi.inf driver and click Next.
+Figure 10 Selecting the driver to install+
- Select the disk and click Next.
Figure 11 Installation path+ If the disk type is Offline, you can stop and then start the ECS, and restart the OS installation process.Figure 12 Offline disk- The Installing Windows window is displayed, and the OS installation starts.
-The installation takes about 50 minutes. The ECS restarts during the installation. After the ECS successfully restarts, log in to it again and configure the OS as prompted.
- You are required to set a password for the OS user.
Supported special characters include !@$%^-_=+[{}]:,./?
Figure 12 Installation progress+
Figure 13 Installation progress- Install related drivers.
- Open Computer and double-click the CD driver.Figure 13 Starting the CD driver-
- Double-click the vmtools-windows folder.Figure 14 Opening the vmtools-windows folder-
- Double-click the Setup file.Figure 15 Executing the Setup file-
- Install drivers as prompted.Figure 16 Installing UVP VMTools for Windows-
- After the driver is installed, start Device Manager and verify that the drivers shown in the red box in the following figure are successfully installed.Figure 17 Device Manager+
- Install drivers.
- Open Computer and double-click the CD drive.Figure 14 Starting the CD drive+
- Double-click virtio-win-gt-x64 or virtio-win-gt-x86. Install drivers as prompted.
- After the installation is complete, start Device Manager and check that all the drivers shown in the red box are successfully installed.Figure 15 Device Manager
- Open Computer and double-click the CD drive.
Creating a Windows ECS from an ISO Image
-Scenarios
This section describes how to create an ECS from a registered ISO image.
Procedure
- Access the IMS console.
- Log in to the management console.
- Under Compute, click Image Management Service.
The IMS console is displayed.
++ + \ No newline at end of file diff --git a/docs/bms/image-creation-guide/en-us_topic_0000001380021690.html b/docs/bms/image-creation-guide/en-us_topic_0000001380021690.html index f4bf7771..219322e0 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0000001380021690.html +++ b/docs/bms/image-creation-guide/en-us_topic_0000001380021690.html @@ -1,7 +1,7 @@Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Use an ISO image to create a Windows ECS.
- Click the Private Images tab. Locate the row that contains the ISO image and click Create ECS in the Operation column.
- Configure the ECS as prompted and click OK.
Creating a Linux ECS from an ISO Image
--Scenarios
This section describes how to create an ECS from a registered ISO image.
Procedure
- Access the IMS console.
- Log in to the management console.
- Under Compute, click Image Management Service.
The IMS console is displayed.
+Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Use an ISO image to create a Linux ECS.
- Click the Private Images tab. Locate the row that contains the ISO image and click Create ECS in the Operation column.
- Configure the ECS as prompted and click OK.
- Access the IMS console.
Procedure
- Access the IMS console.
- Log in to the management console.
- Under Compute, click Image Management Service.
The IMS console is displayed.
+@@ -26,3 +28,10 @@Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Register an ISO file as an ISO image.
- Click Create Image in the upper right corner.
- In the Image Type and Source area, select ISO image for Type.
- In the image file list, select the bucket and then the image file.
- In the Image Information area, set the following parameters.
-
- Boot Mode: Select BIOS or UEFI. Ensure that the selected boot mode is the same as that in the image file, or the ECSs created from this image will not be able to boot up.
- OS: Select the OS specified in the ISO file. To ensure that the image can be created and used properly, select an OS consistent with that in the image file.
- System Disk: Set the system disk capacity (value range: 40 GB to 1024 GB), which must be no less than the size of the system disk in the image file.
- Name: Enter a name for the image to be created.
- Enterprise Project: Select the enterprise project to which your images belong.
- Tag: (Optional) Add a tag to the image to be created.
- Description: (Optional) Enter image description as needed.
- Register an ISO file as an ISO image.
- Click Create Image in the upper right corner.
- In the Image Type and Source area, select Import Image for Type and then select ISO image for Image Type.
- In the image file list, select the bucket and then the image file.Figure 1 Creating a private image from an ISO file+
- In the Image Information area, set the following parameters.
+Figure 2 Configuring image information+
-- Boot Mode: Select BIOS or UEFI. Ensure that the selected boot mode is the same as that in the image file, or the ECSs created from this image will not be able to boot up.
- OS: Select the OS specified in the ISO file. To ensure that the image can be created and used properly, select an OS consistent with that in the image file.
- System Disk: Set the system disk capacity (value range: 40 GB to 1024 GB), which must be no less than the capacity of the system disk in the image file.
- Name: Enter a name for the image to be created.
- Enterprise Project: Select the enterprise project to which your images belong.
- Tag: (Optional) Add a tag to the image to be created.
- Description: (Optional) Enter image description as needed.
- Click Create Now.
- Confirm the settings and click Submit.
- Switch back to the Image Management Service page to monitor the image status.
When the image status changes to Normal, the image is registered successfully.
+- Click Create Now.
- Confirm the settings and click Submit.
+- Switch back to the Image Management Service page to check the image status.
When the image status changes to Normal, the image is registered successfully.
- Access the IMS console.
Using Dism++ to Install the VMTools Driver for an ISO File
-Scenario
A Windows system with the Integrated Drive Electronics (IDE) hard drive and Virtio NIC is used on the cloud. Therefore, you need to integrate the VMTools driver into the ISO file of Windows before registering an image on the cloud platform. Typically, an ISO file contains all the files that would be included on an optical disc. Some software can be installed only from a CD-ROM drive. So, a virtual CD-ROM drive is required.
+Scenario
Windows uses IDE disks and VirtIO NICs. Before registering an image on the cloud platform, integrate VirtIO drivers into the Windows ISO file. Typically, an ISO file contains all the files that would be included on an optical disc. Some software can be installed only from a CD-ROM drive. So, a virtual CD-ROM drive is required.
This section describes how to install the VMTools driver for an ISO file using Dism++.
Prerequisites
You have obtained an ISO file.
diff --git a/docs/bms/image-creation-guide/en-us_topic_0000001696535081.html b/docs/bms/image-creation-guide/en-us_topic_0000001696535081.html new file mode 100644 index 00000000..15033020 --- /dev/null +++ b/docs/bms/image-creation-guide/en-us_topic_0000001696535081.html @@ -0,0 +1,24 @@ + + +How Do I Verify Software Package Integrity?
+++Prerequisites
- A BMS has been created.
- You have obtained the software package and its SHA256 checksum.
+Verifying Software Package Integrity (Linux)
- Log in to the BMS as the root user.
- Obtain the hash value of the software.
sha256sum {Local directory of the software package}/{Software package name}
+Replace {Local directory of the software package} with the actual download directory.
+Replace {Software package name} with the actual name of the downloaded software package. For example, the name can be qemu-img-hw.zip.
+ - Check whether the SHA256 hash value obtained in Prerequisites is consistent with that obtained in step 2. +
+Verifying Software Package Integrity (Windows)
- Log in to the BMS.
- Open the cmd window as an administrator and run the following command to obtain the hash value of the software:
certutil –hashfile {Local directory of the software package}\{Software package name} SHA256
+Replace {Local directory of the software package} with the actual download directory.
+Replace {Software package name} with the actual name of the downloaded software package. For example, the name can be qemu-img-hw.zip.
+ - Check whether the SHA256 hash value obtained in Prerequisites is consistent with that obtained in step 2. +
++ diff --git a/docs/bms/image-creation-guide/en-us_topic_0000002024654874.html b/docs/bms/image-creation-guide/en-us_topic_0000002024654874.html new file mode 100644 index 00000000..65772597 --- /dev/null +++ b/docs/bms/image-creation-guide/en-us_topic_0000002024654874.html @@ -0,0 +1,18 @@ + + +++Parent topic: FAQ+How Do I Check Whether a Physical Server Is Running Properly?
++- Log in to the OS as root and check the software installation path.
cat /etc/ascend_install.info
+Information similar to the following should be displayed:
+Driver_Install_Path_Param=/usr/local/Ascend
+ - Go to the driver installation directory and use upgrade-tool to check the file system version of the physical server.
cd /usr/local/Ascend/driver/tools/
+./upgrade-tool --device_index -1 --system_version
+If information similar to the following is returned, the physical server is running properly:
+
+
++ diff --git a/docs/bms/image-creation-guide/en-us_topic_0081116558.html b/docs/bms/image-creation-guide/en-us_topic_0081116558.html index c64652cf..c6ec3251 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0081116558.html +++ b/docs/bms/image-creation-guide/en-us_topic_0081116558.html @@ -34,7 +34,7 @@++Parent topic: FAQ+This issue is the fourteenth official release.
Added the following content:
-Installing and Upgrading Drivers and Firmware for Ascend 910 BMSs
+Installing and Upgrading Drivers and Firmware for Ascend BMSs
- Access the IMS console.
- Click Load driver and then Browse.
- If the system displays a message indicating that no driver is found, go to 1.g.
- Configure Windows setup.
- Install the Windows OS.
- Specify the parameters on the Install Windows page.
2019-12-30
diff --git a/docs/bms/image-creation-guide/en-us_topic_0081116559.html b/docs/bms/image-creation-guide/en-us_topic_0081116559.html index 039be1e5..4e29ed17 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0081116559.html +++ b/docs/bms/image-creation-guide/en-us_topic_0081116559.html @@ -48,7 +48,7 @@ -Prerequisites
- You have logged in to the VM.
- Cloud-Init has been installed on the VM.
- The bms-network-config software package has been downloaded as instructed in Software and has been uploaded to the VM.
Download the RPM package depending on the OS. Ubuntu and Debian use the .deb package, and CentOS and EulerOS (Arm) use the aarch .rpm package.
+diff --git a/docs/bms/image-creation-guide/en-us_topic_0081116571.html b/docs/bms/image-creation-guide/en-us_topic_0081116571.html index bef1a8ce..62647738 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0081116571.html +++ b/docs/bms/image-creation-guide/en-us_topic_0081116571.html @@ -34,7 +34,7 @@Prerequisites
- You have logged in to the VM.
- Cloud-Init has been installed on the VM.
- You have downloaded the bms-network-config software package by referring to Software.
Download the RPM package depending on the OS. Ubuntu and Debian use the .deb package, and CentOS and EulerOS (Arm) use the aarch .rpm package.
It is used to automatically configure BMS networks.
Obtain the package from the operations administrator.
+Obtain the package from the operations administrator.
SDI driver
diff --git a/docs/bms/image-creation-guide/en-us_topic_0081116685.html b/docs/bms/image-creation-guide/en-us_topic_0081116685.html index 7d9796b8..635c0714 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0081116685.html +++ b/docs/bms/image-creation-guide/en-us_topic_0081116685.html @@ -11,6 +11,8 @@ ... # additional kernel modules to the default add_drivers+="ahci megaraid_sas mpt3sas mpt2sas virtio_blk virtio_scsi virtio_net" + If an error is reported, add a space before and after the driver list in the quotation marks and try again.
+# List of modules that you want to include in your initramfs. # They will be loaded at boot time in the order below. # @@ -31,6 +33,8 @@ virtio_net
- Run the following command to install dracut:
After the installation is complete, add add_drivers+="ahci megaraid_sas mpt3sas mpt2sas virtio_blk virtio_scsi virtio_net" to the end of the /etc/dracut.conf file by performing operations similar to those for Red Hat and Oracle Linux 7.3.
+ If an error is reported, add a space before and after the driver list in the quotation marks and try again.
+ - Run the following command to install initramfs-tools:
apt-get install initramfs-tools
After the installation is complete, add the ahci, megaraid_sas, mpt3sas, mpt2sas, and virtio_blk virtio_scsi virtio_net drivers to the end of the /etc/initramfs-tools/modules file by performing operations similar to those for Ubuntu 14.04.
If some disk partitions do not have UUIDs, check whether the VM OS is properly installed. If it is not, install it again.
Original menu.lst file
Modified menu.lst file
+Modified menu.lst file
Original device.map file
+Original device.map file
(hd0) /dev/disk/by-id/ata-QEMU_HARDDISK_QM00001 ~-
Modified device.map file
+Modified device.map file
(hd0) /dev/sda
Original fstab file
If SUSE 11 SP4 uses LVM, replace the virtual disks in the VM file with the actual physical disks.
- In the /boot/grub directory of the VM, run the blkid command to check whether disk partitions are normal.
If some disk partitions do not have UUIDs, check whether the VM OS is properly installed. If it is not, install it again.
- - Use the vi editor to open the /boot/grub/menu.lst file, modify the OS boot parameters, and save the configuration.
Original menu.lst file
+ - Use the vi editor to open the /boot/grub/menu.lst file, modify the OS boot parameters, and save the configuration.
Original menu.lst file
Modified menu.lst file
diff --git a/docs/bms/image-creation-guide/en-us_topic_0081116754.html b/docs/bms/image-creation-guide/en-us_topic_0081116754.html index 07dd8cde..ff877d3a 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0081116754.html +++ b/docs/bms/image-creation-guide/en-us_topic_0081116754.html @@ -36,7 +36,7 @@
Configuring the VM
Linux:
-- Install and configure Cloud-Init.
- Modify the hardware device driver that boots the OS.
- Install bms-network-config.
- (Optional) Install the SDI driver.
- (Optional) Install the Hi1822 driver.
- (Optional) Install the IB driver.
- (Optional) Install x86 V5/TaiShan server drivers.
- (Optional) Install multipath software.
- Perform security configuration.
- Configure remote login.
- Configuring automatic root partition expansion
- Install and configure Cloud-Init.
- Modify the hardware device driver that boots the OS.
- Install bms-network-config.
- (Optional) Install the SDI driver.
- (Optional) Install the Hi1822 driver.
- (Optional) Install the IB driver.
- (Optional) Install x86 V5/TaiShan server drivers.
- (Optional) Install multipath software.
- Perform security configuration.
- Configure remote login.
- Configure automatic root partition expansion.
Windows:
- Install x86 V5 server drivers.
- Install Cloudbase-Init.
- Install bms-network-config.
- (Optional) Install the SDI driver.
- Set the Windows time zone.
- Set the Windows virtual memory.
- (Optional) Configure automatic windows update.
- Configure the SID.
- Configuring the Root Partition to Be Automatically Extended
-
- Installing and Upgrading Drivers and Firmware for Ascend 910 BMSs
+- Installing and Upgrading Drivers and Firmware for Ascend BMSs
- Deleting Files
diff --git a/docs/bms/image-creation-guide/en-us_topic_0081116771.html b/docs/bms/image-creation-guide/en-us_topic_0081116771.html index 890e37ce..caa2ed95 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0081116771.html +++ b/docs/bms/image-creation-guide/en-us_topic_0081116771.html @@ -33,7 +33,7 @@
SDI driver
With the SDI driver, EVS disks can be attached to BMSs. The EVS disks can be used as system disks from which the BMSs are booted. This facilitates quick BMS provisioning.
-NOTE:This software package is only required by images with SDI cards installed (exclude SDI 2.2 and SDI 3.0).
+NOTE:This software package is only required by images with SDI cards installed (SDI 2.2 and SDI 3.0 excluded).
Linux:
@@ -50,7 +50,7 @@It is used to automatically configure BMS networks.
Contact the operations administrator to obtain the package.
+Contact the operation administrator to obtain the package.
Huawei
Cloudbase-Init is used to initialize Windows instances (for example, initialize the instance login password).
Contact the operations administrator to obtain the package.
+Contact the operation administrator to obtain the package.
Cloudbase-Init
Visit https://support.huawei.com/enterprise/en/servers/fusionserver-idriver-pid-21588909/software. Click the recommended version. Download the driver package based on the image OS.
Huawei
+9
d. Run the grub2-mkconfig -o /boot/grub2/grub.cfg command again. (The directory of the grub.cfg file is an example only.)
e. Run the following command to check whether the baud speed is 115200:
stty -F /dev/ttyS0 -a
-
+
diff --git a/docs/bms/image-creation-guide/en-us_topic_0081116841.html b/docs/bms/image-creation-guide/en-us_topic_0081116841.html index b360119e..7ade6a34 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0081116841.html +++ b/docs/bms/image-creation-guide/en-us_topic_0081116841.html @@ -16,6 +16,10 @@
- How Do I Activate a Windows BMS?
+
- How Do I Verify Software Package Integrity?
+
+- How Do I Check Whether a Physical Server Is Running Properly?
diff --git a/docs/bms/image-creation-guide/en-us_topic_0108488467.html b/docs/bms/image-creation-guide/en-us_topic_0108488467.html index f27f578a..6d4d2b6a 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0108488467.html +++ b/docs/bms/image-creation-guide/en-us_topic_0108488467.html @@ -19,10 +19,15 @@ groups=Administrators
+- Configure hostname and modify the following parameter (if it does not exist, add it):
netbios_host_name_compatibility=false
- Locate and modify logging_serial_port_settings as follows:
logging_serial_port_settings=COM1,115200,N,8
- Add parameter metadata_services and configure the loaded services as follows:
metadata_services=cloudbaseinit.metadata.services.httpservice.HttpService,cloudbaseinit.metadata.services.configdrive.ConfigDriveService
-- Add parameter plugins and configure the modules to be loaded. Separate different modules with commas (,). The information in bold is the keyword of each module.
The following is an example of the Cloudbase-Init file content:-plugins=cloudbaseinit.plugins.common.localscripts.LocalScriptsPlugin,cloudbaseinit.plugins.common.mtu.MTUPlugin,cloudbaseinit.plugins.windows.createuser.CreateUserPlugin,cloudbaseinit.plugins.common.setuserpassword.SetUserPasswordPlugin,cloudbaseinit.plugins.common.sshpublickeys.SetUserSSHPublicKeysPlugin,cloudbaseinit.plugins.common.sethostname.SetHostNamePlugin,cloudbaseinit.plugins.windows.extendvolumes.ExtendVolumesPlugin,cloudbaseinit.plugins.common.userdata.UserDataPlugin,cloudbaseinit.plugins.windows.winrmlistener.ConfigWinRMListenerPlugin,cloudbaseinit.plugins.windows.winrmcertificateauth.ConfigWinRMCertificateAuthPlugin,cloudbaseinit.plugins.windows.licensing.WindowsLicensingPlugin
-Functions of the modules are as follows:
-- LocalScriptsPlugin: sets the scripts.
- MTUPlugin: sets the MTU network ports.
- CreateUserPlugin: creates a user.
- SetUserPasswordPlugin: sets the password.
- SetUserSSHPublicKeysPlugin: sets the private key.
- SetHostNamePlugin: sets the hostname.
- ExtendVolumesPlugin: partitions the disks.
- UserDataPlugin: injects user data.
- ConfigWinRMListenerPlugin: sets listening to remote login.
- ConfigWinRMCertificateAuthPlugin: sets remote login without the password authentication.
- WindowsLicensingPlugin: activates Windows instances.
- Add parameter plugins to configure the plugins that will be loaded. Separate different plugins with commas (,). The information in bold is the keyword of each plugin.
diff --git a/docs/bms/image-creation-guide/en-us_topic_0108600905.html b/docs/bms/image-creation-guide/en-us_topic_0108600905.html index f8caf8a9..3794a1f0 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0108600905.html +++ b/docs/bms/image-creation-guide/en-us_topic_0108600905.html @@ -10,16 +10,16 @@- Mandatory plugins:
plugins=cloudbaseinit.plugins.common.localscripts.LocalScriptsPlugin,cloudbaseinit.plugins.common.mtu.MTUPlugin,cloudbaseinit.plugins.windows.createuser.CreateUserPlugin,cloudbaseinit.plugins.common.setuserpassword.SetUserPasswordPlugin,cloudbaseinit.plugins.common.sshpublickeys.SetUserSSHPublicKeysPlugin,cloudbaseinit.plugins.common.sethostname.SetHostNamePlugin,cloudbaseinit.plugins.windows.extendvolumes.ExtendVolumesPlugin,cloudbaseinit.plugins.common.userdata.UserDataPlugin,cloudbaseinit.plugins.windows.licensing.WindowsLicensingPlugin
+Plugin functions:
+- LocalScriptsPlugin: sets the scripts.
- MTUPlugin: sets the MTU network ports.
- CreateUserPlugin: creates a user.
- SetUserPasswordPlugin: sets the password.
- SetUserSSHPublicKeysPlugin: sets the private key.
- SetHostNamePlugin: sets the hostname.
- ExtendVolumesPlugin: expands disk space.
- UserDataPlugin: injects user data.
- WindowsLicensingPlugin: activates Windows instances.
- Optional plugins:
plugins=cloudbaseinit.plugins.windows.winrmlistener.ConfigWinRMListenerPlugin,cloudbaseinit.plugins.windows.winrmcertificateauth.ConfigWinRMCertificateAuthPlugin
+Plugin functions:
+- ConfigWinRMListenerPlugin: sets listening to remote login.
- ConfigWinRMCertificateAuthPlugin: sets remote login without the password authentication.
+ The WinRM plug-ins use weak cryptographic algorithm, which may cause security risks. So, you are advised not to load the plug-ins.
+
- WDK has been installed.
-Download WDK from http://download.microsoft.com/download/4/E/0/4E07EAAD-E394-4EA8-B2B8-D46E46A409C5/wdk/wdksetup.exe.
+ + \ No newline at end of file diff --git a/docs/bms/image-creation-guide/en-us_topic_0218670457.html b/docs/bms/image-creation-guide/en-us_topic_0218670457.html index cd679bc8..21fd8e5c 100644 --- a/docs/bms/image-creation-guide/en-us_topic_0218670457.html +++ b/docs/bms/image-creation-guide/en-us_topic_0218670457.html @@ -50,7 +50,7 @@Procedure
- Obtain the device management tool devcon.exe from the WDK directory C:\Program Files (x86)\Windows Kits\10\Tools\x64, and place devcon.exe in the same directory as the SDI driver.
-
- Find the EpScsiAdpt installation file and view the PCI ID.
+@@ -30,3 +30,10 @@
Procedure
- Obtain the device management tool devcon.exe from the WDK directory C:\Program Files (x86)\Windows Kits\10\Tools\x64, and place devcon.exe in the same directory as the SDI driver.
+ - Find the EpScsiAdpt installation file and view the PCI ID.
- Open the CLI, go to the directory where the SDI driver and device management tool are located, and run the following command:
devcon install EpScsiAdpt.inf "PCI\VEN_19E5&DEV_1610&SUBSYS_000119E5"
-
+
The PCI ID is an example only.
- - (Optional) Delete device nodes.
- If the environment where you create an image does not have SDI hardware, the storage controller in the device manager has exceptions. +
- (Optional) Delete device nodes.
- If the environment where you create an image does not have SDI hardware, the storage controller in the device manager has exceptions.
- Open the CLI, go to the directory where the SDI driver and devcon installation tool are stored, and delete the abnormal device nodes.
Run the devcon.exe find "PCI\VEN_19E5*" command to locate abnormal device nodes.
Run the devcon.exe remove "@ROOT\SCSIADAPTER\0000" command to delete the nodes.
-
-
- Restart the VM.
+
+ - Restart the VM.
- Check whether the exceptions in the storage controller are cleared.
- Obtain the device management tool devcon.exe from the WDK directory C:\Program Files (x86)\Windows Kits\10\Tools\x64, and place devcon.exe in the same directory as the SDI driver.
7 64-bit
https://archives.fedoraproject.org/pub/epel/7/x86_64/Packages/e/
+https://archives.fedoraproject.org/pub/archive/epel/7/x86_64/Packages/e/
