diff --git a/physical_infra_provider_configuration/l10n/en-US/Author_Group.xml b/physical_infra_provider_configuration/l10n/en-US/Author_Group.xml index c514c67..8b97732 100644 --- a/physical_infra_provider_configuration/l10n/en-US/Author_Group.xml +++ b/physical_infra_provider_configuration/l10n/en-US/Author_Group.xml @@ -19,3 +19,4 @@ icfeedback@lenovo.com + diff --git a/physical_infra_provider_configuration/l10n/en-US/Revision_History.xml b/physical_infra_provider_configuration/l10n/en-US/Revision_History.xml index f034206..e9d4fd0 100644 --- a/physical_infra_provider_configuration/l10n/en-US/Revision_History.xml +++ b/physical_infra_provider_configuration/l10n/en-US/Revision_History.xml @@ -7,12 +7,12 @@ %DOCBOOK_ENTS; ]> - + Revision History 1.0-0 - Mon Mar 5 2018 + Mon Jan 7 2019 Red Hat CCS Initial document creation @@ -21,3 +21,4 @@ + diff --git a/physical_infra_provider_configuration/l10n/en-US/images/automation/images/provider_assign_profile.png b/physical_infra_provider_configuration/l10n/en-US/images/automation/images/provider_assign_profile.png index ea672c0..48e0e31 100644 Binary files a/physical_infra_provider_configuration/l10n/en-US/images/automation/images/provider_assign_profile.png and b/physical_infra_provider_configuration/l10n/en-US/images/automation/images/provider_assign_profile.png differ diff --git a/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_chassis/images/physical_chassis.png b/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_chassis/images/physical_chassis.png new file mode 100644 index 0000000..fe7afd9 Binary files /dev/null and b/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_chassis/images/physical_chassis.png differ diff --git a/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_chassis/images/physical_chassis_identify_led.png b/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_chassis/images/physical_chassis_identify_led.png new file mode 100644 index 0000000..9d1fbeb Binary files /dev/null and b/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_chassis/images/physical_chassis_identify_led.png differ diff --git a/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_rack/images/physical_racks.png b/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_rack/images/physical_racks.png new file mode 100644 index 0000000..4bd7726 Binary files /dev/null and b/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_rack/images/physical_racks.png differ diff --git a/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_server/images/network_device_summary.png b/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_server/images/network_device_summary.png new file mode 100644 index 0000000..b234a3c Binary files /dev/null and b/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_server/images/network_device_summary.png differ diff --git a/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_server/images/physical_server_provision.png b/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_server/images/physical_server_provision.png index 927e40f..2bc5698 100644 Binary files a/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_server/images/physical_server_provision.png and b/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_server/images/physical_server_provision.png differ diff --git a/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_server/images/storage_device_summary.png b/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_server/images/storage_device_summary.png new file mode 100644 index 0000000..87b5d95 Binary files /dev/null and b/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_server/images/storage_device_summary.png differ diff --git a/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_storage/images/physical_storage.png b/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_storage/images/physical_storage.png new file mode 100644 index 0000000..fed74f7 Binary files /dev/null and b/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_storage/images/physical_storage.png differ diff --git a/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_switch/images/physical_switch_restart.png b/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_switch/images/physical_switch_restart.png new file mode 100644 index 0000000..d2fc40f Binary files /dev/null and b/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_switch/images/physical_switch_restart.png differ diff --git a/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_switch/images/physical_switches.png b/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_switch/images/physical_switches.png new file mode 100644 index 0000000..b327b15 Binary files /dev/null and b/physical_infra_provider_configuration/l10n/en-US/images/usage/physical_switch/images/physical_switches.png differ diff --git a/physical_infra_provider_configuration/l10n/en-US/images/usage/relationship/images/topology_widget.png b/physical_infra_provider_configuration/l10n/en-US/images/usage/relationship/images/topology_widget.png index c85746e..ba72cb0 100644 Binary files a/physical_infra_provider_configuration/l10n/en-US/images/usage/relationship/images/topology_widget.png and b/physical_infra_provider_configuration/l10n/en-US/images/usage/relationship/images/topology_widget.png differ diff --git a/physical_infra_provider_configuration/l10n/en-US/main.ent b/physical_infra_provider_configuration/l10n/en-US/main.ent index 07153eb..7717030 100644 --- a/physical_infra_provider_configuration/l10n/en-US/main.ent +++ b/physical_infra_provider_configuration/l10n/en-US/main.ent @@ -1,4 +1,4 @@ - - + + \ No newline at end of file diff --git a/physical_infra_provider_configuration/l10n/en-US/main.xml b/physical_infra_provider_configuration/l10n/en-US/main.xml index d69a83e..88fbb0b 100644 --- a/physical_infra_provider_configuration/l10n/en-US/main.xml +++ b/physical_infra_provider_configuration/l10n/en-US/main.xml @@ -7,11 +7,11 @@ ]> -Configuring the Lenovo Physical Infrastructure ProviderAdding and configuring the Lenovo physical infrastructure provider in Red Hat CloudForms +Configuring the Lenovo Physical Infrastructure Provider for Red Hat CloudFormsAdding and configuring the Lenovo physical infrastructure provider in Red Hat CloudForms -2018-03-05 +2018-11-22 Red Hat CloudForms -4.6 +4.7 Adding and configuring the Lenovo physical infrastructure provider in Red Hat CloudForms. If you have a suggestion for improving this guide or have found an error, please submit a Bugzilla report at http://bugzilla.redhat.com against Red Hat CloudForms Management Engine for the Documentation component. Please provide specific details, such as the section number, guide name, and CloudForms version so we can easily locate the content. @@ -24,13 +24,21 @@ Key features include: -Seamlessly integrates with one or more Lenovo XClarity Administrator virtual appliances, providing a summary view of the Lenovo infrastructure, relationship views of physical servers and virtual hosts, and configuration of servers using Configuration Patterns +Seamlessly integrates with one or more XClarity Administrator virtual appliances, providing a summary view of the Lenovo infrastructure, relationship views of physical servers and virtual hosts, and configuration of servers using Configuration Patterns. In addition, there is a dashboard view that displays the following: + + +The number of servers, switches, racks, and storage systems being mangaged + + +Widgets that display information about server health, availability, and recently discovered servers + + -Provides a single interface to monitor Lenovo hardware that is managed by multiple instances of Lenovo XClarity Administrator +Provides a single interface to monitor Lenovo hardware that is managed by multiple instances of XClarity Administrator -Automatically discovers hardware that is managed by Lenovo XClarity Administrator +Automatically discovers hardware that is managed by XClarity Administrator Manage devices for use in on-premise cloud deployments @@ -48,28 +56,28 @@ Manages current system settings (such as BMC, uEFI, and boot order settings) on the managed devices -Simplifies system management through custom policies and automation that respond to the health status of physical servers +Simplifies system management through custom policies and automation that respond to the health status of hardware devices - -Configuring Lenovo XClarity Administrator -Lenovo XClarity Administrator virtual appliances are connected to CloudForms by adding physical-infrastructure providers. Physical-infrastructure providers enable you to manage and interact with devices that are managed by Lenovo XClarity Administrator. After the physical-infrastructure provider is added, the servers that are managed by the Lenovo XClarity Administrator are registered in CloudForms. Managed devices can be monitored, configured, and updated using Lenovo XClarity Administrator. The physical-infrastructure provider surfaces information about these managed devices and the Lenovo XClarity Administrator instance. -
-Setting up Lenovo XClarity Administrator -For information about downloading and setting up Lenovo XClarity Administrator, see Installing and setting up Lenovo XClarity Administrator in the Lenovo XClarity Administrator online documentation. -Note: You can use all available features in Lenovo XClarity Administrator for free for up to 90 days. After 90 days, you can continue to use Lenovo XClarity Administrator to manage and monitor your hardware for free; however, you must purchase a full-function-enablement license to continue using Lenovo XClarity Administrator to configure your hardware using Configuration Patterns and to deploy operating systems. Lenovo XClarity Pro provides entitlement to service and support and the full-function-enablement license for Lenovo XClarity Administrator. For more information about purchasing Lenovo XClarity Pro, contact your Lenovo representative or authorized business partner. -
-
-Discovering and managing hardware using Lenovo XClarity Administrator -Lenovo XClarity Administrator can discover manageable devices in your environment by performing an SLP discovery for devices that are on the same IP subnet as Lenovo XClarity Administrator. A specified IP address or range of IP addresses also can be used, or information can be imported from a spreadsheet, a process that is known as a bulk import. Discovery options can be accessed by clicking Hardware > Discover and Manage New Devices from the menu bar. Discovered devices can then be managed by Lenovo XClarity Administrator. During the management process, you are asked for login credentials for the management controller of the target servers and given the option to create a recovery account for the servers. For more information about discovering and managing devices, see the Lenovo XClarity Administrator online documentation. + +Configuring XClarity Administrator +XClarity Administrator virtual appliances are connected to CloudForms by adding physical-infrastructure providers. Physical-infrastructure providers enable you to manage and interact with devices that are managed by XClarity Administrator. After the physical-infrastructure provider is added, the devices that are managed by the XClarity Administrator are registered in CloudForms. Managed devices can be monitored, configured, and updated using XClarity Administrator. The physical-infrastructure provider surfaces information about these managed devices and the XClarity Administrator instance. +
+Setting up XClarity Administrator +For information about downloading and setting up XClarity Administrator, see Installing and setting up Lenovo XClarity Administrator in the XClarity Administrator online documentation. +Note: You can use all available features in XClarity Administrator for free for up to 90 days. After 90 days, you can continue to use XClarity Administrator to manage and monitor your hardware for free; however, you must purchase a full-function-enablement license to continue using XClarity Administrator to configure your hardware using Configuration Patterns and to deploy operating systems. Lenovo XClarity Pro provides entitlement to service and support and the full-function-enablement license for XClarity Administrator. For more information about purchasing Lenovo XClarity Pro, contact your Lenovo representative or authorized business partner. +
+
+Discovering and managing hardware using XClarity Administrator +XClarity Administrator can discover manageable devices in your environment by performing an SLP discovery for devices that are on the same IP subnet as XClarity Administrator. A specified IP address or range of IP addresses also can be used, or information can be imported from a spreadsheet, a process that is known as a bulk import. Discovery options can be accessed by clicking Hardware > Discover and Manage New Devices from the menu bar. Discovered devices can then be managed by XClarity Administrator. During the management process, you are asked for login credentials for the management controller of the target servers and given the option to create a recovery account for the servers. For more information about discovering and managing devices, see the XClarity Administrator online documentation. Note: -Ensure that the devices that you intend to manage are supported by Lenovo XClarity Administrator. For information about supported devices, see Supported devices in the Lenovo XClarity Administrator online documentation. +Ensure that the devices that you intend to manage are supported by XClarity Administrator. For information about supported devices, see Supported devices in the XClarity Administrator online documentation. -Ensure that firmware for all devices that you intend to manage using Lenovo XClarity Administrator are at the required levels. For more information about supported firmware levels, see Supported firmware in the Lenovo XClarity Administrator online documentation. +Ensure that firmware for all devices that you intend to manage using XClarity Administrator are at the required levels. For more information about supported firmware levels, see Supported firmware in the XClarity Administrator online documentation.
@@ -78,10 +86,10 @@ Managing physical-infrastructure providers
Adding a physical-infrastructure provider -Lenovo XClarity Administrator virtual appliances are connected to CloudForms by adding physical-infrastructure providers. Physical-infrastructure providers enable you to manage and interact with devices that are managed by Lenovo XClarity Administrator. +XClarity Administrator virtual appliances are connected to CloudForms by adding physical-infrastructure providers. Physical-infrastructure providers enable you to manage and interact with devices that are managed by XClarity Administrator. Note: You must be logged in to CloudForms as a user with permission to add providers. The default user is admin, password smartvm. -Complete the following steps for each Lenovo XClarity Administrator instance that you want to connect to CloudForms. -To connect to a specific Lenovo XClarity Administrator instance: +Complete the following steps for each XClarity Administrator instance that you want to connect to CloudForms. +To connect to a specific XClarity Administrator instance: Navigate to Compute > Physical Infrastructure > Providers. @@ -102,27 +110,27 @@ In the credentials area, provide the following: -Enter the hostname, IPv4 address, or IPv6 address of the Lenovo XClarity Administrator instance. +Enter the hostname, IPv4 address, or IPv6 address of the XClarity Administrator instance. Enter “443” for the API port. -Enter the username and password used to log in to the Lenovo XClarity Administrator instance. +Enter the username and password used to log in to the XClarity Administrator instance. -Click Validate to confirm that you can connect to the Lenovo XClarity Administrator instance. +Click Validate to confirm that you can connect to the XClarity Administrator instance. Click Add. -To discover and then connect to a range of Lenovo XClarity Administrator instances: +To discover and then connect to a range of XClarity Administrator instances: -Discover Lenovo XClarity Administrator instances: +Discover XClarity Administrator instances: Navigate to Compute > Physical Infrastructure > Providers. @@ -145,7 +153,7 @@ -Update credentials for each discovered physical-infrastructure provider (Lenovo XClarity Administrator instance): +Update credentials for each discovered physical-infrastructure provider (XClarity Administrator instance): Navigate to Compute > Physical Infrastructure > Providers. @@ -160,10 +168,10 @@ Click Edit selected infrastructure providers. -Enter the username and password used to log in to the Lenovo XClarity Administrator instance. +Enter the username and password used to log in to the XClarity Administrator instance. -Click Validate to confirm that you can connect to the Lenovo XClarity Administrator instance. +Click Validate to confirm that you can connect to the XClarity Administrator instance. Click Save. A flash message is displayed, confirming your changes were performed successfully. @@ -239,6 +247,30 @@
+
+Changing the password of the XClarity Administrator instance through its physical-infrastructure provider +Within CloudForms, you can change the password of an XClarity Administrator instance through the physical-infrastructure provider with which it is associated. Changing the password this way also changes the password in CloudForms so that they match. + + +Navigate to Compute > Physical Infrastructure > Providers. + + +Click on the physical-infrastructure provider to be modified. + + +Click on the Authentication button in the top menu and select Change password. The Change Password for Physical Infrastructure Provider page is displayed. + + +Enter the current password for the XClarity Administrator instance in the Current Password field. + + +Enter the new password in the New Password and Confirm New Password fields. + + +Click Save. + + +
 Viewing relationships @@ -257,10 +289,13 @@ Navigate to Compute > Physical Infrastructure > Providers. -Select the physical-infrastructure provider to be viewed. +Click on the physical-infrastructure provider to be viewed. + + +Once the page loads, ensure that the summary view is being used. -From the overview section, select Topology to display the Topology page. From this page, you can perform the following actions: +Click on Topology in the Overview table to display the Topology page. From this page, you can perform the following actions: Hide or show all physical server by clicking Physical Servers. @@ -272,6 +307,9 @@ Hide or show all VMs by clicking VMs. +Hide or show nodes in the graph that have a particular health state by clicking on one of the following states: Valid, Warning, Critical, or Unknown. + + Double-click or right-click a node in the graph to navigate to the summary pages for that node. @@ -281,18 +319,41 @@
Viewing server relationships You can view a list of all physical servers that are managed by a specific physical-infrastructure provider. +
+From the physical-infrastructure provider summary view Navigate to Compute > Physical Infrastructure > Providers. -Select the physical-infrastructure provider to be viewed. +Click on the physical-infrastructure provider to be viewed. -Click Physical Servers in the Relationships section. +After the page loads, ensure that the summary view is being used. + + +Click on Physical Servers in the Relationships table.
+
+From the physical-infrastructure provider dashboard view + + +Navigate to Compute > Physical Infrastructure > Providers. + + +Click on the physical-infrastructure provider to be viewed. + + +After the page loads, ensure that the dashboard view is being used. + + +Click on the number of servers that is displayed displayed in the Servers card. + + +
+
Viewing virtual-host relationships You can view a list of physical servers that are associated with hosts that are managed by a specific physical-infrastructure provider. @@ -301,13 +362,16 @@ Navigate to Compute > Physical Infrastructure > Providers. -Select the physical-infrastructure provider to be viewed. +Click on the physical-infrastructure provider to be viewed. -Click Physical Servers with Host button in the Relationships section. +After the page loads, ensure that the summary view is being used. + + +Click on Physical Servers with Host in the Relationships table. -You should see a list of physical servers that are associated with hosts as shown below. +A list of physical servers that are associated with hosts are displayed as shown below. @@ -315,10 +379,163 @@ host relationships
+
+Viewing storage relationships +You can view a list of all storage systems that are managed by a specific physical-infrastructure provider. +
+From the physical-infrastructure provider summary view + + +Navigate to Compute > Physical Infrastructure > Providers. + + +Click on the physical-infrastructure provider to be viewed. + + +After the page loads, ensure that the summary view is being used. + + +Click on Physical Storages in the Relationships table. + + +
+
+From the physical-infrastructure provider dashboard view + + +Navigate to Compute > Physical Infrastructure > Providers. + + +Click on the physical-infrastructure provider to be viewed. + + +After the page loads, ensure that the dashboard view is being used. + + +Click on the number of storage systems that is displayed in the Storages card. + + +
+
+
+Viewing switch relationships +You can view a list of all switches that are managed by a specific physical-infrastructure provider. +
+From the physical-infrastructure provider summary view + + +Navigate to Compute > Physical Infrastructure > Providers. + + +Click on the physical-infrastructure provider to be viewed. + + +After the page loads, ensure that the summary view is being used. + + +Click on Physical Switches in the Relationships table. + + +
+
+From the physical-infrastructure provider dashboard view + + +Navigate to Compute > Physical Infrastructure > Providers. + + +Click on the physical-infrastructure provider to be viewed. + + +After the page loads, ensure that the dashboard view is being used. + + +Click on the number of switches that is displayed in the Switches card. + + +
+
+
+Viewing chassis relationships +You can view a list of chassis that are managed by a specific physical-infrastructure provider. +
+From the physical-infrastructure provider summary view + + +Navigate to Compute > Physical Infrastructure > Providers. + + +Click on the physical-infrastructure provider to be viewed. + + +After the page loads, ensure that the summary view is being used. + + +Click on Physical Chassis in the Relationships table. + + +
+
+From the physical-infrastructure provider dashboard view + + +Navigate to Compute > Physical Infrastructure > Providers. + + +Click on the physical-infrastructure provider to be viewed. + + +After the page loads, ensure that the dashboard view is being used. + + +Click on the number of chassis that is displayed in the Chassis card. + + +
+
+
+Viewing rack relationships +You can view a list of all racks that are managed by a specific physical-infrastructure provider. +
+From the physical-infrastructure provider summary view + + +Navigate to Compute > Physical Infrastructure > Providers. + + +Click on the physical-infrastructure provider to be viewed. + + +After the page loads, ensure that the summary view is being used. + + +Click on Physical Racks in the Relationships table. + + +
+
+From the physical-infrastructure provider dashboard view + + +Navigate to Compute > Physical Infrastructure > Providers. + + +Click on the physical-infrastructure provider to be viewed. + + +After the page loads, ensure that the dashboard view is being used. + + +Click on the number of racks that is displayed in the Racks card. + + +
+
 Managing physical servers -After the Lenovo physical-infrastructure provider is added, the servers that are managed by Lenovo XClarity Administrator are registered in CloudForms. You can then view and manage those servers. +After the Lenovo physical-infrastructure provider is added, the servers that are managed by XClarity Administrator are registered in CloudForms. You can then view and manage those servers. +Note: It may take a few seconds or so for the servers to appear after adding a physical-infrasturcture provider.
Viewing a Physical Server To view a list of all physical servers that are managed by all physical-infrastructure providers, navigate to Compute > Physical Infrastructure > Servers. The Physical Servers page is displayed (see the following figure). @@ -420,8 +637,8 @@
Provisioning physical servers using configuration patterns -You can use configuration patterns in Lenovo XClarity Administrator to quickly provision or preprovision multiple servers from a single set of defined configuration settings. Configuration patterns act as templates for configuring logical storage, I/O adapters, boot order, and other baseboard management controller and Unified Extensible Firmware Interface (UEFI) settings. -A physical-infrastructure provider can discover configuration patterns that are defined on the associated Lenovo XClarity Administrator instance. A configuration pattern can then be applied to a single or multiple physical servers. +You can use configuration patterns in XClarity Administrator to quickly provision or preprovision multiple servers from a single set of defined configuration settings. Configuration patterns act as templates for configuring logical storage, I/O adapters, boot order, and other baseboard management controller and Unified Extensible Firmware Interface (UEFI) settings. +A physical-infrastructure provider can discover configuration patterns that are defined on the associated XClarity Administrator instance. A configuration pattern can then be applied to a single or multiple physical servers. Note: Configuration patterns can be assigned only to physical servers that do not have a pattern assigned to them. @@ -460,14 +677,189 @@
+
+Viewing network devices that are associated with a physical server +From the Physical Server Summary page, you can access details about network devices such as network interface cards. + + +Access the Physical Servers page, as described in the section, and then select a physical server. The Physical Server Summary page is displayed. + + +Click on the Network Devices count in the Properties table. A list of network devices is displayed. + + +Select a network device from the list. The Network Device Summary page is displayed. + + + + + + +network device summary + +
+
+Viewing storage devices that are associated with a physical server +From the Physical Server Summary page, you can access details about storage devices, such as RAID cards. + + +Access the Physical Servers page, as described in the section, and then select a physical server. The Physical Server Summary page is displayed. + + +Click on the Storage Devices count in the Properties table. A list of storage devices is displayed. + + +Select a storage device from the list. The Storage Device Summary page is displayed. + + + + + + +storage device summary + +
+
+Adding physical server widgets to the dashboard +You can add widgets that display information about physical servers to the default dashboard. + + +Navigate to Cloud Intel > Dashboard. + + +Click on the + button from the top menu, and select one of the following widgets: + + +Physical Server Availability + + +Physical Server Health + + +Recently Discovered Physical Servers + + + + +The widget is now displayed on the default dashboard. +
+
+Creating a user that belongs to the physical infrastructure usergroup +You can use the physical infrastructure usergroup to manage physical infrastructures. Users that belong to this group have a default dashboard that contains physical server widgets. The physical server widgets show useful information, such as server health, availability, and recently discovered servers. +To gain the benefits of this usergroup, you must create a new user that belongs to the physical infrastructure group. + + +Follow the steps described in the Creating a User section in the CloudForms General Configuration documentation. For the group, choose EvmGroup-physical_infrastructure. + + +After the user is created, log in as the new user, and the default dashboard containing physical server widgets is displayed. +
 - -Troubleshooting Physical Infrastructure Provider Problems - + +Managing physical chassis +After the Lenovo physical-infrastructure provider is added, the physical chassis that are managed by XClarity Administrator are registered in CloudForms. You can then view and manage the chassis. +
+Viewing physical chassis +To view a list of all physical chassis that are managed by all physical-infrastructure providers, navigate to Compute > Physical Infrastructure > Chassis. The Physical Chassis page is displayed (see the following figure). +Tip: You can sort the table columns to make it easier to find a specific chassis. + + + + +physical chassis + +
+
+Locating a physical chassis +You can change the Location LED state on a physical chassis to locate a chassis in the data center. + + +Navigate to Compute > Physical Infrastructure > Chassis. + + +Select the physical chassis. The Physical Chassis Summary page is displayed. + + +Click on Identify in the top menu, and then click on the appropriate action: Blink LED, Turn On LED, or Turn Off LED. + + + + + + +physical chassis identify led + +
+ + +Managing physical racks +After the Lenovo physical-infrastructure provider is added, the physical racks that are managed by XClarity Administrator are registered in CloudForms. You can then view and manage the racks. +
+Viewing physical racks +To view a list of all physical racks that are managed by all physical-infrastructure providers, navigate to Compute > Physical Infrastructure > Racks. The Physical Racks page is displayed (see the following figure). +Tip: You can sort the table columns to make it easier to find a specific rack. + + + + +physical racks + +
+ + +Managing physical storage systems +After the Lenovo physical-infrastructure provider is added, the physical storage systems that are managed by XClarity Administrator are registered in CloudForms. You can then view and manage the storage systems. +
+Viewing physical storage systems +To view a list of all physical storage systems that are managed by all physical-infrastructure providers, navigate to Compute > Physical Infrastructure > Storages. The Physical Storages page is displayed (see the following figure). +Tip: You can sort the table columns to make it easier to find a specific storage system. + + + + +physical storage + +
+ + +Managing physical switches +After the Lenovo physical-infrastructure provider is added, the physical switches that are managed by XClarity Administrator are registered in CloudForms. You can then view and manage the switches. +
+Viewing physical switches +To view a list of all physical switches that are managed by all physical-infrastructure providers, navigate to Compute > Physical Infrastructure > Switches. The Physical Switches page is displayed (see the following figure). +Tip: You can sort the table columns to make it easier to find a specific switch. + + + + +physical switches + +
+
+Restarting physical switches +You can restart a physical switch that is managed by the physical-infrastructure provider. + + +Navigate to Compute > Physical Infrastructure > Switches. + + +Select a physical switch. The Physical Switches Summary page is displayed. + + +Click on Power in the top menu, and then click on Restart. + + + + + + +physical switch restart + +
 Automating tasks based on events -You can use CloudForms to automatically perform specific tasks when certain events occur on servers that are managed by Lenovo XClarity Administrator through a Lenovo physical-infrastructure provider. To create an automation task, you must create and configure a custom domain. To automatically invoke the task when a certain event occurs, you must create, configure and assign a custom policy. +You can use CloudForms to automatically perform specific tasks when certain events occur on servers that are managed by XClarity Administrator through a Lenovo physical-infrastructure provider. To create an automation task, you must create and configure a custom domain. To automatically invoke the task when a certain event occurs, you must create, configure and assign a custom policy. For more information about the CloudForms automation function, see Scripting Actions in CloudForms website.
Creating an automated task @@ -567,7 +959,7 @@ Enter a name for the new class instance (for example, FQXHMTS0003G, which is the event that is generated when inventory data cannot be retrieved from a device). -Important: The class-instance name must be the same as the name of the event that triggers the task to be invoked. CloudForms matches the class instance with the event by this name. To find the event name, see Messages in the Lenovo XClarity Administrator online documentation. +Important: The class-instance name must be the same as the name of the event that triggers the task to be invoked. CloudForms matches the class instance with the event by this name. To find the event name, see Messages in the XClarity Administrator online documentation. Add the path to the event handlers copied in the field’s rel3. @@ -593,10 +985,10 @@ physical_server_shutdown The policy actions and the policy events must match. For example, use the following path to the policy operation Physical Server Shutdown: +/System/event_handlers/event_action_policy?target=physical_server&policy_event=physical_server_shutdown&param= -/System/event_handlers/event_action_policy? target=physical_server&policy_event=physical_server_shutdown&param= -The policy_event value is matched with the policy operation applied. +The policy_event value is matched with the policy operation applied. Click Add. @@ -662,8 +1054,10 @@ The policy_event value is matched with the policy operation applied. Enter the following script in the Data field: -server = $evm.vmdb('PhysicalServer').first $evm.log(:info, "Powering Server #{server.name} OFF") -server.power_off exit MIQ_OK +server = $evm.vmdb('PhysicalServer').first +$evm.log(:info, "Powering Server #{server.name} OFF") +server.power_off +exit MIQ_OK Click Validate to verify the syntax. @@ -692,7 +1086,7 @@ server.power_off exit MIQ_OK Enter “execute” for the name. -Select “Method” for the type +Select “Method” for the type. Select “String” for the data type. @@ -877,4 +1271,132 @@ server.power_off exit MIQ_OK
+ +Creating an alert to monitor physical server health +Note: For this alert to work correctly, you must first configure the SMTP settings in CloudForms by following instructions in the Outgoing SMTP Email Settings section in the CloudForms Configuration documentation. +In CloudForms, there is a configurable alert for physical servers that sends an alert email when a server that is assigned to the alert is in an unhealthy state. This alert can be used to notify IT administrators that a server is in an unhealthy state, so that they can investigate and resolve potential issues before the issues lead to downtime. +To enable this alert, you must create a physical server alert profile, assign servers to the profile, and then configure the alert that is associated with the profile. +
+Step 1. Create a physical server alert profile + + +Navigate to Control > Explorer. + + +Click Alert Profiles > Physical Server Alert Profiles. + + +Click Configuration > Add a New Physical Server Alert Profile from the top menu. + + +Enter a description into the Description field. + + +Select Physical server has critical health state from the Available Physical Server Alerts list, and click on the > button to add it to the Profile Alerts list on the right. + + +Click Add. + + +
+
+Step 2. Assign servers to the alert profile + + +Click Alert Profiles > Physical Server Alert Profiles > ProfileName, where ProfileName is the name of the physical server alert that was previously created. + + +Click Configuration > Edit assignments for this Alert Profile. + + +Choose Selected Servers from the Assign To dropdown menu. + + +Select the checkboxes next to the servers that you want to assign to the profile from the Selections list. + + +Click Save. + + +
+
+Step 3. Configure the alert associated with the alert profile + + +Click Alert Profiles > Physical Server Alert Profiles > ProfileName > Physical server has critical health state, where ProfileName is the name of the physical server alert profile that was previously created. + + +Click Configuration > Edit this Alert from the top menu. + + +Select the Active checkbox to enable the alert. + + +Optionally, increase the notification frequency by selecting a new value from the Notification Frequency dropdown menu. The default frequency is one hour. + + +Ensure that the Send an E-mail checkbox is selected. + + +Optionally, enter a value into the From field. By default, the cfadmin@cfserver.com address is used. + + +Enter the email address that you want to retrieve the alert notification in the Add field, and then click the + button. The email address is displayed in the To field. + + +Click Save. + + +The assigned servers are checked hourly, and a notification is sent through email if the any of the assigned servers have a critical health state. +
+ + +Creating a policy to power on servers that are powered off +In CloudForms, there is a control policy for physical servers that automatically powers a server back on when it is powered off. +To enable this policy, you must assign the physical infrastructure profile to a server. + + +Navigate to Compute > Physical Infrastructure > Servers to display the Physical Servers page. + + +Click a server (to display the Physical Server Summary page), or select multiple servers that you want to provision. + + +Click Policy > Manage Policies from the top menu. The Physical Server Policy Assignment page is displayed. + + +Select the Physical Infrastructure Profile checkbox. + + +Click Save. + + +The policy is now assigned to the server. + + +Updating physical server firmware using Ansible playbooks +In CloudForms, physical server firmware can be updated using an Ansible playbook. +Note: An Ansible Tower provider that points to an Ansible Tower instance must be added to CloudForms. See the Adding an Ansible Tower Provider section in the CloudForms Managing Providers documentation. + + +Within Ansible Tower, create a job template for the config.yml playbook. Specify update_firmware as the job tag and any extra variables that are required by the playbook. Ensure that the option to prompt on launch is enabled. You can use this playbook to upgrade firmware on a physical server. You can get this playbook from the web at https://galaxy.ansible.com/lenovo/lxca-config. + + +Follow the steps that are described in the Executing an Ansible Tower Job Template from a Service Catalog section in the CloudForms Managing Providers documentation. Use the job template that you created in the previous step. + + + + +Provisioning physical servers using Ansible playbooks +In CloudForms, XClarity Administrator configuration patterns can be used to provision physical servers through the use of an Ansible playbook. Configuration patterns act as templates for configuring logical storage, I/O adapters, boot order, and other baseboard management controller and Unified Extensible Firmware Interface (UEFI) settings. +Note: An Ansible Tower provider that points to an Ansible Tower instance must be added to CloudForms. See the Adding an Ansible Tower Provider section in the CloudForms Managing Providers documentation. + + +Within Ansible Tower, create a job template for the config.yml playbook. Specify apply_configpatterns as the job tag and any extra variables that are required by the playbook. Ensure that the option to prompt on launch is enabled. You can use this playbook to apply a configuration pattern to a physical server. You can get this playbook from the web at https://galaxy.ansible.com/lenovo/lxca-config. + + +Follow the steps that are described in the Executing an Ansible Tower Job Template from a Service Catalog section in the CloudForms Managing Providers documentation. Use the job template that you created in the previous step. + + + \ No newline at end of file diff --git a/physical_infra_provider_configuration/l10n/es-ES/Author_Group.po b/physical_infra_provider_configuration/l10n/es-ES/Author_Group.po index df63fde..ab5e730 100644 --- a/physical_infra_provider_configuration/l10n/es-ES/Author_Group.po +++ b/physical_infra_provider_configuration/l10n/es-ES/Author_Group.po @@ -2,7 +2,7 @@ msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2018-02-26 09:57+1000\n" +"POT-Creation-Date: 2018-11-22 19:44+1000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -10,7 +10,7 @@ msgstr "" "Last-Translator: Sergio Ocón \n" "Language-Team: Spanish\n" "Language: es\n" -"X-Generator: Zanata 4.4.3\n" +"X-Generator: Zanata 4.6.2\n" "Plural-Forms: nplurals=2; plural=(n != 1)\n" msgid "Red Hat CloudForms" diff --git a/physical_infra_provider_configuration/l10n/es-ES/Revision_History.po b/physical_infra_provider_configuration/l10n/es-ES/Revision_History.po index 25c790a..7dfb2c1 100644 --- a/physical_infra_provider_configuration/l10n/es-ES/Revision_History.po +++ b/physical_infra_provider_configuration/l10n/es-ES/Revision_History.po @@ -2,7 +2,7 @@ msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2018-02-26 09:57+1000\n" +"POT-Creation-Date: 2018-11-22 19:44+1000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -10,7 +10,7 @@ msgstr "" "Last-Translator: trh01 \n" "Language-Team: Spanish\n" "Language: es\n" -"X-Generator: Zanata 4.4.3\n" +"X-Generator: Zanata 4.6.2\n" "Plural-Forms: nplurals=2; plural=(n != 1)\n" msgid "Revision History" diff --git a/physical_infra_provider_configuration/l10n/es-ES/main.po b/physical_infra_provider_configuration/l10n/es-ES/main.po index 2b6fe12..2494070 100644 --- a/physical_infra_provider_configuration/l10n/es-ES/main.po +++ b/physical_infra_provider_configuration/l10n/es-ES/main.po @@ -1,21 +1,26 @@ # Sergio Ocón , 2018. #zanata +# edrh02 , 2018. #zanata # trh01 , 2018. #zanata msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2018-02-26 09:57+1000\n" +"POT-Creation-Date: 2018-11-22 19:44+1000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"PO-Revision-Date: 2018-03-02 02:19+0000\n" -"Last-Translator: trh01 \n" +"PO-Revision-Date: 2018-12-05 09:04+0000\n" +"Last-Translator: edrh02 \n" "Language-Team: Spanish\n" "Language: es\n" -"X-Generator: Zanata 4.4.3\n" +"X-Generator: Zanata 4.6.2\n" "Plural-Forms: nplurals=2; plural=(n != 1)\n" -msgid "Configuring the Lenovo Physical Infrastructure Provider" -msgstr "Configurar el proveedor de infraestructura física de Lenovo" +msgid "" +"Configuring the Lenovo Physical Infrastructure Provider for Red Hat " +"CloudForms" +msgstr "" +"Configuración del Proveedor de infraestructura física de Lenovo para Red Hat " +"CloudForms" msgid "" "Adding and configuring the Lenovo physical infrastructure provider in Red " @@ -81,31 +86,43 @@ msgid "Key features include:" msgstr "Algunas de sus funciones principales:" msgid "" -"Seamlessly integrates with one or more Lenovo XClarity Administrator virtual " +"Seamlessly integrates with one or more XClarity Administrator virtual " "appliances, providing a summary view of the Lenovo infrastructure, " "relationship views of physical servers and virtual hosts, and configuration " -"of servers using Configuration Patterns" +"of servers using Configuration Patterns. In addition, there is a dashboard " +"view that displays the following:" msgstr "" -"Integración perfecta con una o más aplicaciones virtuales de Lenovo XClarity " +"Integración perfecta con una o más aplicaciones virtuales de XClarity " "Administrator que permite obtener una descripción resumida de la " -"infraestructura de Lenovo, vistas de las relaciones de los servidores " +"infraestructura de Lenovo, vistas de las relaciones de los servidores " "físicos y los hosts virtuales, y la configuración de los servidores mediante " -"patrones de configuración" +"patrones de configuración. Asimismo, hay una vista de tablero que muestra lo " +"siguiente:" + +msgid "" +"The number of servers, switches, racks, and storage systems being mangaged" +msgstr "" +"El número de servidores, switches, racks y sistemas de almacenamiento que se " +"gestiona" + +msgid "" +"Widgets that display information about server health, availability, and " +"recently discovered servers" +msgstr "" +"Widgets que muestran información sobre el estado del servidor, la " +"disponibilidad y los servidores descubiertos recientemente" msgid "" "Provides a single interface to monitor Lenovo hardware that is managed by " -"multiple instances of Lenovo XClarity Administrator" +"multiple instances of XClarity Administrator" msgstr "" -"Proporciona una única interfaz para supervisar hardware de Lenovo " -"administrado a través de múltiples instancias de Lenovo XClarity " -"Administrator" +"Proporciona una única interfaz para monitorear hardware de Lenovo " +"administrado a través de múltiples instancias de XClarity Administrator" msgid "" -"Automatically discovers hardware that is managed by Lenovo XClarity " -"Administrator" +"Automatically discovers hardware that is managed by XClarity Administrator" msgstr "" -"Detecta automáticamente el hardware administrado por Lenovo XClarity " -"Administrator" +"Detecta automáticamente el hardware administrado por XClarity Administrator" msgid "Manage devices for use in on-premise cloud deployments" msgstr "" @@ -138,145 +155,141 @@ msgstr "" msgid "" "Simplifies system management through custom policies and automation that " -"respond to the health status of physical servers" +"respond to the health status of hardware devices" msgstr "" "Simplifica la gestión del sistema mediante políticas personalizadas y " -"automatización que responde al estado de mantenimiento de los servidores " -"físicos" - -msgid "Configuring Lenovo XClarity Administrator" -msgstr "Configurar Lenovo XClarity Administrator" - -msgid "" -"Lenovo XClarity Administrator virtual appliances are connected to CloudForms " -"by adding physical-infrastructure providers. Physical-infrastructure " -"providers enable you to manage and interact with devices that are managed by " -"Lenovo XClarity Administrator. After the physical-infrastructure provider is " -"added, the servers that are managed by the Lenovo XClarity Administrator are " -"registered in CloudForms. Managed devices can be monitored, configured, and " -"updated using Lenovo XClarity Administrator. The physical-infrastructure " -"provider surfaces information about these managed devices and the Lenovo " -"XClarity Administrator instance." -msgstr "" -"Las aplicaciones virtuales de Lenovo XClarity Administrator se conectan a " -"CloudForms mediante los proveedores de infraestructura física que se añaden. " -"Los proveedores de infraestructura física permiten que usted controle e " -"interactúe con los dispositivos que son administrados por Lenovo XClarity " -"Administrator. Después de añadir el proveedor de infraestructura física, los " -"servidores que son administrados por Lenovo XClarity Administrator se " -"registran en CloudForms. Los dispositivos controlados se pueden supervisar, " -"configurar y actualizar mediante Lenovo XClarity Administrator. El " -"proveedor de infraestructura física proporciona información sobre estos " -"dispositivos controlados y la instancia de Lenovo XClarity Administrator." - -msgid "Setting up Lenovo XClarity Administrator" -msgstr "Configurar Lenovo XClarity Administrator" - -msgid "" -"For information about downloading and setting up Lenovo XClarity " -"Administrator, see Installing and setting up " -"Lenovo XClarity Administrator in the Lenovo XClarity Administrator " -"online documentation." -msgstr "" -"Para más información sobre la descarga y la configuración de Lenovo " -"XClarity Administrator, ver Instalar y configurar " -"Lenovo XClarity Administrator en la documentación en línea de Lenovo " -"XClarity Administrator." +"automatización que responde al estado de los dispositivos de hardware" + +msgid "Configuring XClarity Administrator" +msgstr "Configurar XClarity Administrator" + +msgid "" +"XClarity Administrator virtual appliances are connected to CloudForms by " +"adding physical-infrastructure providers. Physical-infrastructure providers " +"enable you to manage and interact with devices that are managed by XClarity " +"Administrator. After the physical-infrastructure provider is added, the " +"devices that are managed by the XClarity Administrator are registered in " +"CloudForms. Managed devices can be monitored, configured, and updated using " +"XClarity Administrator. The physical-infrastructure provider surfaces " +"information about these managed devices and the XClarity Administrator " +"instance." +msgstr "" +"Las aplicaciones virtuales de XClarity Administrator se conectan a " +"CloudForms mediante los proveedores de infraestructura física que se agregan." +" Los proveedores de infraestructura física permiten que usted controle e " +"interactúe con los dispositivos que son administrados por XClarity " +"Administrator. Después de agregar el proveedor de infraestructura física, " +"los dispositivos que son administrados por XClarity Administrator se " +"registran en CloudForms. Los dispositivos controlados se pueden monitorear, " +"configurar y actualizar mediante XClarity Administrator. El proveedor de " +"infraestructura física proporciona información sobre estos dispositivos " +"controlados y la instancia de XClarity Administrator." + +msgid "Setting up XClarity Administrator" +msgstr "Configurar XClarity Administrator" + +msgid "" +"For information about downloading and setting up XClarity Administrator, see " +"Installing and setting up Lenovo XClarity " +"Administrator in the XClarity Administrator online documentation." +msgstr "" +"Para obtener más información sobre la descarga y la configuración de " +"XClarity Administrator, consulte Instalar " +"y configurar Lenovo XClarity Administrator en la documentación en " +"línea de XClarity Administrator." msgid "" "Note: You can use all available " -"features in Lenovo XClarity Administrator for free for up to 90 days. After " -"90 days, you can continue to use Lenovo XClarity Administrator to manage and " -"monitor your hardware for free; however, you must purchase a full-function-" -"enablement license to continue using Lenovo XClarity Administrator to " -"configure your hardware using Configuration Patterns and to deploy operating " -"systems. Lenovo XClarity Pro provides entitlement to service and support and " -"the full-function-enablement license for Lenovo XClarity Administrator. For " -"more information about purchasing Lenovo XClarity Pro, contact your Lenovo " -"representative or authorized business partner." +"features in XClarity Administrator for free for up to 90 days. After 90 " +"days, you can continue to use XClarity Administrator to manage and monitor " +"your hardware for free; however, you must purchase a full-function-" +"enablement license to continue using XClarity Administrator to configure " +"your hardware using Configuration Patterns and to deploy operating systems. " +"Lenovo XClarity Pro provides entitlement to service and support and the full-" +"function-enablement license for XClarity Administrator. For more information " +"about purchasing Lenovo XClarity Pro, contact your Lenovo representative or " +"authorized business partner." msgstr "" "Nota: Puede usar todas las funciones " -"disponibles en Lenovo XClarity Administrator gratis durante 90 días. Después " -"de los 90 días, puede continuar usando Lenovo XClarity Administrator para " -"administrar y supervisar su hardware gratis; sin embargo, debe adquirir una " -"licencia para habilitar todas las funciones si quiere continuar utilizando " -"Lenovo XClarity Administrator para configurar su hardware mediante los " -"patrones de configuración y desplegar los sistemas operativos. Lenovo " -"XClarity Pro proporciona derechos de servicio y soporte, y la licencia para " -"habilitar todas las funciones de Lenovo XClarity Administrator. Para más " -"información sobre la adquisición de Lenovo XClarity Pro, contacte a un " -"partner empresarial autorizado o representante de servicios de Lenovo." - -msgid "Discovering and managing hardware using Lenovo XClarity Administrator" -msgstr "Detectar y administrar hardware con Lenovo XClarity Administrator" - -msgid "" -"Lenovo XClarity Administrator can discover manageable devices in your " -"environment by performing an SLP discovery for devices that are on the same " -"IP subnet as Lenovo XClarity Administrator. A specified IP address or range " -"of IP addresses also can be used, or information can be imported from a " -"spreadsheet, a process that is known as a bulk import. " -"Discovery options can be accessed by clicking Hardware > Discover and Manage New Devices from the " -"menu bar. Discovered devices can then be managed by Lenovo XClarity " -"Administrator. During the management process, you are asked for login " -"credentials for the management controller of the target servers and given " -"the option to create a recovery account for the servers. For more " -"information about discovering and managing devices, see the Lenovo XClarity Administrator online " +"disponibles en XClarity Administrator gratis durante 90 días. Después de los " +"90 días, puede continuar usando XClarity Administrator para administrar y " +"monitorear su hardware gratis; sin embargo, debe adquirir una licencia para " +"habilitar todas las funciones si quiere continuar utilizando XClarity " +"Administrator para configurar su hardware mediante los patrones de " +"configuración y desplegar los sistemas operativos. Lenovo XClarity Pro " +"proporciona derechos de servicio y soporte, y la licencia para habilitar " +"todas las funciones de XClarity Administrator. Para obtener más información " +"sobre la adquisición de XClarity Pro, contacte a un partner empresarial " +"autorizado o representante de Lenovo." + +msgid "Discovering and managing hardware using XClarity Administrator" +msgstr "Detectar y administrar hardware con XClarity Administrator" + +msgid "" +"XClarity Administrator can discover manageable devices in your environment " +"by performing an SLP discovery for devices that are on the same IP subnet as " +"XClarity Administrator. A specified IP address or range of IP addresses also " +"can be used, or information can be imported from a spreadsheet, a process " +"that is known as a bulk import. Discovery options can " +"be accessed by clicking Hardware > Discover and " +"Manage New Devices from the menu bar. Discovered devices can then " +"be managed by XClarity Administrator. During the management process, you are " +"asked for login credentials for the management controller of the target " +"servers and given the option to create a recovery account for the servers. " +"For more information about discovering and managing devices, see the XClarity Administrator online " "documentation." msgstr "" -"Lenovo XClarity Administrator puede detectar dispositivos controlados en su " -"entorno a través de una detección SLP de dispositivos que se encuentran en " -"la misma subred IP de Lenovo XClarity Administrator. También se puede " -"utilizar una dirección IP específica o un rango de direcciones IP o se puede " -"importar información de una hoja de cálculo, un proceso que es conocido como " +"XClarity Administrator puede detectar dispositivos controlados en su entorno " +"a través de una detección SLP de dispositivos que se encuentran en la misma " +"subred IP de XClarity Administrator. También se puede utilizar una dirección " +"IP específica o un rango de direcciones IP o se puede importar información " +"de una hoja de cálculo, un proceso que es conocido como " "importación masiva. Se puede acceder a las opciones de " -"detección al hacer clic en Hardware > Discover " -"and Manage New Devices en la barra del menú. De esta manera, " -"Lenovo XClarity Administrator puede controlar los dispositivos detectados. " +"detección al hacer clic en Hardware > Detectar " +"y gestionar nuevos dispositivos en la barra del menú. De esta " +"manera, XClarity Administrator puede controlar los dispositivos detectados. " "Durante el proceso de administración, le solicitarán las credenciales de " "acceso al controlador de gestión de los servidores objetivo y le darán la " -"opción de crear una cuenta de recuperación para los servidores. Para más " -"información sobre detección y administración de dispositivos, ver la documentación en línea de Lenovo " +"opción de crear una cuenta de recuperación para los servidores. Para obtener " +"más información sobre detección y administración de dispositivos, consulte " +"la documentación en línea de " "XClarity Administrator." msgid "Note:" msgstr "Nota:" msgid "" -"Ensure that the devices that you intend to manage are supported by Lenovo " -"XClarity Administrator. For information about supported devices, see Supported devices in the Lenovo " -"XClarity Administrator online documentation." +"Ensure that the devices that you intend to manage are supported by XClarity " +"Administrator. For information about supported devices, see Supported devices in the XClarity " +"Administrator online documentation." msgstr "" "Asegúrese de que los dispositivos que intenta controlar sean compatibles con " -"Lenovo XClarity Administrator. Para más información sobre dispositivos " -"compatibles, ver Dispositivos " -"compatibles en la documentación en línea de Lenovo XClarity " -"Administrator." +"XClarity Administrator. Para obtener más información sobre dispositivos " +"compatibles, consulte Dispositivos " +"compatibles en la documentación en línea de XClarity Administrator." msgid "" -"Ensure that firmware for all devices that you intend to manage using Lenovo " +"Ensure that firmware for all devices that you intend to manage using " "XClarity Administrator are at the required levels. For more information " "about supported firmware levels, see Supported firmware in the Lenovo XClarity Administrator " -"online documentation." +"1_3_1_2\">Supported firmware in the XClarity Administrator online " +"documentation." msgstr "" "Asegúrese de que el firmware para todos los dispositivos que intenta " -"controlar con Lenovo XClarity Administrator esté en los niveles requeridos. " -"Para más información sobre los niveles de firmware compatibles, ver Firmware compatible en la " -"documentación en línea de Lenovo XClarity Administrator." +"controlar con XClarity Administrator esté en los niveles requeridos. Para " +"obtener más información sobre los niveles de firmware compatibles, consulte " +"Firmware compatible en la " +"documentación en línea de XClarity Administrator." msgid "Managing physical-infrastructure providers" msgstr "Administrar los proveedores de infraestructura física" @@ -285,16 +298,15 @@ msgid "Adding a physical-infrastructure provider" msgstr "Añadir un proveedor de infraestructura física" msgid "" -"Lenovo XClarity Administrator virtual appliances are connected to CloudForms " -"by adding physical-infrastructure providers. Physical-infrastructure " -"providers enable you to manage and interact with devices that are managed by " -"Lenovo XClarity Administrator." -msgstr "" -"Las aplicaciones virtuales de Lenovo XClarity Administrator están conectadas " -"a CloudForms mediante los proveedores de infraestructura física que se " -"añadieron. Los proveedores de infraestructura física le permiten administrar " -"e interactuar con los dispositivos administrados por Lenovo XClarity " +"XClarity Administrator virtual appliances are connected to CloudForms by " +"adding physical-infrastructure providers. Physical-infrastructure providers " +"enable you to manage and interact with devices that are managed by XClarity " "Administrator." +msgstr "" +"Las aplicaciones virtuales de XClarity Administrator están conectadas a " +"CloudForms mediante los proveedores de infraestructura física que se " +"agregaron. Los proveedores de infraestructura física le permiten administrar " +"e interactuar con los dispositivos administrados por XClarity Administrator." msgid "" "Note: You must be logged in to " @@ -306,16 +318,16 @@ msgstr "" "es admin, la contraseña es smartvm." msgid "" -"Complete the following steps for each Lenovo XClarity Administrator instance " -"that you want to connect to CloudForms." +"Complete the following steps for each XClarity Administrator instance that " +"you want to connect to CloudForms." msgstr "" -"Completar los siguientes pasos para cada instancia de Lenovo XClarity " -"Administrator que desee conectar a CloudForms." +"Complete los siguientes pasos para cada instancia de XClarity Administrator " +"que desee conectar a CloudForms." -msgid "To connect to a specific Lenovo XClarity Administrator instance:" +msgid "To connect to a specific XClarity Administrator instance:" msgstr "" -"Para conectarse a una instancia específica de Lenovo XClarity Administrator, " -"haga lo siguiente:" +"Para conectarse a una instancia específica de XClarity Administrator, haga " +"lo siguiente:" msgid "" "Navigate to Compute > Physical Infrastructure " @@ -352,41 +364,40 @@ msgid "In the credentials area, provide the following:" msgstr "En el área de credenciales, proporcione la siguiente información:" msgid "" -"Enter the hostname, IPv4 address, or IPv6 address of the Lenovo XClarity " +"Enter the hostname, IPv4 address, or IPv6 address of the XClarity " "Administrator instance." msgstr "" -"Ingrese el nombre de host, la dirección IPv4 o IPv6 de la instancia de " -"Lenovo XClarity Administrator." +"Ingrese el nombre de host y la dirección IPv4 o IPv6 de la instancia de " +"XClarity Administrator." msgid "Enter “443” for the API port." msgstr "Ingrese \"443\" en el puerto de API." msgid "" -"Enter the username and password used to log in to the Lenovo XClarity " -"Administrator instance." +"Enter the username and password used to log in to the XClarity Administrator " +"instance." msgstr "" "Ingrese el nombre de usuario y la contraseña para iniciar sesión en la " -"instancia de Lenovo XClarity Administrator." +"instancia de XClarity Administrator." msgid "" "Click Validate to confirm that you can " -"connect to the Lenovo XClarity Administrator instance." +"connect to the XClarity Administrator instance." msgstr "" -"Haga clic en Validate para confirmar " -"que se puede conectar a la instancia de Lenovo XClarity Administrator." +"Haga clic en Validar para confirmar que " +"se puede conectar a la instancia de XClarity Administrator." msgid "Click Add." msgstr "Haga clic en Add." msgid "" -"To discover and then connect to a range of Lenovo XClarity Administrator " -"instances:" +"To discover and then connect to a range of XClarity Administrator instances:" msgstr "" -"Para detectar y luego conectarse a un rango de instancias de Lenovo XClarity " +"Para detectar y luego conectarse a un rango de instancias de XClarity " "Administrator, haga lo siguiente:" -msgid "Discover Lenovo XClarity Administrator instances:" -msgstr "Para detectar las instancias de Lenovo XClarity Administrator:" +msgid "Discover XClarity Administrator instances:" +msgstr "Para detectar las instancias de XClarity Administrator:" msgid "" "Navigate to Compute > Physical Infrastructure " @@ -432,10 +443,10 @@ msgstr "" msgid "" "Update credentials for each discovered physical-infrastructure provider " -"(Lenovo XClarity Administrator instance):" +"(XClarity Administrator instance):" msgstr "" "Actualice las credenciales para cada proveedor de infraestructura física " -"detectado (la instancia de Lenovo XClarity Administrator):" +"detectado (instancia de XClarity Administrator):" msgid "Select the providers to be edited." msgstr "Seleccione los proveedores que serán editados." @@ -545,6 +556,56 @@ msgid "Make the required changes, and revalidate credentials if necessary." msgstr "" "Realice los cambios requeridos y revalide las credenciales si es necesario." +msgid "" +"Changing the password of the XClarity Administrator instance through its " +"physical-infrastructure provider" +msgstr "" +"Cambiar la contraseña de la instancia de XClarity Administrator a través de " +"su proveedor de infraestructura física" + +msgid "" +"Within CloudForms, you can change the password of an XClarity Administrator " +"instance through the physical-infrastructure provider with which it is " +"associated. Changing the password this way also changes the password in " +"CloudForms so that they match." +msgstr "" +"Dentro de CloudForms, puede cambiar la contraseña de una instancia de " +"XClarity Administrator a través del proveedor de infraestructura física, con " +"el que está asociado. Al cambiar la contraseña de esta forma, también se " +"modifica la contraseña en CloudForms, para que coincidan." + +msgid "Click on the physical-infrastructure provider to be modified." +msgstr "Haga clic en el proveedor de infraestructura física para modificar." + +msgid "" +"Click on the Authentication button in " +"the top menu and select Change password." +" The Change Password for Physical Infrastructure Provider page is displayed." +msgstr "" +"Haga clic en el botón Autenticación del " +"menú superior y seleccione Cambiar contraseña. Aparecerá la página Cambiar contraseña para el Proveedor de " +"infraestructura física." + +msgid "" +"Enter the current password for the XClarity Administrator instance in the " +"Current Password field." +msgstr "" +"Ingrese la contraseña actual de la instancia de XClarity Administrator en el " +"campo Contraseña actual." + +msgid "" +"Enter the new password in the New Password and Confirm New Password " +"fields." +msgstr "" +"Ingrese la nueva contraseña en los campos Nueva " +"contraseña y Confirmar nueva " +"contraseña." + +msgid "Click Save." +msgstr "Haga clic en Save." + msgid "Viewing relationships" msgstr "Ver las relaciones" @@ -582,17 +643,23 @@ msgstr "" "Para mostrar la vista de topología de un proveedor de infraestructura física " "específico, realice los siguientes pasos." -msgid "Select the physical-infrastructure provider to be viewed." -msgstr "Seleccione el proveedor de infraestructura física que desea ver." +msgid "Click on the physical-infrastructure provider to be viewed." +msgstr "Haga clic en el proveedor de infraestructura física que desea ver." + +msgid "Once the page loads, ensure that the summary view is being used." +msgstr "" +"Una vez que se carga la página, asegúrese de que se esté utilizando la vista " +"de resumen." msgid "" -"From the overview section, select Topology to display the Topology page. From this page, you can perform the " -"following actions:" +"Click on Topology in the Overview table to display the Topology page. From this " +"page, you can perform the following actions:" msgstr "" -"Seleccione Topology en la sección " -"visión general para mostrar la página de topología. Desde esta página podrá " -"realizar las siguientes acciones:" +"Haga clic en Topología en la tabla " +"Descripción general para que aparezca " +"la página Topología. Desde esta página, podrá realizar las siguientes " +"acciones:" msgid "" "Hide or show all physical server by clicking VMs." +msgid "" +"Hide or show nodes in the graph that have a particular health state by " +"clicking on one of the following states: Valid, Warning, Critical, or Unknown." +msgstr "" +"Oculte o muestre los nodos en el gráfico que tienen un estado particular " +"haciendo clic en uno de los siguientes estados: Válido, Advertencia, Crítico, o Desconocido." + msgid "" "Double-click or right-click a node in the graph to navigate to the summary " "pages for that node." @@ -631,12 +711,35 @@ msgstr "" "Puede ver un listado de todos los servidores físicos que son administrados " "por un proveedor de infraestructura física específico." +msgid "From the physical-infrastructure provider summary view" +msgstr "Desde la vista de resumen del proveedor de infraestructura física" + +msgid "After the page loads, ensure that the summary view is being used." +msgstr "" +"Una vez que se carga la página, asegúrese de que se esté utilizando la vista " +"de resumen." + msgid "" -"Click Physical Servers in the Relationships section." +"Click on Physical Servers in the " +"Relationships table." msgstr "" -"Haga clic en Physical Servers en la " -"sección Relationships." +"Haga clic en Servidores físicos en la " +"tabla Relaciones." + +msgid "From the physical-infrastructure provider dashboard view" +msgstr "Desde la vista de panel del proveedor de infraestructura física" + +msgid "After the page loads, ensure that the dashboard view is being used." +msgstr "" +"Una vez que se carga la página, asegúrese de que se esté utilizando la vista " +"del escritorio." + +msgid "" +"Click on the number of servers that is displayed displayed in the Servers card." +msgstr "" +"Haga clic en el número de servidores que aparece en la tarjeta Servidores." msgid "Viewing virtual-host relationships" msgstr "Ver las relaciones de los hosts virtuales" @@ -649,18 +752,18 @@ msgstr "" "que son administrados por un proveedor de infraestructura física específico." msgid "" -"Click Physical Servers with Host button " -"in the Relationships section." +"Click on Physical Servers with Host in " +"the Relationships table." msgstr "" -"Haga clic en el botón Physical Servers with Host en la sección Relationships." +"Haga clic en Servidores físicos con host en la tabla Relaciones." msgid "" -"You should see a list of physical servers that are associated with hosts as " +"A list of physical servers that are associated with hosts are displayed as " "shown below." msgstr "" -"Verá un listado de los servidores físicos que están asociados con los hosts " -"como se muestra a continuación." +"A continuación, se muestra un listado de los servidores físicos que están " +"asociados con los hosts." msgid "" " relaciones de los hosts " +msgid "Viewing storage relationships" +msgstr "Ver las relaciones de almacenamiento" + +msgid "" +"You can view a list of all storage systems that are managed by a specific " +"physical-infrastructure provider." +msgstr "" +"Puede ver un listado de todos los sistemas de almacenamiento que son " +"administrados por un proveedor de infraestructura física específico." + +msgid "" +"Click on Physical Storages in the " +"Relationships table." +msgstr "" +"Haga clic en Almacenamientos físicos en " +"la tabla Relaciones." + +msgid "" +"Click on the number of storage systems that is displayed in the Storages card." +msgstr "" +"Haga clic en el número de sistemas de almacenamiento que aparece en la " +"tarjeta Almacenamientos." + +msgid "Viewing switch relationships" +msgstr "Ver las relaciones de los switches" + +msgid "" +"You can view a list of all switches that are managed by a specific physical-" +"infrastructure provider." +msgstr "" +"Puede ver un listado de todos los switches que son administrados por un " +"proveedor de infraestructura física específico." + +msgid "" +"Click on Physical Switches in the " +"Relationships table." +msgstr "" +"Haga clic en Switches físicos en la " +"tabla Relaciones." + +msgid "" +"Click on the number of switches that is displayed in the Switches card." +msgstr "" +"Haga clic en el número de switches que aparece en la tarjeta Switches." + +msgid "Viewing chassis relationships" +msgstr "Ver las relaciones de los chasis" + +msgid "" +"You can view a list of chassis that are managed by a specific physical-" +"infrastructure provider." +msgstr "" +"Puede ver un listado de chasis que son administrados por un proveedor de " +"infraestructura física específico." + +msgid "" +"Click on Physical Chassis in the " +"Relationships table." +msgstr "" +"Haga clic en Chasis físicos en la tabla " +"Relaciones." + +msgid "" +"Click on the number of chassis that is displayed in the Chassis card." +msgstr "" +"Haga clic en el número de chasis que aparece en la tarjeta Chasis." + +msgid "Viewing rack relationships" +msgstr "Ver las relaciones del rack" + +msgid "" +"You can view a list of all racks that are managed by a specific physical-" +"infrastructure provider." +msgstr "" +"Puede ver un listado de todos los racks que son administrados por un " +"proveedor de infraestructura física específico." + +msgid "" +"Click on Physical Racks in the " +"Relationships table." +msgstr "" +"Haga clic en Racks físicos en la tabla " +"Relaciones." + +msgid "" +"Click on the number of racks that is displayed in the Racks card." +msgstr "" +"Haga clic en el número de racks que aparece en la tarjeta Racks." + msgid "Managing physical servers" msgstr "Administrar servidores físicos" msgid "" "After the Lenovo physical-infrastructure provider is added, the servers that " -"are managed by Lenovo XClarity Administrator are registered in CloudForms. " -"You can then view and manage those servers." +"are managed by XClarity Administrator are registered in CloudForms. You can " +"then view and manage those servers." +msgstr "" +"Después de agregar el proveedor de infraestructura física Lenovo, los " +"servidores que son administrados por XClarity Administrator se registran en " +"CloudForms. De esta manera, puede ver y administrar esos servidores." + +msgid "" +"Note: It may take a few seconds or so for the servers " +"to appear after adding a physical-infrasturcture provider." msgstr "" -"Después de añadir al proveedor de infraestructura física Lenovo, los " -"servidores que son administrados por Lenovo XClarity Administrator se " -"registran en CloudForms. De esta manera, puede ver y administrar esos " -"servidores." +"Nota: Después de agregar un proveedor de " +"infraestructura física, los servidores pueden demorar algunos segundos en " +"aparecer." msgid "Viewing a Physical Server" msgstr "Ver un servidor físico" @@ -905,31 +1111,31 @@ msgid "Provisioning physical servers using configuration patterns" msgstr "Proporcionar servidores físicos con patrones de configuración" msgid "" -"You can use configuration patterns in Lenovo XClarity Administrator to " -"quickly provision or preprovision multiple servers from a single set of " -"defined configuration settings. Configuration patterns act as templates for " +"You can use configuration patterns in XClarity Administrator to quickly " +"provision or preprovision multiple servers from a single set of defined " +"configuration settings. Configuration patterns act as templates for " "configuring logical storage, I/O adapters, boot order, and other baseboard " "management controller and Unified Extensible Firmware Interface (UEFI) " "settings." msgstr "" -"Puede usar los patrones de configuración en Lenovo XClarity Administrator " -"para aprovisionar o aprovisionar con anticipación a servidores múltiples " -"desde un conjunto único de configuraciones definidas. Los patrones de " -"configuración funcionan como plantillas para configurar el almacenamiento " -"lógico, los adaptadores de entrada y salida y otras configuraciones del " +"Puede usar los patrones de configuración en XClarity Administrator para " +"aprovisionar o aprovisionar con anticipación servidores múltiples desde un " +"conjunto único de configuraciones definidas. Los patrones de configuración " +"funcionan como plantillas para configurar el almacenamiento lógico, los " +"adaptadores de entrada y salida, así como otras configuraciones del " "controlador de administración del tablero y la interfaz de firmware " "extensible y unificada (UEFI)." msgid "" "A physical-infrastructure provider can discover configuration patterns that " -"are defined on the associated Lenovo XClarity Administrator instance. A " +"are defined on the associated XClarity Administrator instance. A " "configuration pattern can then be applied to a single or multiple physical " "servers." msgstr "" "Un proveedor de infraestructura física puede detectar los patrones de " -"configuración que están definidos en la instancia asociada de Lenovo " -"XClarity Administrator. De esta manera, un patrón de configuración se puede " -"aplicar a uno o a múltiples servidores físicos." +"configuración que están definidos en la instancia asociada de XClarity " +"Administrator. De esta manera, un patrón de configuración se puede aplicar a " +"uno o a múltiples servidores físicos." msgid "" "Note: Configuration patterns can be " @@ -1029,26 +1235,453 @@ msgstr "" "estado de la acción en la tabla Requests." -msgid "Troubleshooting Physical Infrastructure Provider Problems" -msgstr "Solucionar problemas de proveedores de infraestructura física" +msgid "Viewing network devices that are associated with a physical server" +msgstr "Ver los dispositivos de red asociados con un servidor físico" + +msgid "" +"From the Physical Server Summary page, you can access details about network " +"devices such as network interface cards." +msgstr "" +"Desde la página Resumen de servidor físico, puede acceder a detalles sobre " +"los dispositivos de red, como las tarjetas de interfaz de red." + +msgid "" +"Access the Physical Servers page, as described in the section, and then select a physical server. " +"The Physical Server Summary page is displayed." +msgstr "" +"Acceda a la página Servidores físicos, según se describe en la sección ; luego, seleccione un servidor " +"físico. Aparecerá la página Resumen de servidor físico." + +msgid "" +"Click on the Network Devices count in " +"the Properties table. A list of network " +"devices is displayed." +msgstr "" +"Haga clic en el número de Dispositivos de red en la tabla Propiedades. " +"Aparecerá un listado de dispositivos de red." + +msgid "" +"Select a network device from the list. The Network Device Summary page is " +"displayed." +msgstr "" +"Seleccione un dispositivo de red de la lista. Aparecerá la página Resumen de " +"dispositivo de red." + +msgid "" +" " +"network device summary " +msgstr "" +" " +"resumen de dispositivo de red " + +msgid "Viewing storage devices that are associated with a physical server" +msgstr "" +"Ver los dispositivos de almacenamiento asociados con un servidor físico" + +msgid "" +"From the Physical Server Summary page, you can access details about storage " +"devices, such as RAID cards." +msgstr "" +"Desde la página Resumen de servidor físico, puede acceder a detalles sobre " +"los dispositivos de almacenamiento, como las tarjetas RAID." + +msgid "" +"Click on the Storage Devices count in " +"the Properties table. A list of storage " +"devices is displayed." +msgstr "" +"Haga clic en el número de Dispositivos de " +"almacenamiento en la tabla Propiedades. Aparecerá un listado de dispositivos de almacenamiento." + +msgid "" +"Select a storage device from the list. The Storage Device Summary page is " +"displayed." +msgstr "" +"Seleccione un dispositivo de almacenamiento de la lista. Aparecerá la página " +"Resumen de dispositivo de almacenamiento." + +msgid "" +" " +"storage device summary " +msgstr "" +" " +"resumen de dispositivo de almacenamiento " + +msgid "Adding physical server widgets to the dashboard" +msgstr "Agregar widgets de servidor físico al tablero" + +msgid "" +"You can add widgets that display information about physical servers to the " +"default dashboard." +msgstr "" +"Puede agregar widgets que muestran información sobre los servidores físicos " +"en el tablero predeterminado." + +msgid "" +"Navigate to Cloud Intel > Dashboard." +msgstr "" +"Navegue a Inteligencia de nube > Tablero." + +msgid "" +"Click on the + button from the top " +"menu, and select one of the following widgets:" +msgstr "" +"Haga clic en el botón + del menú " +"superior y seleccione uno de los siguientes widgets:" + +msgid "Physical Server Availability" +msgstr "Disponibilidad del servidor físico" + +msgid "Physical Server Health" +msgstr "Estado del servidor físico" + +msgid "" +"Recently Discovered Physical Servers" +msgstr "" +"Servidores físicos recientemente detectados" + +msgid "The widget is now displayed on the default dashboard." +msgstr "El widget ahora aparece en el tablero predeterminado." + +msgid "Creating a user that belongs to the physical infrastructure usergroup" +msgstr "" +"Creación de un usuario que pertenece al grupo de usuarios de infraestructura " +"física" + +msgid "" +"You can use the physical infrastructure usergroup to manage physical " +"infrastructures. Users that belong to this group have a default dashboard " +"that contains physical server widgets. The physical server widgets show " +"useful information, such as server health, availability, and recently " +"discovered servers." +msgstr "" +"Puede usar el grupo de usuarios de infraestructura física para gestionar las " +"infraestructuras físicas. Los usuarios que pertenecen a este grupo cuentan " +"con un tablero predeterminado que contiene widgets de servidor físico. Los " +"widgets de servidor físico muestran información útil, como el estado del " +"servidor, la disponibilidad y los servidores recientemente detectados." + +msgid "" +"To gain the benefits of this usergroup, you must create a new user that " +"belongs to the physical infrastructure group." +msgstr "" +"Para obtener los beneficios de este grupo de usuarios, debe crear un nuevo " +"usuario que pertenezca al grupo de infraestructura física" + +msgid "" +"Follow the steps described in the Creating a User " +"section in the CloudForms General Configuration " +"documentation. For the group, choose EvmGroup-" +"physical_infrastructure." +msgstr "" +"Siga estos pasos descritos en la sección Crear un usuario en la documentación Configuración general de CloudForms. Para el grupo, elija EvmGroup-physical_infrastructure." + +msgid "" +"After the user is created, log in as the new user, and the default dashboard " +"containing physical server widgets is displayed." +msgstr "" +"Después de crear el usuario, inicie sesión como usuario nuevo y aparecerá el " +"tablero que contiene los widgets de servidor físico." + +msgid "Managing physical chassis" +msgstr "Administrar chasis físicos" + +msgid "" +"After the Lenovo physical-infrastructure provider is added, the physical " +"chassis that are managed by XClarity Administrator are registered in " +"CloudForms. You can then view and manage the chassis." +msgstr "" +"Después de agregar el proveedor de infraestructura física Lenovo, los chasis " +"físicos que son administrados por XClarity Administrator se registran en " +"CloudForms. De esta manera, puede ver y administrar los chasis." + +msgid "Viewing physical chassis" +msgstr "Ver un chasis físico" + +msgid "" +"To view a list of all physical chassis that are managed by all physical-" +"infrastructure providers, navigate to Compute > " +"Physical Infrastructure > Chassis. The Physical Chassis page " +"is displayed (see the following figure)." +msgstr "" +"Para ver un listado de todos los chasis físicos administrados por todos los " +"proveedores de infraestructura física, navegue a Cálculo > Infraestructura física > Servidores. " +"Se muestra la página Chasis físicos (ver la figura a continuación)." + +msgid "" +"Tip: You can sort the table columns to " +"make it easier to find a specific chassis." +msgstr "" +"Consejo: Puede clasificar las columnas " +"de la tabla para que sea más fácil encontrar un chasis específico." + +msgid "" +" " +"physical chassis " +msgstr "" +" " +"chasis físico " + +msgid "Locating a physical chassis" +msgstr "Ubicar un chasis físico" + +msgid "" +"You can change the Location LED state on a physical chassis to locate a " +"chassis in the data center." +msgstr "" +"Puede modificar la ubicación del estado del LED en un chasis físico para " +"localizar un chasis en el centro de datos." + +msgid "" +"Navigate to Compute > Physical Infrastructure " +"> Chassis." +msgstr "" +"Navegue a Cálculo > Infraestructura > " +"Servidores.." + +msgid "" +"Select the physical chassis. The Physical Chassis Summary page is displayed." +msgstr "" +"Seleccione el chasis físico. Aparecerá la página Resumen del chasis físico." + +msgid "" +"Click on Identify in the top menu, and " +"then click on the appropriate action: Blink LED, Turn On LED, or Turn Off LED." +msgstr "" +"Haga clic en Identificar en el menú " +"superior y, luego, en la acción que corresponda: Blink LED (Parpadeo del LED), Turn On LED (Encender el LED) o Turn Off LED (Apagar el LED)." + +msgid "" +" physical chassis identify led " +msgstr "" +" Led de identificación de chasis físico " + +msgid "Managing physical racks" +msgstr "Administrar racks físicos" + +msgid "" +"After the Lenovo physical-infrastructure provider is added, the physical " +"racks that are managed by XClarity Administrator are registered in " +"CloudForms. You can then view and manage the racks." +msgstr "" +"Después de agregar el proveedor de infraestructura física Lenovo, los racks " +"físicos que son administrados por XClarity Administrator se registran en " +"CloudForms. De esta manera, puede ver y administrar los racks." + +msgid "Viewing physical racks" +msgstr "Ver racks físicos" + +msgid "" +"To view a list of all physical racks that are managed by all physical-" +"infrastructure providers, navigate to Compute > " +"Physical Infrastructure > Racks. The Physical Racks page is " +"displayed (see the following figure)." +msgstr "" +"Para ver un listado de todos los racks físicos administrados por todos los " +"proveedores de infraestructura física, navegue a Cálculo > Infraestructura física > Servidores. " +"Se muestra la página Racks físicos (ver la figura a continuación)." + +msgid "" +"Tip: You can sort the table columns to " +"make it easier to find a specific rack." +msgstr "" +"Consejo: Puede clasificar las columnas " +"de la tabla para que sea más fácil encontrar un rack específico." + +msgid "" +" " +"physical racks " +msgstr "" +" " +"racks físicos " + +msgid "Managing physical storage systems" +msgstr "Administrar sistemas de almacenamiento físico" + +msgid "" +"After the Lenovo physical-infrastructure provider is added, the physical " +"storage systems that are managed by XClarity Administrator are registered in " +"CloudForms. You can then view and manage the storage systems." +msgstr "" +"Después de agregar el proveedor de infraestructura física Lenovo, los " +"sistemas de almacenamiento físico que son administrados por XClarity " +"Administrator se registran en CloudForms. De esta manera, puede ver y " +"administrar los sistemas de almacenamiento." + +msgid "Viewing physical storage systems" +msgstr "Ver sistemas de almacenamiento físico" + +msgid "" +"To view a list of all physical storage systems that are managed by all " +"physical-infrastructure providers, navigate to Compute > Physical Infrastructure > Storages. " +"The Physical Storages page is displayed (see the following figure)." +msgstr "" +"Para ver un listado de todos los sistemas de almacenamiento físico " +"administrados por todos los proveedores de infraestructura física, navegue a " +"Cálculo > Infraestructura física > " +"Servidores. Se muestra la página Almacenamientos físicos (ver la " +"figura a continuación)." + +msgid "" +"Tip: You can sort the table columns to " +"make it easier to find a specific storage system." +msgstr "" +"Consejo: Puede clasificar las columnas " +"de la tabla para que sea más fácil encontrar un sistema de almacenamiento " +"específico." + +msgid "" +" " +"physical storage " +msgstr "" +" " +"almacenamiento físico " + +msgid "Managing physical switches" +msgstr "Administrar switches físicos" + +msgid "" +"After the Lenovo physical-infrastructure provider is added, the physical " +"switches that are managed by XClarity Administrator are registered in " +"CloudForms. You can then view and manage the switches." +msgstr "" +"Después de agregar el proveedor de infraestructura física Lenovo, los " +"switches físicos que son administrados por XClarity Administrator se " +"registran en CloudForms. De esta manera, puede ver y administrar los " +"switches." + +msgid "Viewing physical switches" +msgstr "Ver switches físicos" + +msgid "" +"To view a list of all physical switches that are managed by all physical-" +"infrastructure providers, navigate to Compute > " +"Physical Infrastructure > Switches. The Physical Switches page " +"is displayed (see the following figure)." +msgstr "" +"Para ver un listado de todos los switches físicos administrados por todos " +"los proveedores de infraestructura física, navegue a Cálculo > Infraestructura física > Servidores. " +"Se muestra la página Switches físicos (ver la figura a continuación)." + +msgid "" +"Tip: You can sort the table columns to " +"make it easier to find a specific switch." +msgstr "" +"Consejo: Puede clasificar las columnas " +"de la tabla para que sea más fácil encontrar un switch específico." + +msgid "" +" " +"physical switches " +msgstr "" +" " +"switches físicos " + +msgid "Restarting physical switches" +msgstr "Reiniciar switches físicos" + +msgid "" +"You can restart a physical switch that is managed by the physical-" +"infrastructure provider." +msgstr "" +"Puede reiniciar un switch físico que es gestionado por el proveedor de " +"infraestructura física." + +msgid "" +"Navigate to Compute > Physical Infrastructure " +"> Switches." +msgstr "" +"Navegue a Cálculo > Infraestructura física > " +"Servidores.." + +msgid "" +"Select a physical switch. The Physical Switches Summary page is displayed." +msgstr "" +"Seleccione un switch físico. Aparecerá la página Resumen de switches físicos." +"" + +msgid "" +"Click on Power in the top menu, and " +"then click on Restart." +msgstr "" +"Haga clic en Potencia en el menú " +"superior y, luego, haga clic en Reiniciar." + +msgid "" +" " +"physical switch restart " +msgstr "" +" " +"reinicio de switch físico " msgid "Automating tasks based on events" msgstr "Automatizar las tareas según los eventos" msgid "" "You can use CloudForms to automatically perform specific tasks when certain " -"events occur on servers that are managed by Lenovo XClarity Administrator " -"through a Lenovo physical-infrastructure provider. To create an automation " -"task, you must create and configure a custom domain. To automatically invoke " -"the task when a certain event occurs, you must create, configure and assign " -"a custom policy." +"events occur on servers that are managed by XClarity Administrator through a " +"Lenovo physical-infrastructure provider. To create an automation task, you " +"must create and configure a custom domain. To automatically invoke the task " +"when a certain event occurs, you must create, configure and assign a custom " +"policy." msgstr "" "Puede usar CloudForms para realizar tareas específicas de forma automática " -"cuando ciertos eventos ocurren en los servidores administrados por Lenovo " -"XClarity Administrator con un proveedor de infraestructura física de Lenovo. " -"Para crear una tarea automática, debe crear y configurar un dominio " -"personalizado. Para invocar automáticamente la tarea cuando ocurre un evento " -"determinado, configure y asigne una política personalizada." +"cuando ciertos eventos ocurren en los servidores administrados por XClarity " +"Administrator con un proveedor de infraestructura física de Lenovo. Para " +"crear una tarea automática, debe crear y configurar un dominio personalizado." +" Para invocar automáticamente la tarea cuando ocurre un evento determinado, " +"configure y asigne una política personalizada." msgid "" "For more information about the CloudForms automation function, see Messages in the " -"Lenovo XClarity Administrator online documentation." +"XClarity Administrator online documentation." msgstr "" -"Importante: el nombre de la instancia " -"de clase debe ser el mismo que el nombre del evento que activó la tarea a " +"Importante: El nombre de la instancia " +"de clase debe ser el mismo que el nombre del evento que activó la tarea por " "invocar. CloudForms relaciona la instancia de clase con el evento mediante " -"este nombre. Para encontrar el nombre del evento, ver Messages en la documentación en línea de Lenovo " -"XClarity Administrator." +"html?cp=1_22_16\">Mensajes en la documentación en línea de XClarity " +"Administrator." msgid "" "Add the path to the event handlers copied in the field’s Physical Server Shutdown:" msgid "" -"/System/event_handlers/event_action_policy? target=" -"physical_server&policy_event=physical_server_shutdown&param=\n" -"The policy_event value is matched with the policy operation applied." +"/System/event_handlers/event_action_policy?target=" +"physical_server&policy_event=physical_server_shutdown&param=" msgstr "" -"/System/event_handlers/event_action_policy? target=" -"physical_server&policy_event=physical_server_shutdown&param=\n" -"El valor del evento de política corresponde a la operación de política " -"aplicada." +"/System/event_handlers/event_action_policy?target=" +"physical_server&policy_event=physical_server_shutdown&param=" + +msgid "The policy_event value is matched with the policy operation applied." +msgstr "" +"El valor policy_event corresponde a la operación de política aplicada." msgid "Step 3. Create a namespace." msgstr "Paso 3. Crear un espacio de nombre." @@ -1397,9 +2031,10 @@ msgstr "" "emphasis>:" msgid "" -"server = $evm.vmdb('PhysicalServer').first $evm.log(:info, \"Powering Server " -"#{server.name} OFF\")\n" -"server.power_off exit MIQ_OK" +"server = $evm.vmdb('PhysicalServer').first\n" +"$evm.log(:info, \"Powering Server #{server.name} OFF\")\n" +"server.power_off\n" +"exit MIQ_OK" msgstr "" "server = $evm.vmdb('PhysicalServer').first $evm.log(:info, \"Powering Server " "#{server.name} OFF\")\n" @@ -1434,8 +2069,8 @@ msgstr "" msgid "Enter “execute” for the name." msgstr "Ingrese “execute” para el nombre." -msgid "Select “Method” for the type" -msgstr "Seleccione “Method” para el tipo." +msgid "Select “Method” for the type." +msgstr "Seleccione “Método” para el tipo." msgid "Select “String” for the data type." msgstr "" @@ -1452,9 +2087,6 @@ msgstr "" msgid "Click the check mark icon." msgstr "Haga clic en el botón de verificación." -msgid "Click Save." -msgstr "Haga clic en Save." - msgid "Add the method to the class." msgstr "Añadir el método a la clase." @@ -1686,3 +2318,319 @@ msgstr "" "images/provider_assign_profile.png\" /> " "perfil asignado a proveedor " + +msgid "Creating an alert to monitor physical server health" +msgstr "Creación de una alerta para monitorear el estado del servidor físico" + +msgid "" +"Note: For this alert to work correctly, you must first " +"configure the SMTP settings in CloudForms by following instructions in the " +"Outgoing SMTP Email Settings section in the " +"CloudForms Configuration documentation." +msgstr "" +"Nota: Para que esta alerta funcione correctamente, " +"primero debe configurar SMTP en CloudForms siguiendo instrucciones en la " +"sección Configuración de correo electrónico de SMTP saliente en la documentación Configuración de CloudForms." + +msgid "" +"In CloudForms, there is a configurable alert for physical servers that sends " +"an alert email when a server that is assigned to the alert is in an " +"unhealthy state. This alert can be used to notify IT administrators that a " +"server is in an unhealthy state, so that they can investigate and resolve " +"potential issues before the issues lead to downtime." +msgstr "" +"En CloudForms, existe una alerta configurable para servidores físicos que " +"envía un correo electrónico de alerta cuando un servidor asignado a la " +"alerta se encuentra en mal estado. Esta alerta se puede usar para notificar " +"a los administradores de TI que un servidor se encuentra en mal estado, de " +"manera que puedan investigar y resolver posibles problemas antes de que " +"generen tiempo de inactividad." + +msgid "" +"To enable this alert, you must create a physical server alert profile, " +"assign servers to the profile, and then configure the alert that is " +"associated with the profile." +msgstr "" +"Para activar esta alerta, debe crear un perfil de alerta del servidor " +"físico, asignar servidores al perfil y, luego, configurar la alerta asociada " +"con el perfil." + +msgid "Step 1. Create a physical server alert profile" +msgstr "Paso 1: Crear un perfil de alerta del servidor físico" + +msgid "" +"Click Alert Profiles > Physical Server Alert " +"Profiles." +msgstr "" +"Haga clic en Perfiles de alerta > Perfiles de " +"alerta del servidor físico." + +msgid "" +"Click Configuration > Add a New Physical Server " +"Alert Profile from the top menu." +msgstr "" +"Haga clic en Configuración > Agregar un nuevo " +"perfil de alerta de servidor físico en el menú superior." + +msgid "" +"Enter a description into the Description field." +msgstr "" +"Ingrese una descripción en el campo Descripción." + +msgid "" +"Select Physical server has critical health state from the Available Physical Server " +"Alerts list, and click on the > button to add it to the Profile Alerts list on the right." +msgstr "" +"Seleccione El estado del servidor físico es " +"crítico de la lista Alertas del " +"servidor físico disponibles y haga clic en el botón > para agregarlo a la lista Alertas de perfil en la derecha." + +msgid "Step 2. Assign servers to the alert profile" +msgstr "Paso 2. Asigne servidores al perfil de alertas" + +msgid "" +"Click Alert Profiles > Physical Server Alert " +"Profiles > ProfileName, where " +"ProfileName is the name of the physical server alert " +"that was previously created." +msgstr "" +"Haga clic en Perfiles de alertas > Perfiles de " +"alertas de servidor físico > ProfileName, " +"donde ProfileName es el nombre de alerta del servidor " +"físico que se creó anteriormente." + +msgid "" +"Click Configuration > Edit assignments for this " +"Alert Profile." +msgstr "" +"Haga clic en Configuración > Editar " +"asignaciones para este Perfil de alerta." + +msgid "" +"Choose Selected Servers from the " +"Assign To dropdown menu." +msgstr "" +"Elija Servidores seleccionados del menú " +"desplegable Asignar a." + +msgid "" +"Select the checkboxes next to the servers that you want to assign to the " +"profile from the Selections list." +msgstr "" +"Seleccione las casillas de verificación junto a los servidores que desea " +"asignar al perfil de la lista Selecciones." + +msgid "Step 3. Configure the alert associated with the alert profile" +msgstr "Paso 3. Configure la alerta asociada al perfil de alertas" + +msgid "" +"Click Alert Profiles > Physical Server Alert " +"Profiles > ProfileName > Physical server has " +"critical health state, where ProfileName is " +"the name of the physical server alert profile that was previously created." +msgstr "" +"Haga clic en Perfiles de alertas > Perfiles de " +"alertas de servidor físico > ProfileName, " +"donde ProfileName es el nombre del perfil de alerta del " +"servidor físico creado anteriormente." + +msgid "" +"Click Configuration > Edit this Alert from the top menu." +msgstr "" +"Haga clic en Configuración > Edite esta alerta del menú superior." + +msgid "" +"Select the Active checkbox to enable " +"the alert." +msgstr "" +"Seleccione la casilla de verificación Activa para activar la alerta." + +msgid "" +"Optionally, increase the notification frequency by selecting a new value " +"from the Notification Frequency " +"dropdown menu. The default frequency is one hour." +msgstr "" +"De manera opcional, puede aumentar la frecuencia de notificación " +"seleccionando un nuevo valor del menú desplegable Frecuencia de notificación. La frecuencia " +"predeterminada es de una hora." + +msgid "" +"Ensure that the Send an E-mail checkbox " +"is selected." +msgstr "" +"Asegúrese de que esté seleccionada la casilla de verificación Enviar correo electrónico." + +msgid "" +"Optionally, enter a value into the From " +"field. By default, the cfadmin@cfserver.com address is " +"used." +msgstr "" +"De manera opcional, ingrese un valor en el campo De. De manera predeterminada, se usa la dirección " +"cfadmin@cfserver.com." + +msgid "" +"Enter the email address that you want to retrieve the alert notification in " +"the Add field, and then click the " +"+ button. The email address is " +"displayed in the To field." +msgstr "" +"Ingrese la dirección de correo electrónico de la que desea recuperar la " +"notificación de alerta en el campo Agregar y, luego, haga clic en botón +. La dirección de correo electrónico aparecerá en el campo " +"Para." + +msgid "" +"The assigned servers are checked hourly, and a notification is sent through " +"email if the any of the assigned servers have a critical health state." +msgstr "" +"Los servidores asignados se verifican cada hora y se envía una notificación " +"por correo electrónico si alguno de los servidores asignados tiene estado " +"crítico." + +msgid "Creating a policy to power on servers that are powered off" +msgstr "Creación de una política para encender servidores que están apagados" + +msgid "" +"In CloudForms, there is a control policy for physical servers that " +"automatically powers a server back on when it is powered off." +msgstr "" +"En CloudForms, se cuenta con una política de control para servidores físicos " +"mediante la cual un servidor se vuelve a encender automáticamente al " +"apagarse." + +msgid "" +"To enable this policy, you must assign the physical infrastructure profile " +"to a server." +msgstr "" +"Para habilitar esta política, debe asignar un perfil de infraestructura " +"física a un servidor." + +msgid "" +"Click a server (to display the Physical Server Summary page), or select " +"multiple servers that you want to provision." +msgstr "" +"Haga clic en un servidor (para mostrar la página Resumen de servidor físico) " +"o seleccione múltiples servidores que desee aprovisionar." + +msgid "" +"Click Policy > Manage Policies from " +"the top menu. The Physical Server Policy Assignment page is displayed." +msgstr "" +"Haga clic en Política > Gestionar políticas del menú superior. Aparecerá la página Asignación de políticas al " +"servidor físico." + +msgid "" +"Select the Physical Infrastructure Profile checkbox." +msgstr "" +"Seleccione la casilla de verificación Perfil de " +"infraestructura física." + +msgid "The policy is now assigned to the server." +msgstr "Ahora, la política queda asignada al servidor." + +msgid "Updating physical server firmware using Ansible playbooks" +msgstr "" +"Actualizar el firmware del servidor físico mediante playbooks de Ansible" + +msgid "" +"In CloudForms, physical server firmware can be updated using an Ansible " +"playbook." +msgstr "" +"En CloudForms, el firmware del servidor físico se puede actualizar mediante " +"el playbook de Ansible." + +msgid "" +"Note: An Ansible Tower provider that points to an " +"Ansible Tower instance must be added to CloudForms. See the Adding " +"an Ansible Tower Provider section in the CloudForms " +"Managing Providers documentation." +msgstr "" +"Nota: Se debe agregar un proveedor de Ansible Tower que " +"indique una instancia de Ansible Tower a CloudForms. Consulte la sección " +"Agregar un proveedor de Ansible Tower en la " +"documentación Proveedores de administración de CloudForms." + +msgid "" +"Within Ansible Tower, create a job template for the config.yml playbook. Specify update_firmware as the job " +"tag and any extra variables that are required by the playbook. Ensure that " +"the option to prompt on launch is enabled. You can use this playbook to " +"upgrade firmware on a physical server. You can get this playbook from the " +"web at https://galaxy.ansible.com/lenovo/lxca-config." +msgstr "" +"Dentro de Ansible Tower, cree una plantilla de trabajo para el playbook " +"config.yml. Especifique update_firmware como la etiqueta de trabajo, además de toda variable adicional " +"requerida por el playbook. Asegúrese de que esté activada la opción para " +"solicitar un lanzamiento. Puede usar este playbook para actualizar el " +"firmware en un servidor físico. Puede obtener este playbook de la Web en " +"https://" +"galaxy.ansible.com/lenovo/lxca-config." + +msgid "" +"Follow the steps that are described in the Executing an Ansible " +"Tower Job Template from a Service Catalog section in the " +"CloudForms Managing Providers documentation. Use the " +"job template that you created in the previous step." +msgstr "" +"Siga estos pasos descritos en la sección Ejecutar una plantilla de " +"trabajo de Ansible Tower de un catálogo de servicio en la " +"documentación Proveedores de administración de CloudForms. Use esta plantilla de trabajo que creó en el paso anterior." + +msgid "Provisioning physical servers using Ansible playbooks" +msgstr "Proporcionar servidores físicos con playbooks de Ansible" + +msgid "" +"In CloudForms, XClarity Administrator configuration patterns can be used to " +"provision physical servers through the use of an Ansible playbook. " +"Configuration patterns act as templates for configuring logical storage, I/O " +"adapters, boot order, and other baseboard management controller and Unified " +"Extensible Firmware Interface (UEFI) settings." +msgstr "" +"En CloudForms, los patrones de configuración de XClarity Administrator se " +"pueden utilizar para suministrar servidores físicos mediante el uso de un " +"playbook de Ansible. Los patrones de configuración funcionan como plantillas " +"para configurar el almacenamiento lógico, los adaptadores de entrada y " +"salida, el orden de inicio y otras configuraciones del controlador de " +"administración del tablero y la interfaz de firmware extensible y unificada " +"(UEFI)." + +msgid "" +"Within Ansible Tower, create a job template for the config.yml playbook. Specify apply_configpatterns as the " +"job tag and any extra variables that are required by the playbook. Ensure " +"that the option to prompt on launch is enabled. You can use this playbook to " +"apply a configuration pattern to a physical server. You can get this " +"playbook from the web at https://galaxy.ansible.com/lenovo/lxca-config." +msgstr "" +"Dentro de Ansible Tower, cree una plantilla de trabajo para el playbook " +"config.yml. Especifique apply_configpatterns como la etiqueta de trabajo, además de toda variable adicional " +"requerida por el playbook. Asegúrese de que esté activada la opción para " +"solicitar un lanzamiento. Puede usar este playbook para aplicar un patrón de " +"configuración en un servidor físico. Puede obtener este playbook de la Web " +"en https:/" +"/galaxy.ansible.com/lenovo/lxca-config." diff --git a/physical_infra_provider_configuration/l10n/ja-JP/Author_Group.po b/physical_infra_provider_configuration/l10n/ja-JP/Author_Group.po index 9f18efd..b39a1bf 100644 --- a/physical_infra_provider_configuration/l10n/ja-JP/Author_Group.po +++ b/physical_infra_provider_configuration/l10n/ja-JP/Author_Group.po @@ -2,7 +2,7 @@ msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2018-02-26 09:57+1000\n" +"POT-Creation-Date: 2018-11-22 19:44+1000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -10,7 +10,7 @@ msgstr "" "Last-Translator: tkuroda \n" "Language-Team: Japanese\n" "Language: ja\n" -"X-Generator: Zanata 4.4.3\n" +"X-Generator: Zanata 4.6.2\n" "Plural-Forms: nplurals=1; plural=0\n" msgid "Red Hat CloudForms" diff --git a/physical_infra_provider_configuration/l10n/ja-JP/Revision_History.po b/physical_infra_provider_configuration/l10n/ja-JP/Revision_History.po index 43aa16c..f2d2712 100644 --- a/physical_infra_provider_configuration/l10n/ja-JP/Revision_History.po +++ b/physical_infra_provider_configuration/l10n/ja-JP/Revision_History.po @@ -2,7 +2,7 @@ msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2018-02-26 09:57+1000\n" +"POT-Creation-Date: 2018-11-22 19:44+1000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -10,7 +10,7 @@ msgstr "" "Last-Translator: tkuroda \n" "Language-Team: Japanese\n" "Language: ja\n" -"X-Generator: Zanata 4.4.3\n" +"X-Generator: Zanata 4.6.2\n" "Plural-Forms: nplurals=1; plural=0\n" msgid "Revision History" diff --git a/physical_infra_provider_configuration/l10n/ja-JP/main.po b/physical_infra_provider_configuration/l10n/ja-JP/main.po index bedf813..dab3204 100644 --- a/physical_infra_provider_configuration/l10n/ja-JP/main.po +++ b/physical_infra_provider_configuration/l10n/ja-JP/main.po @@ -2,19 +2,21 @@ msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2018-02-26 09:57+1000\n" +"POT-Creation-Date: 2018-11-22 19:44+1000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"PO-Revision-Date: 2018-02-26 12:23+0000\n" +"PO-Revision-Date: 2018-12-20 01:53+0000\n" "Last-Translator: tkuroda \n" "Language-Team: Japanese\n" "Language: ja\n" -"X-Generator: Zanata 4.4.3\n" +"X-Generator: Zanata 4.6.2\n" "Plural-Forms: nplurals=1; plural=0\n" -msgid "Configuring the Lenovo Physical Infrastructure Provider" -msgstr "Lenovo 物理インフラストラクチャープロバイダーの設定" +msgid "" +"Configuring the Lenovo Physical Infrastructure Provider for Red Hat " +"CloudForms" +msgstr "Red Hat CloudForms への Lenovo 物理インフラストラクチャープロバイダーの設定" msgid "" "Adding and configuring the Lenovo physical infrastructure provider in Red " @@ -69,25 +71,34 @@ msgid "Key features include:" msgstr "主要な機能を以下に示します。" msgid "" -"Seamlessly integrates with one or more Lenovo XClarity Administrator virtual " +"Seamlessly integrates with one or more XClarity Administrator virtual " "appliances, providing a summary view of the Lenovo infrastructure, " "relationship views of physical servers and virtual hosts, and configuration " -"of servers using Configuration Patterns" +"of servers using Configuration Patterns. In addition, there is a dashboard " +"view that displays the following:" msgstr "" -"1 つまたは複数の Lenovo XClarity Administrator 仮想アプライアンスとシームレスに統合して、Lenovo " -"インフラストラクチャーの概要ビュー、物理サーバーと仮想ホストのリレーションシップビュー、および構成パターンを使用したサーバーの設定機能を提供する" +"1 つまたは複数の XClarity Administrator 仮想アプライアンスとシームレスに統合して、Lenovo " +"インフラストラクチャーの概要ビュー、物理サーバーと仮想ホストのリレーションシップビュー、および構成パターンを使用したサーバーの設定機能を提供する。また、以下の項目を表示するダッシュボードビューを提供する" + +msgid "" +"The number of servers, switches, racks, and storage systems being mangaged" +msgstr "管理対象のサーバー、スイッチ、ラック、およびストレージシステムの数" + +msgid "" +"Widgets that display information about server health, availability, and " +"recently discovered servers" +msgstr "サーバーの健全性、可用性、および新たに検出されたサーバーに関する情報を表示するウィジェット" msgid "" "Provides a single interface to monitor Lenovo hardware that is managed by " -"multiple instances of Lenovo XClarity Administrator" +"multiple instances of XClarity Administrator" msgstr "" -"複数の Lenovo XClarity Administrator インスタンスによって管理される Lenovo " +"複数の XClarity Administrator インスタンスによって管理される Lenovo " "ハードウェアを監視するための、単一のインターフェースを提供する" msgid "" -"Automatically discovers hardware that is managed by Lenovo XClarity " -"Administrator" -msgstr "Lenovo XClarity Administrator によって管理されるハードウェアを自動的に検出する" +"Automatically discovers hardware that is managed by XClarity Administrator" +msgstr "XClarity Administrator によって管理されるハードウェアを自動的に検出する" msgid "Manage devices for use in on-premise cloud deployments" msgstr "オンプレミスのクラウドデプロイメント用にデバイスを管理する" @@ -112,125 +123,122 @@ msgstr "管理対象デバイスについて、現在のシステム設定 (BMC msgid "" "Simplifies system management through custom policies and automation that " -"respond to the health status of physical servers" -msgstr "カスタムポリシーおよび物理サーバーのヘルスステータスに応じた自動化を通じて、システム管理を簡素化する" - -msgid "Configuring Lenovo XClarity Administrator" -msgstr "Lenovo XClarity Administrator の設定" - -msgid "" -"Lenovo XClarity Administrator virtual appliances are connected to CloudForms " -"by adding physical-infrastructure providers. Physical-infrastructure " -"providers enable you to manage and interact with devices that are managed by " -"Lenovo XClarity Administrator. After the physical-infrastructure provider is " -"added, the servers that are managed by the Lenovo XClarity Administrator are " -"registered in CloudForms. Managed devices can be monitored, configured, and " -"updated using Lenovo XClarity Administrator. The physical-infrastructure " -"provider surfaces information about these managed devices and the Lenovo " -"XClarity Administrator instance." -msgstr "" -"物理インフラストラクチャープロバイダーを追加して、Lenovo XClarity Administrator 仮想アプライアンスを CloudForms " -"に接続します。物理インフラストラクチャープロバイダーにより、Lenovo XClarity Administrator " -"が管理するデバイスを管理し、それらを操作することができます。物理インフラストラクチャープロバイダーを追加すると、Lenovo XClarity " -"Administrator の管理するサーバーが CloudForms に登録されます。管理対象デバイスを、Lenovo XClarity " -"Administrator " -"を使用して監視、設定、および更新することができます。物理インフラストラクチャープロバイダーにより、これらの管理対象デバイスおよび Lenovo " -"XClarity Administrator インスタンスの情報を把握することができます。" - -msgid "Setting up Lenovo XClarity Administrator" -msgstr "Lenovo XClarity Administrator のセットアップ" - -msgid "" -"For information about downloading and setting up Lenovo XClarity " -"Administrator, see Installing and setting up " -"Lenovo XClarity Administrator in the Lenovo XClarity Administrator " -"online documentation." -msgstr "" -"Lenovo XClarity Administrator のダウンロードおよびセットアップの詳細については、Lenovo XClarity " -"Administrator オンラインドキュメントの「Lenovo XClarity " -"Administrator のインストールとセットアップ」を参照してください。" +"respond to the health status of hardware devices" +msgstr "ハードウェアデバイスのヘルスステータスに対応するカスタムポリシーおよび自動化を通じて、システム管理を簡素化する" + +msgid "Configuring XClarity Administrator" +msgstr "XClarity Administrator の設定" + +msgid "" +"XClarity Administrator virtual appliances are connected to CloudForms by " +"adding physical-infrastructure providers. Physical-infrastructure providers " +"enable you to manage and interact with devices that are managed by XClarity " +"Administrator. After the physical-infrastructure provider is added, the " +"devices that are managed by the XClarity Administrator are registered in " +"CloudForms. Managed devices can be monitored, configured, and updated using " +"XClarity Administrator. The physical-infrastructure provider surfaces " +"information about these managed devices and the XClarity Administrator " +"instance." +msgstr "" +"物理インフラストラクチャープロバイダーを追加して、XClarity Administrator 仮想アプライアンスを CloudForms " +"に接続します。物理インフラストラクチャープロバイダーにより、XClarity Administrator " +"が管理するデバイスを管理し、それらを操作することができます。物理インフラストラクチャープロバイダーを追加すると、XClarity " +"Administrator の管理するデバイスが CloudForms に登録されます。管理対象デバイスを、XClarity Administrator " +"を使用して監視、設定、および更新することができます。物理インフラストラクチャープロバイダーにより、これらの管理対象デバイスおよび XClarity " +"Administrator インスタンスの情報を把握することができます。" + +msgid "Setting up XClarity Administrator" +msgstr "XClarity Administrator のセットアップ" + +msgid "" +"For information about downloading and setting up XClarity Administrator, see " +"Installing and setting up Lenovo XClarity " +"Administrator in the XClarity Administrator online documentation." +msgstr "" +"XClarity Administrator のダウンロードおよびセットアップの詳細については、XClarity Administrator " +"オンラインドキュメントの「Lenovo XClarity Administrator " +"初回のインストールとセットアップ」を参照してください。" msgid "" "Note: You can use all available " -"features in Lenovo XClarity Administrator for free for up to 90 days. After " -"90 days, you can continue to use Lenovo XClarity Administrator to manage and " -"monitor your hardware for free; however, you must purchase a full-function-" -"enablement license to continue using Lenovo XClarity Administrator to " -"configure your hardware using Configuration Patterns and to deploy operating " -"systems. Lenovo XClarity Pro provides entitlement to service and support and " -"the full-function-enablement license for Lenovo XClarity Administrator. For " -"more information about purchasing Lenovo XClarity Pro, contact your Lenovo " -"representative or authorized business partner." -msgstr "" -"メモ: Lenovo XClarity Administrator " -"のすべての利用可能な機能は最長 90 日間は無料で使用できます。90 日が経過した後も、引き続きハードウェアの管理や監視に Lenovo " -"XClarity Administrator を無料で使用できます。ただし、Lenovo XClarity Administrator " +"features in XClarity Administrator for free for up to 90 days. After 90 " +"days, you can continue to use XClarity Administrator to manage and monitor " +"your hardware for free; however, you must purchase a full-function-" +"enablement license to continue using XClarity Administrator to configure " +"your hardware using Configuration Patterns and to deploy operating systems. " +"Lenovo XClarity Pro provides entitlement to service and support and the full-" +"function-enablement license for XClarity Administrator. For more information " +"about purchasing Lenovo XClarity Pro, contact your Lenovo representative or " +"authorized business partner." +msgstr "" +"メモ: XClarity Administrator " +"のすべての利用可能な機能は最長 90 日間は無料で使用できます。90 日が経過した後も、引き続きハードウェアの管理や監視に XClarity " +"Administrator を無料で使用できます。ただし、XClarity Administrator " "を使用して構成パターンを使用したハードウェアの構成とオペレーティングシステムのデプロイを継続するには、全機能有効化ライセンスを購入する必要があります。Lenovo " -"XClarity Pro には、Lenovo XClarity Administrator " +"XClarity Pro には、XClarity Administrator " "の全機能有効化ライセンスに加えて、サービスおよびサポートへのエンタイトルメントが含まれます。Lenovo XClarity Pro " "購入の詳細については、Lenovo 担当者または認定ビジネスパートナーにお問い合わせください。" -msgid "Discovering and managing hardware using Lenovo XClarity Administrator" -msgstr "Lenovo XClarity Administrator を使用したハードウェアの検出および管理" - -msgid "" -"Lenovo XClarity Administrator can discover manageable devices in your " -"environment by performing an SLP discovery for devices that are on the same " -"IP subnet as Lenovo XClarity Administrator. A specified IP address or range " -"of IP addresses also can be used, or information can be imported from a " -"spreadsheet, a process that is known as a bulk import. " -"Discovery options can be accessed by clicking Hardware > Discover and Manage New Devices from the " -"menu bar. Discovered devices can then be managed by Lenovo XClarity " -"Administrator. During the management process, you are asked for login " -"credentials for the management controller of the target servers and given " -"the option to create a recovery account for the servers. For more " -"information about discovering and managing devices, see the Lenovo XClarity Administrator online " +msgid "Discovering and managing hardware using XClarity Administrator" +msgstr "XClarity Administrator を使用したハードウェアの検出および管理" + +msgid "" +"XClarity Administrator can discover manageable devices in your environment " +"by performing an SLP discovery for devices that are on the same IP subnet as " +"XClarity Administrator. A specified IP address or range of IP addresses also " +"can be used, or information can be imported from a spreadsheet, a process " +"that is known as a bulk import. Discovery options can " +"be accessed by clicking Hardware > Discover and " +"Manage New Devices from the menu bar. Discovered devices can then " +"be managed by XClarity Administrator. During the management process, you are " +"asked for login credentials for the management controller of the target " +"servers and given the option to create a recovery account for the servers. " +"For more information about discovering and managing devices, see the XClarity Administrator online " "documentation." msgstr "" -"Lenovo XClarity Administrator は、同じ IP サブネット上にあるデバイスに対して SLP " +"XClarity Administrator は、同じ IP サブネット上にあるデバイスに対して SLP " "検出を実施し、環境内にある管理可能なデバイスを検出することができます。特定の IP アドレスまたは IP " "アドレスの範囲を指定することもできます。また、スプレッドシートから情報をインポートすることもできます " "(この手法は、バルクインポート と呼ばれます)。メニューバーで ハードウェア > 新しいデバイスの検出と管理 " -"の順にクリックして、検出オプションを利用することができます。検出されたデバイスは、Lenovo XClarity Administrator " +"の順にクリックして、検出オプションを利用することができます。検出されたデバイスは、XClarity Administrator " "で管理されるようになります。管理プロセス中、対象サーバーの管理コントローラーに対するログイン認証情報を求められます。また、必要に応じてサーバーのリカバリーアカウントを作成することができます。デバイス検出および管理の詳細については、「Lenovo XClarity Administrator " -"資料」を参照してください。" +"lenovo.lxca.doc%2Faug_product_page.html\">XClarity Administrator " +"オンラインドキュメント を参照してください。" msgid "Note:" msgstr "メモ:" msgid "" -"Ensure that the devices that you intend to manage are supported by Lenovo " -"XClarity Administrator. For information about supported devices, see Supported devices in the Lenovo " -"XClarity Administrator online documentation." +"Ensure that the devices that you intend to manage are supported by XClarity " +"Administrator. For information about supported devices, see Supported devices in the XClarity " +"Administrator online documentation." msgstr "" -"管理するデバイスは、Lenovo XClarity Administrator " -"によりサポートされている必要があります。サポートされるデバイスの詳細については、Lenovo XClarity Administrator " +"管理するデバイスは、XClarity Administrator " +"によりサポートされている必要があります。サポートされるデバイスの詳細については、XClarity Administrator " "オンラインドキュメントの「サポートされるデバイス」を参照してください。" msgid "" -"Ensure that firmware for all devices that you intend to manage using Lenovo " +"Ensure that firmware for all devices that you intend to manage using " "XClarity Administrator are at the required levels. For more information " "about supported firmware levels, see Supported firmware in the Lenovo XClarity Administrator " -"online documentation." +"1_3_1_2\">Supported firmware in the XClarity Administrator online " +"documentation." msgstr "" -"Lenovo XClarity Administrator " -"を使用して管理するデバイスのファームウェアは、すべて要求されるレベルでなければなりません。サポートされているファームウェアレベルの詳細については、Lenovo " -"XClarity Administrator オンラインドキュメントの「サポートされているファームウェア」を参照してください。" msgid "Managing physical-infrastructure providers" @@ -240,13 +248,13 @@ msgid "Adding a physical-infrastructure provider" msgstr "物理インフラストラクチャープロバイダーの追加" msgid "" -"Lenovo XClarity Administrator virtual appliances are connected to CloudForms " -"by adding physical-infrastructure providers. Physical-infrastructure " -"providers enable you to manage and interact with devices that are managed by " -"Lenovo XClarity Administrator." +"XClarity Administrator virtual appliances are connected to CloudForms by " +"adding physical-infrastructure providers. Physical-infrastructure providers " +"enable you to manage and interact with devices that are managed by XClarity " +"Administrator." msgstr "" -"物理インフラストラクチャープロバイダーを追加して、Lenovo XClarity Administrator 仮想アプライアンスを CloudForms " -"に接続します。物理インフラストラクチャープロバイダーにより、Lenovo XClarity Administrator " +"物理インフラストラクチャープロバイダーを追加して、XClarity Administrator 仮想アプライアンスを CloudForms " +"に接続します。物理インフラストラクチャープロバイダーにより、XClarity Administrator " "が管理するデバイスを管理し、それらを操作することができます。" msgid "" @@ -258,14 +266,13 @@ msgstr "" "CloudForms にログインしている必要があります。デフォルトのユーザーは admin で、パスワードは smartvm です。" msgid "" -"Complete the following steps for each Lenovo XClarity Administrator instance " -"that you want to connect to CloudForms." +"Complete the following steps for each XClarity Administrator instance that " +"you want to connect to CloudForms." msgstr "" -"CloudForms に接続するそれぞれの Lenovo XClarity Administrator " -"インスタンスについて、以下のステップを実施します。" +"CloudForms に接続するそれぞれの XClarity Administrator インスタンスについて、以下のステップを実施します。" -msgid "To connect to a specific Lenovo XClarity Administrator instance:" -msgstr "特定の Lenovo XClarity Administrator インスタンスに接続するには、以下の手順を実施します。" +msgid "To connect to a specific XClarity Administrator instance:" +msgstr "特定の XClarity Administrator インスタンスに接続するには、以下の手順を実施します。" msgid "" "Navigate to Compute > Physical Infrastructure " @@ -300,37 +307,34 @@ msgid "In the credentials area, provide the following:" msgstr "認証情報エリアで、以下の情報を指定します。" msgid "" -"Enter the hostname, IPv4 address, or IPv6 address of the Lenovo XClarity " +"Enter the hostname, IPv4 address, or IPv6 address of the XClarity " "Administrator instance." -msgstr "" -"Lenovo XClarity Administrator インスタンスのホスト名、IPv4 アドレス、または IPv6 アドレスを入力します。" +msgstr "XClarity Administrator インスタンスのホスト名、IPv4 アドレス、または IPv6 アドレスを入力します。" msgid "Enter “443” for the API port." msgstr "API ポート に「443」と入力します。" msgid "" -"Enter the username and password used to log in to the Lenovo XClarity " -"Administrator instance." -msgstr "Lenovo XClarity Administrator インスタンスにログインするためのユーザー名およびパスワードを入力します。" +"Enter the username and password used to log in to the XClarity Administrator " +"instance." +msgstr "XClarity Administrator インスタンスにログインするためのユーザー名およびパスワードを入力します。" msgid "" "Click Validate to confirm that you can " -"connect to the Lenovo XClarity Administrator instance." +"connect to the XClarity Administrator instance." msgstr "" -"検証 をクリックして、Lenovo XClarity " -"Administrator インスタンスに接続可能であることを確認します。" +"検証 をクリックして、XClarity Administrator " +"インスタンスに接続可能であることを確認します。" msgid "Click Add." msgstr "追加 をクリックします。" msgid "" -"To discover and then connect to a range of Lenovo XClarity Administrator " -"instances:" -msgstr "" -"さまざまな Lenovo XClarity Administrator インスタンスを検出し、それらに接続するには、以下の手順を実施します。\n" +"To discover and then connect to a range of XClarity Administrator instances:" +msgstr "さまざまな XClarity Administrator インスタンスを検出し、それらに接続するには、以下の手順を実施します。" -msgid "Discover Lenovo XClarity Administrator instances:" -msgstr "Lenovo XClarity Administrator インスタンスを検出します。" +msgid "Discover XClarity Administrator instances:" +msgstr "XClarity Administrator インスタンスを検出します。" msgid "" "Navigate to Compute > Physical Infrastructure " @@ -372,9 +376,9 @@ msgstr "開始 をクリックして検出 msgid "" "Update credentials for each discovered physical-infrastructure provider " -"(Lenovo XClarity Administrator instance):" +"(XClarity Administrator instance):" msgstr "" -"検出されたそれぞれの物理インフラストラクチャープロバイダー (Lenovo XClarity Administrator インスタンス) " +"検出されたそれぞれの物理インフラストラクチャープロバイダー (XClarity Administrator インスタンス) " "について、認証情報を更新します。" msgid "Select the providers to be edited." @@ -471,6 +475,52 @@ msgstr "修正する物理インフラストラクチャープロバイダーを msgid "Make the required changes, and revalidate credentials if necessary." msgstr "必要な変更を行い、必要に応じて認証情報を再検証します。" +msgid "" +"Changing the password of the XClarity Administrator instance through its " +"physical-infrastructure provider" +msgstr "物理インフラストラクチャープロバイダーからの XClarity Administrator インスタンスパスワードの変更" + +msgid "" +"Within CloudForms, you can change the password of an XClarity Administrator " +"instance through the physical-infrastructure provider with which it is " +"associated. Changing the password this way also changes the password in " +"CloudForms so that they match." +msgstr "" +"CloudForms では、XClarity Administrator " +"インスタンスが関連付けられている物理インフラストラクチャープロバイダーから、その XClarity Administrator " +"インスタンスのパスワードを変更することができます。このようにしてパスワードを変更すると CloudForms " +"側でもパスワードが変更され、両者の整合性が維持されます。" + +msgid "Click on the physical-infrastructure provider to be modified." +msgstr "修正する物理インフラストラクチャープロバイダーをクリックします。" + +msgid "" +"Click on the Authentication button in " +"the top menu and select Change password." +" The Change Password for Physical Infrastructure Provider page is displayed." +msgstr "" +"トップメニューで 認証 ボタンをクリックし、パスワードの変更 を選択します。物理インフラストラクチャープロバイダーのパスワードを変更する " +"ページが表示されます。" + +msgid "" +"Enter the current password for the XClarity Administrator instance in the " +"Current Password field." +msgstr "" +"現在のパスワード フィールドに XClarity Administrator " +"インスタンスの現在のパスワードを入力します。" + +msgid "" +"Enter the new password in the New Password and Confirm New Password " +"fields." +msgstr "" +"新規パスワード および 新しいパスワードを確認 フィールドに新しいパスワードを入力します。" + +msgid "Click Save." +msgstr "保存 をクリックします。" + msgid "Viewing relationships" msgstr "リレーションシップの表示" @@ -504,16 +554,20 @@ msgid "" "provider, complete the following steps." msgstr "特定の物理インフラストラクチャープロバイダーについてトポロジービューを表示するには、以下のステップを実施します。" -msgid "Select the physical-infrastructure provider to be viewed." -msgstr "表示する物理インフラストラクチャープロバイダーを選択します。" +msgid "Click on the physical-infrastructure provider to be viewed." +msgstr "表示する物理インフラストラクチャープロバイダーをクリックします。" + +msgid "Once the page loads, ensure that the summary view is being used." +msgstr "ページが読み込まれたら、概要ビューが使われていることを確認します。" msgid "" -"From the overview section, select Topology to display the Topology page. From this page, you can perform the " -"following actions:" +"Click on Topology in the Overview table to display the Topology page. From this " +"page, you can perform the following actions:" msgstr "" -"概要セクションから トポロジー " -"を選択し、トポロジーページを表示します。このページから、以下に示す操作を実施することができます。" +"概要 テーブルで トポロジー をクリックし、トポロジー " +"ページを表示します。このページから、以下に示す操作を実施することができます。" msgid "" "Hide or show all physical server by clicking 仮想マシン をクリックして、すべての仮想マシンを表示または非表示にする。" +msgid "" +"Hide or show nodes in the graph that have a particular health state by " +"clicking on one of the following states: Valid, Warning, Critical, or Unknown." +msgstr "" +"有効、警告、クリティカル、または 不明 " +"のいずれかのステータスをクリックして、選択したヘルスステータスのノードをグラフで表示または非表示にする。" + msgid "" "Double-click or right-click a node in the graph to navigate to the summary " "pages for that node." @@ -544,13 +610,30 @@ msgid "" "physical-infrastructure provider." msgstr "特定の物理インフラストラクチャープロバイダーによって管理される、全物理サーバーのリストを表示することができます。" +msgid "From the physical-infrastructure provider summary view" +msgstr "物理インフラストラクチャープロバイダーの概要ビューから" + +msgid "After the page loads, ensure that the summary view is being used." +msgstr "ページが読み込まれたら、概要ビューが使われていることを確認します。" + msgid "" -"Click Physical Servers in the Relationships section." +"Click on Physical Servers in the " +"Relationships table." msgstr "" -"リレーションシップ セクションで リレーションシップ テーブルで 物理サーバー をクリックします。" +msgid "From the physical-infrastructure provider dashboard view" +msgstr "物理インフラストラクチャープロバイダーのダッシュボードビューから" + +msgid "After the page loads, ensure that the dashboard view is being used." +msgstr "ページが読み込まれたら、ダッシュボードビューが使われていることを確認します。" + +msgid "" +"Click on the number of servers that is displayed displayed in the Servers card." +msgstr "サーバー カードに表示されるサーバー数をクリックします。" + msgid "Viewing virtual-host relationships" msgstr "仮想ホストのリレーションシップの表示" @@ -560,16 +643,16 @@ msgid "" msgstr "特定の物理インフラストラクチャープロバイダーによって管理されるホストに関連付けられた、物理サーバーのリストを表示することができます。" msgid "" -"Click Physical Servers with Host button " -"in the Relationships section." +"Click on Physical Servers with Host in " +"the Relationships table." msgstr "" -"リレーションシップ セクションで ホストに関連付けられた物理サーバー ボタンをクリックします。" +"リレーションシップ テーブルで ホストに関連付けられた物理サーバー をクリックします。" msgid "" -"You should see a list of physical servers that are associated with hosts as " +"A list of physical servers that are associated with hosts are displayed as " "shown below." -msgstr "以下に示すように、ホストに関連付けられた物理サーバーのリストが表示されるはずです。" +msgstr "以下に示すように、ホストに関連付けられた物理サーバーのリストが表示されます。" msgid "" " host relationships " +msgid "Viewing storage relationships" +msgstr "ストレージのリレーションシップの表示" + +msgid "" +"You can view a list of all storage systems that are managed by a specific " +"physical-infrastructure provider." +msgstr "特定の物理インフラストラクチャープロバイダーによって管理される、全ストレージシステムのリストを表示することができます。" + +msgid "" +"Click on Physical Storages in the " +"Relationships table." +msgstr "" +"リレーションシップ テーブルで 物理ストレージ をクリックします。" + +msgid "" +"Click on the number of storage systems that is displayed in the Storages card." +msgstr "ストレージ カードに表示されるストレージシステム数をクリックします。" + +msgid "Viewing switch relationships" +msgstr "スイッチのリレーションシップの表示" + +msgid "" +"You can view a list of all switches that are managed by a specific physical-" +"infrastructure provider." +msgstr "特定の物理インフラストラクチャープロバイダーによって管理される、全スイッチのリストを表示することができます。" + +msgid "" +"Click on Physical Switches in the " +"Relationships table." +msgstr "" +"リレーションシップ テーブルで 物理スイッチ をクリックします。" + +msgid "" +"Click on the number of switches that is displayed in the Switches card." +msgstr "スイッチ カードに表示されるスイッチ数をクリックします。" + +msgid "Viewing chassis relationships" +msgstr "シャーシのリレーションシップの表示" + +msgid "" +"You can view a list of chassis that are managed by a specific physical-" +"infrastructure provider." +msgstr "特定の物理インフラストラクチャープロバイダーによって管理される、シャーシのリストを表示することができます。" + +msgid "" +"Click on Physical Chassis in the " +"Relationships table." +msgstr "" +"リレーションシップ テーブルで 物理シャーシ をクリックします。" + +msgid "" +"Click on the number of chassis that is displayed in the Chassis card." +msgstr "シャーシ カードに表示されるシャーシ数をクリックします。" + +msgid "Viewing rack relationships" +msgstr "ラックのリレーションシップの表示" + +msgid "" +"You can view a list of all racks that are managed by a specific physical-" +"infrastructure provider." +msgstr "特定の物理インフラストラクチャープロバイダーによって管理される、全ラックのリストを表示することができます。" + +msgid "" +"Click on Physical Racks in the " +"Relationships table." +msgstr "" +"リレーションシップ テーブルで 物理ラック をクリックします。" + +msgid "" +"Click on the number of racks that is displayed in the Racks card." +msgstr "ラック カードに表示されるラック数をクリックします。" + msgid "Managing physical servers" msgstr "物理サーバーの管理" msgid "" "After the Lenovo physical-infrastructure provider is added, the servers that " -"are managed by Lenovo XClarity Administrator are registered in CloudForms. " -"You can then view and manage those servers." +"are managed by XClarity Administrator are registered in CloudForms. You can " +"then view and manage those servers." msgstr "" -"Lenovo 物理インフラストラクチャープロバイダーを追加すると、Lenovo XClarity Administrator の管理するサーバーが " +"Lenovo 物理インフラストラクチャープロバイダーを追加すると、XClarity Administrator の管理するサーバーが " "CloudForms に登録されます。これで、これらのサーバーを表示および管理することができるようになります。" +msgid "" +"Note: It may take a few seconds or so for the servers " +"to appear after adding a physical-infrasturcture provider." +msgstr "" +"メモ: " +"物理インフラストラクチャープロバイダーを追加してからサーバーが表示されるまでに、数秒程度かかる場合があります。" + msgid "Viewing a Physical Server" msgstr "物理サーバーの表示" @@ -787,25 +957,25 @@ msgid "Provisioning physical servers using configuration patterns" msgstr "構成パターンを使用した物理サーバーのプロビジョニング" msgid "" -"You can use configuration patterns in Lenovo XClarity Administrator to " -"quickly provision or preprovision multiple servers from a single set of " -"defined configuration settings. Configuration patterns act as templates for " +"You can use configuration patterns in XClarity Administrator to quickly " +"provision or preprovision multiple servers from a single set of defined " +"configuration settings. Configuration patterns act as templates for " "configuring logical storage, I/O adapters, boot order, and other baseboard " "management controller and Unified Extensible Firmware Interface (UEFI) " "settings." msgstr "" -"Lenovo XClarity Administrator " +"XClarity Administrator " "の構成パターンを使用すると、単一セットの定義済み構成設定から複数のサーバーを簡単にプロビジョニングまたは事前プロビジョニングすることができます。構成パターンは、論理ストレージ、I/" "O アダプター、ブート順序、ならびにその他のベースボード管理コントローラーおよび Unified Extensible Firmware " "Interface (UEFI) 設定を定義する際のテンプレートとして機能します。" msgid "" "A physical-infrastructure provider can discover configuration patterns that " -"are defined on the associated Lenovo XClarity Administrator instance. A " +"are defined on the associated XClarity Administrator instance. A " "configuration pattern can then be applied to a single or multiple physical " "servers." msgstr "" -"物理インフラストラクチャープロバイダーでは、関連する Lenovo XClarity Administrator " +"物理インフラストラクチャープロバイダーでは、関連する XClarity Administrator " "インスタンスで定義される構成パターンを検出することができます。その後、構成パターンを 1 つまたは複数の物理サーバーに適用することができます。" msgid "" @@ -893,22 +1063,399 @@ msgstr "" "をクリックして指定したサーバーに構成パターンをデプロイします。要求 " "テーブルで、アクションのステータスを確認することができます。" -msgid "Troubleshooting Physical Infrastructure Provider Problems" -msgstr "物理インフラストラクチャープロバイダーに関する問題のトラブルシューティング" +msgid "Viewing network devices that are associated with a physical server" +msgstr "物理サーバーに関連付けられたネットワークデバイスの表示" + +msgid "" +"From the Physical Server Summary page, you can access details about network " +"devices such as network interface cards." +msgstr "物理サーバーの概要ページから、ネットワークインターフェースカード等のネットワークデバイスの詳細を把握することができます。" + +msgid "" +"Access the Physical Servers page, as described in the section, and then select a physical server. " +"The Physical Server Summary page is displayed." +msgstr "" +"セクションに記載の手順に従って 物理サーバー " +"ページに移動し、続いて物理サーバーを選択します。物理サーバーの概要ページが表示されます。" + +msgid "" +"Click on the Network Devices count in " +"the Properties table. A list of network " +"devices is displayed." +msgstr "" +"プロパティー テーブルで ネットワークデバイス 数をクリックします。ネットワークデバイスのリストが表示されます。" + +msgid "" +"Select a network device from the list. The Network Device Summary page is " +"displayed." +msgstr "リストからネットワークデバイスを選択します。ネットワークデバイスの概要ページが表示されます。" + +msgid "" +" " +"network device summary " +msgstr "" +" " +"network device summary " + +msgid "Viewing storage devices that are associated with a physical server" +msgstr "物理サーバーに関連付けられたストレージデバイスの表示" + +msgid "" +"From the Physical Server Summary page, you can access details about storage " +"devices, such as RAID cards." +msgstr "物理サーバーの概要ページから、RAID カード等のストレージデバイスの詳細を把握することができます。" + +msgid "" +"Click on the Storage Devices count in " +"the Properties table. A list of storage " +"devices is displayed." +msgstr "" +"プロパティー テーブルで ストレージデバイス 数をクリックします。ストレージデバイスのリストが表示されます。" + +msgid "" +"Select a storage device from the list. The Storage Device Summary page is " +"displayed." +msgstr "リストからストレージデバイスを選択します。ストレージデバイスの概要ページが表示されます。" + +msgid "" +" " +"storage device summary " +msgstr "" +" " +"storage device summary " + +msgid "Adding physical server widgets to the dashboard" +msgstr "ダッシュボードへの物理サーバーウィジェットの追加" + +msgid "" +"You can add widgets that display information about physical servers to the " +"default dashboard." +msgstr "物理サーバーに関する情報が表示されるウィジェットを、デフォルトのダッシュボードに追加することができます。" + +msgid "" +"Navigate to Cloud Intel > Dashboard." +msgstr "" +"クラウドインテリジェンス > ダッシュボード の順に移動します。" + +msgid "" +"Click on the + button from the top " +"menu, and select one of the following widgets:" +msgstr "" +"トップメニューで + " +"ボタンをクリックし、以下のウィジェットのいずれかを選択します。" + +msgid "Physical Server Availability" +msgstr "Physical Server Availability" + +msgid "Physical Server Health" +msgstr "Physical Server Health" + +msgid "" +"Recently Discovered Physical Servers" +msgstr "" +"Recently Discovered Physical Servers" + +msgid "The widget is now displayed on the default dashboard." +msgstr "これでウィジェットがデフォルトのダッシュボードに表示されるようになります。" + +msgid "Creating a user that belongs to the physical infrastructure usergroup" +msgstr "物理インフラストラクチャーユーザーグループに属するユーザーの作成" + +msgid "" +"You can use the physical infrastructure usergroup to manage physical " +"infrastructures. Users that belong to this group have a default dashboard " +"that contains physical server widgets. The physical server widgets show " +"useful information, such as server health, availability, and recently " +"discovered servers." +msgstr "" +"物理インフラストラクチャーユーザーグループを使用して、物理インフラストラクチャーを管理することができます。このグループに属するユーザーのデフォルトダッシュボードには、物理サーバーウィジェットが含まれます。物理サーバーウィジェットには、サーバーの健全性、可用性、および新たに検出されたサーバー等の有用な情報が表示されます。" + +msgid "" +"To gain the benefits of this usergroup, you must create a new user that " +"belongs to the physical infrastructure group." +msgstr "このユーザーグループのメリットを得るには、物理インフラストラクチャーグループに属する新規ユーザーを作成する必要があります。" + +msgid "" +"Follow the steps described in the Creating a User " +"section in the CloudForms General Configuration " +"documentation. For the group, choose EvmGroup-" +"physical_infrastructure." +msgstr "" +"『CloudForms General Configuration』の「Creating " +"a User」セクションに記載の手順に従ってください。グループには EvmGroup-" +"physical_infrastructure を選択します。" + +msgid "" +"After the user is created, log in as the new user, and the default dashboard " +"containing physical server widgets is displayed." +msgstr "ユーザーの作成後に新規ユーザーとしてログインすると、物理サーバーウィジェットが含まれるデフォルトダッシュボードが表示されます。" + +msgid "Managing physical chassis" +msgstr "物理シャーシの管理" + +msgid "" +"After the Lenovo physical-infrastructure provider is added, the physical " +"chassis that are managed by XClarity Administrator are registered in " +"CloudForms. You can then view and manage the chassis." +msgstr "" +"Lenovo 物理インフラストラクチャープロバイダーを追加すると、XClarity Administrator の管理する物理シャーシが " +"CloudForms に登録されます。これで、シャーシを表示および管理することができるようになります。" + +msgid "Viewing physical chassis" +msgstr "物理シャーシの表示" + +msgid "" +"To view a list of all physical chassis that are managed by all physical-" +"infrastructure providers, navigate to Compute > " +"Physical Infrastructure > Chassis. The Physical Chassis page " +"is displayed (see the following figure)." +msgstr "" +"すべての物理インフラストラクチャープロバイダーによって管理される全物理シャーシのリストを表示するには、コンピュート > 物理インフラストラクチャー > シャーシ の順に移動します。物理シャーシ " +"ページが表示されます (下図を参照)。" + +msgid "" +"Tip: You can sort the table columns to " +"make it easier to find a specific chassis." +msgstr "" +"ヒント: 表の見出しを使って、特定のシャーシを簡単に探すことができます。" + +msgid "" +" " +"physical chassis " +msgstr "" +" " +"physical chassis " + +msgid "Locating a physical chassis" +msgstr "物理シャーシの場所の特定" + +msgid "" +"You can change the Location LED state on a physical chassis to locate a " +"chassis in the data center." +msgstr "物理シャーシのロケーション LED の状態を変更して、データセンター内でのシャーシの場所を特定することができます。" + +msgid "" +"Navigate to Compute > Physical Infrastructure " +"> Chassis." +msgstr "" +"コンピュート > 物理インフラストラクチャー > シャーシ " +"の順に移動します。" + +msgid "" +"Select the physical chassis. The Physical Chassis Summary page is displayed." +msgstr "物理シャーシを選択します。物理シャーシの概要ページが表示されます。" + +msgid "" +"Click on Identify in the top menu, and " +"then click on the appropriate action: Blink LED, Turn On LED, or Turn Off LED." +msgstr "" +"トップメニューで 識別 " +"をクリックし、続いて次の中から適切な操作をクリックします。LED の点滅、LED をオンにする、または LED をオフにする。" + +msgid "" +" physical chassis identify led " +msgstr "" +" physical chassis identify led " + +msgid "Managing physical racks" +msgstr "物理ラックの管理" + +msgid "" +"After the Lenovo physical-infrastructure provider is added, the physical " +"racks that are managed by XClarity Administrator are registered in " +"CloudForms. You can then view and manage the racks." +msgstr "" +"Lenovo 物理インフラストラクチャープロバイダーを追加すると、XClarity Administrator の管理する物理ラックが " +"CloudForms に登録されます。これで、ラックを表示および管理することができるようになります。" + +msgid "Viewing physical racks" +msgstr "物理ラックの表示" + +msgid "" +"To view a list of all physical racks that are managed by all physical-" +"infrastructure providers, navigate to Compute > " +"Physical Infrastructure > Racks. The Physical Racks page is " +"displayed (see the following figure)." +msgstr "" +"すべての物理インフラストラクチャープロバイダーによって管理される全物理ラックのリストを表示するには、コンピュート > 物理インフラストラクチャー > ラック の順に移動します。物理ラック " +"ページが表示されます (下図を参照)。" + +msgid "" +"Tip: You can sort the table columns to " +"make it easier to find a specific rack." +msgstr "" +"ヒント: 表の見出しを使って、特定のラックを簡単に探すことができます。" + +msgid "" +" " +"physical racks " +msgstr "" +" " +"physical racks " + +msgid "Managing physical storage systems" +msgstr "物理ストレージシステムの管理" + +msgid "" +"After the Lenovo physical-infrastructure provider is added, the physical " +"storage systems that are managed by XClarity Administrator are registered in " +"CloudForms. You can then view and manage the storage systems." +msgstr "" +"Lenovo 物理インフラストラクチャープロバイダーを追加すると、XClarity Administrator の管理する物理ストレージシステムが " +"CloudForms に登録されます。これで、ストレージシステムを表示および管理することができるようになります。" + +msgid "Viewing physical storage systems" +msgstr "物理ストレージシステムの表示" + +msgid "" +"To view a list of all physical storage systems that are managed by all " +"physical-infrastructure providers, navigate to Compute > Physical Infrastructure > Storages. " +"The Physical Storages page is displayed (see the following figure)." +msgstr "" +"すべての物理インフラストラクチャープロバイダーによって管理される全物理ストレージシステムのリストを表示するには、コンピュート > 物理インフラストラクチャー > ストレージ の順に移動します。物理ストレージ " +"ページが表示されます (下図を参照)。" + +msgid "" +"Tip: You can sort the table columns to " +"make it easier to find a specific storage system." +msgstr "" +"ヒント: " +"表の見出しを使って、特定のストレージシステムを簡単に探すことができます。" + +msgid "" +" " +"physical storage " +msgstr "" +" " +"physical storage " + +msgid "Managing physical switches" +msgstr "物理スイッチの管理" + +msgid "" +"After the Lenovo physical-infrastructure provider is added, the physical " +"switches that are managed by XClarity Administrator are registered in " +"CloudForms. You can then view and manage the switches." +msgstr "" +"Lenovo 物理インフラストラクチャープロバイダーを追加すると、XClarity Administrator の管理する物理スイッチが " +"CloudForms に登録されます。これで、スイッチを表示および管理することができるようになります。" + +msgid "Viewing physical switches" +msgstr "物理スイッチの表示" + +msgid "" +"To view a list of all physical switches that are managed by all physical-" +"infrastructure providers, navigate to Compute > " +"Physical Infrastructure > Switches. The Physical Switches page " +"is displayed (see the following figure)." +msgstr "" +"すべての物理インフラストラクチャープロバイダーによって管理される全物理スイッチのリストを表示するには、コンピュート > 物理インフラストラクチャー > スイッチ の順に移動します。物理スイッチ " +"ページが表示されます (下図を参照)。" + +msgid "" +"Tip: You can sort the table columns to " +"make it easier to find a specific switch." +msgstr "" +"ヒント: 表の見出しを使って、特定のスイッチを簡単に探すことができます。" + +msgid "" +" " +"physical switches " +msgstr "" +" " +"physical switches " + +msgid "Restarting physical switches" +msgstr "物理スイッチの再起動" + +msgid "" +"You can restart a physical switch that is managed by the physical-" +"infrastructure provider." +msgstr "物理インフラストラクチャープロバイダーの管理する物理スイッチを再起動することができます。" + +msgid "" +"Navigate to Compute > Physical Infrastructure " +"> Switches." +msgstr "" +"コンピュート > 物理インフラストラクチャー > スイッチ " +"の順に移動します。" + +msgid "" +"Select a physical switch. The Physical Switches Summary page is displayed." +msgstr "物理スイッチを選択します。物理スイッチの概要ページが表示されます。" + +msgid "" +"Click on Power in the top menu, and " +"then click on Restart." +msgstr "" +"トップメニューで 電源 をクリックし、続いて 再起動 をクリックします。" + +msgid "" +" " +"physical switch restart " +msgstr "" +" " +"physical switch restart " msgid "Automating tasks based on events" msgstr "イベントに応じたタスクの自動化" msgid "" "You can use CloudForms to automatically perform specific tasks when certain " -"events occur on servers that are managed by Lenovo XClarity Administrator " -"through a Lenovo physical-infrastructure provider. To create an automation " -"task, you must create and configure a custom domain. To automatically invoke " -"the task when a certain event occurs, you must create, configure and assign " -"a custom policy." -msgstr "" -"Lenovo XClarity Administrator によって管理されるサーバーに特定のイベントが生じた際に、CloudForms の " -"Lenovo " +"events occur on servers that are managed by XClarity Administrator through a " +"Lenovo physical-infrastructure provider. To create an automation task, you " +"must create and configure a custom domain. To automatically invoke the task " +"when a certain event occurs, you must create, configure and assign a custom " +"policy." +msgstr "" +"XClarity Administrator によって管理されるサーバーに特定のイベントが生じた際に、CloudForms の Lenovo " "物理インフラストラクチャープロバイダーを通じて、特定のタスクを自動的に実行することができます。自動化タスクを作成するには、カスタムドメインを作成して設定する必要があります。特定のイベントが生じた際にタスクを自動的に呼び出すには、カスタムポリシーを作成、設定、および割り当てる必要があります。" msgid "" @@ -918,7 +1465,7 @@ msgid "" "Actions in CloudForms website." msgstr "" "CloudForms の自動化機能の詳細については、『Scripting Actions in CloudForms』を参照してください。" @@ -1097,13 +1644,14 @@ msgid "" "CloudForms matches the class instance with the event by this name. To find " "the event name, see Messages in the " -"Lenovo XClarity Administrator online documentation." +"XClarity Administrator online documentation." msgstr "" "重要: " "クラスインスタンス名は、呼び出されるタスクのトリガーとなるイベント名と一致している必要があります。CloudForms " -"では、この名前を使ってクラスインスタンスとイベントを照合します。イベント名を知るには、Lenovo XClarity Administrator " +"では、この名前を使ってクラスインスタンスとイベントを照合します。イベント名を知るには、XClarity Administrator " "オンラインドキュメントの「メッセージ」を参照してください。" +"lenovo.lxca.doc/messages.html?cp=1_22_16\">「イベントとアラートのメッセージ」を参照してください。" msgid "" "Add the path to the event handlers copied in the field’s には、以下のパスを使用します。" msgid "" -"/System/event_handlers/event_action_policy? target=" -"physical_server&policy_event=physical_server_shutdown&param=\n" -"The policy_event value is matched with the policy operation applied." +"/System/event_handlers/event_action_policy?target=" +"physical_server&policy_event=physical_server_shutdown&param=" msgstr "" -"/System/event_handlers/event_action_policy? target=" -"physical_server&policy_event=physical_server_shutdown&param=\n" -"policy_event の値は、適用されるポリシー操作と一致します。" +"/System/event_handlers/event_action_policy?target=" +"physical_server&policy_event=physical_server_shutdown&param=" + +msgid "The policy_event value is matched with the policy operation applied." +msgstr "policy_event の値は、適用されるポリシー操作と一致します。" msgid "Step 3. Create a namespace." msgstr "ステップ 3: 名前空間を作成する" @@ -1214,13 +1763,15 @@ msgid "" msgstr "データ フィールドに以下のスクリプトを入力します。" msgid "" -"server = $evm.vmdb('PhysicalServer').first $evm.log(:info, \"Powering Server " -"#{server.name} OFF\")\n" -"server.power_off exit MIQ_OK" +"server = $evm.vmdb('PhysicalServer').first\n" +"$evm.log(:info, \"Powering Server #{server.name} OFF\")\n" +"server.power_off\n" +"exit MIQ_OK" msgstr "" -"server = $evm.vmdb('PhysicalServer').first $evm.log(:info, \"Powering Server " -"#{server.name} OFF\")\n" -"server.power_off exit MIQ_OK" +"server = $evm.vmdb('PhysicalServer').first\n" +"$evm.log(:info, \"Powering Server #{server.name} OFF\")\n" +"server.power_off\n" +"exit MIQ_OK" msgid "" "Click Validate to verify the syntax." @@ -1247,7 +1798,7 @@ msgstr "＋アイコンをクリックしてスキーマにフィールドを追 msgid "Enter “execute” for the name." msgstr "名前 に「execute」と入力します。" -msgid "Select “Method” for the type" +msgid "Select “Method” for the type." msgstr "タイプ に「Method」を選択します。" msgid "Select “String” for the data type." @@ -1261,9 +1812,6 @@ msgstr "デフォルト値 に「Power_actions」Save." -msgstr "保存 をクリックします。" - msgid "Add the method to the class." msgstr "クラスにメソッドを追加します。" @@ -1473,3 +2021,276 @@ msgstr "" "images/provider_assign_profile.png\" /> " "provider assign profile " + +msgid "Creating an alert to monitor physical server health" +msgstr "物理サーバーの健全性を監視するためのアラートの作成" + +msgid "" +"Note: For this alert to work correctly, you must first " +"configure the SMTP settings in CloudForms by following instructions in the " +"Outgoing SMTP Email Settings section in the " +"CloudForms Configuration documentation." +msgstr "" +"メモ: このアラートが正しく機能するためには、まず CloudForms で SMTP " +"の設定を行う必要があります。『CloudForms General Configuration』の「Outgoing SMTP Email Settings」セクションに記載の手順に従ってください。" + +msgid "" +"In CloudForms, there is a configurable alert for physical servers that sends " +"an alert email when a server that is assigned to the alert is in an " +"unhealthy state. This alert can be used to notify IT administrators that a " +"server is in an unhealthy state, so that they can investigate and resolve " +"potential issues before the issues lead to downtime." +msgstr "" +"CloudForms " +"には、物理サーバーに関する設定可能なアラートが用意されています。アラートに割り当てられたサーバーのヘルスステータスが正常ではない場合に、警告メールが送信されます。このアラートを使用して、サーバーのヘルスステータスが正常ではないことを " +"IT 管理者に通知することができます。これにより、管理者は問題を調査し、ダウンタイムが発生する前にその問題を解決することができます。" + +msgid "" +"To enable this alert, you must create a physical server alert profile, " +"assign servers to the profile, and then configure the alert that is " +"associated with the profile." +msgstr "" +"このアラートを有効にするには、物理サーバーのアラートプロファイルを作成し、サーバーをそのプロファイルに割り当て、プロファイルに関連付けられるアラートを設定する必要があります。" + +msgid "Step 1. Create a physical server alert profile" +msgstr "ステップ 1: 物理サーバーのアラートプロファイルの作成" + +msgid "" +"Click Alert Profiles > Physical Server Alert " +"Profiles." +msgstr "" +"アラートプロファイル > 物理サーバーのアラートプロファイル " +"の順にクリックします。" + +msgid "" +"Click Configuration > Add a New Physical Server " +"Alert Profile from the top menu." +msgstr "" +"トップメニューで 構成 > 新規物理サーバーのアラートプロファイルの追加 " +"の順にクリックします。" + +msgid "" +"Enter a description into the Description field." +msgstr "説明 フィールドに説明を入力します。" + +msgid "" +"Select Physical server has critical health state from the Available Physical Server " +"Alerts list, and click on the > button to add it to the Profile Alerts list on the right." +msgstr "" +"利用可能な物理サーバーのアラート リストから Physical server has critical health state " +"を選択し、> ボタンをクリックして右側の プロファイルアラート リストに追加します。" + +msgid "Step 2. Assign servers to the alert profile" +msgstr "ステップ 2: アラートプロファイルへのサーバーの割り当て" + +msgid "" +"Click Alert Profiles > Physical Server Alert " +"Profiles > ProfileName, where " +"ProfileName is the name of the physical server alert " +"that was previously created." +msgstr "" +"アラートプロファイル > 物理サーバーのアラートプロファイル > " +"プロファイル名 の順にクリックします。ここで、プロファイル名 は前のステップで作成した物理サーバーアラートプロファイルの名前です。" + +msgid "" +"Click Configuration > Edit assignments for this " +"Alert Profile." +msgstr "" +"構成 > このアラートプロファイルの割り当ての編集 " +"の順にクリックします。" + +msgid "" +"Choose Selected Servers from the " +"Assign To dropdown menu." +msgstr "" +"割り当て先 ドロップダウンメニューから 選択したサーバー を選択します。" + +msgid "" +"Select the checkboxes next to the servers that you want to assign to the " +"profile from the Selections list." +msgstr "" +"選択 " +"リストで、プロファイルに割り当てるサーバーの横にあるチェックボックスを選択します。" + +msgid "Step 3. Configure the alert associated with the alert profile" +msgstr "ステップ 3: アラートプロファイルに関連付けられるアラートの設定" + +msgid "" +"Click Alert Profiles > Physical Server Alert " +"Profiles > ProfileName > Physical server has " +"critical health state, where ProfileName is " +"the name of the physical server alert profile that was previously created." +msgstr "" +"アラートプロファイル > 物理サーバーのアラートプロファイル > " +"プロファイル名 > Physical server has critical health state の順にクリックします。ここで、プロファイル名 " +"は前のステップで作成した物理サーバーアラートプロファイルの名前です。" + +msgid "" +"Click Configuration > Edit this Alert from the top menu." +msgstr "" +"トップメニューで 構成 > このアラートの編集 の順にクリックします。" + +msgid "" +"Select the Active checkbox to enable " +"the alert." +msgstr "アクティブ チェックボックスを選択してアラートを有効にします。" + +msgid "" +"Optionally, increase the notification frequency by selecting a new value " +"from the Notification Frequency " +"dropdown menu. The default frequency is one hour." +msgstr "" +"オプションとして、通知頻度 " +"ドロップダウンメニューから新しい値を選択して通知の頻度を下げます。デフォルトの頻度は 1 時間です。" + +msgid "" +"Ensure that the Send an E-mail checkbox " +"is selected." +msgstr "メールの送信 チェックボックスが選択されていることを確認します。" + +msgid "" +"Optionally, enter a value into the From " +"field. By default, the cfadmin@cfserver.com address is " +"used." +msgstr "" +"オプションとして、送信元 " +"フィールドに値を入力します。デフォルトでは、アドレスに cfadmin@cfserver.com " +"が使用されます。" + +msgid "" +"Enter the email address that you want to retrieve the alert notification in " +"the Add field, and then click the " +"+ button. The email address is " +"displayed in the To field." +msgstr "" +"追加 (手動入力) " +"フィールドにアラート通知を受け取るメールアドレスを入力し、続いて + " +"ボタンをクリックします。メールアドレスが 宛先 フィールドに表示されます。" + +msgid "" +"The assigned servers are checked hourly, and a notification is sent through " +"email if the any of the assigned servers have a critical health state." +msgstr "" +"割り当てられたサーバーが 1 " +"時間ごとに確認され、割り当てられたサーバーのいずれかのヘルスステータスがクリティカルである場合に、通知メールが送信されます。" + +msgid "Creating a policy to power on servers that are powered off" +msgstr "電源オフのサーバーの電源をオンにするポリシーの作成" + +msgid "" +"In CloudForms, there is a control policy for physical servers that " +"automatically powers a server back on when it is powered off." +msgstr "CloudForms には、電源オフの物理サーバーの電源を自動的にオンに戻すコントロールポリシーが用意されています。" + +msgid "" +"To enable this policy, you must assign the physical infrastructure profile " +"to a server." +msgstr "このポリシーを有効にするには、物理インフラストラクチャーのプロファイルをサーバーに割り当てる必要があります。" + +msgid "" +"Click a server (to display the Physical Server Summary page), or select " +"multiple servers that you want to provision." +msgstr "プロビジョニングするサーバーをクリックするか (物理サーバーの概要ページが表示されます)、複数のサーバーを選択します。" + +msgid "" +"Click Policy > Manage Policies from " +"the top menu. The Physical Server Policy Assignment page is displayed." +msgstr "" +"トップメニューで ポリシー > ポリシーの管理 " +"の順にクリックします。物理サーバーポリシーの割り当て ページが表示されます。" + +msgid "" +"Select the Physical Infrastructure Profile checkbox." +msgstr "" +"Physical Infrastructure Profile " +"チェックボックスを選択します。" + +msgid "The policy is now assigned to the server." +msgstr "これでポリシーがサーバーに割り当てられました。" + +msgid "Updating physical server firmware using Ansible playbooks" +msgstr "Ansible Playbook を使用した物理サーバーファームウェアの更新" + +msgid "" +"In CloudForms, physical server firmware can be updated using an Ansible " +"playbook." +msgstr "CloudForms では、Ansible Playbook を使用して物理サーバーのファームウェアを更新することができます。" + +msgid "" +"Note: An Ansible Tower provider that points to an " +"Ansible Tower instance must be added to CloudForms. See the Adding " +"an Ansible Tower Provider section in the CloudForms " +"Managing Providers documentation." +msgstr "" +"メモ: Ansible Tower インスタンスをポイントする Ansible Tower プロバイダーを " +"CloudForms に追加する必要があります。『CloudForms Managing Providers』の「Adding an Ansible Tower Provider」セクションを参照してください。" + +msgid "" +"Within Ansible Tower, create a job template for the config.yml playbook. Specify update_firmware as the job " +"tag and any extra variables that are required by the playbook. Ensure that " +"the option to prompt on launch is enabled. You can use this playbook to " +"upgrade firmware on a physical server. You can get this playbook from the " +"web at https://galaxy.ansible.com/lenovo/lxca-config." +msgstr "" +"Ansible Tower 内で config.yml Playbook " +"用のジョブテンプレートを作成します。ジョブタグに update_firmware を指定し、Playbook " +"に必要なその他の変数も指定します。起動時に確認するオプションを必ず有効にしてください。この Playbook " +"を使用して、物理サーバーのファームウェアをアップグレードすることができます。この Playbook は、Web サイト から入手することができます。" + +msgid "" +"Follow the steps that are described in the Executing an Ansible " +"Tower Job Template from a Service Catalog section in the " +"CloudForms Managing Providers documentation. Use the " +"job template that you created in the previous step." +msgstr "" +"『CloudForms Managing Providers』の「Executing an " +"Ansible Tower Job or Workflow Template from a Service Catalog」セクションに記載の手順に従ってください。前のステップで作成したジョブテンプレートを使用します。" + +msgid "Provisioning physical servers using Ansible playbooks" +msgstr "Ansible Playbook を使用した物理サーバーのプロビジョニング" + +msgid "" +"In CloudForms, XClarity Administrator configuration patterns can be used to " +"provision physical servers through the use of an Ansible playbook. " +"Configuration patterns act as templates for configuring logical storage, I/O " +"adapters, boot order, and other baseboard management controller and Unified " +"Extensible Firmware Interface (UEFI) settings." +msgstr "" +"CloudForms では、Ansible Playbook を使用して、XClarity Administrator " +"の構成パターンを用いた物理サーバーのプロビジョニングを行うことができます。構成パターンは、論理ストレージ、I/O " +"アダプター、ブート順序、ならびにその他のベースボード管理コントローラーおよび Unified Extensible Firmware Interface " +"(UEFI) 設定を定義する際のテンプレートとして機能します。" + +msgid "" +"Within Ansible Tower, create a job template for the config.yml playbook. Specify apply_configpatterns as the " +"job tag and any extra variables that are required by the playbook. Ensure " +"that the option to prompt on launch is enabled. You can use this playbook to " +"apply a configuration pattern to a physical server. You can get this " +"playbook from the web at https://galaxy.ansible.com/lenovo/lxca-config." +msgstr "" +"Ansible Tower 内で config.yml Playbook " +"用のジョブテンプレートを作成します。ジョブタグに apply_configpatterns " +"を指定し、Playbook に必要なその他の変数も指定します。起動時に確認するオプションを必ず有効にしてください。この Playbook " +"を使用して、物理サーバーに構成パターンを適用することができます。この Playbook は、Web サイト から入手することができます。" diff --git a/physical_infra_provider_configuration/l10n/pot/Author_Group.pot b/physical_infra_provider_configuration/l10n/pot/Author_Group.pot index 84ae91d..68c7efe 100644 --- a/physical_infra_provider_configuration/l10n/pot/Author_Group.pot +++ b/physical_infra_provider_configuration/l10n/pot/Author_Group.pot @@ -1,8 +1,8 @@ msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2018-02-26 09:57+1000\n" -"PO-Revision-Date: 2018-02-26 09:57+1000\n" +"POT-Creation-Date: 2018-11-22 19:44+1000\n" +"PO-Revision-Date: 2018-11-22 19:44+1000\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "Language: en-US \n" diff --git a/physical_infra_provider_configuration/l10n/pot/Revision_History.pot b/physical_infra_provider_configuration/l10n/pot/Revision_History.pot index 3647b33..24505b6 100644 --- a/physical_infra_provider_configuration/l10n/pot/Revision_History.pot +++ b/physical_infra_provider_configuration/l10n/pot/Revision_History.pot @@ -1,8 +1,8 @@ msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2018-02-26 09:57+1000\n" -"PO-Revision-Date: 2018-02-26 09:57+1000\n" +"POT-Creation-Date: 2018-11-22 19:44+1000\n" +"PO-Revision-Date: 2018-11-22 19:44+1000\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "Language: en-US \n" diff --git a/physical_infra_provider_configuration/l10n/pot/master.pot b/physical_infra_provider_configuration/l10n/pot/main.pot similarity index 50% rename from physical_infra_provider_configuration/l10n/pot/master.pot rename to physical_infra_provider_configuration/l10n/pot/main.pot index fff140a..f808338 100644 --- a/physical_infra_provider_configuration/l10n/pot/master.pot +++ b/physical_infra_provider_configuration/l10n/pot/main.pot @@ -1,8 +1,8 @@ msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2018-02-26 09:57+1000\n" -"PO-Revision-Date: 2018-02-26 09:57+1000\n" +"POT-Creation-Date: 2018-11-22 19:44+1000\n" +"PO-Revision-Date: 2018-11-22 19:44+1000\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "Language: en-US \n" @@ -11,7 +11,7 @@ msgstr "" "Content-Transfer-Encoding: 8bit\n" "X-Generator: Publican v4.3.3\n" -msgid "Configuring the Lenovo Physical Infrastructure Provider" +msgid "Configuring the Lenovo Physical Infrastructure Provider for Red Hat CloudForms" msgstr "" msgid "Adding and configuring the Lenovo physical infrastructure provider in Red Hat CloudForms" @@ -35,13 +35,19 @@ msgstr "" msgid "Key features include:" msgstr "" -msgid "Seamlessly integrates with one or more Lenovo XClarity Administrator virtual appliances, providing a summary view of the Lenovo infrastructure, relationship views of physical servers and virtual hosts, and configuration of servers using Configuration Patterns" +msgid "Seamlessly integrates with one or more XClarity Administrator virtual appliances, providing a summary view of the Lenovo infrastructure, relationship views of physical servers and virtual hosts, and configuration of servers using Configuration Patterns. In addition, there is a dashboard view that displays the following:" msgstr "" -msgid "Provides a single interface to monitor Lenovo hardware that is managed by multiple instances of Lenovo XClarity Administrator" +msgid "The number of servers, switches, racks, and storage systems being mangaged" msgstr "" -msgid "Automatically discovers hardware that is managed by Lenovo XClarity Administrator" +msgid "Widgets that display information about server health, availability, and recently discovered servers" +msgstr "" + +msgid "Provides a single interface to monitor Lenovo hardware that is managed by multiple instances of XClarity Administrator" +msgstr "" + +msgid "Automatically discovers hardware that is managed by XClarity Administrator" msgstr "" msgid "Manage devices for use in on-premise cloud deployments" @@ -59,37 +65,37 @@ msgstr "" msgid "Manages current system settings (such as BMC, uEFI, and boot order settings) on the managed devices" msgstr "" -msgid "Simplifies system management through custom policies and automation that respond to the health status of physical servers" +msgid "Simplifies system management through custom policies and automation that respond to the health status of hardware devices" msgstr "" -msgid "Configuring Lenovo XClarity Administrator" +msgid "Configuring XClarity Administrator" msgstr "" -msgid "Lenovo XClarity Administrator virtual appliances are connected to CloudForms by adding physical-infrastructure providers. Physical-infrastructure providers enable you to manage and interact with devices that are managed by Lenovo XClarity Administrator. After the physical-infrastructure provider is added, the servers that are managed by the Lenovo XClarity Administrator are registered in CloudForms. Managed devices can be monitored, configured, and updated using Lenovo XClarity Administrator. The physical-infrastructure provider surfaces information about these managed devices and the Lenovo XClarity Administrator instance." +msgid "XClarity Administrator virtual appliances are connected to CloudForms by adding physical-infrastructure providers. Physical-infrastructure providers enable you to manage and interact with devices that are managed by XClarity Administrator. After the physical-infrastructure provider is added, the devices that are managed by the XClarity Administrator are registered in CloudForms. Managed devices can be monitored, configured, and updated using XClarity Administrator. The physical-infrastructure provider surfaces information about these managed devices and the XClarity Administrator instance." msgstr "" -msgid "Setting up Lenovo XClarity Administrator" +msgid "Setting up XClarity Administrator" msgstr "" -msgid "For information about downloading and setting up Lenovo XClarity Administrator, see Installing and setting up Lenovo XClarity Administrator in the Lenovo XClarity Administrator online documentation." +msgid "For information about downloading and setting up XClarity Administrator, see Installing and setting up Lenovo XClarity Administrator in the XClarity Administrator online documentation." msgstr "" -msgid "Note: You can use all available features in Lenovo XClarity Administrator for free for up to 90 days. After 90 days, you can continue to use Lenovo XClarity Administrator to manage and monitor your hardware for free; however, you must purchase a full-function-enablement license to continue using Lenovo XClarity Administrator to configure your hardware using Configuration Patterns and to deploy operating systems. Lenovo XClarity Pro provides entitlement to service and support and the full-function-enablement license for Lenovo XClarity Administrator. For more information about purchasing Lenovo XClarity Pro, contact your Lenovo representative or authorized business partner." +msgid "Note: You can use all available features in XClarity Administrator for free for up to 90 days. After 90 days, you can continue to use XClarity Administrator to manage and monitor your hardware for free; however, you must purchase a full-function-enablement license to continue using XClarity Administrator to configure your hardware using Configuration Patterns and to deploy operating systems. Lenovo XClarity Pro provides entitlement to service and support and the full-function-enablement license for XClarity Administrator. For more information about purchasing Lenovo XClarity Pro, contact your Lenovo representative or authorized business partner." msgstr "" -msgid "Discovering and managing hardware using Lenovo XClarity Administrator" +msgid "Discovering and managing hardware using XClarity Administrator" msgstr "" -msgid "Lenovo XClarity Administrator can discover manageable devices in your environment by performing an SLP discovery for devices that are on the same IP subnet as Lenovo XClarity Administrator. A specified IP address or range of IP addresses also can be used, or information can be imported from a spreadsheet, a process that is known as a bulk import. Discovery options can be accessed by clicking Hardware > Discover and Manage New Devices from the menu bar. Discovered devices can then be managed by Lenovo XClarity Administrator. During the management process, you are asked for login credentials for the management controller of the target servers and given the option to create a recovery account for the servers. For more information about discovering and managing devices, see the Lenovo XClarity Administrator online documentation." +msgid "XClarity Administrator can discover manageable devices in your environment by performing an SLP discovery for devices that are on the same IP subnet as XClarity Administrator. A specified IP address or range of IP addresses also can be used, or information can be imported from a spreadsheet, a process that is known as a bulk import. Discovery options can be accessed by clicking Hardware > Discover and Manage New Devices from the menu bar. Discovered devices can then be managed by XClarity Administrator. During the management process, you are asked for login credentials for the management controller of the target servers and given the option to create a recovery account for the servers. For more information about discovering and managing devices, see the XClarity Administrator online documentation." msgstr "" msgid "Note:" msgstr "" -msgid "Ensure that the devices that you intend to manage are supported by Lenovo XClarity Administrator. For information about supported devices, see Supported devices in the Lenovo XClarity Administrator online documentation." +msgid "Ensure that the devices that you intend to manage are supported by XClarity Administrator. For information about supported devices, see Supported devices in the XClarity Administrator online documentation." msgstr "" -msgid "Ensure that firmware for all devices that you intend to manage using Lenovo XClarity Administrator are at the required levels. For more information about supported firmware levels, see Supported firmware in the Lenovo XClarity Administrator online documentation." +msgid "Ensure that firmware for all devices that you intend to manage using XClarity Administrator are at the required levels. For more information about supported firmware levels, see Supported firmware in the XClarity Administrator online documentation." msgstr "" msgid "Managing physical-infrastructure providers" @@ -98,16 +104,16 @@ msgstr "" msgid "Adding a physical-infrastructure provider" msgstr "" -msgid "Lenovo XClarity Administrator virtual appliances are connected to CloudForms by adding physical-infrastructure providers. Physical-infrastructure providers enable you to manage and interact with devices that are managed by Lenovo XClarity Administrator." +msgid "XClarity Administrator virtual appliances are connected to CloudForms by adding physical-infrastructure providers. Physical-infrastructure providers enable you to manage and interact with devices that are managed by XClarity Administrator." msgstr "" msgid "Note: You must be logged in to CloudForms as a user with permission to add providers. The default user is admin, password smartvm." msgstr "" -msgid "Complete the following steps for each Lenovo XClarity Administrator instance that you want to connect to CloudForms." +msgid "Complete the following steps for each XClarity Administrator instance that you want to connect to CloudForms." msgstr "" -msgid "To connect to a specific Lenovo XClarity Administrator instance:" +msgid "To connect to a specific XClarity Administrator instance:" msgstr "" msgid "Navigate to Compute > Physical Infrastructure > Providers." @@ -128,25 +134,25 @@ msgstr "" msgid "In the credentials area, provide the following:" msgstr "" -msgid "Enter the hostname, IPv4 address, or IPv6 address of the Lenovo XClarity Administrator instance." +msgid "Enter the hostname, IPv4 address, or IPv6 address of the XClarity Administrator instance." msgstr "" msgid "Enter “443” for the API port." msgstr "" -msgid "Enter the username and password used to log in to the Lenovo XClarity Administrator instance." +msgid "Enter the username and password used to log in to the XClarity Administrator instance." msgstr "" -msgid "Click Validate to confirm that you can connect to the Lenovo XClarity Administrator instance." +msgid "Click Validate to confirm that you can connect to the XClarity Administrator instance." msgstr "" msgid "Click Add." msgstr "" -msgid "To discover and then connect to a range of Lenovo XClarity Administrator instances:" +msgid "To discover and then connect to a range of XClarity Administrator instances:" msgstr "" -msgid "Discover Lenovo XClarity Administrator instances:" +msgid "Discover XClarity Administrator instances:" msgstr "" msgid "Navigate to Compute > Physical Infrastructure > Providers." @@ -167,7 +173,7 @@ msgstr "" msgid "Click Start to begin the discovery process." msgstr "" -msgid "Update credentials for each discovered physical-infrastructure provider (Lenovo XClarity Administrator instance):" +msgid "Update credentials for each discovered physical-infrastructure provider (XClarity Administrator instance):" msgstr "" msgid "Select the providers to be edited." @@ -227,6 +233,27 @@ msgstr "" msgid "Make the required changes, and revalidate credentials if necessary." msgstr "" +msgid "Changing the password of the XClarity Administrator instance through its physical-infrastructure provider" +msgstr "" + +msgid "Within CloudForms, you can change the password of an XClarity Administrator instance through the physical-infrastructure provider with which it is associated. Changing the password this way also changes the password in CloudForms so that they match." +msgstr "" + +msgid "Click on the physical-infrastructure provider to be modified." +msgstr "" + +msgid "Click on the Authentication button in the top menu and select Change password. The Change Password for Physical Infrastructure Provider page is displayed." +msgstr "" + +msgid "Enter the current password for the XClarity Administrator instance in the Current Password field." +msgstr "" + +msgid "Enter the new password in the New Password and Confirm New Password fields." +msgstr "" + +msgid "Click Save." +msgstr "" + msgid "Viewing relationships" msgstr "" @@ -242,10 +269,13 @@ msgstr "" msgid "To display the topology view for a specific physical-infrastructure provider, complete the following steps." msgstr "" -msgid "Select the physical-infrastructure provider to be viewed." +msgid "Click on the physical-infrastructure provider to be viewed." msgstr "" -msgid "From the overview section, select Topology to display the Topology page. From this page, you can perform the following actions:" +msgid "Once the page loads, ensure that the summary view is being used." +msgstr "" + +msgid "Click on Topology in the Overview table to display the Topology page. From this page, you can perform the following actions:" msgstr "" msgid "Hide or show all physical server by clicking Physical Servers." @@ -257,6 +287,9 @@ msgstr "" msgid "Hide or show all VMs by clicking VMs." msgstr "" +msgid "Hide or show nodes in the graph that have a particular health state by clicking on one of the following states: Valid, Warning, Critical, or Unknown." +msgstr "" + msgid "Double-click or right-click a node in the graph to navigate to the summary pages for that node." msgstr "" @@ -266,7 +299,22 @@ msgstr "" msgid "You can view a list of all physical servers that are managed by a specific physical-infrastructure provider." msgstr "" -msgid "Click Physical Servers in the Relationships section." +msgid "From the physical-infrastructure provider summary view" +msgstr "" + +msgid "After the page loads, ensure that the summary view is being used." +msgstr "" + +msgid "Click on Physical Servers in the Relationships table." +msgstr "" + +msgid "From the physical-infrastructure provider dashboard view" +msgstr "" + +msgid "After the page loads, ensure that the dashboard view is being used." +msgstr "" + +msgid "Click on the number of servers that is displayed displayed in the Servers card." msgstr "" msgid "Viewing virtual-host relationships" @@ -275,19 +323,70 @@ msgstr "" msgid "You can view a list of physical servers that are associated with hosts that are managed by a specific physical-infrastructure provider." msgstr "" -msgid "Click Physical Servers with Host button in the Relationships section." +msgid "Click on Physical Servers with Host in the Relationships table." msgstr "" -msgid "You should see a list of physical servers that are associated with hosts as shown below." +msgid "A list of physical servers that are associated with hosts are displayed as shown below." msgstr "" msgid " host relationships " msgstr "" +msgid "Viewing storage relationships" +msgstr "" + +msgid "You can view a list of all storage systems that are managed by a specific physical-infrastructure provider." +msgstr "" + +msgid "Click on Physical Storages in the Relationships table." +msgstr "" + +msgid "Click on the number of storage systems that is displayed in the Storages card." +msgstr "" + +msgid "Viewing switch relationships" +msgstr "" + +msgid "You can view a list of all switches that are managed by a specific physical-infrastructure provider." +msgstr "" + +msgid "Click on Physical Switches in the Relationships table." +msgstr "" + +msgid "Click on the number of switches that is displayed in the Switches card." +msgstr "" + +msgid "Viewing chassis relationships" +msgstr "" + +msgid "You can view a list of chassis that are managed by a specific physical-infrastructure provider." +msgstr "" + +msgid "Click on Physical Chassis in the Relationships table." +msgstr "" + +msgid "Click on the number of chassis that is displayed in the Chassis card." +msgstr "" + +msgid "Viewing rack relationships" +msgstr "" + +msgid "You can view a list of all racks that are managed by a specific physical-infrastructure provider." +msgstr "" + +msgid "Click on Physical Racks in the Relationships table." +msgstr "" + +msgid "Click on the number of racks that is displayed in the Racks card." +msgstr "" + msgid "Managing physical servers" msgstr "" -msgid "After the Lenovo physical-infrastructure provider is added, the servers that are managed by Lenovo XClarity Administrator are registered in CloudForms. You can then view and manage those servers." +msgid "After the Lenovo physical-infrastructure provider is added, the servers that are managed by XClarity Administrator are registered in CloudForms. You can then view and manage those servers." +msgstr "" + +msgid "Note: It may take a few seconds or so for the servers to appear after adding a physical-infrasturcture provider." msgstr "" msgid "Viewing a Physical Server" @@ -380,10 +479,10 @@ msgstr "" msgid "Provisioning physical servers using configuration patterns" msgstr "" -msgid "You can use configuration patterns in Lenovo XClarity Administrator to quickly provision or preprovision multiple servers from a single set of defined configuration settings. Configuration patterns act as templates for configuring logical storage, I/O adapters, boot order, and other baseboard management controller and Unified Extensible Firmware Interface (UEFI) settings." +msgid "You can use configuration patterns in XClarity Administrator to quickly provision or preprovision multiple servers from a single set of defined configuration settings. Configuration patterns act as templates for configuring logical storage, I/O adapters, boot order, and other baseboard management controller and Unified Extensible Firmware Interface (UEFI) settings." msgstr "" -msgid "A physical-infrastructure provider can discover configuration patterns that are defined on the associated Lenovo XClarity Administrator instance. A configuration pattern can then be applied to a single or multiple physical servers." +msgid "A physical-infrastructure provider can discover configuration patterns that are defined on the associated XClarity Administrator instance. A configuration pattern can then be applied to a single or multiple physical servers." msgstr "" msgid "Note: Configuration patterns can be assigned only to physical servers that do not have a pattern assigned to them." @@ -422,13 +521,190 @@ msgstr "" msgid "Click Submit to deploy the configuration pattern to the specified server. You can monitor the status of the action in the Requests table." msgstr "" -msgid "Troubleshooting Physical Infrastructure Provider Problems" +msgid "Viewing network devices that are associated with a physical server" +msgstr "" + +msgid "From the Physical Server Summary page, you can access details about network devices such as network interface cards." +msgstr "" + +msgid "Access the Physical Servers page, as described in the section, and then select a physical server. The Physical Server Summary page is displayed." +msgstr "" + +msgid "Click on the Network Devices count in the Properties table. A list of network devices is displayed." +msgstr "" + +msgid "Select a network device from the list. The Network Device Summary page is displayed." +msgstr "" + +msgid " network device summary " +msgstr "" + +msgid "Viewing storage devices that are associated with a physical server" +msgstr "" + +msgid "From the Physical Server Summary page, you can access details about storage devices, such as RAID cards." +msgstr "" + +msgid "Click on the Storage Devices count in the Properties table. A list of storage devices is displayed." +msgstr "" + +msgid "Select a storage device from the list. The Storage Device Summary page is displayed." +msgstr "" + +msgid " storage device summary " +msgstr "" + +msgid "Adding physical server widgets to the dashboard" +msgstr "" + +msgid "You can add widgets that display information about physical servers to the default dashboard." +msgstr "" + +msgid "Navigate to Cloud Intel > Dashboard." +msgstr "" + +msgid "Click on the + button from the top menu, and select one of the following widgets:" +msgstr "" + +msgid "Physical Server Availability" +msgstr "" + +msgid "Physical Server Health" +msgstr "" + +msgid "Recently Discovered Physical Servers" +msgstr "" + +msgid "The widget is now displayed on the default dashboard." +msgstr "" + +msgid "Creating a user that belongs to the physical infrastructure usergroup" +msgstr "" + +msgid "You can use the physical infrastructure usergroup to manage physical infrastructures. Users that belong to this group have a default dashboard that contains physical server widgets. The physical server widgets show useful information, such as server health, availability, and recently discovered servers." +msgstr "" + +msgid "To gain the benefits of this usergroup, you must create a new user that belongs to the physical infrastructure group." +msgstr "" + +msgid "Follow the steps described in the Creating a User section in the CloudForms General Configuration documentation. For the group, choose EvmGroup-physical_infrastructure." +msgstr "" + +msgid "After the user is created, log in as the new user, and the default dashboard containing physical server widgets is displayed." +msgstr "" + +msgid "Managing physical chassis" +msgstr "" + +msgid "After the Lenovo physical-infrastructure provider is added, the physical chassis that are managed by XClarity Administrator are registered in CloudForms. You can then view and manage the chassis." +msgstr "" + +msgid "Viewing physical chassis" +msgstr "" + +msgid "To view a list of all physical chassis that are managed by all physical-infrastructure providers, navigate to Compute > Physical Infrastructure > Chassis. The Physical Chassis page is displayed (see the following figure)." +msgstr "" + +msgid "Tip: You can sort the table columns to make it easier to find a specific chassis." +msgstr "" + +msgid " physical chassis " +msgstr "" + +msgid "Locating a physical chassis" +msgstr "" + +msgid "You can change the Location LED state on a physical chassis to locate a chassis in the data center." +msgstr "" + +msgid "Navigate to Compute > Physical Infrastructure > Chassis." +msgstr "" + +msgid "Select the physical chassis. The Physical Chassis Summary page is displayed." +msgstr "" + +msgid "Click on Identify in the top menu, and then click on the appropriate action: Blink LED, Turn On LED, or Turn Off LED." +msgstr "" + +msgid " physical chassis identify led " +msgstr "" + +msgid "Managing physical racks" +msgstr "" + +msgid "After the Lenovo physical-infrastructure provider is added, the physical racks that are managed by XClarity Administrator are registered in CloudForms. You can then view and manage the racks." +msgstr "" + +msgid "Viewing physical racks" +msgstr "" + +msgid "To view a list of all physical racks that are managed by all physical-infrastructure providers, navigate to Compute > Physical Infrastructure > Racks. The Physical Racks page is displayed (see the following figure)." +msgstr "" + +msgid "Tip: You can sort the table columns to make it easier to find a specific rack." +msgstr "" + +msgid " physical racks " +msgstr "" + +msgid "Managing physical storage systems" +msgstr "" + +msgid "After the Lenovo physical-infrastructure provider is added, the physical storage systems that are managed by XClarity Administrator are registered in CloudForms. You can then view and manage the storage systems." +msgstr "" + +msgid "Viewing physical storage systems" +msgstr "" + +msgid "To view a list of all physical storage systems that are managed by all physical-infrastructure providers, navigate to Compute > Physical Infrastructure > Storages. The Physical Storages page is displayed (see the following figure)." +msgstr "" + +msgid "Tip: You can sort the table columns to make it easier to find a specific storage system." +msgstr "" + +msgid " physical storage " +msgstr "" + +msgid "Managing physical switches" +msgstr "" + +msgid "After the Lenovo physical-infrastructure provider is added, the physical switches that are managed by XClarity Administrator are registered in CloudForms. You can then view and manage the switches." +msgstr "" + +msgid "Viewing physical switches" +msgstr "" + +msgid "To view a list of all physical switches that are managed by all physical-infrastructure providers, navigate to Compute > Physical Infrastructure > Switches. The Physical Switches page is displayed (see the following figure)." +msgstr "" + +msgid "Tip: You can sort the table columns to make it easier to find a specific switch." +msgstr "" + +msgid " physical switches " +msgstr "" + +msgid "Restarting physical switches" +msgstr "" + +msgid "You can restart a physical switch that is managed by the physical-infrastructure provider." +msgstr "" + +msgid "Navigate to Compute > Physical Infrastructure > Switches." +msgstr "" + +msgid "Select a physical switch. The Physical Switches Summary page is displayed." +msgstr "" + +msgid "Click on Power in the top menu, and then click on Restart." +msgstr "" + +msgid " physical switch restart " msgstr "" msgid "Automating tasks based on events" msgstr "" -msgid "You can use CloudForms to automatically perform specific tasks when certain events occur on servers that are managed by Lenovo XClarity Administrator through a Lenovo physical-infrastructure provider. To create an automation task, you must create and configure a custom domain. To automatically invoke the task when a certain event occurs, you must create, configure and assign a custom policy." +msgid "You can use CloudForms to automatically perform specific tasks when certain events occur on servers that are managed by XClarity Administrator through a Lenovo physical-infrastructure provider. To create an automation task, you must create and configure a custom domain. To automatically invoke the task when a certain event occurs, you must create, configure and assign a custom policy." msgstr "" msgid "For more information about the CloudForms automation function, see Scripting Actions in CloudForms website." @@ -524,7 +800,7 @@ msgstr "" msgid "Enter a name for the new class instance (for example, FQXHMTS0003G, which is the event that is generated when inventory data cannot be retrieved from a device)." msgstr "" -msgid "Important: The class-instance name must be the same as the name of the event that triggers the task to be invoked. CloudForms matches the class instance with the event by this name. To find the event name, see Messages in the Lenovo XClarity Administrator online documentation." +msgid "Important: The class-instance name must be the same as the name of the event that triggers the task to be invoked. CloudForms matches the class instance with the event by this name. To find the event name, see Messages in the XClarity Administrator online documentation." msgstr "" msgid "Add the path to the event handlers copied in the field’s rel3." @@ -557,8 +833,10 @@ msgstr "" msgid "The policy actions and the policy events must match. For example, use the following path to the policy operation Physical Server Shutdown:" msgstr "" -msgid "/System/event_handlers/event_action_policy? target=physical_server&policy_event=physical_server_shutdown&param=\n" -"The policy_event value is matched with the policy operation applied." +msgid "/System/event_handlers/event_action_policy?target=physical_server&policy_event=physical_server_shutdown&param=" +msgstr "" + +msgid "The policy_event value is matched with the policy operation applied." msgstr "" msgid "Step 3. Create a namespace." @@ -609,8 +887,11 @@ msgstr "" msgid "Enter the following script in the Data field:" msgstr "" -msgid "server = $evm.vmdb('PhysicalServer').first $evm.log(:info, \"Powering Server #{server.name} OFF\")\n" -"server.power_off exit MIQ_OK" +msgid "" +"server = $evm.vmdb('PhysicalServer').first\n" +"$evm.log(:info, \"Powering Server #{server.name} OFF\")\n" +"server.power_off\n" +"exit MIQ_OK" msgstr "" msgid "Click Validate to verify the syntax." @@ -631,7 +912,7 @@ msgstr "" msgid "Enter “execute” for the name." msgstr "" -msgid "Select “Method” for the type" +msgid "Select “Method” for the type." msgstr "" msgid "Select “String” for the data type." @@ -643,9 +924,6 @@ msgstr "" msgid "Click the check mark icon." msgstr "" -msgid "Click Save." -msgstr "" - msgid "Add the method to the class." msgstr "" @@ -772,3 +1050,117 @@ msgstr "" msgid " provider assign profile " msgstr "" +msgid "Creating an alert to monitor physical server health" +msgstr "" + +msgid "Note: For this alert to work correctly, you must first configure the SMTP settings in CloudForms by following instructions in the Outgoing SMTP Email Settings section in the CloudForms Configuration documentation." +msgstr "" + +msgid "In CloudForms, there is a configurable alert for physical servers that sends an alert email when a server that is assigned to the alert is in an unhealthy state. This alert can be used to notify IT administrators that a server is in an unhealthy state, so that they can investigate and resolve potential issues before the issues lead to downtime." +msgstr "" + +msgid "To enable this alert, you must create a physical server alert profile, assign servers to the profile, and then configure the alert that is associated with the profile." +msgstr "" + +msgid "Step 1. Create a physical server alert profile" +msgstr "" + +msgid "Click Alert Profiles > Physical Server Alert Profiles." +msgstr "" + +msgid "Click Configuration > Add a New Physical Server Alert Profile from the top menu." +msgstr "" + +msgid "Enter a description into the Description field." +msgstr "" + +msgid "Select Physical server has critical health state from the Available Physical Server Alerts list, and click on the > button to add it to the Profile Alerts list on the right." +msgstr "" + +msgid "Step 2. Assign servers to the alert profile" +msgstr "" + +msgid "Click Alert Profiles > Physical Server Alert Profiles > ProfileName, where ProfileName is the name of the physical server alert that was previously created." +msgstr "" + +msgid "Click Configuration > Edit assignments for this Alert Profile." +msgstr "" + +msgid "Choose Selected Servers from the Assign To dropdown menu." +msgstr "" + +msgid "Select the checkboxes next to the servers that you want to assign to the profile from the Selections list." +msgstr "" + +msgid "Step 3. Configure the alert associated with the alert profile" +msgstr "" + +msgid "Click Alert Profiles > Physical Server Alert Profiles > ProfileName > Physical server has critical health state, where ProfileName is the name of the physical server alert profile that was previously created." +msgstr "" + +msgid "Click Configuration > Edit this Alert from the top menu." +msgstr "" + +msgid "Select the Active checkbox to enable the alert." +msgstr "" + +msgid "Optionally, increase the notification frequency by selecting a new value from the Notification Frequency dropdown menu. The default frequency is one hour." +msgstr "" + +msgid "Ensure that the Send an E-mail checkbox is selected." +msgstr "" + +msgid "Optionally, enter a value into the From field. By default, the cfadmin@cfserver.com address is used." +msgstr "" + +msgid "Enter the email address that you want to retrieve the alert notification in the Add field, and then click the + button. The email address is displayed in the To field." +msgstr "" + +msgid "The assigned servers are checked hourly, and a notification is sent through email if the any of the assigned servers have a critical health state." +msgstr "" + +msgid "Creating a policy to power on servers that are powered off" +msgstr "" + +msgid "In CloudForms, there is a control policy for physical servers that automatically powers a server back on when it is powered off." +msgstr "" + +msgid "To enable this policy, you must assign the physical infrastructure profile to a server." +msgstr "" + +msgid "Click a server (to display the Physical Server Summary page), or select multiple servers that you want to provision." +msgstr "" + +msgid "Click Policy > Manage Policies from the top menu. The Physical Server Policy Assignment page is displayed." +msgstr "" + +msgid "Select the Physical Infrastructure Profile checkbox." +msgstr "" + +msgid "The policy is now assigned to the server." +msgstr "" + +msgid "Updating physical server firmware using Ansible playbooks" +msgstr "" + +msgid "In CloudForms, physical server firmware can be updated using an Ansible playbook." +msgstr "" + +msgid "Note: An Ansible Tower provider that points to an Ansible Tower instance must be added to CloudForms. See the Adding an Ansible Tower Provider section in the CloudForms Managing Providers documentation." +msgstr "" + +msgid "Within Ansible Tower, create a job template for the config.yml playbook. Specify update_firmware as the job tag and any extra variables that are required by the playbook. Ensure that the option to prompt on launch is enabled. You can use this playbook to upgrade firmware on a physical server. You can get this playbook from the web at https://galaxy.ansible.com/lenovo/lxca-config." +msgstr "" + +msgid "Follow the steps that are described in the Executing an Ansible Tower Job Template from a Service Catalog section in the CloudForms Managing Providers documentation. Use the job template that you created in the previous step." +msgstr "" + +msgid "Provisioning physical servers using Ansible playbooks" +msgstr "" + +msgid "In CloudForms, XClarity Administrator configuration patterns can be used to provision physical servers through the use of an Ansible playbook. Configuration patterns act as templates for configuring logical storage, I/O adapters, boot order, and other baseboard management controller and Unified Extensible Firmware Interface (UEFI) settings." +msgstr "" + +msgid "Within Ansible Tower, create a job template for the config.yml playbook. Specify apply_configpatterns as the job tag and any extra variables that are required by the playbook. Ensure that the option to prompt on launch is enabled. You can use this playbook to apply a configuration pattern to a physical server. You can get this playbook from the web at https://galaxy.ansible.com/lenovo/lxca-config." +msgstr "" + diff --git a/physical_infra_provider_configuration/l10n/publican.cfg b/physical_infra_provider_configuration/l10n/publican.cfg index d0835e1..2df7008 100644 --- a/physical_infra_provider_configuration/l10n/publican.cfg +++ b/physical_infra_provider_configuration/l10n/publican.cfg @@ -1,15 +1,17 @@ # Config::Simple 4.59 -# Mon Mar 5 15:50:12 2018 +# Mon Jan 7 15:36:39 2019 xml_lang: "en-US" dtdver: "5.0" -brand: "common" +brand: "RedHat-Pantheon-db5" type: Book product: "Red Hat CloudForms" -version: "4.6" -docname: "Configuring the Lenovo Physical Infrastructure Provider" +version: "4.7" +docname: "Configuring the Lenovo Physical Infrastructure Provider for Red Hat CloudForms" chunk_section_depth: 0 chunk_first: 0 mainfile: "main" info_file: "main.xml" + + diff --git a/physical_infra_provider_configuration/l10n/zh-CN/Author_Group.po b/physical_infra_provider_configuration/l10n/zh-CN/Author_Group.po index 8c82e65..557e3b0 100644 --- a/physical_infra_provider_configuration/l10n/zh-CN/Author_Group.po +++ b/physical_infra_provider_configuration/l10n/zh-CN/Author_Group.po @@ -2,19 +2,19 @@ msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2018-02-26 09:57+1000\n" +"POT-Creation-Date: 2018-11-22 19:44+1000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"PO-Revision-Date: 2018-02-07 01:19+0000\n" +"PO-Revision-Date: 2018-12-07 04:07+0000\n" "Last-Translator: jsh \n" "Language-Team: Chinese (Simplified)\n" "Language: zh_Hans\n" -"X-Generator: Zanata 4.4.3\n" +"X-Generator: Zanata 4.6.2\n" "Plural-Forms: nplurals=1; plural=0\n" msgid "Red Hat CloudForms" -msgstr "红帽 CloudForms" +msgstr "Red Hat CloudForms" msgid "Documentation Team" msgstr "文档团队" diff --git a/physical_infra_provider_configuration/l10n/zh-CN/Revision_History.po b/physical_infra_provider_configuration/l10n/zh-CN/Revision_History.po index 7dbb5ba..bb243a8 100644 --- a/physical_infra_provider_configuration/l10n/zh-CN/Revision_History.po +++ b/physical_infra_provider_configuration/l10n/zh-CN/Revision_History.po @@ -2,7 +2,7 @@ msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2018-02-26 09:57+1000\n" +"POT-Creation-Date: 2018-11-22 19:44+1000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -10,7 +10,7 @@ msgstr "" "Last-Translator: jsh \n" "Language-Team: Chinese (Simplified)\n" "Language: zh_Hans\n" -"X-Generator: Zanata 4.4.3\n" +"X-Generator: Zanata 4.6.2\n" "Plural-Forms: nplurals=1; plural=0\n" msgid "Revision History" diff --git a/physical_infra_provider_configuration/l10n/zh-CN/main.po b/physical_infra_provider_configuration/l10n/zh-CN/main.po index 89d7316..5614e55 100644 --- a/physical_infra_provider_configuration/l10n/zh-CN/main.po +++ b/physical_infra_provider_configuration/l10n/zh-CN/main.po @@ -2,32 +2,34 @@ msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2018-02-26 09:57+1000\n" +"POT-Creation-Date: 2018-11-22 19:44+1000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"PO-Revision-Date: 2018-03-07 12:04+0000\n" +"PO-Revision-Date: 2018-12-10 01:29+0000\n" "Last-Translator: tfu \n" "Language-Team: Chinese (Simplified)\n" "Language: zh_Hans\n" -"X-Generator: Zanata 4.4.3\n" +"X-Generator: Zanata 4.6.2\n" "Plural-Forms: nplurals=1; plural=0\n" -msgid "Configuring the Lenovo Physical Infrastructure Provider" -msgstr "配置 Lenovo 物理基础架构供应商" +msgid "" +"Configuring the Lenovo Physical Infrastructure Provider for Red Hat " +"CloudForms" +msgstr "为 Red Hat CloudForms 配置 Lenovo 物理基础架构供应商" msgid "" "Adding and configuring the Lenovo physical infrastructure provider in Red " "Hat CloudForms" -msgstr "在红帽 CloudForms 中添加和配置 Lenovo 物理基础架构供应商" +msgstr "在 Red Hat CloudForms 中添加和配置 Lenovo 物理基础架构供应商" msgid "Red Hat CloudForms" -msgstr "红帽 CloudForms" +msgstr "Red Hat CloudForms" msgid "" "Adding and configuring the Lenovo physical infrastructure provider in Red " "Hat CloudForms." -msgstr "在红帽 CloudForms 中添加和配置 Lenovo 物理基础架构供应商。" +msgstr "在Red Hat CloudForms 中添加和配置 Lenovo 物理基础架构供应商。" msgid "" "If you have a suggestion for improving this guide or have found an error, " @@ -41,9 +43,10 @@ msgid "" msgstr "" "如果您有关于改进本指南的建议或发现了错误，请在 http://" -"bugzilla.redhat.com 上针对红帽 CloudForms 管理引擎 的文档组件提交 Bugzilla " -"报告。请提供具体的详细信息，如章节编号、指南名称和 CloudForms 版本等，以便我们能够轻松找到相关的内容。" +"bugzilla.redhat.com 上针对Red Hat CloudForms " +"Management Engine 的 Documentation 组件提交 Bugzilla 报告。请提供具体的详细信息，如章节编号、指南名称和 CloudForms " +"版本等，以便我们能够轻松找到相关的内容。" msgid "Overview" msgstr "概述" @@ -58,7 +61,7 @@ msgid "" "monitoring needed to reduce cost and complexity through server consolidation " "and simplified management." msgstr "" -"Lenovo® 物理基础架构供应商让 IT 管理员能够将 Lenovo XClarity Administrator 的管理功能与红帽 " +"Lenovo® 物理基础架构供应商让 IT 管理员能够将 Lenovo XClarity Administrator 的管理功能与Red Hat " "CloudForms 的混合云功能相集成。通过利用 Lenovo 的硬件管理功能，Lenovo " "扩展了内部云配置的物理基础架构管理功能。它提供了配置、监控、事件管理和电源监控功能，从而可以通过服务器整合和简化的管理来降低成本和复杂度。" @@ -66,23 +69,33 @@ msgid "Key features include:" msgstr "主要功能包括：" msgid "" -"Seamlessly integrates with one or more Lenovo XClarity Administrator virtual " +"Seamlessly integrates with one or more XClarity Administrator virtual " "appliances, providing a summary view of the Lenovo infrastructure, " "relationship views of physical servers and virtual hosts, and configuration " -"of servers using Configuration Patterns" +"of servers using Configuration Patterns. In addition, there is a dashboard " +"view that displays the following:" msgstr "" -"与一台或多台 Lenovo XClarity Administrator 虚拟设备无缝集成，提供 Lenovo " -"基础架构摘要视图、物理服务器与虚拟主机关系视图，以及使用 Configuration Patterns 配置服务器。" +"与一台或多台 XClarity Administrator 虚拟设备无缝集成，提供 Lenovo " +"基础架构摘要视图、物理服务器与虚拟主机关系视图，以及使用 Configuration Patterns " +"配置服务器。此外，还提供仪表板视图，显示以下内容：" + +msgid "" +"The number of servers, switches, racks, and storage systems being mangaged" +msgstr "受管服务器、交换机、机架以及存储系统的数量" + +msgid "" +"Widgets that display information about server health, availability, and " +"recently discovered servers" +msgstr "显示服务器健康状态、可用性以及近期发现的服务器信息的 Widget" msgid "" "Provides a single interface to monitor Lenovo hardware that is managed by " -"multiple instances of Lenovo XClarity Administrator" -msgstr "提供单一界面来监控由多个 Lenovo XClarity Administrator 实例管理的 Lenovo 硬件" +"multiple instances of XClarity Administrator" +msgstr "提供单一界面来监控由多个 XClarity Administrator 实例管理的 Lenovo 硬件" msgid "" -"Automatically discovers hardware that is managed by Lenovo XClarity " -"Administrator" -msgstr "自动发现由 Lenovo XClarity Administrator 管理的硬件" +"Automatically discovers hardware that is managed by XClarity Administrator" +msgstr "自动发现由 XClarity Administrator 管理的硬件" msgid "Manage devices for use in on-premise cloud deployments" msgstr "管理用于内部云部署的设备" @@ -107,119 +120,115 @@ msgstr "管理受管设备上的当前系统设置（如 BMC、uEFI 和引导顺 msgid "" "Simplifies system management through custom policies and automation that " -"respond to the health status of physical servers" -msgstr "通过能响应物理服务器健康状态的自定义策略和自动化来简化系统管理" +"respond to the health status of hardware devices" +msgstr "通过可以根据硬件设备的健康状态作出响应的自定义策略和自动化，简化系统管理" -msgid "Configuring Lenovo XClarity Administrator" -msgstr "配置 Lenovo XClarity Administrator" +msgid "Configuring XClarity Administrator" +msgstr "配置 XClarity Administrator" msgid "" -"Lenovo XClarity Administrator virtual appliances are connected to CloudForms " -"by adding physical-infrastructure providers. Physical-infrastructure " -"providers enable you to manage and interact with devices that are managed by " -"Lenovo XClarity Administrator. After the physical-infrastructure provider is " -"added, the servers that are managed by the Lenovo XClarity Administrator are " -"registered in CloudForms. Managed devices can be monitored, configured, and " -"updated using Lenovo XClarity Administrator. The physical-infrastructure " -"provider surfaces information about these managed devices and the Lenovo " -"XClarity Administrator instance." +"XClarity Administrator virtual appliances are connected to CloudForms by " +"adding physical-infrastructure providers. Physical-infrastructure providers " +"enable you to manage and interact with devices that are managed by XClarity " +"Administrator. After the physical-infrastructure provider is added, the " +"devices that are managed by the XClarity Administrator are registered in " +"CloudForms. Managed devices can be monitored, configured, and updated using " +"XClarity Administrator. The physical-infrastructure provider surfaces " +"information about these managed devices and the XClarity Administrator " +"instance." msgstr "" -"在 CloudForms 中，通过添加物理基础架构供应商的方法就可以把 Lenovo XClarity Administrator 虚拟设连接到 " -"CloudForms。物理基础架构供应商让您能够管理受 Lenovo XClarity Administrator " -"管理的设备并与之互动。在添加了物理基础架构供应商后，受 Lenovo XClarity Administrator 管理的服务器注册到 " -"CloudForms 中，受管理的设备就可以通过 Lenovo XClarity Administrator " -"进行监控、配置和更新。物理基础架构供应商会显示关于这些受管设备和 Lenovo XClarity Administrator 实例的信息。" +"在 CloudForms 中，通过添加物理基础架构供应商的方法就可以将 XClarity Administrator 虚拟设备连接到 " +"CloudForms。物理基础架构供应商让您能够管理受 XClarity Administrator " +"管理的设备并与之互动。在添加了物理基础架构供应商后，受 XClarity Administrator 管理的设备注册到 CloudForms " +"中。受管理的设备就可以通过 XClarity Administrator 进行监控、配置和更新。物理基础架构供应商会显示关于这些受管设备和 " +"XClarity Administrator 实例的信息。" -msgid "Setting up Lenovo XClarity Administrator" -msgstr "设置 Lenovo XClarity Administrator" +msgid "Setting up XClarity Administrator" +msgstr "设置 XClarity Administrator" msgid "" -"For information about downloading and setting up Lenovo XClarity " -"Administrator, see Installing and setting up " -"Lenovo XClarity Administrator in the Lenovo XClarity Administrator " -"online documentation." +"For information about downloading and setting up XClarity Administrator, see " +"Installing and setting up Lenovo XClarity " +"Administrator in the XClarity Administrator online documentation." msgstr "" -"如需关于下载和设置 Lenovo XClarity Administrator 的信息，请参见 Lenovo XClarity " -"Administrator 在线文档中的安装和设置 Lenovo XClarity " -"Administrator。" +"如需关于下载和设置 XClarity Administrator 的信息，请参见 XClarity Administrator 在线文档中的安装和设置 Lenovo XClarity Administrator。" msgid "" "Note: You can use all available " -"features in Lenovo XClarity Administrator for free for up to 90 days. After " -"90 days, you can continue to use Lenovo XClarity Administrator to manage and " -"monitor your hardware for free; however, you must purchase a full-function-" -"enablement license to continue using Lenovo XClarity Administrator to " -"configure your hardware using Configuration Patterns and to deploy operating " -"systems. Lenovo XClarity Pro provides entitlement to service and support and " -"the full-function-enablement license for Lenovo XClarity Administrator. For " -"more information about purchasing Lenovo XClarity Pro, contact your Lenovo " -"representative or authorized business partner." -msgstr "" -"注意： 您可以免费使用 Lenovo XClarity " -"Administrator 中提供的所有功能 90 天。90 天后，仍然可以继续免费使用 Lenovo XClarity Administrator " -"来管理和监控您的硬件，但是，需要购买支持完整功能的许可证才能继续使用 Lenovo XClarity Administrator 来利用 " -"Configuration Patterns 配置您的硬件并部署操作系统。Lenovo XClarity Pro 提供服务和支持权利及支持 Lenovo " -"XClarity Administrator 完整功能的许可证。如需关于购买 Lenovo XClarity Pro 的更多信息，请联系您的 " -"Lenovo 代表或授权商务合作伙伴。" - -msgid "Discovering and managing hardware using Lenovo XClarity Administrator" -msgstr "利用 Lenovo XClarity Administrator 发现和管理硬件" - -msgid "" -"Lenovo XClarity Administrator can discover manageable devices in your " -"environment by performing an SLP discovery for devices that are on the same " -"IP subnet as Lenovo XClarity Administrator. A specified IP address or range " -"of IP addresses also can be used, or information can be imported from a " -"spreadsheet, a process that is known as a bulk import. " -"Discovery options can be accessed by clicking Hardware > Discover and Manage New Devices from the " -"menu bar. Discovered devices can then be managed by Lenovo XClarity " -"Administrator. During the management process, you are asked for login " -"credentials for the management controller of the target servers and given " -"the option to create a recovery account for the servers. For more " -"information about discovering and managing devices, see the Lenovo XClarity Administrator online " +"features in XClarity Administrator for free for up to 90 days. After 90 " +"days, you can continue to use XClarity Administrator to manage and monitor " +"your hardware for free; however, you must purchase a full-function-" +"enablement license to continue using XClarity Administrator to configure " +"your hardware using Configuration Patterns and to deploy operating systems. " +"Lenovo XClarity Pro provides entitlement to service and support and the full-" +"function-enablement license for XClarity Administrator. For more information " +"about purchasing Lenovo XClarity Pro, contact your Lenovo representative or " +"authorized business partner." +msgstr "" +"注意：XClarity Administrator " +"中提供的所有功能可以免费使用 90 天。90 天后，仍然可以继续免费使用 XClarity Administrator " +"来管理和监控您的硬件，但是，需要购买支持完整功能的许可证才能继续使用 XClarity Administrator 来通过 Configuration " +"Patterns 配置您的硬件和部署操作系统。Lenovo XClarity Pro 提供服务和支持授权及支持 XClarity " +"Administrator 完整功能的许可证。如需关于购买 Lenovo XClarity Pro 的更多信息，请联系您的 Lenovo " +"代表或授权商务合作伙伴。" + +msgid "Discovering and managing hardware using XClarity Administrator" +msgstr "利用 XClarity Administrator 发现和管理硬件" + +msgid "" +"XClarity Administrator can discover manageable devices in your environment " +"by performing an SLP discovery for devices that are on the same IP subnet as " +"XClarity Administrator. A specified IP address or range of IP addresses also " +"can be used, or information can be imported from a spreadsheet, a process " +"that is known as a bulk import. Discovery options can " +"be accessed by clicking Hardware > Discover and " +"Manage New Devices from the menu bar. Discovered devices can then " +"be managed by XClarity Administrator. During the management process, you are " +"asked for login credentials for the management controller of the target " +"servers and given the option to create a recovery account for the servers. " +"For more information about discovering and managing devices, see the XClarity Administrator online " "documentation." msgstr "" -"Lenovo XClarity Administrator 可以通过对与 Lenovo XClarity Administrator 处于同一 IP " -"子网中的设备执行 SLP 发现来发现您的环境中的可管理设备。也可以使用指定 IP 地址或 IP " -"地址范围，或者从电子表格导入信息，该流程称为批量导入 。单击菜单栏中的硬件 > 发现和管理新设备可以设置发现选项。Lenovo XClarity Administrator " -"随后会管理所发现的设备。在管理过程中，系统会要求您输入目标服务器的管理控制器的登录凭据，并可以选择为服务器创建恢复帐户。如需关于发现和管理设备的更多信息，请参见 " +"XClarity Administrator 可以通过 SLP 发现操作找出与 XClarity Administrator 处于同一 IP " +"子网中的可管理设备。也可以使用 IP 地址或 IP 地址范围，或者从电子表格导入信息（该操作被称为批量导入）来指定可管理的设备 。单击菜单栏中的硬件 > 发现和管理新设备可以访问发现选项。XClarity Administrator " +"随后会管理所发现的设备。在管理过程中，系统会要求输入目标服务器的管理控制器的登录凭据，并可以选择为服务器创建恢复帐户。如需关于发现和管理设备的更多信息，请参见 " "Lenovo XClarity Administrator " -"在线文档。" +"lenovo.lxca.doc%2Faug_product_page.html\">XClarity Administrator 在线文档。" msgid "Note:" msgstr "注意：" msgid "" -"Ensure that the devices that you intend to manage are supported by Lenovo " -"XClarity Administrator. For information about supported devices, see Supported devices in the Lenovo " -"XClarity Administrator online documentation." +"Ensure that the devices that you intend to manage are supported by XClarity " +"Administrator. For information about supported devices, see Supported devices in the XClarity " +"Administrator online documentation." msgstr "" -"确认 Lenovo XClarity Administrator 支持您想要进行管理的设备。若需关于受支持设备的信息，请参见 Lenovo " -"XClarity Administrator 在线文档中的受支持的设备。" +"确保 XClarity Administrator 支持您想要进行管理的设备。若需关于受支持设备的信息，请参见 XClarity " +"Administrator 在线文档中的受支持的设备。" msgid "" -"Ensure that firmware for all devices that you intend to manage using Lenovo " +"Ensure that firmware for all devices that you intend to manage using " "XClarity Administrator are at the required levels. For more information " "about supported firmware levels, see Supported firmware in the Lenovo XClarity Administrator " -"online documentation." +"1_3_1_2\">Supported firmware in the XClarity Administrator online " +"documentation." msgstr "" -"确保您想要通过 Lenovo XClarity Administrator " -"管理的所有设备的固件都达到所需的级别。如需关于受支持的固件级别的更多信息，请参见 Lenovo XClarity Administrator " -"在线文档中的受支持的固件。" +"确保您想要通过 XClarity Administrator 管理的所有设备的固件都达到所需级别。如需关于受支持的固件级别的更多信息，请参见 " +"XClarity Administrator 在线文档中的受支持的固件。" msgid "Managing physical-infrastructure providers" msgstr "管理物理基础架构供应商" @@ -228,13 +237,13 @@ msgid "Adding a physical-infrastructure provider" msgstr "添加物理基础架构供应商" msgid "" -"Lenovo XClarity Administrator virtual appliances are connected to CloudForms " -"by adding physical-infrastructure providers. Physical-infrastructure " -"providers enable you to manage and interact with devices that are managed by " -"Lenovo XClarity Administrator." +"XClarity Administrator virtual appliances are connected to CloudForms by " +"adding physical-infrastructure providers. Physical-infrastructure providers " +"enable you to manage and interact with devices that are managed by XClarity " +"Administrator." msgstr "" -"Lenovo XClarity Administrator 虚拟设备通过添加物理基础架构供应商来连接到 " -"CloudForms。物理基础架构供应商让您能够管理受 Lenovo XClarity Administrator 管理的设备并与之互动。" +"XClarity Administrator 虚拟设备通过添加物理基础架构供应商来连接到 CloudForms。物理基础架构供应商让您能够管理受 " +"XClarity Administrator 管理的设备并与之互动。" msgid "" "Note: You must be logged in to " @@ -245,12 +254,12 @@ msgstr "" "admin，密码为 smartvm。" msgid "" -"Complete the following steps for each Lenovo XClarity Administrator instance " -"that you want to connect to CloudForms." -msgstr "为您要连接到 CloudForms 的每个 Lenovo XClarity Administrator 实例完成下列步骤。" +"Complete the following steps for each XClarity Administrator instance that " +"you want to connect to CloudForms." +msgstr "为您要连接到 CloudForms 的每个 XClarity Administrator 实例完成下列步骤。" -msgid "To connect to a specific Lenovo XClarity Administrator instance:" -msgstr "连接到特定的 Lenovo XClarity Administrator 实例：" +msgid "To connect to a specific XClarity Administrator instance:" +msgstr "连接到特定的 XClarity Administrator 实例：" msgid "" "Navigate to Compute > Physical Infrastructure " @@ -283,35 +292,34 @@ msgid "In the credentials area, provide the following:" msgstr "在凭据区域中，提供下列信息：" msgid "" -"Enter the hostname, IPv4 address, or IPv6 address of the Lenovo XClarity " +"Enter the hostname, IPv4 address, or IPv6 address of the XClarity " "Administrator instance." -msgstr "输入 Lenovo XClarity Administrator 实例的主机名、 IPv4 地址或 IPv6 地址。" +msgstr "输入 XClarity Administrator 实例的主机名、 IPv4 地址或 IPv6 地址。" msgid "Enter “443” for the API port." msgstr "输入“443”作为 API 端口。" msgid "" -"Enter the username and password used to log in to the Lenovo XClarity " -"Administrator instance." -msgstr "输入用于登录 Lenovo XClarity Administrator 实例的用户名和密码。" +"Enter the username and password used to log in to the XClarity Administrator " +"instance." +msgstr "输入用于登录 XClarity Administrator 实例的用户名和密码。" msgid "" "Click Validate to confirm that you can " -"connect to the Lenovo XClarity Administrator instance." +"connect to the XClarity Administrator instance." msgstr "" -"单击验证来确认您可以连接到 Lenovo XClarity " -"Administrator 实例。" +"单击验证来确认您可以连接到 XClarity Administrator " +"实例。" msgid "Click Add." msgstr "单击添加。" msgid "" -"To discover and then connect to a range of Lenovo XClarity Administrator " -"instances:" -msgstr "发现某一范围的 Lenovo XClarity Administrator 实例后再进行连接：" +"To discover and then connect to a range of XClarity Administrator instances:" +msgstr "发现某一范围的 XClarity Administrator 实例并进行连接：" -msgid "Discover Lenovo XClarity Administrator instances:" -msgstr "发现 Lenovo XClarity Administrator 实例：" +msgid "Discover XClarity Administrator instances:" +msgstr "发现 XClarity Administrator 实例：" msgid "" "Navigate to Compute > Physical Infrastructure " @@ -351,8 +359,8 @@ msgstr "单击开始来开始发现过程 msgid "" "Update credentials for each discovered physical-infrastructure provider " -"(Lenovo XClarity Administrator instance):" -msgstr "更新发现的每一物理基础架构供应商（Lenovo XClarity Administrator 实例）的凭据：" +"(XClarity Administrator instance):" +msgstr "更新发现的每一物理基础架构供应商（XClarity Administrator 实例）的凭据：" msgid "Select the providers to be edited." msgstr "选择要编辑的供应商。" @@ -445,6 +453,49 @@ msgstr "选择要修改的物理基础架构供应商。" msgid "Make the required changes, and revalidate credentials if necessary." msgstr "进行所需的更改，然后根据需要重新验证凭据。" +msgid "" +"Changing the password of the XClarity Administrator instance through its " +"physical-infrastructure provider" +msgstr "通过物理基础架构供应商更改 XClarity Administrator 实例的密码" + +msgid "" +"Within CloudForms, you can change the password of an XClarity Administrator " +"instance through the physical-infrastructure provider with which it is " +"associated. Changing the password this way also changes the password in " +"CloudForms so that they match." +msgstr "" +"在 CloudForms 中，您可以通过与 XClarity Administrator " +"实例关联的物理基础架构供应商来更改其密码。以这种方式更改密码之后，CloudForms 中的密码也随之更改，以便两者匹配。" + +msgid "Click on the physical-infrastructure provider to be modified." +msgstr "单击要修改的物理基础架构供应商。" + +msgid "" +"Click on the Authentication button in " +"the top menu and select Change password." +" The Change Password for Physical Infrastructure Provider page is displayed." +msgstr "" +"单击顶部菜单中的验证按钮，然后选择更改密码。此时会显示“更改物理基础架构供应商密码”页面。" + +msgid "" +"Enter the current password for the XClarity Administrator instance in the " +"Current Password field." +msgstr "" +"在当前密码字段中，输入 XClarity Administrator " +"实例的当前密码。" + +msgid "" +"Enter the new password in the New Password and Confirm New Password " +"fields." +msgstr "" +"在新密码和确认新密码字段中输入新密码。" + +msgid "Click Save." +msgstr "单击保存。" + msgid "Viewing relationships" msgstr "查看关系" @@ -476,15 +527,19 @@ msgid "" "provider, complete the following steps." msgstr "若要显示特定物理基础架构供应商的拓扑视图，请完成下列步骤。" -msgid "Select the physical-infrastructure provider to be viewed." -msgstr "选择要查看的物理基础架构供应商。" +msgid "Click on the physical-infrastructure provider to be viewed." +msgstr "单击要查看的物理基础架构供应商。" + +msgid "Once the page loads, ensure that the summary view is being used." +msgstr "加载页面后，确保已使用概览视图。" msgid "" -"From the overview section, select Topology to display the Topology page. From this page, you can perform the " -"following actions:" +"Click on Topology in the Overview table to display the Topology page. From this " +"page, you can perform the following actions:" msgstr "" -"从概览部分中，选择拓扑来显示“拓扑”页面。您可以从此页中执行下列操作：" +"在概览表中，单击拓扑来显示“拓扑”页面。您可以从此页中执行下列操作：" msgid "" "Hide or show all physical server by clicking VMs." msgstr "单击虚拟机来隐藏或显示所有虚拟机。" +msgid "" +"Hide or show nodes in the graph that have a particular health state by " +"clicking on one of the following states: Valid, Warning, Critical, or Unknown." +msgstr "" +"单击以下任意状态，隐藏或显示图表中特定健康状态的节点： 有效、警告、重要或者未知。" + msgid "" "Double-click or right-click a node in the graph to navigate to the summary " "pages for that node." @@ -513,12 +579,29 @@ msgid "" "physical-infrastructure provider." msgstr "您可以查看受特定物理基础架构供应商管理的所有物理服务器的列表。" +msgid "From the physical-infrastructure provider summary view" +msgstr "从物理基础架构供应商概览视图中" + +msgid "After the page loads, ensure that the summary view is being used." +msgstr "加载页面后，确保使用的是概览视图。" + msgid "" -"Click Physical Servers in the Relationships section." +"Click on Physical Servers in the " +"Relationships table." msgstr "" -"单击关系部分中的物理服务器。" +"单击关系表中的物理服务器。" + +msgid "From the physical-infrastructure provider dashboard view" +msgstr "从物理基础架构供应商仪表板视图中" + +msgid "After the page loads, ensure that the dashboard view is being used." +msgstr "加载页面后，确保使用的是仪表板视图。" + +msgid "" +"Click on the number of servers that is displayed displayed in the Servers card." +msgstr "单击服务器卡中显示的服务器数量。" msgid "Viewing virtual-host relationships" msgstr "查看虚拟主机关系" @@ -529,16 +612,16 @@ msgid "" msgstr "您可以查看，与受特定物理基础架构供应商管理的主机相关联的物理服务器列表。" msgid "" -"Click Physical Servers with Host button " -"in the Relationships section." +"Click on Physical Servers with Host in " +"the Relationships table." msgstr "" -"单击关系部分中的物理服务器与主机按钮。" +"单击关系表中的物理服务器与主机。" msgid "" -"You should see a list of physical servers that are associated with hosts as " +"A list of physical servers that are associated with hosts are displayed as " "shown below." -msgstr "您应该会看到与主机关联的物理服务器的列表，如下所示。" +msgstr "与主机关联的物理服务器列表会被显示，如下所示。" msgid "" " " "主机关系 " +msgid "Viewing storage relationships" +msgstr "查看存储关系" + +msgid "" +"You can view a list of all storage systems that are managed by a specific " +"physical-infrastructure provider." +msgstr "您可以查看受特定物理基础架构供应商管理的所有存储系统的列表。" + +msgid "" +"Click on Physical Storages in the " +"Relationships table." +msgstr "" +"单击关系表中的物理存储。" + +msgid "" +"Click on the number of storage systems that is displayed in the Storages card." +msgstr "单击存储卡中显示的存储系统数量。" + +msgid "Viewing switch relationships" +msgstr "查看交换机关系" + +msgid "" +"You can view a list of all switches that are managed by a specific physical-" +"infrastructure provider." +msgstr "您可以查看受特定物理基础架构供应商管理的所有交换机的列表。" + +msgid "" +"Click on Physical Switches in the " +"Relationships table." +msgstr "" +"单击关系表中的物理交换机。" + +msgid "" +"Click on the number of switches that is displayed in the Switches card." +msgstr "单击交换机卡中显示的交换机数量。" + +msgid "Viewing chassis relationships" +msgstr "查看机箱关系" + +msgid "" +"You can view a list of chassis that are managed by a specific physical-" +"infrastructure provider." +msgstr "您可以查看受特定物理基础架构供应商管理的所有机箱的列表。" + +msgid "" +"Click on Physical Chassis in the " +"Relationships table." +msgstr "" +"单击关系表中的物理机箱。" + +msgid "" +"Click on the number of chassis that is displayed in the Chassis card." +msgstr "单击机箱卡中显示的机箱数量。" + +msgid "Viewing rack relationships" +msgstr "查看机架关系" + +msgid "" +"You can view a list of all racks that are managed by a specific physical-" +"infrastructure provider." +msgstr "您可以查看受特定物理基础架构供应商管理的所有机架的列表。" + +msgid "" +"Click on Physical Racks in the " +"Relationships table." +msgstr "" +"单击关系表中的物理机架。" + +msgid "" +"Click on the number of racks that is displayed in the Racks card." +msgstr "单击机架卡中显示的机架数量。" + msgid "Managing physical servers" msgstr "管理物理服务器" msgid "" "After the Lenovo physical-infrastructure provider is added, the servers that " -"are managed by Lenovo XClarity Administrator are registered in CloudForms. " -"You can then view and manage those servers." +"are managed by XClarity Administrator are registered in CloudForms. You can " +"then view and manage those servers." msgstr "" -"在添加了 Lenovo 物理基础架构供应商后，受 Lenovo XClarity Administrator 管理的服务器就会被注册到 " -"CloudForms 中。然后，您可以查看和管理这些服务器。" +"在添加了 Lenovo 物理基础架构供应商后，受 XClarity Administrator 管理的服务器就会被注册到 CloudForms " +"中。然后，您可以查看和管理这些服务器。" + +msgid "" +"Note: It may take a few seconds or so for the servers " +"to appear after adding a physical-infrasturcture provider." +msgstr "注意：添加物理基础架构供应商之后，服务器需要等待几秒才会显示。" msgid "Viewing a Physical Server" msgstr "查看物理服务器" @@ -738,24 +906,25 @@ msgid "Provisioning physical servers using configuration patterns" msgstr "使用配置 Patterns 置备物理服务器" msgid "" -"You can use configuration patterns in Lenovo XClarity Administrator to " -"quickly provision or preprovision multiple servers from a single set of " -"defined configuration settings. Configuration patterns act as templates for " +"You can use configuration patterns in XClarity Administrator to quickly " +"provision or preprovision multiple servers from a single set of defined " +"configuration settings. Configuration patterns act as templates for " "configuring logical storage, I/O adapters, boot order, and other baseboard " "management controller and Unified Extensible Firmware Interface (UEFI) " "settings." msgstr "" -"您可以使用 Lenovo XClarity Administrator 中的配置 patterns，从一组定义的配置设置置备或预置备多台服务器。配置 " -"Patterns 充当模板，用于配置逻辑存储、I/O 适配器、引导顺序及其他基板管理控制器和统一可扩展固件接口 (UEFI) 设置。" +"您可以使用 XClarity Administrator 中的 Configuration " +"Patterns，从一组定义的配置设置置备或预置备多台服务器。Configuration Patterns 充当模板，用于配置逻辑存储、I/O " +"适配器、引导顺序及其他基板管理控制器和统一可扩展固件接口 (UEFI) 设置。" msgid "" "A physical-infrastructure provider can discover configuration patterns that " -"are defined on the associated Lenovo XClarity Administrator instance. A " +"are defined on the associated XClarity Administrator instance. A " "configuration pattern can then be applied to a single or multiple physical " "servers." msgstr "" -"物理基础架构供应商可以发现关联 Lenovo XClarity Administrator 实例中定义的配置 patterns。然后，就可以选择一个配置 " -"pattern 应用到一台或多台物理服务器。" +"物理基础架构供应商可以发现关联 XClarity Administrator " +"实例中定义的配置模式。然后，就可以选择一个配置模式应用到一台或多台物理服务器。" msgid "" "Note: Configuration patterns can be " @@ -836,21 +1005,382 @@ msgstr "" "单击提交，将配置模式部署到指定的服务器。您可以在请求表中监控操作的状态。" -msgid "Troubleshooting Physical Infrastructure Provider Problems" -msgstr "物理基础架构供应商问题故障排除" +msgid "Viewing network devices that are associated with a physical server" +msgstr "查看与物理服务器关联的网络设备" + +msgid "" +"From the Physical Server Summary page, you can access details about network " +"devices such as network interface cards." +msgstr "在“物理服务器概览”页面，您可以访问网络设备的详细信息，例如网络接口卡。" + +msgid "" +"Access the Physical Servers page, as described in the section, and then select a physical server. " +"The Physical Server Summary page is displayed." +msgstr "" +"按照部分的描述，访问“物理服务器”页面，然后选择一个物理服务器。此时会显示“物理服务器概览”页面。" + +msgid "" +"Click on the Network Devices count in " +"the Properties table. A list of network " +"devices is displayed." +msgstr "" +"单击属性表中的网络设备数量。此时会显示网络设备列表。" + +msgid "" +"Select a network device from the list. The Network Device Summary page is " +"displayed." +msgstr "从列表中选择网络设备。此时会显示“网络设备概览”页面。" + +msgid "" +" " +"network device summary " +msgstr "" +" " +"network device summary " + +msgid "Viewing storage devices that are associated with a physical server" +msgstr "查看与物理服务器关联的存储设备" + +msgid "" +"From the Physical Server Summary page, you can access details about storage " +"devices, such as RAID cards." +msgstr "从“物理服务器概览”页面，可以查看存储设备的详细信息，例如 RAID 卡。" + +msgid "" +"Click on the Storage Devices count in " +"the Properties table. A list of storage " +"devices is displayed." +msgstr "" +"单击属性表中的存储设备数量，将显示存储设备列表。" + +msgid "" +"Select a storage device from the list. The Storage Device Summary page is " +"displayed." +msgstr "从列表中选择存储设备。此时会显示“存储设备概览”页面。" + +msgid "" +" " +"storage device summary " +msgstr "" +" " +"storage device summary " + +msgid "Adding physical server widgets to the dashboard" +msgstr "在仪表板中添加物理服务器 widget" + +msgid "" +"You can add widgets that display information about physical servers to the " +"default dashboard." +msgstr "您可以在默认仪表板中添加用来显示物理服务器详细信息的 widget。" + +msgid "" +"Navigate to Cloud Intel > Dashboard." +msgstr "前往云智能 > 仪表板。" + +msgid "" +"Click on the + button from the top " +"menu, and select one of the following widgets:" +msgstr "单击顶部菜单中的 + 按钮，然后选择下列 widget 之一：" + +msgid "Physical Server Availability" +msgstr "物理服务器可用性" + +msgid "Physical Server Health" +msgstr "物理服务器健康状态" + +msgid "" +"Recently Discovered Physical Servers" +msgstr "最近发现的物理服务器" + +msgid "The widget is now displayed on the default dashboard." +msgstr "该 widget 会在默认仪表板中显示。" + +msgid "Creating a user that belongs to the physical infrastructure usergroup" +msgstr "创建一个属于物理基础架构用户组的用户" + +msgid "" +"You can use the physical infrastructure usergroup to manage physical " +"infrastructures. Users that belong to this group have a default dashboard " +"that contains physical server widgets. The physical server widgets show " +"useful information, such as server health, availability, and recently " +"discovered servers." +msgstr "" +"您可以使用物理基础架构用户组来管理物理基础架构。属于这个组的用户有一个包含物理服务器 widget 的默认仪表板。物理服务器 widget " +"显示有用的信息，例如服务器健康状态、可用性和最近发现的服务器。" + +msgid "" +"To gain the benefits of this usergroup, you must create a new user that " +"belongs to the physical infrastructure group." +msgstr "为了利用这种用户组优势，您必须创建一个属于物理基础架构组的新用户。" + +msgid "" +"Follow the steps described in the Creating a User " +"section in the CloudForms General Configuration " +"documentation. For the group, choose EvmGroup-" +"physical_infrastructure." +msgstr "" +"依照 CloudForms 普通配置文档的创建用户部分所描述的步骤操作。对于组，请选择 EvmGroup-physical_infrastructure。" + +msgid "" +"After the user is created, log in as the new user, and the default dashboard " +"containing physical server widgets is displayed." +msgstr "创建用户之后，以新用户的身份登录，系统将显示包含物理服务器 widget 的默认仪表板。" + +msgid "Managing physical chassis" +msgstr "管理物理机箱" + +msgid "" +"After the Lenovo physical-infrastructure provider is added, the physical " +"chassis that are managed by XClarity Administrator are registered in " +"CloudForms. You can then view and manage the chassis." +msgstr "" +"在添加了 Lenovo 物理基础架构供应商后，受 XClarity Administrator 管理的物理机箱就会被注册到 CloudForms " +"中。然后，您可以查看和管理这些机箱。" + +msgid "Viewing physical chassis" +msgstr "查看物理机箱" + +msgid "" +"To view a list of all physical chassis that are managed by all physical-" +"infrastructure providers, navigate to Compute > " +"Physical Infrastructure > Chassis. The Physical Chassis page " +"is displayed (see the following figure)." +msgstr "" +"若要查看受所有物理基础架构供应商管理的所有物理机箱，请前往计算 > 物理基础架构 > " +"机箱。此时会显示“物理机箱”页面（见下图）。" + +msgid "" +"Tip: You can sort the table columns to " +"make it easier to find a specific chassis." +msgstr "提示： 您可以对表列进行排序，以方便查找特定的机箱。" + +msgid "" +" " +"physical chassis " +msgstr "" +" " +"physical chassis " + +msgid "Locating a physical chassis" +msgstr "定位物理机箱" + +msgid "" +"You can change the Location LED state on a physical chassis to locate a " +"chassis in the data center." +msgstr "您可以更改物理机箱上的位置 LED 状态，以在数据中心中定位机箱。" + +msgid "" +"Navigate to Compute > Physical Infrastructure " +"> Chassis." +msgstr "前往计算 > 物理基础架构 > 机箱。" + +msgid "" +"Select the physical chassis. The Physical Chassis Summary page is displayed." +msgstr "选择物理机箱。此时会显示“物理机箱概览”页面。" + +msgid "" +"Click on Identify in the top menu, and " +"then click on the appropriate action: Blink LED, Turn On LED, or Turn Off LED." +msgstr "" +"单击顶部菜单中的识别，再单击相应的操作：闪烁 LED、打开 LED " +"或关闭 LED。" + +msgid "" +" physical chassis identify led " +msgstr "" +" physical chassis identify led " + +msgid "Managing physical racks" +msgstr "管理物理机架" + +msgid "" +"After the Lenovo physical-infrastructure provider is added, the physical " +"racks that are managed by XClarity Administrator are registered in " +"CloudForms. You can then view and manage the racks." +msgstr "" +"在添加了 Lenovo 物理基础架构供应商后，受 XClarity Administrator 管理的物理机架就会注册到 CloudForms " +"中。然后，您可以查看和管理这些机架。" + +msgid "Viewing physical racks" +msgstr "查看物理机架" + +msgid "" +"To view a list of all physical racks that are managed by all physical-" +"infrastructure providers, navigate to Compute > " +"Physical Infrastructure > Racks. The Physical Racks page is " +"displayed (see the following figure)." +msgstr "" +"若要查看所有物理基础架构供应商管理的所有物理机架的列表，请前往计算 > 物理基础架构 > " +"机架。此时会显示“物理机架”页面（见下图）。" + +msgid "" +"Tip: You can sort the table columns to " +"make it easier to find a specific rack." +msgstr "提示：您可以对表列进行排序，以方便查找特定的机架。" + +msgid "" +" " +"physical racks " +msgstr "" +" " +"physical racks " + +msgid "Managing physical storage systems" +msgstr "管理物理存储系统" + +msgid "" +"After the Lenovo physical-infrastructure provider is added, the physical " +"storage systems that are managed by XClarity Administrator are registered in " +"CloudForms. You can then view and manage the storage systems." +msgstr "" +"在添加了 Lenovo 物理基础架构供应商后，受 XClarity Administrator 管理的物理存储系统就会注册到 CloudForms " +"中。然后，您可以查看和管理这些存储系统。" + +msgid "Viewing physical storage systems" +msgstr "查看物理存储系统" + +msgid "" +"To view a list of all physical storage systems that are managed by all " +"physical-infrastructure providers, navigate to Compute > Physical Infrastructure > Storages. " +"The Physical Storages page is displayed (see the following figure)." +msgstr "" +"若要查看所有物理基础架构供应商管理的所有物理存储系统的列表，请前往计算 > 物理基础架构 " +"> 存储。此时会显示“物理存储”页面（见下图）。" + +msgid "" +"Tip: You can sort the table columns to " +"make it easier to find a specific storage system." +msgstr "提示：您可以对表列进行排序，以方便查找特定的存储系统。" + +msgid "" +" " +"physical storage " +msgstr "" +" " +"physical storage " + +msgid "Managing physical switches" +msgstr "管理物理交换机" + +msgid "" +"After the Lenovo physical-infrastructure provider is added, the physical " +"switches that are managed by XClarity Administrator are registered in " +"CloudForms. You can then view and manage the switches." +msgstr "" +"在添加了 Lenovo 物理基础架构供应商后，受 XClarity Administrator 管理的物理交换机就会注册到 CloudForms " +"中。然后，您可以查看和管理这些交换机。" + +msgid "Viewing physical switches" +msgstr "查看物理交换机" + +msgid "" +"To view a list of all physical switches that are managed by all physical-" +"infrastructure providers, navigate to Compute > " +"Physical Infrastructure > Switches. The Physical Switches page " +"is displayed (see the following figure)." +msgstr "" +"若要查看所有物理基础架构供应商管理的所有物理交换机的列表，请前往计算 > 物理基础架构 " +"> 交换机。此时会显示“物理交换机”页面（见下图）。" + +msgid "" +"Tip: You can sort the table columns to " +"make it easier to find a specific switch." +msgstr "提示：您可以对表列进行排序，以方便查找特定的交换机。" + +msgid "" +" " +"physical switches " +msgstr "" +" " +"physical switches " + +msgid "Restarting physical switches" +msgstr "重启物理交换机" + +msgid "" +"You can restart a physical switch that is managed by the physical-" +"infrastructure provider." +msgstr "您可以重启受物理基础架构供应商管理的物理交换机。" + +msgid "" +"Navigate to Compute > Physical Infrastructure " +"> Switches." +msgstr "前往计算 > 物理基础架构 > 交换机。" + +msgid "" +"Select a physical switch. The Physical Switches Summary page is displayed." +msgstr "选择物理交换机。此时会显示“物理交换机概览”页面。" + +msgid "" +"Click on Power in the top menu, and " +"then click on Restart." +msgstr "" +"单击顶部菜单中的电源，再单击重启。" + +msgid "" +" " +"physical switch restart " +msgstr "" +" " +"physical switch restart " msgid "Automating tasks based on events" msgstr "基于事件自动化任务" msgid "" "You can use CloudForms to automatically perform specific tasks when certain " -"events occur on servers that are managed by Lenovo XClarity Administrator " -"through a Lenovo physical-infrastructure provider. To create an automation " -"task, you must create and configure a custom domain. To automatically invoke " -"the task when a certain event occurs, you must create, configure and assign " -"a custom policy." +"events occur on servers that are managed by XClarity Administrator through a " +"Lenovo physical-infrastructure provider. To create an automation task, you " +"must create and configure a custom domain. To automatically invoke the task " +"when a certain event occurs, you must create, configure and assign a custom " +"policy." msgstr "" -"在 CloudForms 中设置 Lenovo 物理基础架构供应商后，就可以当 Lenovo XClarity Administrator " +"在 CloudForms 中设置 Lenovo 物理基础架构供应商后，就可以在 XClarity Administrator " "所管理的服务器上发生特定事件时，自动执行特定的任务。若要创建自动化任务，您必须创建和配置自定义域。若要在特定事件发生时自动调用任务，您必须创建、配置和分配自定义策略。" msgid "" @@ -1022,11 +1552,11 @@ msgid "" "CloudForms matches the class instance with the event by this name. To find " "the event name, see Messages in the " -"Lenovo XClarity Administrator online documentation." +"XClarity Administrator online documentation." msgstr "" -"重要： 类实例名称必须与触发要调用的任务的事件名称相同。CloudForms " -"按照该名称来匹配类实例和事件。若要查找事件名称，请参见 Lenovo XClarity Administrator 在线文档中的重要：类实例名称必须与触发要调用的任务的事件名称相同。CloudForms " +"按照该名称来匹配类实例和事件。若要查找事件名称，请参见 XClarity Administrator 在线文档中的消息。" msgid "" @@ -1066,13 +1596,14 @@ msgstr "" "策略操作和策略事件必须匹配。例如，使用策略操作物理服务器关机的以下路径：" msgid "" -"/System/event_handlers/event_action_policy? target=" -"physical_server&policy_event=physical_server_shutdown&param=\n" -"The policy_event value is matched with the policy operation applied." +"/System/event_handlers/event_action_policy?target=" +"physical_server&policy_event=physical_server_shutdown&param=" msgstr "" -"/System/event_handlers/event_action_policy? target=" -"physical_server&policy_event=physical_server_shutdown&param=\n" -"policy_event 值与应用的策略操作匹配。" +"/System/event_handlers/event_action_policy?target=" +"physical_server&policy_event=physical_server_shutdown&param=" + +msgid "The policy_event value is matched with the policy operation applied." +msgstr "policy_event 值与应用的策略操作匹配。" msgid "Step 3. Create a namespace." msgstr "第 3 步：创建命名空间。" @@ -1133,13 +1664,15 @@ msgid "" msgstr "在数据字段中输入以下脚本：" msgid "" -"server = $evm.vmdb('PhysicalServer').first $evm.log(:info, \"Powering Server " -"#{server.name} OFF\")\n" -"server.power_off exit MIQ_OK" +"server = $evm.vmdb('PhysicalServer').first\n" +"$evm.log(:info, \"Powering Server #{server.name} OFF\")\n" +"server.power_off\n" +"exit MIQ_OK" msgstr "" -"server = $evm.vmdb('PhysicalServer').first $evm.log(:info, \"Powering Server " -"#{server.name} OFF\")\n" -"server.power_off exit MIQ_OK" +"server = $evm.vmdb('PhysicalServer').first\n" +"$evm.log(:info, \"Powering Server #{server.name} OFF\")\n" +"server.power_off\n" +"exit MIQ_OK" msgid "" "Click Validate to verify the syntax." @@ -1164,8 +1697,8 @@ msgstr "单击 + 图标，为该模式添 msgid "Enter “execute” for the name." msgstr "输入 “execute” 作为名称。" -msgid "Select “Method” for the type" -msgstr "选择 “Method” 作为类型" +msgid "Select “Method” for the type." +msgstr "选择“Method”作为类型。" msgid "Select “String” for the data type." msgstr "选择 “String” 作为数据类型。" @@ -1178,9 +1711,6 @@ msgstr "输入 “Power_actions” 作为 msgid "Click the check mark icon." msgstr "单击勾号图标。" -msgid "Click Save." -msgstr "单击保存。" - msgid "Add the method to the class." msgstr "添加方法到该类。" @@ -1372,3 +1902,252 @@ msgstr "" " " "供应商分配配置集 " + +msgid "Creating an alert to monitor physical server health" +msgstr "创建警告来监测物理服务器健康状态" + +msgid "" +"Note: For this alert to work correctly, you must first " +"configure the SMTP settings in CloudForms by following instructions in the " +"Outgoing SMTP Email Settings section in the " +"CloudForms Configuration documentation." +msgstr "" +"注意：若要这个警告正常工作，您必须先按照CloudForms 配置文档的转出 SMTP 邮件设置部分的指令来配置 CloudForms 的 SMTP 设置。" + +msgid "" +"In CloudForms, there is a configurable alert for physical servers that sends " +"an alert email when a server that is assigned to the alert is in an " +"unhealthy state. This alert can be used to notify IT administrators that a " +"server is in an unhealthy state, so that they can investigate and resolve " +"potential issues before the issues lead to downtime." +msgstr "" +"在 CloudForms 中，有一个针对物理服务器的可配置警告，当分配给该警告的服务器处于不健康状态时，该警告将发送警告电子邮件。此警告可用于通知 IT " +"管理员服务器处于不健康状态，以便在问题导致停机之前调查和解决潜在问题。" + +msgid "" +"To enable this alert, you must create a physical server alert profile, " +"assign servers to the profile, and then configure the alert that is " +"associated with the profile." +msgstr "要启用此警告，您必须创建物理服务器警告配置集，将服务器分配给该配置集，然后配置与该配置集关联的警告。" + +msgid "Step 1. Create a physical server alert profile" +msgstr "第 1 步：创建物理服务器警告配置集" + +msgid "" +"Click Alert Profiles > Physical Server Alert " +"Profiles." +msgstr "单击警告配置集 > 物理服务器警告配置集。" + +msgid "" +"Click Configuration > Add a New Physical Server " +"Alert Profile from the top menu." +msgstr "单击顶部菜单中的配置 > 添加新的物理服务器警告配置集。" + +msgid "" +"Enter a description into the Description field." +msgstr "在描述字段中输入描述信息。" + +msgid "" +"Select Physical server has critical health state from the Available Physical Server " +"Alerts list, and click on the > button to add it to the Profile Alerts list on the right." +msgstr "" +"从可用的物理服务器警告列表选择物理服务器存在关键健康状态，然后单击 > 按钮，将其添加到右侧的配置集警告列表。" + +msgid "Step 2. Assign servers to the alert profile" +msgstr "第 2 步：为警告配置集分配服务器" + +msgid "" +"Click Alert Profiles > Physical Server Alert " +"Profiles > ProfileName, where " +"ProfileName is the name of the physical server alert " +"that was previously created." +msgstr "" +"单击警告配置集 > 物理服务器警告配置集 > " +"ProfileName，其中 ProfileName 是之前创建的物理服务器警告的名称。" + +msgid "" +"Click Configuration > Edit assignments for this " +"Alert Profile." +msgstr "单击配置 > 编辑这个警告配置集的分配。" + +msgid "" +"Choose Selected Servers from the " +"Assign To dropdown menu." +msgstr "" +"从分配给下拉菜单中选择已选服务器。" + +msgid "" +"Select the checkboxes next to the servers that you want to assign to the " +"profile from the Selections list." +msgstr "从选择列表中，选中想要分配给配置集的服务器的复选框。" + +msgid "Step 3. Configure the alert associated with the alert profile" +msgstr "第 3 步：配置与警告配置集关联的警告" + +msgid "" +"Click Alert Profiles > Physical Server Alert " +"Profiles > ProfileName > Physical server has " +"critical health state, where ProfileName is " +"the name of the physical server alert profile that was previously created." +msgstr "" +"单击警告配置集 > 物理服务器警告配置集 > " +"ProfileName > 物理服务器存在关键健康状态，其中 " +"ProfileName 是之前创建的物理服务器警告配置集的名称。" + +msgid "" +"Click Configuration > Edit this Alert from the top menu." +msgstr "单击顶部菜单中的配置 > 编辑这个警告。" + +msgid "" +"Select the Active checkbox to enable " +"the alert." +msgstr "选择激活复选框，以启用该警告。" + +msgid "" +"Optionally, increase the notification frequency by selecting a new value " +"from the Notification Frequency " +"dropdown menu. The default frequency is one hour." +msgstr "" +"（可选）可以通过从通知频率下拉菜单中选择新值来增大通知频率。默认频率为 1 " +"小时。" + +msgid "" +"Ensure that the Send an E-mail checkbox " +"is selected." +msgstr "确保发送电子邮件复选框已选中。" + +msgid "" +"Optionally, enter a value into the From " +"field. By default, the cfadmin@cfserver.com address is " +"used." +msgstr "" +"（可选）在发件人字段中输入值。默认使用的是 " +"cfadmin@cfserver.com 地址。" + +msgid "" +"Enter the email address that you want to retrieve the alert notification in " +"the Add field, and then click the " +"+ button. The email address is " +"displayed in the To field." +msgstr "" +"在添加字段中输入您想要用来收取警告通知的电子邮件地址，然后单击 " +"+ 按钮。电子邮件地址会显示在收件人字段中。" + +msgid "" +"The assigned servers are checked hourly, and a notification is sent through " +"email if the any of the assigned servers have a critical health state." +msgstr "系统每隔一小时检查一次分配的服务器；如果分配的任何服务器存在关键健康状态，会通过电子邮件发送通知。" + +msgid "Creating a policy to power on servers that are powered off" +msgstr "创建一个策略以打开处于关闭状态的服务器" + +msgid "" +"In CloudForms, there is a control policy for physical servers that " +"automatically powers a server back on when it is powered off." +msgstr "CloudForms 中有一个针对物理服务器的控制策略，可以在服务器关闭之后自动将其打开。" + +msgid "" +"To enable this policy, you must assign the physical infrastructure profile " +"to a server." +msgstr "要启动此策略，您必须将物理基础架构配置集分配给服务器。" + +msgid "" +"Click a server (to display the Physical Server Summary page), or select " +"multiple servers that you want to provision." +msgstr "单击一台服务器（以显示“物理服务器概览”页面），或选择您要置备的多台服务器。" + +msgid "" +"Click Policy > Manage Policies from " +"the top menu. The Physical Server Policy Assignment page is displayed." +msgstr "" +"单击顶部菜单的策略 > 管理策略。此时会显示“物理服务器策略分配”页面。" + +msgid "" +"Select the Physical Infrastructure Profile checkbox." +msgstr "选择物理基础架构配置集复选框。" + +msgid "The policy is now assigned to the server." +msgstr "现在，策略已分配给服务器。" + +msgid "Updating physical server firmware using Ansible playbooks" +msgstr "使用 Ansible playbook 更新物理服务器固件" + +msgid "" +"In CloudForms, physical server firmware can be updated using an Ansible " +"playbook." +msgstr "在 CloudForms 中，可使用 Ansible playbook 来更新物理服务器固件。" + +msgid "" +"Note: An Ansible Tower provider that points to an " +"Ansible Tower instance must be added to CloudForms. See the Adding " +"an Ansible Tower Provider section in the CloudForms " +"Managing Providers documentation." +msgstr "" +"注意：指向 Ansible Tower 实例的 Ansible Tower 供应商必须添加至 " +"CloudForms。请查看 CloudForms 管理供应商文档中的添加 Ansible " +"Tower 供应商部分。" + +msgid "" +"Within Ansible Tower, create a job template for the config.yml playbook. Specify update_firmware as the job " +"tag and any extra variables that are required by the playbook. Ensure that " +"the option to prompt on launch is enabled. You can use this playbook to " +"upgrade firmware on a physical server. You can get this playbook from the " +"web at https://galaxy.ansible.com/lenovo/lxca-config." +msgstr "" +"在 Ansible Tower 中，为 config.yml playbook 创建任务模板。指定 " +"update_firmware 作为任务标签，并指定 playbook " +"所需的额外变量。确保已启用“启动提示”选项。您可以使用这个 playbook 升级物理服务器的固件。可以从 https://galaxy.ansible.com/" +"lenovo/lxca-config 网页下载此 playbook。" + +msgid "" +"Follow the steps that are described in the Executing an Ansible " +"Tower Job Template from a Service Catalog section in the " +"CloudForms Managing Providers documentation. Use the " +"job template that you created in the previous step." +msgstr "" +"按照 CloudForms 管理供应商文档的执行来自服务目录的 Ansible Tower " +"任务模版部分所述的步骤进行操作。使用您在之前步骤中创建的任务模板。" + +msgid "Provisioning physical servers using Ansible playbooks" +msgstr "使用 Ansible playbook 配置物理服务器" + +msgid "" +"In CloudForms, XClarity Administrator configuration patterns can be used to " +"provision physical servers through the use of an Ansible playbook. " +"Configuration patterns act as templates for configuring logical storage, I/O " +"adapters, boot order, and other baseboard management controller and Unified " +"Extensible Firmware Interface (UEFI) settings." +msgstr "" +"在 CloudForms 中，XClarity Administrator configuration patterns 可以用来通过 Ansible " +"playbook 置备物理服务器。configuration patterns 充当模板，用于配置逻辑存储、I/O " +"适配器、引导顺序及其他基板管理控制器和统一可扩展固件接口 (UEFI) 设置。" + +msgid "" +"Within Ansible Tower, create a job template for the config.yml playbook. Specify apply_configpatterns as the " +"job tag and any extra variables that are required by the playbook. Ensure " +"that the option to prompt on launch is enabled. You can use this playbook to " +"apply a configuration pattern to a physical server. You can get this " +"playbook from the web at https://galaxy.ansible.com/lenovo/lxca-config." +msgstr "" +"在 Ansible Tower 中，为 config.yml playbook 创建任务模板。指定 " +"apply_configpatterns 作为任务标签，指定 playbook " +"所需的任意额外变量。确保已启用“启动提示”选项。您可以使用这个 playbook 对物理服务器应用配置模式。可以从 https://galaxy.ansible.com/" +"lenovo/lxca-config 网页下载此 playbook。" diff --git a/physical_infra_provider_rest_api/l10n/en-US/Revision_History.xml b/physical_infra_provider_rest_api/l10n/en-US/Revision_History.xml index 3736b04..2f8566e 100644 --- a/physical_infra_provider_rest_api/l10n/en-US/Revision_History.xml +++ b/physical_infra_provider_rest_api/l10n/en-US/Revision_History.xml @@ -12,7 +12,7 @@ 1.0-0 - Mon Mar 5 2018 + Wed Dec 12 2018 Red Hat CCS Initial document creation diff --git a/physical_infra_provider_rest_api/l10n/en-US/main.xml b/physical_infra_provider_rest_api/l10n/en-US/main.xml index d51bbcf..9b99683 100644 --- a/physical_infra_provider_rest_api/l10n/en-US/main.xml +++ b/physical_infra_provider_rest_api/l10n/en-US/main.xml @@ -9,9 +9,9 @@ Lenovo Physical Infrastructure Provider REST APIA reference to the Lenovo physical infrastructure provider REST API -2018-03-05 +2018-11-22 Red Hat CloudForms -4.6 +4.7 A reference to the Lenovo physical infrastructure provider REST API. If you have a suggestion for improving this guide or have found an error, please submit a Bugzilla report at http://bugzilla.redhat.com against Red Hat CloudForms Management Engine for the Documentation component. Please provide specific details, such as the section number, guide name, and CloudForms version so we can easily locate the content. @@ -23,45 +23,41 @@ You can use the REST API to retrieve information about providers, physical-infrastructure providers, and physical servers. You can use the CloudForms REST API if you need information about the servers in your physical infrastructure. Before you begin To use the REST API, you must log in to CloudForms Management Engine API as a user who has permission to access the API. The default user is admin, password is smartvm. -Use the following URL to access the CloudForms REST API: -<CloudForms_address>:<port>/api -For example: -localhost:3000/api
Retrieving Provider Details To retrieve information for all providers, use the following request URL: -GET <CloudForms_address>:<port>/api/providers +GET /api/providers A JSON response with the following keys is returned. actions (list of actions that can be used) count (total number of providers) name (URI name) -pages (count of pages) +pages (number of pages) resource (list of URLs for each provider that is managed by CloudForms) -subcount (number of providers returned) +subcount (number of providers that were returned) Examples To retrieve all information about the providers, use the ?expand=resources query parameter, for example: -GET localhost:3000/api/providers?expand=resources +GET /api/providers?expand=resources To retrieve a specific information about the providers (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example: -GET localhost:3000/ api/providers?expand=resources&attributes=id,name +GET /api/providers?expand=resources&attributes=id,name To retrieve additional information about the providers (such as port, hostname, and IP address), use the ?expand=resources&attributes=<attribute_list> query parameters, for example: -GET localhost:3000/api/providers?expand=resources&attributes=port,hostname,ipaddress +GET /api/providers?expand=resources&attributes=port,hostname,ipaddress To retrieve information about only Lenovo physical-infrastructure providers, use the ?expand=resources&filter[]=type=<provider_type> attribute against all provider resources, for example: -GET localhost:3000/api/providers?expand=resources&filter[]=type=ManageIQ::Providers::Lenovo::PhysicalInfraManager +GET /api/providers?expand=resources&filter[]=type=ManageIQ::Providers::Lenovo::PhysicalInfraManager
Retrieving Provider Details by ID To retrieve information for a specific provider, use the following request URL where <provider_ID> is the unique identifier of the provider: -GET <CloudForms_address>:<port>/api/providers/<provider_ID> +GET /api/providers/<provider_ID> A JSON response with the following keys is returned. href id @@ -80,11 +76,11 @@ actions To retrieve a specific information about the provider (such as name and ID), use the ?attributes=<attribute_list> query parameters, for example: -GET localhost:3000/api/providers/<provider_ID>?expand=resources&attributes=id,name +GET /api/providers/<provider_ID>?expand=resources&attributes=id,name To retrieve additional information about the provider (such as port, hostname, and IP address), use the ?attributes=<attribute_list> query parameters, for example: - GET localhost:3000/api/providers/<provider_ID>?expand=resources +GET /api/providers/<provider_ID>?expand=resources &attributes=port,hostname,ipaddress @@ -96,7 +92,7 @@ actions
Creating a Lenovo physical-infrastructure provider To create a Lenovo physical-infrastructure provider, send a POST request using the following request URL and JSON request body. -POST <CloudForms_address>:<port>/api/providers +POST /api/providers Request body: { "action": "create", @@ -113,7 +109,7 @@ actions
Modifying properties for a Lenovo physical-infrastructure provider To modify properties of a Lenovo physical-infrastructure provider, send a POST request using the following request URL and JSON request body. -POST <CloudForms_address>:<port>/api/providers +POST /api/providers Request body: { "action":"edit", @@ -129,7 +125,7 @@ actions
Refreshing information about all providers To refresh information about all providers, send a POST request using the following request URL and JSON request body. -POST <CloudForms_address>:<port>/api/providers +POST /api/providers Request body: { "action":"refresh" @@ -141,11 +137,11 @@ actions Send a DELETE request using the following request URL. -DELETE <CloudForms_address>:<port>/api/providers/<provider_ID> +DELETE /api/providers/<provider_ID> Send a POST request using the following request URL and JSON request body. -POST <CloudForms_address>:<port>/api/providers/<provider_ID> +POST /api/providers/<provider_ID> Request body: { "action":"delete" @@ -156,7 +152,7 @@ actions
Performing an action on multiple physical-infrastructure providers To perform an action on more than one physical-infrastructure providers, send a POST request using the following request URL and JSON request body. -POST <CloudForms_address>:<port>/api/providers +POST /api/providers Request body: { "action":"<action>", @@ -172,38 +168,46 @@ actions
Retrieving Physical Server Details To retrieve information for all physical servers, use the following request URL: -GET <CloudForms_address>:<port>/api/physical_servers +GET /api/physical_servers A JSON response with the following keys is returned. actions (list of actions that can be used) -count (count of the physical servers) +count (number of physical servers) name (URI name) -pages (count of pages) -resource (list of URLs of the each physical servers) -subcount (count of the physical servers returned) +pages (number of pages) +resource (list of URLs for each physical server) +subcount (number of physical servers that were returned) Examples To retrieve all information about the physical servers, use the ?expand=resources query parameter, for example: -GET localhost:3000/api/physical_servers?expand=resources +GET /api/physical_servers?expand=resources + + +To retrieve specific information about the physical servers (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example: +GET /api/physical_servers?expand=resources&attributes=id,name + + +To retrieve information such as firmware, networks, guest devices, and asset details associated with physical servers, use the ?expand=resources&attributes=<attribute_list> query parameters, for example: +GET /api/physical_servers?expand=resources&attributes=hardware.firmwares,hardware.networks,hardware.guest_devices,hardware.assets_details -To retrieve a specific information about the physical servers (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example: -GET localhost:3000/api/physical_servers?expand=resources&attributes=id,name +To retrieve information such as network adapters and storage adapters in physical servers, use the ?expand=resources&attributes=<attribute_list> query parameters, for example: +GET /api/physical_servers?expand=resources&attributes=guest_devices.with_ethernet_type,guest_devices.with_storage_type -To retrieve specific information about the physical servers (such as firmware, networks, guest devices, and asset details), use the ?expand=resources&attributes=<attribute_list> query parameters, for example: -GET localhost:3000/api/physical_servers?expand=resources&attributes= hardware.firmwares,hardware.networks,hardware.guest_devices,hardware.assets_details +To retrieve information such as switches connected to physical servers, use the ?expand=resources&attributes=<attribute_list> query parameters, for example: +GET /api/physical_servers?expand=resources&attributes=physical_switches To retrieve information about only a specific physical server, use the ?expand=resources&filter[]=name=<server_name> query attributes on all physical-server resources, for example: -GET localhost:3000/api/physical_servers?expand=resources&filter[]=name=Server1-20127X5462 +GET /api/physical_servers?expand=resources&filter[]=name=Server1-20127X5462
Retrieving Physical Server Details by ID To retrieve information for a specific physical server, use the following request URL: -GET <CloudForms_address>:<port>/api/physical_servers/<server_ID> +GET /api/physical_servers/<server_ID> A JSON response with the following keys is returned. actions created_at @@ -228,14 +232,22 @@ vendor Examples -To retrieve a specific information about a specific physical server (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example: -GET localhost:3000/api/physical_servers/<server_ID>?expand=resources&attributes=id,name +To retrieve information about a specific physical server (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example: +GET /api/physical_servers/<server_ID>?expand=resources&attributes=id,name -To retrieve a specific information about a specific physical server (such as firmware, networks, guest devices, and asset details), use the ?expand=resources&attributes=<attribute_list> query parameters, for example: - GET localhost:3000/api/physical_servers/<server_ID>?expand=resources +To retrieve information such as firmware, networks, guest devices, and asset details for a specific server, use the ?expand=resources&attributes=<attribute_list> query parameters, for example: +GET /api/physical_servers/<server_ID>?expand=resources &attributes=hardware.firmwares,hardware.networks,hardware.guest_devices,hardware.assets_details + +To retrieve information such as switches that are connected to a specific server, use the ?expand=resources&attributes=<attribute_list> query parameters, for example: +GET /api/physical_servers/<server_ID>?expand=resources&attributes=physical_switches + + +To retrieve information such as network adapters and storage adapters in a specific physical server, use the ?expand=resources&attributes=<attribute_list> query parameters, for example: +GET /api/physical_servers/<server_ID>?expand=resources&attributes=guest_devices.with_ethernet_type,guest_devices.with_storage_type,hardware.physical_network_ports +
@@ -245,7 +257,7 @@ vendor
Powering on a physical server To power on a specific physical server, send a POST request using the following request URL and JSON request body. -POST <CloudForms_address>:<port>/api/physical_servers/<server_ID> +POST /api/physical_servers/<server_ID> Request body: { "action":"power_on" @@ -254,7 +266,7 @@ vendor
Powering off a physical server To shut down the operating system and power off a specific physical server, send a POST request using the following request URL and JSON request body. -POST <CloudForms_address>:<port>/api/physical_servers/<server_ID> +POST /api/physical_servers/<server_ID> Request body: { "action":"power_off" @@ -263,7 +275,7 @@ vendor
Immediately powering off a physical server To immediately power off a specific physical server, send a POST request using the following request URL and JSON request body. -POST <CloudForms_address>:<port>/api/physical_servers/<server_ID> +POST /api/physical_servers/<server_ID> Request body: { "action":"power_off_now" @@ -272,7 +284,7 @@ vendor
Restarting a physical server To shut down the operating system and restart a specific physical server, send a POST request using the following request URL and JSON request body. -POST <CloudForms_address>:<port>/api/physical_servers/<server_ID> +POST /api/physical_servers/<server_ID> Request body: { "action":"restart" @@ -281,7 +293,7 @@ vendor
Immediately restarting a physical server To immediately restart a specific physical server, send a POST request using the following request URL and JSON request body. -POST <CloudForms_address>:<port>/api/physical_servers/<server_ID> +POST /api/physical_servers/<server_ID> Request body: { "action":"restart_now" @@ -290,7 +302,7 @@ vendor
Changing the location LED state on a physical server to blinking To change the location-LED state to blinking on a specific server, send a POST request using the following request URL and JSON request body. -POST <CloudForms_address>:<port>/api/physical_servers/<server_ID> +POST /api/physical_servers/<server_ID> Request body: { "action":"blink_loc_led" @@ -298,8 +310,8 @@ vendor
Performing an action on multiple physical servers -To perform an action on more than one physical severs, send a POST request using the following request URL and JSON request body. -POST <CloudForms_address>:<port>/api/physical_servers +To perform an action on more than one physical server, send a POST request using the following request URL and JSON request body. +POST /api/physical_servers Request body: { "action":"<action>", @@ -312,5 +324,312 @@ vendor }
+
+Retrieving Physical Chassis Details +To retrieve information for all physical chassis, use the following request URL: +GET /api/physical_chassis +A JSON response with the following keys is returned. +actions (list of actions that can be used) +count (number of physical chassis) +name (URI name) +pages (number of pages) +resources (list of URLs for each physical chassis) +subcount (number of physical chassis that were returned) +Examples + + +To retrieve all information about the physical chassis, use the ?expand=resources query parameter, for example: +GET /api/physical_chassis?expand=resources + + +To retrieve specific information about the physical chassis (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example: +GET /api/physical_chassis?expand=resources&attributes=id,name + + +To retrieve information such as the switches, storage systems, and servers in a chassis, use the ?expand=resources&attributes=<attribute_list> query parameters, for example: +GET /api/physical_chassis?expand=resources&attributes=physical_servers,physical_storages,hardware.connected_physical_switches + + +To retrieve information about only a specific physical chassis, use the ?expand=resources&filter[]=name=<chassis_name> query attributes on all physical chassis resources, for example: +GET /api/physical_chassis?expand=resources&filter[]=name=SN%23Y034BG16E060 + + +
+
+Retrieving Physical Chassis Details by ID +To retrieve information for a specific physical chassis, use the following request URL: +GET /api/physical_chassis/<chassis_ID> +A JSON response with the following keys is returned. +href +id +ems_id +uid_ems +ems_ref +physical_rack_id +name +vendor +type +location_led_state +health_state +overall_health_state +management_module_slot_count +switch_slot_count +fan_slot_count +blade_slot_count +powersupply_slot_count +actions +Examples + + +To retrieve information about a specific physical chassis (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example: +GET /api/physical_chassis/<chassis_ID>?expand=resources&attributes=id,name + + +To retrieve information, such as the switches, storage systems, and servers that are in a specific physical chassis, use the ?expand=resources&attributes=<attribute_list> query parameters, for example: +GET /api/physical_chassis/<chassis_ID>?expand=resources&attributes=physical_servers,physical_storages,hardware.connected_physical_switches + + +
+
+Performing physical chassis actions +You can use the REST API to perform management tasks on a physical chassis, such as changing the location LED state. +Note: To perform actions on physical chassis, you must create a basic authentication using your preferred tool or library, and enter your user name and password to access the CloudForms REST API. +
+Changing the location LED state on a physical chassis to blinking +To change the location LED state to blinking on a specific chassis, send a POST request using the following request URL and JSON request body. +POST /api/physical_chassis/<chassis_ID> +Request body: +{ + "action":"blink_loc_led" +} +
+
+Performing an action on multiple physical chassis +To perform an action on more than one physical chassis, send a POST request using the following request URL and JSON request body. +POST /api/physical_chassis +Request body: +{ + "action":"<action>", + "resources": [{ + "href":"<chassis_ID>" + }, + { + "href":"<chassis_ID>" + }] +} +
+
+
+Retrieving Physical Rack Details +To retrieve information for all physical racks, use the following request URL: +GET /api/physical_racks +A JSON response with the following keys is returned. +actions (list of actions that can be used) +count (number of physical racks) +name (URI name) +pages (number of pages) +resources (list of URLs for each physical rack) +subcount (number of physical racks that were returned) +Examples + + +To retrieve all information about the physical racks, use the ?expand=resources query parameter, for example: +GET /api/physical_racks?expand=resources + + +To retrieve specific information about the physical racks (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example: +GET /api/physical_racks?expand=resources&attributes=id,name + + +To retrieve information about only a specific physical rack, use the ?expand=resources&filter[]=name=<rack_name> query attributes on all physical rack resources, for example: +GET /api/physical_racks?expand=resources&filter[]=name=rack-2 + + +
+
+Retrieving Physical Rack Details by ID +To retrieve information for a specific physical rack, use the following request URL: +GET /api/physical_racks/<rack_ID> +A JSON response with the following keys is returned. +actions +ems_id +ems_ref +href +id +name +uid_ems +Examples + + +To retrieve information about a specific physical rack (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example: +GET /api/physical_racks/<rack_ID>?expand=resources&attributes=id,name + + +
+
+Retrieving Physical Storage Details +To retrieve information for all physical storage systems, use the following request URL: +GET /api/physical_storages +A JSON response with the following keys is returned. +actions (list of actions that can be used) +count (number of physical storage systems) +name (URI name) +pages (number of pages) +resources (list of URLs for each physical storage system) +subcount (number of physical storage systems that were returned) +Examples + + +To retrieve all information about the physical storage systems, use the ?expand=resources query parameter, for example: +GET /api/physical_storages?expand=resources + + +To retrieve specific information about the physical storage systems (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example: +GET /api/physical_storages?expand=resources&attributes=id,name + + +To retrieve information such as canisters and physical disks associated with physical storage systems, use the ?expand=resources&attributes=<attribute_list> query parameters, for example: +GET /api/physical_storages?expand=resources&attributes=canisters,physical_disks + + +To retrieve information about only a specific physical storage system, use the ?expand=resources&filter[]=name=<storage_name> query attributes on all physical storage resources, for example: +GET /api/physical_storages?expand=resources&filter[]=name=SeagateV1-S3200-DM + + +
+
+Retrieving Physical Storage Details by ID +To retrieve information for a specific physical storage system, use the following request URL: +GET /api/physical_storages/<storage_ID> +A JSON response with the following keys is returned. +access_state +actions +canister_slots +drive_bays +ems_id +ems_ref +enclosures +health_state +href +id +name +overall_health_state +physical_chassis_id +physical_rack_id +type +uid_ems +Examples + + +To retrieve information about a specific physical storage system (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example: +GET /api/physical_storages/<storage_ID>?expand=resources&attributes=id,name + + +To retrieve information, such as canisters and physical disks that are associated with a specific physical storage system, use the ?expand=resources&attributes=<attribute_list> query parameters, for example: +GET /api/physical_storages/<storage_ID>?expand=resources&attributes=canisters,physical_disks + + +
+
+Retrieving Physical Switch Details +To retrieve information for all physical switches, use the following request URL: +GET /api/physical_switches +A JSON response with the following keys is returned. +actions (list of actions that can be used) +count (number of physical switches) +name (URI name) +pages (count of pages) +resources (list of URLs for each physical switch) +subcount (number of physical switches that were returned) +Examples + + +To retrieve all information about the physical switches, use the ?expand=resources query parameter, for example: +GET /api/physical_switches?expand=resources + + +To retrieve specific information about the physical switches (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example: +GET /api/physical_switches?expand=resources&attributes=id,name + + +To retrieve information such as ports on physical switches, use the ?expand=resources&attributes=<attribute_list> query parameters, for example: +GET /api/physical_switches?expand=resources&attributes=physical_network_ports + + +To retrieve information such as physical devices connected to physical switches, use the ?expand=resources&attributes=<attribute_list> query parameters, for example: +GET /api/physical_switches?expand=resources&attributes=connected_components + + +To retrieve information about only a specific physical switch, use the ?expand=resources&filter[]=name=<switch_name> query attributes on all physical switch resources, for example: +GET /api/physical_switches?expand=resources&filter[]=name=IO Module 02 + + +
+
+Retrieving Physical Switch Details by ID +To retrieve information for a specific physical switch, use the following request URL: +GET /api/physical_switches/<switch_ID> +A JSON response with the following keys is returned. +actions +allow_promiscuous +ems_id +forged_transmits +health_state +href +id +mac_changes +mtu +name +ports +power_state +shared +switch_uuid +type +uid_ems +Examples + + +To retrieve information about a specific physical switch (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example: +GET /api/physical_switches/<switch_ID>?expand=resources&attributes=id,name + + +To retrieve information such as physical devices that are connected to a specific physical switch, use the ?expand=resources&attributes=<attribute_list> query parameters, for example: +GET /api/physical_switches/<switch_ID>?expand=resources&attributes=connected_components + + +To retrieve information such as ports on a specific physical switch, use the ?expand=resources&attributes=<attribute_list> query parameters, for example: +GET /api/physical_switches/<switch_ID>?expand=resources&attributes=physical_network_ports + + +
+
+Performing physical switch actions +You can use the REST API to perform management tasks on a physical switch, such as restarting the switch. +Note: To perform actions on physical switch, you must create a basic authentication using your preferred tool or library, and enter your user name and password to access the CloudForms REST API. +
+Restarting a physical switch +To restart a specific switch, send a POST request using the following request URL and JSON request body. +POST /api/physical_switches/<switch_ID> +Request body: +{ + "action":"restart" +} +
+
+Performing an action on multiple physical switches +To perform an action on more than one physical switch, send a POST request using the following request URL and JSON request body. +POST /api/physical_switches +Request body: +{ + "action":"<action>", + "resources": [{ + "href":"<switch_ID>" + }, + { + "href":"<switch_ID>" + }] +} +
+
\ No newline at end of file diff --git a/physical_infra_provider_rest_api/l10n/es-ES/Author_Group.po b/physical_infra_provider_rest_api/l10n/es-ES/Author_Group.po index d546a04..f8a342c 100644 --- a/physical_infra_provider_rest_api/l10n/es-ES/Author_Group.po +++ b/physical_infra_provider_rest_api/l10n/es-ES/Author_Group.po @@ -2,7 +2,7 @@ msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2018-02-26 09:56+1000\n" +"POT-Creation-Date: 2018-11-22 19:42+1000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -10,7 +10,7 @@ msgstr "" "Last-Translator: trh01 \n" "Language-Team: Spanish\n" "Language: es\n" -"X-Generator: Zanata 4.4.3\n" +"X-Generator: Zanata 4.6.2\n" "Plural-Forms: nplurals=2; plural=(n != 1)\n" msgid "Red Hat CloudForms" diff --git a/physical_infra_provider_rest_api/l10n/es-ES/Revision_History.po b/physical_infra_provider_rest_api/l10n/es-ES/Revision_History.po index 31046fa..1eadace 100644 --- a/physical_infra_provider_rest_api/l10n/es-ES/Revision_History.po +++ b/physical_infra_provider_rest_api/l10n/es-ES/Revision_History.po @@ -2,7 +2,7 @@ msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2018-02-26 09:56+1000\n" +"POT-Creation-Date: 2018-11-22 19:42+1000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -10,7 +10,7 @@ msgstr "" "Last-Translator: trh01 \n" "Language-Team: Spanish\n" "Language: es\n" -"X-Generator: Zanata 4.4.3\n" +"X-Generator: Zanata 4.6.2\n" "Plural-Forms: nplurals=2; plural=(n != 1)\n" msgid "Revision History" diff --git a/physical_infra_provider_rest_api/l10n/es-ES/main.po b/physical_infra_provider_rest_api/l10n/es-ES/main.po index db1303a..c0676a0 100644 --- a/physical_infra_provider_rest_api/l10n/es-ES/main.po +++ b/physical_infra_provider_rest_api/l10n/es-ES/main.po @@ -1,17 +1,19 @@ # Sergio Ocón , 2018. #zanata +# edrh02 , 2018. #zanata +# myamamot , 2018. #zanata # trh01 , 2018. #zanata msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2018-02-26 09:56+1000\n" +"POT-Creation-Date: 2018-11-22 19:42+1000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"PO-Revision-Date: 2018-03-02 02:06+0000\n" -"Last-Translator: trh01 \n" +"PO-Revision-Date: 2018-12-05 08:17+0000\n" +"Last-Translator: edrh02 \n" "Language-Team: Spanish\n" "Language: es\n" -"X-Generator: Zanata 4.4.3\n" +"X-Generator: Zanata 4.6.2\n" "Plural-Forms: nplurals=2; plural=(n != 1)\n" msgid "Lenovo Physical Infrastructure Provider REST API" @@ -76,18 +78,6 @@ msgstr "" "API como usuario con permiso para acceder al API. El usuario predeterminado " "es admin y la contraseña es smartvm." -msgid "Use the following URL to access the CloudForms REST API:" -msgstr "Use esta URL para acceder al API REST de CloudForms:" - -msgid "<CloudForms_address>:<port>/api" -msgstr "<CloudForms_address>:<port>/api" - -msgid "For example:" -msgstr "Por ejemplo:" - -msgid "localhost:3000/api" -msgstr "localhost:3000/api" - msgid "Retrieving Provider Details" msgstr "Obtener detalles sobre el proveedor" @@ -96,8 +86,8 @@ msgid "" msgstr "" "Para obtener información de todos los proveedores, utilice la siguiente URL:" -msgid "GET <CloudForms_address>:<port>/api/providers" -msgstr "GET <CloudForms_address>:<port>/api/providers" +msgid "GET /api/providers" +msgstr "GET /api/providers" msgid "A JSON response with the following keys is returned." msgstr "Se devolverá una respuesta JSON con las siguientes llaves." @@ -106,9 +96,9 @@ msgid "" "actions (list of actions that can be used)\n" "count (total number of providers)\n" "name (URI name)\n" -"pages (count of pages)\n" +"pages (number of pages)\n" "resource (list of URLs for each provider that is managed by CloudForms)\n" -"subcount (number of providers returned)" +"subcount (number of providers that were returned)" msgstr "" "acciones (listado de acciones que se pueden usar)\n" "total (número total de proveedores)\n" @@ -128,8 +118,8 @@ msgstr "" "consulta ?expand=resources , como por " "ejemplo:" -msgid "GET localhost:3000/api/providers?expand=resources" -msgstr "GET localhost:3000/api/providers?expand=resources" +msgid "GET /api/providers?expand=resources" +msgstr "GET /api/providers?expand=resources" msgid "" "To retrieve a specific information about the providers (such as name and " @@ -140,10 +130,8 @@ msgstr "" "utilice el parámetro de consulta ?expand=" "resources , como por ejemplo:" -msgid "" -"GET localhost:3000/ api/providers?expand=resources&attributes=id,name" -msgstr "" -"GET localhost:3000/ api/providers?expand=resources&attributes=id,name" +msgid "GET /api/providers?expand=resources&attributes=id,name" +msgstr "GET /api/providers?expand=resources&attributes=id,name" msgid "" "To retrieve additional information about the providers (such as port, " @@ -156,11 +144,9 @@ msgstr "" "resources parámetros de consulta, como por ejemplo:" msgid "" -"GET localhost:3000/api/providers?expand=resources&attributes=" -"port,hostname,ipaddress" +"GET /api/providers?expand=resources&attributes=port,hostname,ipaddress" msgstr "" -"GET localhost:3000/api/providers?expand=resources&attributes=" -"port,hostname,ipaddress" +"GET /api/providers?expand=resources&attributes=port,hostname,ipaddress" msgid "" "To retrieve information about only Lenovo physical-infrastructure providers, " @@ -174,11 +160,11 @@ msgstr "" "recursos de proveedores, por ejemplo:" msgid "" -"GET localhost:3000/api/providers?expand=resources&filter[]=type=ManageIQ:" -":Providers::Lenovo::PhysicalInfraManager" +"GET /api/providers?expand=resources&filter[]=type=ManageIQ::Providers::" +"Lenovo::PhysicalInfraManager" msgstr "" -"GET localhost:3000/api/providers?expand=resources&filter[]=type=ManageIQ:" -":Providers::Lenovo::PhysicalInfraManager" +"GET /api/providers?expand=resources&filter[]=type=ManageIQ::Providers::" +"Lenovo::PhysicalInfraManager" msgid "Retrieving Provider Details by ID" msgstr "Obtener detalles del proveedor por ID" @@ -190,12 +176,8 @@ msgstr "" "Para obtener información de un proveedor específico, utilice la siguiente " "URL en donde <provider_ID> es el identificador único del proveedor:" -msgid "" -"GET <CloudForms_address>:<port>/api/providers/" -"<provider_ID>" -msgstr "" -"GET <CloudForms_address>:<port>/api/providers/" -"<provider_ID>" +msgid "GET /api/providers/<provider_ID>" +msgstr "GET /api/providers/<provider_ID>" msgid "" "href\n" @@ -236,11 +218,11 @@ msgstr "" "resources , por ejemplo:" msgid "" -"GET localhost:3000/api/providers/<provider_ID>?expand=" -"resources&attributes=id,name" +"GET /api/providers/<provider_ID>?expand=resources&attributes=" +"id,name" msgstr "" -"GET localhost:3000/api/providers/<provider_ID>?expand=" -"resources&attributes=id,name" +"GET /api/providers/<provider_ID>?expand=resources&attributes=" +"id,name" msgid "" "To retrieve additional information about the provider (such as port, " @@ -252,10 +234,10 @@ msgstr "" "role=\"strong\">?expand=resources, por ejemplo:" msgid "" -" GET localhost:3000/api/providers/<provider_ID>?expand=resources\n" +"GET /api/providers/<provider_ID>?expand=resources\n" "&attributes=port,hostname,ipaddress" msgstr "" -" GET localhost:3000/api/providers/<provider_ID>?expand=resources\n" +"GET /api/providers/<provider_ID>?expand=resources\n" "&attributes=port,hostname,ipaddress" msgid "Performing physical-infrastructure provider actions" @@ -290,8 +272,8 @@ msgstr "" "Para crear un proveedor de infraestructura física de Lenovo, realice una " "petición POST utilizando la siguiente URL y el cuerpo de petición JSON." -msgid "POST <CloudForms_address>:<port>/api/providers" -msgstr "POST <CloudForms_address>:<port>/api/providers" +msgid "POST /api/providers" +msgstr "POST /api/providers" msgid "Request body:" msgstr "Cuerpo de petición:" @@ -383,12 +365,8 @@ msgstr "Para eliminar un proveedor específico:" msgid "Send a DELETE request using the following request URL." msgstr "Envíe una petición DELETE utilizando el siguiente URL." -msgid "" -"DELETE <CloudForms_address>:<port>/api/providers/" -"<provider_ID>" -msgstr "" -"DELETE <CloudForms_address>:<port>/api/providers/" -"<provider_ID>" +msgid "DELETE /api/providers/<provider_ID>" +msgstr "DELETE /api/providers/<provider_ID>" msgid "" "Send a POST request using the following request URL and JSON request body." @@ -396,12 +374,8 @@ msgstr "" "Envíe una petición de POST utilizando la siguiente URL y el cuerpo de " "petición JSON." -msgid "" -"POST <CloudForms_address>:<port>/api/providers/" -"<provider_ID>" -msgstr "" -"POST <CloudForms_address>:<port>/api/providers/" -"<provider_ID>" +msgid "POST /api/providers/<provider_ID>" +msgstr "POST /api/providers/<provider_ID>" msgid "{\n" " \"action\":\"delete\"\n" @@ -452,23 +426,23 @@ msgstr "" "Para obtener detalles sobre todos los servidores físicos, utilice la " "siguiente URL:" -msgid "GET <CloudForms_address>:<port>/api/physical_servers" -msgstr "GET <CloudForms_address>:<port>/api/physical_servers" +msgid "GET /api/physical_servers" +msgstr "GET /api/physical_servers" msgid "" "actions (list of actions that can be used)\n" -"count (count of the physical servers)\n" +"count (number of physical servers)\n" "name (URI name)\n" -"pages (count of pages)\n" -"resource (list of URLs of the each physical servers)\n" -"subcount (count of the physical servers returned)" +"pages (number of pages)\n" +"resource (list of URLs for each physical server)\n" +"subcount (number of physical servers that were returned)" msgstr "" "acciones (listado de acciones que se pueden usar)\n" -"total (número total de proveedores)\n" +"total (número de servidores físicos)\n" "nombre (nombre de URI)\n" "páginas (total de páginas)\n" -"recurso (listado de URL para cada proveedor administradas por CloudForms)\n" -"subtotal (número de proveedores devueltos)" +"recurso (listado de URL para cada servidor físico)\n" +"subtotal (número de servidores físicos devueltos)" msgid "" "To retrieve all information about the physical servers, use the ?expand=resources parámetro de " "consulta, por ejemplo:" -msgid "GET localhost:3000/api/physical_servers?expand=resources" -msgstr "GET localhost:3000/api/physical_servers?expand=resources" +msgid "GET /api/physical_servers?expand=resources" +msgstr "GET /api/physical_servers?expand=resources" msgid "" -"To retrieve a specific information about the physical servers (such as name " +"To retrieve specific information about the physical servers (such as name " "and ID), use the ?expand=resources&attributes=" "<attribute_list> query parameters, for example:" msgstr "" -"Para obtener un dato específico sobre los servidores físicos (como el nombre " -"y ID), utilice parámetros de consulta ?expand=" -"resources&attributes=<attribute_list> , por ejemplo:" +"Para obtener información específica sobre los servidores físicos (como el " +"nombre y la ID), use los ?expand=" +"resources&attributes=<attribute_list> parámetros de " +"consulta, por ejemplo:" + +msgid "GET /api/physical_servers?expand=resources&attributes=id,name" +msgstr "GET /api/physical_servers?expand=resources&attributes=id,name" msgid "" -"GET localhost:3000/api/physical_servers?expand=resources&attributes=" -"id,name" +"To retrieve information such as firmware, networks, guest devices, and asset " +"details associated with physical servers, use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" msgstr "" -"GET localhost:3000/api/physical_servers?expand=resources&attributes=" -"id,name" +"Para obtener información como firmware, redes, dispositivos invitados y " +"detalles de activos relacionados con servidores físicos, use los ?expand=resources&attributes=<attribute_list> parámetros de consulta, por ejemplo:" msgid "" -"To retrieve specific information about the physical servers (such as " -"firmware, networks, guest devices, and asset details), use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +"GET /api/physical_servers?expand=resources&attributes=hardware." +"firmwares,hardware.networks,hardware.guest_devices,hardware.assets_details" +msgstr "" +"GET /api/physical_servers?expand=resources&attributes=hardware." +"firmwares,hardware.networks,hardware.guest_devices,hardware.assets_details" + +msgid "" +"To retrieve information such as network adapters and storage adapters in " +"physical servers, use the ?expand=" +"resources&attributes=<attribute_list> query parameters, " +"for example:" +msgstr "" +"Para obtener información, como adaptadores de redes y adaptadores de " +"almacenamiento en servidores físicos, use los ?expand=resources&attributes=<attribute_list> parámetros de consulta, por ejemplo:" + +msgid "" +"GET /api/physical_servers?expand=resources&attributes=guest_devices." +"with_ethernet_type,guest_devices.with_storage_type" +msgstr "" +"GET /api/physical_servers?expand=resources&attributes=guest_devices." +"with_ethernet_type,guest_devices.with_storage_type" + +msgid "" +"To retrieve information such as switches connected to physical servers, use " +"the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" msgstr "" -"Para obtener un dato específico sobre los servidores físicos (como firmware, " -"redes, dispositivos huéspedes y detalles de recursos), utilice parámetros " -"de consulta ?expand=resources&attributes=" -"<attribute_list> , por ejemplo:" +"Para obtener información, como switches conectados a servidores físicos, use " +"los ?expand=resources&attributes=" +"<attribute_list> parámetros de consulta, por ejemplo:" msgid "" -"GET localhost:3000/api/physical_servers?expand=resources&attributes= " -"hardware.firmwares,hardware.networks,hardware.guest_devices,hardware." -"assets_details" +"GET /api/physical_servers?expand=resources&attributes=physical_switches" msgstr "" -"GET localhost:3000/api/physical_servers?expand=resources&attributes= " -"hardware.firmwares,hardware.networks,hardware.guest_devices,hardware." -"assets_details" +"GET /api/physical_servers?expand=resources&attributes=physical_switches" msgid "" "To retrieve information about only a specific physical server, use the " @@ -529,11 +530,11 @@ msgstr "" "recursos de servidores físicos, por ejemplo:" msgid "" -"GET localhost:3000/api/physical_servers?expand=resources&filter[]=name=" -"Server1-20127X5462" +"GET /api/physical_servers?expand=resources&filter[]=name=Server1-" +"20127X5462" msgstr "" -"GET localhost:3000/api/physical_servers?expand=resources&filter[]=name=" -"Server1-20127X5462" +"GET /api/physical_servers?expand=resources&filter[]=name=Server1-" +"20127X5462" msgid "Retrieving Physical Server Details by ID" msgstr "Obtener detalles del servidor físico por ID" @@ -545,12 +546,8 @@ msgstr "" "Para obtener información de un servidor físico específico, utilice la " "siguiente URL:" -msgid "" -"GET <CloudForms_address>:<port>/api/physical_servers/" -"<server_ID>" -msgstr "" -"GET <CloudForms_address>:<port>/api/physical_servers/" -"<server_ID>" +msgid "GET /api/physical_servers/<server_ID>" +msgstr "GET /api/physical_servers/<server_ID>" msgid "" "actions\n" @@ -596,43 +593,77 @@ msgstr "" "vendor" msgid "" -"To retrieve a specific information about a specific physical server (such as " -"name and ID), use the ?expand=" -"resources&attributes=<attribute_list> query parameters, " -"for example:" +"To retrieve information about a specific physical server (such as name and " +"ID), use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" msgstr "" -"Para obtener un dato específico sobre un servidor físico específico (como el " -"nombre y ID), utilice ?expand=" -"resources&attributes=<attribute_list> parámetros de " -"consulta, por ejemplo:" +"Para obtener información sobre un servidor físico específico (como el nombre " +"y la ID), utilice ?expand=resources&attributes=" +"<attribute_list> parámetros de consulta, por ejemplo:" msgid "" -"GET localhost:3000/api/physical_servers/<server_ID>?expand=" -"resources&attributes=id,name" +"GET /api/physical_servers/<server_ID>?expand=resources&attributes=" +"id,name" msgstr "" -"GET localhost:3000/api/physical_servers/<server_ID>?expand=" -"resources&attributes=id,name" +"GET /api/physical_servers/<server_ID>?expand=resources&attributes=" +"id,name" msgid "" -"To retrieve a specific information about a specific physical server (such as " -"firmware, networks, guest devices, and asset details), use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +"To retrieve information such as firmware, networks, guest devices, and asset " +"details for a specific server, use the ?expand=" +"resources&attributes=<attribute_list> query parameters, " +"for example:" msgstr "" -"Para obtener un dato específico sobre un servidor físico específico (como " -"firmware, redes, dispositivos huéspedes y detalles de recursos), utilice " -"?expand=resources&attributes=" -"<attribute_list> parámetros de consulta, por ejemplo:" +"Para obtener información como firmware, redes, dispositivos invitados y " +"detalles de activos para un servidor específico, use los ?expand=resources&attributes=<attribute_list> parámetros de consulta, por ejemplo:" msgid "" -" GET localhost:3000/api/physical_servers/<server_ID>?expand=resources\n" +"GET /api/physical_servers/<server_ID>?expand=resources\n" "&attributes=hardware.firmwares,hardware.networks,hardware." "guest_devices,hardware.assets_details" msgstr "" -" GET localhost:3000/api/physical_servers/<server_ID>?expand=resources\n" +"GET /api/physical_servers/<server_ID>?expand=resources\n" "&attributes=hardware.firmwares,hardware.networks,hardware." "guest_devices,hardware.assets_details" +msgid "" +"To retrieve information such as switches that are connected to a specific " +"server, use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"Para obtener información, como switches conectados a un servidor específico, " +"use los ?expand=resources&attributes=" +"<attribute_list> parámetros de consulta, por ejemplo:" + +msgid "" +"GET /api/physical_servers/<server_ID>?expand=resources&attributes=" +"physical_switches" +msgstr "" +"GET /api/physical_servers/<server_ID>?expand=resources&attributes=" +"physical_switches" + +msgid "" +"To retrieve information such as network adapters and storage adapters in a " +"specific physical server, use the ?expand=" +"resources&attributes=<attribute_list> query parameters, " +"for example:" +msgstr "" +"Para obtener información, como adaptadores de redes y adaptadores de " +"almacenamiento en un servidor físico específico, use los ?expand=resources&attributes=<attribute_list> parámetros de consulta, por ejemplo:" + +msgid "" +"GET /api/physical_servers/<server_ID>?expand=resources&attributes=" +"guest_devices.with_ethernet_type,guest_devices.with_storage_type,hardware." +"physical_network_ports" +msgstr "" +"GET /api/physical_servers/<server_ID>?expand=resources&attributes=" +"guest_devices.with_ethernet_type,guest_devices.with_storage_type,hardware." +"physical_network_ports" + msgid "Performing physical server actions" msgstr "Realizar acciones en servidores físicos" @@ -665,12 +696,8 @@ msgstr "" "Para encender un servidor físico específico, envíe una petición de POST " "utilizando la siguiente URL y el cuerpo de petición JSON." -msgid "" -"POST <CloudForms_address>:<port>/api/physical_servers/" -"<server_ID>" -msgstr "" -"POST <CloudForms_address>:<port>/api/physical_servers/" -"<server_ID>" +msgid "POST /api/physical_servers/<server_ID>" +msgstr "POST /api/physical_servers/<server_ID>" msgid "{\n" " \"action\":\"power_on\"\n" @@ -771,14 +798,14 @@ msgid "Performing an action on multiple physical servers" msgstr "Realizar una acción en varios servidores físicos" msgid "" -"To perform an action on more than one physical severs, send a POST request " +"To perform an action on more than one physical server, send a POST request " "using the following request URL and JSON request body." msgstr "" -"Para realizar una acción en más de un servidor físico, envíe una petición de " -"POST utilizando la siguiente URL y el cuerpo de petición JSON." +"Para realizar una acción en más de un servidor físico, envíe una solicitud " +"POST utilizando la siguiente URL de solicitud y el cuerpo de solicitud JSON." -msgid "POST <CloudForms_address>:<port>/api/physical_servers" -msgstr "POST <CloudForms_address>:<port>/api/physical_servers" +msgid "POST /api/physical_servers" +msgstr "POST /api/physical_servers" msgid "" "{\n" @@ -800,3 +827,795 @@ msgstr "" " \"href\":\"<server_ID>\"\n" " }]\n" "}" + +msgid "Retrieving Physical Chassis Details" +msgstr "Obtener detalles sobre el chasis físico" + +msgid "" +"To retrieve information for all physical chassis, use the following request " +"URL:" +msgstr "" +"Para obtener información sobre todos los chasis físicos, use la siguiente " +"URL de solicitud:" + +msgid "GET /api/physical_chassis" +msgstr "GET /api/physical_chassis" + +msgid "" +"actions (list of actions that can be used)\n" +"count (number of physical chassis)\n" +"name (URI name)\n" +"pages (number of pages)\n" +"resources (list of URLs for each physical chassis)\n" +"subcount (number of physical chassis that were returned)" +msgstr "" +"acciones (listado de acciones que se pueden usar)\n" +"total (número de chasis físicos)\n" +"nombre (nombre de URI)\n" +"páginas (total de páginas)\n" +"recursos (listado de URL para cada chasis físico)\n" +"subtotal (número de chasis físicos devueltos)" + +msgid "" +"To retrieve all information about the physical chassis, use the ?expand=resources query parameter, for example:" +msgstr "" +"Para obtener toda la información sobre los chasis físicos, use el ?expand=resources parámetro de consulta, por " +"ejemplo:" + +msgid "GET /api/physical_chassis?expand=resources" +msgstr "GET /api/physical_chassis?expand=resources" + +msgid "" +"To retrieve specific information about the physical chassis (such as name " +"and ID), use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"Para obtener información específica sobre los chasis físicos (como el nombre " +"y la ID), use los ?expand=resources&attributes=" +"<attribute_list> parámetros de consulta, por ejemplo:" + +msgid "GET /api/physical_chassis?expand=resources&attributes=id,name" +msgstr "GET /api/physical_chassis?expand=resources&attributes=id,name" + +msgid "" +"To retrieve information such as the switches, storage systems, and servers " +"in a chassis, use the ?expand=" +"resources&attributes=<attribute_list> query parameters, " +"for example:" +msgstr "" +"Para obtener información, como switches, sistemas de almacenamiento y " +"servidores en un chasis, use los ?expand=" +"resources&attributes=<attribute_list> parámetros de " +"consulta, por ejemplo:" + +msgid "" +"GET /api/physical_chassis?expand=resources&attributes=" +"physical_servers,physical_storages,hardware.connected_physical_switches" +msgstr "" +"GET /api/physical_chassis?expand=resources&attributes=" +"physical_servers,physical_storages,hardware.connected_physical_switches" + +msgid "" +"To retrieve information about only a specific physical chassis, use the " +"?expand=resources&filter[]=name=" +"<chassis_name> query attributes on all physical chassis " +"resources, for example:" +msgstr "" +"Para obtener información solo sobre un chasis físico específico, use los " +"?expand=resources&filter[]=name=" +"<server_name> atributos de consulta en todos los recursos " +"de chasis físicos, por ejemplo:" + +msgid "" +"GET /api/physical_chassis?expand=resources&filter[]=name=" +"SN%23Y034BG16E060" +msgstr "" +"GET /api/physical_chassis?expand=resources&filter[]=name=" +"SN%23Y034BG16E060" + +msgid "Retrieving Physical Chassis Details by ID" +msgstr "Obtener detalles del chasis físico por ID" + +msgid "" +"To retrieve information for a specific physical chassis, use the following " +"request URL:" +msgstr "" +"Para obtener información para un chasis físico específico, use la siguiente " +"URL de solicitud:" + +msgid "GET /api/physical_chassis/<chassis_ID>" +msgstr "GET /api/physical_chassis/<chassis_ID>" + +msgid "" +"href\n" +"id\n" +"ems_id\n" +"uid_ems\n" +"ems_ref\n" +"physical_rack_id\n" +"name\n" +"vendor\n" +"type\n" +"location_led_state\n" +"health_state\n" +"overall_health_state\n" +"management_module_slot_count\n" +"switch_slot_count\n" +"fan_slot_count\n" +"blade_slot_count\n" +"powersupply_slot_count\n" +"actions" +msgstr "" +"href\n" +"id\n" +"ems_id\n" +"uid_ems\n" +"ems_ref\n" +"physical_rack_id\n" +"name\n" +"vendor\n" +"type\n" +"location_led_state\n" +"health_state\n" +"overall_health_state\n" +"management_module_slot_count\n" +"switch_slot_count\n" +"fan_slot_count\n" +"blade_slot_count\n" +"powersupply_slot_count\n" +"actions" + +msgid "" +"To retrieve information about a specific physical chassis (such as name and " +"ID), use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"Para obtener información sobre un chasis físico específico (como el nombre y " +"la ID), use ?expand=resources&attributes=" +"<attribute_list> parámetros de consulta, por ejemplo:" + +msgid "" +"GET /api/physical_chassis/<chassis_ID>?expand=resources&attributes=" +"id,name" +msgstr "" +"GET /api/physical_chassis/<chassis_ID>?expand=resources&attributes=" +"id,name" + +msgid "" +"To retrieve information, such as the switches, storage systems, and servers " +"that are in a specific physical chassis, use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" +"Para obtener información, como switches, sistemas de almacenamiento y " +"servidores que se encuentran en un chasis físico específico, use los " +"?expand=resources&attributes=" +"<attribute_list> parámetros de consulta, por ejemplo:" + +msgid "" +"GET /api/physical_chassis/<chassis_ID>?expand=resources&attributes=" +"physical_servers,physical_storages,hardware.connected_physical_switches" +msgstr "" +"GET /api/physical_chassis/<chassis_ID>?expand=resources&attributes=" +"physical_servers,physical_storages,hardware.connected_physical_switches" + +msgid "Performing physical chassis actions" +msgstr "Realizar acciones en chasis físicos" + +msgid "" +"You can use the REST API to perform management tasks on a physical chassis, " +"such as changing the location LED state." +msgstr "" +"La API REST se puede utilizar para realizar tareas de gestión en un chasis " +"físico, como modificar la ubicación del estado del LED. " + +msgid "" +"Note: To perform actions on physical " +"chassis, you must create a basic authentication using your preferred tool or " +"library, and enter your user name and password to access the CloudForms REST " +"API." +msgstr "" +"Nota: Para realizar acciones en chasis " +"físicos, debe crear una autenticación básica mediante su herramienta o " +"biblioteca preferida e ingresar su nombre de usuario y contraseña para " +"acceder a la API REST de CloudForms." + +msgid "Changing the location LED state on a physical chassis to blinking" +msgstr "" +"Modificar la ubicación del estado del LED en un chasis físico a parpadeo" + +msgid "" +"To change the location LED state to blinking on a specific chassis, send a " +"POST request using the following request URL and JSON request body." +msgstr "" +"Para modificar la ubicación del estado del LED a parpadeo en un chasis " +"específico, envíe una solicitud POST utilizando la siguiente URL de " +"solicitud y el cuerpo de solicitud JSON." + +msgid "POST /api/physical_chassis/<chassis_ID>" +msgstr "POST /api/physical_chassis/<chassis_ID>" + +msgid "Performing an action on multiple physical chassis" +msgstr "Realizar una acción en varios chasis físicos" + +msgid "" +"To perform an action on more than one physical chassis, send a POST request " +"using the following request URL and JSON request body." +msgstr "" +"Para realizar una acción en más de un chasis físico, envíe una solicitud " +"POST utilizando la siguiente URL de solicitud y el cuerpo de solicitud JSON." + +msgid "POST /api/physical_chassis" +msgstr "POST /api/physical_chassis" + +msgid "" +"{\n" +" \"action\":\"<action>\",\n" +" \"resources\": [{\n" +" \"href\":\"<chassis_ID>\"\n" +" },\n" +" {\n" +" \"href\":\"<chassis_ID>\"\n" +" }]\n" +"}" +msgstr "" +"{\n" +" \"action\":\"<action>\",\n" +" \"resources\": [{\n" +" \"href\":\"<chassis_ID>\"\n" +" },\n" +" {\n" +" \"href\":\"<chassis_ID>\"\n" +" }]\n" +"}" + +msgid "Retrieving Physical Rack Details" +msgstr "Obtener detalles sobre el rack físico" + +msgid "" +"To retrieve information for all physical racks, use the following request " +"URL:" +msgstr "" +"Para obtener información sobre todos los racks físicos, use la siguiente URL " +"de solicitud:" + +msgid "GET /api/physical_racks" +msgstr "GET /api/physical_racks" + +msgid "" +"actions (list of actions that can be used)\n" +"count (number of physical racks)\n" +"name (URI name)\n" +"pages (number of pages)\n" +"resources (list of URLs for each physical rack)\n" +"subcount (number of physical racks that were returned)" +msgstr "" +"acciones (listado de acciones que se pueden usar)\n" +"total (número de racks físicos)\n" +"nombre (nombre de URI)\n" +"páginas (total de páginas)\n" +"recursos (listado de URL para cada rack físico)\n" +"subtotal (número de racks físicos devueltos)" + +msgid "" +"To retrieve all information about the physical racks, use the ?expand=resources query parameter, for example:" +msgstr "" +"Para obtener toda la información sobre los racks físicos, use el ?expand=resources parámetro de consulta, por " +"ejemplo:" + +msgid "GET /api/physical_racks?expand=resources" +msgstr "GET /api/physical_racks?expand=resources" + +msgid "" +"To retrieve specific information about the physical racks (such as name and " +"ID), use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"Para obtener información específica sobre los racks físicos (como el nombre " +"y la ID), use los ?expand=resources&attributes=" +"<attribute_list> parámetros de consulta, por ejemplo:" + +msgid "GET /api/physical_racks?expand=resources&attributes=id,name" +msgstr "GET /api/physical_racks?expand=resources&attributes=id,name" + +msgid "" +"To retrieve information about only a specific physical rack, use the " +"?expand=resources&filter[]=name=" +"<rack_name> query attributes on all physical rack " +"resources, for example:" +msgstr "" +"Para obtener información solo sobre un rack físico específico, use los " +"?expand=resources&filter[]=name=" +"<server_name> atributos de consulta en todos los recursos " +"de rack físicos, por ejemplo:" + +msgid "GET /api/physical_racks?expand=resources&filter[]=name=rack-2" +msgstr "GET /api/physical_racks?expand=resources&filter[]=name=rack-2" + +msgid "Retrieving Physical Rack Details by ID" +msgstr "Obtener detalles del rack físico por ID" + +msgid "" +"To retrieve information for a specific physical rack, use the following " +"request URL:" +msgstr "" +"Para obtener información de un rack físico específico, use la siguiente URL " +"de solicitud:" + +msgid "GET /api/physical_racks/<rack_ID>" +msgstr "GET /api/physical_racks/<rack_ID>" + +msgid "actions\n" +"ems_id\n" +"ems_ref\n" +"href\n" +"id\n" +"name\n" +"uid_ems" +msgstr "actions\n" +"ems_id\n" +"ems_ref\n" +"href\n" +"id\n" +"name\n" +"uid_ems" + +msgid "" +"To retrieve information about a specific physical rack (such as name and " +"ID), use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"Para obtener información sobre un rack físico específico (como el nombre y " +"la ID), use los ?expand=resources&attributes=" +"<attribute_list> parámetros de consulta, por ejemplo:" + +msgid "" +"GET /api/physical_racks/<rack_ID>?expand=resources&attributes=" +"id,name" +msgstr "" +"GET /api/physical_racks/<rack_ID>?expand=resources&attributes=" +"id,name" + +msgid "Retrieving Physical Storage Details" +msgstr "Obtener detalles sobre el almacenamiento físico" + +msgid "" +"To retrieve information for all physical storage systems, use the following " +"request URL:" +msgstr "" +"Para obtener información sobre todos los sistemas de almacenamiento físico, " +"use la siguiente URL de solicitud:" + +msgid "GET /api/physical_storages" +msgstr "GET /api/physical_storages" + +msgid "" +"actions (list of actions that can be used)\n" +"count (number of physical storage systems)\n" +"name (URI name)\n" +"pages (number of pages)\n" +"resources (list of URLs for each physical storage system)\n" +"subcount (number of physical storage systems that were returned)" +msgstr "" +"acciones (listado de acciones que se pueden usar)\n" +"total (número de sistemas de almacenamiento físico)\n" +"nombre (nombre de URI)\n" +"páginas (total de páginas)\n" +"recursos (listado de URL para cada sistema de almacenamiento físico)\n" +"subtotal (número de sistemas de almacenamiento físico devueltos)" + +msgid "" +"To retrieve all information about the physical storage systems, use the " +"?expand=resources query parameter, for " +"example:" +msgstr "" +"Para obtener toda la información sobre los sistemas de almacenamiento " +"físico, use el ?expand=resources " +"parámetro de consulta, por ejemplo:" + +msgid "GET /api/physical_storages?expand=resources" +msgstr "GET /api/physical_storages?expand=resources" + +msgid "" +"To retrieve specific information about the physical storage systems (such as " +"name and ID), use the ?expand=" +"resources&attributes=<attribute_list> query parameters, " +"for example:" +msgstr "" +"Para obtener información específica sobre los sistemas de almacenamiento " +"físico (como el nombre y la ID), use los ?expand=" +"resources&attributes=<attribute_list> parámetros de " +"consulta, por ejemplo:" + +msgid "GET /api/physical_storages?expand=resources&attributes=id,name" +msgstr "GET /api/physical_storages?expand=resources&attributes=id,name" + +msgid "" +"To retrieve information such as canisters and physical disks associated with " +"physical storage systems, use the ?expand=" +"resources&attributes=<attribute_list> query parameters, " +"for example:" +msgstr "" +"Para obtener información, como recipientes y discos físicos relacionados con " +"los sistemas de almacenamiento físico, use los ?expand=resources&attributes=<attribute_list> parámetros de consulta, por ejemplo:" + +msgid "" +"GET /api/physical_storages?expand=resources&attributes=" +"canisters,physical_disks" +msgstr "" +"GET /api/physical_storages?expand=resources&attributes=" +"canisters,physical_disks" + +msgid "" +"To retrieve information about only a specific physical storage system, use " +"the ?expand=resources&filter[]=name=" +"<storage_name> query attributes on all physical storage " +"resources, for example:" +msgstr "" +"Para obtener información solo sobre un sistema de almacenamiento físico " +"específico, use los ?expand=resources&filter[]=" +"name=<server_name> atributos de consulta en todos los " +"recursos de almacenamiento físico, por ejemplo:" + +msgid "" +"GET /api/physical_storages?expand=resources&filter[]=name=SeagateV1-" +"S3200-DM" +msgstr "" +"GET /api/physical_storages?expand=resources&filter[]=name=SeagateV1-" +"S3200-DM" + +msgid "Retrieving Physical Storage Details by ID" +msgstr "Obtener detalles sobre el almacenamiento físico por ID" + +msgid "" +"To retrieve information for a specific physical storage system, use the " +"following request URL:" +msgstr "" +"Para obtener información sobre un sistema de almacenamiento físico " +"específico, use la siguiente URL de solicitud:" + +msgid "GET /api/physical_storages/<storage_ID>" +msgstr "GET /api/physical_storages/<storage_ID>" + +msgid "" +"access_state\n" +"actions\n" +"canister_slots\n" +"drive_bays\n" +"ems_id\n" +"ems_ref\n" +"enclosures\n" +"health_state\n" +"href\n" +"id\n" +"name\n" +"overall_health_state\n" +"physical_chassis_id\n" +"physical_rack_id\n" +"type\n" +"uid_ems" +msgstr "" +"access_state\n" +"actions\n" +"canister_slots\n" +"drive_bays\n" +"ems_id\n" +"ems_ref\n" +"enclosures\n" +"health_state\n" +"href\n" +"id\n" +"name\n" +"overall_health_state\n" +"physical_chassis_id\n" +"physical_rack_id\n" +"type\n" +"uid_ems" + +msgid "" +"To retrieve information about a specific physical storage system (such as " +"name and ID), use the ?expand=" +"resources&attributes=<attribute_list> query parameters, " +"for example:" +msgstr "" +"Para obtener información sobre un sistema de almacenamiento físico " +"específico (como el nombre y la ID), use los ?expand=resources&attributes=<attribute_list> parámetros de consulta, por ejemplo:" + +msgid "" +"GET /api/physical_storages/<storage_ID>?expand=" +"resources&attributes=id,name" +msgstr "" +"GET /api/physical_storages/<storage_ID>?expand=" +"resources&attributes=id,name" + +msgid "" +"To retrieve information, such as canisters and physical disks that are " +"associated with a specific physical storage system, use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" +"Para obtener información, como recipientes y discos físicos relacionados con " +"un sistema de almacenamiento físico específico, use los ?expand=resources&attributes=<attribute_list> parámetros de consulta, por ejemplo:" + +msgid "" +"GET /api/physical_storages/<storage_ID>?expand=" +"resources&attributes=canisters,physical_disks" +msgstr "" +"GET /api/physical_storages/<storage_ID>?expand=" +"resources&attributes=canisters,physical_disks" + +msgid "Retrieving Physical Switch Details" +msgstr "Obtener detalles sobre el switch físico" + +msgid "" +"To retrieve information for all physical switches, use the following request " +"URL:" +msgstr "" +"Para obtener información sobre todos los switches físicos, use la siguiente " +"URL de solicitud:" + +msgid "GET /api/physical_switches" +msgstr "GET /api/physical_switches" + +msgid "" +"actions (list of actions that can be used)\n" +"count (number of physical switches)\n" +"name (URI name)\n" +"pages (count of pages)\n" +"resources (list of URLs for each physical switch)\n" +"subcount (number of physical switches that were returned)" +msgstr "" +"acciones (listado de acciones que se pueden usar)\n" +"total (número de switches físicos)\n" +"nombre (nombre de URI)\n" +"páginas (total de páginas)\n" +"recursos (listado de URL para cada switch físico)\n" +"subtotal (número de switches físicos devueltos)" + +msgid "" +"To retrieve all information about the physical switches, use the ?expand=resources query parameter, for example:" +msgstr "" +"Para obtener toda la información sobre los switches físicos, use el " +"?expand=resources parámetro de " +"consulta, por ejemplo:" + +msgid "GET /api/physical_switches?expand=resources" +msgstr "GET /api/physical_switches?expand=resources" + +msgid "" +"To retrieve specific information about the physical switches (such as name " +"and ID), use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"Para obtener información específica sobre los switches físicos (como el " +"nombre y la ID), use los ?expand=" +"resources&attributes=<attribute_list> parámetros de " +"consulta, por ejemplo:" + +msgid "GET /api/physical_switches?expand=resources&attributes=id,name" +msgstr "GET /api/physical_switches?expand=resources&attributes=id,name" + +msgid "" +"To retrieve information such as ports on physical switches, use the " +"?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"Para obtener información, como puertos en switches físicos, use los " +"?expand=resources&attributes=" +"<attribute_list> parámetros de consulta, por ejemplo:" + +msgid "" +"GET /api/physical_switches?expand=resources&attributes=" +"physical_network_ports" +msgstr "" +"GET /api/physical_switches?expand=resources&attributes=" +"physical_network_ports" + +msgid "" +"To retrieve information such as physical devices connected to physical " +"switches, use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"Para obtener información, como dispositivos físicos conectados a switches " +"físicos, use los ?expand=resources&attributes=" +"<attribute_list> parámetros de consulta, por ejemplo:" + +msgid "" +"GET /api/physical_switches?expand=resources&attributes=" +"connected_components" +msgstr "" +"GET /api/physical_switches?expand=resources&attributes=" +"connected_components" + +msgid "" +"To retrieve information about only a specific physical switch, use the " +"?expand=resources&filter[]=name=" +"<switch_name> query attributes on all physical switch " +"resources, for example:" +msgstr "" +"Para obtener información solo sobre un switch físico específico, use los " +"?expand=resources&filter[]=name=" +"<server_name> atributos de consulta en todos los recursos " +"de switch físicos, por ejemplo:" + +msgid "" +"GET /api/physical_switches?expand=resources&filter[]=name=IO Module 02" +msgstr "" +"GET /api/physical_switches?expand=resources&filter[]=name=IO Module 02" + +msgid "Retrieving Physical Switch Details by ID" +msgstr "Obtener detalles sobre el switch físico por ID" + +msgid "" +"To retrieve information for a specific physical switch, use the following " +"request URL:" +msgstr "" +"Para obtener información de un switch físico específico, use la siguiente " +"URL de solicitud:" + +msgid "GET /api/physical_switches/<switch_ID>" +msgstr "GET /api/physical_switches/<switch_ID>" + +msgid "" +"actions\n" +"allow_promiscuous\n" +"ems_id\n" +"forged_transmits\n" +"health_state\n" +"href\n" +"id\n" +"mac_changes\n" +"mtu\n" +"name\n" +"ports\n" +"power_state\n" +"shared\n" +"switch_uuid\n" +"type\n" +"uid_ems" +msgstr "" +"actions\n" +"allow_promiscuous\n" +"ems_id\n" +"forged_transmits\n" +"health_state\n" +"href\n" +"id\n" +"mac_changes\n" +"mtu\n" +"name\n" +"ports\n" +"power_state\n" +"shared\n" +"switch_uuid\n" +"type\n" +"uid_ems" + +msgid "" +"To retrieve information about a specific physical switch (such as name and " +"ID), use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"Para obtener información sobre un switch físico específico (como el nombre y " +"la ID), use los ?expand=resources&attributes=" +"<attribute_list> parámetros de consulta, por ejemplo:" + +msgid "" +"GET /api/physical_switches/<switch_ID>?expand=resources&attributes=" +"id,name" +msgstr "" +"GET /api/physical_switches/<switch_ID>?expand=resources&attributes=" +"id,name" + +msgid "" +"To retrieve information such as physical devices that are connected to a " +"specific physical switch, use the ?expand=" +"resources&attributes=<attribute_list> query parameters, " +"for example:" +msgstr "" +"Para obtener información, como dispositivos físicos conectados a un switch " +"físico específico, use los ?expand=" +"resources&attributes=<attribute_list> parámetros de " +"consulta, por ejemplo:" + +msgid "" +"GET /api/physical_switches/<switch_ID>?expand=resources&attributes=" +"connected_components" +msgstr "" +"GET /api/physical_switches/<switch_ID>?expand=resources&attributes=" +"connected_components" + +msgid "" +"To retrieve information such as ports on a specific physical switch, use the " +"?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"Para obtener información, como puertos en un switch físico específico, use " +"los ?expand=resources&attributes=" +"<attribute_list> parámetros de consulta, por ejemplo:" + +msgid "" +"GET /api/physical_switches/<switch_ID>?expand=resources&attributes=" +"physical_network_ports" +msgstr "" +"GET /api/physical_switches/<switch_ID>?expand=resources&attributes=" +"physical_network_ports" + +msgid "Performing physical switch actions" +msgstr "Realizar acciones de switch físico" + +msgid "" +"You can use the REST API to perform management tasks on a physical switch, " +"such as restarting the switch." +msgstr "" +"La API REST se puede utilizar para realizar tareas de gestión en un switch " +"físico, como reiniciar el switch. " + +msgid "" +"Note: To perform actions on physical " +"switch, you must create a basic authentication using your preferred tool or " +"library, and enter your user name and password to access the CloudForms REST " +"API." +msgstr "" +"Nota: Para realizar acciones en un " +"switch físico, debe crear una autenticación básica mediante su herramienta o " +"biblioteca preferida e ingresar su nombre de usuario y contraseña para " +"acceder a la API REST de CloudForms." + +msgid "Restarting a physical switch" +msgstr "Reiniciar un switch físico" + +msgid "" +"To restart a specific switch, send a POST request using the following " +"request URL and JSON request body." +msgstr "" +"Para reiniciar un switch específico, envíe una solicitud POST utilizando la " +"siguiente URL de solicitud y el cuerpo de solicitud JSON." + +msgid "POST /api/physical_switches/<switch_ID>" +msgstr "POST /api/physical_switches/<switch_ID>" + +msgid "Performing an action on multiple physical switches" +msgstr "Realizar una acción en varios switches físicos" + +msgid "" +"To perform an action on more than one physical switch, send a POST request " +"using the following request URL and JSON request body." +msgstr "" +"Para realizar una acción en más de un switch físico, envíe una solicitud " +"POST utilizando la siguiente URL de solicitud y el cuerpo de solicitud JSON." + +msgid "POST /api/physical_switches" +msgstr "POST /api/physical_switches" + +msgid "" +"{\n" +" \"action\":\"<action>\",\n" +" \"resources\": [{\n" +" \"href\":\"<switch_ID>\"\n" +" },\n" +" {\n" +" \"href\":\"<switch_ID>\"\n" +" }]\n" +"}" +msgstr "" +"{\n" +" \"action\":\"<action>\",\n" +" \"resources\": [{\n" +" \"href\":\"<switch_ID>\"\n" +" },\n" +" {\n" +" \"href\":\"<switch_ID>\"\n" +" }]\n" +"}" diff --git a/physical_infra_provider_rest_api/l10n/ja-JP/Author_Group.po b/physical_infra_provider_rest_api/l10n/ja-JP/Author_Group.po index bbce356..0d7ee30 100644 --- a/physical_infra_provider_rest_api/l10n/ja-JP/Author_Group.po +++ b/physical_infra_provider_rest_api/l10n/ja-JP/Author_Group.po @@ -2,7 +2,7 @@ msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2018-02-26 09:56+1000\n" +"POT-Creation-Date: 2018-11-22 19:42+1000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -10,7 +10,7 @@ msgstr "" "Last-Translator: tkuroda \n" "Language-Team: Japanese\n" "Language: ja\n" -"X-Generator: Zanata 4.4.3\n" +"X-Generator: Zanata 4.6.2\n" "Plural-Forms: nplurals=1; plural=0\n" msgid "Red Hat CloudForms" diff --git a/physical_infra_provider_rest_api/l10n/ja-JP/Revision_History.po b/physical_infra_provider_rest_api/l10n/ja-JP/Revision_History.po index 6266637..addd997 100644 --- a/physical_infra_provider_rest_api/l10n/ja-JP/Revision_History.po +++ b/physical_infra_provider_rest_api/l10n/ja-JP/Revision_History.po @@ -2,7 +2,7 @@ msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2018-02-26 09:56+1000\n" +"POT-Creation-Date: 2018-11-22 19:42+1000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -10,7 +10,7 @@ msgstr "" "Last-Translator: tkuroda \n" "Language-Team: Japanese\n" "Language: ja\n" -"X-Generator: Zanata 4.4.3\n" +"X-Generator: Zanata 4.6.2\n" "Plural-Forms: nplurals=1; plural=0\n" msgid "Revision History" diff --git a/physical_infra_provider_rest_api/l10n/ja-JP/main.po b/physical_infra_provider_rest_api/l10n/ja-JP/main.po index eba847d..2645f84 100644 --- a/physical_infra_provider_rest_api/l10n/ja-JP/main.po +++ b/physical_infra_provider_rest_api/l10n/ja-JP/main.po @@ -2,15 +2,15 @@ msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2018-02-26 09:56+1000\n" +"POT-Creation-Date: 2018-11-22 19:42+1000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"PO-Revision-Date: 2018-02-26 11:41+0000\n" +"PO-Revision-Date: 2018-12-10 11:19+0000\n" "Last-Translator: tkuroda \n" "Language-Team: Japanese\n" "Language: ja\n" -"X-Generator: Zanata 4.4.3\n" +"X-Generator: Zanata 4.6.2\n" "Plural-Forms: nplurals=1; plural=0\n" msgid "Lenovo Physical Infrastructure Provider REST API" @@ -67,18 +67,6 @@ msgstr "" "REST API を使用するためには、API へのアクセス権限が与えられたユーザーとして、CloudForms Management Engine " "API にログインする必要があります。デフォルトのユーザーは admin で、パスワードは smartvm です。" -msgid "Use the following URL to access the CloudForms REST API:" -msgstr "以下の URL を使って、CloudForms REST API にアクセスします。" - -msgid "<CloudForms_address>:<port>/api" -msgstr "<CloudForms_address>:<port>/api" - -msgid "For example:" -msgstr "例:" - -msgid "localhost:3000/api" -msgstr "localhost:3000/api" - msgid "Retrieving Provider Details" msgstr "プロバイダー情報の取得" @@ -86,8 +74,8 @@ msgid "" "To retrieve information for all providers, use the following request URL:" msgstr "すべてのプロバイダーに関する情報を取得するには、以下のリクエスト URL を使用します。" -msgid "GET <CloudForms_address>:<port>/api/providers" -msgstr "GET <CloudForms_address>:<port>/api/providers" +msgid "GET /api/providers" +msgstr "GET /api/providers" msgid "A JSON response with the following keys is returned." msgstr "以下のキーを含んだ JSON 応答が返されます。" @@ -96,9 +84,9 @@ msgid "" "actions (list of actions that can be used)\n" "count (total number of providers)\n" "name (URI name)\n" -"pages (count of pages)\n" +"pages (number of pages)\n" "resource (list of URLs for each provider that is managed by CloudForms)\n" -"subcount (number of providers returned)" +"subcount (number of providers that were returned)" msgstr "" "actions (使用することのできるアクションのリスト)\n" "count (プロバイダーの総数)\n" @@ -117,8 +105,8 @@ msgstr "" "プロバイダーに関するすべての情報を取得するには、?expand=resources クエリーパラメーターを使用します。以下に例を示します。" -msgid "GET localhost:3000/api/providers?expand=resources" -msgstr "GET localhost:3000/api/providers?expand=resources" +msgid "GET /api/providers?expand=resources" +msgstr "GET /api/providers?expand=resources" msgid "" "To retrieve a specific information about the providers (such as name and " @@ -129,10 +117,8 @@ msgstr "" "resources&attributes=<attribute_list> " "クエリーパラメーターを使用します。以下に例を示します。" -msgid "" -"GET localhost:3000/ api/providers?expand=resources&attributes=id,name" -msgstr "" -"GET localhost:3000/ api/providers?expand=resources&attributes=id,name" +msgid "GET /api/providers?expand=resources&attributes=id,name" +msgstr "GET /api/providers?expand=resources&attributes=id,name" msgid "" "To retrieve additional information about the providers (such as port, " @@ -145,11 +131,9 @@ msgstr "" "emphasis> クエリーパラメーターを使用します。以下に例を示します。" msgid "" -"GET localhost:3000/api/providers?expand=resources&attributes=" -"port,hostname,ipaddress" +"GET /api/providers?expand=resources&attributes=port,hostname,ipaddress" msgstr "" -"GET localhost:3000/api/providers?expand=resources&attributes=" -"port,hostname,ipaddress" +"GET /api/providers?expand=resources&attributes=port,hostname,ipaddress" msgid "" "To retrieve information about only Lenovo physical-infrastructure providers, " @@ -162,11 +146,11 @@ msgstr "" "emphasis> 属性を使用します。以下に例を示します。" msgid "" -"GET localhost:3000/api/providers?expand=resources&filter[]=type=ManageIQ:" -":Providers::Lenovo::PhysicalInfraManager" +"GET /api/providers?expand=resources&filter[]=type=ManageIQ::Providers::" +"Lenovo::PhysicalInfraManager" msgstr "" -"GET localhost:3000/api/providers?expand=resources&filter[]=type=ManageIQ:" -":Providers::Lenovo::PhysicalInfraManager" +"GET /api/providers?expand=resources&filter[]=type=ManageIQ::Providers::" +"Lenovo::PhysicalInfraManager" msgid "Retrieving Provider Details by ID" msgstr "ID によるプロバイダー情報の取得" @@ -178,12 +162,8 @@ msgstr "" "特定のプロバイダーに関する情報を取得するには、以下のリクエスト URL を使用します。ここで、<provider_ID> " "はプロバイダーに固有の識別子です。" -msgid "" -"GET <CloudForms_address>:<port>/api/providers/" -"<provider_ID>" -msgstr "" -"GET <CloudForms_address>:<port>/api/providers/" -"<provider_ID>" +msgid "GET /api/providers/<provider_ID>" +msgstr "GET /api/providers/<provider_ID>" msgid "" "href\n" @@ -219,30 +199,31 @@ msgid "" "use the ?attributes=<attribute_list> query parameters, for example:" msgstr "" -"プロバイダーに関する特定の情報を取得するには (名前および ID 等)、?attributes=" -"<attribute_list> クエリーパラメーターを使用します。以下に例を示します。" +"特定のプロバイダーに関する特定の情報を取得するには (名前および ID 等)、?expand=" +"resources&attributes=<attribute_list> " +"クエリーパラメーターを使用します。以下に例を示します。" msgid "" -"GET localhost:3000/api/providers/<provider_ID>?expand=" -"resources&attributes=id,name" +"GET /api/providers/<provider_ID>?expand=resources&attributes=" +"id,name" msgstr "" -"GET localhost:3000/api/providers/<provider_ID>?expand=" -"resources&attributes=id,name" +"GET /api/providers/<provider_ID>?expand=resources&attributes=" +"id,name" msgid "" "To retrieve additional information about the provider (such as port, " "hostname, and IP address), use the ?attributes=" "<attribute_list> query parameters, for example:" msgstr "" -"プロバイダーに関する情報をさらに取得するには (ポート、ホスト名、および IP アドレス等)、?attributes=<attribute_list> " -"クエリーパラメーターを使用します。以下に例を示します。" +"特定のプロバイダーに関する情報をさらに取得するには (ポート、ホスト名、および IP アドレス等)、?expand=resources&attributes=<attribute_list> クエリーパラメーターを使用します。以下に例を示します。" msgid "" -" GET localhost:3000/api/providers/<provider_ID>?expand=resources\n" +"GET /api/providers/<provider_ID>?expand=resources\n" "&attributes=port,hostname,ipaddress" msgstr "" -" GET localhost:3000/api/providers/<provider_ID>?expand=resources\n" +"GET /api/providers/<provider_ID>?expand=resources\n" "&attributes=port,hostname,ipaddress" msgid "Performing physical-infrastructure provider actions" @@ -261,7 +242,7 @@ msgid "" msgstr "" "メモ: " "物理インフラストラクチャープロバイダーに関する操作を実施するには、任意のツールまたはライブラリーを用いて基本認証を作成し、REST API " -"を使用する際には CloudForms インスタンス用のユーザー名およびパスワードを使用する必要があります。" +"を使用する際に CloudForms インスタンス用のユーザー名およびパスワードを使用する必要があります。" msgid "Creating a Lenovo physical-infrastructure provider" msgstr "Lenovo 物理インフラストラクチャープロバイダーの作成" @@ -273,8 +254,8 @@ msgstr "" "Lenovo 物理インフラストラクチャープロバイダーを作成するには、以下のリクエスト URL および JSON リクエストボディーを使用して POST " "リクエストを送信します。" -msgid "POST <CloudForms_address>:<port>/api/providers" -msgstr "POST <CloudForms_address>:<port>/api/providers" +msgid "POST /api/providers" +msgstr "POST /api/providers" msgid "Request body:" msgstr "リクエストボディー" @@ -363,23 +344,15 @@ msgstr "特定のプロバイダーを削除する方法:" msgid "Send a DELETE request using the following request URL." msgstr "以下のリクエスト URL を使用して DELETE リクエストを送信する。" -msgid "" -"DELETE <CloudForms_address>:<port>/api/providers/" -"<provider_ID>" -msgstr "" -"DELETE <CloudForms_address>:<port>/api/providers/" -"<provider_ID>" +msgid "DELETE /api/providers/<provider_ID>" +msgstr "DELETE /api/providers/<provider_ID>" msgid "" "Send a POST request using the following request URL and JSON request body." msgstr "以下のリクエスト URL および JSON リクエストボディーを使用して POST リクエストを送信する。" -msgid "" -"POST <CloudForms_address>:<port>/api/providers/" -"<provider_ID>" -msgstr "" -"POST <CloudForms_address>:<port>/api/providers/" -"<provider_ID>" +msgid "POST /api/providers/<provider_ID>" +msgstr "POST /api/providers/<provider_ID>" msgid "{\n" " \"action\":\"delete\"\n" @@ -427,16 +400,16 @@ msgid "" "URL:" msgstr "すべての物理サーバーに関する情報を取得するには、以下のリクエスト URL を使用します。" -msgid "GET <CloudForms_address>:<port>/api/physical_servers" -msgstr "GET <CloudForms_address>:<port>/api/physical_servers" +msgid "GET /api/physical_servers" +msgstr "GET /api/physical_servers" msgid "" "actions (list of actions that can be used)\n" -"count (count of the physical servers)\n" +"count (number of physical servers)\n" "name (URI name)\n" -"pages (count of pages)\n" -"resource (list of URLs of the each physical servers)\n" -"subcount (count of the physical servers returned)" +"pages (number of pages)\n" +"resource (list of URLs for each physical server)\n" +"subcount (number of physical servers that were returned)" msgstr "" "actions (使用することのできるアクションのリスト)\n" "count (物理サーバーの数)\n" @@ -452,11 +425,11 @@ msgstr "" "物理サーバーに関するすべての情報を取得するには、?expand=resources クエリーパラメーターを使用します。以下に例を示します。" -msgid "GET localhost:3000/api/physical_servers?expand=resources" -msgstr "GET localhost:3000/api/physical_servers?expand=resources" +msgid "GET /api/physical_servers?expand=resources" +msgstr "GET /api/physical_servers?expand=resources" msgid "" -"To retrieve a specific information about the physical servers (such as name " +"To retrieve specific information about the physical servers (such as name " "and ID), use the ?expand=resources&attributes=" "<attribute_list> query parameters, for example:" msgstr "" @@ -464,31 +437,56 @@ msgstr "" "resources&attributes=<attribute_list> " "クエリーパラメーターを使用します。以下に例を示します。" -msgid "" -"GET localhost:3000/api/physical_servers?expand=resources&attributes=" -"id,name" -msgstr "" -"GET localhost:3000/api/physical_servers?expand=resources&attributes=" -"id,name" +msgid "GET /api/physical_servers?expand=resources&attributes=id,name" +msgstr "GET /api/physical_servers?expand=resources&attributes=id,name" msgid "" -"To retrieve specific information about the physical servers (such as " -"firmware, networks, guest devices, and asset details), use the ?expand=resources&attributes=<attribute_list>?expand=resources&attributes=<attribute_list> query parameters, for example:" msgstr "" -"物理サーバーに関する情報をさらに取得するには (ファームウェア、ネットワーク、ゲストデバイス、およびアセット詳細など)、?expand=resources&attributes=<attribute_list> クエリーパラメーターを使用します。以下に例を示します。" msgid "" -"GET localhost:3000/api/physical_servers?expand=resources&attributes= " -"hardware.firmwares,hardware.networks,hardware.guest_devices,hardware." -"assets_details" +"GET /api/physical_servers?expand=resources&attributes=hardware." +"firmwares,hardware.networks,hardware.guest_devices,hardware.assets_details" +msgstr "" +"GET /api/physical_servers?expand=resources&attributes=hardware." +"firmwares,hardware.networks,hardware.guest_devices,hardware.assets_details" + +msgid "" +"To retrieve information such as network adapters and storage adapters in " +"physical servers, use the ?expand=" +"resources&attributes=<attribute_list> query parameters, " +"for example:" +msgstr "" +"物理サーバーのネットワークアダプターおよびストレージアダプター等の情報を取得するには、?expand=" +"resources&attributes=<attribute_list> " +"クエリーパラメーターを使用します。以下に例を示します。" + +msgid "" +"GET /api/physical_servers?expand=resources&attributes=guest_devices." +"with_ethernet_type,guest_devices.with_storage_type" +msgstr "" +"GET /api/physical_servers?expand=resources&attributes=guest_devices." +"with_ethernet_type,guest_devices.with_storage_type" + +msgid "" +"To retrieve information such as switches connected to physical servers, use " +"the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"物理サーバーに接続されたスイッチ等の情報を取得するには、?expand=" +"resources&attributes=<attribute_list> " +"クエリーパラメーターを使用します。以下に例を示します。" + +msgid "" +"GET /api/physical_servers?expand=resources&attributes=physical_switches" msgstr "" -"GET localhost:3000/api/physical_servers?expand=resources&attributes= " -"hardware.firmwares,hardware.networks,hardware.guest_devices,hardware." -"assets_details" +"GET /api/physical_servers?expand=resources&attributes=physical_switches" msgid "" "To retrieve information about only a specific physical server, use the " @@ -501,11 +499,11 @@ msgstr "" "emphasis> クエリー属性を使用します。以下に例を示します。" msgid "" -"GET localhost:3000/api/physical_servers?expand=resources&filter[]=name=" -"Server1-20127X5462" +"GET /api/physical_servers?expand=resources&filter[]=name=Server1-" +"20127X5462" msgstr "" -"GET localhost:3000/api/physical_servers?expand=resources&filter[]=name=" -"Server1-20127X5462" +"GET /api/physical_servers?expand=resources&filter[]=name=Server1-" +"20127X5462" msgid "Retrieving Physical Server Details by ID" msgstr "ID による物理サーバー情報の取得" @@ -515,12 +513,8 @@ msgid "" "request URL:" msgstr "特定の物理サーバーに関する情報を取得するには、以下のリクエスト URL を使用します。" -msgid "" -"GET <CloudForms_address>:<port>/api/physical_servers/" -"<server_ID>" -msgstr "" -"GET <CloudForms_address>:<port>/api/physical_servers/" -"<server_ID>" +msgid "GET /api/physical_servers/<server_ID>" +msgstr "GET /api/physical_servers/<server_ID>" msgid "" "actions\n" @@ -566,41 +560,75 @@ msgstr "" "vendor" msgid "" -"To retrieve a specific information about a specific physical server (such as " -"name and ID), use the ?expand=" -"resources&attributes=<attribute_list> query parameters, " -"for example:" +"To retrieve information about a specific physical server (such as name and " +"ID), use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" msgstr "" -"物理サーバーに関する特定の情報を取得するには (名前および ID 等)、?expand=" +"特定の物理サーバーに関する特定の情報を取得するには (名前および ID 等)、?expand=" "resources&attributes=<attribute_list> " "クエリーパラメーターを使用します。以下に例を示します。" msgid "" -"GET localhost:3000/api/physical_servers/<server_ID>?expand=" -"resources&attributes=id,name" +"GET /api/physical_servers/<server_ID>?expand=resources&attributes=" +"id,name" msgstr "" -"GET localhost:3000/api/physical_servers/<server_ID>?expand=" -"resources&attributes=id,name" +"GET /api/physical_servers/<server_ID>?expand=resources&attributes=" +"id,name" msgid "" -"To retrieve a specific information about a specific physical server (such as " -"firmware, networks, guest devices, and asset details), use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +"To retrieve information such as firmware, networks, guest devices, and asset " +"details for a specific server, use the ?expand=" +"resources&attributes=<attribute_list> query parameters, " +"for example:" msgstr "" -"物理サーバーに関する情報をさらに取得するには (ファームウェア、ネットワーク、ゲストデバイス、およびアセット詳細など)、?expand=resources&attributes=<attribute_list> クエリーパラメーターを使用します。以下に例を示します。" msgid "" -" GET localhost:3000/api/physical_servers/<server_ID>?expand=resources\n" +"GET /api/physical_servers/<server_ID>?expand=resources\n" "&attributes=hardware.firmwares,hardware.networks,hardware." "guest_devices,hardware.assets_details" msgstr "" -" GET localhost:3000/api/physical_servers/<server_ID>?expand=resources\n" +"GET /api/physical_servers/<server_ID>?expand=resources\n" "&attributes=hardware.firmwares,hardware.networks,hardware." "guest_devices,hardware.assets_details" +msgid "" +"To retrieve information such as switches that are connected to a specific " +"server, use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"特定のサーバーに接続されたスイッチ等の情報を取得するには、?expand=" +"resources&attributes=<attribute_list> " +"クエリーパラメーターを使用します。以下に例を示します。" + +msgid "" +"GET /api/physical_servers/<server_ID>?expand=resources&attributes=" +"physical_switches" +msgstr "" +"GET /api/physical_servers/<server_ID>?expand=resources&attributes=" +"physical_switches" + +msgid "" +"To retrieve information such as network adapters and storage adapters in a " +"specific physical server, use the ?expand=" +"resources&attributes=<attribute_list> query parameters, " +"for example:" +msgstr "" +"特定物理サーバーのネットワークアダプターおよびストレージアダプター等の情報を取得するには、?expand=resources&attributes=<attribute_list> クエリーパラメーターを使用します。以下に例を示します。" + +msgid "" +"GET /api/physical_servers/<server_ID>?expand=resources&attributes=" +"guest_devices.with_ethernet_type,guest_devices.with_storage_type,hardware." +"physical_network_ports" +msgstr "" +"GET /api/physical_servers/<server_ID>?expand=resources&attributes=" +"guest_devices.with_ethernet_type,guest_devices.with_storage_type,hardware." +"physical_network_ports" + msgid "Performing physical server actions" msgstr "物理サーバーに関する操作の実施" @@ -617,8 +645,8 @@ msgid "" "API." msgstr "" "メモ: " -"物理サーバーに関する操作を実施するには、任意のツールまたはライブラリーを用いて基本認証を作成し、REST API を使用する際には CloudForms " -"インスタンス用のユーザー名およびパスワードを使用する必要があります。" +"物理サーバーに関する操作を実施するには、任意のツールまたはライブラリーを用いて基本認証を作成し、ユーザー名およびパスワードを入力して " +"CloudForms REST API にアクセスする必要があります。" msgid "Powering on a physical server" msgstr "物理サーバーの電源オン" @@ -629,12 +657,8 @@ msgid "" msgstr "" "特定の物理サーバーの電源をオンにするには、以下のリクエスト URL および JSON リクエストボディーを使用して POST リクエストを送信します。" -msgid "" -"POST <CloudForms_address>:<port>/api/physical_servers/" -"<server_ID>" -msgstr "" -"POST <CloudForms_address>:<port>/api/physical_servers/" -"<server_ID>" +msgid "POST /api/physical_servers/<server_ID>" +msgstr "POST /api/physical_servers/<server_ID>" msgid "{\n" " \"action\":\"power_on\"\n" @@ -731,14 +755,14 @@ msgid "Performing an action on multiple physical servers" msgstr "複数の物理サーバーに関する操作の実施" msgid "" -"To perform an action on more than one physical severs, send a POST request " +"To perform an action on more than one physical server, send a POST request " "using the following request URL and JSON request body." msgstr "" "複数の物理サーバーに関する操作を実施するには、以下のリクエスト URL および JSON リクエストボディーを使用して POST " "リクエストを送信します。" -msgid "POST <CloudForms_address>:<port>/api/physical_servers" -msgstr "POST <CloudForms_address>:<port>/api/physical_servers" +msgid "POST /api/physical_servers" +msgstr "POST /api/physical_servers" msgid "" "{\n" @@ -760,3 +784,754 @@ msgstr "" " \"href\":\"<server_ID>\"\n" " }]\n" "}" + +msgid "Retrieving Physical Chassis Details" +msgstr "物理シャーシ情報の取得" + +msgid "" +"To retrieve information for all physical chassis, use the following request " +"URL:" +msgstr "すべての物理シャーシに関する情報を取得するには、以下のリクエスト URL を使用します。" + +msgid "GET /api/physical_chassis" +msgstr "GET /api/physical_chassis" + +msgid "" +"actions (list of actions that can be used)\n" +"count (number of physical chassis)\n" +"name (URI name)\n" +"pages (number of pages)\n" +"resources (list of URLs for each physical chassis)\n" +"subcount (number of physical chassis that were returned)" +msgstr "" +"actions (使用することのできるアクションのリスト)\n" +"count (物理シャーシの数)\n" +"name (URI 名)\n" +"pages (ページ数)\n" +"resources (各物理シャーシの URL のリスト)\n" +"subcount (返された物理シャーシの数)" + +msgid "" +"To retrieve all information about the physical chassis, use the ?expand=resources query parameter, for example:" +msgstr "" +"物理シャーシに関するすべての情報を取得するには、?expand=resources クエリーパラメーターを使用します。以下に例を示します。" + +msgid "GET /api/physical_chassis?expand=resources" +msgstr "GET /api/physical_chassis?expand=resources" + +msgid "" +"To retrieve specific information about the physical chassis (such as name " +"and ID), use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"物理シャーシに関する特定の情報を取得するには (名前および ID 等)、?expand=" +"resources&attributes=<attribute_list> " +"クエリーパラメーターを使用します。以下に例を示します。" + +msgid "GET /api/physical_chassis?expand=resources&attributes=id,name" +msgstr "GET /api/physical_chassis?expand=resources&attributes=id,name" + +msgid "" +"To retrieve information such as the switches, storage systems, and servers " +"in a chassis, use the ?expand=" +"resources&attributes=<attribute_list> query parameters, " +"for example:" +msgstr "" +"シャーシのスイッチ、ストレージシステム、およびサーバー等の情報を取得するには、?expand=" +"resources&attributes=<attribute_list> " +"クエリーパラメーターを使用します。以下に例を示します。" + +msgid "" +"GET /api/physical_chassis?expand=resources&attributes=" +"physical_servers,physical_storages,hardware.connected_physical_switches" +msgstr "" +"GET /api/physical_chassis?expand=resources&attributes=" +"physical_servers,physical_storages,hardware.connected_physical_switches" + +msgid "" +"To retrieve information about only a specific physical chassis, use the " +"?expand=resources&filter[]=name=" +"<chassis_name> query attributes on all physical chassis " +"resources, for example:" +msgstr "" +"特定の物理シャーシに関する情報だけを取得するには、すべての物理シャーシリソースに対して ?expand=resources&filter[]=name=<chassis_name> クエリー属性を使用します。以下に例を示します。" + +msgid "" +"GET /api/physical_chassis?expand=resources&filter[]=name=" +"SN%23Y034BG16E060" +msgstr "" +"GET /api/physical_chassis?expand=resources&filter[]=name=" +"SN%23Y034BG16E060" + +msgid "Retrieving Physical Chassis Details by ID" +msgstr "ID による物理シャーシ情報の取得" + +msgid "" +"To retrieve information for a specific physical chassis, use the following " +"request URL:" +msgstr "特定の物理シャーシに関する情報を取得するには、以下のリクエスト URL を使用します。" + +msgid "GET /api/physical_chassis/<chassis_ID>" +msgstr "GET /api/physical_chassis/<chassis_ID>" + +msgid "" +"href\n" +"id\n" +"ems_id\n" +"uid_ems\n" +"ems_ref\n" +"physical_rack_id\n" +"name\n" +"vendor\n" +"type\n" +"location_led_state\n" +"health_state\n" +"overall_health_state\n" +"management_module_slot_count\n" +"switch_slot_count\n" +"fan_slot_count\n" +"blade_slot_count\n" +"powersupply_slot_count\n" +"actions" +msgstr "" +"href\n" +"id\n" +"ems_id\n" +"uid_ems\n" +"ems_ref\n" +"physical_rack_id\n" +"name\n" +"vendor\n" +"type\n" +"location_led_state\n" +"health_state\n" +"overall_health_state\n" +"management_module_slot_count\n" +"switch_slot_count\n" +"fan_slot_count\n" +"blade_slot_count\n" +"powersupply_slot_count\n" +"actions" + +msgid "" +"To retrieve information about a specific physical chassis (such as name and " +"ID), use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"特定の物理シャーシに関する特定の情報を取得するには (名前および ID 等)、?expand=" +"resources&attributes=<attribute_list> " +"クエリーパラメーターを使用します。以下に例を示します。" + +msgid "" +"GET /api/physical_chassis/<chassis_ID>?expand=resources&attributes=" +"id,name" +msgstr "" +"GET /api/physical_chassis/<chassis_ID>?expand=resources&attributes=" +"id,name" + +msgid "" +"To retrieve information, such as the switches, storage systems, and servers " +"that are in a specific physical chassis, use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" +"特定物理シャーシのスイッチ、ストレージシステム、およびサーバー等の情報を取得するには、?expand=" +"resources&attributes=<attribute_list> " +"クエリーパラメーターを使用します。以下に例を示します。" + +msgid "" +"GET /api/physical_chassis/<chassis_ID>?expand=resources&attributes=" +"physical_servers,physical_storages,hardware.connected_physical_switches" +msgstr "" +"GET /api/physical_chassis/<chassis_ID>?expand=resources&attributes=" +"physical_servers,physical_storages,hardware.connected_physical_switches" + +msgid "Performing physical chassis actions" +msgstr "物理シャーシに関する操作の実施" + +msgid "" +"You can use the REST API to perform management tasks on a physical chassis, " +"such as changing the location LED state." +msgstr "REST API を使用して、物理シャーシのロケーション LED の状態変更などの管理タスクを実施することができます。" + +msgid "" +"Note: To perform actions on physical " +"chassis, you must create a basic authentication using your preferred tool or " +"library, and enter your user name and password to access the CloudForms REST " +"API." +msgstr "" +"メモ: " +"物理シャーシに関する操作を実施するには、任意のツールまたはライブラリーを用いて基本認証を作成し、ユーザー名およびパスワードを入力して " +"CloudForms REST API にアクセスする必要があります。" + +msgid "Changing the location LED state on a physical chassis to blinking" +msgstr "物理シャーシロケーション LED 状態の点滅への変更" + +msgid "" +"To change the location LED state to blinking on a specific chassis, send a " +"POST request using the following request URL and JSON request body." +msgstr "" +"特定のシャーシについてロケーション LED の状態を点滅に変更するには、以下のリクエスト URL および JSON リクエストボディーを使用して " +"POST リクエストを送信します。" + +msgid "POST /api/physical_chassis/<chassis_ID>" +msgstr "POST /api/physical_chassis/<chassis_ID>" + +msgid "Performing an action on multiple physical chassis" +msgstr "複数の物理シャーシに関する操作の実施" + +msgid "" +"To perform an action on more than one physical chassis, send a POST request " +"using the following request URL and JSON request body." +msgstr "" +"複数の物理シャーシに関する操作を実施するには、以下のリクエスト URL および JSON リクエストボディーを使用して POST " +"リクエストを送信します。" + +msgid "POST /api/physical_chassis" +msgstr "POST /api/physical_chassis" + +msgid "" +"{\n" +" \"action\":\"<action>\",\n" +" \"resources\": [{\n" +" \"href\":\"<chassis_ID>\"\n" +" },\n" +" {\n" +" \"href\":\"<chassis_ID>\"\n" +" }]\n" +"}" +msgstr "" +"{\n" +" \"action\":\"<action>\",\n" +" \"resources\": [{\n" +" \"href\":\"<chassis_ID>\"\n" +" },\n" +" {\n" +" \"href\":\"<chassis_ID>\"\n" +" }]\n" +"}" + +msgid "Retrieving Physical Rack Details" +msgstr "物理ラック情報の取得" + +msgid "" +"To retrieve information for all physical racks, use the following request " +"URL:" +msgstr "すべての物理ラックに関する情報を取得するには、以下のリクエスト URL を使用します。" + +msgid "GET /api/physical_racks" +msgstr "GET /api/physical_racks" + +msgid "" +"actions (list of actions that can be used)\n" +"count (number of physical racks)\n" +"name (URI name)\n" +"pages (number of pages)\n" +"resources (list of URLs for each physical rack)\n" +"subcount (number of physical racks that were returned)" +msgstr "" +"actions (使用することのできるアクションのリスト)\n" +"count (物理ラックの数)\n" +"name (URI 名)\n" +"pages (ページ数)\n" +"resources (各物理ラックの URL のリスト)\n" +"subcount (返された物理ラックの数)" + +msgid "" +"To retrieve all information about the physical racks, use the ?expand=resources query parameter, for example:" +msgstr "" +"物理ラックに関するすべての情報を取得するには、?expand=resources クエリーパラメーターを使用します。以下に例を示します。" + +msgid "GET /api/physical_racks?expand=resources" +msgstr "GET /api/physical_racks?expand=resources" + +msgid "" +"To retrieve specific information about the physical racks (such as name and " +"ID), use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"物理ラックに関する特定の情報を取得するには (名前および ID 等)、?expand=" +"resources&attributes=<attribute_list> " +"クエリーパラメーターを使用します。以下に例を示します。" + +msgid "GET /api/physical_racks?expand=resources&attributes=id,name" +msgstr "GET /api/physical_racks?expand=resources&attributes=id,name" + +msgid "" +"To retrieve information about only a specific physical rack, use the " +"?expand=resources&filter[]=name=" +"<rack_name> query attributes on all physical rack " +"resources, for example:" +msgstr "" +"特定の物理ラックに関する情報だけを取得するには、すべての物理ラックリソースに対して ?expand=" +"resources&filter[]=name=<rack_name> " +"クエリー属性を使用します。以下に例を示します。" + +msgid "GET /api/physical_racks?expand=resources&filter[]=name=rack-2" +msgstr "GET /api/physical_racks?expand=resources&filter[]=name=rack-2" + +msgid "Retrieving Physical Rack Details by ID" +msgstr "ID による物理ラック情報の取得" + +msgid "" +"To retrieve information for a specific physical rack, use the following " +"request URL:" +msgstr "特定の物理ラックに関する情報を取得するには、以下のリクエスト URL を使用します。" + +msgid "GET /api/physical_racks/<rack_ID>" +msgstr "GET /api/physical_racks/<rack_ID>" + +msgid "actions\n" +"ems_id\n" +"ems_ref\n" +"href\n" +"id\n" +"name\n" +"uid_ems" +msgstr "actions\n" +"ems_id\n" +"ems_ref\n" +"href\n" +"id\n" +"name\n" +"uid_ems" + +msgid "" +"To retrieve information about a specific physical rack (such as name and " +"ID), use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"特定の物理ラックに関する特定の情報を取得するには (名前および ID 等)、?expand=" +"resources&attributes=<attribute_list> " +"クエリーパラメーターを使用します。以下に例を示します。" + +msgid "" +"GET /api/physical_racks/<rack_ID>?expand=resources&attributes=" +"id,name" +msgstr "" +"GET /api/physical_racks/<rack_ID>?expand=resources&attributes=" +"id,name" + +msgid "Retrieving Physical Storage Details" +msgstr "物理ストレージ情報の取得" + +msgid "" +"To retrieve information for all physical storage systems, use the following " +"request URL:" +msgstr "すべての物理ストレージシステムに関する情報を取得するには、以下のリクエスト URL を使用します。" + +msgid "GET /api/physical_storages" +msgstr "GET /api/physical_storages" + +msgid "" +"actions (list of actions that can be used)\n" +"count (number of physical storage systems)\n" +"name (URI name)\n" +"pages (number of pages)\n" +"resources (list of URLs for each physical storage system)\n" +"subcount (number of physical storage systems that were returned)" +msgstr "" +"actions (使用することのできるアクションのリスト)\n" +"count (物理ストレージシステムの数)\n" +"name (URI 名)\n" +"pages (ページ数)\n" +"resources (各物理ストレージシステムの URL のリスト)\n" +"subcount (返された物理ストレージシステムの数)" + +msgid "" +"To retrieve all information about the physical storage systems, use the " +"?expand=resources query parameter, for " +"example:" +msgstr "" +"物理ストレージシステムに関するすべての情報を取得するには、?expand=resources クエリーパラメーターを使用します。以下に例を示します。" + +msgid "GET /api/physical_storages?expand=resources" +msgstr "GET /api/physical_storages?expand=resources" + +msgid "" +"To retrieve specific information about the physical storage systems (such as " +"name and ID), use the ?expand=" +"resources&attributes=<attribute_list> query parameters, " +"for example:" +msgstr "" +"物理ストレージシステムに関する特定の情報を取得するには (名前および ID 等)、?expand=" +"resources&attributes=<attribute_list> " +"クエリーパラメーターを使用します。以下に例を示します。" + +msgid "GET /api/physical_storages?expand=resources&attributes=id,name" +msgstr "GET /api/physical_storages?expand=resources&attributes=id,name" + +msgid "" +"To retrieve information such as canisters and physical disks associated with " +"physical storage systems, use the ?expand=" +"resources&attributes=<attribute_list> query parameters, " +"for example:" +msgstr "" +"物理ストレージシステムに関するキャニスターおよび物理ディスク等の情報を取得するには、?expand=" +"resources&attributes=<attribute_list> " +"クエリーパラメーターを使用します。以下に例を示します。" + +msgid "" +"GET /api/physical_storages?expand=resources&attributes=" +"canisters,physical_disks" +msgstr "" +"GET /api/physical_storages?expand=resources&attributes=" +"canisters,physical_disks" + +msgid "" +"To retrieve information about only a specific physical storage system, use " +"the ?expand=resources&filter[]=name=" +"<storage_name> query attributes on all physical storage " +"resources, for example:" +msgstr "" +"特定の物理ストレージシステムに関する情報だけを取得するには、すべての物理ストレージリソースに対して ?expand=resources&filter[]=name=<storage_name> クエリー属性を使用します。以下に例を示します。" + +msgid "" +"GET /api/physical_storages?expand=resources&filter[]=name=SeagateV1-" +"S3200-DM" +msgstr "" +"GET /api/physical_storages?expand=resources&filter[]=name=SeagateV1-" +"S3200-DM" + +msgid "Retrieving Physical Storage Details by ID" +msgstr "ID による物理ストレージ情報の取得" + +msgid "" +"To retrieve information for a specific physical storage system, use the " +"following request URL:" +msgstr "特定の物理ストレージシステムに関する情報を取得するには、以下のリクエスト URL を使用します。" + +msgid "GET /api/physical_storages/<storage_ID>" +msgstr "GET /api/physical_storages/<storage_ID>" + +msgid "" +"access_state\n" +"actions\n" +"canister_slots\n" +"drive_bays\n" +"ems_id\n" +"ems_ref\n" +"enclosures\n" +"health_state\n" +"href\n" +"id\n" +"name\n" +"overall_health_state\n" +"physical_chassis_id\n" +"physical_rack_id\n" +"type\n" +"uid_ems" +msgstr "" +"access_state\n" +"actions\n" +"canister_slots\n" +"drive_bays\n" +"ems_id\n" +"ems_ref\n" +"enclosures\n" +"health_state\n" +"href\n" +"id\n" +"name\n" +"overall_health_state\n" +"physical_chassis_id\n" +"physical_rack_id\n" +"type\n" +"uid_ems" + +msgid "" +"To retrieve information about a specific physical storage system (such as " +"name and ID), use the ?expand=" +"resources&attributes=<attribute_list> query parameters, " +"for example:" +msgstr "" +"特定の物理ストレージシステムに関する特定の情報を取得するには (名前および ID 等)、?expand=resources&attributes=<attribute_list> クエリーパラメーターを使用します。以下に例を示します。" + +msgid "" +"GET /api/physical_storages/<storage_ID>?expand=" +"resources&attributes=id,name" +msgstr "" +"GET /api/physical_storages/<storage_ID>?expand=" +"resources&attributes=id,name" + +msgid "" +"To retrieve information, such as canisters and physical disks that are " +"associated with a specific physical storage system, use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" +"特定の物理ストレージシステムに関するキャニスターおよび物理ディスク等の情報を取得するには、?expand=resources&attributes=<attribute_list> クエリーパラメーターを使用します。以下に例を示します。" + +msgid "" +"GET /api/physical_storages/<storage_ID>?expand=" +"resources&attributes=canisters,physical_disks" +msgstr "" +"GET /api/physical_storages/<storage_ID>?expand=" +"resources&attributes=canisters,physical_disks" + +msgid "Retrieving Physical Switch Details" +msgstr "物理スイッチ情報の取得" + +msgid "" +"To retrieve information for all physical switches, use the following request " +"URL:" +msgstr "すべての物理スイッチに関する情報を取得するには、以下のリクエスト URL を使用します。" + +msgid "GET /api/physical_switches" +msgstr "GET /api/physical_switches" + +msgid "" +"actions (list of actions that can be used)\n" +"count (number of physical switches)\n" +"name (URI name)\n" +"pages (count of pages)\n" +"resources (list of URLs for each physical switch)\n" +"subcount (number of physical switches that were returned)" +msgstr "" +"actions (使用することのできるアクションのリスト)\n" +"count (物理スイッチの数)\n" +"name (URI 名)\n" +"pages (ページ数)\n" +"resources (各物理スイッチの URL のリスト)\n" +"subcount (返された物理スイッチの数)" + +msgid "" +"To retrieve all information about the physical switches, use the ?expand=resources query parameter, for example:" +msgstr "" +"物理スイッチに関するすべての情報を取得するには、?expand=resources クエリーパラメーターを使用します。以下に例を示します。" + +msgid "GET /api/physical_switches?expand=resources" +msgstr "GET /api/physical_switches?expand=resources" + +msgid "" +"To retrieve specific information about the physical switches (such as name " +"and ID), use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"物理スイッチに関する特定の情報を取得するには (名前および ID 等)、?expand=" +"resources&attributes=<attribute_list> " +"クエリーパラメーターを使用します。以下に例を示します。" + +msgid "GET /api/physical_switches?expand=resources&attributes=id,name" +msgstr "GET /api/physical_switches?expand=resources&attributes=id,name" + +msgid "" +"To retrieve information such as ports on physical switches, use the " +"?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"物理スイッチのポート等の情報を取得するには、?expand=" +"resources&attributes=<attribute_list> " +"クエリーパラメーターを使用します。以下に例を示します。" + +msgid "" +"GET /api/physical_switches?expand=resources&attributes=" +"physical_network_ports" +msgstr "" +"GET /api/physical_switches?expand=resources&attributes=" +"physical_network_ports" + +msgid "" +"To retrieve information such as physical devices connected to physical " +"switches, use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"物理スイッチに接続された物理デバイス等の情報を取得するには、?expand=" +"resources&attributes=<attribute_list> " +"クエリーパラメーターを使用します。以下に例を示します。" + +msgid "" +"GET /api/physical_switches?expand=resources&attributes=" +"connected_components" +msgstr "" +"GET /api/physical_switches?expand=resources&attributes=" +"connected_components" + +msgid "" +"To retrieve information about only a specific physical switch, use the " +"?expand=resources&filter[]=name=" +"<switch_name> query attributes on all physical switch " +"resources, for example:" +msgstr "" +"特定の物理スイッチに関する情報だけを取得するには、すべての物理スイッチリソースに対して ?expand=resources&filter[]=name=<switch_name> クエリー属性を使用します。以下に例を示します。" + +msgid "" +"GET /api/physical_switches?expand=resources&filter[]=name=IO Module 02" +msgstr "" +"GET /api/physical_switches?expand=resources&filter[]=name=IO Module 02" + +msgid "Retrieving Physical Switch Details by ID" +msgstr "ID による物理スイッチ情報の取得" + +msgid "" +"To retrieve information for a specific physical switch, use the following " +"request URL:" +msgstr "特定の物理スイッチに関する情報を取得するには、以下のリクエスト URL を使用します。" + +msgid "GET /api/physical_switches/<switch_ID>" +msgstr "GET /api/physical_switches/<switch_ID>" + +msgid "" +"actions\n" +"allow_promiscuous\n" +"ems_id\n" +"forged_transmits\n" +"health_state\n" +"href\n" +"id\n" +"mac_changes\n" +"mtu\n" +"name\n" +"ports\n" +"power_state\n" +"shared\n" +"switch_uuid\n" +"type\n" +"uid_ems" +msgstr "" +"actions\n" +"allow_promiscuous\n" +"ems_id\n" +"forged_transmits\n" +"health_state\n" +"href\n" +"id\n" +"mac_changes\n" +"mtu\n" +"name\n" +"ports\n" +"power_state\n" +"shared\n" +"switch_uuid\n" +"type\n" +"uid_ems" + +msgid "" +"To retrieve information about a specific physical switch (such as name and " +"ID), use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"特定の物理スイッチに関する特定の情報を取得するには (名前および ID 等)、?expand=" +"resources&attributes=<attribute_list> " +"クエリーパラメーターを使用します。以下に例を示します。" + +msgid "" +"GET /api/physical_switches/<switch_ID>?expand=resources&attributes=" +"id,name" +msgstr "" +"GET /api/physical_switches/<switch_ID>?expand=resources&attributes=" +"id,name" + +msgid "" +"To retrieve information such as physical devices that are connected to a " +"specific physical switch, use the ?expand=" +"resources&attributes=<attribute_list> query parameters, " +"for example:" +msgstr "" +"特定の物理スイッチに接続された物理デバイス等の情報を取得するには、?expand=" +"resources&attributes=<attribute_list> " +"クエリーパラメーターを使用します。以下に例を示します。" + +msgid "" +"GET /api/physical_switches/<switch_ID>?expand=resources&attributes=" +"connected_components" +msgstr "" +"GET /api/physical_switches/<switch_ID>?expand=resources&attributes=" +"connected_components" + +msgid "" +"To retrieve information such as ports on a specific physical switch, use the " +"?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"特定物理スイッチのポート等の情報を取得するには、?expand=" +"resources&attributes=<attribute_list> " +"クエリーパラメーターを使用します。以下に例を示します。" + +msgid "" +"GET /api/physical_switches/<switch_ID>?expand=resources&attributes=" +"physical_network_ports" +msgstr "" +"GET /api/physical_switches/<switch_ID>?expand=resources&attributes=" +"physical_network_ports" + +msgid "Performing physical switch actions" +msgstr "物理スイッチに関する操作の実施" + +msgid "" +"You can use the REST API to perform management tasks on a physical switch, " +"such as restarting the switch." +msgstr "REST API を使用して、物理スイッチの再起動などの管理タスクを実施することができます。" + +msgid "" +"Note: To perform actions on physical " +"switch, you must create a basic authentication using your preferred tool or " +"library, and enter your user name and password to access the CloudForms REST " +"API." +msgstr "" +"メモ: " +"物理スイッチに関する操作を実施するには、任意のツールまたはライブラリーを用いて基本認証を作成し、ユーザー名およびパスワードを入力して " +"CloudForms REST API にアクセスする必要があります。" + +msgid "Restarting a physical switch" +msgstr "物理スイッチの再起動" + +msgid "" +"To restart a specific switch, send a POST request using the following " +"request URL and JSON request body." +msgstr "" +"特定のスイッチを再起動するには、以下のリクエスト URL および JSON リクエストボディーを使用して POST リクエストを送信します。" + +msgid "POST /api/physical_switches/<switch_ID>" +msgstr "POST /api/physical_switches/<switch_ID>" + +msgid "Performing an action on multiple physical switches" +msgstr "複数の物理スイッチに関する操作の実施" + +msgid "" +"To perform an action on more than one physical switch, send a POST request " +"using the following request URL and JSON request body." +msgstr "" +"複数の物理スイッチに関する操作を実施するには、以下のリクエスト URL および JSON リクエストボディーを使用して POST " +"リクエストを送信します。" + +msgid "POST /api/physical_switches" +msgstr "POST /api/physical_switches" + +msgid "" +"{\n" +" \"action\":\"<action>\",\n" +" \"resources\": [{\n" +" \"href\":\"<switch_ID>\"\n" +" },\n" +" {\n" +" \"href\":\"<switch_ID>\"\n" +" }]\n" +"}" +msgstr "" +"{\n" +" \"action\":\"<action>\",\n" +" \"resources\": [{\n" +" \"href\":\"<switch_ID>\"\n" +" },\n" +" {\n" +" \"href\":\"<switch_ID>\"\n" +" }]\n" +"}" diff --git a/physical_infra_provider_rest_api/l10n/pot/Author_Group.pot b/physical_infra_provider_rest_api/l10n/pot/Author_Group.pot index 4440974..766dc6e 100644 --- a/physical_infra_provider_rest_api/l10n/pot/Author_Group.pot +++ b/physical_infra_provider_rest_api/l10n/pot/Author_Group.pot @@ -1,8 +1,8 @@ msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2018-02-26 09:56+1000\n" -"PO-Revision-Date: 2018-02-26 09:56+1000\n" +"POT-Creation-Date: 2018-11-22 19:42+1000\n" +"PO-Revision-Date: 2018-11-22 19:42+1000\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "Language: en-US \n" diff --git a/physical_infra_provider_rest_api/l10n/pot/Revision_History.pot b/physical_infra_provider_rest_api/l10n/pot/Revision_History.pot index 03787bd..08ea95d 100644 --- a/physical_infra_provider_rest_api/l10n/pot/Revision_History.pot +++ b/physical_infra_provider_rest_api/l10n/pot/Revision_History.pot @@ -1,8 +1,8 @@ msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2018-02-26 09:56+1000\n" -"PO-Revision-Date: 2018-02-26 09:56+1000\n" +"POT-Creation-Date: 2018-11-22 19:42+1000\n" +"PO-Revision-Date: 2018-11-22 19:42+1000\n" "Last-Translator: Automatically generated\n" "Language-Team: None\n" "Language: en-US \n" diff --git a/physical_infra_provider_rest_api/l10n/pot/main.pot b/physical_infra_provider_rest_api/l10n/pot/main.pot new file mode 100644 index 0000000..8de5082 --- /dev/null +++ b/physical_infra_provider_rest_api/l10n/pot/main.pot @@ -0,0 +1,849 @@ +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"POT-Creation-Date: 2018-11-22 19:42+1000\n" +"PO-Revision-Date: 2018-11-22 19:42+1000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: None\n" +"Language: en-US \n" +"MIME-Version: 1.0\n" +"Content-Type: application/x-publican; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Publican v4.3.3\n" + +msgid "Lenovo Physical Infrastructure Provider REST API" +msgstr "" + +msgid "A reference to the Lenovo physical infrastructure provider REST API" +msgstr "" + +msgid "Red Hat CloudForms" +msgstr "" + +msgid "A reference to the Lenovo physical infrastructure provider REST API." +msgstr "" + +msgid "If you have a suggestion for improving this guide or have found an error, please submit a Bugzilla report at http://bugzilla.redhat.com against Red Hat CloudForms Management Engine for the Documentation component. Please provide specific details, such as the section number, guide name, and CloudForms version so we can easily locate the content." +msgstr "" + +msgid "REST API" +msgstr "" + +msgid "You can use the REST API to retrieve information about providers, physical-infrastructure providers, and physical servers. You can use the CloudForms REST API if you need information about the servers in your physical infrastructure." +msgstr "" + +msgid "Before you begin" +msgstr "" + +msgid "To use the REST API, you must log in to CloudForms Management Engine API as a user who has permission to access the API. The default user is admin, password is smartvm." +msgstr "" + +msgid "Retrieving Provider Details" +msgstr "" + +msgid "To retrieve information for all providers, use the following request URL:" +msgstr "" + +msgid "GET /api/providers" +msgstr "" + +msgid "A JSON response with the following keys is returned." +msgstr "" + +msgid "" +"actions (list of actions that can be used)\n" +"count (total number of providers)\n" +"name (URI name)\n" +"pages (number of pages)\n" +"resource (list of URLs for each provider that is managed by CloudForms)\n" +"subcount (number of providers that were returned)" +msgstr "" + +msgid "Examples" +msgstr "" + +msgid "To retrieve all information about the providers, use the ?expand=resources query parameter, for example:" +msgstr "" + +msgid "GET /api/providers?expand=resources" +msgstr "" + +msgid "To retrieve a specific information about the providers (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/providers?expand=resources&attributes=id,name" +msgstr "" + +msgid "To retrieve additional information about the providers (such as port, hostname, and IP address), use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/providers?expand=resources&attributes=port,hostname,ipaddress" +msgstr "" + +msgid "To retrieve information about only Lenovo physical-infrastructure providers, use the ?expand=resources&filter[]=type=<provider_type> attribute against all provider resources, for example:" +msgstr "" + +msgid "GET /api/providers?expand=resources&filter[]=type=ManageIQ::Providers::Lenovo::PhysicalInfraManager" +msgstr "" + +msgid "Retrieving Provider Details by ID" +msgstr "" + +msgid "To retrieve information for a specific provider, use the following request URL where <provider_ID> is the unique identifier of the provider:" +msgstr "" + +msgid "GET /api/providers/<provider_ID>" +msgstr "" + +msgid "" +"href\n" +"id\n" +"name\n" +"created_on\n" +"updated_on\n" +"guid\n" +"zone_id\n" +"type\n" +"last_refresh_date\n" +"tenant_id\n" +"enabled\n" +"options\n" +"actions" +msgstr "" + +msgid "To retrieve a specific information about the provider (such as name and ID), use the ?attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/providers/<provider_ID>?expand=resources&attributes=id,name" +msgstr "" + +msgid "To retrieve additional information about the provider (such as port, hostname, and IP address), use the ?attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/providers/<provider_ID>?expand=resources\n" +"&attributes=port,hostname,ipaddress" +msgstr "" + +msgid "Performing physical-infrastructure provider actions" +msgstr "" + +msgid "You can use the REST API to perform actions on a physical-infrastructure provider, such as creating, modifying and deleting." +msgstr "" + +msgid "Note: To perform actions on physical-infrastructure providers, you must create a basic authentication using your preferred tool or library, and use the user name and password for the CloudForms instance when using the REST API." +msgstr "" + +msgid "Creating a Lenovo physical-infrastructure provider" +msgstr "" + +msgid "To create a Lenovo physical-infrastructure provider, send a POST request using the following request URL and JSON request body." +msgstr "" + +msgid "POST /api/providers" +msgstr "" + +msgid "Request body:" +msgstr "" + +msgid "" +"{\n" +" \"action\": \"create\",\n" +" \"credentials\": {\n" +" \"password\": \"<PASSWORD>\",\n" +" \"userid\": \"<USERNAME>\"\n" +" },\n" +" \"hostname\": \"<LENOVO XCLARITY ADMINISTRATOR ADDRESS>\",\n" +" \"name\": \"<NAME>\",\n" +" \"port\": \"<THE SERVICE PORT>\",\n" +" \"type\": \"ManageIQ::Providers::Lenovo::PhysicalInfraManager\"\n" +"}" +msgstr "" + +msgid "Modifying properties for a Lenovo physical-infrastructure provider" +msgstr "" + +msgid "To modify properties of a Lenovo physical-infrastructure provider, send a POST request using the following request URL and JSON request body." +msgstr "" + +msgid "" +"{\n" +" \"action\":\"edit\",\n" +" \"credentials\": {\n" +" \"password\":\"<new_passowrd>\",\n" +" \"userid\":\"<new_user_name>\"\n" +" },\n" +" \"hostname\":\"<New_Lenovo_XClarity_Administrator_address>\",\n" +" \"name\":\"<new_provider_name>\",\n" +" \"port\":\"<new_service_port>\"\n" +"}" +msgstr "" + +msgid "Refreshing information about all providers" +msgstr "" + +msgid "To refresh information about all providers, send a POST request using the following request URL and JSON request body." +msgstr "" + +msgid "" +"{\n" +" \"action\":\"refresh\"\n" +"}" +msgstr "" + +msgid "Deleting a physical-infrastructure provider" +msgstr "" + +msgid "To delete a specific provider:" +msgstr "" + +msgid "Send a DELETE request using the following request URL." +msgstr "" + +msgid "DELETE /api/providers/<provider_ID>" +msgstr "" + +msgid "Send a POST request using the following request URL and JSON request body." +msgstr "" + +msgid "POST /api/providers/<provider_ID>" +msgstr "" + +msgid "" +"{\n" +" \"action\":\"delete\"\n" +"}" +msgstr "" + +msgid "Performing an action on multiple physical-infrastructure providers" +msgstr "" + +msgid "To perform an action on more than one physical-infrastructure providers, send a POST request using the following request URL and JSON request body." +msgstr "" + +msgid "" +"{\n" +" \"action\":\"<action>\",\n" +" \"resources\": [{\n" +" \"href\":\"<provider_ID>\"\n" +" },\n" +" {\n" +" \"href\":\"<provider_ID>\"\n" +" }]\n" +"}" +msgstr "" + +msgid "Retrieving Physical Server Details" +msgstr "" + +msgid "To retrieve information for all physical servers, use the following request URL:" +msgstr "" + +msgid "GET /api/physical_servers" +msgstr "" + +msgid "" +"actions (list of actions that can be used)\n" +"count (number of physical servers)\n" +"name (URI name)\n" +"pages (number of pages)\n" +"resource (list of URLs for each physical server)\n" +"subcount (number of physical servers that were returned)" +msgstr "" + +msgid "To retrieve all information about the physical servers, use the ?expand=resources query parameter, for example:" +msgstr "" + +msgid "GET /api/physical_servers?expand=resources" +msgstr "" + +msgid "To retrieve specific information about the physical servers (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/physical_servers?expand=resources&attributes=id,name" +msgstr "" + +msgid "To retrieve information such as firmware, networks, guest devices, and asset details associated with physical servers, use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/physical_servers?expand=resources&attributes=hardware.firmwares,hardware.networks,hardware.guest_devices,hardware.assets_details" +msgstr "" + +msgid "To retrieve information such as network adapters and storage adapters in physical servers, use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/physical_servers?expand=resources&attributes=guest_devices.with_ethernet_type,guest_devices.with_storage_type" +msgstr "" + +msgid "To retrieve information such as switches connected to physical servers, use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/physical_servers?expand=resources&attributes=physical_switches" +msgstr "" + +msgid "To retrieve information about only a specific physical server, use the ?expand=resources&filter[]=name=<server_name> query attributes on all physical-server resources, for example:" +msgstr "" + +msgid "GET /api/physical_servers?expand=resources&filter[]=name=Server1-20127X5462" +msgstr "" + +msgid "Retrieving Physical Server Details by ID" +msgstr "" + +msgid "To retrieve information for a specific physical server, use the following request URL:" +msgstr "" + +msgid "GET /api/physical_servers/<server_ID>" +msgstr "" + +msgid "" +"actions\n" +"created_at\n" +"ems_id\n" +"ems_ref\n" +"field_replaceable_unit\n" +"health_state\n" +"hostname\n" +"href\n" +"location_led_state\n" +"machine_type\n" +"manufacturer\n" +"model\n" +"name\n" +"power_state\n" +"product_name\n" +"serial_number\n" +"type\n" +"uid_ems\n" +"updated_at\n" +"vendor" +msgstr "" + +msgid "To retrieve information about a specific physical server (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/physical_servers/<server_ID>?expand=resources&attributes=id,name" +msgstr "" + +msgid "To retrieve information such as firmware, networks, guest devices, and asset details for a specific server, use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/physical_servers/<server_ID>?expand=resources\n" +"&attributes=hardware.firmwares,hardware.networks,hardware.guest_devices,hardware.assets_details" +msgstr "" + +msgid "To retrieve information such as switches that are connected to a specific server, use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/physical_servers/<server_ID>?expand=resources&attributes=physical_switches" +msgstr "" + +msgid "To retrieve information such as network adapters and storage adapters in a specific physical server, use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/physical_servers/<server_ID>?expand=resources&attributes=guest_devices.with_ethernet_type,guest_devices.with_storage_type,hardware.physical_network_ports" +msgstr "" + +msgid "Performing physical server actions" +msgstr "" + +msgid "You can use the REST API to perform management tasks on a physical server, such as powering on an off, restarting, and changing the location-LED state." +msgstr "" + +msgid "Note: To perform actions on physical servers, you must create a basic authentication using your preferred tool or library, and enter your user name and password to access the CloudForms REST API." +msgstr "" + +msgid "Powering on a physical server" +msgstr "" + +msgid "To power on a specific physical server, send a POST request using the following request URL and JSON request body." +msgstr "" + +msgid "POST /api/physical_servers/<server_ID>" +msgstr "" + +msgid "" +"{\n" +" \"action\":\"power_on\"\n" +"}" +msgstr "" + +msgid "Powering off a physical server" +msgstr "" + +msgid "To shut down the operating system and power off a specific physical server, send a POST request using the following request URL and JSON request body." +msgstr "" + +msgid "" +"{\n" +" \"action\":\"power_off\"\n" +"}" +msgstr "" + +msgid "Immediately powering off a physical server" +msgstr "" + +msgid "To immediately power off a specific physical server, send a POST request using the following request URL and JSON request body." +msgstr "" + +msgid "" +"{\n" +" \"action\":\"power_off_now\"\n" +"}" +msgstr "" + +msgid "Restarting a physical server" +msgstr "" + +msgid "To shut down the operating system and restart a specific physical server, send a POST request using the following request URL and JSON request body." +msgstr "" + +msgid "" +"{\n" +" \"action\":\"restart\"\n" +"}" +msgstr "" + +msgid "Immediately restarting a physical server" +msgstr "" + +msgid "To immediately restart a specific physical server, send a POST request using the following request URL and JSON request body." +msgstr "" + +msgid "" +"{\n" +" \"action\":\"restart_now\"\n" +"}" +msgstr "" + +msgid "Changing the location LED state on a physical server to blinking" +msgstr "" + +msgid "To change the location-LED state to blinking on a specific server, send a POST request using the following request URL and JSON request body." +msgstr "" + +msgid "" +"{\n" +" \"action\":\"blink_loc_led\"\n" +"}" +msgstr "" + +msgid "Performing an action on multiple physical servers" +msgstr "" + +msgid "To perform an action on more than one physical server, send a POST request using the following request URL and JSON request body." +msgstr "" + +msgid "POST /api/physical_servers" +msgstr "" + +msgid "" +"{\n" +" \"action\":\"<action>\",\n" +" \"resources\": [{\n" +" \"href\":\"<server_ID>\"\n" +" },\n" +" {\n" +" \"href\":\"<server_ID>\"\n" +" }]\n" +"}" +msgstr "" + +msgid "Retrieving Physical Chassis Details" +msgstr "" + +msgid "To retrieve information for all physical chassis, use the following request URL:" +msgstr "" + +msgid "GET /api/physical_chassis" +msgstr "" + +msgid "" +"actions (list of actions that can be used)\n" +"count (number of physical chassis)\n" +"name (URI name)\n" +"pages (number of pages)\n" +"resources (list of URLs for each physical chassis)\n" +"subcount (number of physical chassis that were returned)" +msgstr "" + +msgid "To retrieve all information about the physical chassis, use the ?expand=resources query parameter, for example:" +msgstr "" + +msgid "GET /api/physical_chassis?expand=resources" +msgstr "" + +msgid "To retrieve specific information about the physical chassis (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/physical_chassis?expand=resources&attributes=id,name" +msgstr "" + +msgid "To retrieve information such as the switches, storage systems, and servers in a chassis, use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/physical_chassis?expand=resources&attributes=physical_servers,physical_storages,hardware.connected_physical_switches" +msgstr "" + +msgid "To retrieve information about only a specific physical chassis, use the ?expand=resources&filter[]=name=<chassis_name> query attributes on all physical chassis resources, for example:" +msgstr "" + +msgid "GET /api/physical_chassis?expand=resources&filter[]=name=SN%23Y034BG16E060" +msgstr "" + +msgid "Retrieving Physical Chassis Details by ID" +msgstr "" + +msgid "To retrieve information for a specific physical chassis, use the following request URL:" +msgstr "" + +msgid "GET /api/physical_chassis/<chassis_ID>" +msgstr "" + +msgid "" +"href\n" +"id\n" +"ems_id\n" +"uid_ems\n" +"ems_ref\n" +"physical_rack_id\n" +"name\n" +"vendor\n" +"type\n" +"location_led_state\n" +"health_state\n" +"overall_health_state\n" +"management_module_slot_count\n" +"switch_slot_count\n" +"fan_slot_count\n" +"blade_slot_count\n" +"powersupply_slot_count\n" +"actions" +msgstr "" + +msgid "To retrieve information about a specific physical chassis (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/physical_chassis/<chassis_ID>?expand=resources&attributes=id,name" +msgstr "" + +msgid "To retrieve information, such as the switches, storage systems, and servers that are in a specific physical chassis, use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/physical_chassis/<chassis_ID>?expand=resources&attributes=physical_servers,physical_storages,hardware.connected_physical_switches" +msgstr "" + +msgid "Performing physical chassis actions" +msgstr "" + +msgid "You can use the REST API to perform management tasks on a physical chassis, such as changing the location LED state." +msgstr "" + +msgid "Note: To perform actions on physical chassis, you must create a basic authentication using your preferred tool or library, and enter your user name and password to access the CloudForms REST API." +msgstr "" + +msgid "Changing the location LED state on a physical chassis to blinking" +msgstr "" + +msgid "To change the location LED state to blinking on a specific chassis, send a POST request using the following request URL and JSON request body." +msgstr "" + +msgid "POST /api/physical_chassis/<chassis_ID>" +msgstr "" + +msgid "Performing an action on multiple physical chassis" +msgstr "" + +msgid "To perform an action on more than one physical chassis, send a POST request using the following request URL and JSON request body." +msgstr "" + +msgid "POST /api/physical_chassis" +msgstr "" + +msgid "" +"{\n" +" \"action\":\"<action>\",\n" +" \"resources\": [{\n" +" \"href\":\"<chassis_ID>\"\n" +" },\n" +" {\n" +" \"href\":\"<chassis_ID>\"\n" +" }]\n" +"}" +msgstr "" + +msgid "Retrieving Physical Rack Details" +msgstr "" + +msgid "To retrieve information for all physical racks, use the following request URL:" +msgstr "" + +msgid "GET /api/physical_racks" +msgstr "" + +msgid "" +"actions (list of actions that can be used)\n" +"count (number of physical racks)\n" +"name (URI name)\n" +"pages (number of pages)\n" +"resources (list of URLs for each physical rack)\n" +"subcount (number of physical racks that were returned)" +msgstr "" + +msgid "To retrieve all information about the physical racks, use the ?expand=resources query parameter, for example:" +msgstr "" + +msgid "GET /api/physical_racks?expand=resources" +msgstr "" + +msgid "To retrieve specific information about the physical racks (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/physical_racks?expand=resources&attributes=id,name" +msgstr "" + +msgid "To retrieve information about only a specific physical rack, use the ?expand=resources&filter[]=name=<rack_name> query attributes on all physical rack resources, for example:" +msgstr "" + +msgid "GET /api/physical_racks?expand=resources&filter[]=name=rack-2" +msgstr "" + +msgid "Retrieving Physical Rack Details by ID" +msgstr "" + +msgid "To retrieve information for a specific physical rack, use the following request URL:" +msgstr "" + +msgid "GET /api/physical_racks/<rack_ID>" +msgstr "" + +msgid "" +"actions\n" +"ems_id\n" +"ems_ref\n" +"href\n" +"id\n" +"name\n" +"uid_ems" +msgstr "" + +msgid "To retrieve information about a specific physical rack (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/physical_racks/<rack_ID>?expand=resources&attributes=id,name" +msgstr "" + +msgid "Retrieving Physical Storage Details" +msgstr "" + +msgid "To retrieve information for all physical storage systems, use the following request URL:" +msgstr "" + +msgid "GET /api/physical_storages" +msgstr "" + +msgid "" +"actions (list of actions that can be used)\n" +"count (number of physical storage systems)\n" +"name (URI name)\n" +"pages (number of pages)\n" +"resources (list of URLs for each physical storage system)\n" +"subcount (number of physical storage systems that were returned)" +msgstr "" + +msgid "To retrieve all information about the physical storage systems, use the ?expand=resources query parameter, for example:" +msgstr "" + +msgid "GET /api/physical_storages?expand=resources" +msgstr "" + +msgid "To retrieve specific information about the physical storage systems (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/physical_storages?expand=resources&attributes=id,name" +msgstr "" + +msgid "To retrieve information such as canisters and physical disks associated with physical storage systems, use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/physical_storages?expand=resources&attributes=canisters,physical_disks" +msgstr "" + +msgid "To retrieve information about only a specific physical storage system, use the ?expand=resources&filter[]=name=<storage_name> query attributes on all physical storage resources, for example:" +msgstr "" + +msgid "GET /api/physical_storages?expand=resources&filter[]=name=SeagateV1-S3200-DM" +msgstr "" + +msgid "Retrieving Physical Storage Details by ID" +msgstr "" + +msgid "To retrieve information for a specific physical storage system, use the following request URL:" +msgstr "" + +msgid "GET /api/physical_storages/<storage_ID>" +msgstr "" + +msgid "" +"access_state\n" +"actions\n" +"canister_slots\n" +"drive_bays\n" +"ems_id\n" +"ems_ref\n" +"enclosures\n" +"health_state\n" +"href\n" +"id\n" +"name\n" +"overall_health_state\n" +"physical_chassis_id\n" +"physical_rack_id\n" +"type\n" +"uid_ems" +msgstr "" + +msgid "To retrieve information about a specific physical storage system (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/physical_storages/<storage_ID>?expand=resources&attributes=id,name" +msgstr "" + +msgid "To retrieve information, such as canisters and physical disks that are associated with a specific physical storage system, use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/physical_storages/<storage_ID>?expand=resources&attributes=canisters,physical_disks" +msgstr "" + +msgid "Retrieving Physical Switch Details" +msgstr "" + +msgid "To retrieve information for all physical switches, use the following request URL:" +msgstr "" + +msgid "GET /api/physical_switches" +msgstr "" + +msgid "" +"actions (list of actions that can be used)\n" +"count (number of physical switches)\n" +"name (URI name)\n" +"pages (count of pages)\n" +"resources (list of URLs for each physical switch)\n" +"subcount (number of physical switches that were returned)" +msgstr "" + +msgid "To retrieve all information about the physical switches, use the ?expand=resources query parameter, for example:" +msgstr "" + +msgid "GET /api/physical_switches?expand=resources" +msgstr "" + +msgid "To retrieve specific information about the physical switches (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/physical_switches?expand=resources&attributes=id,name" +msgstr "" + +msgid "To retrieve information such as ports on physical switches, use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/physical_switches?expand=resources&attributes=physical_network_ports" +msgstr "" + +msgid "To retrieve information such as physical devices connected to physical switches, use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/physical_switches?expand=resources&attributes=connected_components" +msgstr "" + +msgid "To retrieve information about only a specific physical switch, use the ?expand=resources&filter[]=name=<switch_name> query attributes on all physical switch resources, for example:" +msgstr "" + +msgid "GET /api/physical_switches?expand=resources&filter[]=name=IO Module 02" +msgstr "" + +msgid "Retrieving Physical Switch Details by ID" +msgstr "" + +msgid "To retrieve information for a specific physical switch, use the following request URL:" +msgstr "" + +msgid "GET /api/physical_switches/<switch_ID>" +msgstr "" + +msgid "" +"actions\n" +"allow_promiscuous\n" +"ems_id\n" +"forged_transmits\n" +"health_state\n" +"href\n" +"id\n" +"mac_changes\n" +"mtu\n" +"name\n" +"ports\n" +"power_state\n" +"shared\n" +"switch_uuid\n" +"type\n" +"uid_ems" +msgstr "" + +msgid "To retrieve information about a specific physical switch (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/physical_switches/<switch_ID>?expand=resources&attributes=id,name" +msgstr "" + +msgid "To retrieve information such as physical devices that are connected to a specific physical switch, use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/physical_switches/<switch_ID>?expand=resources&attributes=connected_components" +msgstr "" + +msgid "To retrieve information such as ports on a specific physical switch, use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" + +msgid "GET /api/physical_switches/<switch_ID>?expand=resources&attributes=physical_network_ports" +msgstr "" + +msgid "Performing physical switch actions" +msgstr "" + +msgid "You can use the REST API to perform management tasks on a physical switch, such as restarting the switch." +msgstr "" + +msgid "Note: To perform actions on physical switch, you must create a basic authentication using your preferred tool or library, and enter your user name and password to access the CloudForms REST API." +msgstr "" + +msgid "Restarting a physical switch" +msgstr "" + +msgid "To restart a specific switch, send a POST request using the following request URL and JSON request body." +msgstr "" + +msgid "POST /api/physical_switches/<switch_ID>" +msgstr "" + +msgid "Performing an action on multiple physical switches" +msgstr "" + +msgid "To perform an action on more than one physical switch, send a POST request using the following request URL and JSON request body." +msgstr "" + +msgid "POST /api/physical_switches" +msgstr "" + +msgid "" +"{\n" +" \"action\":\"<action>\",\n" +" \"resources\": [{\n" +" \"href\":\"<switch_ID>\"\n" +" },\n" +" {\n" +" \"href\":\"<switch_ID>\"\n" +" }]\n" +"}" +msgstr "" + diff --git a/physical_infra_provider_rest_api/l10n/pot/master.pot b/physical_infra_provider_rest_api/l10n/pot/master.pot deleted file mode 100644 index 90e7c89..0000000 --- a/physical_infra_provider_rest_api/l10n/pot/master.pot +++ /dev/null @@ -1,438 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: 0\n" -"POT-Creation-Date: 2018-02-26 09:56+1000\n" -"PO-Revision-Date: 2018-02-26 09:56+1000\n" -"Last-Translator: Automatically generated\n" -"Language-Team: None\n" -"Language: en-US \n" -"MIME-Version: 1.0\n" -"Content-Type: application/x-publican; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"X-Generator: Publican v4.3.3\n" - -msgid "Lenovo Physical Infrastructure Provider REST API" -msgstr "" - -msgid "A reference to the Lenovo physical infrastructure provider REST API" -msgstr "" - -msgid "Red Hat CloudForms" -msgstr "" - -msgid "A reference to the Lenovo physical infrastructure provider REST API." -msgstr "" - -msgid "If you have a suggestion for improving this guide or have found an error, please submit a Bugzilla report at http://bugzilla.redhat.com against Red Hat CloudForms Management Engine for the Documentation component. Please provide specific details, such as the section number, guide name, and CloudForms version so we can easily locate the content." -msgstr "" - -msgid "REST API" -msgstr "" - -msgid "You can use the REST API to retrieve information about providers, physical-infrastructure providers, and physical servers. You can use the CloudForms REST API if you need information about the servers in your physical infrastructure." -msgstr "" - -msgid "Before you begin" -msgstr "" - -msgid "To use the REST API, you must log in to CloudForms Management Engine API as a user who has permission to access the API. The default user is admin, password is smartvm." -msgstr "" - -msgid "Use the following URL to access the CloudForms REST API:" -msgstr "" - -msgid "<CloudForms_address>:<port>/api" -msgstr "" - -msgid "For example:" -msgstr "" - -msgid "localhost:3000/api" -msgstr "" - -msgid "Retrieving Provider Details" -msgstr "" - -msgid "To retrieve information for all providers, use the following request URL:" -msgstr "" - -msgid "GET <CloudForms_address>:<port>/api/providers" -msgstr "" - -msgid "A JSON response with the following keys is returned." -msgstr "" - -msgid "" -"actions (list of actions that can be used)\n" -"count (total number of providers)\n" -"name (URI name)\n" -"pages (count of pages)\n" -"resource (list of URLs for each provider that is managed by CloudForms)\n" -"subcount (number of providers returned)" -msgstr "" - -msgid "Examples" -msgstr "" - -msgid "To retrieve all information about the providers, use the ?expand=resources query parameter, for example:" -msgstr "" - -msgid "GET localhost:3000/api/providers?expand=resources" -msgstr "" - -msgid "To retrieve a specific information about the providers (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" -msgstr "" - -msgid "GET localhost:3000/ api/providers?expand=resources&attributes=id,name" -msgstr "" - -msgid "To retrieve additional information about the providers (such as port, hostname, and IP address), use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" -msgstr "" - -msgid "GET localhost:3000/api/providers?expand=resources&attributes=port,hostname,ipaddress" -msgstr "" - -msgid "To retrieve information about only Lenovo physical-infrastructure providers, use the ?expand=resources&filter[]=type=<provider_type> attribute against all provider resources, for example:" -msgstr "" - -msgid "GET localhost:3000/api/providers?expand=resources&filter[]=type=ManageIQ::Providers::Lenovo::PhysicalInfraManager" -msgstr "" - -msgid "Retrieving Provider Details by ID" -msgstr "" - -msgid "To retrieve information for a specific provider, use the following request URL where <provider_ID> is the unique identifier of the provider:" -msgstr "" - -msgid "GET <CloudForms_address>:<port>/api/providers/<provider_ID>" -msgstr "" - -msgid "" -"href\n" -"id\n" -"name\n" -"created_on\n" -"updated_on\n" -"guid\n" -"zone_id\n" -"type\n" -"last_refresh_date\n" -"tenant_id\n" -"enabled\n" -"options\n" -"actions" -msgstr "" - -msgid "To retrieve a specific information about the provider (such as name and ID), use the ?attributes=<attribute_list> query parameters, for example:" -msgstr "" - -msgid "GET localhost:3000/api/providers/<provider_ID>?expand=resources&attributes=id,name" -msgstr "" - -msgid "To retrieve additional information about the provider (such as port, hostname, and IP address), use the ?attributes=<attribute_list> query parameters, for example:" -msgstr "" - -msgid " GET localhost:3000/api/providers/<provider_ID>?expand=resources\n" -"&attributes=port,hostname,ipaddress" -msgstr "" - -msgid "Performing physical-infrastructure provider actions" -msgstr "" - -msgid "You can use the REST API to perform actions on a physical-infrastructure provider, such as creating, modifying and deleting." -msgstr "" - -msgid "Note: To perform actions on physical-infrastructure providers, you must create a basic authentication using your preferred tool or library, and use the user name and password for the CloudForms instance when using the REST API." -msgstr "" - -msgid "Creating a Lenovo physical-infrastructure provider" -msgstr "" - -msgid "To create a Lenovo physical-infrastructure provider, send a POST request using the following request URL and JSON request body." -msgstr "" - -msgid "POST <CloudForms_address>:<port>/api/providers" -msgstr "" - -msgid "Request body:" -msgstr "" - -msgid "" -"{\n" -" \"action\": \"create\",\n" -" \"credentials\": {\n" -" \"password\": \"<PASSWORD>\",\n" -" \"userid\": \"<USERNAME>\"\n" -" },\n" -" \"hostname\": \"<LENOVO XCLARITY ADMINISTRATOR ADDRESS>\",\n" -" \"name\": \"<NAME>\",\n" -" \"port\": \"<THE SERVICE PORT>\",\n" -" \"type\": \"ManageIQ::Providers::Lenovo::PhysicalInfraManager\"\n" -"}" -msgstr "" - -msgid "Modifying properties for a Lenovo physical-infrastructure provider" -msgstr "" - -msgid "To modify properties of a Lenovo physical-infrastructure provider, send a POST request using the following request URL and JSON request body." -msgstr "" - -msgid "" -"{\n" -" \"action\":\"edit\",\n" -" \"credentials\": {\n" -" \"password\":\"<new_passowrd>\",\n" -" \"userid\":\"<new_user_name>\"\n" -" },\n" -" \"hostname\":\"<New_Lenovo_XClarity_Administrator_address>\",\n" -" \"name\":\"<new_provider_name>\",\n" -" \"port\":\"<new_service_port>\"\n" -"}" -msgstr "" - -msgid "Refreshing information about all providers" -msgstr "" - -msgid "To refresh information about all providers, send a POST request using the following request URL and JSON request body." -msgstr "" - -msgid "" -"{\n" -" \"action\":\"refresh\"\n" -"}" -msgstr "" - -msgid "Deleting a physical-infrastructure provider" -msgstr "" - -msgid "To delete a specific provider:" -msgstr "" - -msgid "Send a DELETE request using the following request URL." -msgstr "" - -msgid "DELETE <CloudForms_address>:<port>/api/providers/<provider_ID>" -msgstr "" - -msgid "Send a POST request using the following request URL and JSON request body." -msgstr "" - -msgid "POST <CloudForms_address>:<port>/api/providers/<provider_ID>" -msgstr "" - -msgid "" -"{\n" -" \"action\":\"delete\"\n" -"}" -msgstr "" - -msgid "Performing an action on multiple physical-infrastructure providers" -msgstr "" - -msgid "To perform an action on more than one physical-infrastructure providers, send a POST request using the following request URL and JSON request body." -msgstr "" - -msgid "" -"{\n" -" \"action\":\"<action>\",\n" -" \"resources\": [{\n" -" \"href\":\"<provider_ID>\"\n" -" },\n" -" {\n" -" \"href\":\"<provider_ID>\"\n" -" }]\n" -"}" -msgstr "" - -msgid "Retrieving Physical Server Details" -msgstr "" - -msgid "To retrieve information for all physical servers, use the following request URL:" -msgstr "" - -msgid "GET <CloudForms_address>:<port>/api/physical_servers" -msgstr "" - -msgid "" -"actions (list of actions that can be used)\n" -"count (count of the physical servers)\n" -"name (URI name)\n" -"pages (count of pages)\n" -"resource (list of URLs of the each physical servers)\n" -"subcount (count of the physical servers returned)" -msgstr "" - -msgid "To retrieve all information about the physical servers, use the ?expand=resources query parameter, for example:" -msgstr "" - -msgid "GET localhost:3000/api/physical_servers?expand=resources" -msgstr "" - -msgid "To retrieve a specific information about the physical servers (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" -msgstr "" - -msgid "GET localhost:3000/api/physical_servers?expand=resources&attributes=id,name" -msgstr "" - -msgid "To retrieve specific information about the physical servers (such as firmware, networks, guest devices, and asset details), use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" -msgstr "" - -msgid "GET localhost:3000/api/physical_servers?expand=resources&attributes= hardware.firmwares,hardware.networks,hardware.guest_devices,hardware.assets_details" -msgstr "" - -msgid "To retrieve information about only a specific physical server, use the ?expand=resources&filter[]=name=<server_name> query attributes on all physical-server resources, for example:" -msgstr "" - -msgid "GET localhost:3000/api/physical_servers?expand=resources&filter[]=name=Server1-20127X5462" -msgstr "" - -msgid "Retrieving Physical Server Details by ID" -msgstr "" - -msgid "To retrieve information for a specific physical server, use the following request URL:" -msgstr "" - -msgid "GET <CloudForms_address>:<port>/api/physical_servers/<server_ID>" -msgstr "" - -msgid "" -"actions\n" -"created_at\n" -"ems_id\n" -"ems_ref\n" -"field_replaceable_unit\n" -"health_state\n" -"hostname\n" -"href\n" -"location_led_state\n" -"machine_type\n" -"manufacturer\n" -"model\n" -"name\n" -"power_state\n" -"product_name\n" -"serial_number\n" -"type\n" -"uid_ems\n" -"updated_at\n" -"vendor" -msgstr "" - -msgid "To retrieve a specific information about a specific physical server (such as name and ID), use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" -msgstr "" - -msgid "GET localhost:3000/api/physical_servers/<server_ID>?expand=resources&attributes=id,name" -msgstr "" - -msgid "To retrieve a specific information about a specific physical server (such as firmware, networks, guest devices, and asset details), use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" -msgstr "" - -msgid " GET localhost:3000/api/physical_servers/<server_ID>?expand=resources\n" -"&attributes=hardware.firmwares,hardware.networks,hardware.guest_devices,hardware.assets_details" -msgstr "" - -msgid "Performing physical server actions" -msgstr "" - -msgid "You can use the REST API to perform management tasks on a physical server, such as powering on an off, restarting, and changing the location-LED state." -msgstr "" - -msgid "Note: To perform actions on physical servers, you must create a basic authentication using your preferred tool or library, and enter your user name and password to access the CloudForms REST API." -msgstr "" - -msgid "Powering on a physical server" -msgstr "" - -msgid "To power on a specific physical server, send a POST request using the following request URL and JSON request body." -msgstr "" - -msgid "POST <CloudForms_address>:<port>/api/physical_servers/<server_ID>" -msgstr "" - -msgid "" -"{\n" -" \"action\":\"power_on\"\n" -"}" -msgstr "" - -msgid "Powering off a physical server" -msgstr "" - -msgid "To shut down the operating system and power off a specific physical server, send a POST request using the following request URL and JSON request body." -msgstr "" - -msgid "" -"{\n" -" \"action\":\"power_off\"\n" -"}" -msgstr "" - -msgid "Immediately powering off a physical server" -msgstr "" - -msgid "To immediately power off a specific physical server, send a POST request using the following request URL and JSON request body." -msgstr "" - -msgid "" -"{\n" -" \"action\":\"power_off_now\"\n" -"}" -msgstr "" - -msgid "Restarting a physical server" -msgstr "" - -msgid "To shut down the operating system and restart a specific physical server, send a POST request using the following request URL and JSON request body." -msgstr "" - -msgid "" -"{\n" -" \"action\":\"restart\"\n" -"}" -msgstr "" - -msgid "Immediately restarting a physical server" -msgstr "" - -msgid "To immediately restart a specific physical server, send a POST request using the following request URL and JSON request body." -msgstr "" - -msgid "" -"{\n" -" \"action\":\"restart_now\"\n" -"}" -msgstr "" - -msgid "Changing the location LED state on a physical server to blinking" -msgstr "" - -msgid "To change the location-LED state to blinking on a specific server, send a POST request using the following request URL and JSON request body." -msgstr "" - -msgid "" -"{\n" -" \"action\":\"blink_loc_led\"\n" -"}" -msgstr "" - -msgid "Performing an action on multiple physical servers" -msgstr "" - -msgid "To perform an action on more than one physical severs, send a POST request using the following request URL and JSON request body." -msgstr "" - -msgid "POST <CloudForms_address>:<port>/api/physical_servers" -msgstr "" - -msgid "" -"{\n" -" \"action\":\"<action>\",\n" -" \"resources\": [{\n" -" \"href\":\"<server_ID>\"\n" -" },\n" -" {\n" -" \"href\":\"<server_ID>\"\n" -" }]\n" -"}" -msgstr "" - diff --git a/physical_infra_provider_rest_api/l10n/publican.cfg b/physical_infra_provider_rest_api/l10n/publican.cfg index cca6f2a..f5276de 100644 --- a/physical_infra_provider_rest_api/l10n/publican.cfg +++ b/physical_infra_provider_rest_api/l10n/publican.cfg @@ -1,13 +1,13 @@ # Config::Simple 4.59 -# Mon Mar 5 15:53:11 2018 +# Wed Dec 12 13:39:53 2018 xml_lang: "en-US" dtdver: "5.0" -brand: "common" +brand: "RedHat-Pantheon-db5" type: Book product: "Red Hat CloudForms" -version: "4.6" +version: "4.7" docname: "Lenovo Physical Infrastructure Provider REST API" chunk_section_depth: 0 chunk_first: 0 diff --git a/physical_infra_provider_rest_api/l10n/zh-CN/Author_Group.po b/physical_infra_provider_rest_api/l10n/zh-CN/Author_Group.po index 84d5977..a407fd8 100644 --- a/physical_infra_provider_rest_api/l10n/zh-CN/Author_Group.po +++ b/physical_infra_provider_rest_api/l10n/zh-CN/Author_Group.po @@ -2,7 +2,7 @@ msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2018-02-26 09:56+1000\n" +"POT-Creation-Date: 2018-11-22 19:42+1000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -10,7 +10,7 @@ msgstr "" "Last-Translator: jsh \n" "Language-Team: Chinese (Simplified)\n" "Language: zh_Hans\n" -"X-Generator: Zanata 4.4.3\n" +"X-Generator: Zanata 4.6.2\n" "Plural-Forms: nplurals=1; plural=0\n" msgid "Red Hat CloudForms" diff --git a/physical_infra_provider_rest_api/l10n/zh-CN/Revision_History.po b/physical_infra_provider_rest_api/l10n/zh-CN/Revision_History.po index b55275a..a5ef117 100644 --- a/physical_infra_provider_rest_api/l10n/zh-CN/Revision_History.po +++ b/physical_infra_provider_rest_api/l10n/zh-CN/Revision_History.po @@ -2,7 +2,7 @@ msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2018-02-26 09:56+1000\n" +"POT-Creation-Date: 2018-11-22 19:42+1000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -10,7 +10,7 @@ msgstr "" "Last-Translator: jsh \n" "Language-Team: Chinese (Simplified)\n" "Language: zh_Hans\n" -"X-Generator: Zanata 4.4.3\n" +"X-Generator: Zanata 4.6.2\n" "Plural-Forms: nplurals=1; plural=0\n" msgid "Revision History" diff --git a/physical_infra_provider_rest_api/l10n/zh-CN/main.po b/physical_infra_provider_rest_api/l10n/zh-CN/main.po index 588de41..00f7cca 100644 --- a/physical_infra_provider_rest_api/l10n/zh-CN/main.po +++ b/physical_infra_provider_rest_api/l10n/zh-CN/main.po @@ -1,17 +1,16 @@ -# jsh , 2018. #zanata # tfu , 2018. #zanata msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2018-02-26 09:56+1000\n" +"POT-Creation-Date: 2018-11-22 19:42+1000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"PO-Revision-Date: 2018-03-07 12:36+0000\n" -"Last-Translator: jsh \n" +"PO-Revision-Date: 2018-12-07 03:10+0000\n" +"Last-Translator: myamamot \n" "Language-Team: Chinese (Simplified)\n" "Language: zh_Hans\n" -"X-Generator: Zanata 4.4.3\n" +"X-Generator: Zanata 4.6.2\n" "Plural-Forms: nplurals=1; plural=0\n" msgid "Lenovo Physical Infrastructure Provider REST API" @@ -65,18 +64,6 @@ msgstr "" "若要使用 REST API，您必须以有权访问该 API 的用户身份登录 CloudForms Management Engine API。默认用户为 " "admin，密码为 smartvm。" -msgid "Use the following URL to access the CloudForms REST API:" -msgstr "使用以下 URL 来访问 CloudForms REST API：" - -msgid "<CloudForms_address>:<port>/api" -msgstr "<CloudForms_address>:<port>/api" - -msgid "For example:" -msgstr "例如：" - -msgid "localhost:3000/api" -msgstr "localhost:3000/api" - msgid "Retrieving Provider Details" msgstr "检索供应商详细信息" @@ -84,8 +71,8 @@ msgid "" "To retrieve information for all providers, use the following request URL:" msgstr "若要检索所有供应商的信息，请使用以下请求 URL：" -msgid "GET <CloudForms_address>:<port>/api/providers" -msgstr "GET <CloudForms_address>:<port>/api/providers" +msgid "GET /api/providers" +msgstr "GET /api/providers" msgid "A JSON response with the following keys is returned." msgstr "系统将返回含有下列键的 JSON 回复。" @@ -94,15 +81,15 @@ msgid "" "actions (list of actions that can be used)\n" "count (total number of providers)\n" "name (URI name)\n" -"pages (count of pages)\n" +"pages (number of pages)\n" "resource (list of URLs for each provider that is managed by CloudForms)\n" -"subcount (number of providers returned)" +"subcount (number of providers that were returned)" msgstr "" -"actions (可用操作的列表)\n" -"count (供应商的总数)\n" +"actions (可用操作列表)\n" +"count (供应商总数)\n" "name (URI 名称)\n" "pages (页数)\n" -"resource (受 CloudForms 管理的各个供应商的 URL 的列表 )\n" +"resource (CloudForms 管理的各个供应商的 URL 列表 )\n" "subcount (返回的供应商数目)" msgid "Examples" @@ -115,8 +102,8 @@ msgstr "" "若要检索供应商的所有信息，请使用 ?expand=resources " "查询参数，例如：" -msgid "GET localhost:3000/api/providers?expand=resources" -msgstr "GET localhost:3000/api/providers?expand=resources" +msgid "GET /api/providers?expand=resources" +msgstr "GET /api/providers?expand=resources" msgid "" "To retrieve a specific information about the providers (such as name and " @@ -126,10 +113,8 @@ msgstr "" "若要检索供应商的某一具体信息（如名称和 ID），请使用 ?expand=" "resources&attributes=<attribute_list> 查询参数，例如：" -msgid "" -"GET localhost:3000/ api/providers?expand=resources&attributes=id,name" -msgstr "" -"GET localhost:3000/ api/providers?expand=resources&attributes=id,name" +msgid "GET /api/providers?expand=resources&attributes=id,name" +msgstr "GET /api/providers?expand=resources&attributes=id,name" msgid "" "To retrieve additional information about the providers (such as port, " @@ -141,11 +126,9 @@ msgstr "" "resources&attributes=<attribute_list> 查询参数，例如：" msgid "" -"GET localhost:3000/api/providers?expand=resources&attributes=" -"port,hostname,ipaddress" +"GET /api/providers?expand=resources&attributes=port,hostname,ipaddress" msgstr "" -"GET localhost:3000/api/providers?expand=resources&attributes=" -"port,hostname,ipaddress" +"GET /api/providers?expand=resources&attributes=port,hostname,ipaddress" msgid "" "To retrieve information about only Lenovo physical-infrastructure providers, " @@ -157,26 +140,22 @@ msgstr "" "resources&filter[]=type=<provider_type> 属性，例如：" msgid "" -"GET localhost:3000/api/providers?expand=resources&filter[]=type=ManageIQ:" -":Providers::Lenovo::PhysicalInfraManager" +"GET /api/providers?expand=resources&filter[]=type=ManageIQ::Providers::" +"Lenovo::PhysicalInfraManager" msgstr "" -"GET localhost:3000/api/providers?expand=resources&filter[]=type=ManageIQ:" -":Providers::Lenovo::PhysicalInfraManager" +"GET /api/providers?expand=resources&filter[]=type=ManageIQ::Providers::" +"Lenovo::PhysicalInfraManager" msgid "Retrieving Provider Details by ID" -msgstr "按照 ID 检索供应商详细信息" +msgstr "通过 ID 获取供应商详细信息" msgid "" "To retrieve information for a specific provider, use the following request " "URL where <provider_ID> is the unique identifier of the provider:" msgstr "若要检索特定供应商的信息，请使用以下请求 URL，其中 <provider_ID> 是供应商的唯一标识符：" -msgid "" -"GET <CloudForms_address>:<port>/api/providers/" -"<provider_ID>" -msgstr "" -"GET <CloudForms_address>:<port>/api/providers/" -"<provider_ID>" +msgid "GET /api/providers/<provider_ID>" +msgstr "GET /api/providers/<provider_ID>" msgid "" "href\n" @@ -216,11 +195,11 @@ msgstr "" "<attribute_list> 查询参数，例如：" msgid "" -"GET localhost:3000/api/providers/<provider_ID>?expand=" -"resources&attributes=id,name" +"GET /api/providers/<provider_ID>?expand=resources&attributes=" +"id,name" msgstr "" -"GET localhost:3000/api/providers/<provider_ID>?expand=" -"resources&attributes=id,name" +"GET /api/providers/<provider_ID>?expand=resources&attributes=" +"id,name" msgid "" "To retrieve additional information about the provider (such as port, " @@ -231,10 +210,10 @@ msgstr "" "<attribute_list> 查询参数，例如：" msgid "" -" GET localhost:3000/api/providers/<provider_ID>?expand=resources\n" +"GET /api/providers/<provider_ID>?expand=resources\n" "&attributes=port,hostname,ipaddress" msgstr "" -" GET localhost:3000/api/providers/<provider_ID>?expand=resources\n" +"GET /api/providers/<provider_ID>?expand=resources\n" "&attributes=port,hostname,ipaddress" msgid "Performing physical-infrastructure provider actions" @@ -263,8 +242,8 @@ msgid "" "using the following request URL and JSON request body." msgstr "若要创建 Lenovo 物理基础架构供应商，请使用以下请求 URL 和 JSON 请求正文发送 POST 请求。" -msgid "POST <CloudForms_address>:<port>/api/providers" -msgstr "POST <CloudForms_address>:<port>/api/providers" +msgid "POST /api/providers" +msgstr "POST /api/providers" msgid "Request body:" msgstr "请求正文：" @@ -349,23 +328,15 @@ msgstr "要删除特定的供应商：" msgid "Send a DELETE request using the following request URL." msgstr "使用以下请求 URL 发送 DELETE 请求。" -msgid "" -"DELETE <CloudForms_address>:<port>/api/providers/" -"<provider_ID>" -msgstr "" -"DELETE <CloudForms_address>:<port>/api/providers/" -"<provider_ID>" +msgid "DELETE /api/providers/<provider_ID>" +msgstr "DELETE /api/providers/<provider_ID>" msgid "" "Send a POST request using the following request URL and JSON request body." msgstr "使用以下请求 URL 和 JSON 请求正文发送 POST 请求。" -msgid "" -"POST <CloudForms_address>:<port>/api/providers/" -"<provider_ID>" -msgstr "" -"POST <CloudForms_address>:<port>/api/providers/" -"<provider_ID>" +msgid "POST /api/providers/<provider_ID>" +msgstr "POST /api/providers/<provider_ID>" msgid "{\n" " \"action\":\"delete\"\n" @@ -411,22 +382,22 @@ msgid "" "URL:" msgstr "若要检索所有物理服务器的信息，请使用以下请求 URL：" -msgid "GET <CloudForms_address>:<port>/api/physical_servers" -msgstr "GET <CloudForms_address>:<port>/api/physical_servers" +msgid "GET /api/physical_servers" +msgstr "GET /api/physical_servers" msgid "" "actions (list of actions that can be used)\n" -"count (count of the physical servers)\n" +"count (number of physical servers)\n" "name (URI name)\n" -"pages (count of pages)\n" -"resource (list of URLs of the each physical servers)\n" -"subcount (count of the physical servers returned)" +"pages (number of pages)\n" +"resource (list of URLs for each physical server)\n" +"subcount (number of physical servers that were returned)" msgstr "" -"actions (可用操作的列表)\n" -"count (物理服务器的数量)\n" +"actions (可用操作列表)\n" +"count (物理服务器数量)\n" "name (URI 名称)\n" "pages (页数)\n" -"resource (各物理服务器的 URL 的列表 )\n" +"resource (各个物理服务器的 URL 列表 )\n" "subcount (返回的物理服务器数量)" msgid "" @@ -436,41 +407,65 @@ msgstr "" "若要检索物理服务器的所有信息，请使用 ?expand=resources " "查询参数，例如：" -msgid "GET localhost:3000/api/physical_servers?expand=resources" -msgstr "GET localhost:3000/api/physical_servers?expand=resources" +msgid "GET /api/physical_servers?expand=resources" +msgstr "GET /api/physical_servers?expand=resources" msgid "" -"To retrieve a specific information about the physical servers (such as name " +"To retrieve specific information about the physical servers (such as name " "and ID), use the ?expand=resources&attributes=" "<attribute_list> query parameters, for example:" msgstr "" -"若要检索物理服务器的某一具体信息（如名称和 ID），请使用 ?expand=" +"若要获取物理服务器的某一具体信息（如名称和 ID），请使用 ?expand=" "resources&attributes=<attribute_list> 查询参数，例如：" +msgid "GET /api/physical_servers?expand=resources&attributes=id,name" +msgstr "GET /api/physical_servers?expand=resources&attributes=id,name" + msgid "" -"GET localhost:3000/api/physical_servers?expand=resources&attributes=" -"id,name" +"To retrieve information such as firmware, networks, guest devices, and asset " +"details associated with physical servers, use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" msgstr "" -"GET localhost:3000/api/physical_servers?expand=resources&attributes=" -"id,name" +"若要获取物理服务器的具体信息（如固件、网络、客户机设备以及与物理服务器相关联的资产信息），请使用 ?expand=resources&attributes=<attribute_list> 查询参数，例如：" msgid "" -"To retrieve specific information about the physical servers (such as " -"firmware, networks, guest devices, and asset details), use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +"GET /api/physical_servers?expand=resources&attributes=hardware." +"firmwares,hardware.networks,hardware.guest_devices,hardware.assets_details" +msgstr "" +"GET /api/physical_servers?expand=resources&attributes=hardware." +"firmwares,hardware.networks,hardware.guest_devices,hardware.assets_details" + +msgid "" +"To retrieve information such as network adapters and storage adapters in " +"physical servers, use the ?expand=" +"resources&attributes=<attribute_list> query parameters, " +"for example:" +msgstr "" +"若要获取物理服务中的网络适配器、存储适配器等信息，请使用 ?expand=" +"resources&attributes=<attribute_list> 查询参数，例如：" + +msgid "" +"GET /api/physical_servers?expand=resources&attributes=guest_devices." +"with_ethernet_type,guest_devices.with_storage_type" +msgstr "" +"GET /api/physical_servers?expand=resources&attributes=guest_devices." +"with_ethernet_type,guest_devices.with_storage_type" + +msgid "" +"To retrieve information such as switches connected to physical servers, use " +"the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" msgstr "" -"若要检索物理服务器的具体信息（如固件、网络、客户设备和资源详细信息），请使用 ?expand=" +"若要获取具体信息，例如与物理服务器连接的交换机的信息，请使用 ?expand=" "resources&attributes=<attribute_list> 查询参数，例如：" msgid "" -"GET localhost:3000/api/physical_servers?expand=resources&attributes= " -"hardware.firmwares,hardware.networks,hardware.guest_devices,hardware." -"assets_details" +"GET /api/physical_servers?expand=resources&attributes=physical_switches" msgstr "" -"GET localhost:3000/api/physical_servers?expand=resources&attributes= " -"hardware.firmwares,hardware.networks,hardware.guest_devices,hardware." -"assets_details" +"GET /api/physical_servers?expand=resources&attributes=physical_switches" msgid "" "To retrieve information about only a specific physical server, use the " @@ -482,11 +477,11 @@ msgstr "" "resources&filter[]=name=<server_name> 查询属性，例如：" msgid "" -"GET localhost:3000/api/physical_servers?expand=resources&filter[]=name=" -"Server1-20127X5462" +"GET /api/physical_servers?expand=resources&filter[]=name=Server1-" +"20127X5462" msgstr "" -"GET localhost:3000/api/physical_servers?expand=resources&filter[]=name=" -"Server1-20127X5462" +"GET /api/physical_servers?expand=resources&filter[]=name=Server1-" +"20127X5462" msgid "Retrieving Physical Server Details by ID" msgstr "按照 ID 检索物理服务器详细信息" @@ -496,12 +491,8 @@ msgid "" "request URL:" msgstr "若要检索特定物理服务器的信息，请使用以下请求 URL：" -msgid "" -"GET <CloudForms_address>:<port>/api/physical_servers/" -"<server_ID>" -msgstr "" -"GET <CloudForms_address>:<port>/api/physical_servers/" -"<server_ID>" +msgid "GET /api/physical_servers/<server_ID>" +msgstr "GET /api/physical_servers/<server_ID>" msgid "" "actions\n" @@ -547,39 +538,71 @@ msgstr "" "vendor" msgid "" -"To retrieve a specific information about a specific physical server (such as " -"name and ID), use the ?expand=" -"resources&attributes=<attribute_list> query parameters, " -"for example:" +"To retrieve information about a specific physical server (such as name and " +"ID), use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" msgstr "" -"若要检索特定物理服务器的某一具体信息（如名称和 ID），请使用 ?expand=" +"若要获取一个特定物理服务器的信息（如名称和 ID），请使用 ?expand=" "resources&attributes=<attribute_list> 查询参数，例如：" msgid "" -"GET localhost:3000/api/physical_servers/<server_ID>?expand=" -"resources&attributes=id,name" +"GET /api/physical_servers/<server_ID>?expand=resources&attributes=" +"id,name" msgstr "" -"GET localhost:3000/api/physical_servers/<server_ID>?expand=" -"resources&attributes=id,name" +"GET /api/physical_servers/<server_ID>?expand=resources&attributes=" +"id,name" msgid "" -"To retrieve a specific information about a specific physical server (such as " -"firmware, networks, guest devices, and asset details), use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +"To retrieve information such as firmware, networks, guest devices, and asset " +"details for a specific server, use the ?expand=" +"resources&attributes=<attribute_list> query parameters, " +"for example:" msgstr "" -"若要检索特定物理服务器的具体信息（如固件、网络、客户设备和资源详细信息），请使用 ?expand=" +"若要获取一个特定物理服务器的具体信息（如固件、网络、客户机设备以及资产信息），请使用 ?expand=" "resources&attributes=<attribute_list> 查询参数，例如：" msgid "" -" GET localhost:3000/api/physical_servers/<server_ID>?expand=resources\n" +"GET /api/physical_servers/<server_ID>?expand=resources\n" "&attributes=hardware.firmwares,hardware.networks,hardware." "guest_devices,hardware.assets_details" msgstr "" -" GET localhost:3000/api/physical_servers/<server_ID>?expand=resources\n" +"GET /api/physical_servers/<server_ID>?expand=resources\n" "&attributes=hardware.firmwares,hardware.networks,hardware." "guest_devices,hardware.assets_details" +msgid "" +"To retrieve information such as switches that are connected to a specific " +"server, use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"若要获取具体信息，例如与一个特定物理服务器连接的交换机的信息，请使用 ?expand=" +"resources&attributes=<attribute_list> 查询参数，例如：" + +msgid "" +"GET /api/physical_servers/<server_ID>?expand=resources&attributes=" +"physical_switches" +msgstr "" +"GET /api/physical_servers/<server_ID>?expand=resources&attributes=" +"physical_switches" + +msgid "" +"To retrieve information such as network adapters and storage adapters in a " +"specific physical server, use the ?expand=" +"resources&attributes=<attribute_list> query parameters, " +"for example:" +msgstr "" +"若要获取一个特定物理服务中的网络适配器、存储适配器等信息，请使用 ?expand=" +"resources&attributes=<attribute_list> 查询参数，例如：" + +msgid "" +"GET /api/physical_servers/<server_ID>?expand=resources&attributes=" +"guest_devices.with_ethernet_type,guest_devices.with_storage_type,hardware." +"physical_network_ports" +msgstr "" +"GET /api/physical_servers/<server_ID>?expand=resources&attributes=" +"guest_devices.with_ethernet_type,guest_devices.with_storage_type,hardware." +"physical_network_ports" + msgid "Performing physical server actions" msgstr "执行物理服务器操作" @@ -606,12 +629,8 @@ msgid "" "following request URL and JSON request body." msgstr "若要打开特定物理服务器的电源，请使用以下请求 URL 和 JSON 请求正文发送 POST 请求。" -msgid "" -"POST <CloudForms_address>:<port>/api/physical_servers/" -"<server_ID>" -msgstr "" -"POST <CloudForms_address>:<port>/api/physical_servers/" -"<server_ID>" +msgid "POST /api/physical_servers/<server_ID>" +msgstr "POST /api/physical_servers/<server_ID>" msgid "{\n" " \"action\":\"power_on\"\n" @@ -636,7 +655,7 @@ msgstr "{\n" "}" msgid "Immediately powering off a physical server" -msgstr "立即关闭物理服务器电源" +msgstr "立即关闭一个物理服务器电源" msgid "" "To immediately power off a specific physical server, send a POST request " @@ -699,12 +718,12 @@ msgid "Performing an action on multiple physical servers" msgstr "对多台物理服务器执行操作" msgid "" -"To perform an action on more than one physical severs, send a POST request " +"To perform an action on more than one physical server, send a POST request " "using the following request URL and JSON request body." msgstr "若要对多台物理服务器执行操作，请使用以下请求 URL 和 JSON 请求正文发送 POST 请求。" -msgid "POST <CloudForms_address>:<port>/api/physical_servers" -msgstr "POST <CloudForms_address>:<port>/api/physical_servers" +msgid "POST /api/physical_servers" +msgstr "POST /api/physical_servers" msgid "" "{\n" @@ -726,3 +745,727 @@ msgstr "" " \"href\":\"<server_ID>\"\n" " }]\n" "}" + +msgid "Retrieving Physical Chassis Details" +msgstr "获取物理机箱的详细信息" + +msgid "" +"To retrieve information for all physical chassis, use the following request " +"URL:" +msgstr "若要获取所有物理机箱的信息，请使用以下请求 URL：" + +msgid "GET /api/physical_chassis" +msgstr "GET /api/physical_chassis" + +msgid "" +"actions (list of actions that can be used)\n" +"count (number of physical chassis)\n" +"name (URI name)\n" +"pages (number of pages)\n" +"resources (list of URLs for each physical chassis)\n" +"subcount (number of physical chassis that were returned)" +msgstr "" +"actions (可用操作列表)\n" +"count (物理机箱数量)\n" +"name (URI 名称)\n" +"pages (页数)\n" +"resource (各物理机箱的 URL 的列表 )\n" +"subcount (返回的物理机箱数量)" + +msgid "" +"To retrieve all information about the physical chassis, use the ?expand=resources query parameter, for example:" +msgstr "" +"若要获取物理机箱的所有信息，请使用 ?expand=resources " +"查询参数，例如：" + +msgid "GET /api/physical_chassis?expand=resources" +msgstr "GET /api/physical_chassis?expand=resources" + +msgid "" +"To retrieve specific information about the physical chassis (such as name " +"and ID), use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"若要获取物理机箱的具体信息（如名称和 ID），请使用 ?expand=" +"resources&attributes=<attribute_list> 查询参数，例如：" + +msgid "GET /api/physical_chassis?expand=resources&attributes=id,name" +msgstr "GET /api/physical_chassis?expand=resources&attributes=id,name" + +msgid "" +"To retrieve information such as the switches, storage systems, and servers " +"in a chassis, use the ?expand=" +"resources&attributes=<attribute_list> query parameters, " +"for example:" +msgstr "" +"若要获取如机箱中的交换机、存储系统和服务器的信息，请使用 ?expand=" +"resources&attributes=<attribute_list> 查询参数，例如：" + +msgid "" +"GET /api/physical_chassis?expand=resources&attributes=" +"physical_servers,physical_storages,hardware.connected_physical_switches" +msgstr "" +"GET /api/physical_chassis?expand=resources&attributes=" +"physical_servers,physical_storages,hardware.connected_physical_switches" + +msgid "" +"To retrieve information about only a specific physical chassis, use the " +"?expand=resources&filter[]=name=" +"<chassis_name> query attributes on all physical chassis " +"resources, for example:" +msgstr "" +"若要获取一个特定物理机箱的信息，请使用 ?expand=resources&filter[]=" +"name=<chassis_name> 查询属性，例如：" + +msgid "" +"GET /api/physical_chassis?expand=resources&filter[]=name=" +"SN%23Y034BG16E060" +msgstr "" +"GET /api/physical_chassis?expand=resources&filter[]=name=" +"SN%23Y034BG16E060" + +msgid "Retrieving Physical Chassis Details by ID" +msgstr "通过 ID 获取物理机箱的详细信息" + +msgid "" +"To retrieve information for a specific physical chassis, use the following " +"request URL:" +msgstr "若要获取一个特定物理机箱的信息，请使用以下请求 URL：" + +msgid "GET /api/physical_chassis/<chassis_ID>" +msgstr "GET /api/physical_chassis/<chassis_ID>" + +msgid "" +"href\n" +"id\n" +"ems_id\n" +"uid_ems\n" +"ems_ref\n" +"physical_rack_id\n" +"name\n" +"vendor\n" +"type\n" +"location_led_state\n" +"health_state\n" +"overall_health_state\n" +"management_module_slot_count\n" +"switch_slot_count\n" +"fan_slot_count\n" +"blade_slot_count\n" +"powersupply_slot_count\n" +"actions" +msgstr "" +"href\n" +"id\n" +"ems_id\n" +"uid_ems\n" +"ems_ref\n" +"physical_rack_id\n" +"name\n" +"vendor\n" +"type\n" +"location_led_state\n" +"health_state\n" +"overall_health_state\n" +"management_module_slot_count\n" +"switch_slot_count\n" +"fan_slot_count\n" +"blade_slot_count\n" +"powersupply_slot_count\n" +"actions" + +msgid "" +"To retrieve information about a specific physical chassis (such as name and " +"ID), use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"若要获取一个特定物理机箱的信息（如名称和 ID），请使用 ?expand=" +"resources&attributes=<attribute_list> 查询参数，例如：" + +msgid "" +"GET /api/physical_chassis/<chassis_ID>?expand=resources&attributes=" +"id,name" +msgstr "" +"GET /api/physical_chassis/<chassis_ID>?expand=resources&attributes=" +"id,name" + +msgid "" +"To retrieve information, such as the switches, storage systems, and servers " +"that are in a specific physical chassis, use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" +"若要获取如一个特定物理机箱中的交换机、存储系统和服务器的信息，请使用 ?expand=" +"resources&attributes=<attribute_list> 查询参数，例如：" + +msgid "" +"GET /api/physical_chassis/<chassis_ID>?expand=resources&attributes=" +"physical_servers,physical_storages,hardware.connected_physical_switches" +msgstr "" +"GET /api/physical_chassis/<chassis_ID>?expand=resources&attributes=" +"physical_servers,physical_storages,hardware.connected_physical_switches" + +msgid "Performing physical chassis actions" +msgstr "执行物理机箱操作" + +msgid "" +"You can use the REST API to perform management tasks on a physical chassis, " +"such as changing the location LED state." +msgstr "您可以使用 REST API 对物理机箱执行管理任务，如更改位置 LED 状态。" + +msgid "" +"Note: To perform actions on physical " +"chassis, you must create a basic authentication using your preferred tool or " +"library, and enter your user name and password to access the CloudForms REST " +"API." +msgstr "" +"注意：要对物理机箱执行操作，您必须使用您首选的工具或库创建基本的身份验证信息，并输入您的用户名和密码来访问 CloudForms REST " +"API。" + +msgid "Changing the location LED state on a physical chassis to blinking" +msgstr "将物理机箱的位置 LED 状态更改为闪烁" + +msgid "" +"To change the location LED state to blinking on a specific chassis, send a " +"POST request using the following request URL and JSON request body." +msgstr "若要将特定机箱的位置 LED 状态更改为闪烁，请使用以下请求 URL 和 JSON 请求正文发送 POST 请求。" + +msgid "POST /api/physical_chassis/<chassis_ID>" +msgstr "POST /api/physical_chassis/<chassis_ID>" + +msgid "Performing an action on multiple physical chassis" +msgstr "对多台物理机箱执行操作" + +msgid "" +"To perform an action on more than one physical chassis, send a POST request " +"using the following request URL and JSON request body." +msgstr "若要对多台物理机箱执行操作，请使用以下请求 URL 和 JSON 请求正文发送 POST 请求。" + +msgid "POST /api/physical_chassis" +msgstr "POST /api/physical_chassis" + +msgid "" +"{\n" +" \"action\":\"<action>\",\n" +" \"resources\": [{\n" +" \"href\":\"<chassis_ID>\"\n" +" },\n" +" {\n" +" \"href\":\"<chassis_ID>\"\n" +" }]\n" +"}" +msgstr "" +"{\n" +" \"action\":\"<action>\",\n" +" \"resources\": [{\n" +" \"href\":\"<chassis_ID>\"\n" +" },\n" +" {\n" +" \"href\":\"<chassis_ID>\"\n" +" }]\n" +"}" + +msgid "Retrieving Physical Rack Details" +msgstr "获取物理机架的详细信息" + +msgid "" +"To retrieve information for all physical racks, use the following request " +"URL:" +msgstr "若要获取所有物理机架的信息，请使用以下请求 URL：" + +msgid "GET /api/physical_racks" +msgstr "GET /api/physical_racks" + +msgid "" +"actions (list of actions that can be used)\n" +"count (number of physical racks)\n" +"name (URI name)\n" +"pages (number of pages)\n" +"resources (list of URLs for each physical rack)\n" +"subcount (number of physical racks that were returned)" +msgstr "" +"actions (可用操作列表)\n" +"count (物理机架数量)\n" +"name (URI 名称)\n" +"pages (页数)\n" +"resource (各物理机架的 URL 列表 )\n" +"subcount (返回的物理机架数量)" + +msgid "" +"To retrieve all information about the physical racks, use the ?expand=resources query parameter, for example:" +msgstr "" +"若要检索物理机架的所有信息，请使用 ?expand=resources " +"查询参数，例如：" + +msgid "GET /api/physical_racks?expand=resources" +msgstr "GET /api/physical_racks?expand=resources" + +msgid "" +"To retrieve specific information about the physical racks (such as name and " +"ID), use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"若要获取物理机架的具体信息（如名称和 ID），请使用 ?expand=" +"resources&attributes=<attribute_list> 查询参数，例如：" + +msgid "GET /api/physical_racks?expand=resources&attributes=id,name" +msgstr "GET /api/physical_racks?expand=resources&attributes=id,name" + +msgid "" +"To retrieve information about only a specific physical rack, use the " +"?expand=resources&filter[]=name=" +"<rack_name> query attributes on all physical rack " +"resources, for example:" +msgstr "" +"若要获取某个特定物理机架的相关信息，请对所有物理机架资源使用 ?expand=" +"resources&filter[]=name=<rack_name> 查询属性，例如：" + +msgid "GET /api/physical_racks?expand=resources&filter[]=name=rack-2" +msgstr "GET /api/physical_racks?expand=resources&filter[]=name=rack-2" + +msgid "Retrieving Physical Rack Details by ID" +msgstr "通过 ID 获取物理机架的详细信息" + +msgid "" +"To retrieve information for a specific physical rack, use the following " +"request URL:" +msgstr "若要获取一个特定物理机架的信息，请使用以下请求 URL：" + +msgid "GET /api/physical_racks/<rack_ID>" +msgstr "GET /api/physical_racks/<rack_ID>" + +msgid "actions\n" +"ems_id\n" +"ems_ref\n" +"href\n" +"id\n" +"name\n" +"uid_ems" +msgstr "actions\n" +"ems_id\n" +"ems_ref\n" +"href\n" +"id\n" +"name\n" +"uid_ems" + +msgid "" +"To retrieve information about a specific physical rack (such as name and " +"ID), use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"若要检索特定物理机架的信息（如名称和 ID），请使用 ?expand=" +"resources&attributes=<attribute_list> 查询参数，例如：" + +msgid "" +"GET /api/physical_racks/<rack_ID>?expand=resources&attributes=" +"id,name" +msgstr "" +"GET /api/physical_racks/<rack_ID>?expand=resources&attributes=" +"id,name" + +msgid "Retrieving Physical Storage Details" +msgstr "获取物理存储详细信息" + +msgid "" +"To retrieve information for all physical storage systems, use the following " +"request URL:" +msgstr "若要检索所有物理存储系统的信息，请使用以下请求 URL：" + +msgid "GET /api/physical_storages" +msgstr "GET /api/physical_storages" + +msgid "" +"actions (list of actions that can be used)\n" +"count (number of physical storage systems)\n" +"name (URI name)\n" +"pages (number of pages)\n" +"resources (list of URLs for each physical storage system)\n" +"subcount (number of physical storage systems that were returned)" +msgstr "" +"actions (可用操作列表)\n" +"count (物理存储系统的数量)\n" +"name (URI 名称)\n" +"pages (页数)\n" +"resource (各物理存储系统的 URL 列表 )\n" +"subcount (返回的物理存储系统数量)" + +msgid "" +"To retrieve all information about the physical storage systems, use the " +"?expand=resources query parameter, for " +"example:" +msgstr "" +"若要检索物理存储系统的所有信息，请使用 ?expand=resources " +"查询参数，例如：" + +msgid "GET /api/physical_storages?expand=resources" +msgstr "GET /api/physical_storages?expand=resources" + +msgid "" +"To retrieve specific information about the physical storage systems (such as " +"name and ID), use the ?expand=" +"resources&attributes=<attribute_list> query parameters, " +"for example:" +msgstr "" +"若要检索物理存储系统的具体信息（如名称和 ID），请使用 ?expand=" +"resources&attributes=<attribute_list> 查询参数，例如：" + +msgid "GET /api/physical_storages?expand=resources&attributes=id,name" +msgstr "GET /api/physical_storages?expand=resources&attributes=id,name" + +msgid "" +"To retrieve information such as canisters and physical disks associated with " +"physical storage systems, use the ?expand=" +"resources&attributes=<attribute_list> query parameters, " +"for example:" +msgstr "" +"若要检索与物理存储系统关联的机箱和物理磁盘等信息，请使用 ?expand=" +"resources&attributes=<attribute_list> 查询参数，例如：" + +msgid "" +"GET /api/physical_storages?expand=resources&attributes=" +"canisters,physical_disks" +msgstr "" +"GET /api/physical_storages?expand=resources&attributes=" +"canisters,physical_disks" + +msgid "" +"To retrieve information about only a specific physical storage system, use " +"the ?expand=resources&filter[]=name=" +"<storage_name> query attributes on all physical storage " +"resources, for example:" +msgstr "" +"若要检索仅与特定物理存储系统相关的信息，请对所有物理存储资源使用 ?expand=" +"resources&filter[]=name=<storage_name> 查询属性，例如：" + +msgid "" +"GET /api/physical_storages?expand=resources&filter[]=name=SeagateV1-" +"S3200-DM" +msgstr "" +"GET /api/physical_storages?expand=resources&filter[]=name=SeagateV1-" +"S3200-DM" + +msgid "Retrieving Physical Storage Details by ID" +msgstr "通过 ID 获取物理存储详细信息" + +msgid "" +"To retrieve information for a specific physical storage system, use the " +"following request URL:" +msgstr "若要获取一个特定物理存储系统的信息，请使用以下请求 URL：" + +msgid "GET /api/physical_storages/<storage_ID>" +msgstr "GET /api/physical_storages/<storage_ID>" + +msgid "" +"access_state\n" +"actions\n" +"canister_slots\n" +"drive_bays\n" +"ems_id\n" +"ems_ref\n" +"enclosures\n" +"health_state\n" +"href\n" +"id\n" +"name\n" +"overall_health_state\n" +"physical_chassis_id\n" +"physical_rack_id\n" +"type\n" +"uid_ems" +msgstr "" +"access_state\n" +"actions\n" +"canister_slots\n" +"drive_bays\n" +"ems_id\n" +"ems_ref\n" +"enclosures\n" +"health_state\n" +"href\n" +"id\n" +"name\n" +"overall_health_state\n" +"physical_chassis_id\n" +"physical_rack_id\n" +"type\n" +"uid_ems" + +msgid "" +"To retrieve information about a specific physical storage system (such as " +"name and ID), use the ?expand=" +"resources&attributes=<attribute_list> query parameters, " +"for example:" +msgstr "" +"若要检索特定物理存储系统的信息（如名称和 ID），请使用 ?expand=" +"resources&attributes=<attribute_list> 查询参数，例如：" + +msgid "" +"GET /api/physical_storages/<storage_ID>?expand=" +"resources&attributes=id,name" +msgstr "" +"GET /api/physical_storages/<storage_ID>?expand=" +"resources&attributes=id,name" + +msgid "" +"To retrieve information, such as canisters and physical disks that are " +"associated with a specific physical storage system, use the ?expand=resources&attributes=<attribute_list> query parameters, for example:" +msgstr "" +"若要检索与特定物理存储系统关联的机箱和物理磁盘等信息，请使用 ?expand=" +"resources&attributes=<attribute_list> 查询参数，例如：" + +msgid "" +"GET /api/physical_storages/<storage_ID>?expand=" +"resources&attributes=canisters,physical_disks" +msgstr "" +"GET /api/physical_storages/<storage_ID>?expand=" +"resources&attributes=canisters,physical_disks" + +msgid "Retrieving Physical Switch Details" +msgstr "检索物理交换机详细信息" + +msgid "" +"To retrieve information for all physical switches, use the following request " +"URL:" +msgstr "若要获取所有物理交换机的信息，请使用以下请求 URL：" + +msgid "GET /api/physical_switches" +msgstr "GET /api/physical_switches" + +msgid "" +"actions (list of actions that can be used)\n" +"count (number of physical switches)\n" +"name (URI name)\n" +"pages (count of pages)\n" +"resources (list of URLs for each physical switch)\n" +"subcount (number of physical switches that were returned)" +msgstr "" +"actions (可用操作列表)\n" +"count (物理交换机数量)\n" +"name (URI 名称)\n" +"pages (页数)\n" +"resource (各物理交换机的 URL 列表 )\n" +"subcount (返回的物理交换机数量)" + +msgid "" +"To retrieve all information about the physical switches, use the ?expand=resources query parameter, for example:" +msgstr "" +"若要检索物理交换机的所有信息，请使用 ?expand=resources " +"查询参数，例如：" + +msgid "GET /api/physical_switches?expand=resources" +msgstr "GET /api/physical_switches?expand=resources" + +msgid "" +"To retrieve specific information about the physical switches (such as name " +"and ID), use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"若要检索物理交换机的具体信息（如名称和 ID），请使用 ?expand=" +"resources&attributes=<attribute_list> 查询参数，例如：" + +msgid "GET /api/physical_switches?expand=resources&attributes=id,name" +msgstr "GET /api/physical_switches?expand=resources&attributes=id,name" + +msgid "" +"To retrieve information such as ports on physical switches, use the " +"?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"若要获取具体信息，例如物理交换机上的端口，请使用 ?expand=" +"resources&attributes=<attribute_list> 查询参数，例如：" + +msgid "" +"GET /api/physical_switches?expand=resources&attributes=" +"physical_network_ports" +msgstr "" +"GET /api/physical_switches?expand=resources&attributes=" +"physical_network_ports" + +msgid "" +"To retrieve information such as physical devices connected to physical " +"switches, use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"若要检索具体信息，例如连接至物理交换机的物理设备，请使用 ?expand=" +"resources&attributes=<attribute_list> 查询参数，例如：" + +msgid "" +"GET /api/physical_switches?expand=resources&attributes=" +"connected_components" +msgstr "" +"GET /api/physical_switches?expand=resources&attributes=" +"connected_components" + +msgid "" +"To retrieve information about only a specific physical switch, use the " +"?expand=resources&filter[]=name=" +"<switch_name> query attributes on all physical switch " +"resources, for example:" +msgstr "" +"若要获取与某个特定物理交换机相关的信息，请对所有物理交换机资源使用 ?expand=" +"resources&filter[]=name=<switch_name> 查询属性，例如：" + +msgid "" +"GET /api/physical_switches?expand=resources&filter[]=name=IO Module 02" +msgstr "" +"GET /api/physical_switches?expand=resources&filter[]=name=IO Module 02" + +msgid "Retrieving Physical Switch Details by ID" +msgstr "按照 ID 获取物理交换机详细信息" + +msgid "" +"To retrieve information for a specific physical switch, use the following " +"request URL:" +msgstr "若要获取某个特定物理交换机的信息，请使用以下请求 URL：" + +msgid "GET /api/physical_switches/<switch_ID>" +msgstr "GET /api/physical_switches/<switch_ID>" + +msgid "" +"actions\n" +"allow_promiscuous\n" +"ems_id\n" +"forged_transmits\n" +"health_state\n" +"href\n" +"id\n" +"mac_changes\n" +"mtu\n" +"name\n" +"ports\n" +"power_state\n" +"shared\n" +"switch_uuid\n" +"type\n" +"uid_ems" +msgstr "" +"actions\n" +"allow_promiscuous\n" +"ems_id\n" +"forged_transmits\n" +"health_state\n" +"href\n" +"id\n" +"mac_changes\n" +"mtu\n" +"name\n" +"ports\n" +"power_state\n" +"shared\n" +"switch_uuid\n" +"type\n" +"uid_ems" + +msgid "" +"To retrieve information about a specific physical switch (such as name and " +"ID), use the ?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"若要获取一个特定物理交换机的信息（如名称和 ID），请使用 ?expand=" +"resources&attributes=<attribute_list> 查询参数，例如：" + +msgid "" +"GET /api/physical_switches/<switch_ID>?expand=resources&attributes=" +"id,name" +msgstr "" +"GET /api/physical_switches/<switch_ID>?expand=resources&attributes=" +"id,name" + +msgid "" +"To retrieve information such as physical devices that are connected to a " +"specific physical switch, use the ?expand=" +"resources&attributes=<attribute_list> query parameters, " +"for example:" +msgstr "" +"若要获取具体信息，例如连接至某个特定物理交换机的物理设备，请使用 ?expand=" +"resources&attributes=<attribute_list> 查询参数，例如：" + +msgid "" +"GET /api/physical_switches/<switch_ID>?expand=resources&attributes=" +"connected_components" +msgstr "" +"GET /api/physical_switches/<switch_ID>?expand=resources&attributes=" +"connected_components" + +msgid "" +"To retrieve information such as ports on a specific physical switch, use the " +"?expand=resources&attributes=" +"<attribute_list> query parameters, for example:" +msgstr "" +"若要获取具体信息，例如特定物理交换机上的端口，请使用 ?expand=" +"resources&attributes=<attribute_list> 查询参数，例如：" + +msgid "" +"GET /api/physical_switches/<switch_ID>?expand=resources&attributes=" +"physical_network_ports" +msgstr "" +"GET /api/physical_switches/<switch_ID>?expand=resources&attributes=" +"physical_network_ports" + +msgid "Performing physical switch actions" +msgstr "执行物理交换机操作" + +msgid "" +"You can use the REST API to perform management tasks on a physical switch, " +"such as restarting the switch." +msgstr "您可以使用 REST API 对一个特定物理交换机执行管理任务，如重启交换机。" + +msgid "" +"Note: To perform actions on physical " +"switch, you must create a basic authentication using your preferred tool or " +"library, and enter your user name and password to access the CloudForms REST " +"API." +msgstr "" +"注意：要对物理交换机执行操作，您必须使用您首选的工具或库创建基本的身份验证信息，再输入您的用户名和密码来访问 CloudForms REST " +"API。" + +msgid "Restarting a physical switch" +msgstr "重启一个物理交换机" + +msgid "" +"To restart a specific switch, send a POST request using the following " +"request URL and JSON request body." +msgstr "若要重启一个特定的交换机，请使用以下请求 URL 和 JSON 请求正文发送 POST 请求。" + +msgid "POST /api/physical_switches/<switch_ID>" +msgstr "POST /api/physical_switches/<switch_ID>" + +msgid "Performing an action on multiple physical switches" +msgstr "对多台物理交换机执行操作" + +msgid "" +"To perform an action on more than one physical switch, send a POST request " +"using the following request URL and JSON request body." +msgstr "若要对多台物理交换机执行操作，请使用以下请求 URL 和 JSON 请求正文发送 POST 请求。" + +msgid "POST /api/physical_switches" +msgstr "POST /api/physical_switches" + +msgid "" +"{\n" +" \"action\":\"<action>\",\n" +" \"resources\": [{\n" +" \"href\":\"<switch_ID>\"\n" +" },\n" +" {\n" +" \"href\":\"<switch_ID>\"\n" +" }]\n" +"}" +msgstr "" +"{\n" +" \"action\":\"<action>\",\n" +" \"resources\": [{\n" +" \"href\":\"<switch_ID>\"\n" +" },\n" +" {\n" +" \"href\":\"<switch_ID>\"\n" +" }]\n" +"}"