intel / intelrsd Goto Github PK

Intel® Rack Scale Design Reference Software

Shell 0.34% Java 16.36% C++ 66.22% Python 7.27% CMake 2.40% C 5.02% Makefile 0.13% JavaScript 1.87% CSS 0.02% Perl 0.05% HTML 0.04% Groovy 0.10% Dockerfile 0.01% Smarty 0.01% Kotlin 0.13% ANTLR 0.01% Mustache 0.05%

intel-rsd intel-rack-scale

intelrsd's Introduction

DISCONTINUATION OF PROJECT.

This project will no longer be maintained by Intel.

Intel has ceased development and contributions including, but not limited to, maintenance, bug fixes, new releases, or updates, to this project.

Intel no longer accepts patches to this project.

If you have an ongoing need to use this project, are interested in independently developing it, or would like to maintain patches for the open source software community, please create your own fork of this project.

Intel^® Rack Scale Design Reference Software

Intel^® Rack Scale Design (Intel^® RSD) reference software is a logical architecture that disaggregates compute, storage, and network resources while introducing the ability to more efficiently pool and utilize these resources. Intel^® RSD software APIs simplify resource management and provide the ability to dynamically compose resources based on workload-specific demands.

Getting Started

This repository is a good starting point for developers who are interested in working with Intel^® RSD reference software, and are interesten in building an Intel^® RSD complaint implementation. Before you begin work on your own design solution, we recommend reading the available documentation at the official Intel RSD site.

Note: This code is reference software only and we expect developers to adapt it to their needs.

Documents

Any documents referred to in this ReadMe document can be found at the official Intel^® RSD site.

Support

For questions, concerns, or defects found in the in the current Intel^® RSD reference software, create a new issue in this repository. If your questions are about a previous release, include the software version in your topic.

Note: When creating a new issue, try to include additional information such as log files, REST API dumps or other operating system information to expedite response time.

News

Coming Soon: Automation through Ansible Galaxy*

Preliminary support for automating the provisioning of RSD hardware via Ansible is available at Ansible Galaxy, enabling users to easily compose and boot an entire datacenter cluster. It comes in the form of Ansible Role named ‘rsd-provisioning’ and can be found through the search page, for example, by using the “RSD” keyword, or by looking up "Intel contributions" in the advanced search form. This Ansible Role comes with an initial set of modules for the following operations: composition and deletion, booting and power option controls. More information on their usage and full set of available options can be found in the associated README file.

At the time of writing the aforementioned modules are being proposed to the community, to be made available through the standard Ansible distribution under the “Remote Management” category. These modules are currently pending review and approval, the final location and acceptance is subject to change without notice.

[July 2019] v2.5 of the Intel^® RSD reference software has been released!

This release is based on the Redfish^® specification v1.6.1. It uses the Redfish^® Schema v2018.3 and Swordfish^® Schema v1.0.7a.

The interfaces for various resources are enhanced with Intel^® RSD extensions.

Below is a list of the most important features added in this software version:

Compute Log Service - records from the System Events Log on a platform are now presented in a Redfish LogService.
CTS includes support for Redfish^® metadata 2019.1 (with Swordfish 1.0.7, included in Redfish Metadata 2018.3 & 2019.1) in regular tests and support for Rack Scale & OCP^® profiles.

[April 2019] v2.4 of the Intel^® RSD reference software has been released!

This release is based on the Redfish^® specification v1.5.0. It uses the Redfish^® Schema v2018.1 and Swordfish^® Schema v1.0.6. The exceptions are as follows:

the interface for Manager and Memory resources is based on Redfish^® Schema v2018.2.
the interface for FPGA is based on a Redfish^® WIP IS0007.
the interface for Telemetry is based on a Redfish^® WIP DSP2051.
the interfaces for various resources are enhanced with Intel^® Rack Scale Design extensions.

Below is a list of the most important features added in this software version:

FPGA Pooling over Fabrics

Enables composition of nodes connected to FPGAs via Remote Direct Memory Access (RDMA) over Converged Ethernet protocol through the Top of Rack switches (TORs) or leaf switches.
FPGA Pooling over PCIe

Enables composition of nodes connected to FPGAs via a PCIe Switch.
Optane DC Persistent Memory management

Enables discovery of Optane DC Persistent Memory modules and composition of nodes containing those modules.
Redfish authentication

The RSD services now conform to Redfish* requirements for authentication.
High Availability

PODM High Availability is provided by the Kubernetes* platform, which allows for running multiple instances of PODM components. In case of failure of some instance, other nodes of cluster will take over and Kubernetes will bring back online the missing instance - without disrupting PODM functions.

[September 2018] v2.3.2 of the Intel^® RSD reference software has been released!

Important change to the new software version:

Added the NVMe Initiator Wheel script (nvme-wheel)

An initiator host polls the Discovery Service to ensure that its connections to remote volumes are up-to-date. And the NVMe Intiator Wheel script, nvme-wheel, is a tool that performs these actions.

NVMe-Wheel is located here

[July 2018] v2.3.1 of the Intel^® RSD reference software has been released!

Important change to the new software version:

Updated the Conformance Test Suite (CTS)

A new set of CRUD tests designed to verify NVMe* over Fabrics (NVMe-oF) operations has been added.

[May 2018] v2.3 of the Intel^® RSD reference software has been released!

Below is a list of the most important changes to the new software version:

NVMe* over Fabrics (NVMe-oF)

Enables composition of nodes connected to NVM Express (NVMe)* drives via Remote Direct Memory Access (RDMA) over Converged Ethernet protocol through the Top of Rack switches (TORs) or leaf switches.
Quality of Service (QoS)

Supports setting some QoS parameters to configure the leaf switches. It is required to allocate the capability of a network for selected network traffic over Ethernet. NVMe-oF is one of the traffic types that requires an appropriate level of network resources to be allocated.
Standards-Based Storage Management

The Intel^® RSD Storage Services REST API is aligned to the Storage Networking Industry Association (SNIA) Swordfish* specification.

Disclaimer

This code is reference software only and is not feature complete. Intel^® makes no claims for the quality or completeness of this code.

Intel, the Intel logo, are trademarks of Intel Corporation or its subsidiaries in the U.S. and/or other countries.

Copies of documents that have an order number and are referenced in this document may be obtained by calling 1 800 548 4725 or by visiting www.intel.com/design/literature.htm.

*Other names and brands may be claimed as the property of others. (when using third-party trademarks and names)

intelrsd's People

Contributors

Stargazers

Watchers

intelrsd's Issues

Problem - PSME Compute Agent encrypt and decrypt functions fail

Dear intel -
the issue is related to #48,
Questions how PSME compute agent send IPMI commands to BMC AST2400 2500 and remove CY7C65215 ,

../../agent/compute/psme-key and /etc/psme/psme-key are the same files,
but PSME Compute Agent encrypt and decrypt functions still fail,
the detail steps are in the following comment,
Please support, thank you.
House

iSCSI boot does not work with OS RHEL7.4/7.3

Hi,
I install RHEL7.4 or RHEL7.3 on an iSCSI target, and then iSCSI boot from the target with a composed node. It hangs at "Booting from SAN device 0x80" forever as the following picture,

Is there any suggestion for this issue?

Thanks,
Andy

ServiceRemovalTask task finished exceptionally

Dear Intel,

Now I use pod-manager 2.1.3, and I occasionally get "ServiceRemovalTask task finished exceptionally" error. after I get this error message, I must need to restart pod-manager.

It seems ServiceRemovalTask cannot get singleton bean "DiscoveryScheduler "'s lock.
Do you have plan to fix the issue?
or Can you give me some suggestions to handle this error?

exception message:
2018-01-29 23:58:04,744 [EE-ManagedScheduledExecutorService-TasksExecutor-Thread-1] ERROR c.i.p.c.s.TaskCoordinatorImpl - Scheduled 'ServiceRemovalTask$Proxy$_$$WeldSubclass' task finished exceptionally. Will not be scheduled again.
javax.ejb.ConcurrentAccessTimeoutException: WFLYEJB0241: EJB 3.1 PFD2 4.8.5.5.1 concurrent access timeout on DiscoveryScheduler - could not obtain lock within 5000MILLISECONDS
at org.jboss.as.ejb3.concurrency.ContainerManagedConcurrencyInterceptor.processInvocation(ContainerManagedConcurrencyInterceptor.java:106) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) ~[na:na]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) ~[na:na]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) ~[na:na]
at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:636) ~[na:na]
at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) ~[na:na]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) ~[na:na]
at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) ~[na:na]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) ~[na:na]
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195) ~[na:na]
at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) ~[na:na]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) ~[na:na]
at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) ~[na:na]
at com.intel.podm.discovery.external.DiscoveryScheduler$$$view13.cancel(Unknown Source) ~[podm-discovery-2.1.3.4.0.jar:na]
at sun.reflect.GeneratedMethodAccessor1426.invoke(Unknown Source) ~[na:na]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_111]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_111]
at org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:436) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:127) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at com.intel.podm.discovery.external.DiscoveryScheduler$Proxy$$$Weld$EnterpriseProxy$.cancel(Unknown Source) ~[podm-discovery-2.1.3.4.0.jar:na]
at com.intel.podm.discovery.external.ServiceRemovalTask.run(ServiceRemovalTask.java:63) ~[podm-discovery-2.1.3.4.0.jar:na]
at com.intel.podm.discovery.external.ServiceRemovalTask$Proxy$$$WeldSubclass.run$$super(Unknown Source) ~[podm-discovery-2.1.3.4.0.jar:na]
at sun.reflect.GeneratedMethodAccessor330.invoke(Unknown Source) ~[na:na]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_111]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_111]
at org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:49) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:77) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.invokeInOurTx(TransactionalInterceptorBase.java:117) ~[narayana-jts-idlj-5.2.12.Final.jar!/:5.2.12.Final (revision: f6563)]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequiresNew.doIntercept(TransactionalInterceptorRequiresNew.java:60) ~[narayana-jts-idlj-5.2.12.Final.jar!/:5.2.12.Final (revision: f6563)]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.intercept(TransactionalInterceptorBase.java:76) ~[narayana-jts-idlj-5.2.12.Final.jar!/:5.2.12.Final (revision: f6563)]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequiresNew.intercept(TransactionalInterceptorRequiresNew.java:47) ~[narayana-jts-idlj-5.2.12.Final.jar!/:5.2.12.Final (revision: f6563)]
at sun.reflect.GeneratedMethodAccessor312.invoke(Unknown Source) ~[na:na]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_111]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_111]
at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:74) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at com.intel.podm.discovery.external.ServiceRemovalTask$Proxy$$$_WeldSubclass.run(Unknown Source) ~[podm-discovery-2.1.3.4.0.jar:na]
at com.intel.podm.common.synchronization.TaskCoordinatorImpl.lambda$scheduleWithFixedDelay$0(TaskCoordinatorImpl.java:81) ~[synchronization-2.1.3.4.0.jar:na]
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1626) ~[na:1.8.0_111]
at com.codahale.metrics.InstrumentedScheduledExecutorService$InstrumentedRunnable.run(InstrumentedScheduledExecutorService.java:235) ~[metrics-core-3.1.2.jar:3.1.2]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[na:1.8.0_111]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_111]
at org.glassfish.enterprise.concurrent.internal.ManagedFutureTask.run(ManagedFutureTask.java:141) ~[javax.enterprise.concurrent-1.0.jar!/:na]
at org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$101(ManagedScheduledThreadPoolExecutor.java:383) ~[javax.enterprise.concurrent-1.0.jar!/:na]
at org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:532) ~[javax.enterprise.concurrent-1.0.jar!/:na]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_111]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_111]
at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_111]
at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250) ~[javax.enterprise.concurrent-1.0.jar!/:na]

environment for running PODM and PSME without RMM where PSME handles RMM's functionalities

