OpenBMC 1/30 community telecon - Call for Topics

OpenBMC 1/30 community telecon - Call for Topics

[Brad Bishop]

[-- Attachment #1: Type: text/plain, Size: 345 bytes --]

Please reply with any topics for the 1/30 call.

thx - brad
--------
https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=85891389&accessNumber=2158616239 <https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=85891389&accessNumber=2158616239>

Monday, 10:00pm EDT
888-426-6840
password: 85891389

[-- Attachment #2: Type: text/html, Size: 1610 bytes --]

Re: OpenBMC 1/29 community telecon - Call for Topics

[Brad Bishop]

> On Jan 23, 2018, at 11:42 AM, Brad Bishop <bradleyb@fuzziesquirrel.com> wrote:
> 
> Please reply with any topics for the 1/30 call.

Oops - as usual the call will be Monday which is 1/29.

> 
> thx - brad
> --------
> https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=85891389&accessNumber=2158616239
> 
> Monday, 10:00pm EDT
> 888-426-6840
> password: 85891389

Re: OpenBMC 1/29 community telecon - Call for Topics

[Brad Bishop]

I’d like to talk about how OpenBMC might support systems with BMC redundancy.
Please join to discuss if that is interesting to you.

thx - brad


> On Jan 23, 2018, at 1:12 PM, Brad Bishop <bradleyb@fuzziesquirrel.com> wrote:
> 
> 
> 
>> On Jan 23, 2018, at 11:42 AM, Brad Bishop <bradleyb@fuzziesquirrel.com> wrote:
>> 
>> Please reply with any topics for the 1/30 call.
> 
> Oops - as usual the call will be Monday which is 1/29.
> 
>> 
>> thx - brad
>> --------
>> https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=85891389&accessNumber=2158616239
>> 
>> Monday, 10:00pm EDT
>> 888-426-6840
>> password: 85891389
> 

Re: OpenBMC 1/29 community telecon - Call for Topics

[Andrew Geissler]

I've got a couple misc one's, time permitting:

- How's the yocto 2.4 update going, any discussion needed on the
separate layer discussion?
- How's SELinux looking?
- Redfish workgroup going somewhere? Seems like we have a few
implementations out there already and people working on more, how do
we converge?
- Other workgroups?  IP KVM (2799), Remote Media (261), SNMP (2800),
User ID Mgmt (273).
- Did we ever get a doc that mapped people's names to IIRC handles?

Thanks,
Andrew

On Mon, Jan 29, 2018 at 9:47 AM, Brad Bishop
<bradleyb@fuzziesquirrel.com> wrote:
> I’d like to talk about how OpenBMC might support systems with BMC redundancy.
> Please join to discuss if that is interesting to you.
>
> thx - brad
>
>
>> On Jan 23, 2018, at 1:12 PM, Brad Bishop <bradleyb@fuzziesquirrel.com> wrote:
>>
>>
>>
>>> On Jan 23, 2018, at 11:42 AM, Brad Bishop <bradleyb@fuzziesquirrel.com> wrote:
>>>
>>> Please reply with any topics for the 1/30 call.
>>
>> Oops - as usual the call will be Monday which is 1/29.
>>
>>>
>>> thx - brad
>>> --------
>>> https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=85891389&accessNumber=2158616239
>>>
>>> Monday, 10:00pm EDT
>>> 888-426-6840
>>> password: 85891389
>>

Re: OpenBMC 1/29 community telecon - Call for Topics

[Stewart Smith]

Brad Bishop <bradleyb@fuzziesquirrel.com> writes:
> I’d like to talk about how OpenBMC might support systems with BMC redundancy.
> Please join to discuss if that is interesting to you.

Interesting!

Considering in a past life I worked on high availability clustered
databases, I may be able to contribute some design/design review around
some of these parts.

-- 
Stewart Smith
OPAL Architect, IBM.