From: "Abner Chang" <abner.chang@hpe.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Ni, Ray" <ray.ni@intel.com>
Subject: Re: [edk2-announce] TianoCore Community Design Meeting Minutes - Apr 3, 2020
Date: Wed, 8 Apr 2020 09:53:11 +0000 [thread overview]
Message-ID: <TU4PR8401MB0429ECE678515DCCFC70F40DFFC00@TU4PR8401MB0429.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <H4HJ.1586309281291201951.NmQ1@groups.io>
> -----Original Message-----
> From: announce@edk2.groups.io [mailto:announce@edk2.groups.io] On
> Behalf Of Ni, Ray
> Sent: Wednesday, April 8, 2020 9:28 AM
> To: announce@edk2.groups.io
> Subject: [edk2-announce] TianoCore Community Design Meeting Minutes -
> Apr 3, 2020
>
> Topic:
>
> 1. EDK2 Redfish Implementation Review (Directory/File Structure)
>
> Slides: INVALID URI REMOVED
> 3A__edk2.groups.io_g_devel_files_Designs_2020_0403_EDK2-2520Redfish-
> 2520Implementation-
> 2520Review.pdf&d=DwIFaQ&c=C5b8zRQO1miGmBeVZ2LFWg&r=_SN6FZBN4
> Vgi4Ulkskz6qU3NYRO03nHp9P7Z5q59A3E&m=lFA3ifo6O5zNAwZmZJ5oMe5G
> YnEwNW5YDIxrpVFiJZA&s=OEiHjFFyyjnHiCpZ_bzKiEXWN3BzYdjb3OAOx9JX_
> vk&e=
>
> * RedfishPkg
>
> * /IndustryStandard: Industry standard definitions should be in MdePkg.
> * /Protocol: UEFI/PI protocols should be in MdePkg
>
> @Felix: A general guideline is don't use EFI_ prefix if a protocol is not
> defined in UEFI/PI spec.
>
> @Ray: For protocols planned to be in UEFI/PI spec, encourage to use code
> first process (INVALID URI REMOVED
> 3A__edk2.groups.io_g_devel_topic_72500372&d=DwIFaQ&c=C5b8zRQO1mi
> GmBeVZ2LFWg&r=_SN6FZBN4Vgi4Ulkskz6qU3NYRO03nHp9P7Z5q59A3E&m=
> lFA3ifo6O5zNAwZmZJ5oMe5GYnEwNW5YDIxrpVFiJZA&s=hOSbYwIBFKoU5M
> dv-PYU72UIWqyBxYUQNrv4gSwyGjI&e= ).
>
> * /Pcd: Looks good
>
> UINTN to UINT32 change is good to Siyuan/Jiaxin/Fan.
>
> @Ray: Suggest to submit a bugzilla for structure pcd tool issue.
>
> * EmulatorPkg
> * /Application/RedfishPlatformConfig: Location looks good.
> * /Library
> * RedfishPlatformHostInterfaceLib: platform specific lib consuming
> variables created by /Application/RedfishPlatformConfig. Location looks good.
> * RedfishPlatformCredentialLib: Location looks good.
> * WinSnp
> * New PCD PcdEmuNetworkInterface to select network interface by index.
>
> @Siyuan: Suggest to use existing PCD by put the index integer in string
> format.
> * NetworkPkg: NETWORK_HTTP_BOOT_ENABLE macro
>
> Do not include HttpDxe driver when NETWORK_HTTP_BOOT_ENABLE is
> FALSE to hide HTTP boot option from boot option list.
>
> @igork: SMBIOS 42 contains field pointing to URL so please include DnsDxe
> driver even when NETWORK_HTTP_BOOT_ENABLE is FALSE.
>
> @Abner: Will evaluate today's RedfishPlatformHostInterfaceLib to support
> IP address and URL.
[Abner] Yes, HttpDns driver should be also involved to build for accessing to Redfish service if using hostname. However, the HostName is not defined clearly in Redfish Host Interface spec. Such as should Redfish Client use IP address of HostName queried from DNS to connect to Redfish service? This instead of using IP address from Redfish Service IP Address filed which maybe left as 0s if HostName is not NULL. I had some talks with Redfish Host Interface spec owner and he will revise it and make the description clear.
>
> @Felix: Can you put RestEx driver in NetworkPkg because RestEx does not
> only support Redfish stack.
[Abner] AsyncSendReceive and EventService functions are RESTful service implementation specific, for example the implementation of event service for AWS, Redfish, OpenStack is different. The current implementation is to have Redfish REST EX driver for Redfish service and stay in RedfishPkg.
>
>
next parent reply other threads:[~2020-04-08 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <H4HJ.1586309281291201951.NmQ1@groups.io>
2020-04-08 9:53 ` Abner Chang [this message]
[not found] ` <1603CF75396F979D.15536@groups.io>
2020-04-14 15:58 ` [edk2-devel] [edk2-announce] TianoCore Community Design Meeting Minutes - Apr 3, 2020 Abner Chang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=TU4PR8401MB0429ECE678515DCCFC70F40DFFC00@TU4PR8401MB0429.NAMPRD84.PROD.OUTLOOK.COM \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox