From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=mnE+=DB=lists.ozlabs.org=openbmc-bounces+openbmc=archiver.kernel.org@kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
X-Spam-Level: 
X-Spam-Status: No, score=-3.9 required=3.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,
	SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no
	version=3.4.0
Received: from mail.kernel.org (mail.kernel.org [198.145.29.99])
	by smtp.lore.kernel.org (Postfix) with ESMTP id 717D0C2D0E2
	for <openbmc@archiver.kernel.org>; Thu, 24 Sep 2020 16:19:37 +0000 (UTC)
Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by mail.kernel.org (Postfix) with ESMTPS id AFB532311B
	for <openbmc@archiver.kernel.org>; Thu, 24 Sep 2020 16:19:36 +0000 (UTC)
Authentication-Results: mail.kernel.org;
	dkim=pass (1024-bit key) header.d=yadro.com header.i=@yadro.com header.b="r/ftU+Fa"
DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org AFB532311B
Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=yadro.com
Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=openbmc-bounces+openbmc=archiver.kernel.org@lists.ozlabs.org
Received: from bilbo.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3])
	by lists.ozlabs.org (Postfix) with ESMTP id 4By0cP5FMFzDqkC
	for <openbmc@archiver.kernel.org>; Fri, 25 Sep 2020 02:19:33 +1000 (AEST)
Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized)
 smtp.mailfrom=yadro.com (client-ip=89.207.88.252; helo=mta-01.yadro.com;
 envelope-from=a.kartashev@yadro.com; receiver=<UNKNOWN>)
Authentication-Results: lists.ozlabs.org;
 dmarc=pass (p=none dis=none) header.from=yadro.com
Authentication-Results: lists.ozlabs.org; dkim=pass (1024-bit key;
 unprotected) header.d=yadro.com header.i=@yadro.com header.a=rsa-sha256
 header.s=mta-01 header.b=r/ftU+Fa; dkim-atps=neutral
Received: from mta-01.yadro.com (mta-02.yadro.com [89.207.88.252])
 (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 4By0Zf12hlzDqRs
 for <openbmc@lists.ozlabs.org>; Fri, 25 Sep 2020 02:18:02 +1000 (AEST)
Received: from localhost (unknown [127.0.0.1])
 by mta-01.yadro.com (Postfix) with ESMTP id 7BE50579F2
 for <openbmc@lists.ozlabs.org>; Thu, 24 Sep 2020 16:17:58 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yadro.com; h=
 content-transfer-encoding:mime-version:user-agent:content-type
 :content-type:organization:references:in-reply-to:date:date:from
 :from:subject:subject:message-id:received:received:received; s=
 mta-01; t=1600964277; x=1602778678; bh=dxCe+pIUfLoxYSNR7syRE3hX4
 3jp+YdPoGNvKPA0gW8=; b=r/ftU+FaJj7Q1TRovTjWI7jV4butWTbkW4J65+cDx
 3KdJWZgEWqZFRhvsKg427QHG2u76DjHuimWuTGcbue2578wXS4MeJYx7b/r++IMs
 r3gzDwRA3jwcFCoo0+wjS7kOcnlHbZGWPYqNesaESncTq/YW34N/mK3NvO53KeBz
 S0=
X-Virus-Scanned: amavisd-new at yadro.com
Received: from mta-01.yadro.com ([127.0.0.1])
 by localhost (mta-01.yadro.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id PJzoDRx7fz2w for <openbmc@lists.ozlabs.org>;
 Thu, 24 Sep 2020 19:17:57 +0300 (MSK)
Received: from T-EXCH-04.corp.yadro.com (t-exch-04.corp.yadro.com
 [172.17.100.104])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits))
 (No client certificate requested)
 by mta-01.yadro.com (Postfix) with ESMTPS id 18CAD57953
 for <openbmc@lists.ozlabs.org>; Thu, 24 Sep 2020 19:17:57 +0300 (MSK)
Received: from [10.199.3.26] (10.199.3.26) by T-EXCH-04.corp.yadro.com
 (172.17.100.104) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.669.32; Thu, 24
 Sep 2020 19:17:56 +0300
