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

[housemic]

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

[tbykowsk]

Hi @housemic,

POD Manager automatically discovers PSME services using DHCP or SSDP protocols (details in section 3.1 of PODM User Guide), but you can also add a service manually. In this case, you should create a /tmp/services.list file on a machine where PODM is running. In this file add a line with an address to REST API and a type of service (psme - for Compute service, rss - for Storage service, rmm - for RMM service, lui - for Deep Discovery service). For example, for a Compute service the line should look like this:
https://10.3.0.123:8443/redfish/v1 psme

In general, PSME Compute Simulator was designed for the Deep Discovery feature (specifics in section 2.2 of PSME User Guide and 6.3 of PODM User Guide), so it may not be suitable to act as a stand-alone PSME Compute service.

If you want to use PODM with mocked PSME data, then it might be easier to use PSME REST API Simulators.

[housemic]

Dear tbykowsk,

the following steps are creating /tmp/services.list and restart pod-manager :

PODM No.1
OS : uBuntu 16.04
hostname : podm1
IP Address : 192.168.1.135

---

PSME No.1
OS : uBuntu 16.04
hostname : psme1
IP Address : 192.168.1.105

---

PSME No.2
OS : Fedora 23
hostname : psme2
IP Address : 192.168.1.136

---

cat /etc/pod-manager/service-detection.json

{
"EnabledProtocols": [
"DHCP",
"SSDP"
],
"ServiceTypeMapping": {
"PSME": "PSME Service Root",
"RSS": "RSS Service Root",
"LUI": "LUI Service Root",
"RMM": "Root Service",
"INBAND": "In Band Service"
},
"Protocols": {
"SSDP": {
"AnnouncementFrequencyInSeconds": 600,
"MX": 5,
"Subnets": [
"0.0.0.0/0"
]
},
"DHCP": {
"FilesCheckIntervalInSeconds": 10,
"NumberOfRetriesForFailedServiceCheck": 5,
"FailedEndpointRecheckIntervalInSeconds": 300
}
}
}

---

ls -al /tmp/services.list
ls: cannot access '/tmp/services.list': No such file or directory

---

sudo gedit /tmp/services.list

https://192.168.1.105:8443/redfish/v1/ psme
https://192.168.1.136:8443/redfish/v1/ psme

---

cat /tmp/services.list

https://192.168.1.105:8443/redfish/v1/ psme
https://192.168.1.136:8443/redfish/v1/ psme

---

sudo gedit /tmp/services.list

https://127.0.0.1:8448/redfish/v1/ inband

---

cat /tmp/services.list

https://192.168.1.105:8443/redfish/v1/ psme
https://192.168.1.136:8443/redfish/v1/ psme
https://127.0.0.1:8448/redfish/v1/ inband

---

cat /etc/pod-manager/inband-service-config.json

{
"InBandServiceSupportEnabled": false
}

---

sudo gedit /etc/pod-manager/inband-service-config.json

{
"InBandServiceSupportEnabled": true
}

---

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

---

sudo service postgresql restart

sudo service postgresql status

---

sudo service pod-manager restart

sudo service pod-manager status

---

cat /tmp/pod-manager/config/network-service.json

{
"Name" : "Manager Network Service",
"Description" : "Manager Network Service Status",
"State" : "Enabled",
"Health" : "OK",
"HostName" : "podm1",
"FQDN" : "podm1",
"HTTP" : {
"Enabled" : true,
"Port" : 8080
},
"HTTPS" : {
"Enabled" : true,
"Port" : 8443
},
"IPMI" : {
"Enabled" : false
},
"SSH" : {
"Enabled" : false
},
"SNMP" : {
"Enabled" : false
},
"VirtualMedia" : {
"Enabled" : false
},
"SSDP" : {
"Enabled" : false
},
"Telnet" : {
"Enabled" : false
},
"KVMIP" : {
"Enabled" : false
}
}

---

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

