Return-Path: Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=linux.ibm.com (client-ip=148.163.156.1; helo=mx0a-001b2d01.pphosted.com; envelope-from=anoo@linux.ibm.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=linux.ibm.com 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 47DbGZ6NcMzF7hl; Fri, 15 Nov 2019 09:08:38 +1100 (AEDT) Received: from pps.filterd (m0098396.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id xAELxWl5030779; Thu, 14 Nov 2019 17:08:34 -0500 Received: from ppma02wdc.us.ibm.com (aa.5b.37a9.ip4.static.sl-reverse.com [169.55.91.170]) by mx0a-001b2d01.pphosted.com with ESMTP id 2w9fb009h8-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 14 Nov 2019 17:08:34 -0500 Received: from pps.filterd (ppma02wdc.us.ibm.com [127.0.0.1]) by ppma02wdc.us.ibm.com (8.16.0.27/8.16.0.27) with SMTP id xAEM0DnI006811; Thu, 14 Nov 2019 22:08:33 GMT Received: from b01cxnp23033.gho.pok.ibm.com (b01cxnp23033.gho.pok.ibm.com [9.57.198.28]) by ppma02wdc.us.ibm.com with ESMTP id 2w9f8q837a-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 14 Nov 2019 22:08:33 +0000 Received: from b01ledav006.gho.pok.ibm.com (b01ledav006.gho.pok.ibm.com [9.57.199.111]) by b01cxnp23033.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id xAEM8VlY13238610 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 14 Nov 2019 22:08:31 GMT Received: from b01ledav006.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 98D45ACA29; Thu, 14 Nov 2019 22:08:31 +0000 (GMT) Received: from b01ledav006.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 47060ACA28; Thu, 14 Nov 2019 22:08:31 +0000 (GMT) Received: from ltc.linux.ibm.com (unknown [9.16.170.189]) by b01ledav006.gho.pok.ibm.com (Postfix) with ESMTP; Thu, 14 Nov 2019 22:08:31 +0000 (GMT) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 14 Nov 2019 16:10:11 -0600 From: Adriana Kobylak To: "Alexander A. Filippov" Cc: openbmc@lists.ozlabs.org, openbmc Subject: Re: Packaging and deploying multiple firmware image types in one In-Reply-To: <20191114075131.GA6696@bbwork.lan> References: <20191112074921.GA4938@bbwork.lan> <9ddc3deca00904404c72a49c4f89c8a4@linux.vnet.ibm.com> <20191114075131.GA6696@bbwork.lan> Message-ID: <8755e79fb8f5b06113a953039daa2348@linux.vnet.ibm.com> X-Sender: anoo@linux.ibm.com User-Agent: Roundcube Webmail/1.0.1 X-TM-AS-GCONF: 00 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-11-14_05:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=825 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1911140000 definitions=main-1911140178 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: Thu, 14 Nov 2019 22:08:39 -0000 On 2019-11-14 01:51, Alexander A. Filippov wrote: > On Tue, Nov 12, 2019 at 04:54:22PM -0600, Adriana Kobylak wrote: >> >> Yeah, the purpose is not currently preserved across reboots. I have a >> change >> here for that: >> https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-bmc-code-mgmt/+/27045 >> > > On Thu, Nov 14, 2019 at 03:14:41AM +0000, Adriana Kobylak (Code Review) > wrote: >> ... >> but let's continue on the mailing list about your thoughts on how you >> think >> the tarball of tarballs should be handled. >> > > Ok, here are my thoughts: > The phosphor-version-software-manager might put all internal tarballs > in the > /tmp/images folder during processing the top level tarball. That will > lead to > creation of corresponding D-Bus objects. Each of them will have their > own > purpose, version, object path and so on. Yeah agree. We may still need some way to let the phosphor-version-software-manager know that it needs to untar the internal tarballs, maybe a very simple MANIFEST with a new field, then each individual tarball would have their own MANIFEST that creates the D-Bus versions like you mentioned. > > The root D-Bus object and their folder might be removed after that to > reduce a > used file system space.