From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Authentication-Results: lists.ozlabs.org; spf=none (no SPF record) smtp.mailfrom=linux.intel.com (client-ip=192.55.52.88; helo=mga01.intel.com; envelope-from=james.feist@linux.intel.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=fail (p=none dis=none) header.from=linux.intel.com Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) (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 4Bs5Hy0mJxzDqb0 for ; Thu, 17 Sep 2020 02:33:17 +1000 (AEST) IronPort-SDR: /XD3bMX/DDznLZN2F5acLi8Rvf4S21Ntlcpu2TeP/h/5gRcVYrtLAnCg+ujfR2qZMcpoVRun9Q GmFS9OqsN9eg== X-IronPort-AV: E=McAfee;i="6000,8403,9746"; a="177584683" X-IronPort-AV: E=Sophos;i="5.76,433,1592895600"; d="scan'208";a="177584683" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 Sep 2020 09:33:11 -0700 IronPort-SDR: aiHf6DppO5H36a00EDx+hFKsq+tklSbyPD5Z29peDLAs48j4ZEca+bfl0cnquTCtVYD3FcH8GB bgRUN4f6ukyg== X-IronPort-AV: E=Sophos;i="5.76,433,1592895600"; d="scan'208";a="319894763" Received: from jfeist-mobl2.amr.corp.intel.com (HELO [10.212.68.202]) ([10.212.68.202]) by orsmga002-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 Sep 2020 09:33:10 -0700 Subject: Re: Using bios-settings-mgr for setting hypervisor network attributes To: Ed Tanous , manoj kiran Cc: "openbmc@lists.ozlabs.org" References: From: James Feist Message-ID: Date: Wed, 16 Sep 2020 09:33:07 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2020 16:33:19 -0000 On 9/16/2020 9:26 AM, Ed Tanous wrote: > > > On Wed, Sep 16, 2020 at 7:47 AM manoj kiran > wrote: > > Hi Ed & James, > > Till now IBM was using phosphor-settings infrastructure as back-end > and uses Ethernet Schema for Hypervisor computer > system(hypervisor_ethernet.hpp) for setting the IP address of > hypervisor. And now we are planning to leverage the capabilities of > bios-settings-mgr(backend) as well to set the hypervisor attributes. > > do you see any concerns here ? > > Thanks, > Manoj > Sent from Mailspring > > > None that I can think of (although I don't know much about > bios-settings-mgr).  Holding all the host data in one daemon seems like > a better way to do it than putting it in settings. Agree, as long as we use the mapper to look up interfaces, should be transparent.