error message : 404 - not found

---

http://192.168.1.135:8080/redfish/v1

error message : 404 - not found

---

Does these steps have something wrong ?
thanks
House

[housemic]

Dear tbykowsk,
I installed IntelRSD 2.2/Simulators/
and run nodejs --harmony psme_mock.js
go to the PSME Mock web server http://127.0.0.1:9443/redfish/v1/Systems/1
can see hardware information.
House

[tbykowsk]

It seems that the WildFly service has not been deployed correctly.
Could you attach /var/log/wildfly/console.log and /var/log/pod-manager/pod-manager-application.log, please?

In addition verify which IP address is used by PODM:

PODM No.1
IP Address : 192.168.0.135

or

PODM IP : 192.168.1.135

[housemic]

Dear tbykowsk,

PODM No.1
OS : uBuntu 16.04
hostname : podm1
IP Address : 192.168.1.135

PSME No.1
OS : uBuntu 16.04
hostname : psme1
IP Address : 192.168.1.105

PSME No.2
OS : Fedora 23
hostname : psme2
IP Address : 192.168.1.136

[housemic]

Dear tbykowsk,
Attachment is /var/log/wildfly/console.log

console.log

[housemic]

Dear tbykowsk,
Attachment is /var/log/pod-manager/pod-manager-application.log

pod-manager-application.log

[housemic]

Dear tbykowsk,
Attachment is /var/log/pod-manager/pod-manager-services-detection.log

pod-manager-services-detection.log

[tbykowsk]

Thank you @housemic,

There is a problem with /etc/pod-manager/events.json configuration, your system does not seem to have eth0.4093 and eth0.4094 interfaces.
If you are running nodejs Simulators locally, then you should set all NetworkInterfaceName to lo. Alternatively, you may select an interface with a network to which PSMEs are connected.

[housemic]

Dear tbykowsk,
thank you
tomorrow I will setup /etc/pod-manager/events.json.

I installed nodejs Simulator (in IntelRSD 2.2/Simulators/) in PODM server and run nodejs PSME mock success,
I can see hardware information in http://127.0.0.1:9443/redfish/v1/Systems/1

and I have questions that

1. Do I install nodejs Simulators in PSME server
2. Does the nodejs Simulators connect to PODM Server ?
3. Can I see hardware information in http://192.168.1.135:9443/redfish/v1/Systems/1
   (192.168.1.135 is )
   thank you
   House

[housemic]

Dear tbykowsk,
I checked PODM events.json that is the same configuration as yours.
it has eth0.4093 and eth0.4094 interfaces.

ls -la /etc/pod-manager/events.json

user@podm1:~$ ls -la /etc/pod-manager/events.json
-rw-rw-r-- 1 root root 789 銝� 11 22:40 /etc/pod-manager/events.json

cat /etc/pod-manager/events.json

