|
Post by sunitha on Feb 22, 2024 6:57:08 GMT
Thank you for the response.
I will check the schema for the CollectDiagnosticData to see if this can be suitable.
These are not dumps or debug logs. These are some persistent host configuration/resource data which should be accessible to all the admins (redfish client) connected. Our usecase needs this data to be available even when the system host is powered off. Thus we arrived at some specific directory at the BMC persistent file system to be the best place to store them. The storage is owned by the BMC, but the data is consumable to the host, and the managing redfish clients.
|
|
|
Post by sunitha on Feb 21, 2024 9:54:12 GMT
Any further thoughts ?
|
|
|
Post by sunitha on Feb 7, 2024 4:46:31 GMT
My use case is to allow the redfish client to use the server's persistency storage to save critical data as files. There is no SSH available to the server(we block it for security) to upload and manage files. Yes, I too share the same concerns of letting the file system edits - but there should be rules & validations at the server to allow the operations without causing any security threats.
|
|
|
Post by sunitha on Feb 6, 2024 7:07:25 GMT
I am looking for a redfish resource, which will represent the files as resources. With this, I should be able to perform create, read, update and delete a file at the servers file system. Something like redfish/v1/Systems/<systemdId>/FileCollection/<fileId>
There should be relevant security validations at the backend, and the spec can contain the allowed file content types, file permissions, max and min size limitations etc.
Please share your views on the same.
|
|
|
Post by sunitha on Jul 26, 2022 9:35:58 GMT
|
|
|
Post by sunitha on Jul 26, 2022 9:35:12 GMT
For (1) On a system with two interfaces; say eth0 and eth1 - when they are set with IP addresses belonging to the same subnet, we need a way to set the routing priorities on the routing table. Otherwise, kernel adds two default routes for the same subnet on both interfaces, and its not guaranteed as which interface is actually responding to the incoming packets. Setting the route priorities is achieved via the 'Metric' value in the routing table. For a dynamic address assignment(eg: DHCPv4), networkd assigns 1024 as the metric value by default. There is currently no way to set this Metric value for a Static configuration via Redfish PATCH command on EthernetInterface.
For (2) Static route configuration interface will help in setting up the system's network in such a way that, user can add another device(say a redfish client) to reach the system via a specific controlled route, other than using the default routes. This enables to have client and server at two different geo locations & two independent network zones.
|
|
|
Post by sunitha on May 17, 2022 14:02:06 GMT
|
|
|
Post by sunitha on Apr 12, 2022 14:16:36 GMT
One thing that has come up is trying to understand the need of controlling this on an interface by interface perspective. From my understanding, while it's possible to be that granular with the settings for NTP servers, is there a real practical need to support this? My impression is most users like to control this for the entirety of the manager rather than going through each of the interfaces, but if there really is a good usage for being specific to each of the interfaces, I'd like to understand that first. This is what i had received from the systemd experts. ------------------------------------------------------------------- About the question why NTP or DNS servers assigned by networkd is per-link config. Because each network interface may be connected to different network. For example, if the host is a router, then one interface is connected to upstream (WAN), and another is to downstream (LAN). In such case, the NTP or DNS provided through WAN interface cannot be connected through the LAN interface, and vice versa. And if the WAN interface becomes down, then timesyncd or resolved should and can handle that the DNS or NTP servers assigned to the WAN interface cannot be accessed if these settings are per-link. If these servers are assigned globally, these daemons cannot do like that. Anyway, this is the design of timesyncd, resolved, and networkd. And we cannot change that. And I do not think there is no good reason to change that. Closing. ------------------------------------------------------------------
|
|
|
Post by sunitha on Apr 8, 2022 9:55:18 GMT
@edtanous please share your views as well
|
|
|
Post by sunitha on Apr 8, 2022 9:34:00 GMT
Sure. Thank you ! I think we can still retain that global setting as per the systemd discussion. But we need the NTP servers at ethernet interface level as well - so that the systems which need two interfaces at two different subnets can do the required settings
|
|
|
Post by sunitha on Apr 7, 2022 5:28:18 GMT
The current NetworkProtocol schema has "NTPServers" property which lists the current active NTP servers set on the system. There is no way to differentiate between the DHCP provided NTP servers and the servers set by the user statically. This property should be defined similar to the "NameServers" and "StaticNameServers" where it can be clearly identifiable as which IP is set statically by the user. Another change needed is: NTPServers should also be made as properties of EthernetInterface resource. So that each ethernet interface, which may connect to different subnet of the system, can set different NTP servers. Please refer a systemd discussion on the same at github.com/systemd/systemd/issues/22384
|
|
|
Post by sunitha on Oct 5, 2021 13:05:22 GMT
Sounds good Jeff. Thank you.
|
|
|
Post by sunitha on Oct 4, 2021 14:07:15 GMT
mraineri Would redfish be interested in adding "InitiatedBy"/"CreatedBy" as an optional parameter at the LogEntry schema? Basically this can be used for a user initiated LogEntry (say user initiated dump) to give out the data as who triggered this.
|
|
|
Post by sunitha on Sept 30, 2021 13:25:17 GMT
Thanks for the quick answer mraineri . Yes. we have a use-case where we need to tie-up the LogEntry to the user who asked for it. Is there any other way to tag these with the current schema?
|
|
|
Post by sunitha on Sept 30, 2021 9:57:35 GMT
The LogEntry schema has a property "Link" , which can give the "OriginOfCondition" of the specific LogEntry. It is explained as "This property shall contain a link to the resource that caused the log entry."
My question is : When there is a user triggered (manually initiated) dump on a system, can this property be used to map to the session url which initiated the dump ?
Example response data for GET /redfish/v1/Managers/<manager>/LogServices/<id>/Entries/<id> {
... ... "Links": {
"OriginOfCondition": "/redfish/v1/SessionService/Sessions/<sessionId>"
},
... ... }
|
|