From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Authentication-Results: ozlabs.org; spf=pass (mailfrom) smtp.mailfrom=in.ibm.com (client-ip=148.163.156.1; helo=mx0a-001b2d01.pphosted.com; envelope-from=sivas.srr@in.ibm.com; receiver=) Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3yN8Lr3SZRzDqkJ for ; Fri, 27 Oct 2017 01:21:08 +1100 (AEDT) Received: from pps.filterd (m0098404.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v9QEKtXG044429 for ; Thu, 26 Oct 2017 10:21:05 -0400 Received: from smtp.notes.na.collabserv.com (smtp.notes.na.collabserv.com [192.155.248.73]) by mx0a-001b2d01.pphosted.com with ESMTP id 2dugkravqc-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 26 Oct 2017 10:21:04 -0400 Received: from localhost by smtp.notes.na.collabserv.com with smtp.notes.na.collabserv.com ESMTP for from ; Thu, 26 Oct 2017 14:21:02 -0000 Received: from us1a3-smtp03.a3.dal06.isc4sb.com (10.106.154.98) by smtp.notes.na.collabserv.com (10.106.227.90) with smtp.notes.na.collabserv.com ESMTP; Thu, 26 Oct 2017 14:21:01 -0000 Received: from us1a3-mail65.a3.dal09.isc4sb.com ([10.142.3.23]) by us1a3-smtp03.a3.dal06.isc4sb.com with ESMTP id 2017102614210077-691820 ; Thu, 26 Oct 2017 14:21:00 +0000 Subject: Re: OpenBMC community telecon - New time! In-Reply-To: From: "Sivas Srr" To: bradleyb@fuzziesquirrel.com Cc: openbmc@lists.ozlabs.org Date: Thu, 26 Oct 2017 14:21:01 +0000 Sensitivity: MIME-Version: 1.0 References: , <242042C5-601B-45C0-B6CA-D9EEB173A753@fuzziesquirrel.com> Importance: Normal X-Priority: 3 (Normal) X-Mailer: IBM Verse Build 15600-1257 | IBM Domino Build SCN17263_20170920T0022_FP4 October 11, 2017 at 08:48 X-LLNOutbound: False X-Disclaimed: 32535 X-TNEFEvaluated: 1 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8 x-cbid: 17102614-3107-0000-0000-0000037DCA4E X-IBM-SpamModules-Scores: BY=0; FL=0; FP=0; FZ=0; HX=0; KW=0; PH=0; SC=0.410169; ST=0; TS=0; UL=0; ISC=; MB=0.095403 X-IBM-SpamModules-Versions: BY=3.00007955; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000239; SDB=6.00936758; UDB=6.00472080; IPR=6.00717020; BA=6.00005660; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00017725; XFM=3.00000015; UTC=2017-10-26 14:21:02 X-IBM-AV-DETECTION: SAVI=unsuspicious REMOTE=unsuspicious XFE=unused X-IBM-AV-VERSION: SAVI=2017-10-26 00:59:38 - 6.00007517 x-cbparentid: 17102614-3108-0000-0000-00006B04EE8B Message-Id: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-10-26_04:, , signatures=0 X-Proofpoint-Spam-Reason: safe X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.24 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Oct 2017 14:21:10 -0000
Thank you Brad fo= r adjusting time.
 
Have multiple topics:
 
1) How about using MQTT for Telemetry - MQTT is light wei= ght and it uses
widely and it is from IBM.
 
2) root allowed to set with null password - Just because = linux community allows
do we (openbmc application) also need to allow ?  I = dont think other applications
based on linux like HMC / FSP allows it. BMC is base for = server where chances of multiple VMs can run. Do we need to worry about the= security/safety of those?
 
3) bmc dump performance improvement - less priority - it = is taking care, I guess.
 
<= div style=3D"font-size: 12pt; font-weight: bold; font-family: sans-serif; c= olor: #7C7C5F;" >Sivas R. S
=
E2E FSP Test Architecture, OpenBMC Test Lead, Lab Management
Automation is good, Identifying Defect earlier is better always
9902233500
08046678273
 
 
----- Original message -----
From: Brad Bishop <br= adleyb@fuzziesquirrel.com>
Sent by: "openbmc" <openbmc-bounces+siv= as.srr=3Din.ibm.com@lists.ozlabs.org>
To: OpenBMC <openbmc@lists.o= zlabs.org>
Cc:
Subject: OpenBMC community telecon - New time!
D= ate: Thu, Oct 26, 2017 7:00 PM
 
Hi everyone.

This telec= on will be moving to a new time starting this Monday 10/30.
=
The new time is 10:00PM EDT.

thx - brad


= > Begin forwarded message:
>
> From: Brad Bishop <bradleyb@fuzziesquirrel.c= om>
> Subject: Op= enBMC community telecon
>=  Date: October 23, 2017 at 9:55:17 AM EDT
> To: OpenBMC <openbmc@lists.ozlabs.org>
>
> For the last year or so a small group of t= echnical folks have been

>= ; meeting Monday evenings at 8:30 EDT to discuss the ins and outs of
> working with the co= de at github.com/openbmc.
&g= t;
> Given the annou= ncement made by Chris Austen here:
https://urldefense.proofpoint.com/v2/url?u=3Dhttp= s-3A=5F=5Flists.ozlabs.org=5Fpipermail=5Fopenbmc=5F2017-2DSeptember=5F00928= 9.html&d=3DDwICAg&c=3Djf=5FiaSHvJObTbx-siA1ZOg&r=3DQcbdMr=5FGcD= 0whMjo3lNOD6NrR5C5mjWsWSGeIA8x3JQ&m=3D-1f3RyDjZaoOEKPG6ANRrPxqxn31Z1gxz= VFMDgLgcKg&s=3D2kPqwha8SLbHh3JDNtw8rVwSSBT2lDJDUBB=5Fjho0=5FX4&e=3D=
>
> the time seems right to open this me= eting up to the entire

>&= nbsp;community.  The meeting information is:
> Mondays, 8:30 EDT
> 888-426-6840
> password: 85891389
>
>=  Please feel free to join if you have a technical topic or just want t= o
> listen in.  = ;I will send out a weekly request for topics - please reply
= > if you have one so I can set an a= genda.  Some example topics might be
> based around:
>
> - p= rogress of contributions to the repo
> - technical questions on future contributions
> - (brief) code review discus= sion; additional to anything on the
>  mailing list
>
> Going for= ward I'd like to make our primary medium for discussion of
<= tt>> topics be the mailing list.  = So please consider using that rather than

> waiting until the meeting.
>

= > The OpenBMC community is hard at work establishing a formal proje= ct
> governance mode= l.  Once that model is established this meeting will be> superseded by whatever process i= s selected for technical
>= ; steering.  Additionally, topics raised with any significant imp= act to
> the future = direction of the project will likely be tabled until that
> model is established.
>
> Thx - brad bishop