{
"Northbound": {
"DeliveryRetryAttempts": 2,
"DeliveryRetryIntervalSeconds": 1
},
"Southbound": {
"EventSubscriptionIntervalSeconds": 90,
"BufferedEventProcessing" : {
"ProcessingWindowSizeInSeconds": 5
},
"ServicesConfiguration": [
{
"ServiceType": "psme",
"NetworkInterfaceName": "eth0.4094",
"PodManagerIpAddress": null
},
{
"ServiceType": "rss",
"NetworkInterfaceName": "eth0.4093",
"PodManagerIpAddress": null
},
{
"ServiceType": "rmm",
"NetworkInterfaceName": "eth0.4094",
"PodManagerIpAddress": null
},
{
"ServiceType": "inband",
"NetworkInterfaceName": "lo",
"PodManagerIpAddress": null
}
]
}

[housemic]

Dear tbykowsk
I think it maybe wildfly issue..
because I can display PSME HW information when go to PSME Web site in PODM server

House

PODM No.1
OS : uBuntu 16.04
hostname : podm1
IP Address : 192.168.1.135

https://192.168.1.135:8443/redfish/v1
error message ; 404 - not found

---

PSME No.1
OS : uBuntu 16.04
hostname : psme1
IP Address : 192.168.1.105

https://192.168.1.135:8443/redfish/v1/Systems

it can display PSME HW information in PODM server

[tbykowsk]

Have you replaced in /etc/pod-manager/events.json all eth0.4093 and eth0.4094 to lo?
It will be simpler if you install nodejs Simulators on PODM server, not PSME.
When your setup is properly configured, then you will see on PODM Rest API Systems acquired from nodejs Simulators.

[housemic]

Dear tbykowsk,
about the issue of web browser error message - 404 - Not Found,
I found it is my mistake,
I rollback /etc/default/grub modification because it make system lag (slower).
I fix it after I modify /etc/default/grub following PODM user guide 2.7 setup GRUB.
thanks
House

[housemic]

Dear tbykowsk,
Currently I start PSME REST server and PSME compute simulator (Not nodejs simulator (PSME Mock)),
and I can see the PSME HW info in PODM server by WEb browser.
https://<PSME_IP_Addr>:8443/redfish/v1
Currently I don't need nodejs simulator (PSME Mock)).
House

[housemic]

Dear tbykowsk
my Question is -
in PODM server,
I can see PSME HW Information in the PODM server.
but PODM HW Information is empty (not found any assets).
(I don't install RMM)

House

---

PODM No.1
OS : uBuntu 16.04
hostname : podm1
IP Address : 192.168.1.135

https://192.168.1.135:8443/redfish/v1

https://192.168.1.135:8443/redfish/v1/Systems

https://192.168.1.135:8443/redfish/v1/Nodes

PODM HW Information is empty (not found any assets).

---

PSME No.1
OS : uBuntu 16.04
hostname : psme1
IP Address : 192.168.1.105

https://192.168.1.105:8443/redfish/v1

https://192.168.1.105:8443/redfish/v1/Systems

https://192.168.1.105:8443/redfish/v1/Systems/9

it can display PSME HW information in PODM server

[tbykowsk]

Do you mean that PSME Rest Server API at 192.168.1.105 displays hardware data, but PODM API at 192.168.1.135 does not?
Did you changed NetworkInterfaceName in /etc/pod-manager/events.json to the one connected to 192.168.1.* network?
Did you noticed in PODM logs any attempts to connect to PSME Rest Server?

[housemic]

Dear tbykowsk,
No,
my environment is :
one PODM Server (IP Addr : 192.168.1.135),
one PSME Server (IP Addr : 192.168.1.105), run PSME REST server + PSME compute simulator,
without RMM,

in the same PODM Server (192.168.1.135),
I use FireFox to see PODM REST API - https://localhost:8443/redfish/v1/Systems
not found assets.

in the same PODM Server (192.168.1.135),
I use FireFox to see PSME REST API - https://192.168.1.105:8443/redfish/v1/Systems
can find assets (1 host )

and https://192.168.1.105:8443/redfish/v1/Systems/9
can find its detail HW information (the data comes from PSME compute simulator)

Does it a setting problem ? thank you
House

[housemic]

Dear tbykowsk,
after modify event.json and install nodejs Simulaors,
there are additional PODM compute assets,
and I have more questions in issue #43.
in this question, I don't use nodejs simulator,
I only use PODM server + PSME REST server + PSME compute simulator and without RMM.
thank you.
House

[housemic]

Dear tbykowsk,
the issue can be closed, thank you.
House

after one night , PODM can find assets.
the HW information comes from PSME compute simulator
PODM maybe wait some hours time to find PSME assets.

I use PODM 2 Server that only have PODM SW and don't install nodejs simulator (don't run PSME Mock),

PODM 2 localhost -

PODM 2 IP address - 192.168.1.87 -

[tbykowsk]

You are welcome House, I am glad it works for you!