We have a setup where PODM runs in one linux box and psme-rest-server, agents psme-compute-intel, psme-storage and psme-chassis are running in another linux box. we don,t have RMM running and we want PSME to handle RMM's functionalities and serve RMM's redfish APIs. In psme-rest-server.json "rmm-present" flag is set to false indicating there is no RMM. At PODM /tmp/services.list contains PSME service URL( http://PSME IP addr:8888/redfish/v1 psme). since "rmm-present" flag set to false, we expected to receive RMM related redfish APIs to be sent from PODM to PSME rest server, but no RMM APIs were sent from PODM. we tried by adding an entry in /tmp/services.list ( http://PSME IP addr:8888/redfish/v1 rmm ) and modified the port number in /etc/pod-manager/service-connection.json to same port number as PSME service, but that also not helpful.

so how can we setup this environment where there is no RMM and PSME has to receive and handle RMM's redfish APIs?

Qestions for additional PODM compute assets after modify event.json and install nodejs Simulaors

Dear intel,
I have questions that
after modify event.json and install nodejs Simulaors and run PSME Mock ,
there are additional PODM compute assets (8 hosts) -
10-s-1, 3-s-1, 8-s-1, ..... , 6-s-1.

Do they come from nodejs Simulaors ?
How to check ? thank you
House

cat /etc/pod-manager/events.json
{
"Northbound": {
"DeliveryRetryAttempts": 2,
"DeliveryRetryIntervalSeconds": 1
},
"Southbound": {
"EventSubscriptionIntervalSeconds": 90,
"BufferedEventProcessing" : {
"ProcessingWindowSizeInSeconds": 5
},
"ServicesConfiguration": [
{
"ServiceType": "psme",
"NetworkInterfaceName": "lo",
"PodManagerIpAddress": null
},
{
"ServiceType": "rss",
"NetworkInterfaceName": "lo",
"PodManagerIpAddress": null
},
{
"ServiceType": "rmm",
"NetworkInterfaceName": "lo",
"PodManagerIpAddress": null
},
{
"ServiceType": "inband",
"NetworkInterfaceName": "lo",
"PodManagerIpAddress": null
}
]
}
}

run PSME Mock

PSME Mock -

http://127.0.0.1:9443/redfish/v1

http://127.0.0.1:9443/redfish/v1/Systems

http://127.0.0.1:9443/redfish/v1/Systems/1

can see detail hardware information from PSME Mock :

in PODM Server Web ,
https://localhost:8443/redfish/v1/Systems
can found compute assets (8 hosts) -

Error: Redefinition of struct i2c_msg

Following error occurred while building PSME :

[ 6%] Built target logger_example_streams
[ 6%] Built target logger_example_udp_receiving
[ 6%] Building C object common/pca95xx/CMakeFiles/pca95xx.dir/src/pca95xx_i2c.c.o
In file included from /tmp/intelRSD/PSME/common/pca95xx/src/pca95xx_i2c.c:34:0:
/usr/include/linux/i2c-dev.h:37:8: error: redefinition of ‘struct i2c_msg’
struct i2c_msg {
^
compilation terminated due to -Wfatal-errors.
common/pca95xx/CMakeFiles/pca95xx.dir/build.make:103: recipe for target 'common/pca95xx/CMakeFiles/pca95xx.dir/src/pca95xx_i2c.c.o' failed
make[2]: *** [common/pca95xx/CMakeFiles/pca95xx.dir/src/pca95xx_i2c.c.o] Error 1
CMakeFiles/Makefile2:1167: recipe for target 'common/pca95xx/CMakeFiles/pca95xx.dir/all' failed
make[1]: *** [common/pca95xx/CMakeFiles/pca95xx.dir/all] Error 2
Makefile:146: recipe for target 'all' failed
make: *** [all] Error 2

This could be a platform specific issue while building on SLE 12 SP1. But I haven't tried to reproduce it in other platforms.

[PODM] InBand service

Dear Intel,

I have one questions about pod-manager UG – in band service support (6.4), and I want to follow the instruction to try example code,

But I didn’t find README.md & InBand Service sample code in pod-manager source code, do you know where can I get those files?

Question for PODM web service refresh time to change compute assets status

Dear intel -
the question is related to -
run PSME server and compute simulator and PODM but not found compute assets #38

in PODM - https://localhost:8443/redfish/v1/Systems/1-s-10
I can see the web page - Status - State is enabled,
and if I shutdown PSME Server and PSME compute simulator,
and wait about 5 ~ 10 minutes, the web page - Status - State is changed to Absent,

my question is -

What is the setting (configuration file) about the PODM web service refresh time ?
Can I change the setting ?
thank you
House

Don't find ca.pfx in PODM server when creating client certificate

Dear intel

I follow PODM user guide 2.2 :

4.3.1 Creating client certificate
Example 2 : Create client certificate and sign it with existing CA certificate.

cd /var/lib/pod-manager

sudo pod-manager-certificate-creation.sh --ca-certificate /path/to/ca/file/ca.pfx --client-certificate "C=PL,ST=State,L=locality,O=organization,CN=fqdn_or_ip"

but I don't find ca.pfx in PODM server,
Could you help ?
thank you
House

VLAN creation on node composition with Ethernet interface

Hi,

we tried to do node composition with Ethernet interface requirement specified in the json template as given in the podm api specification guide. node composition was successful. log shows neighbor mac of switch port and the mac address of Ethernet interface of the selected compute node are matching. here we need some understanding about the behavior observed. there was primary Vlan and list of Vlan fields specified in the template. are those Vlans expected to be created as part of node composition command execution or should those Vlan's to be created manually prior to node composition command execution. in our case, vlan was not created prior to node composition and after successful node composition also no Vlan's were created. let us know that the observed behavior is as expected? does the node composition creates the Vlans given in the requirement json template?

PODM support of swordfish

Hi,
does the pod-manager now supports swordfish compliant interfaces or is it only possible to use psme-storage?

Question for display hardware information when run PSME REST server and compute simulator

Dear Intel
when I run PSME REST server and PSME compute simulator, but don't run PODM,
PSME compute simulator loaded deep_discovery.xml that have pseudo hardware (HW) information,
Could I display the hardware information in PSME server ? thanks you.

PSME REST Server running

PSME compute simulator running

in PSME REST server
use uBuntu 16.04 FireFox browser , but not found hardware information from PSME compute simulator :

http://localhost:8888/redfish/v1

Question - PODM wildfly fail - 404-Not Found - after run PSME Mock and can not recovery

Dear intel,
the question is related to #38 -
run PSME server and compute simulator and PODM but not found compute assets

I found that
I installed PODM and its wildfly work normally,
go to https://localhost:8443/redfish/v1 , I can see odata.

but when I run PSME Mock (nodejs Simulator) in the same computer with PODM,
go to https://localhost:8443/redfish/v1 ,but I got error message - 404-Not Found,

I must modify /etc/pod-manager/events.json
to change the settings from - "NetworkInterfaceName": "eth0.4094",
to - "NetworkInterfaceName": "lo",

then go to https://localhost:8443/redfish/v1 , I can see odata.

Question 1 - Is it an issue ? thank you.

Question 2 - How to recovery PODM ?
if I recovery /etc/pod-manager/events.json and wildfly will fail.

thank you
House

secured communication between PODM and PSME

Hi,

we have PODM and PSME up and running. north bound of PSME and south bound of PODM are secured with CA certificated as per the instruction in PODM user guide chapter 7. we don't have RMM in our setup so as per the user guide manually all relevant cert and key files are manually copied to their respective places. pod-manager-certificate-creation.sh script was used to generate these cert and key file and updated the jks file in path /var/lib/pod-manager . took back up of generated cert and files as well as client.jks and keystore.jks file for future use. then PODM application was re-installed and PSME kept running as it is or restarted the PSME services, in both the cases , secure connection between PODM and PSME is failling. PSME reports "No certificate file unavailable" error message. previously generated certificate file and key were kept in their respective place and expected that secured connection remain in tact. question is, does it required to run the pod-manager-certificate-creation.sh script every time on re-installation of PODM. what is the dependency here.? if there is set of certificate file and keystore generated once and it should be able to use same set across multiple re-installation instance and secure connection between PODM and PSME should be in tact.

PSME Server web server - Systems page has authorization error

Dear Intel,

when I go to PSME Server web server, can see the information in the following picture ,

but when go to Systems page, get error message : "While accessing the resource at /redfish/v1/Systems, the service received an authorization error."
resolution : Ensure that the appropriate access is provided for the service in order for it to access the URI.

Could you help ? thank you
House

[PSME] Make it able to be built offline

When trying to compile PSME components in a internet-restricted machine, it will try to download several components.

It would be grat to have this components being used as libraries or devel packages from the system before trying to download them. Some components (googletest, gmock, json, microhttpd) even have their source code inside the repo (psme/common/) but are still being trying to download.

This makes building PSME packages on services like openSuse build (https://build.opensuse.org/) fails as they dont allow any downloads inside the build environment.

Making it sure that the dependencies are provided by the system, then fall back to what we have on the psme/common dir and as a last resort trying to download would be the proper way of dealing with this IMO, but Im not sure if there is any issues that may prevent this.

psme-rest-server fails with " Cannot start connector on port 8443: Success"

Hi,

I used an lxc container with Ubuntu 14.04 amd64, updated to built the binaries, like described in the PSME User Guide v1.2 . My target system is also Ubuntu 14.04 amd64, updated. I have used the psme-gen-serv-cert.sh script to generate certificates. The problem is that the psme-rest-server fails to start because connactor cannot be started:

/usr/bin$ sudo ./psme-rest-server /etc/psme/psme-rest-server-configuration.json

Results in this error:
2016-10-31 14:27:49.641298098 - ERROR - app - [application-ref/src/app.cpp:run:163] Cannot start connector on port 8443: Success

This looks for me similar to some issue in #4 , but the solution to use "setenv.sh && build64.sh" didn't work for me.

During build process the libmicrohttp.so is found:

-- Threads: 
-- Found CURL: /usr/include  
-- CURL header: /usr/include
-- CURL lib   : /usr/lib/x86_64-linux-gnu/libcurl.so
-- Found mhd: /usr/include  
-- MHD header: /usr/include
-- MHD lib   : /usr/lib/x86_64-linux-gnu/libmicrohttpd.so
-- Found Doxygen: /usr/bin/doxygen (found version "1.8.6") 
-- Could NOT find Boost
-- Found doxygen: /usr/bin/doxygen
-- Configuring done
-- Generating done

psme-rest-server-configuration.txt
certifcate_generation_log.txt
ldd_psme_rest_server.txt
psme_rest_server.txt

ldd_libmicrohttpd.so.10.txt

How to create an bootable iSCSI target with Linux as Operating System?

Hi,

how can we create an bootable iSCSI target with Linux as Operating System?
We followed the steps in the PSME User Guide but we stuck at step 5 in chapter 5.3.2.2

5.3.2.2 Creation of LVM structure

dd if=your_image.raw of=/dev/main_volume_group/base_logical_volume

I copied an ubuntu server iso to the iscsi target, the installation process fails because it searches the drivers on a CDROM..

How is this intended to be done?

wildfly fail to start normally

Hi,
i am trying to install PODM and seeing warning when wildfly is started as below
root@DCE-DV:/home/admin# service wildfly start

Starting WildFly Application Server wildfly [ OK ]
WildFly Application Server hasn't started within the timeout allowed
please review file "/var/log/wildfly/console.log" to see the status of the service

i checked "/var/log/wildfly/console.log" which states that "Could not start http listener". i have attached the full log file here.

wildfly-console.txt

in some wildfly forum, there was suggestion to change the port numbers. i have tried those option also but still same problem persist. please let me know anything you can make out from the log file.

Thanks

Question - PSME compute agent - Can it find MUX or BMC devices without IP address settings

Dear intel -
the question is related to Questions how PSME compute agent send IPMI commands to BMC AST2400 2500 and remove CY7C65215 #48,
Currently I can modify code of PSME compute agent to send Standard IPMI command (ex - Get Device ID) to BMC,

PSME compute agent start command is -
./psme-compute ../../agent/compute/configuration.json

BMC IP address is 192.168.1.106, so add IP address in configuration.json
"managers": [
{
"slot" : 1,
"switchPortIdentifier" : "sw0p37",
"ipv4": "192.168.1.106",
"username": “xxx",
"password": “xxx",
"port": 623,
"serialConsoleEnabled": true
}

Please help the questions, thank you -

Question 1 - in intel RSD 2.2, if do not setup BMC IP address in configuration.json, Can PSME compute agent find the BMC ?

Question 2 - related to Question 1, Does PSME compute agent find the BMC devices by SSDP (Simple Service Discovery Protocol) ?

Question 3 - related to Question 1, Can we modify code to implement Question 1's request ?

thank you.
House

Pod-manager cannot detect PSME

Dear Intel,

I found an issue that is pod-manager can not detect PSME after restating PSME.

steps:

Kill PSME restful server & compute/chassis agent
Start PSME restful server & compute/chassis agent

After I perform those steps, my expectation is I can see this PSME in external_service, but actually I can not found it, so I check the log:

Log:

Thread-1 (Discovery job)
2018-04-07 23:47:22,404 [EE-ManagedScheduledExecutorService-TasksExecutor-Thread-1] INFO c.i.p.d.external.DiscoveryRunner - Polling data from ExternalService {UUID=52dc9db9-784a-4857-9c7c-3fab259fb13f, baseUri=https://10.3.0.113:8407/redfish/v1, type=PSME} started
2018-04-07 23:47:22,821 [EE-ManagedScheduledExecutorService-TasksExecutor-Thread-1] WARN c.i.p.d.external.DiscoveryRunner - Connection error while getting data from ExternalService {UUID=52dc9db9-784a-4857-9c7c-3fab259fb13f, baseUri=https://10.3.0.113:8407/redfish/v1, type=PSME} service - performing check on this service

Thread-8 (Service removal job)

2018-04-07 23:48:01,162 [EE-ManagedScheduledExecutorService-TasksExecutor-Thread-8] INFO c.i.p.d.external.ServiceRemovalTask[ServiceLifecycle] - ExternalService {UUID=52dc9db9-784a-4857-9c7c-3fab259fb13f, baseUri=https://10.3.0.113:8407/redfish/v1, type=PSME, unreachableSince=2018-04-07T23:47:23.235} is unreachable longer than PT0S - will be evicted.

Thread-3 (Service detect job)

2018-04-07 23:48:02,077 [EE-ManagedScheduledExecutorService-TasksExecutor-Thread-3] DEBUG c.i.p.d.e.ServiceDetectionListenerImpl - Service Detect ..Schedule deep disvocery for 52dc9db9-784a-4857-9c7c-3fab259fb13f
2018-04-07 23:48:02,078 [EE-ManagedScheduledExecutorService-TasksExecutor-Thread-3] DEBUG c.i.p.c.s.SerialExecutorImpl - Registering new async task for 52dc9db9-784a-4857-9c7c-3fab259fb13f
2018-04-07 23:48:02,198 [EE-ManagedScheduledExecutorService-TasksExecutor-Thread-3] INFO c.i.p.d.e.event.EventSubscribeRunner - Successfully subscribed to event service for '52dc9db9-784a-4857-9c7c-3fab259fb13f'
2018-04-07 23:48:02,200 [ForkJoinPool.commonPool-worker-1] DEBUG c.i.p.c.s.SerialExecutorImpl - Requesting execution of next ASYNC operation(DiscoveryRunner(52dc9db9-784a-4857-9c7c-3fab259fb13f)) for (52dc9db9-784a-4857-9c7c-3fab259fb13f)

Thread-7 (Discovery Job)

2018-04-07 23:48:02,216 [EE-ManagedScheduledExecutorService-TasksExecutor-Thread-7] INFO c.i.p.d.external.DiscoveryRunner - Polling data from ExternalService {UUID=52dc9db9-784a-4857-9c7c-3fab259fb13f, baseUri=https://10.3.0.113:8407/redfish/v1, type=PSME, unreachableSince=2018-04-07T23:47:23.235} started
2018-04-07 23:48:02,317 [EE-ManagedScheduledExecutorService-TasksExecutor-Thread-7] DEBUG c.i.p.c.e.u.l.MethodInvocationLoggingInterceptor - [Discovery] RestGraphBuilderImpl.build - started
2018-04-07 23:48:02,378 [EE-ManagedScheduledExecutorService-TasksExecutor-Thread-7] DEBUG c.i.p.c.e.u.l.MethodInvocationLoggingInterceptor - [Discovery] RestGraphBuilderImpl.build - ended, execution time: 60.98 ms
2018-04-07 23:48:05,381 [EE-ManagedScheduledExecutorService-TasksExecutor-Thread-7] DEBUG c.i.p.c.e.u.l.MethodInvocationLoggingInterceptor - [Discovery] EntityGraphMapper.map - started
2018-04-07 23:48:05,396 [EE-ManagedScheduledExecutorService-TasksExecutor-Thread-7] ERROR c.i.p.d.external.DiscoveryRunner - Error while polling data from ExternalService {UUID=52dc9db9-784a-4857-9c7c-3fab259fb13f, baseUri=https://10.3.0.113:8407/redfish/v1, type=PSME, unreachableSince=2018-04-07T23:47:23.235}
javax.ejb.EJBTransactionRolledbackException: there is no service with UUID '52dc9db9-784a-4857-9c7c-3fab259fb13f'

I think the sequence is like this:

Thread 1 : pod-manager cannot connect to PSME (because I kill it)
Thread 8 : Service removal task prepare to remove PSME from external_service table
Thread 3 : service detect (because I start PSME)
*** pod-manager got the old external_service data which thread 8 prepare to delete
(you can observe it from
2018-04-07 23:48:02,216 [EE-ManagedScheduledExecutorService-TasksExecutor-Thread-7] INFO c.i.p.d.external.DiscoveryRunner - Polling data from ExternalService {UUID=52dc9db9-784a-4857-9c7c-3fab259fb13f, baseUri=https://10.3.0.113:8407/redfish/v1, type=PSME, unreachableSince=2018-04-07T23:47:23.235} started, why new detect service has unreachableSince ?)
Thread 7: pod-manager start to polling the PSME
…. (Thread 8)remove the PSME from external_service table
pod-manager throws exception: there is no service with UUID '52dc9db9-784a-4857-9c7c-3fab259fb13f'
--> because the tuple in external_service is removed by Thread 8

And here is my assumption about why pod-manager can not persist new detect PSME to its database, even though this PSME is keep running.

Pod-manager service detect thread read the old external_service data and then the old data are deleted by service removal thread. This result in service detect fail and the PSME doesn’t enter to external_service table.
PSME is running and keep to send alive message, even though PSME doesn’t enter to external_service table, it is still in SSDP registry cache.
When pod-manager receive m-search response or notification from this PSME, pod-manager will think this PSME is known service (due to it is already in SSDP registry cache), and never fire service detect task.

Could you please help to check this issue?

startup PSME compute simulator fail - error msg - RPC Error - METHOD_NOT_FOUND

Dear Intel,
I startup PSME rest server success,
$ sudo ./psme-rest-server ../../application/config/psme-rest-server-configuration.json

but startup PSME compute simulator fail, this is my steps,

Edit /home/user/IntelRSD/intelRSD-2-2/PSME/agent-simulator/compute/configuration.json
"assetConfiguration" : {
"input" : "/home/user/IntelRSD/intelRSD-2-2/PSME/agent-simulator/compute/deep_discovery.xml",
"schema" : "/home/user/IntelRSD/intelRSD-2-2/PSME/agent-simulator/compute/deep_discovery.xsd"
},
"service-uuid-file" : "/var/opt/psme/compute-service-uuid.json",
create directory in /var/opt/psme/
$ sudo mkdir /var/opt/psme
startup PSME compute simulator
$pwd
/home/user/IntelRSD/intelRSD-2-2/PSME/build/bin

$ sudo ./psme-compute-simulator ../../agent-simulator/compute/configuration.json

2018-01-10 13:46:11.637516758 - INFO - compute-agent - MANUAL PSME BUILD; Built 13:42:27, 28-12-2017
2018-01-10 13:46:11.637569096 - DEBUG - configuration - Added file ../../agent-simulator/compute/configuration.json
2018-01-10 13:46:11.637629569 - WARN - configuration - Cannot load default file
2018-01-10 13:46:11.637654782 - INFO - configuration - Load file
2018-01-10 13:46:11.637715016 - INFO - configuration - Loaded file ../../agent-simulator/compute/configuration.json
2018-01-10 13:46:11.637749701 - INFO - configuration - Load internal defaults
2018-01-10 13:46:11.637850880 - INFO - compute-agent - JSON Schema load!
2018-01-10 13:46:28.309609980 - ERROR - command-server - RPC Error : Exception -32601 - METHOD_NOT_FOUND: The method being requested is not available on this server: Unknown method: getTasksCollection
2018-01-10 13:46:28.309970204 - ERROR - command-server - RPC Error : Exception -32601 - METHOD_NOT_FOUND: The method being requested is not available on this server: Unknown method: getMetricDefinitionsCollection
2018-01-10 13:46:28.310301963 - ERROR - command-server - RPC Error : Exception -32601 - METHOD_NOT_FOUND: The method being requested is not available on this server: Unknown method: getMetrics

Please help to support, thank you.
House

LUI can't find NVMe drives

Dear Intel,

The LUI uses lshw command to collect hw/system information including storage controller and disk info.

I have a compute system with 2 local NVMe drives installed and I ran the LUI on it thru RSD deep discovery. From the results of deep_discovery.xml and lshw command, there is no disk info but storage.

Not sure if it's the limitation of lshw. Could you please help on this? Thanks.

# lshw -C disk -C storage
  *-storage
       description: SATA controller
       product: Lewisburg SSATA Controller [AHCI mode]
       vendor: Intel Corporation
       physical id: 11.5
       bus info: pci@0000:00:11.5
       version: 04
       width: 32 bits
       clock: 66MHz
       capabilities: storage msi pm ahci_1.0 bus_master cap_list
       configuration: driver=ahci latency=0
       resources: irq:66 memory:9d284000-9d285fff memory:9d286000-9d2860ff ioport:3030(size=8) ioport:3020(size=4) ioport:3000(size=32) memory:9d200000-9d27ffff
  *-storage
       description: Non-Volatile memory controller
       product: Intel Corporation
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:21:00.0
       version: 00
       width: 64 bits
       clock: 33MHz
       capabilities: storage pm msix pciexpress msi nvm_express bus_master cap_list rom
       configuration: driver=nvme latency=0
       resources: irq:195 memory:aa710000-aa713fff memory:aa700000-aa70ffff
  *-storage
       description: Non-Volatile memory controller
       product: Intel Corporation
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:44:00.0
       version: 00
       width: 64 bits
       clock: 33MHz
       capabilities: storage pm msix pciexpress msi nvm_express bus_master cap_list rom
       configuration: driver=nvme latency=0
       resources: irq:196 memory:b7f10000-b7f13fff memory:b7f00000-b7f0ffff

# fdisk -l
fdisk: device has more than 2^32 sectors, can't use all of them

Disk /dev/nvme1n1: 2199.0 GB, 2199023255040 bytes
64 heads, 32 sectors/track, 2097151 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Disk /dev/nvme1n1 doesn't contain a valid partition table
fdisk: device has more than 2^32 sectors, can't use all of them

Disk /dev/nvme0n1: 2199.0 GB, 2199023255040 bytes
64 heads, 32 sectors/track, 2097151 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Disk /dev/nvme0n1 doesn't contain a valid partition table

# ls -al /dev/nvme*
crw-------    1 root     root      248,   0 Apr 11 07:15 /dev/nvme0
brw-rw----    1 root     disk      259,   1 Apr 11 07:15 /dev/nvme0n1
crw-------    1 root     root      248,   1 Apr 11 07:15 /dev/nvme1
brw-rw----    1 root     disk      259,   0 Apr 11 07:15 /dev/nvme1n1
# lsmod
Module                  Size  Used by    Not tainted
x86_pkg_temp_thermal     4128  0
nvme                   37433  0

<?xml version="1.0" encoding="utf-8"?>
<manager>
    <manager>
        <serialConsole>s
            <enabled>true</enabled>
        </serialConsole>
        <chassis>
            <locationOffset>0</locationOffset>
            <type>Module</type>
            <parentId>0</parentId>
        </chassis>
        <ComputeSystem>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>a190</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2056</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2084</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2025</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2082</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2057</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>a194</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2041</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2042</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2058</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>204d</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2018</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2085</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>a1a1</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2043</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>208e</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>11f8</vendorId>
                <deviceId>8536</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>a1b1</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>a1d2</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>208d</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>a1a4</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2034</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>a1bb</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>204c</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2055</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>204b</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2081</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>a1a3</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>a1ba</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>a1af</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>204e</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2080</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2036</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2059</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2040</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>a1be</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2016</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2083</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2046</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2030</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>a1ec</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>1563</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2015</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2049</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>0a54</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2086</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2014</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2024</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2048</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2054</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2045</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>1a03</vendorId>
                <deviceId>2000</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>1a03</vendorId>
                <deviceId>1150</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>204a</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2044</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2066</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2021</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2047</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2035</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>a1c6</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2020</deviceId>
            </pciDevice>
            <pciDevice>
                <vendorId>8086</vendorId>
                <deviceId>2026</deviceId>
            </pciDevice>
            <fruInfo>
                <partNumber></partNumber>
                <modelNumber>X11DPS-R</modelNumber>
                <manufacturer>Supermicro</manufacturer>
                <serialNumber>UM183S000243</serialNumber>
            </fruInfo>
            <networkInterface>
                <macAddress>0c:c4:7a:88:15:fc</macAddress>
                <fullDuplex>true</fullDuplex>
                <factoryMacAddress>0c:c4:7a:88:15:fc</factoryMacAddress>
                <frameSize>1500</frameSize>
                <autoSense>true</autoSense>
                <speedMbps>1000</speedMbps>
            </networkInterface>
            <networkInterface>
                <macAddress>0c:c4:7a:88:15:fd</macAddress>
                <fullDuplex>true</fullDuplex>
                <factoryMacAddress>0c:c4:7a:88:15:fd</factoryMacAddress>
                <frameSize>1500</frameSize>
                <autoSense>true</autoSense>
                <speedMbps>10000</speedMbps>
            </networkInterface>
            <storageSubsystem>
                <storageController>
                    <status>
                        <state>Enabled</state>
                        <health>OK</health>
                    </status>
                    <interface>SATA</interface>
                    <busInfo>pci@0000:00:11.5</busInfo>
                </storageController>
            </storageSubsystem>
            <location>0</location>
            <memory>
                <minimumVoltageVolt>1.200</minimumVoltageVolt>
                <dimmLocation>
                    <slot>0</slot>
                    <controller>0</controller>
                    <socket>0</socket>
                    <channel>0</channel>
                </dimmLocation>
                <dataWidthBits>64</dataWidthBits>
                <busWidthBits>72</busWidthBits>
                <fruInfo>
                    <partNumber>36ASF4G72PZ-2G6H1R</partNumber>
                    <modelNumber></modelNumber>
                    <manufacturer>Micron</manufacturer>
                    <serialNumber>168B5A67</serialNumber>
                </fruInfo>
                <maximumVoltageVolt>1.200</maximumVoltageVolt>
                <operatingSpeedMHz>2666</operatingSpeedMHz>
                <rankCount>2</rankCount>
                <voltageVolt>1.200</voltageVolt>
                <deviceLocator>P1-DIMMA1</deviceLocator>
            </memory>
            <memory>
                <minimumVoltageVolt>1.200</minimumVoltageVolt>
                <dimmLocation>
                    <slot>0</slot>
                    <controller>0</controller>
                    <socket>0</socket>
                    <channel>0</channel>
                </dimmLocation>
                <dataWidthBits>64</dataWidthBits>
                <busWidthBits>72</busWidthBits>
                <fruInfo>
                    <partNumber>36ASF4G72PZ-2G6H1R</partNumber>
                    <modelNumber></modelNumber>
                    <manufacturer>Micron</manufacturer>
                    <serialNumber>16E94C9E</serialNumber>
                </fruInfo>
                <maximumVoltageVolt>1.200</maximumVoltageVolt>
                <operatingSpeedMHz>2666</operatingSpeedMHz>
                <rankCount>2</rankCount>
                <voltageVolt>1.200</voltageVolt>
                <deviceLocator>P1-DIMMD1</deviceLocator>
            </memory>
            <memory>
                <minimumVoltageVolt>1.200</minimumVoltageVolt>
                <dimmLocation>
                    <slot>0</slot>
                    <controller>0</controller>
                    <socket>0</socket>
                    <channel>0</channel>
                </dimmLocation>
                <dataWidthBits>64</dataWidthBits>
                <busWidthBits>72</busWidthBits>
                <fruInfo>
                    <partNumber>36ASF4G72PZ-2G6H1R</partNumber>
                    <modelNumber></modelNumber>
                    <manufacturer>Micron</manufacturer>
                    <serialNumber>16E6E903</serialNumber>
                </fruInfo>
                <maximumVoltageVolt>1.200</maximumVoltageVolt>
                <operatingSpeedMHz>2666</operatingSpeedMHz>
                <rankCount>2</rankCount>
                <voltageVolt>1.200</voltageVolt>
                <deviceLocator>P2-DIMMA1</deviceLocator>
            </memory>
            <memory>
                <minimumVoltageVolt>1.200</minimumVoltageVolt>
                <dimmLocation>
                    <slot>0</slot>
                    <controller>0</controller>
                    <socket>0</socket>
                    <channel>0</channel>
                </dimmLocation>
                <dataWidthBits>64</dataWidthBits>
                <busWidthBits>72</busWidthBits>
                <fruInfo>
                    <partNumber>36ASF4G72PZ-2G6H1R</partNumber>
                    <modelNumber></modelNumber>
                    <manufacturer>Micron</manufacturer>
                    <serialNumber>16E6EB91</serialNumber>
                </fruInfo>
                <maximumVoltageVolt>1.200</maximumVoltageVolt>
                <operatingSpeedMHz>2666</operatingSpeedMHz>
                <rankCount>2</rankCount>
                <voltageVolt>1.200</voltageVolt>
                <deviceLocator>P2-DIMMD1</deviceLocator>
            </memory>
            <processor>
                <processorArchitecture>x86</processorArchitecture>
                <modelName>Intel(R) Xeon(R) Gold 6152 CPU @ 2.10GHz</modelName>
                <totalCores>22</totalCores>
                <socket>CPU1</socket>
                <processorType>CPU</processorType>
                <enabledThreads>44</enabledThreads>
                <instructionSet>x86-64</instructionSet>
                <capability>x86-64</capability>
                <capability>fpu</capability>
                <capability>fpu_exception</capability>
                <capability>wp</capability>
                <capability>vme</capability>
                <capability>de</capability>
                <capability>pse</capability>
                <capability>tsc</capability>
                <capability>msr</capability>
                <capability>pae</capability>
                <capability>mce</capability>
                <capability>cx8</capability>
                <capability>apic</capability>
                <capability>sep</capability>
                <capability>mtrr</capability>
                <capability>pge</capability>
                <capability>mca</capability>
                <capability>cmov</capability>
                <capability>pat</capability>
                <capability>pse36</capability>
                <capability>clflush</capability>
                <capability>dts</capability>
                <capability>acpi</capability>
                <capability>mmx</capability>
                <capability>fxsr</capability>
                <capability>sse</capability>
                <capability>sse2</capability>
                <capability>ss</capability>
                <capability>ht</capability>
                <capability>tm</capability>
                <capability>pbe</capability>
                <capability>syscall</capability>
                <capability>nx</capability>
                <capability>pdpe1gb</capability>
                <capability>rdtscp</capability>
                <capability>constant_tsc</capability>
                <capability>arch_perfmon</capability>
                <capability>pebs</capability>
                <capability>bts</capability>
                <capability>rep_good</capability>
                <capability>nopl</capability>
                <capability>xtopology</capability>
                <capability>nonstop_tsc</capability>
                <capability>aperfmperf</capability>
                <capability>eagerfpu</capability>
                <capability>pni</capability>
                <capability>pclmulqdq</capability>
                <capability>dtes64</capability>
                <capability>monitor</capability>
                <capability>ds_cpl</capability>
                <capability>vmx</capability>
                <capability>smx</capability>
                <capability>est</capability>
                <capability>tm2</capability>
                <capability>ssse3</capability>
                <capability>sdbg</capability>
                <capability>fma</capability>
                <capability>cx16</capability>
                <capability>xtpr</capability>
                <capability>pdcm</capability>
                <capability>pcid</capability>
                <capability>dca</capability>
                <capability>sse4_1</capability>
                <capability>sse4_2</capability>
                <capability>x2apic</capability>
                <capability>movbe</capability>
                <capability>popcnt</capability>
                <capability>tsc_deadline_timer</capability>
                <capability>aes</capability>
                <capability>xsave</capability>
                <capability>avx</capability>
                <capability>f16c</capability>
                <capability>rdrand</capability>
                <capability>lahf_lm</capability>
                <capability>abm</capability>
                <capability>3dnowprefetch</capability>
                <capability>ida</capability>
                <capability>arat</capability>
                <capability>epb</capability>
                <capability>pln</capability>
                <capability>pts</capability>
                <capability>dtherm</capability>
                <capability>intel_pt</capability>
                <capability>tpr_shadow</capability>
                <capability>vnmi</capability>
                <capability>flexpriority</capability>
                <capability>ept</capability>
                <capability>vpid</capability>
                <capability>fsgsbase</capability>
                <capability>tsc_adjust</capability>
                <capability>bmi1</capability>
                <capability>hle</capability>
                <capability>avx2</capability>
                <capability>smep</capability>
                <capability>bmi2</capability>
                <capability>erms</capability>
                <capability>invpcid</capability>
                <capability>rtm</capability>
                <capability>cqm</capability>
                <capability>mpx</capability>
                <capability>avx512f</capability>
                <capability>rdseed</capability>
                <capability>adx</capability>
                <capability>smap</capability>
                <capability>clflushopt</capability>
                <capability>clwb</capability>
                <capability>avx512cd</capability>
                <capability>xsaveopt</capability>
                <capability>xsavec</capability>
                <capability>xgetbv1</capability>
                <capability>cqm_llc</capability>
                <capability>cqm_occup_llc</capability>
                <capability>cpufreq</capability>
                <totalThreads>44</totalThreads>
                <maxSpeedMHz>2100</maxSpeedMHz>
                <cpuid>
                    <vendorId>GenuineIntel</vendorId>
                    <family>6</family>
                    <step>4</step>
                    <microcodeInfo>0x2000043</microcodeInfo>
                    <model>85</model>
                    <numericId>0</numericId>
                </cpuid>
                <model>Unknown</model>
                <manufacturer>Intel Corp.</manufacturer>
                <enabledCores>22</enabledCores>
            </processor>
            <processor>
                <processorArchitecture>x86</processorArchitecture>
                <modelName>Intel(R) Xeon(R) Gold 6152 CPU @ 2.10GHz</modelName>
                <totalCores>22</totalCores>
                <socket>CPU2</socket>
                <processorType>CPU</processorType>
                <enabledThreads>44</enabledThreads>
                <instructionSet>x86-64</instructionSet>
                <capability>x86-64</capability>
                <capability>fpu</capability>
                <capability>fpu_exception</capability>
                <capability>wp</capability>
                <capability>vme</capability>
                <capability>de</capability>
                <capability>pse</capability>
                <capability>tsc</capability>
                <capability>msr</capability>
                <capability>pae</capability>
                <capability>mce</capability>
                <capability>cx8</capability>
                <capability>apic</capability>
                <capability>sep</capability>
                <capability>mtrr</capability>
                <capability>pge</capability>
                <capability>mca</capability>
                <capability>cmov</capability>
                <capability>pat</capability>
                <capability>pse36</capability>
                <capability>clflush</capability>
                <capability>dts</capability>
                <capability>acpi</capability>
                <capability>mmx</capability>
                <capability>fxsr</capability>
                <capability>sse</capability>
                <capability>sse2</capability>
                <capability>ss</capability>
                <capability>ht</capability>
                <capability>tm</capability>
                <capability>pbe</capability>
                <capability>syscall</capability>
                <capability>nx</capability>
                <capability>pdpe1gb</capability>
                <capability>rdtscp</capability>
                <capability>constant_tsc</capability>
                <capability>arch_perfmon</capability>
                <capability>pebs</capability>
                <capability>bts</capability>
                <capability>rep_good</capability>
                <capability>nopl</capability>
                <capability>xtopology</capability>
                <capability>nonstop_tsc</capability>
                <capability>aperfmperf</capability>
                <capability>eagerfpu</capability>
                <capability>pni</capability>
                <capability>pclmulqdq</capability>
                <capability>dtes64</capability>
                <capability>monitor</capability>
                <capability>ds_cpl</capability>
                <capability>vmx</capability>
                <capability>smx</capability>
                <capability>est</capability>
                <capability>tm2</capability>
                <capability>ssse3</capability>
                <capability>sdbg</capability>
                <capability>fma</capability>
                <capability>cx16</capability>
                <capability>xtpr</capability>
                <capability>pdcm</capability>
                <capability>pcid</capability>
                <capability>dca</capability>
                <capability>sse4_1</capability>
                <capability>sse4_2</capability>
                <capability>x2apic</capability>
                <capability>movbe</capability>
                <capability>popcnt</capability>
                <capability>tsc_deadline_timer</capability>
                <capability>aes</capability>
                <capability>xsave</capability>
                <capability>avx</capability>
                <capability>f16c</capability>
                <capability>rdrand</capability>
                <capability>lahf_lm</capability>
                <capability>abm</capability>
                <capability>3dnowprefetch</capability>
                <capability>ida</capability>
                <capability>arat</capability>
                <capability>epb</capability>
                <capability>pln</capability>
                <capability>pts</capability>
                <capability>dtherm</capability>
                <capability>intel_pt</capability>
                <capability>tpr_shadow</capability>
                <capability>vnmi</capability>
                <capability>flexpriority</capability>
                <capability>ept</capability>
                <capability>vpid</capability>
                <capability>fsgsbase</capability>
                <capability>tsc_adjust</capability>
                <capability>bmi1</capability>
                <capability>hle</capability>
                <capability>avx2</capability>
                <capability>smep</capability>
                <capability>bmi2</capability>
                <capability>erms</capability>
                <capability>invpcid</capability>
                <capability>rtm</capability>
                <capability>cqm</capability>
                <capability>mpx</capability>
                <capability>avx512f</capability>
                <capability>rdseed</capability>
                <capability>adx</capability>
                <capability>smap</capability>
                <capability>clflushopt</capability>
                <capability>clwb</capability>
                <capability>avx512cd</capability>
                <capability>xsaveopt</capability>
                <capability>xsavec</capability>
                <capability>xgetbv1</capability>
                <capability>cqm_llc</capability>
                <capability>cqm_occup_llc</capability>
                <capability>cpufreq</capability>
                <totalThreads>44</totalThreads>
                <maxSpeedMHz>2100</maxSpeedMHz>
                <cpuid>
                    <vendorId>GenuineIntel</vendorId>
                    <family>6</family>
                    <step>4</step>
                    <microcodeInfo>0x2000043</microcodeInfo>
                    <model>85</model>
                    <numericId>1</numericId>
                </cpuid>
                <model>Unknown</model>
                <manufacturer>Intel Corp.</manufacturer>
                <enabledCores>22</enabledCores>
            </processor>
        </ComputeSystem>
    </manager>
    <chassis>
        <locationOffset>0</locationOffset>
        <type>Drawer</type>
        <parentId>0</parentId>
    </chassis>
    <serialConsole>
        <enabled>true</enabled>
    </serialConsole>
</manager>

Instalation help

Hi guys,
I'm trying to setup PSME to talk to our project without success. I've managed to compile and start the rest server and the compute-agent(that's all we are testing for now). In the compute-agent config file, in section"managers" we put the credentials for our redfish server that is responding for our servers.
Both servers (rest-server and compute-agent) starts fine, compute-agent manages to register with the rest-server. The rest server keeps pooling something. The rest-server responds fine to /redfish/v1 (service root) request. When I try to get to managers (/redfish/v1/Managers) or systems(/redfish/v1/Systems) I get a reply with zero info, no managers, no systems found.
While doing these requests I see nothing on the compute-agent logs. And since the service is started not a single byte was sent to our redfish server. I can't find anyway to debug or understand what's going on. Documentation available just tell me how to compile it. The configuration part is quite problematic. For example: in the rest-configuration you have a table of properties on pag 31, a sample configuration starting on pag. 32, and the configuration schema starting on pag 33. The kind of problem I refer to is: properties: "certs-directory", "thread-pool-size", "client-cert-required" of connectors section that appear on the sample code (pag 32) does not appear on the table of contents nor in the schema. Another example is the configuration sample available at <PSM_root>/application/config/psme-rest-server-configuration.json. This was the sample file I used to create my config. It does not have section connectors at all(and this is required at the schema and I see the server complaining about it missing in the start up) and have a property URL that don't show up in the table nor in the schema. So I'm kind of lost here.
Trying to be more accurate with my problem:
What I expect:
When I access /redfish/v1/Systems of the PSME server I would see my available hardware in a redfish response.
How I think this works:

I send a request to the rest-server and it would ask the compute-agent to get a list a computer systems available OR that the compute-agent upon start would already discover this information(hardware available) and feed it to the rest server.
I expected that the compute-agent would access my redfish API available at the IP/Port with user name and password hash I provided in the managers section of the compute-agent config file and get the hardware available there and pass them to the rest-server
Here is my server config file:

{
    "server": {
        "network-interface-name" : "enp0s3",
	"connectors":[
		{
			"use-ssl": true,
			"certs-directory": "/etc/psme/certs",
			"port": 8443,
			"thread-mode": "select",
			"thread-pool-size": 10,
			"client-cert-required": false
		},
		{
			"use-ssl": false,
			"port": 8888,
			"redirect-port": 8443,
			"thread-mode": "select"
		}
	]
    },
    "registration": {
        "port": 8383,
        "minDelay": 3
    },
    "commands": {
        "generic": "Registration"
    },
    "rmm-present": false,
    "eventing" : {
        "enabled" : false,
        "address": "localhost",
        "port" : 5567,
        "poll-interval-sec" : 20
    },
    "rest-server" : {
        "storage-service-mode" : false
    },
    "service-uuid-file" : "/etc/psme/service_uuid.json",
    "subscription-config-file" : "/tmp/subscriptions",
    "logger" : {
        "app" : {
            "level" : "INFO",
            "timeformat" : "DATE_NS",
            "color" : true,
            "output" : true,
            "tagging" : true,
            "moredebug" : false,
            "streams" : [
                 {
                    "type" : "STDOUT"
                 }
            ]
        }
    }
}

and here is my compute-agent config file:

{
    "agent": {
        "vendor" : "Test",
        "capabilities" : [ "Compute" ]
    },
    "server": {
        "port": 7777
    },
    "registration": {
        "ipv4": "localhost",
        "port": 8383,
        "interval": 3
    },
    "managers": [
        {
            "slot" : 1,
            "switchPortIdentifier" : "sw0p37",
            "ipv4": "192.168.200.30",
            "username": "CBB6DE08B54A14F756B7A62BBCC51005",
            "password": "21BB36EAA74E097B",
            "port": 5000,
            "serialConsoleEnabled": true
        }
    ],
    "service-uuid-file" : "/var/opt/psme/compute-service-uuid.json",
    "logger" : {
        "agent" : {
            "level" : "INFO",
            "timeformat" : "DATE_NS",
            "color" : true,
            "output" : true,
            "tagging" : true,
            "moredebug" : false,
            "streams" : [
                {
                    "type" : "STDOUT"
                }
            ]
        }
    }
}

Here something in the logs of the computer-agent that makes me wonder if there's something wrong. See the "DISCOVERY_MISSING" in the end...
2017-12-04 13:43:39.078658890 - INFO - compute-agent - MANUAL PSME BUILD; Built 18:44:11, 30-11-2017
2017-12-04 13:43:39.078836732 - DEBUG - configuration - Added file /etc/psme/compute-configuration.json
2017-12-04 13:43:39.078985790 - WARN - configuration - Cannot load default file
2017-12-04 13:43:39.079025838 - INFO - configuration - Load file
2017-12-04 13:43:39.079077302 - INFO - configuration - Loaded file /etc/psme/compute-configuration.json
2017-12-04 13:43:39.079117279 - INFO - configuration - Load internal defaults
2017-12-04 13:43:39.079185243 - INFO - compute-agent - JSON Schema load!
2017-12-04 13:43:39.089642978 - INFO - compute-agent -
Running SDV PSME Compute Agent.
2017-12-04 13:43:39.089814363 - INFO - eventing - Starting EventDispatcher thread...
2017-12-04 13:43:39.091596527 - INFO - default - Service UUID: dce65a84-d8fa-11e7-af8d-c7ed297637db
2017-12-04 13:43:39.096350941 - INFO - registration - Agent has been registered to http://localhost:8383
2017-12-04 13:43:39.096484570 - INFO - eventing - Sending AMC notifications enabled.
2017-12-04 13:43:42.098815905 - INFO - state-machine - Starting State Machine thread...
2017-12-04 13:43:43.099323281 - INFO - state-machine - Starting State Machine Module thread...
2017-12-04 13:43:53.099958156 - INFO - agent - Module e5c37dc6-d909-11e7-9542-43ae2d42f28c status changed to ABSENT after event DISCOVERY_MISSING

Node composition at PODM

Tried Node composition at PODM, Facing an issue here,

Node creation was successful when tried with JSON template containing only Processor Requirements.
But when the same Template along with Processor , Memory, Ethernet Interface and Local drive Requirements failed to compose node with following Error Message.

error" : {
"code" : "Base.1.0.ResourcesStateMismatch",
"message" : "Conflict during allocation",
"@Message.ExtendedInfo" : [ {
"Message" : "There are no computer systems available for this allocation request."
}, {
"Message" : "Available assets count after applying filters: [available: 9 -> status: 9 -> resource: 1 -> chassis: 1 -> processors: 1 -> memory: 0 -> local drives: 0 -> ethernet interfaces: 0]"
} ]
}

Question for How to get PODM client.jks keystore password by keytool

Dear Intel
when I use keytool and /var/lib/pod-manager/client.jks to list valid date or generate client certificate ,
it prompt - Enter keystore password:
How to get PODM client.jks keystore password ?
thank you.
House

cd /var/lib/pod-manager/
user@podm1:/var/lib/pod-manager$
user@podm1:/var/lib/pod-manager$ keytool -v -list -keystore client.jks
Enter keystore password:
keytool error: java.io.IOException: Keystore was tampered with, or password was incorrect
java.io.IOException: Keystore was tampered with, or password was incorrect
at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:780)
at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:56)
at sun.security.provider.KeyStoreDelegator.engineLoad(KeyStoreDelegator.java:224)
at sun.security.provider.JavaKeyStore$DualFormatJKS.engineLoad(JavaKeyStore.java:70)
at java.security.KeyStore.load(KeyStore.java:1445)
at sun.security.tools.keytool.Main.doCommands(Main.java:933)
at sun.security.tools.keytool.Main.run(Main.java:366)
at sun.security.tools.keytool.Main.main(Main.java:359)
Caused by: java.security.UnrecoverableKeyException: Password verification failed
at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:778)
... 7 more

cd /var/lib/pod-manager/

sudo keytool -importkeystore -srckeystore client.jks -destkeystore client.p12 -deststoretype pkcs12
Importing keystore client.jks to client.p12...
Enter destination keystore password:
Re-enter new password:
Enter source keystore password:
keytool error: java.io.IOException: Keystore was tampered with, or password was incorrect

Feasibility of running a compute simulator on a single node or VM

I have a question on the minimum requirements for a basic integration with openstack.

Is it feasible to run just the psme-compute-simulator as a service on a single node or on a VM to be interpreted by an openstack controller as a potential compute node ?
What are the minimum set of services that need to be run in order to be able to interact with PSME APIs ?

I dont expect to create instances on the node but would like to test the APIs in a single node environment and use this for development. Any pointers on this will be helpful.

TypedQuery [ComposedNode] is incompatible with query return type [ComposedNode

Dear Intel,

I am using 2.1.3 pod-manager,when I start pod-manager, I got the error " javax.ejb.EJBException: java.lang.IllegalArgumentException: Type specified for TypedQuery [com.intel.podm.business.entities.redfish.ComposedNode] is incompatible with query return type [class com.intel.podm.business.entities.redfish.ComposedNode]", that cause pod-manager deploy failed.

Do you know why ComposedNode cannot cast to ComposedNode ?

Error message (/var/log/wildfly):
2018-01-31 19:37:38,994 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "pod-manager-2.1.3.4.0-rest.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit."pod-manager-2.1.3.4.0-rest.war".component.AllocationStartup.START" => "org.jboss.msc.service.StartException in service jboss.deployment.unit."pod-manager-2.1.3.4.0-rest.war".component.AllocationStartup.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance
Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance
Caused by: javax.ejb.EJBException: java.lang.IllegalArgumentException: Type specified for TypedQuery [com.intel.podm.business.entities.redfish.ComposedNode] is incompatible with query return type [class com.intel.podm.business.entities.redfish.ComposedNode]
Caused by: java.lang.IllegalArgumentException: Type specified for TypedQuery [com.intel.podm.business.entities.redfish.ComposedNode] is incompatible with query return type [class com.intel.podm.business.entities.redfish.ComposedNode]"}}

Error message (/var/log/pod-manager):
2018-01-31 19:37:11,523 [EE-ManagedScheduledExecutorService-TasksExecutor-Thread-8] DEBUG c.i.p.c.e.u.l.MethodInvocationLoggingInterceptor - [Discovery] EntityGraphMapper.map - started
2018-01-31 19:37:11,620 [EE-ManagedScheduledExecutorService-TasksExecutor-Thread-8] ERROR c.i.p.d.external.DiscoveryRunner - Error while polling data from ExternalService {UUID=1cf31eef-cacd-43da-a94d-a86a7315fd0a, baseUri=https://10.3.0.25:8403/redfish/v1, type=PSME}
javax.ejb.EJBTransactionRolledbackException: Type specified for TypedQuery [com.intel.podm.business.entities.redfish.ComposedNode] is incompatible with query return type [class com.intel.podm.business.entities.redfish.ComposedNode]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleInCallerTx(CMTTxInterceptor.java:159) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:256) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:329) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:239) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) ~[na:na]
at org.jboss.as.ejb3.concurrency.ContainerManagedConcurrencyInterceptor.processInvocation(ContainerManagedConcurrencyInterceptor.java:110) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) ~[na:na]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) ~[na:na]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) ~[na:na]
at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:636) ~[na:na]
at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) ~[na:na]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) ~[na:na]
at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) ~[na:na]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) ~[na:na]
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195) ~[na:na]
at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) ~[na:na]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) ~[na:na]
at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) ~[na:na]
at com.intel.podm.discovery.external.finalizers.DiscoveryFinalizer$$$view36.finalizeDiscovery(Unknown Source) ~[podm-discovery-2.1.3.4.0.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_111]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_111]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_111]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_111]
at org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:436) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:127) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at com.intel.podm.discovery.external.finalizers.DiscoveryFinalizer$Proxy$_$$Weld$EnterpriseProxy$.finalizeDiscovery(Unknown Source) ~[podm-discovery-2.1.3.4.0.jar:na]
at com.intel.podm.discovery.external.EntityGraphMapper.map(EntityGraphMapper.java:75) ~[podm-discovery-2.1.3.4.0.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_111]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_111]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_111]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_111]
at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) ~[na:na]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) ~[na:na]
at org.jboss.as.weld.ejb.DelegatingInterceptorInvocationContext.proceed(DelegatingInterceptorInvocationContext.java:87) ~[wildfly-weld-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.weld.interceptor.proxy.WeldInvocationContext.interceptorChainCompleted(WeldInvocationContext.java:98) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.WeldInvocationContext.proceed(WeldInvocationContext.java:117) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at com.intel.podm.common.enterprise.utils.logger.MethodInvocationLoggingInterceptor.interceptingMethod(MethodInvocationLoggingInterceptor.java:44) ~[enterprise-utils-2.1.3.4.0.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_111]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_111]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_111]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_111]
at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:74) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.WeldInvocationContext.invokeNext(WeldInvocationContext.java:83) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.WeldInvocationContext.proceed(WeldInvocationContext.java:115) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.bean.InterceptorImpl.intercept(InterceptorImpl.java:108) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.as.weld.ejb.DelegatingInterceptorInvocationContext.proceed(DelegatingInterceptorInvocationContext.java:77) ~[wildfly-weld-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.weld.interceptor.proxy.WeldInvocationContext.interceptorChainCompleted(WeldInvocationContext.java:98) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.WeldInvocationContext.proceed(WeldInvocationContext.java:117) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.invokeInOurTx(TransactionalInterceptorBase.java:117) [narayana-jts-idlj-5.2.12.Final.jar!/:5.2.12.Final (revision: f6563)]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequiresNew.doIntercept(TransactionalInterceptorRequiresNew.java:55) [narayana-jts-idlj-5.2.12.Final.jar!/:5.2.12.Final (revision: f6563)]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.intercept(TransactionalInterceptorBase.java:76) [narayana-jts-idlj-5.2.12.Final.jar!/:5.2.12.Final (revision: f6563)]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequiresNew.intercept(TransactionalInterceptorRequiresNew.java:47) [narayana-jts-idlj-5.2.12.Final.jar!/:5.2.12.Final (revision: f6563)]
at sun.reflect.GeneratedMethodAccessor303.invoke(Unknown Source) ~[na:na]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_111]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_111]
at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:74) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.WeldInvocationContext.invokeNext(WeldInvocationContext.java:83) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.WeldInvocationContext.proceed(WeldInvocationContext.java:115) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.bean.InterceptorImpl.intercept(InterceptorImpl.java:108) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.as.weld.ejb.DelegatingInterceptorInvocationContext.proceed(DelegatingInterceptorInvocationContext.java:77) ~[wildfly-weld-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:68) ~[wildfly-weld-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:80) ~[wildfly-weld-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93) ~[wildfly-weld-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) ~[na:na]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) ~[na:na]
at com.intel.podm.common.enterprise.utils.retry.RetryOnRollbackInterceptor.invoke(RetryOnRollbackInterceptor.java:43) ~[enterprise-utils-2.1.3.4.0.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_111]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_111]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_111]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_111]
at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:89) ~[na:na]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) ~[na:na]
at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) ~[wildfly-weld-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) ~[wildfly-ee-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) ~[na:na]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) ~[na:na]
at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) ~[na:na]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ejb3.component.singleton.SingletonComponentInstanceAssociationInterceptor.processInvocation(SingletonComponentInstanceAssociationInterceptor.java:53) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:254) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:329) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:239) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) ~[na:na]
at org.jboss.as.ejb3.concurrency.ContainerManagedConcurrencyInterceptor.processInvocation(ContainerManagedConcurrencyInterceptor.java:110) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) ~[na:na]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) ~[na:na]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) ~[na:na]
at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:636) ~[na:na]
at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) ~[na:na]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) ~[na:na]
at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) ~[na:na]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) ~[na:na]
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195) ~[na:na]
at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) ~[na:na]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) ~[na:na]
at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) ~[na:na]
at com.intel.podm.discovery.external.EntityGraphMapper$$$view39.map(Unknown Source) ~[podm-discovery-2.1.3.4.0.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_111]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_111]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_111]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_111]
at org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:436) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:127) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at com.intel.podm.discovery.external.EntityGraphMapper$Proxy$$$Weld$EnterpriseProxy$.map(Unknown Source) ~[podm-discovery-2.1.3.4.0.jar:na]
at com.intel.podm.discovery.external.DiscoveryRunner.discover(DiscoveryRunner.java:97) [podm-discovery-2.1.3.4.0.jar:na]
at com.intel.podm.discovery.external.DiscoveryRunner.run(DiscoveryRunner.java:81) [podm-discovery-2.1.3.4.0.jar:na]
at com.intel.podm.discovery.external.DiscoveryRunner$Proxy$$$WeldSubclass.run$$super(Unknown Source) [podm-discovery-2.1.3.4.0.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_111]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_111]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_111]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_111]
at org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:49) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:77) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.invokeInOurTx(TransactionalInterceptorBase.java:117) [narayana-jts-idlj-5.2.12.Final.jar!/:5.2.12.Final (revision: f6563)]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequiresNew.doIntercept(TransactionalInterceptorRequiresNew.java:60) [narayana-jts-idlj-5.2.12.Final.jar!/:5.2.12.Final (revision: f6563)]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.intercept(TransactionalInterceptorBase.java:76) [narayana-jts-idlj-5.2.12.Final.jar!/:5.2.12.Final (revision: f6563)]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequiresNew.intercept(TransactionalInterceptorRequiresNew.java:47) [narayana-jts-idlj-5.2.12.Final.jar!/:5.2.12.Final (revision: f6563)]
at sun.reflect.GeneratedMethodAccessor303.invoke(Unknown Source) ~[na:na]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_111]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_111]
at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:74) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at com.intel.podm.discovery.external.DiscoveryRunner$Proxy$$$WeldSubclass.run(Unknown Source) [podm-discovery-2.1.3.4.0.jar:na]
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1626) [na:1.8.0_111]
at com.codahale.metrics.InstrumentedScheduledExecutorService$InstrumentedRunnable.run(InstrumentedScheduledExecutorService.java:235) [metrics-core-3.1.2.jar:3.1.2]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_111]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_111]
at org.glassfish.enterprise.concurrent.internal.ManagedFutureTask.run(ManagedFutureTask.java:141) [javax.enterprise.concurrent-1.0.jar!/:na]
at org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$101(ManagedScheduledThreadPoolExecutor.java:383) [javax.enterprise.concurrent-1.0.jar!/:na]
at org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:532) [javax.enterprise.concurrent-1.0.jar!/:na]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_111]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_111]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111]
at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250) [javax.enterprise.concurrent-1.0.jar!/:na]
Caused by: java.lang.IllegalArgumentException: Type specified for TypedQuery [com.intel.podm.business.entities.redfish.ComposedNode] is incompatible with query return type [class com.intel.podm.business.entities.redfish.ComposedNode]
at org.hibernate.jpa.spi.AbstractEntityManagerImpl.resultClassChecking(AbstractEntityManagerImpl.java:354) ~[hibernate-entitymanager-5.0.7.Final.jar!/:5.0.7.Final]
at org.hibernate.jpa.spi.AbstractEntityManagerImpl.createNamedJpqlQuery(AbstractEntityManagerImpl.java:759) ~[hibernate-entitymanager-5.0.7.Final.jar!/:5.0.7.Final]
at org.hibernate.jpa.spi.AbstractEntityManagerImpl.buildQueryFromName(AbstractEntityManagerImpl.java:743) ~[hibernate-entitymanager-5.0.7.Final.jar!/:5.0.7.Final]
at org.hibernate.jpa.spi.AbstractEntityManagerImpl.createNamedQuery(AbstractEntityManagerImpl.java:890) ~[hibernate-entitymanager-5.0.7.Final.jar!/:5.0.7.Final]
at org.jboss.as.jpa.container.AbstractEntityManager.createNamedQuery(AbstractEntityManager.java:99) ~[wildfly-jpa-10.0.0.Final.jar!/:10.0.0.Final]
at com.intel.podm.business.entities.dao.ComposedNodeDao.getComposedNodesEligibleForRecovery(ComposedNodeDao.java:33) ~[podm-business-entities-2.1.3.4.0.jar:na]
at com.intel.podm.business.entities.dao.ComposedNodeDao$Proxy$$$WeldSubclass.getComposedNodesEligibleForRecovery$$super(Unknown Source) ~[podm-business-entities-2.1.3.4.0.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_111]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_111]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_111]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_111]
at org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:49) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:77) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.invokeInCallerTx(TransactionalInterceptorBase.java:129) [narayana-jts-idlj-5.2.12.Final.jar!/:5.2.12.Final (revision: f6563)]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorMandatory.doIntercept(TransactionalInterceptorMandatory.java:59) ~[narayana-jts-idlj-5.2.12.Final.jar!/:5.2.12.Final (revision: f6563)]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.intercept(TransactionalInterceptorBase.java:76) [narayana-jts-idlj-5.2.12.Final.jar!/:5.2.12.Final (revision: f6563)]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorMandatory.intercept(TransactionalInterceptorMandatory.java:51) ~[narayana-jts-idlj-5.2.12.Final.jar!/:5.2.12.Final (revision: f6563)]
at sun.reflect.GeneratedMethodAccessor287.invoke(Unknown Source) ~[na:na]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_111]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_111]
at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:74) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at com.intel.podm.business.entities.dao.ComposedNodeDao$Proxy$$$WeldSubclass.getComposedNodesEligibleForRecovery(Unknown Source) ~[podm-business-entities-2.1.3.4.0.jar:na]
at com.intel.podm.discovery.ComposedNodeUpdater.reattachComposedNodeResources(ComposedNodeUpdater.java:90) ~[podm-discovery-2.1.3.4.0.jar:na]
at com.intel.podm.discovery.ComposedNodeUpdater.updateRelatedComposedNodes(ComposedNodeUpdater.java:73) ~[podm-discovery-2.1.3.4.0.jar:na]
at com.intel.podm.discovery.ComposedNodeUpdater$Proxy$$$WeldSubclass.updateRelatedComposedNodes$$super(Unknown Source) ~[podm-discovery-2.1.3.4.0.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_111]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_111]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_111]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_111]
at org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:49) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:77) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.invokeInCallerTx(TransactionalInterceptorBase.java:129) [narayana-jts-idlj-5.2.12.Final.jar!/:5.2.12.Final (revision: f6563)]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorMandatory.doIntercept(TransactionalInterceptorMandatory.java:59) ~[narayana-jts-idlj-5.2.12.Final.jar!/:5.2.12.Final (revision: f6563)]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.intercept(TransactionalInterceptorBase.java:76) [narayana-jts-idlj-5.2.12.Final.jar!/:5.2.12.Final (revision: f6563)]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorMandatory.intercept(TransactionalInterceptorMandatory.java:51) ~[narayana-jts-idlj-5.2.12.Final.jar!/:5.2.12.Final (revision: f6563)]
at sun.reflect.GeneratedMethodAccessor287.invoke(Unknown Source) ~[na:na]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_111]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_111]
at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:74) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at com.intel.podm.discovery.ComposedNodeUpdater$Proxy$$$WeldSubclass.updateRelatedComposedNodes(Unknown Source) ~[podm-discovery-2.1.3.4.0.jar:na]
at com.intel.podm.discovery.external.finalizers.psme.PsmeDiscoveryFinalizer.finalize(PsmeDiscoveryFinalizer.java:52) ~[podm-discovery-2.1.3.4.0.jar:na]
at com.intel.podm.discovery.external.finalizers.psme.PsmeDiscoveryFinalizer$Proxy$$$WeldSubclass.finalize$$super(Unknown Source) ~[podm-discovery-2.1.3.4.0.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_111]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_111]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_111]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_111]
at org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:49) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:77) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.invokeInCallerTx(TransactionalInterceptorBase.java:129) [narayana-jts-idlj-5.2.12.Final.jar!/:5.2.12.Final (revision: f6563)]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorMandatory.doIntercept(TransactionalInterceptorMandatory.java:59) ~[narayana-jts-idlj-5.2.12.Final.jar!/:5.2.12.Final (revision: f6563)]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.intercept(TransactionalInterceptorBase.java:76) [narayana-jts-idlj-5.2.12.Final.jar!/:5.2.12.Final (revision: f6563)]
at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorMandatory.intercept(TransactionalInterceptorMandatory.java:51) ~[narayana-jts-idlj-5.2.12.Final.jar!/:5.2.12.Final (revision: f6563)]
at sun.reflect.GeneratedMethodAccessor287.invoke(Unknown Source) ~[na:na]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_111]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_111]
at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:74) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68) [weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at com.intel.podm.discovery.external.finalizers.psme.PsmeDiscoveryFinalizer$Proxy$$$_WeldSubclass.finalize(Unknown Source) ~[podm-discovery-2.1.3.4.0.jar:na]
at com.intel.podm.discovery.external.finalizers.DiscoveryFinalizer.lambda$finalizeDiscovery$0(DiscoveryFinalizer.java:47) ~[podm-discovery-2.1.3.4.0.jar:na]
at java.util.Optional.ifPresent(Optional.java:159) ~[na:1.8.0_111]
at com.intel.podm.discovery.external.finalizers.DiscoveryFinalizer.finalizeDiscovery(DiscoveryFinalizer.java:47) ~[podm-discovery-2.1.3.4.0.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_111]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_111]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_111]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_111]
at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) ~[na:na]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) ~[na:na]
at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82) ~[wildfly-weld-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93) ~[wildfly-weld-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) ~[na:na]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) ~[na:na]
at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:64) ~[weld-core-impl-2.3.2.Final.jar!/:2.3.2.Final]
at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) ~[wildfly-weld-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) ~[wildfly-ee-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) ~[na:na]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) ~[na:na]
at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) ~[na:na]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ejb3.component.singleton.SingletonComponentInstanceAssociationInterceptor.processInvocation(SingletonComponentInstanceAssociationInterceptor.java:53) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) ~[na:na]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:254) ~[wildfly-ejb3-10.0.0.Final.jar!/:10.0.0.Final]
... 188 common frames omitted