Message-ID: <0b1e848f0f47c4cd8f1faeabfa60bfd285e23d60.camel@yadro.com>
Subject: Re: entity manager configurations and dbus interfaces
From: Andrei Kartashev <a.kartashev@yadro.com>
To: openbmc <openbmc@lists.ozlabs.org>
Date: Thu, 24 Sep 2020 19:17:55 +0300
In-Reply-To: <CACWQX83msYLyZxcNfoMKWd5LmoQ+OZpK302=irPedea46ziZrw@mail.gmail.com>
References: <20200924143036.inmugtvxkj3f6zny@thinkpad.fuzziesquirrel.com>
 <d4761f08a2beca775827171d4d1934cd76641cb5.camel@yadro.com>
 <CACWQX83msYLyZxcNfoMKWd5LmoQ+OZpK302=irPedea46ziZrw@mail.gmail.com>
Organization: YADRO
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.5 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.199.3.26]
X-ClientProxiedBy: T-EXCH-01.corp.yadro.com (172.17.10.101) To
 T-EXCH-04.corp.yadro.com (172.17.100.104)
X-BeenThere: openbmc@lists.ozlabs.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Development list for OpenBMC <openbmc.lists.ozlabs.org>
List-Unsubscribe: <https://lists.ozlabs.org/options/openbmc>,
 <mailto:openbmc-request@lists.ozlabs.org?subject=unsubscribe>
List-Archive: <http://lists.ozlabs.org/pipermail/openbmc/>
List-Post: <mailto:openbmc@lists.ozlabs.org>
List-Help: <mailto:openbmc-request@lists.ozlabs.org?subject=help>
List-Subscribe: <https://lists.ozlabs.org/listinfo/openbmc>,
 <mailto:openbmc-request@lists.ozlabs.org?subject=subscribe>
Errors-To: openbmc-bounces+openbmc=archiver.kernel.org@lists.ozlabs.org
Sender: "openbmc"
 <openbmc-bounces+openbmc=archiver.kernel.org@lists.ozlabs.org>

Well, I didn't meant EM is bad, it was "I don't understand well how all
this supposed to work".
Now I have number of inputs from you in different topics but I still
need to bring things together to get the picture.

On Thu, 2020-09-24 at 08:54 -0700, Ed Tanous wrote:
> On Thu, Sep 24, 2020 at 8:43 AM Andrei Kartashev <
> a.kartashev@yadro.com> wrote:
> > Hi Brad,
> > 
> > Thank for bring up this question.
> > Same as you we have slightly bad view on EM architecture since
> > before
> > we had only Power-based platforms and now we are working on our
> > first
> > x86-based one.
> 
> Can you go into more specifics about what you don't like about it?  I
> know a lot of the complaints I've heard revolves around
> documentation.
> I'm trying to hammer away at that as I get time.  Is there any other
> low hanging fruit that we can fix that's entity-manager specific?
> 
> > Following up the discussion in the review and also mailing
> > discussion
> > we had early, I now preparing some Implementation Proposal document
> > for
> > EM-based inventory. I gonna to submit it to docs repo for
> > discussing
> > and finding our common understanding of how it supposed to be.
> > 
> > 
> > On Thu, 2020-09-24 at 10:30 -0400, Brad Bishop wrote:
> > > Hi Ed
> > > 
> > > Will quote a comment from this EM review:
> > > 
> > > https://gerrit.openbmc-project.xyz/36702
> > > 
> > > > entity-manager was designed with the tenant that it config
> > > > files
> > > > have
> > > > no knowledge of dbus.
> > > 
> > > FWIW I had no idea this was the case.
> > > 
> > > > We've broken that a little with the inventory interfaces on the
> > > > entity
> > > > as a short term patch to gain some compatibility, but its easy
> > > > enough
> > > > to roll back in the future.
> > > 
> > > Interesting - so there is a vision here, but I have no idea what
> > > it
> > > is.
> > > Can you elaborate on how you envision inventory working if EM is
> > > not
> > > implementing the inventory dbus interfaces?
> > > 
> > > thx - brad
> > --
> > Best regards,
> > Andrei Kartashev
> > 
> > 
-- 
Best regards,
Andrei Kartashev