Currently, when LXCA deploys an OS to a target, the corresponding "Deploy OS image" job on the Jobs page doesn't list anywhere the actual OS name/type/etc that was deployed. Opening the individual job only shows the image in a cryptic name, such as "/dump/xcat/faketftp/xcat/isos/node1C17C7DC46F.iso". While this may be useful information for the support and development teams, this is rather pointless and frustrating info for a customer. who is the primary consumer of the Jobs webpage.
The feature request is to show the actual OS name that was deployed. For example, "win2012r2-x86_64-install-Datacenter". LXCA certainly has access to this information because it is shown as the "OS Name" on the Manage and Deploy OS Images pages.
This feature would be useful so that customers can keep an accurate record of what OS images were deployed, to what targets, and on what date. All they see today is that on date X, some type of OS was deployed to target Y. Furthermore, having the OS name in the exported jobs .csv spreadsheet would be very useful for IT engineers who have to present charts/metrics/etc. to management.
Thanks for your consideration.
I would be nice to be able to just point so a folder which contains all the downloaded drivers and then Xclarity could import them, instead of me having to identify then individually, then extrack them and so on.
Or the ability to select the machine type and then Xclarity would download the drivers directly from Lenovo, without the middle interaction of downloading to a workstation.
It would be nice to acknowledg an error, so that the status or job indicator sign is going back to green.
Today, I have to delete the job with the fault to go back to the green status and so some importent information is lost.
as for Today, if the xClarity is not sync with the server and you start OS deployment, it fail because the xClarity send the wrong power action to the server.
why is it depend on the server power state?!? or maybe its a bug...
Not sync = the server is ON but xClarity server didn't acknowledge it yet, it still show that the server is OFF
since 8.4.3 f for CN4093 and similar switches, its not possible to access the switch if it has connection issue to xClarity server.
Its possible to access to the CMM/IMM using the Recovery_ID user.
Why isn't it possible to use this user to access the switch in case of a connection issue to the xClarity?
From the IMM its possible to boot the server from any state (ON/Off) to BIOS,
but from xClarity its only possible to restart the server to BIOS only if it acknowledge that the server is ON.
If the server is OFF you need to turn it on, than wait for xClarity to refresh the server state and only than you can boot the server to BIOS.
We have three different NTP servers in our environment. For high availability reasons it would be great to configure at least two NTP servers in Lenovo XClarity. As far as I know, it is only possible to enter one NTP server at the moment (v 1.3.0).
Customer requirement request. Provide for the ability to import a pool of IMM FOD keys; also request for an Enterprise level IMM FOD key that covers a certain number of endpoints. Once the keys are imported or downloaded, XClarity Administrator should be able to distribute this key or set of keys to the desired system IMM's. Would also like the ability to easily deactivate a key on one system, so that it could be used on a different system if the user deems that the advanced function is no longer needed/desired on a system (floating pool was how it was explained)
Request from customer. Add the ability to centrally manage user accounts for the IMM/CMM and push updates to endpoints. This would include the ability to push new passwords to these devices for those clients that are on a schedule in which they must change passwords. That includes the ability to update the password for the RECOVERY_ID account created when using centralized management. This would be very beneficial in sceanrios where the endpoint is configured with the "Secure" security policy in which password expiration is enforced.
Add the ability to use standard LDAP servers for authentication within XClarity Administrator. Today, the only external LDAP solution supported is Microsoft Active Directory. This requirement came from a customer.
Currently LXCA is issuing certificates to managed endpoints with self signed root CA, it would be nice to have option to act as subordinate of the signed root CA
Add a view within XClarity Administrator that allows the admin to view the history of firmware applied to a system (all components) along with the current firmware applied within that same view. Of course this information should be able to be exported. All supported APIs and scripting tools (REST, PowerShell etc..) should also be able to extract this information.
Recently, I tried to add xclarity integrator to our test vcenter that is running vcenter 6.0 behind a vmware platform service controller. We have a total of 4 vcenters, all behind the same platform service controller for our vdi environment per design from vmware. so here is the issue:
for testing, i only wanted to have my test environment see the xclarity integrator in the web client. i was not tryng to add the integrator to all my other vcenters at this time. Howeve, it appears that the web client for vcenter is trying to apply the lxci to all my vcenters
here is my question to the powers that be
since vmware is heading the way of allowing multiple vcenters to be under 1 psc, is there a way to lxca to manage all vcenters in a psc or web client? forgive me for the poor wording of the question....
please reach out if you have any further questions
Allow for creation of a Policy that can be assigned to a Flex chassis bay/bays that results in automatic firmware update provisioning, assign server profile, and install Operating system as soon as a compute node is inserted into a Flex chassis bay.