psme network agent udev issues

We are seeing some issues with network agent code: can you please help us with these queries ?

We are seeing that all the udev APIs in sysfs.cpp fails when we run the network agent on ubuntu 14.
Also the netlink socket calls are not going through.

Thanks
Anand

Error when compiling PSME on Fedora 20

Hello.

When trying to compile PSME on Fedora 20, I get the following error:

Any help to solve this would be appreciated. Thanks.

run PSME server and compute simulator and PODM but not found compute assets

Dear intel,
I run PSME server and compute simulator and PODM, but not found compute assets,

PSME server started by the command
sudo ./psme-rest-server ../../application/config/psme-rest-server-configuration.json

PSME compute simulator started by the command
sudo ./psme-compute-simulator ../../agent-simulator/compute/configuration.json

PODM installed and check service running by these commands
service --status-all

[ + ] ntp
[ - ] pod-manager
[ + ] pod-manager-configuration-agent
[ + ] postgresql

sudo service postgresql status

sudo service pod-manager status

but check POMD log and web server, not found the compute assets by these commands
tail /var/log/wildfly/console.log

tail /opt/pod-manager/wildfly/standalone/log/server.log

PODM IP : 192.168.1.135

accessing POD manager REST API

access POD API web
https://:8443/redfish/v1

https://192.168.1.135:8443/redfish/v1

