* Invitation: BMC/Redfish Aggregator Use Case and Requirements @ Thu Jan 16, 2020 10am - 11am (PST) (openbmc@lists.ozlabs.org)
@ 2020-01-14 0:22 rhanley
0 siblings, 0 replies; only message in thread
From: rhanley @ 2020-01-14 0:22 UTC (permalink / raw)
To: openbmc, vishwa, neladk
[-- Attachment #1.1: Type: text/plain, Size: 2220 bytes --]
You have been invited to the following event.
Title: BMC/Redfish Aggregator Use Case and Requirements
There has been some email discussion on the mailing list about working on a
Redfish aggregator. I'd like to take some time to have a live discussion
about various use cases and requirements.
Some agenda items to consider:
1) Layer 2/3 discovery and negotiation
2) Caching, proxy, and consistency requirements
3) Target hardware, performance requirements, and scale of aggregation
4) Tooling and infrastructure improvements needed to support an aggregator
5) Amount of configuration and knowledge an aggregator needs to know a
priori.
6) Data presentation from Inband?
7) Security
When: Thu Jan 16, 2020 10am – 11am Pacific Time - Los Angeles
Where: SVL-MAT3-4-Sea Drive (7) [GVC]
Joining info: Join Hangouts Meet
https://meet.google.com/bqh-ajec-bqy
Join by phone
+1 707-702-2738 (PIN: 293302)
More phone numbers: https://tel.meet/bqh-ajec-bqy?pin=9001976403191&hs=0
Calendar: openbmc@lists.ozlabs.org
Who:
* rhanley@google.com - organizer
* openbmc@lists.ozlabs.org
* vishwa@linux.vnet.ibm.com
* neladk@microsoft.com
* Nancy Yuen - optional
Event details:
https://www.google.com/calendar/event?action=VIEW&eid=NTVuZ2FtaW9jaWpwNmQ1cW42NHU1NGVmaHAgb3BlbmJtY0BsaXN0cy5vemxhYnMub3Jn&tok=MTgjcmhhbmxleUBnb29nbGUuY29tYzlmNWUyYjQ1OTE4ZDMxY2ZlMmUyZDFmZmUxOGRjMDU2MWMzOTI3Nw&ctz=America%2FLos_Angeles&hl=en&es=0
Invitation from Google Calendar: https://www.google.com/calendar/
You are receiving this courtesy email at the account
openbmc@lists.ozlabs.org because you are an attendee of this event.
To stop receiving future updates for this event, decline this event.
Alternatively you can sign up for a Google account at
https://www.google.com/calendar/ and control your notification settings for
your entire calendar.
Forwarding this invitation could allow any recipient to send a response to
the organizer and be added to the guest list, or invite others regardless
of their own invitation status, or to modify your RSVP. Learn more at
https://support.google.com/calendar/answer/37135#forwarding
[-- Attachment #1.2: Type: text/html, Size: 13795 bytes --]
[-- Attachment #1.3: Type: text/calendar, Size: 2870 bytes --]
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20200116T180000Z
DTEND:20200116T190000Z
DTSTAMP:20200114T002200Z
ORGANIZER;CN=rhanley@google.com:mailto:rhanley@google.com
UID:55ngamiocijp6d5qn64u54efhp@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=openbmc@lists.ozlabs.org;X-NUM-GUESTS=0:mailto:openbmc@lists.ozlabs
.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=Nancy Yuen;X-NUM-GUESTS=0:mailto:yuenn@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
;CN=rhanley@google.com;X-NUM-GUESTS=0:mailto:rhanley@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=vishwa@linux.vnet.ibm.com;X-NUM-GUESTS=0:mailto:vishwa@linux.vnet.i
bm.com
ATTENDEE;CUTYPE=RESOURCE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TR
UE;CN=SVL-MAT3-4-Sea Drive (7) [GVC];X-NUM-GUESTS=0:mailto:google.com_726f6
f6d5f75735f73766c5f6d6174335f345f346a37@resource.calendar.google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=neladk@microsoft.com;X-NUM-GUESTS=0:mailto:neladk@microsoft.com
X-MICROSOFT-CDO-OWNERAPPTID:-1954189224
CREATED:20200114T002159Z
DESCRIPTION:There has been some email discussion on the mailing list about
working on a Redfish aggregator. I'd like to take some time to have a live
discussion about various use cases and requirements.\n\nSome agenda items
to consider:\n\n1) Layer 2/3 discovery and negotiation\n\n2) Caching\, prox
y\, and consistency requirements\n\n3) Target hardware\, performance requir
ements\, and scale of aggregation\n\n4) Tooling and infrastructure improvem
ents needed to support an aggregator\n\n5) Amount of configuration and know
ledge an aggregator needs to know a priori.\n\n6) Data presentation from In
band?\n\n7) Security \n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\nPlease do not edit this section of t
he description.\n\nThis event has a video call.\nJoin: https://meet.google.
com/bqh-ajec-bqy\n+1 707-702-2738 PIN: 293302#\nView more phone numbers: ht
tps://tel.meet/bqh-ajec-bqy?pin=9001976403191&hs=7\n\nView your event at ht
tps://www.google.com/calendar/event?action=VIEW&eid=NTVuZ2FtaW9jaWpwNmQ1cW4
2NHU1NGVmaHAgb3BlbmJtY0BsaXN0cy5vemxhYnMub3Jn&tok=MTgjcmhhbmxleUBnb29nbGUuY
29tYzlmNWUyYjQ1OTE4ZDMxY2ZlMmUyZDFmZmUxOGRjMDU2MWMzOTI3Nw&ctz=America%2FLos
_Angeles&hl=en&es=1.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20200114T002159Z
LOCATION:SVL-MAT3-4-Sea Drive (7) [GVC]
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:BMC/Redfish Aggregator Use Case and Requirements
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR
[-- Attachment #2: invite.ics --]
[-- Type: application/ics, Size: 2924 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-01-14 0:22 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-14 0:22 Invitation: BMC/Redfish Aggregator Use Case and Requirements @ Thu Jan 16, 2020 10am - 11am (PST) (openbmc@lists.ozlabs.org) rhanley
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.