Re: [edk2-devel] [edk2-announce] TianoCore Community Design Meeting Minutes - Apr 3, 2020

["Abner Chang" <abner.chang@hpe.com>]

Hi Mike,
Per to the comment from last TianoCore design meeting, which repo RedfishPkg should stay? Edk2 repo or edk2-platform?

Abner

> -----Original Message-----
> From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of
> Abner Chang
> Sent: Wednesday, April 8, 2020 5:53 PM
> To: devel@edk2.groups.io
> Cc: Ni, Ray <ray.ni@intel.com>
> Subject: Re: [edk2-devel] [edk2-announce] TianoCore Community Design
> Meeting Minutes - Apr 3, 2020
> 
> 
> 
> > -----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.
> >
> >
> 
> 
>