Regarding psme-network agent compilation

We are trying to compile psme-network agent, and it fails due to missing fm10kd-devel package.
In the PSME User Guide, its mentioned that the package is available for fedora but not for Ubuntu.

Can you please help in locating this package for Ubuntu ?

Cmake error reports that a particular header file is missing, hence failing out. Can you please let us know what functionality is required from this package.

Many Thanks
Anand

Safe-string-0.0.1 library compilation error

Dear intel ,

I install PSME make all j8 has error on ubuntu 16.04 but pass on Fedora 23

the following is my steps, please support, thank you -

ubuntu 16.04
select [About the Computer] -> [Install Update]
after download and installed completed, reboot.

sudo apt-get install cmake clang gcc-5 g++-5 libgcrypt20-dev libncurses5-dev
libnl-3-dev libudev-dev libglibmm-2.4-dev libglib3.0-cil-dev libxml++2.6-dev
libgnutls-dev libnl-route-3-dev flex bison valgrind doxygen cmake cpp ccache
build-essential linux-libc-dev libmpc-dev libstdc++6 libcurl4-openssl-dev
libmicrohttpd-dev lcov libxml++2.6-dev libnl-3-dev libnl-route-3-200 libudev-dev
libgcrypt20-dev libgnutls-dev libpopt-dev libusb-dev patch
libdevmapper-dev liblvm2-dev unzip libnl-genl-3-dev libblkid-dev debsigs
debsig-verify gnupg libusb-1.0-0-dev

cd /home/user/intelRSD/intelRSD-2-2/PSME/third_party

./download.sh

user@psme4:~/intelRSD/intelRSD-2-2/PSME/third_party$ ls -al
total 21380
drwxrwxr-x 2 user user 4096 鈭? 3 03:44 .
drwxrwxr-x 12 user user 4096 鈭? 3 03:53 ..
-rw-rw-r-- 1 user user 3498551 ?? 19 2017 curl-7.54.0.tar.gz
-rwxr-xr-x 1 user user 958 ?? 22 16:23 download.sh
-rw-rw-r-- 1 user user 192341 鈭? 3 03:44 EosSdk-stubs-1.13.0.tar.gz
-rw-rw-r-- 1 user user 2897695 銝� 18 2017 gcrypt-1.7.6.tar.bz2
-rw-rw-r-- 1 user user 371264 鈭? 3 03:44 gmock-1.7.0.zip
-rw-rw-r-- 1 user user 1671264 鈭? 6 2012 gmp-5.0.5.tar.xz
-rw-rw-r-- 1 user user 7166932 鈭? 12 2017 gnutls-3.5.9.tar.xz
-rw-rw-r-- 1 user user 813060 鈭? 28 2017 gpg-error-1.27.tar.bz2
-rw-rw-r-- 1 user user 633003 鈭? 3 03:44 gtest-1.7.0.zip
-rw-rw-r-- 1 user user 772570 鈭? 6 2016 ipmitool-1.8.17.tar.bz2
-rw-rw-r-- 1 user user 1309560 鈭? 3 2017 libmicrohttpd-0.9.54.tar.gz
-rw-rw-r-- 1 user user 1887927 ?? 1 2016 nettle-3.3.tar.gz
-rw-rw-r-- 1 user user 291 ?? 22 16:23 README.md
-rw-rw-r-- 1 user user 244202 鈭? 3 03:44 safestring-0.0.1.zip
-rw-rw-r-- 1 user user 397048 銝? 5 2008 uuid-1.6.2.tar.gz

Building release version:

cd /home/user/intelRSD/intelRSD-2-2/PSME

mkdir build

cd /home/user/intelRSD/intelRSD-2-2/PSME/build

sudo cmake ..

-- Configuring done
-- Generating done
-- Build files have been written to: /home/user/intelRSD/intelRSD-2-2/PSME/build

sudo make all -j8

sudo make all -j8
Scanning dependencies of target ipmi-base
Scanning dependencies of target base64
Scanning dependencies of target generic_mdr
Scanning dependencies of target logger
Scanning dependencies of target sysfsref
Scanning dependencies of target md5
Scanning dependencies of target uuid
Scanning dependencies of target database
[ 0%] Building CXX object common/mdr/CMakeFiles/generic_mdr.dir/src/printers.cpp.o
[ 1%] Building CXX object common/base64/CMakeFiles/base64.dir/src/base64.cpp.o
[ 1%] Building CXX object common/sysfs/CMakeFiles/sysfsref.dir/src/path.cpp.o
[ 1%] Building C object common/md5/CMakeFiles/md5.dir/src/md5.c.o
[ 1%] Building CXX object common/database/CMakeFiles/database.dir/src/database.cpp.o
[ 1%] Building CXX object common/uuid/CMakeFiles/uuid.dir/uuid-1.6.2/uuid++.cc.o
[ 1%] Building C object common/logger/CMakeFiles/logger.dir/src/logger.c.o
[ 1%] Building CXX object common/ipmi/src/CMakeFiles/ipmi-base.dir/connection_data.cpp.o
[ 1%] Linking C static library ../../lib/libmd5.a
[ 1%] Building CXX object common/logger/CMakeFiles/logger.dir/src/logger.cpp.o
[ 1%] Building C object common/uuid/CMakeFiles/uuid.dir/uuid-1.6.2/uuid.c.o
[ 1%] Built target md5
[ 2%] Building CXX object common/ipmi/src/CMakeFiles/ipmi-base.dir/bridge_info.cpp.o
In file included from /home/user/intelRSD/intelRSD-2-2/PSME/build/include/safe-string/safe_lib.h:59:0,
from /home/user/intelRSD/intelRSD-2-2/PSME/build/include/safe-string/safe_mem_lib.h:36,
from /home/user/intelRSD/intelRSD-2-2/PSME/common/uuid/uuid-1.6.2/uuid.c:54:
/home/user/intelRSD/intelRSD-2-2/PSME/build/include/safe-string/safe_str_lib.h:268:8: error: unknown type name ?char_t?? extern wchar_t *
^
compilation terminated due to -Wfatal-errors.
common/uuid/CMakeFiles/uuid.dir/build.make:86: recipe for target 'common/uuid/CMakeFiles/uuid.dir/uuid-1.6.2/uuid.c.o' failed
make[2]: *** [common/uuid/CMakeFiles/uuid.dir/uuid-1.6.2/uuid.c.o] Error 1
CMakeFiles/Makefile2:600: recipe for target 'common/uuid/CMakeFiles/uuid.dir/all' failed
make[1]: *** [common/uuid/CMakeFiles/uuid.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 2%] Building CXX object common/ipmi/src/CMakeFiles/ipmi-base.dir/management_controller.cpp.o
[ 2%] Building CXX object common/mdr/CMakeFiles/generic_mdr.dir/src/generic_entry_point.cpp.o
[ 2%] Linking CXX static library ../../lib/libbase64.a
[ 2%] Built target base64
[ 2%] Building CXX object common/logger/CMakeFiles/logger.dir/src/logger_options.cpp.o
[ 2%] Building CXX object common/database/CMakeFiles/database.dir/src/file_database.cpp.o
[ 2%] Building CXX object common/database/CMakeFiles/database.dir/src/persistent_attributes.cpp.o
[ 2%] Building CXX object common/logger/CMakeFiles/logger.dir/src/logger_factory.cpp.o
[ 2%] Linking CXX static library ../../lib/libgeneric_mdr.a
[ 2%] Built target generic_mdr
[ 3%] Building CXX object common/sysfs/CMakeFiles/sysfsref.dir/src/sysfs_interface.cpp.o
[ 3%] Building CXX object common/sysfs/CMakeFiles/sysfsref.dir/src/abstract_sysfs_interface.cpp.o
[ 3%] Building CXX object common/ipmi/src/CMakeFiles/ipmi-base.dir/ipmi_controller.cpp.o
[ 3%] Building C object common/logger/CMakeFiles/logger.dir/src/logger_alloc.c.o
[ 3%] Building C object common/logger/CMakeFiles/logger.dir/src/logger_buffer.c.o
[ 3%] Building CXX object common/ipmi/src/CMakeFiles/ipmi-base.dir/ipmi_interface.cpp.o
[ 3%] Building C object common/logger/CMakeFiles/logger.dir/src/logger_color.c.o
[ 3%] Building CXX object common/ipmi/src/CMakeFiles/ipmi-base.dir/ipmi_interface_factory.cpp.o
[ 3%] Building CXX object common/ipmi/src/CMakeFiles/ipmi-base.dir/message.cpp.o
[ 4%] Building C object common/logger/CMakeFiles/logger.dir/src/logger_level.c.o
[ 4%] Building CXX object common/ipmi/src/CMakeFiles/ipmi-base.dir/request.cpp.o
[ 4%] Building CXX object common/ipmi/src/CMakeFiles/ipmi-base.dir/response.cpp.o
[ 4%] Linking CXX static library ../../lib/libsysfsref.a
[ 4%] Building C object common/logger/CMakeFiles/logger.dir/src/logger_list.c.o
[ 4%] Building C object common/logger/CMakeFiles/logger.dir/src/logger_stream.c.o
[ 4%] Built target sysfsref
[ 4%] Building CXX object common/logger/CMakeFiles/logger.dir/src/logger_stream.cpp.o
[ 4%] Building CXX object common/ipmi/src/CMakeFiles/ipmi-base.dir/response_error.cpp.o
[ 4%] Building CXX object common/ipmi/src/CMakeFiles/ipmi-base.dir/sel_record.cpp.o
[ 4%] Building C object common/logger/CMakeFiles/logger.dir/src/logger_time.c.o
[ 4%] Building C object common/logger/CMakeFiles/logger.dir/src/stream/logger_stream_config.c.o
[ 4%] Building C object common/logger/CMakeFiles/logger.dir/src/stream/logger_stream_file.c.o
[ 4%] Building C object common/logger/CMakeFiles/logger.dir/src/stream/logger_stream_socket.c.o
[ 4%] Building C object common/logger/CMakeFiles/logger.dir/src/stream/logger_stream_standard.c.o
[ 4%] Building CXX object common/ipmi/src/CMakeFiles/ipmi-base.dir/sel.cpp.o
[ 4%] Building CXX object common/ipmi/src/CMakeFiles/ipmi-base.dir/utils/byte_buffer.cpp.o
[ 4%] Building CXX object common/ipmi/src/CMakeFiles/ipmi-base.dir/telemetry/telemetry_hub.cpp.o
[ 4%] Building CXX object common/ipmi/src/CMakeFiles/ipmi-base.dir/utils/sdv/mdr_region_accessor.cpp.o
[ 4%] Linking CXX static library ../../lib/liblogger.a
[ 4%] Built target logger
[ 5%] Building CXX object common/ipmi/src/CMakeFiles/ipmi-base.dir/utils/sdv/purley_mdr_region_accesor.cpp.o
[ 5%] Building CXX object common/ipmi/src/CMakeFiles/ipmi-base.dir/utils/sdv/grantley_mdr_region_accessor.cpp.o
[ 5%] Building CXX object common/ipmi/src/CMakeFiles/ipmi-base.dir/utils/sdv/linear_to_double.cpp.o
[ 5%] Linking CXX static library ../../lib/libdatabase.a
[ 5%] Built target database
[ 5%] Built target ipmi-base
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2
user@psme4:~/intelRSD/intelRSD-2-2/PSME/build$

Question - PODM do not find PSME REST server when not add psme service in services list

Dear intel,
the issue is related to -
Question for PODM do not find second PSME server and PSME compute simulator #50,

PODM can find PSME compute asset after I add psme service in : /tmp/services.list
https://<PSME_IP>:8443/redfish/v1 psme

but if I do not add psme service in : /tmp/services.list,
PODM can not find PSME REST server.

the following is my detail checking,
Please support, thank you.
House

[PSME] Configuration file "bdc_r_configuration.json" is missing or postint is outdated

Hi,

the file bdc_r_configuration.json is missing in this repository, it exists in the v1.1 repository which is outdated. Some postint refeer to this file. Can you clarify if I can use the file from the v1.1 version or if the postinst files are not up to date.

https://github.com/01org/intelRSD/PSME/agent-intel/packages/DEB/psme-compute-intel/DEBIAN/postinst

install PODM no error but not found OrientDB and WildFly

Dear Intel
I download intel RSD Git last version 2.2 and compiled and deployed PODM,
following 332871-003 POD user guide,
after install packages in guide "3.3. Prerequisties" and "4. POD Manager Compilation",
and "5. Application server and Database Configuration" said that OrientDB and WildFly will be deployed after installed PODM .deb package,
could you help to support ? thank you
House

Question - Can PSME compute agent auto find new BMC

Dear intel ,
the question is related to #53,
Question - PSME compute agent - Can it find MUX or BMC devices without IP address settings,

if new computer server with BMC was added into network,
Can PSME compute agent auto find the new BMC ?
thank you
currently I need to add slot information into configuration.json.
House

Question for PODM do not find second PSME server and PSME compute simulator

Dear intel -
the question is related to -
run PSME server and compute simulator and PODM but not found compute assets #38

I successfully startup a PODM (OS: ubuntu16.04, IP: 192.168.1.135, hostname : podm1)
and first PSME server and PSME compute simulator (OS: ubuntu16.04, IP: 192.168.1.105, hostname : psme1),
first PSME server built LUI (Linux Utility Image - bzimage) and copyed to PODM,

in PODM - https://localhost:8443/redfish/v1/Systems
found first PSME compute asset ( 1 host),
in PODM - https://localhost:8443/redfish/v1/Systems/1-s-10
I can see the first PSME compute asset,

but second PSME server do not build LUI (Linux Utility Image - bzimage),
but when I startup second PSME server and PSME compute simulator (OS: ubuntu16.04, IP: 192.168.1.87, hostname : psme2),
in PODM - https://localhost:8443/redfish/v1/Systems
only found first PSME compute asset (1 host),
PODM do not find second PSME compute asset.

my Questions are -
Q1. Does second PSME server need to build again LUI ?

Q2. if second PSME server build a new LUI, file name is bzimage, Does it need to rename to another file name ?

Q3. if second PSME LUI (bzimage) will copy to PODM - /opt/pod-manager/wildfly/discovery/bzimage, the first PSME's LUI file will be overwrite, Is it a problem ?

thank you
House

run PSME-compute but has error message

Deat Intel
I prepare Ubuntu 14.04 LTS. and download Intel RSD Git last ver. 2.2.
I follow 335460-003 PSME user guide "3 , PSME Develop Enviroment"
installed PSME packages and its agents, and use root.crt as ca.crt and generate server.key and ,crt,
"rmm-present" is false,
run PSME REST server success,
sudo ./psme-rest-server ../../application/config/psme-rest-server-configuration.json

but run psme-compute have error message
sudo ./psme-compute ../../agent/compute/configuration.json

2017-12-29 10:36:45.705924178 - ERROR - db - Cannot write file /var/opt/psme/compute-service-uuid.json
2017-12-29 10:36:45.705935923 - INFO - default - Service UUID 1cb9d204-ec41-11e7-a28d-df8968720580 assigned and stored.
2017-12-29 10:36:45.712996847 - INFO - registration - Agent has been registered to http://localhost:8383, interval 3s, rest runs for 0s
2017-12-29 10:36:45.713010062 - INFO - eventing - Sending AMC notifications enabled.
2017-12-29 10:36:48.734942629 - INFO - agent - gpio minimal read interval: 5000ms
2017-12-29 10:36:48.736868600 - ERROR - default - Unable to send/receive data to/from MUX: Connection refused
2017-12-29 10:36:53.736477394 - ERROR - default - Unable to send/receive data to/from MUX: Connection refused

Please support, thank you
House

[PSME] 2 memory leaks

logger
"msg" should be freed at the end of this function.
make_uuid
"char*" returned from id.string() should be freed manually.

DiscoveryCancelable flag in discovery.json

Dear Intel,

I have a question about discovery config, I check for pod-manager source code,
I guess DiscoveryCancelable in discovery.json is used for cancel discovery job(polling external service job),

But I don't know why I need this flag, I didn't find any document interpret about this configuration.
could you please give me some hint about the usage of this configuration? #

Shared storage for composed nodes

Hi,

I would like to know how to create a shared isci storage target between two nodes using intel RSD.
My objective is to create a shared storage between two composed nodes so that the composed nodes mount
them at particular location.

We thought of using remote isci storage target but one target could not be allocated to two composed nodes(even if they have different IQN).
When we try to allocate the same remote storage target to different composed nodes, it gives

'/redfish/v1/Nodes/Actions/Allocate' (status 409): '{
            "error" : {
                   "code" : "Base.1.0.ResourcesStateMismatch",
                   "message" : "Conflict during allocation",
                   "@Message.ExtendedInfo" : [ {
                   "Message" : "Specified remote target (iqn.2017-06.com:test2) is currently in use."
             } ]
      }

Is there any way to achieve shared storage between nodes using Intel RSD?

Thanks in advance.

Confusion about the composed node

Hello, I am confused about the "Composed Node"

According to the API, "Composed Node" seems just like resource Virtual Machine, but it is obvious not, because virtualization can not be conducted on bare metal.
I noticed that the pod-manager-api-specification said that:

Currently a user can request allocation of a single node with a single request. Node components--CPU,memory,local storage,network interface--must be located on a single physical blade. Remote storage can be located anywhere in the Pod.

Then I got the following questions:

Is it possible to compose more than one node on a single physical server, if it is, how dose it be implemented, if not, there is no limitations mentioned on API specification.
If composing a node is just marking the resource(Allocate) and specifying the boot source(Assemble), dose it make any sense? Is there any supposed usage scenario or is there any existing use case.
Is there any further plan to break these hardware limitations and make Composed Node more flexible, and how?

PSME configuration issue

Hi,
We have been trying to get a demo virtual environment of RSD running and I might be missing something, but we have run into some issues. Having set up POD Manager and RMM we moved on to a PSME server with a few agents. As I used the standard setting with RMM distributing the certificates I ran into Exception -32601: METHOD_NOT_FOUND which I assumed, perhaps wrongfully, is caused by the fact that I have relied on the stub for the HAL driver without implementing anything on my own.
Hence, I opted for a configuration without an RMM and I placed the PODM certificate in /etc/psme/certs manually. However, for some reason the PSME certificate (server.cert and server.key) does not get generated automatically. Since I also had to create the /etc/psme manually, I assume something went wrong with the building/installation process but I have followed the documentation carefully. I am quite confused as to what the real problem might be. Could you advise?

Questions how PSME compute agent send IPMI commands to BMC AST2400 2500 and remove CY7C65215

Dear intel -
the questions are related to these issues No. -

run PSME-compute but has error message #34,
run cyMUX -f but have error message #35,

Q1 - Currently I have no the hardware USB-Serial Bridge Controller CY7C65215 - Cypress Semiconductor,
and I setup 2 PSME servers that have BMC - ASPEED AST2400 / AST2500 chip,
if PSME compute agent want to send IPMI commands (ex: get Device ID) to BMC - AST2400 / AST2500,
because currently BMC (AST2400 / AST2500) don't support PSME REST API,
I think that PSME compute agent use IPMI commands to communicate with BMC,
Could you have suggestions ?
Does it only modify configuration (.hpp) ?
or need to modify a lot of code (.hpp, *.cpp) ? thanks.

Q2 - The PSME Compute Agent requires communication with the Cypress USB to I2C driver,
which is provided by the cyMUX service.
if PSME Compute Agent want to remove Cypress USB to I2C driver,
Could you have suggestions ? thank you.

House

Why is initatior-name is set to ALL in the targets config file?

Hi,

I have seen that the initator-name is set to "ALL" in the targets config file. From the manpage

initiator-address <addr>
    Allows connections only from the specified IP address. Defaults to ALL if no initiator-address directive is specified. 

initiator-name <addr>
    Allows connections only from the specified initiator name.

This configuration seems to be wrong. I didn't find a section in the code where initiator-name is set to ALL. I could only find the initator-address which is set to ALL. Do you know why this could happen?

This issue blocks iscsi target discovery (Ubuntu 16.04) using iscsiadm (open-iscsi, command: iscsiadm -m discovery -t st -p <psme_portal_ip>). Discovery works if I delete this line manually on the storage node in the targets config file.

I tested it with rsdv1 and debian jessie

run cyMUX -f but have error message

Dear Intel
I prepare Ubuntu 14.04 LTS. and download Intel RSD Git last ver. 2.2.
I follow README file in the Git package \intelRSD-2.2\tools\CyMUX
to build the tool by make command ,
and Installing library on Ubuntu x86_64 target and binaries.

the README said "cyMUX should be run as a service during start up."
but I can see byMUX at service list and
run
/usr/bin/cyMUX -?
and
/usr/bin/cyMUX -f
Error: CY7C65215: HW detection failed (or already bound by another process)

Please help to support the error message, thank you.
House

Question - PSME compute agent - How to send IPMI OEM command to BMC

but If I want to add IPMI OEM command, need to add new Net function ID, new command ID,
Could you have suggestions ? thank you.
House

Unable to compose node

I am able to compose/manage node based on Intel PODM, but after an unexpected outage in our lab, everything looks like in a mess, I cannot recover it anymore.

I am consisting see the below exceptions from the pod-manager-application.log,
2017-10-27 01:12:38,513 [EE-ManagedScheduledExecutorService-EventsExecutor-Thread-1] ERROR c.i.p.d.e.event.EventSubscribeRunner - Error while subscribing to event service for '4c4c4544-434d-1001-8000-44a8421764ac': Couldn't create valid PodM Event Service destination

If am trying to allocate node, but I see the exceptions like this:
allocate_node.txt

And if I am trying to power off or restart some node, I see this exceptions:
force_off.txt

Looks like node is not is a right status, so I check the status and got the output like below:
node_statue.txt

The node's status is indeed "Absent", so what does that mean by "Absent", how can I make it "Healthy" or "Enabled"?

Could you anyone help me get it back to normal? thanks a lot!

cmake error

Installing: /u01/intelRSD-master/PSME/build/include/jsonrpccpp/common
-- Installing: /u01/intelRSD-master/PSME/build/include/jsonrpccpp/common/jsonparser.h
-- Package JsonRpcCpp/JSONRPCCPP built
-- Looking for package JsonRpcCpp/JSONRPCCPP
-- Find package JsonRpcCpp/JSONRPCCPP, module jsonrpccpp
-- checking for module 'jsonrpccpp'
-- found jsonrpccpp, version 0.6.0.master
CMake Warning at cmake/InstallScriptsCommon.cmake:378 (message):
Cannot find library jsonrpccpp-server required for JsonRpcCpp/JSONRPCCPP
Call Stack (most recent call first):
cmake/FindJsonRpcCpp.cmake:19 (find_package_local)
cmake/InstallScriptsCommon.cmake:254 (find_package)
cmake/InstallScriptsCommon.cmake:269 (build_and_find_afterward)
CMakeLists.txt:91 (install_third_party)

CMake Error at cmake/InstallScriptsCommon.cmake:258 (message):
Package JsonRpcCpp/JSONRPCCPP not found after build
Call Stack (most recent call first):
cmake/InstallScriptsCommon.cmake:269 (build_and_find_afterward)
CMakeLists.txt:91 (install_third_party)

-- Configuring incomplete, errors occurred!

intel / intelrsd Goto Github PK

intelrsd's Introduction

Intel® Rack Scale Design Reference Software

Getting Started

Documents

Support

News

Coming Soon: Automation through Ansible Galaxy*

[July 2019] v2.5 of the Intel® RSD reference software has been released!

[April 2019] v2.4 of the Intel® RSD reference software has been released!

[September 2018] v2.3.2 of the Intel® RSD reference software has been released!

[July 2018] v2.3.1 of the Intel® RSD reference software has been released!

[May 2018] v2.3 of the Intel® RSD reference software has been released!

Disclaimer

intelrsd's People

Contributors

Stargazers

Watchers

Forkers

intelrsd's Issues

Log:

the following is my steps, please support, thank you -

Recommend Projects

Recommend Topics

Recommend Org

Intel^® Rack Scale Design Reference Software

[July 2019] v2.5 of the Intel^® RSD reference software has been released!

[April 2019] v2.4 of the Intel^® RSD reference software has been released!

[September 2018] v2.3.2 of the Intel^® RSD reference software has been released!

[July 2018] v2.3.1 of the Intel^® RSD reference software has been released!

[May 2018] v2.3 of the Intel^® RSD reference software has been released!